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 542457 - crash in Rhythmbox Music Player: plugging an ipod nano 4g...
crash in Rhythmbox Music Player: plugging an ipod nano 4g...
Status: RESOLVED DUPLICATE of bug 524985
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-07-10 23:01 UTC by fabarbuck
Modified: 2008-07-10 23:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description fabarbuck 2008-07-10 23:01:58 UTC 
Version: 0.11.5

What were you doing when the application crashed?
plugging an ipod nano 4gb (which seemed before that to be frozen due to an unplug while still mounted)


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.17 #1 Thu Jun 28 13:34:08 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 62029824 vsize: 62029824 resident: 27197440 share: 16916480 rss: 27197440 rss_rlim: 4294967295
CPU usage: start_time: 1215713915 rtime: 221 utime: 206 stime: 15 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb65d9740 (LWP 4320)]
(no debugging symbols found)
0xb7ccdf91 in waitpid () from /lib/libpthread.so.0

+ Trace 202517

Thread 1 (Thread 0xb65d9740 (LWP 4320))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 rb_ipod_db_set_ipod_name
    from /usr/lib/rhythmbox/plugins/ipod/libipod.so
  • #6 ??
    from /usr/lib/rhythmbox/plugins/ipod/libipod.so
  • #7 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
  at System.IO.FileStream.ReadInternal (System.Byte[] dest, Int32 dest_offset, Int32 count) [0x00000] 
  at System.IO.FileStream.Read (System.Byte[] dest, Int32 dest_offset, Int32 count) [0x00000] 
  at System.IO.BinaryReader.ReadBytes (Int32 count) [0x00000] 
  at IPod.TrackRecord.Read (IPod.DatabaseRecord db, System.IO.BinaryReader reader) [0x00000] 
  at IPod.TrackListRecord.Read (IPod.DatabaseRecord db, System.IO.BinaryReader reader) [0x00000] 
  at IPod.DataSetRecord.Read (IPod.DatabaseRecord db, System.IO.BinaryReader reader) [0x00000] 
  at IPod.DatabaseRecord.Read (IPod.DatabaseRecord db, System.IO.BinaryReader reader) [0x00000] 
  at IPod.TrackDatabase.Reload (Boolean createFresh) [0x00000] 
  at IPod.TrackDatabase..ctor (IPod.Device device, Boolean createFresh) [0x00000] 
  at IPod.Device.LoadTrackDatabase (Boolean createFresh) [0x00000] 
  at IPod.Device.LoadTrackDatabase () [0x00000] 
  at Banshee.Dap.Ipod.IpodDap.LoadIpod () [0x00000] 
Debug: [7/10/2008 8:18:35 PM] (DAP has not been added) - /org/freedesktop/Hal/devices/volume_uuid_3141_5926
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2000061 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Christophe Fergeau 2008-07-10 23:16:46 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 524985 ***