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 404485 - crash in Rhythmbox Music Player: I was just opening rhyth...
crash in Rhythmbox Music Player: I was just opening rhyth...
Status: RESOLVED DUPLICATE of bug 358855
Product: rhythmbox
Classification: Other
Component: general
0.9.7
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-05 02:35 UTC by louis.riopel
Modified: 2007-02-05 03:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description louis.riopel 2007-02-05 02:35:15 UTC
What were you doing when the application crashed?
I was just opening rhythmbox


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 18:50:56 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 387657728 vsize: 387657728 resident: 22331392 share: 14360576 rss: 22331392 rss_rlim: -1
CPU usage: start_time: 1170642846 rtime: 45 utime: 40 stime: 5 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912625919728 (LWP 6725)]
(no debugging symbols found)
0x00002aaaaf16596f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912625919728 (LWP 6725))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 rb_ipod_source_register_type
    from /usr/lib64/rhythmbox/plugins/ipod/libipod.so
  • #4 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #5 g_signal_chain_from_overridden
    from /lib64/libgobject-2.0.so.0
  • #6 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #7 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #8 g_object_class_override_property
    from /lib64/libgobject-2.0.so.0
  • #9 g_object_newv
    from /lib64/libgobject-2.0.so.0
  • #10 g_object_new_valist
    from /lib64/libgobject-2.0.so.0
  • #11 g_object_new
    from /lib64/libgobject-2.0.so.0
  • #12 rb_ipod_source_new
    from /usr/lib64/rhythmbox/plugins/ipod/libipod.so
  • #13 register_rb_plugin
    from /usr/lib64/rhythmbox/plugins/ipod/libipod.so
  • #14 rb_marshal_OBJECT__OBJECT
  • #15 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #16 g_signal_chain_from_overridden
    from /lib64/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #19 rb_removable_media_manager_get_type
  • #20 rb_removable_media_manager_scan
  • #21 rb_shell_new
  • #22 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #23 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #25 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #26 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (7764 sec old) ---------------------
** (gtkpod:28694): WARNING **: iTunesDB and ArtworkDB artwork sizes inconsistent (0+1 != 1933870653)
** (gtkpod:28694): WARNING **: iTunesDB and ArtworkDB artwork sizes inconsistent (0+1 != 1933870653)
** (gtkpod:28694): WARNING **: iTunesDB and ArtworkDB artwork sizes inconsistent (0+1 != 1933870653)
** (gtkpod:28694): WARNING **: iTunesDB and ArtworkDB artwork sizes inconsistent (0+1 != 1933870653)
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Alex Lancaster 2007-02-05 03:38:23 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 358855 ***