[Bug 1900584] Re: Regression: suspend/wake-up no longer working properly

2020-12-11 Thread craigleat
The crux of the problem is an API mismatch between the kernel module and the nvidia driver. The problem arises in the normal course of applying updates and not from user tinkering (see #1). $ uname -a Linux OptiPlex-380 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 x86_64 x86_64

[Bug 1900584] Re: Regression: suspend/wake-up no longer working properly

2020-12-11 Thread craigleat
$ sudo apt update ... $ sudo apt install nvidia-drivers-455 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package nvidia-drivers-455 $ sudo apt install nvidia-driver-455 Reading package lists... Done Building dependency tree

[Bug 1900584] Re: Regression: suspend/wake-up no longer working properly

2020-12-11 Thread craigleat
>"it looks like the user installed the driver through >the nvidia installer, and then used our packages. >The perfect recipe for disaster." Thanks for continuing to look into this. I don't believe I have an nvidia installer, only nvidia settings. I can't test with a live disk, because the nvidia

[Bug 1900584] Re: Regression: suspend/wake-up no longer working properly

2020-12-09 Thread craigleat
The display wakes up correctly with 5.4.0-57 and the nouveau driver. The display wakes up correctly with 5.4.0-47 and the nvidia driver. It doesn't seem possible to fix the API mismatch with 5.4.0-57 and the nvidia driver. linux-generic pulled in the 5.4.0-57 kernel and the 450 nvidia server,

[Bug 1900584] Re: Regression: suspend/wake-up no longer working properly

2020-12-09 Thread craigleat
>From the Xorg log: [10.479] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [10.479] (EE) NVIDIA: system's kernel log for additional error messages and [10.479] (EE) NVIDIA: consult the NVIDIA README for details. [10.479] (EE) NVIDIA: Failed

[Bug 1900584] Re: Regression: suspend/wake-up no longer working properly

2020-12-09 Thread craigleat
`journalctl -b -1 -k` seems to miss the last boot. I did `journalctl -b -k` instead. See log attached. ** Attachment added: "journalctl -b -k.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900584/+attachment/5442276/+files/journalctl%20-b%20-k.txt -- You received this bug

Re: [Bug 1900584] Re: Regression: suspend/wake-up no longer working properly

2020-12-08 Thread craigleat
I tested with 5.4.0-57.63 (that's the version installed by the linux-generic meta package). Still not working for me. On Tue, 8 Dec 2020 at 03:41, Kai-Heng Feng <1900...@bugs.launchpad.net> wrote: > Can you please test 5.4.0.57.60 from -proposed? > > ** Changed in: linux (Ubuntu) >

[Bug 1900584] [NEW] Regression: suspend/wake-up no longer working properly

2020-10-19 Thread craigleat
Public bug reported: With kernel 5.4.0-47.51, suspend (and resuming thereafter) works flawlessly. With 5.4.0-48.52 and later versions, the display refuses to wake up after a suspend. Display adaptor: Nvidia driver version: 440.100 Screens: 1 GPU: GeForce GT 710 ProblemType: Bug DistroRelease:

[Bug 1452849] Re: initctl cannot find Upstart

2016-04-11 Thread craigleat
*** This bug is a duplicate of bug 1447099 *** https://bugs.launchpad.net/bugs/1447099 On my system (15.10) unity-greeter depends on upstart -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452849