System Hangs when switching from one User to another

[Frank Krauss]

Dear Sirs,
I have been using Bionic Beaver for a little while and I find it
seems to Hang a lot more than my previous version Trusty Tahr.
Normally these Hangs occur when switching between different users.

In this case, that was exactly what happened.

1. I had my Normal User Id up and running.
2. I switched over to another Id in order to bring up my Server.
3. I then attempted to switch back to my normal id by pressing
        CTRL + ALT + F1 to get to the screen that gives the list
        of Users that are on your system.
        This did not work
4. I then pressed CTRL + ALT + F2 which did get me back to the
          Normal user Id Screen.
5. At that point the System appeared to have hung.
   The mouse would move around but nothing responded on the Screen
      to either a Mouse Click or any Key presses.
   For example when I pressed CTRL + ALT + "T" The Terminal window
            would NOT come up.
I used the SysrRq - Magic Key combination to get the following information
ALT + PrtScrn, ALT + CREISUB
The system re-booted and gave me the usual files in /var/crash
I used the crash program with the Symbols file and in the backtrace section
   under the exception line it says:
           exception RIP mwait_idle+132
   in the disassembly of mwait_idle, the line at +132 is:
     mov %gs:0x7a174cb4(%rip),%r12d # 0x10350
Any information that I can supply to you I will be glad to in order to
aid you in solving this problem.
I'm computer literate and so I can follow any directions that
you want to give to me.
If you have some commands or Options that you want me to try
at Boot time, I will be happy to oblige.
I have a System with at least three (3) Users on at all times
and I have to be able to shift between them consistantely without
worrying that the process will hang up the System.
Yours truly,
Frank Krauss
(208)-547-4452

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.37
ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
Uname: Linux 5.3.0-51-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sun May 17 17:39:00 2020
InstallationDate: Installed on 2020-04-20 (27 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.update-manager.release-upgrades: 2020-05-17T10:26:59.443734
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2020-04-20 (27 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: ubuntu-release-upgrader (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
Tags: bionic dist-upgrade
Uname: Linux 5.3.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video
_MarkForUpload: True

[Frank Krauss (fmfkrauss)]

apport information

[Frank Krauss (fmfkrauss)]

I added to the Report the output of the command "apport-collect 1879201"

[Frank Krauss (fmfkrauss)]

Dear Sirs,
Please feel free to close out this Bug.
The Solution was to run with the 4.15.0 Nucleus.
The problem was probably caused by the fact that my Computer System was 10+ years old
and so it couldn't support the new HWE code in the 5.x Series.
If you look at bug 1877890 you will see a fuller description of the problem.
Yours truly,
Frank Krauss