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 538092 - crash in Rhythmbox Music Player: pluging an ipod nano 4gb...
crash in Rhythmbox Music Player: pluging an ipod nano 4gb...
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-06-13 03:38 UTC by fabarbuck
Modified: 2008-06-14 19:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description fabarbuck 2008-06-13 03:38:27 UTC
Version: 0.11.5

What were you doing when the application crashed?
pluging an ipod nano 4gb, banshee was running	


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: 52953088 vsize: 52953088 resident: 26918912 share: 16850944 rss: 26918912 rss_rlim: 4294967295
CPU usage: start_time: 1213328213 rtime: 222 utime: 196 stime: 26 cutime:1 cstime: 2 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 0xb66a0a80 (LWP 14933)]
(no debugging symbols found)
0xb7d38f91 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0xb66a0a80 (LWP 14933))

  • #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 (19 sec old) ---------------------
Debug: [6/13/2008 5:34:59 AM] (Enabled multimedia keys support) - Using org.gnome.SettingsDaemon
Setting IO Backend to Banshee.IO.Unix.IOConfig (unix)
Importing timer stopped: 00:00:03.7661820
Debug: [6/13/2008 5:36:49 AM] (Testing device for DAP support) - /org/freedesktop/Hal/devices/storage_serial_Apple_iPod_000A27001B77B815_0_0
Debug: [6/13/2008 5:36:49 AM] (DAP has not been added) - /org/freedesktop/Hal/devices/storage_serial_Apple_iPod_000A27001B77B815_0_0
Debug: [6/13/2008 5:36:53 AM] (Testing device for DAP support) - /org/freedesktop/Hal/devices/volume_uuid_3141_5926
Debug: [6/13/2008 5:36:53 AM] (Waiting for possible DAP to mount) - /org/freedesktop/Hal/devices/volume_uuid_3141_5926
Debug: [6/13/2008 5:36:53 AM] (DAP has not been added) - /org/freedesktop/Hal/devices/volume_uuid_3141_5926
Debug: [6/13/2008 5:36:54 AM] (Possible DAP has mounted) - /org/freedesktop/Hal/devices/volume_uuid_3141_5926
Debug: [6/13/2008 5:36:54 AM] (Testing device for DAP support) - /org/freedesktop/Hal/devices/volume_uuid_3141_5926
Found 0 files in /iPod_Control/Music
Creating fresh track db: /media/usbkey/iPod_Control/iTunes/iTunesDB
Debug: [6/13/2008 5:36:55 AM] (DAP has been added) - Banshee.Dap.Ipod.IpodDap: /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 0x3200061 (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-06-14 19:16:21 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.

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