Re: [Touch-packages] [Bug 1453307] Re: The booting process ends in a terminal. No lightdm, no graphic screen. The file system is read only. It is a systemd problem, because I can use upstart with no p

*** This bug is a duplicate of bug 1431743 *** https://bugs.launchpad.net/bugs/1431743 That was it. I changed the invalid UUID for the correct one and everything is fine now. As I can see, I was not the only one to have this problem. Thank you Martin for your excellent support! g 2015-06-12

Re: [Touch-packages] [Bug 1453307] Re: The booting process ends in a terminal. No lightdm, no graphic screen. The file system is read only. It is a systemd problem, because I can use upstart with no p

Hi, Sorry, I didn't have time before today to try what you suggest. So I added hte init=/bin/sysetmd to the grub command line and I installed the /var/log/journal. I could open a terminal on VT 9. When I tried to journalctl -b root/journal.txt I had the message Read only file system. So I

Re: [Touch-packages] [Bug 1453307] Re: The booting process ends in a terminal. No lightdm, no graphic screen. The file system is read only. It is a systemd problem, because I can use upstart with no p

with upstart at 14:14 Thanks, Gilbert Dion Attached: syslog g 2015-05-18 4:13 GMT-04:00 Martin Pitt martin.p...@ubuntu.com: You reported this under upstart, so there are no logs yet to diagnose the problem. Please boot with systemd, and describe what you see: do you get an emergency mode root shell