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 490038 - crash in Rhythmbox Music Player: I was closing the app. N...
crash in Rhythmbox Music Player: I was closing the app. N...
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-25 06:42 UTC by cicciobello112003
Modified: 2007-10-27 03:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description cicciobello112003 2007-10-25 06:42:01 UTC 
Version: 0.10.1

What were you doing when the application crashed?
I was closing the app. Nothing seemed to be wrong.


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: gnome

Memory status: size: 81932288 vsize: 81932288 resident: 33566720 share: 17657856 rss: 33566720 rss_rlim: 4294967295
CPU usage: start_time: 1193294428 rtime: 812 utime: 740 stime: 72 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 0xb6b786c0 (LWP 3835)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 172701

Thread 1 (Thread 0xb6b786c0 (LWP 3835))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 ??
  • #5 ??
  • #0 __kernel_vsyscall 






Comment 1


Jonathan Matthew





          2007-10-27 03:32:00 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 ***