| Bug #64056 | Field copy via right-click menu failed | ||
|---|---|---|---|
| Submitted: | 18 Jan 2012 0:20 | Modified: | 27 Mar 2012 9:56 |
| Reporter: | Roger Bass | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
| Version: | 5.2.37 CE Rev 8576 | OS: | Windows |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | clipboard, copy | ||
[18 Jan 2012 0:20]
Roger Bass
[18 Jan 2012 5:19]
Valeriy Kravchuk
When you'll get this error again, please, right click somewhere in the error dialog box with no text and use Copy stack trace to clipboard context menu item. Send stack trace to this report.
[20 Jan 2012 18:23]
Roger Bass
Stack trace: Exception = System.Runtime.InteropServices.ExternalException Message = Requested Clipboard operation did not succeed. FullText = System.Runtime.InteropServices.ExternalException (0x800401D0): Requested Clipboard operation did not succeed. at System.Windows.Forms.Clipboard.ThrowIfFailed(Int32 hr) at System.Windows.Forms.Clipboard.SetDataObject(Object data, Boolean copy, Int32 retryTimes, Int32 retryDelay) at System.Windows.Forms.Clipboard.SetText(String text, TextDataFormat format) at System.Windows.Forms.Clipboard.SetText(String text) at MySQL.Forms.UtilitiesImpl.set_clipboard_text(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* content) at MySQL.MCallback1<void\,std::basic_string<char\,std::char_traits<char>\,std::allocator<char> > const \&>.cpp_callback(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* arg1) at MySQL.Grt.Db.RecordsetWrapper.activate_popup_menu_item(String action, List`1 rows, Int32 column) at MySQL.GUI.Workbench.SqlIdeMenuManager.OnMenuItemClick(Object sender, EventArgs e) at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
[24 Jan 2012 9:13]
Valeriy Kravchuk
Please, send the output of Help > System Info also.
[25 Feb 2012 1: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".
[25 Feb 2012 2:27]
Roger Bass
Starting thread...
Thread started
18068 INFO Connecting to SSH server at ec2-174-129-242-117.compute-1.amazonaws.com:22 using key C:\Users\Roger\Documents\Traxian\Operations\AWS\Traxian.pem...
C:\Program Files\MySQL\MySQL Workbench 5.2 CE/python/site-packages\paramiko\client.py:93: UserWarning: Unknown ssh-rsa host key for ec2-174-129-242-117.compute-1.amazonaws.com: 6ba558ebfa33fd2af5adbae049c4bd83
(key.get_name(), hostname, hexlify(key.get_fingerprint())))
18068 INFO Connection opened
New client connection
client connection established
18068 INFO Tunnel now open ('127.0.0.1', 49430) -> ('174.129.242.117', 22) -> ('127.0.0.1', 3306)
New client connection
client connection established
18068 INFO Tunnel now open ('127.0.0.1', 49433) -> ('174.129.242.117', 22) -> ('127.0.0.1', 3306)
No handlers could be found for logger "paramiko.transport"
Client for 18068 disconnected
Client for 18068 disconnected
Closing tunnel to ec2-174-129-242-117.compute-1.amazonaws.com:22 from inactivity...
Starting thread...
Thread started
20942 INFO Connecting to SSH server at ec2-174-129-242-117.compute-1.amazonaws.com:22 using key C:\Users\Roger\Documents\Traxian\Operations\AWS\Traxian.pem...
20942 INFO Connection opened
New client connection
client connection established
20942 INFO Tunnel now open ('127.0.0.1', 50602) -> ('174.129.242.117', 22) -> ('127.0.0.1', 3306)
New client connection
client connection established
20942 INFO Tunnel now open ('127.0.0.1', 50605) -> ('174.129.242.117', 22) -> ('127.0.0.1', 3306)
Client for 20942 disconnected
Client for 20942 disconnected
Closing tunnel to ec2-174-129-242-117.compute-1.amazonaws.com:22 from inactivity...
Starting thread...
Thread started
58060 INFO Connecting to SSH server at ec2-174-129-242-117.compute-1.amazonaws.com:22 using key C:\Users\Roger\Documents\Traxian\Operations\AWS\Traxian.pem...
58060 INFO Connection opened
New client connection
client connection established
58060 INFO Tunnel now open ('127.0.0.1', 51533) -> ('174.129.242.117', 22) -> ('127.0.0.1', 3306)
New client connection
client connection established
58060 INFO Tunnel now open ('127.0.0.1', 51538) -> ('174.129.242.117', 22) -> ('127.0.0.1', 3306)
Client for 58060 disconnected
Client for 58060 disconnected
New client connection
client connection established
58060 ERROR Remote connection to 127.0.0.1:3306 was rejected by the SSH server.
Closing tunnel to ec2-174-129-242-117.compute-1.amazonaws.com:22 from inactivity...
Starting thread...
Thread started
33210 INFO Connecting to SSH server at ec2-174-129-242-117.compute-1.amazonaws.com:22 using key C:\Users\Roger\Documents\Traxian\Operations\AWS\Traxian.pem...
33210 INFO Connection opened
New client connection
client connection established
33210 INFO Tunnel now open ('127.0.0.1', 62199) -> ('174.129.242.117', 22) -> ('127.0.0.1', 3306)
New client connection
client connection established
33210 INFO Tunnel now open ('127.0.0.1', 62202) -> ('174.129.242.117', 22) -> ('127.0.0.1', 3306)
Client for 33210 disconnected
Client for 33210 disconnected
New client connection
client connection established
33210 ERROR Remote connection to 127.0.0.1:3306 was rejected by the SSH server.
Closing tunnel to ec2-174-129-242-117.compute-1.amazonaws.com:22 from inactivity...
Starting thread...
Thread started
62695 INFO Connecting to SSH server at ec2-174-129-242-117.compute-1.amazonaws.com:22 using key C:\Users\Roger\Documents\Traxian\Operations\AWS\Traxian.pem...
62695 INFO Connection opened
New client connection
client connection established
62695 INFO Tunnel now open ('127.0.0.1', 53764) -> ('174.129.242.117', 22) -> ('127.0.0.1', 3306)
New client connection
client connection established
62695 INFO Tunnel now open ('127.0.0.1', 53769) -> ('174.129.242.117', 22) -> ('127.0.0.1', 3306)
MySQL Workbench CE for Windows version 5.2.37 revision 8576
Configuration Directory: C:\Users\Roger\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.
OpenGL Driver Version: 2.1.0 - Build 8.15.10.2302
OS: Microsoft Windows 7 Service Pack 1 (build 7601), 32-bit
CPU: 2x Intel(R) Core(TM)2 Duo CPU P8800 @ 2.66GHz, 3.0 GiB RAM
Active video adapter (0): Mobile Intel(R) 4 Series Express Chipset Family
Installed video RAM: 1287 MB
Current video mode: 1440 x 900 x 4294967296 colors
Used bit depth: 32
Driver version: 8.15.10.2302
Installed display drivers: igdumdx32.dll,igd10umd32.dll
Current user language: English (United States)
[27 Feb 2012 9:56]
Valeriy Kravchuk
Please, check if the same problem still happens with a newer version, 5.2.38.
[28 Mar 2012 1: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".
