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 541925 - crash in Rhythmbox Music Player: charging my ipd
crash in Rhythmbox Music Player: charging my ipd
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-07 18:30 UTC by baumnath
Modified: 2008-07-21 06:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description baumnath 2008-07-07 18:30:28 UTC
Version: 0.11.5

What were you doing when the application crashed?
charging my ipd


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

System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 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: 70578176 vsize: 70578176 resident: 33476608 share: 17489920 rss: 33476608 rss_rlim: 4294967295
CPU usage: start_time: 1215455411 rtime: 111 utime: 93 stime: 18 cutime:0 cstime: 3 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 0xb65eb740 (LWP 4486)]
(no debugging symbols found)
0xb7cdff91 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0xb65eb740 (LWP 4486))

  • #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 (16 sec old) ---------------------
Debug: [7/7/2008 2:30:09 PM] (DAP has not been added) - /org/freedesktop/Hal/devices/storage_serial_Apple_iPod_000A27001314B3C2_0_0
Debug: [7/7/2008 2:30:11 PM] (Testing device for DAP support) - /org/freedesktop/Hal/devices/volume_uuid_3141_5926
Debug: [7/7/2008 2:30:11 PM] (Waiting for possible DAP to mount) - /org/freedesktop/Hal/devices/volume_uuid_3141_5926
Debug: [7/7/2008 2:30:11 PM] (DAP has not been added) - /org/freedesktop/Hal/devices/volume_uuid_3141_5926
Debug: [7/7/2008 2:30:11 PM] (Possible DAP has mounted) - /org/freedesktop/Hal/devices/volume_uuid_3141_5926
Debug: [7/7/2008 2:30:11 PM] (Testing device for DAP support) - /org/freedesktop/Hal/devices/volume_uuid_3141_5926
System.Exception: org.freedesktop.Hal.NoSuchProperty: No property org.podsleuth.ipod.serial_number on device with id /org/freedesktop/Hal/devices/volume_uuid_3141_5926
  at IDeviceProxy.GetPropertyString (System.String ) [0x00000] 
  at Hal.Device.GetPropertyString (System.String key) [0x00000] 
  at IPod.HalClient.HalDevice+HalProductionInfo..ctor (Hal.Volume volume) [0x00000] 
  at IPod.HalClient.HalDevice..ctor (Hal.Volume volume) [0x00000] 
  at Banshee.Dap.Ipod.IpodDap.LoadIpod () [0x00000] 
Debug: [7/7/2008 2:30:11 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 0x2a00022 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Susana 2008-07-13 21:53:57 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Susana 2008-07-21 06:26:16 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 ***