Looked at strace: gedit is stuck in `lstat("/mnt/disk",...)` where
/mnt/disk is a NFS share mounted via autofs, the NFS server is on the
Activating the VPN suddenly cut the communication with the LAN... and
the NFS server!
As soon as I've disabled the autofs service and unmounted `/mnt/disk`
(with -f to force), gedit window suddenly appeared!
So the problem is identified: when starting, `gedit` lists some mount
points and it can stay stuck.
Would that be possible not to list mount points or at leat do it in a
thread so that it doesn't stay stuck without obvious reason? thanks.
(please don't mark as solved as there still a problem with gedit
stat'ing mount points in an unsafe way)
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
gedit is stuck starting, no window is shown
Status in gedit package in Ubuntu:
I use VPN to log to my workplace which uses proxy.
I don't know if the proxy is an issue, but with or without $http_proxy set,
gedit won't start properly.
DistroRelease: Ubuntu 16.04
Package: gedit 3.18.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Date: Tue Sep 20 22:10:49 2016
InstallationDate: Installed on 2016-06-26 (86 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~desktop-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp