GNOME Bugzilla – Bug 343853
Rhythmbox crashes after podcast update
Last modified: 2006-06-07 05:12:53 UTC
Steps to reproduce: 1. gdb /usr/bin/rhythmbox 2. run 3. bt 4. bt full Stack trace: 1. debug using gdb 2. debug using bug buddy ################################# 1. ### $ gdb /usr/bin/rhythmbox GNU gdb 6.4-debian Copyright 2005 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i486-linux-gnu"...(no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (gdb) run Starting program: /usr/bin/rhythmbox (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1496090944 (LWP 18835)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread -1498801232 (LWP 18838)] [New Thread -1499411536 (LWP 18844)] [New Thread -1507804240 (LWP 18845)] [Thread -1499411536 (LWP 18844) exited] [Thread -1507804240 (LWP 18845) exited] [New Thread -1499411536 (LWP 18848)] [New Thread -1507804240 (LWP 18849)] [Thread -1507804240 (LWP 18849) exited] [Thread -1499411536 (LWP 18848) exited] [New Thread -1499411536 (LWP 18850)] [New Thread -1507804240 (LWP 18851)] [New Thread -1542456400 (LWP 18852)] [New Thread -1550849104 (LWP 18853)] [New Thread -1559241808 (LWP 18854)] [Thread -1507804240 (LWP 18851) exited] [Thread -1499411536 (LWP 18850) exited] [Thread -1542456400 (LWP 18852) exited] [New Thread -1542456400 (LWP 18855)] [Thread -1542456400 (LWP 18855) exited] [Thread -1559241808 (LWP 18854) exited] [New Thread -1559241808 (LWP 18889)] [New Thread -1542456400 (LWP 18890)] [New Thread -1499411536 (LWP 18891)] [New Thread -1507804240 (LWP 18892)] [Thread -1559241808 (LWP 18889) exited] [Thread -1507804240 (LWP 18892) exited] [Thread -1499411536 (LWP 18891) exited] [Thread -1542456400 (LWP 18890) exited] ---Type <return> to continue, or q <return> to quit--- Program received signal SIGSEGV, Segmentation fault.
+ Trace 68644
Thread NaN (LWP 18835)
Other information: I run my Debian SID on a FujitsuSiemens laptop, with Xfce as WE. Everything works fine and is up-to-date.
Which podcast feeds have you added to rhythmbox? It may be a problem in how we parse the feed.
here my podcast feeds: http://www.ilsole24ore.com/rss/radio24_podcasting.xml http://www.radio.rai.it/radio3/podcast/rssradio3.jsp http://rss.kataweb.it/podcasting/repubblicaradio.xml http://www.wto.org/library/rss/podcasts_e.xml
I can't reproduce the problem with CVS HEAD or 0.9.4.1. Stack trace looks basically the same as bug 343981.
The stace trace is basically the same, and two of those feed have slightly odd <pubdate> tags, which weren't handled correctly in 0.9.4.1 but are not fixed. So I'm marking as a dupe. *** This bug has been marked as a duplicate of 343981 ***