Bug 486824 – crash in Panel: launched synaptic

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 486824 - crash in Panel: launched synaptic


Summary:	crash in Panel: launched synaptic


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-15 13:12 UTC by ankou29666
Modified:	2007-10-15 19:07 UTC

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

Description ankou29666 2007-10-15 13:12:33 UTC

Version: 2.20.0.1

What were you doing when the application crashed?
launched synaptic


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

System: Linux 2.6.22.1+ank1 #1 SMP Sat Aug 4 14:59:34 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 355024896 vsize: 355024896 resident: 47304704 share: 8679424 rss: 47304704 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192100744 rtime: 28821 utime: 21855 stime: 6966 cutime:0 cstime: 42 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2aecf4f162e0 (LWP 10579)]
[New Thread 0x40040950 (LWP 14549)]
(no debugging symbols found)
0x00002aeceeb1fc7f in waitpid () from /lib/libpthread.so.0

+ Trace 170328

Thread 1 (Thread 0x2aecf4f162e0 (LWP 10579))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 g_markup_escape_text
from /usr/lib/libglib-2.0.so.0
#6 ??
from /usr/lib/libgtk-x11-2.0.so.0
#7 g_object_set_valist
from /usr/lib/libgobject-2.0.so.0
#8 g_object_set
from /usr/lib/libgobject-2.0.so.0
#9 ??
from /usr/lib/libwnck-1.so.22
#10 ??
from /usr/lib/libwnck-1.so.22
#11 ??
from /usr/lib/libstartup-notification-1.so.0
#12 sn_list_foreach
from /usr/lib/libstartup-notification-1.so.0
#13 ??
from /usr/lib/libstartup-notification-1.so.0
#14 sn_list_foreach
from /usr/lib/libstartup-notification-1.so.0
#15 ??
from /usr/lib/libstartup-notification-1.so.0
#16 ??
from /usr/lib/libstartup-notification-1.so.0
#17 sn_list_foreach
from /usr/lib/libstartup-notification-1.so.0
#18 sn_internal_xmessage_process_event
from /usr/lib/libstartup-notification-1.so.0
#19 sn_display_process_event
from /usr/lib/libstartup-notification-1.so.0
#20 ??
from /usr/lib/libwnck-1.so.22
#21 ??
from /usr/lib/libgdk-x11-2.0.so.0
#22 ??
from /usr/lib/libgdk-x11-2.0.so.0
#23 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#24 ??
from /usr/lib/libgdk-x11-2.0.so.0
#25 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#26 ??
from /usr/lib/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 main
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (1027446 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Vincent Untz 2007-10-15 19:07:59 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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