** Description changed: Binary package hint: nvidia-settings I have a Dell D620 laptop with a nvidia card that I bring with me between work and home. After resuming from suspend at work, I typically run nvidia-settings to switch to my external screen, but nvidia-settings tends to hang for a long time before opening its window. Minor annoyance, as it will usually come around. Today I ran an strace, and I think this identifies the culprit. It ends like this: stat64("/home/ketil/.config", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat64("/home/ketil/.local", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 stat64("/home/ketil/.selected_editor", {st_mode=S_IFREG|0644, st_size=74, ...}) = 0 stat64("/home/ketil/#.gnus.el#", {st_mode=S_IFREG|0644, st_size=2354, ...}) = 0 stat64("/home/ketil/gal.csv.gz", {st_mode=S_IFREG|0644, st_size=5367671, ...}) = 0 stat64("/home/ketil/.gcjwebplugin", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 stat64("/home/ketil/_newsrc.eld", {st_mode=S_IFREG|0644, st_size=45174, ...}) = 0 stat64("/home/ketil/bin", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat64("/home/ketil/data", ^C <unfinished ...> Now, "data" is an sshfs mount, which obviously got broken when I suspended the machine, and stat64 apparently hangs non-interruptedly for - a long time when a mount has gone astray. So, easily fixed by mounting - stuff in a subdirectory (i.e. ~/mnt/data) instead, but still, two - questions: + a long time when a mount has gone astray. - 1. Does the kernel really need to wait this long for stat'ing a broken network mount? Couldn't it somehow be detected? + So, to reproduce it, I just did: + 1. mount a disk over the net in your home directory + 2. run nvidia-settings, verify that it pops up immediately + 3. unplug the net + 4. run nvidia-settings again, see that it hangs for a long time + 5. reconnect net, check that net mount works + 6. run nvidia-settings, immediate response again + + Of course, this is easily worked around by mounting stuff in a + subdirectory (i.e. ~/mnt/data) instead, but still, two questions: + + 1. Does the kernel/stat64 really need to wait this long for stat'ing a broken network mount? Couldn't it somehow be detected? 2. Does nvidia-settings *really* need to stat each and every file in my home directory?
-- nvidia-settings hangs for some time after suspend https://bugs.launchpad.net/bugs/388296 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in ubuntu. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp