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 407328 - crash in Rhythmbox Music Player: trying to run rhythmbox....
crash in Rhythmbox Music Player: trying to run rhythmbox....
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: 2007-02-13 03:45 UTC by thelusiv
Modified: 2007-02-13 08:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description thelusiv 2007-02-13 03:45:07 UTC 
What were you doing when the application crashed?
trying to run rhythmbox...almost right away it crashes. nothing is printed on the terminal if i run the program from there. it returns to the prompt immediately. before i closed it, a few minutes ago, it was working fine. i can't find any program log or anything that might tell what was happening during the crash.


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

Memory status: size: 50589696 vsize: 0 resident: 50589696 share: 0 rss: 21184512 rss_rlim: 0
CPU usage: start_time: 1171338556 rtime: 0 utime: 79 stime: 0 cutime:72 cstime: 0 timeout: 7 it_real_value: 0 frequency: 3

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

+ Trace 110285

Thread 1 (Thread -1228232512 (LWP 23440))

  • #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_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #12 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #13 PyEval_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #14 PyClassMethod_New
    from /usr/lib/libpython2.4.so.1.0
  • #15 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #16 PyClass_IsSubclass
    from /usr/lib/libpython2.4.so.1.0
  • #17 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #18 PyObject_CallMethod
    from /usr/lib/libpython2.4.so.1.0
  • #19 rb_python_object_get_type
  • #20 rb_python_object_get_type
  • #21 rb_plugin_activate
  • #22 rb_plugins_engine_activate_plugin
  • #23 rb_plugins_engine_init
  • #24 rb_uri_handle_recursively
  • #25 gnome_vfs_directory_open_from_uri
    from /usr/lib/libgnomevfs-2.so.0
  • #26 gnome_vfs_directory_open_from_uri
    from /usr/lib/libgnomevfs-2.so.0
  • #27 gnome_vfs_directory_visit
    from /usr/lib/libgnomevfs-2.so.0
  • #28 rb_uri_handle_recursively
  • #29 rb_plugins_engine_init
  • #30 rb_shell_new
  • #31 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #34 rb_shell_new
  • #35 main
  • #0 __kernel_vsyscall 






Comment 1


Alex Lancaster





          2007-02-13 08:30:11 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 ***