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 369712 - crash in Rhythmbox Music Player: Trying to add new podcas...
crash in Rhythmbox Music Player: Trying to add new podcas...
Status: RESOLVED DUPLICATE of bug 336842
Product: rhythmbox
Classification: Other
Component: general
0.9.5
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-02 23:09 UTC by gavin_young
Modified: 2006-11-07 14:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description gavin_young 2006-11-02 23:09:15 UTC
What were you doing when the application crashed?
Trying to add new podcast feed (v0.9.5)


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
----------- .xsession-errors (929 sec old) ---------------------
5356: arguments to dbus_pending_call_get_completed() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 581.
This is normally a bug in some application using the D-Bus library.
5356: arguments to dbus_pending_call_steal_reply() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 604.
This is normally a bug in some application using the D-Bus library.
5356: arguments to dbus_pending_call_unref() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 487.
This is normally a bug in some application using the D-Bus library.
5356: arguments to dbus_pending_call_get_completed() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 581.
This is normally a bug in some application using the D-Bus library.
5356: arguments to dbus_pending_call_steal_reply() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 604.
This is normally a bug in some application using the D-Bus library.
5356: arguments to dbus_pending_call_unref() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 487.
This is normally a bug in some application using the D-Bus library.
5356: arguments to dbus_pending_call_get_completed() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 581.
This is normally a bug in some application 
...Too much output, ignoring rest...
--------------------------------------------------

Memory status: size: 132235264 vsize: 0 resident: 132235264 share: 0 rss: 18411520 rss_rlim: 0
CPU usage: start_time: 1162508871 rtime: 0 utime: 106 stime: 0 cutime:100 cstime: 0 timeout: 6 it_real_value: 0 frequency: 1

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208244512 (LWP 7272)]
[New Thread -1299608688 (LWP 7286)]
[New Thread -1289118832 (LWP 7280)]
0x009b1402 in __kernel_vsyscall ()

Thread 2 (Thread -1299608688 (LWP 7286))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 rb_podcast_parse_load_feed
    at rb-podcast-parse.c line 505
  • #5 rb_podcast_manager_thread_parse_feed
    at rb-podcast-manager.c line 729
  • #6 g_thread_create_full
    from /lib/libglib-2.0.so.0
  • #7 start_thread
    from /lib/libpthread.so.0
  • #8 clone
    from /lib/libc.so.6

Comment 1 Alex Lancaster 2006-11-02 23:23:18 UTC
Couldn't find a dupe of this bug, but please plead with the rhythmbox maintainer on Fedora to upgrade to 0.9.6 because many of these podcast-related bugs were fixed in 0.9.6.  I was planning to file a bug on bugzilla.redhat.com myself.
Comment 2 Jonathan Matthew 2006-11-07 14:24:49 UTC
This is actually a duplicate of bug 336842, which would have been fixed in 0.9.5 were it not for a typo.

This, ladies and gentlemen, is why it's a bad idea to have variables called 'ctxt' and 'ctx' in the same scope.

*** This bug has been marked as a duplicate of 336842 ***