Improve Wayland zero output handling
Closed, ResolvedPublic

Description

When no output is connected, there are problems:

  • In Drm backend final output removal is not propagated via screensQueried, seg faults.
  • Having no wl_output crashes clients.

Proposed steps:

  • Move Wayland output creation from plugins to AbstractOutput
  • Create dummy output in OutputScreens
  • Always call screensQueried
romangg created this task.Nov 9 2018, 5:14 PM
romangg triaged this task as High priority.

Having no wl_output crashes clients

That's a client bug then. Qt shouldn't have an issue.

Having no wl_output crashes clients

That's a client bug then. Qt shouldn't have an issue.

Martin assumed otherwise here: https://bugs.kde.org/show_bug.cgi?id=389551

Since I experienced crashes in KDE apps and plasmashell when removing all screens, I thought his assumption is right although this would be of course somewhat an oversight in the Wayland protocol specification. You think it should be no problem?

From other task:

But I heard different things about that.

Kwin's internal QPA now fakes having a screen if there's none. Same as the QtWayland and QtXCB QPAs.
It might be enough to close the crashing task.

romangg moved this task from Backlog to Work In Progress on the KWin board.Dec 11 2019, 12:42 PM
romangg moved this task from Work In Progress to Done on the KWin board.Jan 8 2020, 9:21 AM
romangg closed this task as Resolved.