Thanks. If you comment out this line from fstab:
tmpfs /var/lock tmpfs defaults 0 0
do things work again?
Note that this is really broken: /var/lock must be a symlink to
/run/lock, otherwise different programs use different lock directories.
However, it's not really obvious that this is the c
Martin Pitt,
I've commented the tmpfs lines in /etc/fstab and now the system starts
perfectly with systemd.
Thanks a lot for your help!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpa
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+attachment/4399331/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launc
Martin Pitt,
Attaching files that you requested.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1452717
Title:
Xorg doesn't start after upgrade from utopic to vivid, start
** Attachment added: "fstab"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+attachment/4399332/+files/fstab
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bug
This was apparently reported on a system where Xorg *does* start,
according to LightdmLog.txt. There is one error which looks fishy:
мая 07 15:49:00 hostname systemd[1]: var-lock.mount: Mount on symlink /var/lock
not allowed.
мая 07 15:49:00 hostname systemd[1]: var-lock.mount failed to run 'moun
** Changed in: systemd (Ubuntu)
Importance: Medium => Low
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
** Description changed:
- Problem happens when choosing a normal boot.
- Works ok when choosing upstart.
+ Problem happens when choosing a normal boot. Works ok when choo
Christopher M. Penalver, I used a spare HDD to install a clean Vivid and
it works well. I works well even after installation of proprietary
Nvidia driver.
So, is there anything that can be done to repair the upgraded system, or
using upstart configuration is the only option ?
--
You received thi
Lior Goikhburg, folks typically backup their data, and then do a new
install.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1452717
Title:
Xorg doesn't start after upgrad
Christopher M. Penalver, that's something I cannot test ATM, as it would
require reformating my laptop and installing a fresh Vivid from scratch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.
Lior Goikhburg, thank you for reporting this and helping make Ubuntu
better. Does this still occur if you do a new install of Vivid via
http://releases.ubuntu.com/vivid/ubuntu-15.04-desktop-amd64.iso ?
** Package changed: xorg (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Import
11 matches
Mail list logo
