GNOME Bugzilla – Bug 602303
Intermittent error parsing all podcast feeds in Rhythmbox 0.12.5
Last modified: 2015-03-15 17:21:40 UTC
Created attachment 148044 [details] Dependencies After about a couple of days or so of functioning correctly the pod-catching function of Rhythmbox 0.12.5 all podcast feeds start to show a stop error sign and update all no longer works, if you try to update and individual feed the following error is reported: Error in podcast There was a problem adding this podcast: Unable to parse the feed contents. Please verify the URL: http://botchagalupe.libsyn.com/rss # lsb_release -rd Description: Ubuntu 9.10 Release: 9.10 # apt-cache policy rhythmbox rhythmbox: Installed: 0.12.5-0ubuntu4 Candidate: 0.12.5-0ubuntu5 Version table: 0.12.5-0ubuntu5 0 500 http://gb.archive.ubuntu.com karmic-updates/main Packages *** 0.12.5-0ubuntu4 0 500 http://gb.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status ProblemType: Bug Architecture: amd64 Date: Tue Nov 17 11:11:37 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/rhythmbox NonfreeKernelModules: nvidia Package: rhythmbox 0.12.5-0ubuntu4 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: rhythmbox Uname: Linux 2.6.31-14-generic x86_64
Created attachment 148045 [details] ProcMaps
Created attachment 148047 [details] ProcStatus
Created attachment 148048 [details] Xsession Errors
A reboot of the system temporarily fixes this issue, simply killing the application does not.
(In reply to comment #4) > A reboot of the system temporarily fixes this issue, simply killing the > application does not. Try a "killall gvfsd-http" instead? If so, then it's probably an fd leak in gvfs's http code. You can also try to parse the RSS feed using Totem when the problem happens, so you'd see whether the problem is within Rhythmbox itself, or in the supporting libraries.
Your spot on the killall gvfsd-http got it working again.
My spot on? :) Could you check the output of: ls -l /proc/`pidof gvfsd-http`/fd Which would probably show loads of leaked sockets and file descriptors.
Created attachment 148306 [details] Output of ls -l /proc/`pidof gvfsd-http`/fd ls -l /proc/`pidof gvfsd-http`/fd
Reassigning to gvfs. Is there any way to know which remote files those sockets are assigned to, or which program created them? It would make it easier to detect files that aren't closed properly, and avoid fd leaks.
Created attachment 150328 [details] Test program that show problem with gvfsd-http Hi, we are having similar problem that may be related to this bug. For spot the problem i wrote a simple program that load some file from http. Try to execute it and after some time [not deterministic] you get error from g_file_load_contents_async [ DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ] . Kill gvfsd-http fix the problem, but only for a very short time. Michele
I cannot reproduce this. With the port to use SoupSession, the problems of fd leaks should be fixed.