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 546720 - crash in Rhythmbox Music Player: Ejecting IPOD Classic by...
crash in Rhythmbox Music Player: Ejecting IPOD Classic by...
Status: RESOLVED INCOMPLETE
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-07 05:56 UTC by jwolf
Modified: 2008-08-09 10:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description jwolf 2008-08-07 05:56:22 UTC
Version: 0.11.6

What were you doing when the application crashed?
Ejecting IPOD Classic by right clicking on the Device Name and selecting "Eject" from the menu.


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 560164864 vsize: 560164864 resident: 56020992 share: 22876160 rss: 56020992 rss_rlim: 18446744073709551615
CPU usage: start_time: 1218088218 rtime: 1715 utime: 1363 stime: 352 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fee39a657a0 (LWP 14052)]
[New Thread 0x41e42950 (LWP 14213)]
[New Thread 0x42643950 (LWP 14062)]
(no debugging symbols found)
0x00007fee38cd8edf in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x7fee39a657a0 (LWP 14052))

  • #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 g_object_ref
    from /usr/lib/libgobject-2.0.so.0
  • #6 ??
    from /usr/lib/librhythmbox-core.so.0
  • #7 ??
    from /usr/lib/librhythmbox-core.so.0
  • #8 ??
    from /usr/lib/librhythmbox-core.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #12 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 main
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (52750 sec old) ---------------------
WARN: Skipping sector, waiting for first VOBU...
WARN: Skipping sector, waiting for first VOBU...
WARN: Skipping sector, waiting for first VOBU...
WARN: Skipping sector, waiting for first VOBU...
WARN: Skipping sector, waiting for first VOBU...
WARN: Skipping sector, waiting for first VOBU...
WARN: Skipping sector, waiting for first VOBU...
WARN: Skipping sector, waiting for first VOBU...
WARN: Skipping sector, waiting for first VOBU...
WARN: Skipping sector, waiting for first VOBU...
WARN: Skipping sector, waiting for first VOBU...
WARN: Skipping sector, waiting for first VOBU...
WARN: Skipping sector, waiting for first VOBU...
WARN: Skipping sector, waiting for firs
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Susana 2008-08-09 10:05:45 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!

Please install debugging packages for: rhythmbox, glib, gtk+, libgnome, libgnomeui.