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 512357 - crash in Rhythmbox Music Player: simply get exit from it....
crash in Rhythmbox Music Player: simply get exit from it....
Status: RESOLVED DUPLICATE of bug 465946
Product: rhythmbox
Classification: Other
Component: general
0.10.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-27 12:59 UTC by kahovski
Modified: 2008-01-27 23:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description kahovski 2008-01-27 12:59:47 UTC 
Version: 0.10.1

What were you doing when the application crashed?
simply get exit from it. But before I've tried to set one of my sound card (I have two) be default. Unfortunatelly, no one player doesn't want to play sound now - and rythmbox too.	


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 652046336 vsize: 652046336 resident: 50454528 share: 24428544 rss: 50454528 rss_rlim: 18446744073709551615
CPU usage: start_time: 1201438517 rtime: 620 utime: 550 stime: 70 cutime:0 cstime: 4 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 0x2b2411d63d90 (LWP 6627)]
[New Thread 0x41802950 (LWP 6928)]
(no debugging symbols found)
0x00002b24078a9b99 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/libpthread.so.0

+ Trace 186950

Thread 2 (Thread 0x41802950 (LWP 6928))

  • #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 xmlEncodeEntitiesReentrant
    from /usr/lib/libxml2.so.2
  • #6 ??
  • #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 g_hash_table_foreach
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 g_hash_table_foreach
    from /usr/lib/libglib-2.0.so.0
  • #14 rhythmdb_entry_type_foreach
  • #15 ??
  • #16 ??
  • #17 ??
    from /usr/lib/libglib-2.0.so.0
  • #18 start_thread
    from /lib/libpthread.so.0
  • #19 clone
    from /lib/libc.so.6
  • #20 ?? 


----------- .xsession-errors (21 sec old) ---------------------
(rhythmbox:6627): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(rhythmbox:6627): RhythmDB-CRITICAL **: rhythmdb_entry_ref: assertion `entry->refcount > 0' failed
(rhythmbox:6627): RhythmDB-CRITICAL **: rhythmdb_entry_get_double: assertion `entry != NULL' failed
(rhythmbox:6627): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion `entry != NULL' failed
(rhythmbox:6627): RhythmDB-CRITICAL **: rhythmdb_entry_ref: assertion `entry->refcount > 0' failed
(rhythmbox:6627): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed
(rhythmbox:6627): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion `entry != NULL' failed
(rhythmbox:6627): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion `entry->refcount > 0' failed
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-01-27 23:50:17 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 ***