[Bug 1879585] Re: System Hung when moving Windows around on the Screen

2020-06-01 Thread Frank Krauss
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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879585

Title:
  System Hung when moving Windows around on the Screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1879585/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879201] Re: System Hangs when switching from one User to another

2020-06-01 Thread Frank Krauss
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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879201

Title:
  System Hangs when switching from one User to another

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1879201/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879176] Re: System Hangs after being in Power Safe Mode

2020-06-01 Thread Frank Krauss
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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879176

Title:
  System Hangs after being in Power Safe Mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1879176/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] Re: System Hangs when trying to kill a Window

2020-06-01 Thread Frank Krauss
Dear Sirs,
Please feel free to close out this Bug.
The Solution as mentioned above 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.
Thank you everyone who took the time to look at this problem.
Yours truly,
Frank Krauss

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1877890] Re: System Hangs when trying to kill a Window

2020-06-01 Thread Frank Krauss
Dear Sir,

I wish to thank you for your suggestion about using a different
and older Nucleus.
I didn't understand initially about the difference between the
4.x and 5.x Versions.

After I did research on them, I installed the 4.15.0 release.
It has been running perfectly for the past week so I believe
that is the correct solution to my problems of the System hanging
periodically.

I think that maybe it is because my System was built for me over 10+
years ago.  It probably dosn't support the HWE code of the 5.x Series.

I will close out this bug and also three other bugs which likewise
have no longer shown up.

Thank you again for your excellent suggestion that has cleared up
these serious problems on my Bionic Beaver System.

Yours truly,

Frank Krauss

+

On Tue, 2020-05-12 at 07:10 +, Kai-Heng Feng wrote:
> Does the GA kernel (i.e. 4.15) have this issue?
> 
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] Re: System Hangs when trying to kill a Window

2020-05-19 Thread Frank Krauss
Dear Sir,
I used the workaround from bug 994921 and rebooted the system.
I ran about one hour and the same type of Hangup of the System occurred.
Doing my normal Alt + PrtScrn, Alt + CREISUB, I thus got my system back.
I then ran the "sudo ubuntu-bug .crash" command and created bug # 1879585
Please see that Report for what I was doing at the time of the Hangup.
Any additional information that I can give to you, I will be happy to.
Thank you for your effort in solving this very pesky problem.
Frank Krauss

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879585] [NEW] System Hung when moving Windows around on the Screen

2020-05-19 Thread Frank Krauss
Public bug reported:

Sirs,
I was running on this system after having re-booted it only about an Hour ago.
I had four(4) windows open on the user.
Two were vi sessions.
One was running a Program
and the last one was playing a video using mplayer.
I was simply attempting to move these windows around for better placement on 
the Screen.
I had moved the two VI sessions up higher on the screen and when I attempted to 
move
the Window that was playing the Video it hung up the System.
I could move the Mouse around but it didn't accept any clicks from it or any 
responses
from pressing keys.
When I pressed CTRL + ALT + F1, I was able to get to the Screen that shows all 
of my
Users on it, but it wouldn't allow me to select any of them.
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
In this case, I used the "sudo ubuntu-bug xx.crash" command to create this 
record
as per my instructions in problem # 1877890.
Please see that problem for my reason to create this problem this way.
If there is any information I can supply to help you correct these Hangups,
I would be happy to oblige.
Yours truly,
Frank Krauss

ProblemType: KernelCrash
DistroRelease: Ubuntu 18.04
Package: linux-image-5.3.0-51-generic 5.3.0-51.44~18.04.2
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
Date: Mon May 18 16:58:48 2020
InstallationDate: Installed on 2020-04-20 (29 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-kernelcrash bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879585

Title:
  System Hung when moving Windows around on the Screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1879585/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879201] Re: System Hangs when switching from one User to another

2020-05-17 Thread Frank Krauss
I added to the Report the output of the command "apport-collect 1879201"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879201

Title:
  System Hangs when switching from one User to another

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1879201/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879201] [NEW] System Hangs when switching from one User to another

2020-05-17 Thread Frank Krauss
Public bug reported:

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=
 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=
 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

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug apport-collected bionic dist-upgrade

** Tags added: apport-collected

** Description changed:

  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 dis

[Bug 1879201] ProcCpuinfoMinimal.txt

2020-05-17 Thread Frank Krauss
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1879201/+attachment/5373059/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879201

Title:
  System Hangs when switching from one User to another

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1879201/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879176] ProcCpuinfoMinimal.txt

2020-05-17 Thread Frank Krauss
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1879176/+attachment/5373004/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879176

Title:
  System Hangs after being in Power Safe Mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1879176/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879176] [NEW] System Hangs after being in Power Safe Mode

2020-05-17 Thread Frank Krauss
Public bug reported:

