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 349654 - gnome-dict crashed
gnome-dict crashed
Status: RESOLVED DUPLICATE of bug 330782
Product: gnome-utils
Classification: Deprecated
Component: gdict
2.14.x
Other Linux
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-02 10:36 UTC by Jules Colding
Modified: 2006-08-02 11:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Jules Colding 2006-08-02 10:36:10 UTC 
This is from Bug-Buddy:


Distribution: Gentoo Base System version 1.6.15
Package: gnome-utils
Severity: Normal
Version: GNOME2.14.2 2.14.0
Gnome-Distributor: Gentoo
Synopsis: gnome-dictionary crashed
Bugzilla-Product: gnome-utils
Bugzilla-Component: gdict
Bugzilla-Version: 2.14.0
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
I started the dictionary and pasted the word 'grievance' into it. The
dictionary crashed when I pressed 'Enter'.

Steps to reproduce the crash:
1. Start gnome-dictionary
2. Paste 'grievance' into it
3. Press 'Enter'

Expected Results: 
   I should see the result(s)

How often does this happen?
   Every time.

Additional Information:
 The crash does not happen for other words.


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47502217846992 (LWP 14097)]
0x00002b33f6ebaed4 in waitpid () from /lib/libpthread.so.0

+ Trace 69903

Thread 1 (Thread 47502217846992 (LWP 14097))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib/libglib-2.0.so.0
  • #7 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #8 gdict_defbox_clear
    from /usr/lib/libgdict-1.0.so.1
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_has_handler_pending
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #13 gdict_client_context_get_client
    from /usr/lib/libgdict-1.0.so.1
  • #14 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #17 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gdict_main
  • #19 main
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Emmanuele Bassi (:ebassi)





          2006-08-02 10:43:50 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.







Comment 2


Jules Colding





          2006-08-02 11:00:27 UTC
        



Sure, here you go:

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47048646455504 (LWP 3901)]
0x00002aca5bf57ed4 in waitpid () from /lib/libpthread.so.0




+
Trace
    69904






Thread 1
          (Thread 47048646455504 (LWP 3901))


    

  • 
#0
waitpid

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#1
libgnomeui_module_info_get

    
                from
                /usr/lib/libgnomeui-2.so.0

    

    • 

  • 
#2
<signal handler called>

    • 

  • 
#3
raise

    
                from
                /lib/libc.so.6

    

    • 

  • 
#4
abort

    
                from
                /lib/libc.so.6

    

    • 

  • 
#5
g_logv

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#6
g_log

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#7
g_assert_warning

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#8
lookup_start_cb

    
                at gdict-defbox.c
                  line
                  1113

    

    • 

  • 
#9
g_closure_invoke

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#10
g_signal_has_handler_pending

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#11
g_signal_emit_valist

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#12
g_signal_emit_by_name

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#13
gdict_client_context_parse_line

    
                at gdict-client-context.c
                  line
                  1474

    

    • 

  • 
#14
gdict_client_context_io_watch_cb

    
                at gdict-client-context.c
                  line
                  1752

    

    • 

  • 
#15
g_main_context_dispatch

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#16
g_main_context_acquire

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#17
g_main_loop_run

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#18
gtk_main

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#19
gdict_main

    
                at gdict-app.c
                  line
                  548

    

    • 

  • 
#20
main

    
                at main.c
                  line
                  19

    

    • 

  • 
#0
waitpid

    
                from
                /lib/libpthread.so.0

    

    • 













Comment 3


Emmanuele Bassi (:ebassi)





          2006-08-02 11:19:21 UTC
        



This is a duplicate of bug #330782 which has already been fixed in HEAD and 2.15.0, so it'll be in the next stable release.

Thanks for the bug report.

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