Bug 353575 – crash in Deskbar: nothing -- it was starti...

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 353575 - crash in Deskbar: nothing -- it was starti...


Summary:	crash in Deskbar: nothing -- it was starti...


Status:	RESOLVED DUPLICATE of bug 353548

Product:	deskbar-applet
Classification:	Deprecated
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Deskbar Applet Maintainer(s)
QA Contact:	Deskbar Applet Maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-08-30 17:34 UTC by vladanian
Modified:	2006-08-30 18:08 UTC

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

Description vladanian 2006-08-30 17:34:39 UTC

What were you doing when the application crashed?
nothing -- it was starting up after login


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
BugBuddy Version: 2.15.92

Memory status: size: 65056768 vsize: 0 resident: 65056768 share: 0 rss: 32935936 rss_rlim: 0
CPU usage: start_time: 1156959155 rtime: 0 utime: 248 stime: 0 cutime:222 cstime: 0 timeout: 26 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/libexec/deskbar-applet'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209907536 (LWP 5095)]
[New Thread -1252226144 (LWP 5176)]
[New Thread -1243833440 (LWP 5160)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71267

Thread 1 (Thread -1209907536 (LWP 5095))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 dbus_connection_has_messages_to_send
from /usr/lib/libdbus-1.so.3
#5 dbus_pending_call_unref
from /usr/lib/libdbus-1.so.3
#6 dbus_connection_get_unix_fd
from /usr/lib/libdbus-1.so.3
#7 dbus_connection_get_unix_fd
from /usr/lib/libdbus-1.so.3
#8 dbus_connection_flush
from /usr/lib/libdbus-1.so.3
#9 dbus_connection_flush
from /usr/lib/libdbus-1.so.3
#10 dbus_pending_call_block
from /usr/lib/libdbus-1.so.3
#11 ??
from /usr/lib/python2.4/site-packages/dbus/dbus_bindings.so
#12 ??
#13 ??
#0 __kernel_vsyscall

Comment 1 Mikkel Kamstrup Erlandsen 2006-08-30 18:08:24 UTC

It appears you are not alone on this one...

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