starting version 219 after updating to 15.04

Asked by Bohdan Harasymiw on 2015-04-24

I have just updated to Ubuntu 15.04 and keep getting "starting version 219" error. The only way that I can boot in to Ubuntu 15.04 is to hold down the Shift key and then boot in to Safe mode.

Without doing anything else, if I then select "Resume normal boot" Ubuntu 15.04 boots up okay.

How can I fix this problem?

Question information

English Edit question
Ubuntu Edit question
No assignee Edit question
Last query:
Last reply:

I suggest you report a bug

Manfred Hampl (m-hampl) said : #2

The message "starting version 219" is just informational and does not cause any harm, see bug #1432171

If you system is a kubuntu system, maybe you have a similar error to the one shown in

Bohdan Harasymiw (bsamhara) said : #3

My system is a straight Ubuntu system.

I saw the various Kubuntu fixes suggesting to do a sudo systemctl enable sddm.service -f but don't know what the equivalent is in Ubuntu. That command is not recognised on my system.

My concern is that I can't boot up without first going through the Safe mode first. So something is obviously wrong. I have reported it as a bug as suggested by Andrew.

Manfred Hampl (m-hampl) said : #4

I see the following warning in your dmesg output in bug# 1447978

"/usr appears to be on its own filesystem and is not already mounted. This is not a supported setup. Some things will probably break (sometimes even silently) in mysterious ways. Consult for more information."

Maybe that is the culprit? This would explain that a two-step boot with recovery mode and then resuming normal boot might give the system enough time to complete mounting the /usr partition.

Bohdan Harasymiw (bsamhara) said : #5

I have just run Gparted and note that I have usr and var and tmp on separate partitions. From that article that you provide a link to it suggests that I should move var to the root partition. Should I also move the var and tmp directories to the root partition?

Also in moving the directories, what is the most appropriate way to do so with breaking something else?

Fodiator (fodiator) said : #6

By chance I found out that sddm shows black screen with or without this "219" message and doesn't show login screen if configuration of pam_mount (/etc/security/pam_mount.conf.xml) is somehow inaccurate. Maybe some above mentioned problems result from this.

Can you help with this problem?

Provide an answer of your own, or ask Bohdan Harasymiw for more information if necessary.

To post a message you must log in.