Sorry, but it seems that adding the user to the fuse group is not
necessary. Just killing gvfs, nautilus -q and restart it does the trick.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/
Had this issue since a recent update. I'm using a 16.04. All worked
fine, and after an update the /run/user//gvfs stayed empty. I added
my user to fuse group, killed gvfs and restarted nautilus, and it
worked.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
Argyle: first of all it may help if you read the thread, as I have
described the solution further up!;)
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm
Hi guys!
I guess what Bryce Harrington required from me is then obsolete?
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs
Ladies and gentlemen here comes the solution:
I realized by connecting to the machine via ssh that actually everything is
running, ie. GDM, X, Pulse, whatever you just don't get to see anything which
is due to a completely out of range resolution of horizontal 268kHz, vertical
281Hz.
I have now
Ok guys, here's the deal:
Not only GDM is not starting but also TTY1-TTY7 are being terminated, and that
before GDM is attempted to be started.
Of course GDM cannot start if there is no TTY available.
Further this problem occurs only with kernel 2.6.31-14
kernel 2.6.28-15 boots perfectly!
Btw. t
