After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 696401 - Segfault in GTK+ crashes gnome-dictionary
Segfault in GTK+ crashes gnome-dictionary
Status: RESOLVED DUPLICATE of bug 695304
Product: gtk+
Classification: Platform
Component: Widget: Other
3.7.x
Other Linux
: Normal critical
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-03-22 16:13 UTC by Hashem Nasarat
Modified: 2013-03-22 16:41 UTC
See Also:
GNOME target: ---
GNOME version: 3.7/3.8


Description Hashem Nasarat 2013-03-22 16:13:00 UTC 
I was using the 3.7.92 iso from GNOME. 
Steps to trigger:
Make sure Internet access is enabled.
Open gnome-dictionary
search for a term
scroll in the window
observe how the app crashes/disappears

(I wasn't sure if this should go in gnome-dictionary)


[liveuser@localhost ~]$ gdb gnome-dictionary
GNU gdb (GDB) Fedora (7.5.50.20130310-13.fc19)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/gnome-dictionary...Reading symbols from
/usr/bin/gnome-dictionary...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install
gnome-dictionary-3.6.0-2.fc19.i686
(gdb) r
Starting program: /usr/bin/gnome-dictionary
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[New Thread 0xb4f20b40 (LWP 1465)]
[New Thread 0xb4469b40 (LWP 1466)]

** (gnome-dictionary:1461): WARNING **: Unable to load the window state
file: No such file or directory

(gnome-dictionary:1461): Gtk-CRITICAL **: gtk_device_grab_add: assertion
`GDK_IS_DEVICE (device)' failed
[New Thread 0xb3aabb40 (LWP 1467)]

Program received signal SIGSEGV, Segmentation fault.
0xb7aba6fb in _gtk_bubble_window_popdown () from /lib/libgtk-3.so.0
(gdb) bt

+ Trace 231675

  • #0 _gtk_bubble_window_popdown
    from /lib/libgtk-3.so.0
  • #1 text_window_scroll.isra.11
    from /lib/libgtk-3.so.0
  • #2 gtk_text_view_value_changed
    from /lib/libgtk-3.so.0
  • #3 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #4 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #5 signal_emit_unlocked_R
    from /lib/libgobject-2.0.so.0
  • #6 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #7 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #8 gtk_adjustment_value_changed
    from /lib/libgtk-3.so.0
  • #9 gtk_adjustment_set_value
    from /lib/libgtk-3.so.0
  • #10 gtk_scrolled_window_scroll_event
    from /lib/libgtk-3.so.0
  • #11 _gtk_marshal_BOOLEAN__BOXEDv
    from /lib/libgtk-3.so.0
  • #12 g_type_class_meta_marshalv
    from /lib/libgobject-2.0.so.0
  • #13 _g_closure_invoke_va
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #16 gtk_widget_event_internal
    from /lib/libgtk-3.so.0
  • #17 propagate_event
    from /lib/libgtk-3.so.0
  • #18 gtk_main_do_event
    from /lib/libgtk-3.so.0
  • #19 _gdk_event_emit
    from /lib/libgdk-3.so.0
  • #20 gdk_event_source_dispatch
    from /lib/libgdk-3.so.0
  • #21 g_main_context_dispatch
    from /lib/libglib-2.0.so.0 






Comment 1


Emmanuele Bassi (:ebassi)





          2013-03-22 16:41:05 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 695304 ***