https://bugs.kde.org/show_bug.cgi?id=470469
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
CC| |n...@kde.org
Status|REPORTED |NEEDSINFO
Component|general |wayland-generic
Summary|Unable to start wayland |Unable to start wayland
|session NVIDIA 1050 Ti |session NVIDIA 1050 Ti
|triple monitor setup |triple monitor setup due to
| |kwin_wayland crashing
--- Comment #2 from Nate Graham <n...@kde.org> ---
Thanks for the logging. Unfortunately the backtrace is mangled and
unsymbolicated, which complicates the situation. in a terminal window, can you
run `coredumpctl gdb 633`, let it collect debug symbols when it asks, then type
"bt" when you get a prompt? Hit C to continue paging if needed, then
copy-and-paste that backtrace here.
See also
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Thanks again!
--
You are receiving this mail because:
You are watching all bug changes.
