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 489822 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
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-24 14:44 UTC by tibido
Modified: 2007-10-27 04:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description tibido 2007-10-24 14:44:49 UTC
Version: 0.10.1

What were you doing when the application crashed?



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

System: Linux 2.6.23 #1 SMP Wed Oct 10 23:12:57 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Neu

Memory status: size: 96563200 vsize: 96563200 resident: 35966976 share: 19972096 rss: 35966976 rss_rlim: 4294967295
CPU usage: start_time: 1193235182 rtime: 9718 utime: 9381 stime: 337 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 0xb6c246c0 (LWP 3994)]
[New Thread 0xb5638b90 (LWP 4000)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()


----------- .xsession-errors ---------------------
** Message: GetValue variable 2 (2)
(rhythmbox:3994): Rhythmbox-WARNING **: Unable to stop mDNS browsing: Il servizio MDNS non è in esecuzione
** Message: GetValue variable 1 (1)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-10-27 04:04:57 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 ***