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 492415 - crash in Dictionary: Looked for the german wo...
crash in Dictionary: Looked for the german wo...
Status: RESOLVED DUPLICATE of bug 465336
Product: gnome-utils
Classification: Deprecated
Component: gdict
2.18.x
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-01 17:16 UTC by leof
Modified: 2007-12-08 09:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description leof 2007-11-01 17:16:36 UTC
Version: 2.18.1

What were you doing when the application crashed?
Looked for the german word 'wissen' after double-clicking the german-english Freedict dictionary


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 282705920 vsize: 282705920 resident: 23629824 share: 18751488 rss: 23629824 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193937298 rtime: 118 utime: 93 stime: 25 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-dictionary'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912513453536 (LWP 13616)]
(no debugging symbols found)
0x0000003544a0d945 in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912513453536 (LWP 13616))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__OBJECT
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strlen
    from /lib64/libc.so.6
  • #4 g_strrstr
    from /lib64/libglib-2.0.so.0
  • #5 g_utf8_strrchr
    from /lib64/libglib-2.0.so.0
  • #6 g_cclosure_marshal_VOID__OBJECT
    from /usr/lib64/libgdict-1.0.so.5
  • #7 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #8 g_cclosure_marshal_VOID__OBJECT
    from /lib64/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #10 g_signal_emit_by_name
    from /lib64/libgobject-2.0.so.0
  • #11 g_cclosure_marshal_VOID__OBJECT
    from /usr/lib64/libgdict-1.0.so.5
  • #12 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #13 g_cclosure_marshal_VOID__OBJECT
    from /lib64/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #16 gdict_main
  • #17 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (23 sec old) ---------------------
xscreensaver: 17:11:47: 0: for window 0x300001f (gnome-terminal / Gnome-terminal)
xscreensaver: 17:11:48: 0: unrecognised ClientMessage "WM_CHANGE_STATE" received
xscreensaver: 17:11:48: 0: for window 0x360007e (gecko / Thunderbird-bin)
xscreensaver: 17:11:49: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 17:11:49: 0: for window 0x360007e (gecko / Thunderbird-bin)
xscreensaver: 17:11:59: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 17:11:59: 0: for window 0x320007e (gecko / Firefox-bin)
(gnome-dictionary:13576): GLib-CRITICAL **: g_strrstr_len: assertion `haystack != NULL' failed
(gnome-dictionary:13576): GLib-CRITICAL **: g_string_append: assertion `val != NULL' failed
(gnome-dictionary:13616): GLib-CRITICAL **: g_strrstr_len: assertion `haystack != NULL' failed
(gnome-dictionary:13616): GLib-CRITICAL **: g_string_append: assertion `val != NULL' failed
--------------------------------------------------
Comment 1 Teppo Turtiainen 2007-12-08 09:02:09 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 465336 ***