Description of problem: connecting to webdav share via nautilus freezes desktop for a while Version-Release number of selected component (if applicable): nautilus-3.4.2-5.fc17.x86_64 gvfs-1.12.3-1.fc17.x86_64 How reproducible: connect to https://docs.ohm2013.org, make directory, try to upload Actual results: frozen desktop: no alt-TAB, no response to mouseclicks, no response to left windoze key. Expected results: no loss of control Additional info: desktop also freezes when copying data via nfs. see other bug.
(In reply to comment #0) > Description of problem: > connecting to webdav share via nautilus freezes desktop for a while What do you mean by "desktop"? Is it the traditional desktop with icons provided by Nautilus or the whole environment (gnome-shell)? > Version-Release number of selected component (if applicable): > nautilus-3.4.2-5.fc17.x86_64 > gvfs-1.12.3-1.fc17.x86_64 Component version in this bugzilla is rawhide, which is correct?
desktop == gui, so maybe gnome-shell. nothing responded anymore! until a timeout or me killing the dav gfs process. rawhide? we're in fedora 17 until fedora 18 had some updates. sorry for not correcting that. I just did.
Sorry, I've forgot to mention versions: - Fedora 18 - gvfs-1.14.2-3.fc18.x86_64 - nautilus-3.6.3-4.fc18.x86_64
Affects me too Fedora 18 nautilus-3.6.3-4 gvfs-1.14.2-3 everything freezes. I can move only mouse and I can switch to another virtual terminal (Ctrl-Alt-F2; the virtual terminal works OK) relevant: https://bugzilla.gnome.org/show_bug.cgi?id=637382 https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1075923 https://bugzilla.gnome.org/show_bug.cgi?id=697782 https://bugzilla.gnome.org/show_bug.cgi?id=569175
Whatever the real bug is, applications shouldn't be doing sync calls at a first place where's a slightest possibility of that it could take longer than expected (any I/O). (In reply to Ondra Pelech from comment #6) > everything freezes. I can move only mouse and I can switch to another > virtual terminal (Ctrl-Alt-F2; the virtual terminal works OK) Please complain to that "everything" component, the fix should go there in a first place. Ideally with backtrace of the "everything" process showing where's it's frozen. That would also show you the problem causing the freeze (i.e. frozen gvfs backend), so two fixes would be necessary.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
this effect is especially apparent when bittorrent is turned on
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
still present on Fedora 20
Please see the comment 7. Could you provide backtrace for gvfsd-dav and nautilus in time of hang?
can you please tell me how to get the traces? doesn't have to be any verbose howto, I'm somewhat proficient user.
There is wiki page for it: http://fedoraproject.org/wiki/StackTraces#gdb So: - In s time of hang, switch to a console Ctrl+Alt+F2 if possible. - Attach the running process using: gdb <PROCESS> <PID> - And get the trace...
Which process?
The frozen one, good candidates are gvfsd-dav and nautilus as I wrote at the comment 13....
Created attachment 935040 [details] frozen nautilus when gvfsd-dav is stopped in gdb, it freezes the whole system GUI (not just nautilus, but all windows don't respond to clicking, etc) this is the backtrace of nautilus when in such a freeze
Created attachment 935043 [details] lagging gvfsd this is a backtrace of gvfsd-dav with bittorrent client turned on a also downloading a video on youtube this does not freeze the system, but it makes it more or less laggy (the higher the bittorrent traffic, the more laggy the GUI)
Confirmed at f21 too, I tested against ownCloud, a local server in my lan and a remote server, there is two flavors of this problem. If I add the ownCloud server to gnome online accounts the icon to access the server appears on nautilus, accessing the server from that icon "freezes the desktop" (aka. you can move the mouse but can't do anything else), switching to a text console and killing gvfs-dav solves the problem. There's another way to trigger this problem, accessing the dav share putting the url in nautilus address bar, I mean dav://<server>/... (or davs, its the same), now the problem is a little less serious, instead of freezing the desktop it turns slow, deadly slow, tipping is slow, switching windows, etc... I also note that is not a cpu problem, when is freeze or slow, the cpu usage is quite low... and killing gvfs-dav always solves the problem. Final note, this is not a fedora bug, I tested in ubuntu and its the same... so its an upstream problem.
On further testing I think is not gvfsd-dav fault, I tested mounting the same webdav share over davfs2 and almost the same happen, the desktop freeze or is almost unusable. Over davfs2 I saw something crawling the entire share... So, just to test I created a test user, a new one with vanilla gnome desktop, and the mounting goes well, no slowness at desktop. I'm suspecting now of some service running at my desktop, tracker? zeitgeist?... I'm not sure, I usually upgrade or reinstall fedora, but the home is always the same, so I'm not sure what are the differences between my session and the new user one...
(In reply to Ondra Pelech from comment #18) > Created attachment 935040 [details] > frozen nautilus > > when gvfsd-dav is stopped in gdb, it freezes the whole system GUI (not just > nautilus, but all windows don't respond to clicking, etc) > > this is the backtrace of nautilus when in such a freeze I can't reproduce the freezes using gdb. The backtrace isn't really useful, seems nautilus doesn't cause the problem. (In reply to Ondra Pelech from comment #19) > Created attachment 935043 [details] > lagging gvfsd > > this is a backtrace of gvfsd-dav with bittorrent client turned on a also > downloading a video on youtube > > this does not freeze the system, but it makes it more or less laggy > (the higher the bittorrent traffic, the more laggy the GUI) Neither gvfsd-dav backtrace doesn't seems to be useful.
(In reply to Juan Pablo Giménez from comment #21) > On further testing I think is not gvfsd-dav fault, I tested mounting the > same webdav share over davfs2 and almost the same happen, the desktop freeze > or is almost unusable. Over davfs2 I saw something crawling the entire > share... So, just to test I created a test user, a new one with vanilla > gnome desktop, and the mounting goes well, no slowness at desktop. I'm > suspecting now of some service running at my desktop, tracker? zeitgeist?... > I'm not sure, I usually upgrade or reinstall fedora, but the home is always > the same, so I'm not sure what are the differences between my session and > the new user one... It seems to me also like some service using sync calls which can block the shell somehow... maybe some gnome-shell extension to monitor disk/mountpoints or something like that?
So we retest with disabled (killed) zeitgeist and tracker. As I don't have a test webdav site/account at the moment I do hope someone can do this test. Also: Could this bug https://bugzilla.redhat.com/show_bug.cgi?id=579346 be caused by similar circumstances?
Disabling tracker and all gnome extensions everything goes well... so yes, is not gvfsd-dav, I'll try to find the real culprit.
(In reply to udo from comment #24) > So we retest with disabled (killed) zeitgeist and tracker. > As I don't have a test webdav site/account at the moment I do hope someone > can do this test. You can find public accessible webdav test account at: http://www.ajaxfilebrowser.com/ See "Test Folder" paragraph on the right side and just change the http scheme to dav. > Also: > > Could this bug https://bugzilla.redhat.com/show_bug.cgi?id=579346 be caused > by similar circumstances? I don't think so, because nfs isn't provided by gvfs in Fedora currently.
(In reply to Juan Pablo Giménez from comment #25) > Disabling tracker and all gnome extensions everything goes well... so yes, > is not gvfsd-dav, I'll try to find the real culprit. Cool, so please try to find the culprit!
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.