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 414449 - crash in Rhythmbox Music Player: Starting up. BTW, rhyth...
crash in Rhythmbox Music Player: Starting up. BTW, rhyth...
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-03-04 03:19 UTC by rogue_ronin
Modified: 2007-03-04 09:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description rogue_ronin 2007-03-04 03:19:46 UTC 
What were you doing when the application crashed?
Starting up.  BTW, rhythmbox has been somewhat insistent about posessing my DAP when it's plugged in.  I have to exit rhythmbox before I can disconnect the DAP.

I've been doing a lot of file copying, and everything gets slow and unstable.


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

Memory status: size: 53272576 vsize: 0 resident: 53272576 share: 0 rss: 6864896 rss_rlim: 0
CPU usage: start_time: 1172978061 rtime: 0 utime: 215 stime: 0 cutime:190 cstime: 0 timeout: 25 it_real_value: 0 frequency: 13

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1228867920 (LWP 4658)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 115634

Thread 1 (Thread -1228867920 (LWP 4658))

  • #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 call_python_method
    at rb-python-plugin.c line 48
  • #20 impl_activate
    at rb-python-plugin.c line 118
  • #21 rb_plugin_activate
    at rb-plugin.c line 153
  • #22 rb_plugins_engine_activate_plugin
    at rb-plugins-engine.c line 489
  • #23 rb_plugins_engine_load_cb
    at rb-plugins-engine.c line 290
  • #24 rb_uri_handle_recursively_cb
    at rb-file-helpers.c line 688
  • #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
    at rb-file-helpers.c line 716
  • #29 rb_plugins_engine_init
    at rb-plugins-engine.c line 299
  • #30 rb_shell_constructor
    at rb-shell.c line 1361
  • #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
    at rb-shell.c line 956
  • #35 main
    at main.c line 305
  • #0 __kernel_vsyscall 






Comment 1


Alex Lancaster





          2007-03-04 09:32:32 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 ***