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 618636 - crash in Devhelp: I typing in the search a...
crash in Devhelp: I typing in the search a...
Status: RESOLVED DUPLICATE of bug 601048
Product: devhelp
Classification: Applications
Component: General
2.28.x
Other All
: Normal critical
: ---
Assigned To: devhelp-maint
devhelp-maint
Depends on:
Blocks:
 
 
Reported: 2010-05-14 14:43 UTC by Nicolas Dufresne (ndufresne)
Modified: 2010-05-14 16:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Nicolas Dufresne (ndufresne) 2010-05-14 14:43:40 UTC
Version: 2.28.1

What were you doing when the application crashed?
I typing in the search area.


Distribution: Gentoo Base System release 1.12.13
Gnome Release: 2.28.2 2010-05-04 (Gentoo)
BugBuddy Version: 2.28.0

System: Linux 2.6.33-gentoo-r2 #2 SMP Mon May 10 12:10:03 EDT 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10706000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 545804288 vsize: 545804288 resident: 55771136 share: 22425600 rss: 55771136 rss_rlim: 18446744073709551615
CPU usage: start_time: 1273847241 rtime: 1604 utime: 1477 stime: 127 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/devhelp'

Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2400.0-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[Thread debugging using libthread_db enabled]
[New Thread 0x7f6bddd5a910 (LWP 7707)]
0x00007f6be9b0b94f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x7f6bedc85740 (LWP 7703))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at gspawn.c line 386
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 700
  • #3 run_bug_buddy
    at gnome-breakpad.cc line 369
  • #4 check_if_gdb
    at gnome-breakpad.cc line 440
  • #5 bugbuddy_segv_handle
    at gnome-breakpad.cc line 223
  • #6 <signal handler called>
  • #7 queryInfoCallback
    at WebCore/platform/network/soup/ResourceHandleSoup.cpp line 845
  • #8 complete_in_idle_cb_for_thread
    at gsimpleasyncresult.c line 653
  • #9 g_main_dispatch
    at gmain.c line 1960
  • #10 IA__g_main_context_dispatch
    at gmain.c line 2513
  • #11 g_main_context_iterate
    at gmain.c line 2591
  • #12 IA__g_main_loop_run
    at gmain.c line 2799
  • #13 IA__gtk_main
    at gtkmain.c line 1218
  • #14 main
    at dh-main.c line 299

	Inferior 1 [process 7703] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (1309 sec old) ---------------------
(firefox:7590): Gdk-WARNING **: XID collision, trouble ahead
(firefox:7590): Gdk-WARNING **: XID collision, trouble ahead
(firefox:7590): Gdk-WARNING **: XID collision, trouble ahead
(firefox:7590): Gdk-WARNING **: XID collision, trouble ahead
(firefox:7590): Gdk-WARNING **: XID collision, trouble ahead
(firefox:7590): Gdk-WARNING **: XID collision, trouble ahead
(firefox:7590): Gdk-WARNING **: XID collision, trouble ahead
(firefox:7590): Gdk-WARNING **: XID collision, trouble ahead
--------------------------------------------------
Comment 1 Frederic Peters 2010-05-14 14:47:18 UTC
Looks like a duplicate of bug 601048; could you check your webkit version, and update if required?

*** This bug has been marked as a duplicate of bug 601048 ***
Comment 2 Nicolas Dufresne (ndufresne) 2010-05-14 16:20:49 UTC
Sorry for duplicate, Bug Buddy does not seem to allow searching anymore. Webkit version on Gentoo is too low (1.1.15). According to the bug I need >= 1.1.17. This is a bug for Gentoo.

Thanks.