[Ubuntu-x-swat] [Bug 2034995] Re: Xwayland crashed with SIGABRT in __libc_start_call_main() when blank/lock screen
*** 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 external monitor --> everything works. There must be something I can do to produce some logs or get closer to the problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2034995 Title: Xwayland crashed with SIGABRT in __libc_start_call_main() when blank/lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2034995/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2034995] Re: Xwayland crashed with SIGABRT in __libc_start_call_main() when blank/lock screen
*** 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 we would need to make the judgement: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2034995/+activity So we're left with only one option; to assume the bot was right. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2034995 Title: Xwayland crashed with SIGABRT in __libc_start_call_main() when blank/lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2034995/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2034995] Re: Xwayland crashed with SIGABRT in __libc_start_call_main() when blank/lock screen
*** 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 xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2034995 Title: Xwayland crashed with SIGABRT in __libc_start_call_main() when blank/lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2034995/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2034995] Re: Xwayland crashed with SIGABRT in __libc_start_call_main() when blank/lock screen
*** 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. Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Please continue to report any other bugs you may
find.
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/2034995/+attachment/5699547/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/2034995/+attachment/5699549/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/2034995/+attachment/5699553/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/2034995/+attachment/5699554/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/2034995/+attachment/5699555/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/2034995/+attachment/5699556/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/2034995/+attachment/5699557/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of bug 1751508
Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("Couldn't add screen\n") from InitOutput()
** Information type changed from Private to Public
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/2034995
Title:
Xwayland crashed with SIGABRT in __libc_start_call_main() when
blank/lock screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2034995/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
