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 528072 - crash in Rhythmbox Music Player: Musik gehört, sonst nich...
crash in Rhythmbox Music Player: Musik gehört, sonst nich...
Status: RESOLVED DUPLICATE of bug 465946
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-14 17:11 UTC by vamp898
Modified: 2008-04-17 01:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description vamp898 2008-04-14 17:11:30 UTC 
Version: 0.11.5

What were you doing when the application crashed?
Musik gehört, sonst nicht. Mit Iceweasel nebenher auf Last.fm geschaut warum das plugin meine lieder nicht überträgt


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gm-Looks
Icon Theme: black-white_2-Gloss

Memory status: size: 154529792 vsize: 154529792 resident: 48058368 share: 23298048 rss: 48058368 rss_rlim: 4294967295
CPU usage: start_time: 1208192447 rtime: 2507 utime: 2204 stime: 303 cutime:1 cstime: 1 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 0xb66f49c0 (LWP 5412)]
[New Thread 0xb08ffb90 (LWP 5656)]
[New Thread 0xb2a93b90 (LWP 5655)]
[New Thread 0xb1100b90 (LWP 5617)]
[New Thread 0xb1901b90 (LWP 5424)]
[New Thread 0xb2102b90 (LWP 5423)]
[New Thread 0xb528fb90 (LWP 5421)]
[New Thread 0xb35feb90 (LWP 5420)]
[New Thread 0xb3dffb90 (LWP 5417)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 195215

Thread 3 (Thread 0xb2a93b90 (LWP 5655))

  • #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 xmlEncodeEntitiesReentrant
    from /usr/lib/libxml2.so.2
  • #7 ??
    from /usr/lib/librhythmbox-core.so.0
  • #8 ?? 


----------- .xsession-errors (15 sec old) ---------------------
(rhythmbox:5412): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion `entry != NULL' failed
(rhythmbox:5412): RhythmDB-CRITICAL **: rhythmdb_entry_ref: assertion `entry->refcount > 0' failed
(rhythmbox:5412): RhythmDB-CRITICAL **: rhythmdb_entry_get_double: assertion `entry != NULL' failed
(rhythmbox:5412): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion `entry != NULL' failed
(rhythmbox:5412): RhythmDB-CRITICAL **: rhythmdb_entry_ref: assertion `entry->refcount > 0' failed
(rhythmbox:5412): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed
(rhythmbox:5412): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion `entry != NULL' failed
Xlib: unexpected async reply (sequence 0x22574)!
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-04-17 01:32:40 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 465946 ***