Bsrgvty

How do you all work out the relative costs of spells?

Does this code demonstrate the central limit theorem?

Conveying the idea of « go figure »

What is the difference between "more" and "less" commands?

Is the worst version of the accusations against President Trump impeachable?

Why is it recommended to combine WordPress and Godaddy for hosting?

Is there any benefit of being treated as "professor" by students and admin?

Is there a guide/reference for character hairstyle possible in D&D Forgotten Realms universe?

How can an AI train itself if no one is telling it if its answer is correct or wrong?

Which quantity is mass (tensor, vector or scalar)?

Idiom for "Ahead of its time"

Why is a living creature being frozen in carbonite in “The Mandalorian” so common when it seemed so risky in “The Empire Strikes Back?”

What do you call candidates in elections who don't actually have a chance to win and only create an illusion of competition?

Why are compartments in western European day trains falling out of fashion?

What does "two ells within the selvages" mean in the Magna Carta?

Which Grows Faster: Factorial or Double Exponentiation

Don't let this riddle put you in a foul mood

How to create a new file via touch if it is in a directory which doesn't exist?

Risk Neutral and Real World Valuations using Monte Carlo

How can I justify this without determining the determinant?

Why would anyone choose not use the lowlatency kernel?

Mindslavering a Mindslavered player?

Why is Gaia operating around Earth orbit? Why not send it to Neptune's orbit?

How to prepare for The Mandalorian?

Ubuntu Window Manager Not starting after Upgrade from 18.04 to 19.04 (logs attached)

Trouble upgrading ubuntu 11.10 to 12.04 LTS after upgrading from 10.04Ubuntu can't boot after upgrade from 13.04 to 13.10 without inserting a random remote disk/harddriveupgrade from 16.04 to 18.04, lock screen is stuck19.04 will not boot from HD nor USBProblem installing Ubuntu 19.04 (18.04)

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;

0

two days ago, I updated my Ubuntu System from 17.10 to 18.04. And despite being actually too late, everything went almost without any issue (only minor things I could fix quickly). Afterwards I run apt-get update/upgrade to bring everything up-to-date, also without issues.

Happy with that result, I decided yesterday to update further. I set the update mode from lts to normal and run do-release-upgrade again. I expected the system to upgrade to 18.10 first but it did directly an upgrade to 19.04. Everything run through smoothly but after reboot the system is not usable.

The Mate booting screen is shown properly. Afterwards both screens show a new background, and an almost empty panel, which is blinking every few seconds. I can click right on the desktop, but there are no helpful actions. Keyboard commands are not recognized, with the exception of Alt+Ctrl+F1 and similar.

It looks like this after start: https://drive.google.com/open?id=10_RixZrn3PysInUmTkHUoTu5KGBurRrL

This is the shown error message: https://drive.google.com/open?id=10a5W-1BsQUREw62Z2aCKv4HupHzAykAT

I used the terminal session to look at some log files in /var/log. On the console with really low resolution and without scrolling ability (using less instead), I had really problems to find anything helpful. Especially, as there are ten-thousands of lines in the relevant time frame.

I tried to boot in recovery mode, choosing the failsafeX Option. But this way the screens remained black with a blinking cursor.

I am thinking about booting with a live cd and checking the log files in a more comfortable environment. What would be the first things/files to look for/at?

Thanks for your time and eventual help,

McMatt

PS: As suggested, I executed journalctl and got this output:
https://drive.google.com/file/d/1an9B-ilmA01Vm9Gr7TbEc50QjALGVokx
I am a bit lost in there, none of the errors sticks out as critical. Please let me know, if you have found something that might be causing the startup issue.

18.04 upgrade xorg 19.04 mate

share|improve this question

edited Sep 22 at 11:17

McMatt

asked Sep 19 at 9:17

McMattMcMatt

111 bronze badge

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  When you say Ctrl+Alt+F1 works are you saying you can log into a terminal session? If so try journalctl to look for errors.
  
  – WinEunuuchs2Unix
  Sep 19 at 11:48
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for the hint. Yes to your question, but as I have already booted the live cd, I do it from here. I mounted the partition containing the log files and executed: journalctl --directory=/mnt/sda2/var/log/journal/ --since="2019-09-19 12:00:00" >> /tmp/journal.txt. (I did start the system once before switching to the live cd to generate fresh log files). I hope that I can attach the file here somehow.
  
  – McMatt
  Sep 19 at 19:34
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Here is the result of the comment: drive.google.com/open?id=1an9B-ilmA01Vm9Gr7TbEc50QjALGVokx
  
  – McMatt
  Sep 19 at 19:41
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I added a video of the final situation after startup: drive.google.com/file/d/10_RixZrn3PysInUmTkHUoTu5KGBurRrL/…
  
  – McMatt
  Sep 21 at 10:36
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This is error message that shows up: drive.google.com/file/d/10a5W-1BsQUREw62Z2aCKv4HupHzAykAT/…
  
  – McMatt
  Sep 21 at 10:39
  

  
  
  
  

 | 
show 4 more comments

0

two days ago, I updated my Ubuntu System from 17.10 to 18.04. And despite being actually too late, everything went almost without any issue (only minor things I could fix quickly). Afterwards I run apt-get update/upgrade to bring everything up-to-date, also without issues.