Dear Sirs,
I'm a long term user of Ubuntu.
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.
Yesterdays Hang was different.
This one occurred by the following sequence of events:
1. The System had been idle for a while.
2. The Monitor was blank in Power Save mode.
3. I pressed the Enter key expecting to log onto my User.
4. The entire screen stayed black EXCEPT for the Top of the Screen
   that had the "Activities  Day and time etc" on it.
5. I could move the Mouse around the Screen but I got no response
   from the system when Clicking the Mouse or pressing any Keys.
I used the SysRq - 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:0x78974cb4(%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.
I have enjoyed using Ubutnu for many years but I do need a Stable
environment for my Development work and for my Users satisfaction.
Yours truly,
Frank Krauss
(208)-547-4452
fmfkra...@gmail.com

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 11:14:20 2020
InstallationDate: Installed on 2020-04-20 (26 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=
 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 (26 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=
 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

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug apport-collected bionic dist-upgrade

** Tags added: apport-collected

** Description changed:

  Dear Sirs,
  I'm a long term user of Ubuntu.
  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.
  Yesterdays Hang was different.
  This one occurred by the following sequence of events:
  1. The System had been idle for a while.
  2. The Monitor was blank in Power Save mode.
  3. I pressed the Enter key expecting to log onto my User.
  4. The entire screen stayed black EXCEPT for the Top of the Screen
 that had the "Activities  Day and time etc" on it.
  5. I could move the Mouse around the Screen but I got no response
 from the system when Clicking the Mouse or pressing any Keys.
  I used the SysRq - 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:0x78974cb4(%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.
  I have enjoyed using Ubutnu for many years but I do need a Stable
  environment for my Development work and for my Users satisfaction.
  Yours truly,
  Frank Krauss
  (208)-547-4452
  fmfkra...@gmail.com
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04

[Bug 1879176] Re: System Hangs after being in Power Safe Mode

2020-05-17 Thread Frank Krauss
Sirs,
I added the output of "apport-collect 1879176" to this Report.
Frank Krauss

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879176

Title:
  System Hangs after being in Power Safe Mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1879176/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] Re: System Hangs when trying to kill a Window

2020-05-16 Thread Frank Krauss
Dear Sirs,
Can you please tell me what information is missing in this problem
so that I can supply it to you.
Thank you,
Frank Krauss

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1877890] Re: System Hangs when trying to kill a Window

2020-05-16 Thread Frank Krauss
Hello,
Sorry I didn't respond to your note sooner.
I'm running Kernel 5.3.0-51 which is way later than 4.15.
Frank

++

On Tue, 2020-05-12 at 07:10 +, Kai-Heng Feng wrote:
> Does the GA kernel (i.e. 4.15) have this issue?
> 
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] Re: System Hangs when trying to kill a Window

2020-05-11 Thread Frank Krauss
Dear Sirs,
I just wish you to be aware of one fact with my supplying you with the apport 
information today.
Last night after another Hangup in the same place in mwait_idle, I thought that 
maybe the
problem is something to do with this module.
I came across an option at Boot time called "idle=nomwait"
Thinking that maybe putting this option into the kernel at boot time may fix 
the problem
that's what I did when I had to re-boot yesterday.
So I just want you to be aware that that option was NOT being used during the 
original Hang Up
problems.
I don't know if that effects the information that I just sent you or not but I 
wanted you
to be aware of that.
Frank Krauss

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] WifiSyslog.txt

2020-05-11 Thread Frank Krauss
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1877890/+attachment/5370029/+files/WifiSyslog.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] ProcInterrupts.txt

2020-05-11 Thread Frank Krauss
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1877890/+attachment/5370025/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] Lsusb.txt

2020-05-11 Thread Frank Krauss
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1877890/+attachment/5370022/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] Re: System Hangs when trying to kill a Window

2020-05-11 Thread Frank Krauss
apport information

** Tags added: apport-collected

** Description changed:

  Dear Sirs,
  I'm a long term user of Ubuntu,
  I run a Client/Server system that my clients expect to be very stable.
  I ran under Trust Tahr for a long while with great success and no Hangups at 
all.
  I recently upgraded to Bionic Beaver and I find that I have a number of
  Hangups.
  They seem to occur mostly when switching between different users.
  The latest one that occurred last night that I want to show you here was
  caused by something else.
  I was watching a video from Youtube under Firefox.
  At the end of it I clicked the upper right hand button of the window
  to kill the screen. At this point the system froze on me.
  I could move the mouse around but none of the keys worked.
  I used the SysrRq - Magic Key combination to get the following information
  ALT + PrtScrn, ALT + CREISUB
  The system re-booted and gave me the following files in /var/crash
