[Ubuntu-x-swat] [Bug 2034995] Re: Xwayland crashed with SIGABRT in __libc_start_call_main() when blank/lock screen

2023-09-11 Thread Martin Randau
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 Hehe, ok. Well, the problem I'm experiencing is very reproducible and specific: wayland, no external monitor --> lock screen or screen blank --> crash and return to gdm. If in xorg or in wayland with an

[Ubuntu-x-swat] [Bug 2034995] Re: Xwayland crashed with SIGABRT in __libc_start_call_main() when blank/lock screen

2023-09-11 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 There certainly doesn't appear to be enough information here to prove it is or isn't bug 1751508. So de-duplicating this wouldn't really help. It looks like the apport bot removed the file attachments that

[Ubuntu-x-swat] [Bug 2034995] Re: Xwayland crashed with SIGABRT in __libc_start_call_main() when blank/lock screen

2023-09-09 Thread Martin Randau
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 I don't think this is a duplicate. Problem is only present when NOT connected to an external monitor. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 2034995] Re: Xwayland crashed with SIGABRT in __libc_start_call_main() when blank/lock screen

2023-09-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1751508, so is being marked as such.