This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1877890

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  System Hangs when trying to kill a Window

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to