Bug 465685 - regression: unresponsive Application Menu/Launcher/Dashboard and Task Manager
Summary: regression: unresponsive Application Menu/Launcher/Dashboard and Task Manager
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.26.90
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2023-02-13 20:42 UTC by Rick Scholten
Modified: 2023-02-17 06:59 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Log - resulting in unresponsive behaviour (14.77 KB, text/plain)
2023-02-14 13:26 UTC, Rick Scholten
Details
Log - resulting in plasma/kwin crash (15.59 KB, text/plain)
2023-02-14 13:27 UTC, Rick Scholten
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rick Scholten 2023-02-13 20:42:06 UTC
SUMMARY
***
Flatpak Google Chrome Incognito window causes unresponsive Application Menu and Task Manager in Plasma 5.26.90. No problems in normal Chrome window. No problems in Plasma 5.26.5 with Incognito.
***

STEPS TO REPRODUCE
1. Install Google Chrome from Flathub.
2. Open Google Chrome Incognito with right click from Application Menu.

OBSERVED RESULT
Application Menu and Task Manager are unresponsive.

EXPECTED RESULT
Application Menu and Task Manager are responsive.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Kinoite 38
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

Screen recording: https://ufile.io/g3jwvtlx
Comment 1 Rick Scholten 2023-02-14 06:21:47 UTC
STEPS TO REPRODUCE
1. Install Google Chrome from Flathub.
2. In Application Menu go to Internet, Right-click Google Chrome, Add to Favourites
3. From Favourites in Application Menu, Right-click Google Chrome, New Incognito window.
OBSERVED RESULT: 
unresponsive Application Menu and Task Manager

Seems to be related to Plasma?/KWin? crashing and restarting:
1. Install Google Chrome from Flathub.
2. In Application Menu go to Internet, Right-click Google Chrome, New Incognito window.
OBSERVED RESULT:
Plasma?/KWin? crashing and restarting.
Comment 2 Rick Scholten 2023-02-14 12:08:04 UTC
I encounter the same unresponsiveness when opening Google Chrome Incognito window from either Application Dashboard or Application Launcher. 

Here there is no Plasma/KWin crash when not opening the Incognito window from favourites. There is only unresponsive Application Dashboard/Launcher and Task Manager.
Comment 3 amilots 2023-02-14 13:04:03 UTC
Could not reproduce on latest plasma stable on neon. Could you provide the following info?

1. 5.26.90: how did you install this version? from fedora rawhide or using kdesrc-build?
2. Which windowing system in use ie X11 or wayland?
3. Which graphics processor is in use?

Are you using any custom launcher?

Also provide journal log, it really helps. start journalctl -f > log.txt, reproduce the bug, stop journalctl and attach the log.txt here.
Comment 4 Rick Scholten 2023-02-14 13:26:34 UTC
Created attachment 156226 [details]
Log - resulting in unresponsive behaviour

Opening Chrome Incognito by right-click favourite in Application Menu.
Comment 5 Rick Scholten 2023-02-14 13:27:50 UTC
Created attachment 156227 [details]
Log - resulting in plasma/kwin crash

Opening Incognito window by right-click Google Chrome from Application Menu/Internet.
Comment 6 Rick Scholten 2023-02-14 13:30:57 UTC
Ty for the information.

1. It's Fedora Kinoite 38: image based distro. No installation on my part.
2. Wayland
3. Nvidia GTX 1060. I don't have proprietary Nvidia drivers installed.

The launchers are the default launchers shipped in Plasma, both 5.26.5 and 5.26.90.

It happens with all Chromium based flatpak browsers.
Comment 7 Rick Scholten 2023-02-14 13:34:52 UTC
In X11 I experience the same behaviour as in Wayland.
Comment 8 Rick Scholten 2023-02-15 05:40:04 UTC
After updating Fedora 37 Kinoite with plasma 5.26.5 to KDE Frameworks 5.103.0 the problems has appeared there too.

I've also tested it on my iGPU Intel laptop with F37K 5.26.5 and 5.103.0 and it has the problem too.
Comment 9 Rick Scholten 2023-02-15 05:42:02 UTC
Looks like KDE Frameworks 5.103.0 introduced the problem, not Plasma 5.26.90.
Comment 10 Rick Scholten 2023-02-17 06:59:39 UTC
After Fedora 37 Kinoite update from plasma 5.26.5 to 5.27.0 the was resolved.