Hi. I don't know if it is a nautilus bug or a gnome-user-share one. If I enable "Personal file sharing" in the control center, then open nautilus and select "Browse network", I get a "Public files of user on machine" folder. If I try to open it, I get the following error dialog: "Can't access to location - HTTP error: internal server error" (Message are a translation of what I actually get, I'm using the french locale). I also get this error from one machine trying to open a shared folder on another machine.
When I have "Personal file sharing" enabled, I have the following processes running, which seems to look fine: ps ax | grep http 24379 ? Sl 0:00 /usr/libexec/gvfsd-http --spawner :1.3 /org/gtk/gvfs/exec_spaw/7 28441 ? Ss 0:01 /usr/sbin/httpd -f /usr/share/gnome-user-share/dav_user_2.4.conf -C Listen 46708 28442 ? S 0:00 /usr/sbin/httpd -f /usr/share/gnome-user-share/dav_user_2.4.conf -C Listen 46708 28443 ? S 0:00 /usr/sbin/httpd -f /usr/share/gnome-user-share/dav_user_2.4.conf -C Listen 46708
Seeing the same here. On top of that, I find that gnome-user-share is not started/stopped when I flick the switch in the sharing panel.
What's in ~/.config/user-share/log ?
I do notice the following in the logs: May 31 06:31:05 golem /etc/gdm/Xsession[9305]: JS LOG: pushModal: invocation of begin_modal failed May 31 06:31:08 golem kernel: gvfsd-dav[10162]: segfault at 4 ip 00007febd73abd90 sp 00007fff10f295f8 error 6 in libdbus-1.so.3.7.2[7febd7387000+45000] May 31 06:31:08 golem /etc/gdm/Xsession[9305]: JS LOG: pushModal: invocation of begin_modal failed May 31 06:31:11 golem kernel: pool[10193]: segfault at 4 ip 00007f602c408d90 sp 00007f601f3ed798 error 6 in libdbus-1.so.3.7.2[7f602c3e4000+45000] So I think gvfsd-dav may be to blame here
Created attachment 755227 [details] .config/user-share/log
Created attachment 755256 [details] a gvfsd log
here is a log from GVFS_HTTP_DEBUG=all gvfsd -r, while I was first clicking on Browse network and then on mclasens public files in nautilus, which gave me a HTTP request cancelled warning.
From a quick look it seems like we're not catching the soup_authenticate_interactive() callback, which is connected to the "authenticate" signal on SoupSession instance. Could be a fallout from recent port to SoupRequester or could be a libsoup issue internally. (In reply to Matthias Clasen from comment #4) > May 31 06:31:08 golem kernel: gvfsd-dav[10162]: segfault at 4 ip > 00007febd73abd90 sp 00007fff10f295f8 error 6 in > libdbus-1.so.3.7.2[7febd7387000+45000] Could be from some library, we shouldn't be using libdbus in gvfsd-dav.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.