xubuntu 20.04 'live' qa-test; suspend, resume but system froze on waking

[Chris Guiver]

Xubuntu daily test (20.04) on
dell vostro 430 (i7-870, 8gb, nvidia geforce gt 6600 gt)
test went well, then I suspended system, waited, on resume (keystroke) system appeared to stop with mucked-up but mostly-recognizable display (https://photos.app.goo.gl/2kSU5SubdbkdpFUcA)

I was unable to use any keyboard input to switch to terminal, or gain any clues (sorry keyboard didn't have sysrq key to see if kernel was up).

I rebooted the system which is when `ubuntu-bug linux` was ran. After this bug was submitted I suspended system, waited & it resumed correctly. I suspended it again, waited & it resumed normally; so the issue doesn't occur all the time.

Because CTRL+ALT+T wasn't working (different issue; https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1827459), nor menu items having icons etc, I `xfsettingsd --replace` to fix that issue & suspended again.. This time the system didn't resume reliably. This time however it was not as I'm describing above, as the screen was correctly drawn. The mouse-pointer was visible but static, then appeared to move (following my movements) before disappearing, redrawn but static again .. IF the system was 'up', it'd become super slow; and I eventually turned box off. I'll retest on requests (too tried now)

photo of screen on resume : https://photos.app.goo.gl/2kSU5SubdbkdpFUcA

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-14-generic 5.4.0-14.17
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: xubuntu 4057 F.... pulseaudio
CasperVersion: 1.441
CurrentDesktop: XFCE
Date: Thu Mar 5 10:35:57 2020
IwConfig:
 enp2s0 no wireless extensions.

 lo no wireless extensions.
LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200305)
MachineType: Dell Inc. Vostro 430
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-14-generic N/A
 linux-backports-modules-5.4.0-14-generic N/A
 linux-firmware 1.186
RfKill:

SourcePackage: linux-5.4
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/13/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 054KM3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.family: 0
dmi.product.name: Vostro 430
dmi.product.sku: 0
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1866172

[Chris Guiver (guiverc)]

`lshw -C video` on subsequent reboots (2x) showed 'driver=nouveau'
I hadn't looked before system had frozen sorry.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.