| Summary: | kwin_wayland crashed when I tried to run Vivaldi browser natively on Wayland | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Patrick Silva <bugseforuns> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | alex765, nate |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Patrick Silva
2022-11-14 18:06:22 UTC
Do you use virtual keyboard? (In reply to Vlad Zahorodnii from comment #1) > Do you use virtual keyboard? No. What windows did you close before opening vivaldi? I can't make kwin crash by running "vivaldi-stable --enable-features=UseOzonePlatform --ozone-platform=wayland" > #6 0x00007fd0b0a401d3 in std::function<bool (KWin::X11Window const*)>::operator()(KWin::X11Window const*) const (__args#0=<optimized out>, this=0x7ffc7a840db0) at /usr/include/c++/11/bits/std_function.h:590
were there any apps that run through xwayland?
I enabled the flag to run Vivaldi natively on Wayland in vivaldi:flags page (set Preferred Ozone platform flag to 'Auto') and clicked on 'Relaunch' button. Vivaldi tried to restart but it got stuck in the task manager with a Wayland generic icon and never appeared on the screen. I closed the unusable Vivaldi with a middle-clicked on its task and then kwin_wayland crashed. (In reply to Vlad Zahorodnii from comment #4) > > #6 0x00007fd0b0a401d3 in std::function<bool (KWin::X11Window const*)>::operator()(KWin::X11Window const*) const (__args#0=<optimized out>, this=0x7ffc7a840db0) at /usr/include/c++/11/bits/std_function.h:590 > > were there any apps that run through xwayland? When the crashed occured, no. But before setting Vivaldi to run natively on Wayland I was running it on Xwayland. Can you still reproduce the crash? I followed your steps, but kwin seems to be okay I can reproduce (but not consistently) by following these steps: (In reply to Patrick Silva from comment #5) > I enabled the flag to run Vivaldi natively on Wayland in vivaldi:flags page > (set 'Preferred Ozone platform' flag to 'Auto') and clicked on 'Relaunch' > button. Vivaldi tried to restart but it got stuck in the task manager with a > Wayland generic icon and never appeared on the screen. I closed the unusable > Vivaldi with a middle-click... And then opening Kickoff or right-clicking on desktop. Also reproducible on Arch Linux after update to vivaldi 5.6.2867.36-1 Operating System: Arch Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Graphics Platform: Wayland I got a similar crash shortly after trying to run Discord natively on Wayland. I followed the step given here: https://github.com/flathub/com.discordapp.Discord#wayland I then started Discord, the loading spinner appeared, and then the Task Manager entry for the Discord window appeared, but the window itself wasn't visible. The timing of the kwin crash is a bit random, I think once it crashed when attempting to close Discord via the context menu in that situation - possibly similar to https://bugs.kde.org/show_bug.cgi?id=460598 Plasma 5.27.4 Qt 5.15.9 Frameworks 5.105.0 This bug is a crash report that is over a year old without any activity, as our software is always changing, the information in this ticket is unlikely to still be useful. If this issue is still reproducible in a newer version of kwin (5.27.5 or 6.0) please reopen this ticket with a bumped version number or it will be closed in 30 days. 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! 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! |