[SOLVED] Your session only lasted less than 10 seconds

I am running Linux Mint 18.3. I updated, from the update manager, Virtualbox plus guest additions and add-ons. Then I tried to open VLC Media Player which would not open. I reinstalled anything to do with VLC from Synaptic Package Manager nut still could not open VLC.

So, I logged out and when I tried to log back in I got the error message above, plus the following information:

(~.xsession-errors file)

syndaemon:no process found
/etc/mdm/Xsession:Begining session setup ...
Localuser:donald being added to access control list


I am in the middle of something very urgent and will reinstall the system if I have to. Any suggestions would be greatly appreciated.

I am having the exact same issue. I also just updated Virtualbox and now get the msg "Your session only lasted less than 10 seconds"

initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connect syndaemon: no process found

A lot of people have just reported this at the Mint Forum. Log in at the CLI (press Ctrl-Alt-F2) to get there) and do
sudo apt-get remove virtualbox*
which should enable you to use the GUI again. Presumably you can get the old version of Virtualbox, if you must have it.

Unfortunately that didn't fix it for me. I still have the same error message.

it worked for me.

thx

Oops. I forgot the asterix at the end of Virtualbox. I re-ran the command and now I am up and running again. Many thanks!!

Thread on Mint forum: https://forums.linuxmint.com/viewtop...?f=47&t=266431

I am hoping this is my problem--certainly it followed the last batch of updates. Unfortunately, so far I have been unable to open the terminal.

I take it I should be able to open the terminal before logging in? (each time I try to log-in, I see the same error message)

I use a an Apple keyboard, and the Ctl-Alt-F2 key combination isn't responding. Would there be a different key-combination with this keyboard, or do I just need to borrow a regular keyboard?

Thanks

Brant,

See Clem's reply on:
https://forums.linuxmint.com/viewtop...66431&start=40

If you already applied the virtualbox-guest* updates and you're unable to log in:

Drop to console by pressing CTRL+ALT+F1
Login in text mode
Remove the virtualbox guest packages with the command below:

sudo apt-get purge virtualbox-guest-dkms virtualbox-guest-utils virtualbox-guest-x11

Reboot the computer

Originally Posted by Brant I am hoping this is my problem--certainly it followed the last batch of updates. Unfortunately, so far I have been unable to open the terminal. I take it I should be able to open the terminal before logging in? (each time I try to log-in, I see the same error message) I use a an Apple keyboard, and the Ctl-Alt-F2 key combination isn't responding. Would there be a different key-combination with this keyboard, or do I just need to borrow a regular keyboard?

When you see the log-in screen, you need to move to a CLI terminal. On a PC this is done with Control + Alternate + any function key other than F7 or F1, one of which will give you the GUI.

On an Mac keyboard, the equivalent to Control is Option (four loops) and the equivalent to Alternate is Option (bird).

When you've removed the Virtual box things, Cmd+Opt+F7 (or perhaps F1) takes you back to the GUI. If it doesn't work, reboot and try again.

Grat. Thanks very much.

I am having the exact same issue on my new installation. Many thanks for this thread as I was considering a new SSD.

A friend installed 18.3 on his i5 laptop two weeks ago. On reboot there was only desktop wallpaper. We reinstalled totally last Tuesday - all appeared to be fine. I got a call that evening to say it was still not working. I suspect that the issue (still unseen by me) may be associated with this issue too. Time will tell.

Originally Posted by winlinuser I am having the exact same issue on my new installation. Many thanks for this thread as I was considering a new SSD. A friend installed 18.3 on his i5 laptop two weeks ago. On reboot there was only desktop wallpaper. We reinstalled totally last Tuesday - all appeared to be fine. I got a call that evening to say it was still not working. I suspect that the issue (still unseen by me) may be associated with this issue too. Time will tell.

A rocky introduction to Mint for your friend! Let us know if it wasn't the virtualbox-guest issue that was the problem.

I had a corrupted nvidia install, had to sudo apt purge nvidia*
Then it worked again and I reinstalled the nvidia driver.
Did a control-alt-f1 and logged into the console window outside of the gui.

The os was running on a mb with serious memory errors, and there were many weird problems, I finally ditched the board.

I ran a memtest, had failures on block move test on GOOD memory. Simply moved to another slot, memory passed, but its weird problems resurfaced. One was sometimes at boot, got a hard drive writing outside of hd0 error, on a GOOD hard drive.

After I moved the install onto a good working mb, I reinstalled the OS to make sure any file corruption would be gone.

Originally Posted by sdowney717 I had a corrupted nvidia install, had to sudo apt purge nvidia* Then it worked again and I reinstalled the nvidia driver. Did a control-alt-f1 and logged into the console window outside of the gui. The os was running on a mb with serious memory errors, and there were many weird problems, I finally ditched the board. I ran a memtest, had failures on block move test on GOOD memory. Simply moved to another slot, memory passed, but its weird problems resurfaced. One was sometimes at boot, got a hard drive writing outside of hd0 error, on a GOOD hard drive. After I moved the install onto a good working mb, I reinstalled the OS to make sure any file corruption would be gone.

My goodness, you've been having fun and games. I'm glad you've got it all sorted now.