Summary: | Invisible windows appear randomly on wayland | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Alexandre Pereira <pereira.alex> |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | alex765, auxsvr, bugseforuns, kde, kde, lonefenris, nate, sonichedgehog_hyperblast00 |
Priority: | NOR | ||
Version: | git master | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Alexandre Pereira
2018-09-04 00:47:50 UTC
Example of "present windows" effect showing an area where an invisible window is, and its close button next to it. Clicking on that button results in kwin crash. https://imgur.com/a/hMInSnK First lets try to identify this invisible window: qdbus org.kde.KWin /KWin org.kde.KWin.showDebugConsole then in the "windows tab" look around for anything relevant and try to work out what it is. My guess would would be it's xembedsniproxy. You can verify this will killall xembedsniproxy and see if it goes away. --- As for the crash, a crash report will really help. It's a pain to get wtih kwin wayland, but going to a TTY running sudo gdb --pid `pidof kwin_wayland` typing continue then reproducing the crash is a good way. Then back from the tty you can type "set logging on" "bt" to save a crash report. thanx David for the reply. Sorry for the lame video, but i got a invisible window, a konsole window, and recorded a video: https://youtu.be/-c5my2wp0tg the window is a konsole window, other konsole windows display fine. The problematic window is selected in showDebugConsole. Is there a way to save the info of showDebugConsole into a file ? Today I noticed the same problem in plasma 5.14 on Arch Linux. I can confirm Wayland session crash when I close the hidden window while "present windows" effect is active. In my case only xWayland apps (Firefox and Opera browsers) were affected. 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 set the bug status 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 #3 provided new information; changing status for inspection. Just to confirm comment #4, in my case its also only Xwayland apps. It was happening in kde apps also, because they were using Xwayland ( using opensuse, they seem to use xwayland if not using the qt_qpa_platform=wayland;xcb env. Also, found out ( hinted by a user on reddit with this problem also ), that the window is recoverable. Minimizing the window ( through keyboard ) and then restoring it again, makes ir become visible and working ( sometimes I have to minimize and restore 2 or 3 times ). Since I've been seeing this problem, I decided to do a little reproduction testing with it. This issue seems to affect more than just windows for me, but rather any popup UI element in an XWayland application. That includes menu activations. It's affecting both Qt-based (VLC) and GTK-based (Firefox and Thunderbird) applications that run in XWayland. A semi-reliable way to reproduce it on my end is to have an XWayland window minimized (I don't know why this helps reproduce it, but it does), and mash a menu button in another XWayland application. You should notice invisible activations. To add to my previous comment, when you produce an invisible menu activation as described, and with the invisible menu active, you then restore the minimized XWayland window, the restored window will be non-interactive until it is minimized and restored again (e.g. using the taskbar menu). Possible duplicate of bug 394803 ? This is likely in some way related to bug 420039 - Please check the info there and see if anything helps or resembles this. I haven't been hit by this bug in some time. Kyle, can you test kde daily git packages of plasma 5.19 ( by either neon or opensuse or manjaro )? I'm on Arch. There's AUR packages. I'll give it a shot when I have a moment. It seems the AUR packages for plasma git aren't well-maintained, so it will be more difficult for me to set up an environment based on the git versions than I'd expected. (In reply to Kyle Tirak from comment #15) > It seems the AUR packages for plasma git aren't well-maintained, so it will > be more difficult for me to set up an environment based on the git versions > than I'd expected. I recommend either set up a live usb stick with kde neon or this: https://en.opensuse.org/SDB:Argon_and_Krypton ( i am testing on an installation similar to krypton myself, its very well mantained and works rather well ) Its easier than to change your whole setup and probably break something ! *** This bug has been marked as a duplicate of bug 420039 *** |