16.04，升级后，出现eroor geting authority:

jimlon · **发表于 :** 2015-12-11 14:24

Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)

似乎是因为内核升级？

vickycq · **发表于 :** 2015-12-11 14:59

看看原因是否相似
http://askubuntu.com/questions/631362/error-getting-authority-error-initializing-authority-could-not-connect-no-suc
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779057
https://bugs.launchpad.net/lightdm/+bug/1463116
http://c0rp.kz/ubuntu-boot-problem-after-upgrade-14-10-15-04/

引用:

The reason for this error was an entry in /etc/fstab that pointed to partition UUID that was no longer existing....
The solution was to remove the fstab entry.

引用:

When being dropped into emergency mode (e.g. if you have a missing
device from fstab), and you run "systemctl daemon-reload", one gets the
following error message...

引用:

Turns out /var/run was not being (properly?) mounted.
systemd[1]: var-run.mount failed to run 'mount' task (...)
......
All I had to do was comment the following line from /etc/fstab and it solved the problem:
......

引用:

The final solution was to check /etc/fstab for correct entries, and commenting all suspicious lines. For me it was /var/lock mount point.

jimlon · **发表于 :** 2015-12-31 14:09

vickycq 写道:

看看原因是否相似
http://askubuntu.com/questions/631362/error-getting-authority-error-initializing-authority-could-not-connect-no-suc
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779057
https://bugs.launchpad.net/lightdm/+bug/1463116
http://c0rp.kz/ubuntu-boot-problem-after-upgrade-14-10-15-04/

引用:

The reason for this error was an entry in /etc/fstab that pointed to partition UUID that was no longer existing....
The solution was to remove the fstab entry.

引用:

When being dropped into emergency mode (e.g. if you have a missing
device from fstab), and you run "systemctl daemon-reload", one gets the
following error message...

引用:

Turns out /var/run was not being (properly?) mounted.
systemd[1]: var-run.mount failed to run 'mount' task (...)
......
All I had to do was comment the following line from /etc/fstab and it solved the problem:
......

引用:

The final solution was to check /etc/fstab for correct entries, and commenting all suspicious lines. For me it was /var/lock mount point.

忘记回复，
当时查了资料怀疑是fstab的问题，把挂载的几个NTFS分区全注释掉了，然后正常 :Haha

16.04，升级后，出现eroor geting authority:

在线用户