Segmentation fault: Ctrl + C in "Messages"

[cryos]

Ctrl+C doesn't work in "Messages" tab, causes Segmentation fault.
Rightclick->"Copy (Ctrl+C)" works, though.

Reported by: soc88

[cryos]

Logged In: YES
user_id=1883751
Originator: YES

avogadro
This is Avogadro, SVN revision 647M
("avogadro")
Found Engine: "Axes" - "Renders x, y and z axes"
Found Engine: "Dynamic Ball and Stick" - "Renders primitives using Balls (atoms) and Sticks (bonds). Includes demonstration of dynamic rendering based on distance from camera"
Found Engine: "Debug Info" - "Renders debug information"
Found Engine: "Label" - "Renders primitive labels"
Found Engine: "Ribbon" - "Renders residues as ribbons"
Found Engine: "VdW Sphere" - "Renders atoms as Van der Waals spheres"
Found Engine: "Stick" - "Renders as Cylinders"
Found Engine: "Wireframe" - "Wireframe rendering"
"libautorotatetool.so"
Found Tool: "AutoRotate" - "Auto Rotation Tool"
"libbondcentrictool.so"
Found Tool: "BondCentric" - "Bond Centric Manipulation Tool"
"libclickmeasuretool.so"
Found Tool: "ClickMeasure" - "Click to Measure Tool"
"libdrawtool.so"
Found Tool: "Draw" - "Draws Things"
"libmanipulatetool.so"
Found Tool: "Manipulate" - "Manipulation Tool"
"libnavigatetool.so"
Found Tool: "Navigate" - "Navigation Tool"
"libselectrotatetool.so"
Found Tool: "Select/Rotate" - "Selection and Rotation Tool"
SearchPath: "/usr/local/lib/avogadro/extensions"

Found Extension: "GAMESS" - "GAMESS Input Deck Generator"
Object::connect: Parentheses expected, slot Avogadro::GamessExtension::dockWidgetDestroyed
ForceFieldDialog::ForceFieldDialog()

Found Extension: "Ghemical" - "Ghemical Plugin"
Found Extension: "H2Methyl" - "H2Methyl Plugin"
Found Extension: "Hydrogens" - "Hydrogens Plugin"
Found Extension: "SMARTS" - "SMARTS Plugin"
Found Extension: "UnitCell" - "Unit Cell Parameters Plugin"
createObjects()
QObject::connect: Cannot queue arguments of type 'QTextCursor'
(Make sure 'QTextCursor' is registered using qRegisterMetaType().)
Segmentation fault

Original comment by: soc88

[cryos]

Logged In: YES
user_id=684210
Originator: NO

Running r656 I can still confirm this. Qt 4.3.1.

Here is my backtrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1225976112 (LWP 5356)]
0x00000010 in ?? ()
(gdb) bt
#0 0x00000010 in ?? ()
#1 0xb7879404 in QClipboard::setMimeData () from /usr//lib/libQtGui.so.4
#2 0x080671e7 in Avogadro::CopyCommand::redo ()
#3 0xb7ceea37 in QUndoStack::push () from /usr//lib/libQtGui.so.4
#4 0x080721ba in Avogadro::MainWindow::copy ()
#5 0x0807413b in Avogadro::MainWindow::qt_metacall ()
#6 0xb7477081 in QMetaObject::activate () from /usr//lib/libQtCore.so.4
#7 0xb7477390 in QMetaObject::activate () from /usr//lib/libQtCore.so.4
#8 0xb7817d51 in QAction::triggered () from /usr//lib/libQtGui.so.4
#9 0xb781888f in QAction::activate () from /usr//lib/libQtGui.so.4
#10 0xb781a680 in QAction::event () from /usr//lib/libQtGui.so.4
#11 0xb781dcf0 in QApplicationPrivate::notify_helper () from /usr//lib/libQtGui.so.4
#12 0xb7823dd9 in QApplication::notify () from /usr//lib/libQtGui.so.4
#13 0xb7465ecb in QCoreApplication::notifyInternal () from /usr//lib/libQtCore.so.4
#14 0xb784852a in QShortcut::QShortcut () from /usr//lib/libQtGui.so.4
#15 0xb7849a1f in QShortcut::QShortcut () from /usr//lib/libQtGui.so.4
#16 0xb78250c5 in QApplication::notify () from /usr//lib/libQtGui.so.4
#17 0xb7465ecb in QCoreApplication::notifyInternal () from /usr//lib/libQtCore.so.4
#18 0xb7869a0e in QApplicationPrivate::createEventDispatcher () from /usr//lib/libQtGui.so.4
#19 0xb7892c2f in QX11Info::copyX11Data () from /usr//lib/libQtGui.so.4
#20 0xb78948a2 in QX11Info::copyX11Data () from /usr//lib/libQtGui.so.4
#21 0xb7872734 in QApplication::x11ProcessEvent () from /usr//lib/libQtGui.so.4
#22 0xb7895ddb in QX11Info::copyX11Data () from /usr//lib/libQtGui.so.4
#23 0xb6f44de2 in g_main_context_dispatch () from /opt/gnome/lib/libglib-2.0.so.0
#24 0xb6f47e1f in g_main_context_prepare () from /opt/gnome/lib/libglib-2.0.so.0
#25 0xb6f48385 in g_main_context_iteration () from /opt/gnome/lib/libglib-2.0.so.0
#26 0xb7487808 in QEventDispatcherGlib::processEvents () from /usr//lib/libQtCore.so.4
#27 0xb7895bc5 in QX11Info::copyX11Data () from /usr//lib/libQtGui.so.4
#28 0xb7465408 in QEventLoop::processEvents () from /usr//lib/libQtCore.so.4
#29 0xb746551c in QEventLoop::exec () from /usr//lib/libQtCore.so.4
#30 0xb74675d8 in QCoreApplication::exec () from /usr//lib/libQtCore.so.4
#31 0xb781d407 in QApplication::exec () from /usr//lib/libQtGui.so.4
#32 0x0806d2a7 in main ()

Original comment by: @cniehaus

[cryos]

Logged In: YES
user_id=1500648
Originator: NO

The segmentation faults wasn't a problem with the textEdit, it was a problem copying molecules. However, for now it doesn't segfault but you can't copy text unless you right click and hit edit->copy. So it works but it's not ideal. It's more of a problem to detect which widget is highlighted and use that for copy/paste. We can work on it. Need some input on this.

Original comment by: @milkypostman

[cryos]

Logged In: YES
user_id=21420
Originator: NO

Re-reading this bug, I think this can be closed. Yes, we need to detect widgets for copy/paste, but that's a separate bug. Certainly the crash issue is finished.

Original comment by: @ghutchis