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 526129 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
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-04 11:39 UTC by stefan.vatev
Modified: 2008-04-05 21:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description stefan.vatev 2008-04-04 11:39:13 UTC 
Version: 0.11.5

What were you doing when the application crashed?



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

System: Linux 2.6.18-5-amd64 #1 SMP Thu Aug 30 01:14:54 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gorilla
Icon Theme: Gorilla

Memory status: size: 824524800 vsize: 824524800 resident: 183492608 share: 25047040 rss: 183492608 rss_rlim: 18446744073709551615
CPU usage: start_time: 1207297476 rtime: 21831 utime: 20254 stime: 1577 cutime:21 cstime: 8 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b6b3d6d9460 (LWP 15653)]
[New Thread 0x44007950 (LWP 23505)]
[New Thread 0x42003950 (LWP 23488)]
[New Thread 0x41001950 (LWP 23484)]
[New Thread 0x40800950 (LWP 23483)]
[New Thread 0x43005950 (LWP 23482)]
[New Thread 0x41802950 (LWP 23481)]
[New Thread 0x42804950 (LWP 15665)]
(no debugging symbols found)
0x00002b6b37359ab6 in poll () from /lib/libc.so.6

+ Trace 194186

Thread 2 (Thread 0x44007950 (LWP 23505))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
    from /usr/lib/librhythmbox-core.so.0
  • #6 g_hash_table_foreach
    from /usr/lib/libglib-2.0.so.0
  • #7 g_hash_table_foreach
    from /usr/lib/libglib-2.0.so.0
  • #8 g_hash_table_foreach
    from /usr/lib/libglib-2.0.so.0
  • #9 g_hash_table_foreach
    from /usr/lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/librhythmbox-core.so.0
  • #11 ??
    from /usr/lib/librhythmbox-core.so.0
  • #12 g_hash_table_foreach
    from /usr/lib/libglib-2.0.so.0
  • #13 rhythmdb_entry_type_foreach
    from /usr/lib/librhythmbox-core.so.0
  • #14 ??
    from /usr/lib/librhythmbox-core.so.0
  • #15 ??
    from /usr/lib/librhythmbox-core.so.0
  • #16 ??
    from /usr/lib/libglib-2.0.so.0
  • #17 start_thread
    from /lib/libpthread.so.0
  • #18 clone
    from /lib/libc.so.6
  • #19 ?? 


----------- .xsession-errors (33 sec old) ---------------------
(rhythmbox:15653): RhythmDB-CRITICAL **: rhythmdb_entry_ref: assertion `entry->refcount > 0' failed
(rhythmbox:15653): RhythmDB-CRITICAL **: rhythmdb_entry_ref: assertion `entry->refcount > 0' failed
(rhythmbox:15653): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed
(rhythmbox:15653): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion `entry != NULL' failed
(rhythmbox:15653): RhythmDB-CRITICAL **: rhythmdb_entry_ref: assertion `entry->refcount > 0' failed
(rhythmbox:15653): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed
(rhythmbox:15653): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion `entry != NULL' failed
Xlib: unexpected async reply (sequence 0x760e0)!
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-04-05 21:12:35 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 ***