I'm not going to go so far as to say the bug itself is fixed, but upon
upgrading to Bionic it is no longer using Wayland by default so...
no longer a bug that affects me at least. I'd suggest others try
upgrading and switching to the new default window manager and backend.
--
You received this b
I'm still seeing crashes under the exact same conditions as since
October. When I do ubuntu-bug on the crash file it directs me here, so I
think this bug may still be getting triggered for me at least.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Crash still occurs every time I turn my monitor back on, as has been the
case since October.
--
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/1731911
Title:
Xwayland crashed with SIGABRT in
I don't know how to tell if it's definitely the same, but for me the
crash occurs not when the monitor is turned off but rather when it is
turned back on. The actual time stamp of the crash isn't until after
turning it on.
--
You received this bug notification because you are a member of Ubuntu-X
I previously had bug https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1724557 which causes the desktop to hard crash when the
monitor is turned on, related to gnome-shell and mutter.
That bug hasn't reported anything to /var/crash lately, but the behavior
has stayed the same for me. If
5 matches
Mail list logo