4096 May  9 23:38 202005092338
 349 May 10 11:01 kexec_cmd
   25387 May  9 23:39 linux-image-5.3.0-51-generic-202005092338.crash
  
   69696 May  9 23:38 dmesg.202005092338
   291014103 May  9 23:38 dump.202005092338
  
  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:0x72774cb4(%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 fairly computer literate and so I can follow any directions that
  you want to give to me.
  
  I have enjoyed using Ubutnu for many years but I do need a Stable
  environment for my Development work and for my users satisfaction.
  
  Yours truly,
  Frank Krauss
  
  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 10 13:19:54 2020
  InstallationDate: Installed on 2020-04-20 (19 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=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.14
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  fkrauss1808 F pulseaudio
+  /dev/snd/controlC0:  fkrauss1808 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2020-04-20 (20 days ago)
+ InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
+ IwConfig:
+  ens2  no wireless extensions.
+  
+  lono wireless extensions.
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 nouveaudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 
zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait
+ ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-51-generic N/A
+  linux-backports-modules-5.3.0-51-generic  N/A
+  linux-firmware1.173.17
+ RfKill:
+  
+ Tags:  bionic
+ 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
+ dmi.bios.date: 02/08/2010
+ dmi.bios.vendor: Intel Corp.
+ dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: DG31PR
+ dmi.board.vendor: Intel Corporation
+ dmi.board.version: AAD97573-306
+ dmi.chassis.type: 3
+ dmi.modalias: 
dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr:

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1877890/+attachment/5370018/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubun

[Bug 1877890] CRDA.txt

2020-05-11 Thread Frank Krauss
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1877890/+attachment/5370019/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] PulseList.txt

2020-05-11 Thread Frank Krauss
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1877890/+attachment/5370027/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] UdevDb.txt

2020-05-11 Thread Frank Krauss
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1877890/+attachment/5370028/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] ProcCpuinfoMinimal.txt

2020-05-11 Thread Frank Krauss
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1877890/+attachment/5370024/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] CurrentDmesg.txt

2020-05-11 Thread Frank Krauss
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1877890/+attachment/5370020/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] Lspci.txt

2020-05-11 Thread Frank Krauss
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1877890/+attachment/5370021/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] ProcModules.txt

2020-05-11 Thread Frank Krauss
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1877890/+attachment/5370026/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] ProcCpuinfo.txt

2020-05-11 Thread Frank Krauss
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1877890/+attachment/5370023/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877890] [NEW] System Hangs when trying to kill a Window

2020-05-10 Thread Frank Krauss
Public bug reported:

Dear Sirs,
I'm a long term user of Ubuntu,
I run a Client/Server system that my clients expect to be very stable.
I ran under Trust Tahr for a long while with great success and no Hangups at 
all.
I recently upgraded to Bionic Beaver and I find that I have a number of
Hangups.
They seem to occur mostly when switching between different users.
The latest one that occurred last night that I want to show you here was
caused by something else.
I was watching a video from Youtube under Firefox.
At the end of it I clicked the upper right hand button of the window
to kill the screen. At this point the system froze on me.
I could move the mouse around but none of the keys worked.
I used the SysrRq - Magic Key combination to get the following information
ALT + PrtScrn, ALT + CREISUB
The system re-booted and gave me the following files in /var/crash
  4096 May  9 23:38 202005092338
   349 May 10 11:01 kexec_cmd
 25387 May  9 23:39 linux-image-5.3.0-51-generic-202005092338.crash

 69696 May  9 23:38 dmesg.202005092338
 291014103 May  9 23:38 dump.202005092338

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:0x72774cb4(%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 fairly computer literate and so I can follow any directions that
you want to give to me.

I have enjoyed using Ubutnu for many years but I do need a Stable
environment for my Development work and for my users satisfaction.

Yours truly,
Frank Krauss

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 10 13:19:54 2020
InstallationDate: Installed on 2020-04-20 (19 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=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890

Title:
  System Hangs when trying to kill a Window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1877890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 979960] [NEW] totem crashed with SIGSEGV in g_object_notify()

2012-04-12 Thread Frank Krauss
Public bug reported:

Don't have any additional information

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: totem 2.30.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-40.87-generic 2.6.32.57+drm33.23
Uname: Linux 2.6.32-40-generic i686
Architecture: i386
Date: Wed Apr 11 22:37:11 2012
Disassembly: = 0x0:Cannot access memory at address 0x0
ExecutablePath: /usr/bin/totem
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
ProcCmdline: totem 
/media/1a7128d2-7d53-40ff-9fcb-27765e7c7cc5/Roy.Orbison.and.Friends.mp4
ProcCwd: /home/fkrauss
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? ()
 g_object_notify () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/gstreamer-0.10/libgstplaybin.so
 g_cclosure_marshal_VOID__PARAM ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: totem crashed with SIGSEGV in g_object_notify()
UserGroups: adm admin audio cdrom dialout dip lpadmin plugdev sambashare video

** Affects: totem (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash i386 lucid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979960

Title:
  totem crashed with SIGSEGV in g_object_notify()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/979960/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 979960] Re: totem crashed with SIGSEGV in g_object_notify()

2012-04-12 Thread Frank Krauss
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979960

Title:
  totem crashed with SIGSEGV in g_object_notify()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/979960/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs