Bug #55266 Workbench crash: Requested Clipboard operation did not succeed
Submitted: 14 Jul 2010 16:56 Modified: 15 Aug 2010 9:44
Reporter: Gisbert Selke (Basic Quality Contributor) Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Workbench: SQL Editor Severity:S2 (Serious)
Version:5.2.25 OS:Windows (XP)
Assigned to: CPU Architecture:Any
Tags: qc

[14 Jul 2010 16:56] Gisbert Selke
The result of a query is displayed (many rows returned, clipped to 1000). I highlight one cell in one of the result rows and press Ctrl-C to copy that value. Then I get a window "MySQL Workbench has encountered a problem", detail msg as per synopsis above.

How to repeat:
see above
[14 Jul 2010 16:58] MySQL Verification Team
Could you please provide the output of Help->System Info. Thanks in advance.
[14 Jul 2010 17:28] Gisbert Selke
I'd love to include the output of System Info, but after that message I cannot access my clipboard anymore. I'll have to reboot. Stay tuned...
[14 Jul 2010 17:38] Gisbert Selke
MySQL Workbench CE for Windows version 5.2.25
Data Directory: C:\Programme\MySQL\GUITools\Workbench
Cairo Version: 1.8.8
Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.
OpenGL Driver Version: 1.5.0 - Build
OS: Microsoft Windows XP Professional Service Pack 3 (build 2600)
CPU: 2x Intel(R) Core(TM)2 Duo CPU     L7100  @ 1.20GHz, 2.0 GiB RAM
Video adapter info:
Adapter type: Mobile Intel(R) 965 Express Chipset Family
Chip Type: Mobile Intel(R) 965 Express Chipset Family
BIOS String: Intel Video BIOS
Video Memory: 393216 KB
[14 Jul 2010 17:42] Valeriy Kravchuk
What is the data type of column for the problematic cell?
[14 Jul 2010 18:28] Gisbert Selke
int(10) unsigned not null
[15 Jul 2010 9:44] Susanne Ebrecht
Is the problem repeatable or was it a random failure?
[15 Aug 2010 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".