Bug 457384 - KWin: Present Windows effect suddenly stopped working.
Summary: KWin: Present Windows effect suddenly stopped working.
Status: RESOLVED DUPLICATE of bug 452344
Alias: None
Product: kwin
Classification: Plasma
Component: effects-present-windows (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: 2022-08-01 19:07 UTC by Moritz
Modified: 2022-08-04 17:36 UTC (History)
1 user (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 Moritz 2022-08-01 19:07:01 UTC
Hello

My Present Windows function suddenly stopped working in KDE.
I don't know how many days  ago since I don't use this function too often.
I am using Arch Linux (EndeavourOS) with all the latest updates.

Present Windows was and is activated under Settings > Workspace Behavior > Desktop Effects > Window Management: Desktop Grid, Overview, Present Windows.

The default shortcut `Meta+W` does not work anymore and I also had Present Windows bound to a corner in the Screen Edges settings - also not working anymore.

I think `qdbus org.kde.kglobalaccel /component/kwin invokeShortcut "ExposeAll"` is the console command for Present Windows but that's also not working.

When I press the shortcut or use the corner nothing happens at all.

___

I did not change anything in my settings so I guess some update broke this functionality but I don't know when exactly, how or why.

*A friend of mine is also using Arch Linux (EndeavourOS) and has the same problem.*


STEPS TO REPRODUCE
1.  Try to activate the Present Windows 

OBSERVED RESULT
Nothing happens

EXPECTED RESULT
The Present Windows effect appears on screen.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  
KDE Plasma Version: 5.25.3
KDE Frameworks Version:  5.96.0
Qt Version: 5.15.5
 X11

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-08-01 19:53:11 UTC
Meta+W activates Overview, not Present Windows.

`qdbus org.kde.kglobalaccel /component/kwin invokeShortcut "ExposeAll" works for me.

What happens when you run that command? What output do you get back? Nothing?
Comment 2 Moritz 2022-08-01 21:56:21 UTC
(In reply to Nate Graham from comment #1)
> Meta+W activates Overview, not Present Windows.

Then I guess Overview is also not working for me.

> `qdbus org.kde.kglobalaccel /component/kwin invokeShortcut "ExposeAll" works
> for me.
> 
> What happens when you run that command? What output do you get back? Nothing?

Nothing.

I just checked again: Desktop Grid, Overview and Present Window are all not working.

Thank you for your reply.
Comment 3 Moritz 2022-08-01 22:28:03 UTC
I just used the program Timeshift and booted into a snapshot of my system dated 2022-07-22 (my oldest available snapshot) and at that point of time the Present Windows effect etc. were already not working.

In hindsight this make sense since I used to activate the Present Window effect via the top left corner all the time by accident but this did not happen in the last week or so (obviously since it was not able to happen).

Maybe this time frame is somewhat helpful.
Comment 4 Nate Graham 2022-08-02 14:16:07 UTC
Can you do this:
1. Restart kwin with `kwin_x11 --replace` in a terminal window
2. In another terminal window, run `qdbus org.kde.kglobalaccel /component/kwin invokeShortcut "ExposeAll`
3. Go back to the first terminal window and see the text output; post it here
Comment 5 Moritz 2022-08-02 19:14:43 UTC
(In reply to Nate Graham from comment #4)
> Can you do this:
> 1. Restart kwin with `kwin_x11 --replace` in a terminal window
> 2. In another terminal window, run `qdbus org.kde.kglobalaccel
> /component/kwin invokeShortcut "ExposeAll`
> 3. Go back to the first terminal window and see the text output; post it here

Hello Nathan,
`kwin_x11 --replace`  helped me a lot.

The output was:
>kwin_x11 --replace                                                                                                                                                                    ✔ 
>kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker"
>kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate"
>qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2109, resource id: 106954788, major code: 3 (GetWindowAttributes), minor code: 0
>qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2110, resource id: 106954788, major code: 14 (GetGeometry), minor code: 0
>qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2121, resource id: 106954792, major code: 3 (GetWindowAttributes), minor code: 0
>qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2122, resource id: 106954792, major code: 14 (GetGeometry), minor code: 0
>kwin_platform_x11_standalone: Compositing disabled: video driver seems unstable. If you think it's a false positive, please remove  "OpenGLIsUnsafe"  from [Compositing] in kwinrc and restart kwin.
>kwin_core: Compositing is not possible

I googled the error message a bit and went into: Settings > Display and Monitor > Compositor
Over there I saw a big warning looking exactly like this one: 
https://fitzcarraldoblog.wordpress.com/2020/08/05/re-enabling-opengl-compositing-automatically-after-it-crashes-kwin-at-login-to-kde-plasma/

I clicked on `Re-enabling OpenGL detection` used `kwin_x11 --replace` again and now everthing works now.

The output of `kwin_x11 --replace`  changed into this now:
>kwin_x11 --replace                                                                                                                                                         ✔   8m 38s 
>qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 180, resource id: 6291466, major code: 20 (GetProperty), minor code: 0
>qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 181, resource id: 6291466, major code: 20 (GetProperty), minor code: 0
>kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker"
>kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate"
>qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2795, resource id: 6291492, major code: 3 (GetWindowAttributes), minor code: 0
>qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2796, resource id: 6291492, major code: 14 (GetGeometry), minor code: 0
>qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2820, resource id: 6291504, major code: 3 (GetWindowAttributes), minor code: 0
>qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2821, resource id: 6291504, major code: 14 (GetGeometry), minor code: 0
>qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2832, resource id: 6291507, major code: 3 (GetWindowAttributes), minor code: 0
>OpenGL vendor string:                   NVIDIA Corporation
>OpenGL renderer string:                 NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
>OpenGL version string:                  3.1.0 NVIDIA 515.57
>OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
>Driver:                                 NVIDIA
>Driver version:                         515.57
>GPU class:                              Unknown
>OpenGL version:                         3.1
>GLSL version:                           1.40
>X server version:                       1.21.1
>Linux kernel version:                   5.18.15
>Requires strict binding:                no
>GLSL shaders:                           yes
>Texture NPOT support:                   yes
>Virtual Machine:                        no
>QObject::connect(KWin::InputMethod, KWin::EffectsHandlerImpl): invalid nullptr parameter

I am using a Nvidia GPU. 
I guess my issue is solved for now although I still don't know why it happened in the first place.
Comment 6 Nate Graham 2022-08-04 17:36:41 UTC
> kwin_platform_x11_standalone: Compositing disabled: video driver seems unstable. If you think it's a false positive, please remove  "OpenGLIsUnsafe"  from [Compositing] in kwinrc and restart kwin.
> kwin_core: Compositing is not possible

So what happened here was that KWin crashed five times in a row while trying to do compositing and therefore decided that compositing was unstable and disabled it. The Present Windows effect requires compositing, so it stopped working, with no explanation.

This is ultimately caused by Bug 452344; we'll discuss a fix there.

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