[Dapper] Rhythmbox crashes after two podcasts are deleted

with version 0.9.3.1-0ubuntu7 on powerpc i could not reproduce this.

i added the podcast http://labs.reuters.com/audio/news/usa/top/rss/rss.xml, then right clicked and removed the files one by one from the podcast source.

could you try upgrading to the latest version and installing rhythmbox-dbg. then follow the instructions at https://wiki.ubuntu.com/DebuggingProgramCrash (you dont need to do step 2)

Well, I updated my sources.list and did an upgrade though rhythmbox
package wasn't updated so I must have the latest version. In fact,
after an upgrade it's a bit harder to reproduce the bug. Now, it
doesn't happen every time.
The exact steps that I followed to reproduce the bug were:
1) Launch Rhythmbox.
2) Copy-paste and add this link:
http://labs.reuters.com/audio/news/uk/top/rss/rss.xml
3) Then this link: http://labs.reuters.com/audio/news/uk/world/rss/rss.xml
4) Then delete the World news feed and Rhythmbox crashes.

I include the log file from gdb.
By the way, I'm on i686 if that matters.

P.S. "Aucun fichier ou répertoire de ce type" means "No such file or directory".

(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) run
Starting program: /usr/bin/rhythmbox
[Thread debugging using libthread_db enabled]
[New Thread -1226626848 (LWP 7880)]
[New Thread -1237828688 (LWP 7882)]
[New Thread -1246221392 (LWP 7883)]
[New Thread -1246807120 (LWP 7884)]
[New Thread -1255199824 (LWP 7885)]

(rhythmbox:7880): Rhythmbox-WARNING **: Unable to start mDNS browsing
[New Thread -1265632336 (LWP 7887)]
[Thread -1255199824 (LWP 7885) exited]
[Thread -1246807120 (LWP 7884) exited]
[Thread -1265632336 (LWP 7887) exited]
[New Thread -1265632336 (LWP 7888)]
[New Thread -1246807120 (LWP 7890)]
[Thread -1246807120 (LWP 7890) exited]
[Thread -1265632336 (LWP 7888) exited]
[New Thread -1265632336 (LWP 7891)]
[Thread -1265632336 (LWP 7891) exited]
[New Thread -1265632336 (LWP 7892)]
[Thread -1265632336 (LWP 7892) exited]
[New Thread -1265632336 (LWP 7893)]

(rhythmbox:7880): GLib-GObject-WARNING **: value "235" of type `gint' is invalid or out of range for property `value' of type `gint'

(rhythmbox:7880): GLib-GObject-WARNING **: value "235" of type `gint' is invalid or out of range for property `value' of type `gint'
[New Thread -1246807120 (LWP 7894)]
[New Thread -1255199824 (LWP 7895)]
[New Thread -1277592656 (LWP 7896)]
[Thread -1246807120 (LWP 7894) exited]
[Thread -1265632336 (LWP 7893) exited]
[Thread -1255199824 (LWP 7895) exited]
[Thread -1277592656 (LWP 7896) exited]
[New Thread -1246807120 (LWP 7897)]
[Thread -1246807120 (LWP 7897) exited]
[New Thread -1246807120 (LWP 7898)]

(rhythmbox:7880): GLib-GObject-WARNING **: value "235" of type `gint' is invalid or out of range for property `value' of type `gint'

(rhythmbox:7880): GLib-GObject-WARNING **: value "235" of type `gint' is invalid or out of range for property `value' of type `gint'
[New Thread -1255199824 (LWP 7899)]
[New Thread -1277592656 (LWP 7900)]
[New Thread -1265632336 (LWP 7901)]
[Thread -1265632336 (LWP 7901) exited]
[Thread -1246807120 (LWP 7898) exited]
[Thread -1255199824 (LWP 7899) exited]
[Thread -1277592656 (LWP 7900) exited]
[New Thread -1246807120 (LWP 7902)]
[Thread -1246807120 (LWP 7902) exited]
[New Thread -1246807120 (LWP 7903)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1226626848 (LWP 7880)]
0x080955c1 in rb_podcast_source_cmd_delete_feed (action=0x84aec88, source=0x847d170)
    at rb-podcast-source.c:1366
1366 rb-po...

i followed you instructions but it still did not crash so i'll have to leave this on unconfirmed.

thanks for the gdb backtrace, that helps the devs a lot.

could this be related to Bug #42331

Seems to be fixed with 0.9.4.1, marking as "Fix Committed", if somebody wants to make a simple patch for 0.9.3.1 for dapper we can use it. Other way that's a corner case and we will probably get it fixed with the new version after dapper

i had a look but i could not find the patch that fixes the issue. there was a similar sounding bug http://bugzilla.gnome.org/show_bug.cgi?id=326862 fixed on 2006-01-14, but is before even 0.9.3 was released.

there seems to be lots of patches to the podcast code between 0.9.3 and current. i dont think it would be trivial to patch this without bringing in lots of new code.

fixed with 0.9.5 to edgy