LXQt Freeze

[robb990099]

/usr/lib/gdm3/gdm-x-session[2681]: (EE) open /dev/fb0: Permission denied
/usr/lib/gdm3/gdm-x-session[2681]: (EE) modeset(G0): glamor initialization failed

Description: Ubuntu 20.04.3 LTS
Release: 20.04

gdm3:
  Installed: 3.36.3-0ubuntu0.20.04.4
  Candidate: 3.36.3-0ubuntu0.20.04.4
  Version table:
 *** 3.36.3-0ubuntu0.20.04.4 500
        500 http://au.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     3.36.3-0ubuntu0.20.04.2 500
        500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
     3.34.1-1ubuntu1 500
        500 http://au.archive.ubuntu.com/ubuntu focal/main amd64 Packages

xorg:
  Installed: 1:7.7+19ubuntu14
  Candidate: 1:7.7+19ubuntu14
  Version table:
 *** 1:7.7+19ubuntu14 500
        500 http://au.archive.ubuntu.com/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status

3) What you expected to happen - continue to respond to keyboard and mouse
4) What happened instead - no response from keyboard or mouse

TIA

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
Uname: Linux 5.4.0-89-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: LXQt
Date: Sat Nov 20 23:31:52 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Once a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12bd]
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12bd]
InstallationDate: Installed on 2021-01-07 (317 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046d:c542 Logitech, Inc. Wireless Receiver
 Bus 001 Device 004: ID 8087:0026 Intel Corp.
 Bus 001 Device 003: ID 5986:211b Acer, Inc HD Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Micro-Star International Co., Ltd. GF63 Thin 10SCXR
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-89-generic root=UUID=3405df65-a898-4ac8-86a0-474b4da9b724 ro rootflags=subvol=@ quiet splash crashkernel=512M-:192M vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16R4IMS.108
dmi.board.asset.tag: Default string
dmi.board.name: MS-16R4
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16R4IMS.108:bd09/30/2020:svnMicro-StarInternationalCo.,Ltd.:pnGF63Thin10SCXR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16R4:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
dmi.product.family: GF
dmi.product.name: GF63 Thin 10SCXR
dmi.product.sku: 16R4.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.4
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.4
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[robb990099 (rebrown)]

boot.log added

Thanks for your work!

[Daniel van Vugt (vanvugt)]

Thanks for the bug report.

If you have graphics problems then the most likely cause is the 'nouveau' driver you are using. Please open the 'Additional Drivers' app and install the latest Nvidia driver. Then reboot.

If the problem continues after that then please run:

  lspci -kv > lspci.txt

and attach the resulting text file here.

[robb990099 (rebrown)]

Thanks.
Have installed nvidia-driver-470 and will monitor.

Cheers

[Launchpad Janitor (janitor)]

[Expired for Ubuntu because there has been no activity for 60 days.]

[robb990099 (rebrown)]

New freeze today after a couple of months on nvidia-driver-470.

Please advise of further info required.

[Daniel van Vugt (vanvugt)]

Thanks. Please attach the full system log of the freeze, not truncated. If it's the previous boot then:

  journalctl -b-1 > syslog.txt

or if it was the boot before that then:

  journalctl -b-2 > syslog.txt

Please also check for crashes by following these instructions:

  https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[robb990099 (rebrown)]

Thanks.
syslog attached. but it seems to end too early(?).

ubuntu-bug YOURFILE.crash ran but it generated no new bug ID so how will it be linked to this current bug report? Filemname was /var/crash/_usr_bin_qlipper.1000.crash

[Daniel van Vugt (vanvugt)]

Thanks again.

The log file in comment #9 appears to be older than where the log in comment #6 ended. So comment #9 is from the wrong boot. Try using a different number in the journalctl command.

Also _usr_bin_qlipper.1000.crash is probably not relevant here. We're only interested in gnome-shell or Xorg crashes really.

[robb990099 (rebrown)]

 journalctl -b-1 > syslog2202-02-08A.txt ends at Feb 08 12:47:48
 journalctl -b-2 > syslog2202-02-08C.txt starts at Feb 08 12:50:17 and ends at Feb 08 16:11:54

I thought the crash happened before 12:50:17 and the start of the reboot was a t 12:50:17 so the freeze should have been in the syslog2202-02-08A.txt file

Thanks

[Daniel van Vugt (vanvugt)]

I can't see any crashes around the time before 12:50:17 but also if you're using LXQt then I wouldn't know what programs to look for...

I suggest repeating the steps in https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment in case the freeze is caused by something crashing. Failing that, please attach more syslogs from future crashes in case the cause of the issue becomes clearer.

[robb990099 (rebrown)]

Thanks Daniel. Your comments and help are much appreciated. The attachments in #1 are all pre-nvidia when using Nouveau so not likely to be relevant now. I will try and capture some new logs in case of another freeze.

[Daniel van Vugt (vanvugt)]

Preferably:

1. Look in /var/crash for crash files and if found run:

     ubuntu-bug YOURFILE.crash

   Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID
   where ID is the content of file /var/lib/whoopsie/whoopsie-id on
   the machine. Do you find any links to recent problems on that page?
   If so then please send the links to us.

[robb990099 (rebrown)]

New crash today. Log attached.

cat /var/crash/kexec_cmd
/sbin/kexec -p -s --command-line="BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-89-generic root=UUID=3405df65-a898-4ac8-86a0-474b4da9b724 ro rootflags=subvol=@ quiet splash vt.handoff=7 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

No file created *.crash

No new file posted at https://errors.ubuntu.com/user/ID

[Daniel van Vugt (vanvugt)]

What is the content of the file: /var/lib/whoopsie/whoopsie-id ?

[robb990099 (rebrown)]

Thanks Daniel.
cat /var/lib/whoopsie/whoopsie-id
e85201b46e9f1cd63274a63c5926fbb947a65e98887bdffa63fc5cf3e1a51379df0326aa35c54b472f5bb7443a49964f84a569d7fb5efb75d5c48e5148695c87root@robert-msiLaptop:/home/rbrown#

[Daniel van Vugt (vanvugt)]

Thanks. It appears there have been no relevant crash reports from that machine:

https://errors.ubuntu.com/user/e85201b46e9f1cd63274a63c5926fbb947a65e98887bdffa63fc5cf3e1a51379df0326aa35c54b472f5bb7443a49964f84a569d7fb5efb75d5c48e5148695c87

Next time a freeze happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

[robb990099 (rebrown)]

Hi
I didn't have to wait long.
This freeze happened today after 2x Foxit Reader hung when trying to edit a pdf document.

The cascade of lines like this"

/usr/lib/gdm3/gdm-x-session[4938]: (II) modeset(0): EDID vendor "BOE", prod id 2391

is what I typically see when the freeze occurs. Previously not related to Foxit Reader problems.

Thanks!

[Daniel van Vugt (vanvugt)]

I still can't see anything crashing or going obviously wrong to explain a freeze. Maybe try contacting the developers: https://github.com/lxqt/lxqt/wiki/Contact

[robb990099 (rebrown)]

Two more freezes, yesterday and today.
See attached. journalctl -b-1 > syslog2022-03-07A.txt

lxqt people offer no help saying they don't control the display.

Nothing new in crash files
ls -la /var/crash/
total 1568
drwxrwsrwt 1 root whoopsie 92 Mar 8 13:50 .
drwxr-xr-x 1 root root 154 Jul 18 2017 ..
-rw-r--r-- 1 root whoopsie 0 Mar 8 13:50 kdump_lock
-rw-r--r-- 1 root whoopsie 336 Mar 8 13:50 kexec_cmd
-rw-r----- 1 rbrown whoopsie 1597620 Mar 2 09:10 _usr_bin_qlipper.1000.crash

[robb990099 (rebrown)]

Today's syslog prev boot
journalctl -b-1 > syslog2022-03-08.txt

[robb990099 (rebrown)]

Crash report uploaded.
FF version 97.0.2 causing lxpanel to crash now following recent updates.

[Paul White (paulw2u)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

https://lubuntu.me/lubuntu-20-04-lts-end-of-life-and-current-support-statuses/

I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of *Lubuntu* then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time.

[Launchpad Janitor (janitor)]

[Expired for Ubuntu because there has been no activity for 60 days.]