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 485306 - crash in Rhythmbox Music Player: not a thing - it had jus...
crash in Rhythmbox Music Player: not a thing - it had jus...
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-10 08:39 UTC by Anand Kumria
Modified: 2007-10-17 08:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Anand Kumria 2007-10-10 08:39:24 UTC 
Version: 0.10.1

What were you doing when the application crashed?
not a thing - it had just automagiced itself into existence and died


Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

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: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 63934464 vsize: 63934464 resident: 21544960 share: 10387456 rss: 21544960 rss_rlim: 4294967295
CPU usage: start_time: 1191920299 rtime: 5068 utime: 4892 stime: 176 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 0xb6af0ab0 (LWP 26851)]
[New Thread 0xb67a6b90 (LWP 26864)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 169196

Thread 1 (Thread 0xb6af0ab0 (LWP 26851))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 ??
  • #8 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (179 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-10-13 06:54:51 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 Jonathan Matthew 2007-10-17 08:08:52 UTC 
Actually, this is another duplicate of 484988, but I have to reopen it before I can mark it as such.
Comment 3 Jonathan Matthew 2007-10-17 08:09:13 UTC 

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