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 489152 - crash in Rhythmbox Music Player: I've closed rhythmbox by...
crash in Rhythmbox Music Player: I've closed rhythmbox by...
Status: RESOLVED DUPLICATE of bug 484988
Product: rhythmbox
Classification: Other
Component: general
0.10.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-22 20:32 UTC by marco
Modified: 2007-10-24 08:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description marco 2007-10-22 20:32:15 UTC
Version: 0.10.1

What were you doing when the application crashed?
I've closed rhythmbox by right-clicking the tray icon


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: tango-noir0-8.0

Memory status: size: 99999744 vsize: 99999744 resident: 40148992 share: 19902464 rss: 40148992 rss_rlim: 4294967295
CPU usage: start_time: 1193080066 rtime: 37181 utime: 35911 stime: 1270 cutime:0 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c3f6c0 (LWP 15420)]
[New Thread 0xb576bb90 (LWP 15425)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()


----------- .xsession-errors (1118 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: Failed to close thumbnail pixbuf loader for /home/marco/Desktop/DSC00184.JPG: Fehler beim Lesen einer JPEG-Bilddatei (Application transferred too few scanlines)
** Message: Failed to close thumbnail pixbuf loader for /home/marco/Desktop/DSC00184.JPG: Fehler beim Lesen einer JPEG-Bilddatei (Application transferred too few scanlines)
** Message: Failed to close thumbnail pixbuf loader for /home/marco/Desktop/DSC00184.JPG: Fehler beim Lesen einer JPEG-Bilddatei (Application transferred too few scanlines)
** Message: drive = 0
** Message: volume = 0
** Message: Failed to close thumbnail pixbuf loader for /home/marco/Desktop/DSC00184.JPG: Fehler beim Lesen einer JPEG-Bilddatei (Application transferred too few scanlines)
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-10-23 12:30:12 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 marco 2007-10-23 14:58:27 UTC
There you go:

Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: tango-noir0-8.0

Memory status: size: 91250688 vsize: 91250688 resident: 35270656 share: 18628608 rss: 35270656 rss_rlim: 4294967295
CPU usage: start_time: 1193151310 rtime: 438 utime: 397 stime: 41 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c2b6c0 (LWP 5149)]
[New Thread 0xb43fdb90 (LWP 5157)]
0xffffe410 in __kernel_vsyscall ()


----------- .xsession-errors (179 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
20070719T142046Z-6276-1000-1-11@mws-marco has recurrences
20070814T190159Z-9021-1000-1-7@mws-marco has recurrences
20070719T140929Z-6276-1000-1-6@mws-marco has recurrences
20070719T141249Z-6276-1000-1-8@mws-marco has recurrences
20070814T190101Z-9021-1000-1-6@mws-marco has recurrences
20070719T141038Z-6276-1000-1-7@mws-marco has recurrences
20070719T140500Z-6276-1000-1-5@mws-marco has recurrences
pas-id-463F829E00000001-birthday has recurrences
pas-id-46364C3200000000-birthday has recurrences
--------------------------------------------------
Comment 3 Jonathan Matthew 2007-10-23 21:26:21 UTC
That still doesn't help, unfortunately.  We'd also need debug symbols for libc6, libglib2.0-0, and possibly libgtk2.0-0.

Alternatively, if you have libsoup version 2.2.101 or newer (current in debian testing and unstable), this is almost certainly a duplicate of bug 484988.
Comment 4 marco 2007-10-24 04:26:44 UTC
Yes, libsoup is installed in version 2.2.101-1.
As I've tried to rebuild the crash (after installing the new debug symbols), it didn't work. I'll try again when I'm back from school (if you need so)
Comment 5 Jonathan Matthew 2007-10-24 08:02:22 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 484988 ***