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 359386 - crash in Deskbar: Trying to launch either ...
crash in Deskbar: Trying to launch either ...
Status: RESOLVED DUPLICATE of bug 359371
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-10-03 20:05 UTC by Everett Guerny
Modified: 2006-10-03 20:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Everett Guerny 2006-10-03 20:05:13 UTC 
What were you doing when the application crashed?
Trying to launch either gaim or rhythmbox. Neither time did I get past the second letter. 

It had worked flawlessly for days until there was just some funkiness with the gnome panel on which it lives, causing me to try restarting gdm and logging back in. But the panel would fail to load upon login (and, I seem to remember, give me an error I can't quite recall at the moment, sorry), which had me fully rebooting my computer. It never cause a proper crash, though, w/ bug reporting, etc.

I guess I'll try clearing out ~/.gnome2/deskbar


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

Memory status: size: 56676352 vsize: 0 resident: 56676352 share: 0 rss: 33263616 rss_rlim: 0
CPU usage: start_time: 1159905627 rtime: 0 utime: 240 stime: 0 cutime:218 cstime: 0 timeout: 22 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 -1210165584 (LWP 5042)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 74335

Thread 1 (Thread -1210165584 (LWP 5042))

  • #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 PyObject_Malloc
  • #5 init_gobject
    from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
  • #6 init_gtk
    from /var/lib/python-support/python2.4/gtk-2.0/gtk/_gtk.so
  • #7 PyEval_EvalFrame
  • #8 PyEval_EvalCodeEx
  • #9 PyClassMethod_New
  • #10 PyObject_Call
  • #11 PyClass_IsSubclass
  • #12 PyObject_Call
  • #13 PyEval_CallObjectWithKeywords
  • #14 PyInstance_New
  • #15 PyObject_Call
  • #16 PyEval_EvalFrame
  • #17 PyEval_EvalCodeEx
  • #18 PyClassMethod_New
  • #19 PyObject_Call
  • #20 PyClass_IsSubclass
  • #21 PyObject_Call
  • #22 PyType_GenericAlloc
  • #23 PyObject_GetIter
  • #24 PyEval_EvalFrame
  • #25 PyEval_EvalCodeEx
  • #26 PyEval_EvalFrame
  • #27 PyEval_EvalCodeEx
  • #28 PyClassMethod_New
  • #29 PyObject_Call
  • #30 PyClass_IsSubclass
  • #31 PyObject_Call
  • #32 PyEval_CallObjectWithKeywords
  • #33 PyObject_CallObject
  • #34 init_gobject
    from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
  • #35 g_source_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #36 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #37 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #38 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #39 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #40 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #41 bonobo_generic_factory_main
    from /usr/lib/libbonobo-2.so.0
  • #42 panel_applet_factory_main_closure
    from /usr/lib/libpanel-applet-2.so.0
  • #43 initgnomeapplet
    from /usr/lib/python2.4/site-packages/gtk-2.0/gnomeapplet.so
  • #44 PyEval_EvalFrame
  • #45 PyEval_EvalCodeEx
  • #46 PyEval_EvalCode
  • #47 PyRun_FileExFlags
  • #48 PyRun_SimpleFileExFlags
  • #49 Py_Main
  • #50 main
  • #0 __kernel_vsyscall 






Comment 1


Elijah Newren





          2006-10-03 20:16:25 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 359371 ***