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 385103 - crash in Rhythmbox Music Player: Je lançais l'application
crash in Rhythmbox Music Player: Je lançais l'application
Status: RESOLVED DUPLICATE of bug 362488
Product: rhythmbox
Classification: Other
Component: general
0.9.6
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-12 16:32 UTC by michel.belleville
Modified: 2006-12-27 15:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description michel.belleville 2006-12-12 16:32:04 UTC 
What were you doing when the application crashed?
Je lançais l'application


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

Memory status: size: 80343040 vsize: 0 resident: 80343040 share: 0 rss: 22495232 rss_rlim: 0
CPU usage: start_time: 1165941097 rtime: 0 utime: 71 stime: 0 cutime:65 cstime: 0 timeout: 6 it_real_value: 0 frequency: 4

Backtrace was generated from '/usr/bin/rhythmbox'

(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 -1229130064 (LWP 6750)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 93581

Thread 1 (Thread -1229130064 (LWP 6750))

  • #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 init_gobject
    from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
  • #5 init_gobject
    from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
  • #6 init_gobject
    from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
  • #7 init_gobject
    from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
  • #8 init_gobject
    from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
  • #9 PyCFunction_Call
    from /usr/lib/libpython2.4.so.1.0
  • #10 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #11 PyEval_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #12 PyClassMethod_New
    from /usr/lib/libpython2.4.so.1.0
  • #13 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #14 PyClass_IsSubclass
    from /usr/lib/libpython2.4.so.1.0
  • #15 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #16 PyObject_CallMethod
    from /usr/lib/libpython2.4.so.1.0
  • #17 rb_python_object_get_type
  • #18 rb_python_object_get_type
  • #19 rb_plugin_activate
  • #20 rb_plugins_engine_activate_plugin
  • #21 rb_plugins_engine_init
  • #22 rb_uri_handle_recursively
  • #23 gnome_vfs_directory_open_from_uri
    from /usr/lib/libgnomevfs-2.so.0
  • #24 gnome_vfs_directory_open_from_uri
    from /usr/lib/libgnomevfs-2.so.0
  • #25 gnome_vfs_directory_visit
    from /usr/lib/libgnomevfs-2.so.0
  • #26 rb_uri_handle_recursively
  • #27 rb_plugins_engine_init
  • #28 rb_shell_new
  • #29 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #32 rb_shell_new
  • #33 main
  • #0 __kernel_vsyscall 






Comment 1


James "Doc" Livingston





          2006-12-12 21:17:54 UTC
        



*** Bug 385193 has been marked as a duplicate of this bug. ***






Comment 2


Alex Lancaster





          2006-12-13 00:05:46 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

This could be a dupe of bug #362488.






Comment 3


Christian Kirbach





          2006-12-27 15:32:34 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 362488 ***