SUMMARY Whe I press Meta+Tab to switch activity, It change activity successfully but the activity switch bar can't be closed automatically. It is fixed there. Only after press Meta+Tab many times, It can be closed automatically STEPS TO REPRODUCE 1. Press Meta+Tab without release them in the same time before the appear of activity switch bar 2. release them, the activity switch bar can't be closed automatically 3. Press Meta+Tab many times, the activity switch bar maybe closed OBSERVED RESULT The activity switch bar fixed there EXPECTED RESULT The activity switch bar can auto-hide SOFTWARE/OS VERSIONS Windows: no macOS: no Linux/KDE Plasma: Manjaro Kde 20.1.1 (available in About System) KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.71.0 Qt Version: 5.15 ADDITIONAL INFORMATION
This may be a plasmashell bug. Pressing alt+space and running `killall plasmashell ; plasmashell` closes the activities panel.
*** Bug 424134 has been marked as a duplicate of this bug. ***
I see this, too. To get the switcher to hide it looks to me as one has to release the keys while the switch animation is still active.
Possible duplicates: 1. https://bugs.kde.org/show_bug.cgi?id=389771 2. https://bugs.kde.org/show_bug.cgi?id=422957
*** Bug 422957 has been marked as a duplicate of this bug. ***
*** Bug 389771 has been marked as a duplicate of this bug. ***
You can manually close with Meta+q (work-a-round) I was following the advice to `killall plasmashell` and then ran that from a terminal. Next time this bug occurred, the following was in my terminal if that helps the person with fixing the bug. file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:165: TypeError: Value is null and could not be converted to an object file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:165: TypeError: Value is null and could not be converted to an object file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:165: TypeError: Value is null and could not be converted to an object file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... } file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Plasma/ScrollViewStyle.qml:60:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... } file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Angus, there is patch fixing error message you've mentioned, see: https://bugs.kde.org/show_bug.cgi?id=422957#c6.
*** Bug 393912 has been marked as a duplicate of this bug. ***
*** Bug 394798 has been marked as a duplicate of this bug. ***
*** Bug 425871 has been marked as a duplicate of this bug. ***
*** Bug 424524 has been marked as a duplicate of this bug. ***
I can't reproduce with the instructions given. Is this still an issue with Plasma 5.20 beta?
It does not appear here immediately. I'll be aware during the next week. No extra screen during the weekend. -- fredag den 18. september 2020 00.50.58 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=424020 > > David Edmundson <kde@davidedmundson.co.uk> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |kde@davidedmundson.co.uk Status|CONFIRMED > |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #13 from David Edmundson <kde@davidedmundson.co.uk> --- > I can't reproduce with the instructions given. > > Is this still an issue with Plasma 5.20 beta?
(In reply to David Edmundson from comment #13) > I can't reproduce with the instructions given. > > Is this still an issue with Plasma 5.20 beta? I'm not able to reproduce this issue in Plasma 5.20 beta. I tested it in recent (today updated) KDE neon, so with Plasma version 5.19.90 and KF-5.75. Nevertheless I still experience this in Plasma 5.19.5, KF-5.74, Qt-5.15.1. Maybe this depends on some switcher in Plasma, but didn't discovered which one.
(In reply to nyanpasu64 from comment #1) > This may be a plasmashell bug. Pressing alt+space and running `killall > plasmashell ; plasmashell` closes the activities panel. Faster is usage of shortcut: Meta+Q
Meta+Q does indeed make it stick open, but I think that's intentional. Meta+Tab shows the auto-closing version. ...I have no idea why these are different things, of course.
(In reply to Nate Graham from comment #17) > Meta+Q does indeed make it stick open, but I think that's intentional. > Meta+Tab shows the auto-closing version. > > ...I have no idea why these are different things, of course. I meant that I'm able to unstick this bar by Meta+Q. When no bar is present then this shortcut just shows it. When I switch Activities quickly by Meta+Tab - not holding Meta - then bar isn't show. Only when I will hold Meta then bar is shonw and after release Meta, isn't autohide. Now I need to use again Meta+Q to hide it.
One way to hide it is to show the desktop, rightclick and select "Activities..." fredag den 18. september 2020 18.49.20 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=424020 > > --- Comment #18 from Piotr Mierzwinski <piotr.mierzwinski@gmail.com> --- > (In reply to Nate Graham from comment #17) > > > Meta+Q does indeed make it stick open, but I think that's intentional. > > Meta+Tab shows the auto-closing version. > > > > ...I have no idea why these are different things, of course. > > I meant that I'm able to unstick this bar by Meta+Q. When no bar is present > then this shortcut just shows it. > When I switch Activities quickly by Meta+Tab - not holding Meta - then bar > isn't show. Only when I will hold Meta then bar is shonw and after release > Meta, isn't autohide. Now I need to use again Meta+Q to hide it.
(In reply to Anders Lund from comment #19) > One way to hide it is to show the desktop, rightclick and select > "Activities..." > > fredag den 18. september 2020 18.49.20 CEST skrev du: > > https://bugs.kde.org/show_bug.cgi?id=424020 > > > > --- Comment #18 from Piotr Mierzwinski <piotr.mierzwinski@gmail.com> --- > > (In reply to Nate Graham from comment #17) > > > > > Meta+Q does indeed make it stick open, but I think that's intentional. > > > Meta+Tab shows the auto-closing version. > > > > > > ...I have no idea why these are different things, of course. > > > > I meant that I'm able to unstick this bar by Meta+Q. When no bar is present > > then this shortcut just shows it. > > When I switch Activities quickly by Meta+Tab - not holding Meta - then bar > > isn't show. Only when I will hold Meta then bar is shonw and after release > > Meta, isn't autohide. Now I need to use again Meta+Q to hide it. All of these 'solutions' are only workarounds, we don't know yet what terms must be met to reproduce the issue. I wasn't able to reproduce it in KDE Neon with Plasma 5.20 beta, but it wasn't my regular system which I use every day. So I'm not sure if after update to 5.20 issue will still persists.
*** Bug 426887 has been marked as a duplicate of this bug. ***
(In reply to Piotr Mierzwinski from comment #20) > All of these 'solutions' are only workarounds, we don't know yet what terms > must be met to reproduce the issue. I wasn't able to reproduce it in KDE > Neon with Plasma 5.20 beta, but it wasn't my regular system which I use > every day. So I'm not sure if after update to 5.20 issue will still persists. I'm on 5.19.5 via openSUSE Tumbleweed. I can trigger the bug reliably everytime but spamming Meta + Space a few times.
(In reply to Tamara Zoe Schmitz from comment #22) > > I'm on 5.19.5 via openSUSE Tumbleweed. > I can trigger the bug reliably everytime but spamming Meta + Space a few > times. I meant Meta + Tab. I am using X.org
The comments are unclear. Please reopen if the bug is not fixed in Plasma 5.20.
*** Bug 428121 has been marked as a duplicate of this bug. ***
I din't experience this in 5.20.
*** Bug 431015 has been marked as a duplicate of this bug. ***