Bug 482479 - Can not set move window to next screen to meta + when zoom in is assigned meta +
Summary: Can not set move window to next screen to meta + when zoom in is assigned meta +
Status: RESOLVED DUPLICATE of bug 480862
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keys (show other bugs)
Version: 6.0.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-05 16:59 UTC by Andres
Modified: 2024-03-15 23:09 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andres 2024-03-05 16:59:43 UTC
SUMMARY
Can not set move window to next screen to meta +
Default meta shift right works as excpected

STEPS TO REPRODUCE
1. Open shortcut settings
2. find move window to next screen
3. set keybind to meta +
4. test new binding of meta +

OBSERVED RESULT
Nothing happens

EXPECTED RESULT
The window moves to the next screen

Operating System: Garuda Linux 
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.8-1-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT
Comment 1 fanzhuyifan 2024-03-06 04:14:27 UTC
Steps to reproduce (on wayland, plasma 6 dev build):

1. assign Meta ++ to zoom in (this is the default)
2. assign Meta++ to move to next screen (press meta, shift, =)
3. confirm the reassignment
4. apply
5. press Meta++

Nothing happens.

6. delete, apply, and reassign, apply

Now it works.
Comment 2 Nicolas Fella 2024-03-11 22:00:35 UTC

*** This bug has been marked as a duplicate of bug 482068 ***
Comment 3 Nicolas Fella 2024-03-11 22:01:21 UTC

*** This bug has been marked as a duplicate of bug 471370 ***
Comment 4 Andres 2024-03-15 21:46:41 UTC
@Nicolas Fella I don't think this a dup of https://bugs.kde.org/show_bug.cgi?id=471370 as  its not a problem on having to set the shortcut multiple times. 

In my case no amount of setting and unsettling of the move window to next screen hotkey allows me to use the meta and + keys together
Comment 5 Andres 2024-03-15 21:55:30 UTC
(In reply to Andres from comment #4)
> @Nicolas Fella I don't think this a dup of
> https://bugs.kde.org/show_bug.cgi?id=471370 as  its not a problem on having
> to set the shortcut multiple times. 
> 
> In my case no amount of setting and unsettling of the move window to next
> screen hotkey allows me to use the meta and + keys together

`Meta` + `Shift` + `=` does work (after multiple reassigns) however which is what @fanzhuyifan reported what I am reporting is `Meta` + `+` (numpad plus) is a not working (On any shortcut actually I have tried several) this was working on 5.27.10
Comment 6 fanzhuyifan 2024-03-15 22:10:26 UTC
(In reply to Andres from comment #5)
> (In reply to Andres from comment #4)
> > @Nicolas Fella I don't think this a dup of
> > https://bugs.kde.org/show_bug.cgi?id=471370 as  its not a problem on having
> > to set the shortcut multiple times. 
> > 
> > In my case no amount of setting and unsettling of the move window to next
> > screen hotkey allows me to use the meta and + keys together
> 
> `Meta` + `Shift` + `=` does work (after multiple reassigns) however which is
> what @fanzhuyifan reported what I am reporting is `Meta` + `+` (numpad plus)
> is a not working (On any shortcut actually I have tried several) this was
> working on 5.27.10

For numpad keys the problem might be BUG 481164. Do you observe this problem with non-numpad keys?
Comment 7 Andres 2024-03-15 23:09:02 UTC
the shortcut works with non num pad keys. It seems my problem is a duplicate of https://bugs.kde.org/show_bug.cgi?id=480862? although should that be fixed on 6.0.2?
Comment 8 fanzhuyifan 2024-03-15 23:09:58 UTC
(In reply to Andres from comment #7)
> the shortcut works with non num pad keys. It seems my problem is a duplicate
> of https://bugs.kde.org/show_bug.cgi?id=480862? although should that be
> fixed on 6.0.2?

Upstream Qt patch is needed.

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