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 558862 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
Status: RESOLVED DUPLICATE of bug 523463
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-01 22:59 UTC by dionysius300
Modified: 2008-11-02 00:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description dionysius300 2008-11-01 22:59:19 UTC
Version: 0.11.6

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24.4-hellbent #1 SMP PREEMPT Sun Apr 13 20:00:46 KST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 92770304 vsize: 92770304 resident: 35659776 share: 18939904 rss: 35659776 rss_rlim: 4294967295
CPU usage: start_time: 1225580452 rtime: 66 utime: 60 stime: 6 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6577720 (LWP 3710)]
[New Thread 0xb3679b90 (LWP 3722)]
[New Thread 0xb3fa9b90 (LWP 3721)]
[New Thread 0xb4a66b90 (LWP 3720)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6577720 (LWP 3710))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 IA__g_main_context_check
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2491
  • #8 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2642
  • #9 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2853
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 main
    at main.c line 335
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
Cannot access memory at address 0x7
Cannot access memory at address 0x7
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
compiz.real (animation) - Error: Animation settings mismatch in "Animation Selection" list for Close event.
Cannot access memory at address 0x7
Cannot access memory at address 0x7
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-11-02 00:43: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 523463 ***