Happy with that result, I decided yesterday to update further. I set the update mode from lts to normal and run do-release-upgrade again. I expected the system to upgrade to 18.10 first but it did directly an upgrade to 19.04. Everything run through smoothly but after reboot the system is not usable.

The Mate booting screen is shown properly. Afterwards both screens show a new background, and an almost empty panel, which is blinking every few seconds. I can click right on the desktop, but there are no helpful actions. Keyboard commands are not recognized, with the exception of Alt+Ctrl+F1 and similar.

It looks like this after start: https://drive.google.com/open?id=10_RixZrn3PysInUmTkHUoTu5KGBurRrL

This is the shown error message: https://drive.google.com/open?id=10a5W-1BsQUREw62Z2aCKv4HupHzAykAT

I used the terminal session to look at some log files in /var/log. On the console with really low resolution and without scrolling ability (using less instead), I had really problems to find anything helpful. Especially, as there are ten-thousands of lines in the relevant time frame.

I tried to boot in recovery mode, choosing the failsafeX Option. But this way the screens remained black with a blinking cursor.

I am thinking about booting with a live cd and checking the log files in a more comfortable environment. What would be the first things/files to look for/at?

Thanks for your time and eventual help,

McMatt

PS: As suggested, I executed journalctl and got this output:
https://drive.google.com/file/d/1an9B-ilmA01Vm9Gr7TbEc50QjALGVokx
I am a bit lost in there, none of the errors sticks out as critical. Please let me know, if you have found something that might be causing the startup issue.

18.04 upgrade xorg 19.04 mate

share|improve this question

edited Sep 22 at 11:17

McMatt

asked Sep 19 at 9:17

McMattMcMatt

111 bronze badge

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  When you say Ctrl+Alt+F1 works are you saying you can log into a terminal session? If so try journalctl to look for errors.
  
  – WinEunuuchs2Unix
  Sep 19 at 11:48
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for the hint. Yes to your question, but as I have already booted the live cd, I do it from here. I mounted the partition containing the log files and executed: journalctl --directory=/mnt/sda2/var/log/journal/ --since="2019-09-19 12:00:00" >> /tmp/journal.txt. (I did start the system once before switching to the live cd to generate fresh log files). I hope that I can attach the file here somehow.
  
  – McMatt
  Sep 19 at 19:34
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Here is the result of the comment: drive.google.com/open?id=1an9B-ilmA01Vm9Gr7TbEc50QjALGVokx
  
  – McMatt
  Sep 19 at 19:41
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I added a video of the final situation after startup: drive.google.com/file/d/10_RixZrn3PysInUmTkHUoTu5KGBurRrL/…
  
  – McMatt
  Sep 21 at 10:36
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This is error message that shows up: drive.google.com/file/d/10a5W-1BsQUREw62Z2aCKv4HupHzAykAT/…
  
  – McMatt
  Sep 21 at 10:39
  

  
  
  
  

 | 
show 4 more comments

two days ago, I updated my Ubuntu System from 17.10 to 18.04. And despite being actually too late, everything went almost without any issue (only minor things I could fix quickly). Afterwards I run apt-get update/upgrade to bring everything up-to-date, also without issues.

Happy with that result, I decided yesterday to update further. I set the update mode from lts to normal and run do-release-upgrade again. I expected the system to upgrade to 18.10 first but it did directly an upgrade to 19.04. Everything run through smoothly but after reboot the system is not usable.

The Mate booting screen is shown properly. Afterwards both screens show a new background, and an almost empty panel, which is blinking every few seconds. I can click right on the desktop, but there are no helpful actions. Keyboard commands are not recognized, with the exception of Alt+Ctrl+F1 and similar.

It looks like this after start: https://drive.google.com/open?id=10_RixZrn3PysInUmTkHUoTu5KGBurRrL

This is the shown error message: https://drive.google.com/open?id=10a5W-1BsQUREw62Z2aCKv4HupHzAykAT

I used the terminal session to look at some log files in /var/log. On the console with really low resolution and without scrolling ability (using less instead), I had really problems to find anything helpful. Especially, as there are ten-thousands of lines in the relevant time frame.

I tried to boot in recovery mode, choosing the failsafeX Option. But this way the screens remained black with a blinking cursor.

I am thinking about booting with a live cd and checking the log files in a more comfortable environment. What would be the first things/files to look for/at?

Thanks for your time and eventual help,

McMatt

PS: As suggested, I executed journalctl and got this output:
https://drive.google.com/file/d/1an9B-ilmA01Vm9Gr7TbEc50QjALGVokx
I am a bit lost in there, none of the errors sticks out as critical. Please let me know, if you have found something that might be causing the startup issue.

18.04 upgrade xorg 19.04 mate

share|improve this question

edited Sep 22 at 11:17

McMatt

asked Sep 19 at 9:17

McMattMcMatt

111 bronze badge

share|improve this question

edited Sep 22 at 11:17

McMatt

asked Sep 19 at 9:17

McMattMcMatt

111 bronze badge

share|improve this question

edited Sep 22 at 11:17

McMatt

asked Sep 19 at 9:17

McMattMcMatt

111 bronze badge

asked Sep 19 at 9:17

McMattMcMatt

111 bronze badge

asked Sep 19 at 9:17

McMattMcMatt

111 bronze badge