Bug 465860 – crash in Help: Starting the system,and ...

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 465860 - crash in Help: Starting the system,and ...


Summary:	crash in Help: Starting the system,and ...


Status:	RESOLVED DUPLICATE of bug 364790

Product:	yelp
Classification:	Applications
Component:	General
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Yelp maintainers
QA Contact:	Yelp maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-12 04:20 UTC by iamzxt999
Modified:	2007-09-04 16:04 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description iamzxt999 2007-08-12 04:20:45 UTC

Version: 2.16.0

What were you doing when the application crashed?
Starting the system,and I didn't close the application when I closed the system last time. 


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 44441600 vsize: 0 resident: 44441600 share: 0 rss: 11120640 rss_rlim: 0
CPU usage: start_time: 1186891438 rtime: 0 utime: 16 stime: 0 cutime:12 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208355104 (LWP 2955)]
[New Thread -1211802736 (LWP 2970)]
(no debugging symbols found)
0x007a4402 in __kernel_vsyscall ()

+ Trace 154570

Thread 1 (Thread -1208355104 (LWP 2955))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/nosegneg/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/i686/nosegneg/libc.so.6
#6 abort
from /lib/i686/nosegneg/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_cclosure_marshal_VOID__VOID
#10 gnome_ice_init
from /usr/lib/libgnomeui-2.so.0
#11 g_closure_invoke
from /lib/libgobject-2.0.so.0
#12 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#14 g_signal_emit
from /lib/libgobject-2.0.so.0
#15 gnome_client_set_clone_command
from /usr/lib/libgnomeui-2.so.0
#16 _SmcProcessMessage
from /usr/lib/libSM.so.6
#17 IceProcessMessages
from /usr/lib/libICE.so.6
#18 gnome_ice_init
from /usr/lib/libgnomeui-2.so.0
#19 g_io_channel_unix_get_fd
from /lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#21 g_main_context_check
from /lib/libglib-2.0.so.0
#22 g_main_loop_run
from /lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_cclosure_marshal_VOID__VOID
#25 __libc_start_main
from /lib/i686/nosegneg/libc.so.6
#26 g_cclosure_marshal_VOID__VOID
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-09-04 16:04:11 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 ***