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 534092 - crash in Rhythmbox Music Player: Update podcast feeds.
crash in Rhythmbox Music Player: Update podcast feeds.
Status: RESOLVED DUPLICATE of bug 525954
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-20 19:10 UTC by jeffrey
Modified: 2008-05-25 16:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description jeffrey 2008-05-20 19:10:36 UTC
Version: 0.11.5

What were you doing when the application crashed?
Update podcast feeds.


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

System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 86900736 vsize: 86900736 resident: 32440320 share: 18128896 rss: 32440320 rss_rlim: 4294967295
CPU usage: start_time: 1211310563 rtime: 180 utime: 156 stime: 24 cutime:1 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 "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb653a740 (LWP 4714)]
[New Thread 0xb3cffb90 (LWP 4731)]
[New Thread 0xb4606b90 (LWP 4730)]
[New Thread 0xb4ed6b90 (LWP 4720)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread 0xb3cffb90 (LWP 4731))

  • #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 __kernel_vsyscall
  • #7 raise
    from /lib/i686/cmov/libc.so.6
  • #8 abort
    from /lib/i686/cmov/libc.so.6
  • #9 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #10 g_log
    from /usr/lib/libglib-2.0.so.0
  • #11 g_type_class_ref
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #15 totem_pl_parser_new
    from /usr/lib/libtotem-plparser.so.10
  • #16 rb_podcast_parse_load_feed
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
    from /usr/lib/libgthread-2.0.so.0
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
    from /usr/lib/libglib-2.0.so.0
  • #26 ??
  • #27 ??
    from /lib/i686/cmov/libpthread.so.0
  • #28 ??
  • #29 ??
    from /usr/lib/libglib-2.0.so.0
  • #30 ??
  • #31 ??
  • #32 ??
    from /lib/i686/cmov/libc.so.6
  • #33 ??
    from /lib/i686/cmov/libc.so.6
  • #34 ??
    from /lib/i686/cmov/libc.so.6
  • #35 ??
  • #36 ??
    from /lib/i686/cmov/libpthread.so.0
  • #37 ??
    from /lib/i686/cmov/libpthread.so.0
  • #38 ??


----------- .xsession-errors ---------------------
Initializing gnome-mount extension
Debug: Done reading conf from /etc/beagle/config-files/BeagleSearch.xml
Debug: Done reading conf from /etc/beagle/config-files/Daemon.xml
Got accel 65481, 0, 0
Got keycode 96
Got modmask 0
Got Event! 33, -1
Got Event! 33, -1
** Message: <info>  Forcing device '/org/freedesktop/NetworkManager/Devices/wlan0'
** Message: <info>  You are now connected to the wireless network '+6>Pah>R'.
GLib-GObject-ERROR **: g_type_plugin_*() invalidly modified type `TotemPlParser'
aborting...
--------------------------------------------------
Comment 1 Susana 2008-05-25 16:55:56 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 525954 ***