GNOME Bugzilla – Bug 115852
gnome-panel crashed
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: critical Version: 2.2.0.1 Synopsis: gnome-panel crashed Bugzilla-Product: gnome-panel Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Did nothing special, uptime on laptop is 4 hrs 7 minutes. Steps to reproduce the problem: 1. Absolutely no idea 2. 3. Actual Results: Segmentation fault Expected Results: Shouldn't happen ;) How often does this happen? A few times, I think I submitted one before but with another traceback.. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread -1084382592 (LWP 1087)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x0074343e in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 38126
Thread 1 (Thread -1084382592 (LWP 1087))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-24 09:32 ------- Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
Appears to be a unique stack trace, according to the simple-dup-finder. Setting version->2.2.x, marking priority->high & severity->critical (it's a crasher), adding GNOMEVER2.2 and bugsquad keywords, and marking as new. Also, it looks like this should be moved to gtk+.
Yeah, that was real bright of me. Moving to gtk+ without reassigning to the right owner... Doing that now. Is this also a duplicate of bug 107007? I believe it is, but again, I'm not totally sure do to the unblock_source not matching g_get_current_time...
*** This bug has been marked as a duplicate of 107007 ***