*** This bug is a duplicate of bug 90769 ***
    https://bugs.launchpad.net/bugs/90769

Confirmed,

And you can reproduce it just by hitting "CTRL-C" with the cursor in the
history pane.

Here is my stack trace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1230989088 (LWP 22566)]
0xf590840f in ?? ()
(gdb) bt
#0  0xf590840f in ?? ()
#1  0xb7b1a6bf in _gtk_marshal_BOOLEAN__BOXED ()
   from /usr/lib/libgtk-x11-2.0.so.0
#2  0xb734362b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#3  0xb7354103 in ?? () from /usr/lib/libgobject-2.0.so.0
#4  0x081febc0 in ?? ()
#5  0xbf9e13b0 in ?? ()
#6  0x00000002 in ?? ()
#7  0xbf9e148c in ?? ()
#8  0xbf9e139c in ?? ()
#9  0xb6ee7bf0 in pthread_mutex_unlock ()
   from /lib/tls/i686/cmov/libpthread.so.0
#10 0xb73553ef in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#11 0xb73557e9 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#12 0xb7c2ee18 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#13 0x08193000 in ?? ()
#14 0x00000033 in ?? ()
#15 0x00000000 in ?? ()

-- 
[apport] qalculate-gtk crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
https://bugs.launchpad.net/bugs/99504
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to