Bug 454672 – I have no idea what the bug is doing, but whenever I restart the system, or kill the gnome panel and start it up again, the bug reporting tool keeps showing up saying that Bugzilla doesn't know what crashed GNOME and said that I should send the bug to ...

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 454672 - I have no idea what the bug is doing, but whenever I restart the system, or kill the gnome panel and start it up again, the bug reporting tool keeps showing up saying that Bugzilla doesn't know what crashed GNOME and said that I should send the bug to ...


Summary:	I have no idea what the bug is doing, but whenever I restart the system, or k...


Status:	RESOLVED DUPLICATE of bug 363437

Product:	gnome-panel
Classification:	Other
Component:	panel
Version:	2.16.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-07 21:07 UTC by Justin Minaker
Modified:	2007-07-08 08:16 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Justin Minaker 2007-07-07 21:07:21 UTC

Steps to reproduce:
1. Just start the system over again and gnome-panel doesn't work.
2. 
3. 


Stack trace:
Memory status: size: 48857088 vsize: 0 resident: 48857088 share: 0 rss: 10739712 rss_rlim: 0
CPU usage: start_time: 1183841206 rtime: 0 utime: 10 stime: 0 cutime:9 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(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)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208767936 (LWP 3605)]
(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)
(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)
0x004c0402 in __kernel_vsyscall ()

+ Trace 146393

Thread 1 (Thread -1208767936 (LWP 3605))

#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_assert_warning
from /lib/libglib-2.0.so.0
#10 gtk_recent_info_get_short_name
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_recent_info_get_display_name
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_recent_chooser_menu_new
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#14 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#15 g_main_context_check
from /lib/libglib-2.0.so.0
#16 g_main_loop_run
from /lib/libglib-2.0.so.0
#17 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#18 main
#0 __kernel_vsyscall



Other information:
Above is the bug details given by bug buddy. Thank you for your time and consideration. : D

Comment 1 Vincent Untz 2007-07-08 08:16:46 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 363437 ***

Comment 2 Justin Minaker 2009-08-15 18:04:40 UTC

The original summary for this bug was longer than 255 characters, and so it was truncated when Bugzilla was upgraded. The original summary was:

I have no idea what the bug is doing, but whenever I restart the system, or kill the gnome panel and start it up again, the bug reporting tool keeps showing up saying that Bugzilla doesn't know what crashed GNOME and said that I should send the bug to the bug tracker.