Bug 453100 – crash in Help: Powered up the PC on a M...

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 453100 - crash in Help: Powered up the PC on a M...


Summary:	crash in Help: Powered up the PC on a M...


Status:	RESOLVED DUPLICATE of bug 371007

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-07-02 13:38 UTC by smauget
Modified:	2007-07-02 20:59 UTC

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

Description smauget 2007-07-02 13:38:27 UTC

Version: 2.16.0

What were you doing when the application crashed?
Powered up the PC on a Monday morning and this Bug reporting pop-up appeared (?)


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

System: Linux 2.6.18-1.2849.fc6PAE #1 SMP Fri Nov 10 13:27:10 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
----------- .xsession-errors ---------------------
** (bug-buddy:2894): WARNING **: Couldn't load icon for Screensaver
** (bug-buddy:2894): WARNING **: Couldn't load icon for System Monitor
** (bug-buddy:2894): WARNING **: Couldn't load icon for Trash
** (bug-buddy:2894): WARNING **: Couldn't load icon for Disk Mounter
** (bug-buddy:2894): WARNING **: Couldn't load icon for System Monitor
** (bug-buddy:2894): WARNING **: Couldn't load icon for Battery Charge Monitor
** (bug-buddy:2894): WARNING **: Couldn't load icon for Volume Control
** (bug-buddy:2894): WARNING **: Couldn't load icon for Weather Report
--------------------------------------------------

Memory status: size: 62152704 vsize: 0 resident: 62152704 share: 0 rss: 14835712 rss_rlim: 0
CPU usage: start_time: 1183383271 rtime: 0 utime: 35 stime: 0 cutime:28 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208957216 (LWP 2881)]
[New Thread -1211057264 (LWP 2890)]
(no debugging symbols found)
0x00dd5410 in __kernel_vsyscall ()

+ Trace 145248

Thread 1 (Thread -1208957216 (LWP 2881))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/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/libc.so.6
#6 abort
from /lib/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/libc.so.6
#26 g_cclosure_marshal_VOID__VOID
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2007-07-02 20:59:55 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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