Bug 371173 – crash in Deskbar: I think I was changing t...

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 371173 - crash in Deskbar: I think I was changing t...


Summary:	crash in Deskbar: I think I was changing t...


Status:	RESOLVED DUPLICATE of bug 352265

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-11-05 19:14 UTC by hax0r.0v3rl04d
Modified:	2006-11-06 09:12 UTC

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

Description hax0r.0v3rl04d 2006-11-05 19:14:10 UTC

What were you doing when the application crashed?
I think I was changing the theme.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 64417792 vsize: 0 resident: 64417792 share: 0 rss: 31911936 rss_rlim: 0
CPU usage: start_time: 1162671475 rtime: 0 utime: 286 stime: 0 cutime:259 cstime: 0 timeout: 27 it_real_value: 0 frequency: 11

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 -1210149200 (LWP 5324)]
[New Thread -1277486176 (LWP 5471)]
[New Thread -1269093472 (LWP 5469)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 83318

Thread 1 (Thread -1210149200 (LWP 5324))

#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 ??
#5 gdk_x11_drawable_get_xdisplay
from /usr/lib/libgdk-x11-2.0.so.0
#6 gdk_events_pending
from /usr/lib/libgdk-x11-2.0.so.0
#7 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#8 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#9 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#10 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#11 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#12 bonobo_main
from /usr/lib/libbonobo-2.so.0
#13 bonobo_generic_factory_main_timeout
from /usr/lib/libbonobo-2.so.0
#14 bonobo_generic_factory_main
from /usr/lib/libbonobo-2.so.0
#15 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#16 initgnomeapplet
from /usr/lib/python2.4/site-packages/gtk-2.0/gnomeapplet.so
#17 PyEval_EvalFrame
#18 PyEval_EvalCodeEx
#19 PyEval_EvalCode
#20 PyRun_FileExFlags
#21 PyRun_SimpleFileExFlags
#22 Py_Main
#23 main
#0 __kernel_vsyscall

Comment 1 Damien Durand 2006-11-06 04:42:47 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 is duplicated of : http://bugzilla.gnome.org/show_bug.cgi?id=352265

Comment 2 André Klapper 2006-11-06 09:12:41 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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