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 346061 - Bug Report
Bug Report
Status: RESOLVED DUPLICATE of bug 330782
Product: gnome-utils
Classification: Deprecated
Component: gdict
2.14.x
Other other
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
: 346167 350285 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-06-27 22:05 UTC by Kip
Modified: 2006-08-07 15:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Kip 2006-06-27 22:05:19 UTC
From:  <kip@thevertigo.com>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.14.0
Subject: gnome-dictionary crash

Distribution: Debian testing/unstable
Package: gnome-utils
Severity: Normal
Version: GNOME2.14.2 2.14.0
Gnome-Distributor: Debian
Synopsis: gnome-dictionary crash
Bugzilla-Product: gnome-utils
Bugzilla-Component: gdict
Bugzilla-Version: 2.14.0
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Searched for "attrition".

Steps to reproduce the crash:
1. Search for "attrition".

How often does this happen?
Repeatable



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)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 13340)]
(no debugging symbols found)
0xb7422f28 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 13340))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 __pthread_sighandler
    from /lib/libpthread.so.0
  • #4 <signal handler called>
  • #5 kill
    from /lib/libc.so.6
  • #6 pthread_kill
    from /lib/libpthread.so.0
  • #7 raise
    from /lib/libpthread.so.0
  • #8 raise
    from /lib/libc.so.6
  • #9 abort
    from /lib/libc.so.6
  • #10 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #11 g_log
    from /usr/lib/libglib-2.0.so.0
  • #12 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #13 gdict_defbox_clear
    from /usr/lib/libgdict-1.0.so.1
  • #14 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #19 gdict_client_context_get_client
    from /usr/lib/libgdict-1.0.so.1
  • #20 g_io_channel_unix_get_fd
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #24 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gdict_main
  • #26 main
  • #0 waitpid
    from /lib/libpthread.so.0




------- Bug created by bug-buddy at 2006-06-27 22:05 -------


Unknown version 2.14.0 in product gnome-utils.  Setting version to "2.14.x".

Comment 1 Fabio Bonelli 2006-06-28 08:01:51 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 Fabio Bonelli 2006-06-29 08:00:30 UTC
*** Bug 346167 has been marked as a duplicate of this bug. ***
Comment 3 Emmanuele Bassi (:ebassi) 2006-08-07 15:15:32 UTC
*** Bug 350285 has been marked as a duplicate of this bug. ***
Comment 4 Emmanuele Bassi (:ebassi) 2006-08-07 15:16:53 UTC
cannot reproduce with 2.15/HEAD.

seems a lot like a dupe of #330782.

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

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