SUMMARY Fresh install of KDEneon-User (Download Oct. 27, 2020) works fine with X11 but crashes frequently under wayland. The applications still are working. Killall and restart of kwin resolves for some time. STEPS TO REPRODUCE 1. just wait, it happens frequently sometimes after minutes, sometime after zwo hours. OBSERVED RESULT /var/log/syslog shows the following logs (last line shows the timestamp indicated also by the clock in the menu bar: Oct 6 12:20:08 surface-pro plasmashell[359283]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Oct 6 12:20:12 surface-pro plasmashell[359283]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:285:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... } Oct 6 12:21:29 surface-pro plasmashell[359283]: message repeated 2 times: [ file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:285:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }] I am documenting the crashes and the outputs of the syslog and the above line repeats frequently. Also the fact, that it coincidents with the stop of the menu-bar watch points to these lines. I could not find any special combination with a specific application and/or action. Similar behaviour came up with Manjaro and tumbleweed installation (but I do not have logs of these) when I was searching for a stable installation. KDEneon seems to be the most stable one however. Willing to make further experiments in order to resolve this issue. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDEneon 5.19 / 20.04 (focal) (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74 Qt Version: 5.15.0 ADDITIONAL INFORMATION Kernel: 5.8.10-surface additional software: libreoffice, wine, gimp, xsane, kate, kubuntu-restricted-extras, syncthing, firejail, mpv, easytag, bleachbit, net-tools, nmap, fns-common, openssh-server, partitionmanager, gparted, cups with driver, pdafarranger, mc, mesa-utils, kcalk, google-earth, flameshot, timeshift, brave-browser, yED, mysql-workbench in addition some applikations as AppImages I work in a multi-screen environment with the following monitors: - surface-pro 4 screen (2736x1824) scaling 125% - BenQ EW327OU on DP-3 screen (3830x2160) scaling 100% - BenQ GW2265 on DP-4 screen (1920x1080) scaling 100% Compositor: OpenGL 3.1 and OpenGL 2.0
Can you attach the crash log? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
> The applications still are working. Killall and restart of kwin resolves for some time. kwin can't be restarted on wayland at the moment. Please provide the output of `qdbus org.kde.KWin /KWin supportInformation` along the backtrace.
unfortunately I can not find kdelib5-dbg on my system: sudo apt search kdelibs5-dbg kde5libs-dbg kdelib5-dbg kde5lib-dbg Sortierung... Fertig Volltextsuche... Fertig I have the User-version not the Developer version installed. Which packages or ppa's do I have to install in order to get access to the debugging packages? No crash-Dialog appears. Only one of the screens turns to black/white and the kwin-menu bars are not responding anymore. The output of gdb does not give me further information either: gdb kwin GNU gdb (Ubuntu 9.1-0ubuntu1) 9.1 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from kwin... (No debugging symbols found in kwin) (gdb) thread apply all backtrace (gdb) For the restart of kwin I use the following (hotkey with script) killall plasmashell plasmashell & After this the system is responsible again, No (other) application is affected.
(In reply to Peter L. Steger from comment #3) > unfortunately I can not find kdelib5-dbg on my system: > > sudo apt search kdelibs5-dbg kde5libs-dbg kdelib5-dbg kde5lib-dbg > Sortierung... Fertig > Volltextsuche... Fertig > > I have the User-version not the Developer version installed. Which packages > or ppa's do I have to install in order to get access to the debugging > packages? I believe the debug symbols are in the normal repository, the are postfixed by -dbgsym for neon or ubuntu. You probably want to install kwin-wayland-dbgsym , kwin-common-dbgsym or plasma-desktop-dbgsym > > No crash-Dialog appears. Only one of the screens turns to black/white and > the kwin-menu bars are not responding anymore. > > The output of gdb does not give me further information either: > > gdb kwin > GNU gdb (Ubuntu 9.1-0ubuntu1) 9.1 > Copyright (C) 2020 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > Type "show copying" and "show warranty" for details. > This GDB was configured as "x86_64-linux-gnu". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>. > Find the GDB manual and other documentation resources online at: > <http://www.gnu.org/software/gdb/documentation/>. > > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from kwin... > (No debugging symbols found in kwin) > (gdb) thread apply all backtrace > (gdb) Here you don't nothing. To use gdb you'd want next to launch the program using "r" command (for run). But in wayland you can't debug kwin_wayland from within the session or you lose ALL keyboard input and will be forced a hard reboot. > > For the restart of kwin I use the following (hotkey with script) > > killall plasmashell > plasmashell & > > After this the system is responsible again, No (other) application is > affected. The process here does not affect kwin, plasmashell is an independent program, handling the session UI, taskbar... For wayland kwin program is kwin_wayland. So it seems to me your bug relates to plasmashell. You might want to reproduce your crash running beforehand : sudo gdb -pid `pidof plasmashell` # to attach gdb to the running plasmashell process # then in the gdb console type "c" (for continue) and hit enter, this might take a few seconds... The next time plasmashell crashes you will get a back trace in the console.
installed the packages, reboot and started the debugging with the command you provided and got the following results (incl. after entering 'c' + 'RET': sudo gdb -pid `pidof plasmashell` GNU gdb (Ubuntu 9.1-0ubuntu1) 9.1 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". Attaching to process 15111 [New LWP 15112] [New LWP 15113] [New LWP 15130] [New LWP 15131] [New LWP 15132] [New LWP 15133] [New LWP 15134] [New LWP 15182] [New LWP 15183] [New LWP 15184] [New LWP 15185] [New LWP 15268] [New LWP 15335] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". --Type <RET> for more, q to quit, c to continue without paging--c 0x00007f8b05d3aaff in __GI___poll (fds=0x5566bc5bee20, nfds=11, timeout=16) at ../sysdeps/unix/sysv/linux/poll.c:29 29 ../sysdeps/unix/sysv/linux/poll.c: Datei oder Verzeichnis nicht gefunden. (gdb) I belive that there was something going wrong... in addition another crash happend without any log/trace back
Just want to re-confirm that it is related to plasmashell and wayland. Installation works fine with X11, no crashes of plasmashell.
(In reply to Peter L. Steger from comment #5) > installed the packages, reboot and started the debugging with the command > you provided and got the following results (incl. after entering 'c' + 'RET': > > sudo gdb -pid `pidof plasmashell` > GNU gdb (Ubuntu 9.1-0ubuntu1) 9.1 > Copyright (C) 2020 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > Type "show copying" and "show warranty" for details. > This GDB was configured as "x86_64-linux-gnu". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>. > Find the GDB manual and other documentation resources online at: > <http://www.gnu.org/software/gdb/documentation/>. > > For help, type "help". > Type "apropos word" to search for commands related to "word". > Attaching to process 15111 > [New LWP 15112] > [New LWP 15113] > [New LWP 15130] > [New LWP 15131] > [New LWP 15132] > [New LWP 15133] > [New LWP 15134] > [New LWP 15182] > [New LWP 15183] > [New LWP 15184] > [New LWP 15185] > [New LWP 15268] > [New LWP 15335] > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > --Type <RET> for more, q to quit, c to continue without paging--c > 0x00007f8b05d3aaff in __GI___poll (fds=0x5566bc5bee20, nfds=11, timeout=16) > at ../sysdeps/unix/sysv/linux/poll.c:29 > 29 ../sysdeps/unix/sysv/linux/poll.c: Datei oder Verzeichnis nicht > gefunden. > (gdb) > Did you enter "c" as instructed ? This traces is not a backtrace just the output of gdb when starting. What you did is paused plasmashell which would make it unresponsive, please retry typing in the gdb command prompt "c" for continue and then hit "enter" . When this is working it should display : --Type <RET> for more, q to quit, c to continue without paging-- 0x00007f36c2305aff in __GI___poll (fds=0x55dfc53d7c10, nfds=13, timeout=245) at ../sysdeps/unix/sysv/linux/poll.c:29 29 ../sysdeps/unix/sysv/linux/poll.c: Aucun fichier ou dossier de ce type. (gdb) c Continuing. Then when a crash happen you will get the backtrace in the console.
I did this already - it is hard to see, but the line > --Type <RET> for more, q to quit, c to continue without paging--c shows my input 'c' at the end. In addition I tied it just hitting RETURN without prior c (after restarting gdb) => the same error message as shown. However after you post I tried something in addition: typeing c AFTER the error message (which is also shown in your post) - et voila - I get the 'continuing message' I will come back with further infos soon...
As promised my results: -) I added the debug libraries as described -) I started the gdb as described -) I worked for mor than 5 hours as usual -) I could not face any crashes of plasmashell anymore! However the debug konsole dit not show any useful information (at least for me): [Thread 0x7f951d63e700 (LWP 284060) exited] [Thread 0x7f958911f700 (LWP 284062) exited] [Thread 0x7f9589920700 (LWP 284061) exited] [Thread 0x7f958a121700 (LWP 284059) exited] [New Thread 0x7f9589920700 (LWP 349555)] [New Thread 0x7f958a121700 (LWP 349556)] [New Thread 0x7f958911f700 (LWP 349557)] [New Thread 0x7f951d63e700 (LWP 349558)] The individual figures changed After reboot, not activating gdb, the crashes appeared as usual. Hence I conclude that the gdb activates something, that inhibits the crashes. So I have at least a workaround in order to keep on working => start gdb for plasmashell ;-)
(In reply to Peter L. Steger from comment #9) > As promised my results: > -) I added the debug libraries as described > -) I started the gdb as described > -) I worked for mor than 5 hours as usual > -) I could not face any crashes of plasmashell anymore! > However the debug konsole dit not show any useful information (at least for > me): > [Thread 0x7f951d63e700 (LWP 284060) exited] > [Thread 0x7f958911f700 (LWP 284062) exited] > [Thread 0x7f9589920700 (LWP 284061) exited] > [Thread 0x7f958a121700 (LWP 284059) exited] > [New Thread 0x7f9589920700 (LWP 349555)] > [New Thread 0x7f958a121700 (LWP 349556)] > [New Thread 0x7f958911f700 (LWP 349557)] > [New Thread 0x7f951d63e700 (LWP 349558)] > The individual figures changed > Those are just traces that just depend on the activity of plasma, that's unimportant. > After reboot, not activating gdb, the crashes appeared as usual. > > Hence I conclude that the gdb activates something, that inhibits the > crashes. > > So I have at least a workaround in order to keep on working => start gdb for > plasmashell ;-) It can happen that gdb prevents crashes but this is rare, so I would guess those 5 hours were not long enough to randomly triggers the condition of the bug. Try to find to remember the sequence of actions you did just before a crash and reenact this with gdb on. Hopefully you will trigger the crash eventually. Keep us posted !
In fact this happens frequently within the first five minutes and later on randomly in less than one hour again. Anyway, I will keep on testing and will inform about any item I can figure out. As soon as Plasma 5.20 will be available for KDEneon I intend to install it. Maybe the issue will be resolved there. If you like I can keep the actual configuration running in parallel for a while.
made yesterday a complete new installation (similar to the lase one) but with plasma 5.20 ==> same effects in respect of wayland plasmashell instabilities. came to the point that plasma and wayland are not a suitable combination for productive work now looking for alternatives since I want to use my 3-Monitor setup...
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!
Update to Plasma 5.20.0 did not resolve the problem I will check with 5.20.2 and report again.
(In reply to Peter L. Steger from comment #12) > made yesterday a complete new installation (similar to the lase one) but > with plasma 5.20 ==> same effects in respect of wayland plasmashell > instabilities. > > came to the point that plasma and wayland are not a suitable combination for > productive work Plasma Wayland is somewhat in beta state. We have plenty to do left. Multi-screen and screen hotplugging is an area of focus. > > now looking for alternatives since I want to use my 3-Monitor setup... Fair enough. Btw is this crash reproducible with 1 or 2 screens only ?
Just made some tests - MS-Surface without any external monitor connected => still got a crash, however it took almost one hour but I think this is more related to plasma 5.20.2. I still had the extention unit attached (for power supply, external keyboard and mouse). I will make another test without anything attached (except RF-mouse since I hate touchpads).
I still don't see an actual backtrace of the crash here. :( Can you attach one if the issue is still reproducible?
Great Improvement after latest update (Plasma 5.21.0 inkl. KDE-Apps). Most of my issues are gone, especially the crashes. However, from time to time the wallpaper switches to black & white mode for some seconds, but no issue to be realized. I figured out in addition, that the MS Surface is not suitable for three monitor setup as described. I got heavy CPU/GPU loads resulting in throttling down to 0,8 GHz. After taking away the "full HD screen" everything was fine again.
see below - original issue seems to be resolved by update one issue still ongoing => copy/paste from dolphin to thunderbird attachment not working, but I think this is an issue of thunderbird
That's a separate issue, yeah. Thanks for the info.