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 564842 - online radio connection remains open after leaving rhythmbox
online radio connection remains open after leaving rhythmbox
Status: RESOLVED DUPLICATE of bug 563382
Product: gvfs
Classification: Core
Component: http backend
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2008-12-17 11:17 UTC by Pedro Villavicencio
Modified: 2009-01-26 11:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pedro Villavicencio 2008-12-17 11:17:29 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/rhythmbox/+bug/302111

rhythmbox version is: 0.11.6svn20081008

"i've launched online radios, i noticed that gvfs-http has opened some sockets
for the websites as well as rhythmbox. When i stop the playback and close rhythmbox, the
sockets of rythmbox were closed but gvfs-http's were not. They stayed CLOSE_WAIT until i kill the process (three hours after).
Is there a way to close all used sockets at leaving (even the gvfs-http ones)?"

"

just a mere coincidence but i've been hit by this today. I' m not an usual user off rythmbox but i decided to give it a try and found the exact same behaviour:

sudo netstat -tupan | grep gvfs
[sudo] password for andres:
tcp 1 0 172.29.93.100:50517 200.75.56.170:80 CLOSE_WAIT 20321/gvfsd-http
tcp 0 0 172.29.93.100:40005 200.75.56.170:80 ESTABLECIDO 20321/gvfsd-http
tcp 1 0 172.29.93.100:40178 200.75.56.170:80 CLOSE_WAIT 20321/gvfsd-http
tcp 0 0 172.29.93.100:56583 72.21.207.7:80 ESTABLECIDO 20321/gvfsd-http
tcp 1 0 172.29.93.100:38753 200.75.56.170:80 CLOSE_WAIT 20321/gvfsd-http
tcp 1 0 172.29.93.100:50518 200.75.56.170:80 CLOSE_WAIT 20321/gvfsd-http
tcp 0 0 172.29.93.100:40006 200.75.56.170:80 ESTABLECIDO 20321/gvfsd-http
tcp 1 0 172.29.93.100:40180 200.75.56.170:80 CLOSE_WAIT 20321/gvfsd-http
tcp 1 0 172.29.93.100:45072 200.75.56.170:80 CLOSE_WAIT 20321/gvfsd-http
tcp 1 0 172.29.93.100:45051 200.75.56.170:80 CLOSE_WAIT 20321/gvfsd-http
tcp 1 0 172.29.93.100:45071 200.75.56.170:80 CLOSE_WAIT 20321/gvfsd-http
tcp 0 0 172.29.93.100:52957 72.21.207.7:80 ESTABLECIDO 20321/gvfsd-http
"

is this a gvfs issue?

Thanks in advance,
Comment 1 Jonathan Matthew 2008-12-17 11:39:08 UTC
This might be a bug in gvfs or possibly libsoup (or maybe even the kernel..), but I don't really see how it could be a bug in rhythmbox.  It has no control over sockets opened by other processes.
Comment 2 Tom Hughes 2009-01-26 11:01:36 UTC
This is a duplicate of bug #563382.
Comment 3 A. Walton 2009-01-26 11:05:08 UTC

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