[Ubuntu-x-swat] [Bug 1775593] [NEW] X server crashes with SIGBUS when resuming from suspend

Public bug reported: Every night I suspend my laptop and resume it in the morning. At least once a week, the X server crashes with SIGBUS when resuming from suspend. I scoured systemd journals and all logs under /var/log, and this was the only suspicious message I found: [ 59358.134] (EE)

[Ubuntu-x-swat] [Bug 1775593] Re: X server crashes with SIGBUS when resuming from suspend

Thanks for the swift feedback. I had tried to run: ubuntu-bug /var/crash/FILE.crash but it complained of lack of permission. I wasn't aware of the workaround of bug #994921. As soon as I get another crash, I'll follow your instructions. -- You received this bug notification because you are a

[Ubuntu-x-swat] [Bug 1775593] Re: X server crashes with SIGBUS when resuming from suspend

Dummy me, forgive me: I still had the crash file around, it was just a question of giving read permission to everyone (since it was only readable by root and group whoopsie), and running ubuntu-bug over it. So, after changing problem_types in /etc/apport/crashdb.conf to: 'problem_types':

[Ubuntu-x-swat] [Bug 1775593] Re: X server crashes with SIGBUS when resuming from suspend

*** This bug is a duplicate of bug 1753012 *** https://bugs.launchpad.net/bugs/1753012 I've just got an automated email saying that my bug #1775790 is a duplicate of bug #1753012, but if I try to open it, I get a not found page, I suppose because these reports are private to the subscribers.

[Ubuntu-x-swat] [Bug 1775593] Re: X server crashes with SIGBUS when resuming from suspend

*** This bug is a duplicate of bug 1753012 *** https://bugs.launchpad.net/bugs/1753012 As I started to suspect of the kernel i915 modesetting driver, yesterday I put a workaround in place, not sure if it will have any effect. I created /etc/X11/xorg.conf.d/10-intel.conf: Section "Device"

[Ubuntu-x-swat] [Bug 1298578] Re: Brightness is low after resume from suspend, can't be increased

This bug is still present in Xubuntu 18.04. Workaround https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1298578/comments/7 does restore maximum brightness, but not the actual brightness level before suspending. -- You received this bug notification because you are a

[Ubuntu-x-swat] [Bug 1775593] Re: X server crashes with SIGBUS when resuming from suspend

*** This bug is a duplicate of bug 1753012 *** https://bugs.launchpad.net/bugs/1753012 @Alan, oh, you're description of the bug is far more accurate than mine: it's precisely what I experienced. I'm running vanilla kernel 4.15.0-23-generic, without your fix, so I wonder why forcing the intel

[Ubuntu-x-swat] [Bug 1753012] Re: Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe() from InitOutput() from dix_main() from __libc_start_main()

A hypothesis was discussed in bug #1753012 that the root cause of this bug was in the kernel, specifically in blk-core.c. The patch was finally merged in kernel version 4.15.0-31-generic. I'm running on 4.15.0-32-generic but the bug is still happening: 1. Xorg starts to become unresponsive: it

[Ubuntu-x-swat] [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

I'm running Xubuntu 18.0.03, which hasn't reached end-of-life, and this bug is still present. It was introduced when I upgraded to kernel 5.0 with xorg 1.20.4-1ubuntu3~18.04.1. It can be circumvented using either of 2 methods: 1. Uninstalling light-locker and installing xscreensaver or 2. As

[Ubuntu-x-swat] [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

Ops, apologies for the typo, I'm running Xubuntu 18.04.03 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up