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 527280 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
Status: RESOLVED DUPLICATE of bug 463948
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-10 04:37 UTC by Víctor Daniel
Modified: 2008-04-12 22:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Víctor Daniel 2008-04-10 04:37:35 UTC 
Version: 0.11.3

What were you doing when the application crashed?



Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.3 2008-01-08 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.15-137.fc8 #1 SMP Sun Feb 10 17:48:34 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Aurora-Midnight
Icon Theme: UbuntuStudio

Memory status: size: 170782720 vsize: 170782720 resident: 47964160 share: 23105536 rss: 47964160 rss_rlim: 4294967295
CPU usage: start_time: 1207801727 rtime: 1253 utime: 1095 stime: 158 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

Using host libthread_db library "/lib/libthread_db.so.1".
Getting all the debuginfos: debuginfo-install rhythmbox
[Thread debugging using libthread_db enabled]
[New Thread -1208162528 (LWP 24490)]
[New Thread -1281487984 (LWP 24530)]
[New Thread -1323447408 (LWP 24517)]
0x00110402 in __kernel_vsyscall ()

+ Trace 194800

Thread 1 (Thread -1208162528 (LWP 24490))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 369
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 677
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 rb_player_playing
    at rb-player.c line 326
  • #10 notify_playing_idle
    at rb-shell-player.c line 608
  • #11 g_idle_dispatch
    at gmain.c line 4132
  • #12 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #13 g_main_context_iterate
    at gmain.c line 2694
  • #14 IA__g_main_loop_run
    at gmain.c line 2898
  • #15 IA__gtk_main
    at gtkmain.c line 1163
  • #16 main
    at main.c line 340
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/80/795e331588df33050e4b5b8f4b21d2af31fb33.debug
Missing separate debuginfo for /usr/lib/libmp4v2.so.0
Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/b0/63c9e20f3a002e9818c6aa6c90007ce37a7067.debug
Missing separate debuginfo for /usr/lib/libmad.so.0
Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/2e/019cb0256552d38c8f4dca65303406701aacfd.debug
Missing separate debuginfo for /usr/lib/libid3tag.so.0
Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/87/1ca83130449b070cf17b02bdfe1517b6f07f62.debug
Missing separate debuginfo for /usr/lib/liboil-0.3.so.0
Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/c2/aead9101ffd98f361bdb878bcb85efd5f3e062.debug
Missing separate debuginfo for /usr/lib/gstreamer-0.10/libgstautodetect.so
Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/9d/33f0e287b969d3489993db141f1abbcd3ff470.debug
Missing separate debuginfo for /usr/lib/libpulse.so.0
Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/ab/ec093ca7d473863359c5a28839d1ca67df9bea.debug
Cannot access memory at address 0x1
Cannot access memory at address 0x1
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-04-12 22:45:22 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 463948 ***