Bug 473037 - Kwin error when GPU connected on external screen
Summary: Kwin error when GPU connected on external screen
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.27.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: multiscreen
Depends on:
Blocks:
 
Reported: 2023-08-05 12:12 UTC by deco33000
Modified: 2023-09-08 03:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description deco33000 2023-08-05 12:12:56 UTC 
Hi,
This bug is a duplicate of the one I posted on the Nvidia forum, here https://forums.developer.nvidia.com/t/driver-5-35-linux-6-3/262175.

I repost here the corpus of my post:
Hi,
Debian testing, X11, KDE, HDMI, external monitor.

When I just use my laptop's screen everything runs smooth. When HDMI is connected, here is the kind of
 error that occurs after a few minutes:

```
2023-08-05T13:39:10.679385+02:00 User plasmashell[3510]: [GFX1-]: Failed to create EGLSurface!: 0x3009
2023-08-05T13:39:10.679482+02:00 User plasmashell[3510]: [GFX1-]: Failed to create EGLSurface. 1 renderers, 0 active.
2023-08-05T13:39:10.693465+02:00 User kwin_x11[1874]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 38926, resource id: 29362575, major code: 3 (GetWindowAttributes), minor code: 0
2023-08-05T13:39:10.693519+02:00 User kwin_x11[1874]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 38927, resource id: 29362575, major code: 14 (GetGeometry), minor code: 0
2023-08-05T13:39:10.949457+02:00 User plasmashell[3510]: [GFX1-]: Handling webrender error 3
2023-08-05T13:39:10.949505+02:00 User plasmashell[3510]: [GFX1-]: Fallback WR to SW-WR
2023-08-05T13:39:11.063129+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:39:11.063510+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:39:11.609316+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:39:11.609580+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:39:11.622183+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:39:11.622580+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:39:11.644358+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:39:11.644627+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:39:13.280134+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:39:13.280514+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:39:18.426580+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:39:18.426814+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:39:29.270028+02:00 User plasmashell[2914]: #033[90m[main 2023-08-05T11:39:29.267Z]#033[0m update#setState checking for updates
2023-08-05T13:39:29.275350+02:00 User plasmashell[2914]: #033[91m[main 2023-08-05T11:39:29.275Z]#033[0m Error: net::ERR_INTERNET_DISCONNECTED
2023-08-05T13:39:29.275421+02:00 User plasmashell[2914]:     at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:49312)
2023-08-05T13:39:29.275439+02:00 User plasmashell[2914]:     at SimpleURLLoaderWrapper.emit (node:events:513:28)
2023-08-05T13:39:29.275468+02:00 User plasmashell[2914]: #033[90m[main 2023-08-05T11:39:29.275Z]#033[0m update#setState idle
2023-08-05T13:39:42.216210+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:39:42.216441+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:40:20.571826+02:00 User wpa_supplicant[1028]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-45 noise=9999 txrate=144400
2023-08-05T13:40:25.348789+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:40:25.349055+02:00 User rtkit-daemon[1177]: Supervising 8 threads of 5 processes of 1 users.
2023-08-05T13:41:52.187911+02:00 User kwin_x11[1874]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7236, resource id: 29366350, major code: 3 (GetWindowAttributes), minor code: 0
2023-08-05T13:41:52.187981+02:00 User kwin_x11[1874]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 7237, resource id: 29366350, major code: 14 (GetGeometry), minor code: 0
2023-08-05T13:41:55.117511+02:00 User kwin_x11[1874]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8051, resource id: 104857648, major code: 18 (ChangeProperty), minor code: 0
2023-08-05T13:42:12.630521+02:00 User kwin_x11[1874]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 9723, resource id: 81788945, major code: 18 (ChangeProperty), minor code: 0
```

Error with kwin is really irritating and prevent any serious work to be done: the screen literally lock, I have to unplug the external screen to put everything back into order. Powermixer with preference to maximum performance won't change anything.

If you need any details..
Comment 1 Nate Graham 2023-08-07 22:16:43 UTC 
Multi-GPU is not well supported on X11. Can you try Wayland and see if it's any better?
Comment 2 deco33000 2023-08-08 06:00:36 UTC 
(In reply to Nate Graham from comment #1)
> Multi-GPU is not well supported on X11. Can you try Wayland and see if it's
> any better?

Thanks Nate,

Unfortunately, under Wayland, the external screen is an awful experience: it is as if the refresh rate was like 1Hz. 
Note that the laptop screen is not impacted. 
It's a so-so situation that make working on two screens complicated for the eyes.
Comment 3 Nate Graham 2023-08-08 19:36:56 UTC 
That sounds like quite a bad bug. Have you reported it? If not, please do submit a new bug report to track that issue so it can get fixed.
Comment 4 deco33000 2023-08-09 08:45:56 UTC 
(In reply to Nate Graham from comment #3)
> That sounds like quite a bad bug. Have you reported it? If not, please do
> submit a new bug report to track that issue so it can get fixed.

Please find it here:
https://bugs.kde.org/show_bug.cgi?id=473197
Comment 5 Bug Janitor Service 2023-08-24 03:45: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 6 Bug Janitor Service 2023-09-08 03:45:29 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!