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 508650 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
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-11 01:08 UTC by beppich
Modified: 2008-01-11 07:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description beppich 2008-01-11 01:08:40 UTC
Version: 0.10.1

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 20:39:56 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 759996416 vsize: 759996416 resident: 234864640 share: 25088000 rss: 234864640 rss_rlim: 18446744073709551615
CPU usage: start_time: 1200013445 rtime: 1758 utime: 1579 stime: 179 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912503172768 (LWP 25486)]
[New Thread 1178638672 (LWP 12320)]
[New Thread 1115699536 (LWP 28260)]
(no debugging symbols found)
0x000000347460c808 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

Thread 2 (Thread 1178638672 (LWP 12320))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 g_hash_table_foreach
    from /lib64/libglib-2.0.so.0
  • #5 g_hash_table_foreach
    from /lib64/libglib-2.0.so.0
  • #6 g_hash_table_foreach
    from /lib64/libglib-2.0.so.0
  • #7 g_hash_table_foreach
    from /lib64/libglib-2.0.so.0
  • #8 ??
  • #9 ??
  • #10 g_hash_table_foreach
    from /lib64/libglib-2.0.so.0
  • #11 rhythmdb_entry_type_foreach
  • #12 ??
  • #13 ??
  • #14 ??
    from /lib64/libglib-2.0.so.0
  • #15 start_thread
    from /lib64/libpthread.so.0
  • #16 clone
    from /lib64/libc.so.6


----------- .xsession-errors (672289 sec old) ---------------------
[mpeg4 @ 0xf5e8f054]marker does not match f_code
[mpeg4 @ 0xf5e8f054]marker does not match f_code
[mpeg4 @ 0xf5e8f054]marker does not match f_code
[mpeg4 @ 0xf5e8f054]marker does not match f_code
[mpeg4 @ 0xf5e8f054]marker does not match f_code
[mpeg4 @ 0xf5e8f054]marker does not match f_code
[mpeg4 @ 0xf5e8f054]marker does not match f_code
[mpeg4 @ 0xf5e8f054]marker does not match f_code
[mpeg4 @ 0xf5e8f054]marker does not match f_code
[mpeg4 @ 0xf5e8f054]marker does not match f_code
[mpeg4 @ 0xf5e8f054]marker does not match f_code
[mpeg4 @ 0xf5e8f054]marker does not match f_code
[mpeg4 @ 0xf5e8f054]marker does not match f_code
[mpeg4 @ 0xf5e8f054]marker does not match f_co
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-01-11 07:50:09 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 ***