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 506312 - crash in Rhythmbox Music Player: while listening a song (...
crash in Rhythmbox Music Player: while listening a song (...
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: 2007-12-29 19:57 UTC by marioeric
Modified: 2007-12-31 08:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description marioeric 2007-12-29 19:57:34 UTC 
Version: 0.10.1

What were you doing when the application crashed?
while listening a song (mp3) I decide to close rhythmbox then the crash


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 23:05:33 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 111210496 vsize: 111210496 resident: 47169536 share: 26390528 rss: 47169536 rss_rlim: 4294967295
CPU usage: start_time: 1198956135 rtime: 29515 utime: 27297 stime: 2218 cutime:106 cstime: 53 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 -1209009616 (LWP 1806)]
[New Thread -1287656560 (LWP 10415)]
[New Thread -1233634416 (LWP 3383)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 183481

Thread 2 (Thread -1287656560 (LWP 10415))

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


----------- .xsession-errors (109 sec old) ---------------------
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-12-31 08:08:44 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 ***