Created attachment 159360 [details] results of `XDG_SESSION_TYPE=wayland dbus-run-session kwin_wayland --exit-with-session=konsole SUMMARY I am unable to start plasma with wayland using tty or sddm, sddm loads a black screen for a few seconds and quits out. From cli it fails, I have attached both the coredump from journalctl and a log from running `XDG_SESSION_TYPE=wayland dbus-run-session kwin_wayland --exit-with-session=konsole`, which is not able to start anything either. Not even an empty window. STEPS TO REPRODUCE 1. Load newest kernel and nvidia proprietary drivers on triple monitor setup 2. Try to start KDE wayland in any fashion 3. Fail OBSERVED RESULT Black screens and errors, nothing that can continually execute by itself EXPECTED RESULT Start a wayland session, or at least a konsole session SOFTWARE/OS VERSIONS Archlinux/KDE Plasma: 6.3.4-arch2-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Nvidia 1050 Ti with all ports taken is being used. X11 works without error. All correct wayland packages installed (i.e. egl-wayland, xorg-wayland, wayland-protocols, wayland-utils, etc. and nvidia_drm.modeset=1 enabled.
Created attachment 159361 [details] core dumps from sddm start attempts
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!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Comment on attachment 159361 [details] core dumps from sddm start attempts On further inspection the core dumps were unrelated and I am not getting them just from starting wayland now. But however, it still does not do anything more than black screen when I try to start a wayland session in any form.
(In reply to Bug Janitor Service from comment #3) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! I finally found the wall blocking me from a kwin_wayland coredump. entering c yields "The program is not being run." But what I have now from gdb is ``` #0 0x00007faecea9f26c in () at /usr/lib/libc.so.6 #1 0x00007faecea4fa08 in raise () at /usr/lib/libc.so.6 #2 0x00007faecea38538 in abort () at /usr/lib/libc.so.6 #3 0x00007faed0b8afee in () at /usr/lib/libepoxy.so.0 #4 0x00007faed0b8b02e in () at /usr/lib/libepoxy.so.0 #5 0x00007faed0b8c46f in () at /usr/lib/libepoxy.so.0 #6 0x00007faed0b8eee7 in () at /usr/lib/libepoxy.so.0 #7 0x00007faed0b8f8a8 in () at /usr/lib/libepoxy.so.0 #8 0x00007faed0b346a5 in () at /usr/lib/libepoxy.so.0 #9 0x00007faed0b57b2f in () at /usr/lib/libepoxy.so.0 #10 0x00007faed18d0864 in KWin::GLPlatform::detect(KWin::OpenGLPlatformInterface) () at /usr/lib/libkwinglutils.so.14 #11 0x00007faed16338ae in KWin::AbstractEglBackend::initKWinGL() () at /usr/lib/libkwin.so.5 #12 0x00007faed1576d8f in () at /usr/lib/libkwin.so.5 #13 0x00007faed13beff6 in KWin::Compositor::attemptOpenGLCompositing() () at /usr/lib/libkwin.so.5 #14 0x00007faed13bfb64 in () at /usr/lib/libkwin.so.5 #15 0x00007faed13c14c5 in KWin::WaylandCompositor::start() () at /usr/lib/libkwin.so.5 #16 0x00007faecfac31e4 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #17 0x00007faecf17893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x00007faecfa9b778 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x00007faecfaa06db in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #20 0x00007faecfae9ee7 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #21 0x000056432eede502 in () #22 0x00007faecfa9a484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #23 0x00007faecfa9b923 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #24 0x000056432edfa2fb in () #25 0x00007faecea39850 in () at /usr/lib/libc.so.6 #26 0x00007faecea3990a in __libc_start_main () at /usr/lib/libc.so.6 #27 0x000056432edfbed5 in () ``` And I will attach my new log file from journalctl with the date in the filename.
Created attachment 159895 [details] Log resulting from wayland failing a few times from startup from sddm
I was finally able to reach the plasma desktop with wayland using KWIN_COMPOSE=Q in my /etc/environment, HOWEVER it is constantly running at 50% usage and incredibly buggy/studdery, rendering it basically unusable.
I have since moved my installation to a new drive and in the process had the opportunity to try with a stock kde install with no differences in behavior
Can you install debuginfod and provide new backtraces that include debug symbols? Check Arch Wiki how to install debuginfod Can you also attach the output of `eglinfo` command to this bug report please?
.
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!