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 535510 - crash in Rhythmbox Music Player: Listening to music. I'd ...
crash in Rhythmbox Music Player: Listening to music. I'd ...
Status: RESOLVED DUPLICATE of bug 522247
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-29 15:02 UTC by Dafydd Harries
Modified: 2008-07-27 06:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Dafydd Harries 2008-05-29 15:02:54 UTC
Version: 0.11.5

What were you doing when the application crashed?
Listening to music. I'd seen some notifications that Rhythmbox was downloading some podcasts. Music continued to play and UI continued to be responsive after bug buddy launched.


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-1-686 #1 SMP Mon Apr 28 13:54:58 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: gnome

Memory status: size: 272748544 vsize: 272748544 resident: 64860160 share: 23384064 rss: 64860160 rss_rlim: 4294967295
CPU usage: start_time: 1211986738 rtime: 60232 utime: 50169 stime: 10063 cutime:2 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 0xb65bfa80 (LWP 12743)]
[New Thread 0xab0fab90 (LWP 10625)]
[New Thread 0xaeb02b90 (LWP 10613)]
[New Thread 0xad0feb90 (LWP 10577)]
[New Thread 0xac0fcb90 (LWP 10576)]
[New Thread 0xaf303b90 (LWP 10575)]
[New Thread 0xae295b90 (LWP 10259)]
[New Thread 0xad8ffb90 (LWP 10246)]
[New Thread 0xb0305b90 (LWP 10244)]
[New Thread 0xb15feb90 (LWP 10243)]
[New Thread 0xafb04b90 (LWP 10242)]
[New Thread 0xb4f33b90 (LWP 10239)]
[New Thread 0xb1dffb90 (LWP 12757)]
0xb7ee8424 in __kernel_vsyscall ()

Thread 3 (Thread 0xaeb02b90 (LWP 10613))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
    from /usr/lib/libtotem-plparser.so.10
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libtotem-plparser.so.10
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 totem_pl_parser_parse_with_base
    from /usr/lib/libtotem-plparser.so.10


----------- .xsession-errors ---------------------
(rhythmbox:12743): GLib-GObject-WARNING **: IA__g_object_set_valist: object class `TotemPlParser' has no property named `recurse'
warning: .dynamic section for "/usr/lib/libpython2.5.so.1.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libgdk_pixbuf-2.0.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/python2.5/lib-dynload/strop.so" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/python2.5/lib-dynload/time.so" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/python2.5/lib-dynload/binascii.so" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/python2.5/lib-dynload/datetime.so" is not at the expected address (wrong library or version mismatch?)
Cannot access memory at address 0x10
Cannot access memory at address 0x10
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-07-27 06:46:54 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 522247 ***