Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop (Bug #911760)

To: 911760@bugs.debian.org, 911760-submitter@bugs.debian.org
Subject: Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop (Bug #911760)
From: Bernhard Übelacker <bernhardu@mailbox.org>
Date: Wed, 24 Oct 2018 21:53:21 +0200
Message-id: <[🔎] 6a7b7361-28fd-3072-bde7-a617e91f9348@mailbox.org>
Reply-to: Bernhard Übelacker <bernhardu@mailbox.org>, 911760@bugs.debian.org
In-reply-to: <[🔎] 154038712775.3566.11107340081319327020.reportbug@hellspawn>
References: <[🔎] 154038712775.3566.11107340081319327020.reportbug@hellspawn> <[🔎] 154038712775.3566.11107340081319327020.reportbug@hellspawn> <[🔎] 154038712775.3566.11107340081319327020.reportbug@hellspawn>

Hello Alex Andreotti,
just tried to reproduce this issue but did not happen inside my unstable amd64 qemu VM.

Probably you can install an core dump collector like systemd-coredump?

Then you could see the stack where the crash happened by:
  coredumpctl gdb list
  coredumpctl gdb <PID>

And even better would be if you could add the debug symbol repository
described in [1] and install e.g. lightdm-gtk-greeter-dbgsym plus
maybe more dbgsym packages for the shared objects shown in the stack.

Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace

Reply to:

Follow-Ups:
- Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop (Bug #911760)
  - From: Alex Andreotti <alex.andreotti@gmail.com>

References:
- Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop
  - From: Alex Andreotti <alex.andreotti@gmail.com>

Prev by Date: Bug#911760: lightdm: more info
Next by Date: Bug#911760: Same issue here - disappeared in the meanwhile
Previous by thread: Bug#911760: lightdm: more info
Next by thread: Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop (Bug #911760)
Index(es):
- Date
- Thread