>> Should we continue solving the timeout problem in this issue? > Yes, let's do that. What do you mean by a 120000ms timeout, does the chromium window take 2 whole minutes to appear when you launch it?
Yes it does wait for 2 minutes before showing a window. It's a pain and makes the chromium practically useless on an NFS-homed workstation that is shutdown every time after it has been used. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1848753 Title: [snap] chromium times out connecting document portal with NFS home Status in snapd: New Status in chromium-browser package in Ubuntu: Incomplete Status in snapd package in Ubuntu: New Bug description: I have my /home folder shared via NFS from a local server one floor below in my house. The server runs Ubuntu 18.04. After starting a snapped version of chromium-browser in my Ubuntu 19.10 the document portal timeouts like this: XXX@koira:~$ chromium-browser 2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document portal: Failed to activate service 'org.freedesktop.portal.Documents': timed out (service_start_timeout=120000ms) After the timeout my chromium cannot seem to remember accounts or passwords. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1848753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
