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 359416 - crash in Deskbar: unmounting an ipod video...
crash in Deskbar: unmounting an ipod video...
Status: RESOLVED DUPLICATE of bug 359335
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 21:26 UTC by Roel Groeneveld
Modified: 2006-10-14 15:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Roel Groeneveld 2006-10-03 21:26:14 UTC
What were you doing when the application crashed?
unmounting an ipod video (right-click, choose 'Eject')	 


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

Memory status: size: 88915968 vsize: 0 resident: 88915968 share: 0 rss: 36593664 rss_rlim: 0
CPU usage: start_time: 1159909394 rtime: 0 utime: 150 stime: 0 cutime:125 cstime: 0 timeout: 25 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 -1209936208 (LWP 8652)]
[New Thread -1279759456 (LWP 8669)]
[New Thread -1271366752 (LWP 8663)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1209936208 (LWP 8652))

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

Comment 1 Rob Bradford 2006-10-14 15:55:29 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 359335 ***