Bug 421021 - [Wayland] Sometimes, the behaviour of Alt+Tab is reversed temporally
Summary: [Wayland] Sometimes, the behaviour of Alt+Tab is reversed temporally
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: tabbox (show other bugs)
Version: 5.25.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-04 19:15 UTC by magiblot
Modified: 2024-07-07 03:47 UTC (History)
3 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 magiblot 2020-05-04 19:15:04 UTC
SUMMARY

During intense workflow in a Wayland session, I sometimes find that Alt+Tab walks through tasks in reverse order (upwards). In these cases, Alt+Shift+Tab still works as intended (upwards). The issue persists if I let the task switcher disappear and press Alt+Tab again. I can only deal with it until it goes back to its normal behaviour (downwards) a few minutes later. 

I don't know how to help you debug this, so I will accept any suggestions (including patches).

I haven't experienced this issue in X11.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.2
Kernel Version: 5.6.8-arch1-1
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 11,6 GiB of RAM

ADDITIONAL INFORMATION

I am using the Wayland session as my default environment. Due to various issues, I request QT and GTK applications to run as X applications. So, I run Plasma in the following way:

> GDK_BACKEND=x11 QT_QPA_PLATFORM=xcb startplasma-wayland
I don't know if this is related with the issue, but it is very hard for me to work in a Wayland session without these settings. Basically, due to issues like bug 392376, any application can crash at any moment. XWayland clients are a lot more stable.
Comment 1 kde.org 2021-11-06 13:28:13 UTC
This issue report is quite old. Can you please confirm, that it still persists with KDE 5.23? If so, can you please describe steps on how to reliably reproduce this issue?
Comment 2 Bug Janitor Service 2021-11-21 04:40:32 UTC
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!
Comment 3 Bug Janitor Service 2021-12-06 04:39:45 UTC
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!
Comment 4 magiblot 2022-07-29 22:01:11 UTC
I used the Wayland session again after a very long time and experienced this issue again in Plasma 5.25.3. Therefore, I'm reopening this issue.

I'm sorry that I cannot provide steps to reproduce this issue reliably, since it just happens all of a suden.
Comment 5 Zamundaaa 2024-06-07 16:54:05 UTC
Does this still happen in Plasma 6? There have been a few changes around modifier handling for the tabbox, which might have fixed this
Comment 6 Bug Janitor Service 2024-06-22 03:47:34 UTC
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!
Comment 7 Bug Janitor Service 2024-07-07 03:47:21 UTC
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!