Bug 488613 – crash in Panel:

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 488613 - crash in Panel:


Summary:	crash in Panel:


Status:	RESOLVED DUPLICATE of bug 476299

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-20 13:46 UTC by jeanjacques.goessens
Modified:	2007-10-28 15:10 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description jeanjacques.goessens 2007-10-20 13:46:36 UTC

Version: 2.20.0.1

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-2-486 #1 Thu Aug 30 23:45:36 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 32272384 vsize: 32272384 resident: 18006016 share: 12546048 rss: 18006016 rss_rlim: 4294967295
CPU usage: start_time: 1192887965 rtime: 175 utime: 149 stime: 26 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6f346b0 (LWP 9169)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 171694

Thread 1 (Thread 0xb6f346b0 (LWP 9169))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 g_markup_escape_text
from /usr/lib/libglib-2.0.so.0
#7 ??
from /usr/lib/libgtk-x11-2.0.so.0
#8 ??
#9 ??
#10 ??
#11 g_value_transform
from /usr/lib/libgobject-2.0.so.0
#12 g_object_set_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_object_set
from /usr/lib/libgobject-2.0.so.0
#14 gtk_widget_set_tooltip_text
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libwnck-1.so.22
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
from /usr/lib/libwnck-1.so.22
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
from /usr/lib/libwnck-1.so.22
#28 ??
#29 ??
#30 ??
#31 ??
from /usr/lib/libwnck-1.so.22
#32 ??
#33 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-10-28 15:10:09 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 476299 ***