Bug 482235 - No longer able to trigger desktop grid effect via screen edge corner action
Summary: No longer able to trigger desktop grid effect via screen edge corner action
Status: RESOLVED DUPLICATE of bug 478137
Alias: None
Product: kwin
Classification: Plasma
Component: effects-desktop-grid (show other bugs)
Version: 6.0.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-02 15:51 UTC by Sean Colsen
Modified: 2024-03-03 19:58 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sean Colsen 2024-03-02 15:51:42 UTC
Prior to upgrading to Plasma 6.0, I was able to initiate the desktop grid effect via moving my pointer to a screen corner. After the upgrade, I am able to initiate the desktop grid effect via a keyboard shortcut (and the desktop grid itself works fine). But I'm no longer able to configure my screen edge actions to trigger the desktop grid effect.

The options I have available for all eight screen edge/corner locations are as follows:

No action
Peek at Desktop
Lock Screen
Show KRunner
Activity Manager
Present Windows - All Desktops
Present Windows - Current Desktop
Present Windows - Current Application
Overview
Toggle window switching
Toggle alternative window switching

I would expect to see "Desktop Grid" within that list of options, but I don't.

I've tried selecting "Overview", thinking that perhaps it would show a grid, but it does not. It seems to function in a nearly identical manner to "Present Windows - Current Desktop".

These existing bugs seem like potential duplicates:

https://bugs.kde.org/show_bug.cgi?id=442518
https://bugs.kde.org/show_bug.cgi?id=454102

However, they show as already being fixed.

I am running on Plasma 6.0.0, KDE Neon 6.0, Qt Version 6.6.2, Kernel 6.5.0-21-generic, Wayland
Comment 1 fanzhuyifan 2024-03-02 19:10:28 UTC
Fixed in 6.1

*** This bug has been marked as a duplicate of bug 478137 ***