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 482838 - crash in Help:
crash in Help:
Status: RESOLVED DUPLICATE of bug 364790
Product: yelp
Classification: Applications
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Yelp maintainers
Yelp maintainers
: 483405 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-10-03 05:48 UTC by meehan
Modified: 2008-01-10 21:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description meehan 2007-10-03 05:48:28 UTC 
Version: 2.16.0

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2952.fc6 #1 SMP Wed May 16 18:59:18 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 52727808 vsize: 0 resident: 52727808 share: 0 rss: 16736256 rss_rlim: 0
CPU usage: start_time: 1191390376 rtime: 0 utime: 32 stime: 0 cutime:28 cstime: 0 timeout: 4 it_real_value: 0 frequency: 3

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208772352 (LWP 18940)]
[New Thread -1210872944 (LWP 18977)]
0x00221402 in __kernel_vsyscall ()

+ Trace 167318

Thread 1 (Thread -1208772352 (LWP 18940))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 IA__g_logv
    at gmessages.c line 497
  • #8 IA__g_log
    at gmessages.c line 517
  • #9 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 56
  • #10 _gnome_marshal_BOOLEAN__INT_ENUM_BOOLEAN_ENUM_BOOLEAN
    at gnome-marshal.c line 86
  • #11 IA__g_closure_invoke
    at gclosure.c line 490
  • #12 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #13 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #14 IA__g_signal_emit
    at gsignal.c line 2243
  • #15 client_save_yourself_callback
    at gnome-client.c line 755
  • #16 _SmcProcessMessage
    at sm_process.c line 252
  • #17 IceProcessMessages
    at process.c line 344
  • #18 process_ice_messages
    at gnome-ice.c line 57
  • #19 g_io_unix_dispatch
    at giounix.c line 162
  • #20 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #21 g_main_context_iterate
    at gmain.c line 2677
  • #22 IA__g_main_loop_run
    at gmain.c line 2881
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 56
  • #25 __libc_start_main
    from /lib/libc.so.6
  • #26 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 56
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
warning: the debug information found in "/usr/lib/debug//lib/libnss_files-2.5.so.debug" does not match "/lib/libnss_files.so.2" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/gconv/ISO8859-1.so.debug" does not match "/usr/lib/gconv/ISO8859-1.so" (CRC mismatch).
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
Xlib:  extension "DPMS" missing on display "django.cs.wwu.edu:1.0".
warning: the debug information found in "/usr/lib/debug//usr/lib/kde3/plugins/styles/plastik.so.debug" does not match "/usr/lib/kde3/plugins/styles/plastik.so" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/libkdefx.so.4.2.0.debug" does not match "/usr/lib/libkdefx.so.4" (CRC mismatch).
--------------------------------------------------
Comment 1 palfrey 2007-10-05 14:41:42 UTC 
*** Bug 483405 has been marked as a duplicate of this bug. ***
Comment 2 Don Scorgie 2008-01-10 21:57:02 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 364790 ***