[KScreen] [Bug 386900] KScreen picks wrong resolution in QEMU on wayland

[Sebastian Kügler]

https://bugs.kde.org/show_bug.cgi?id=386900

Sebastian Kügler  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Sebastian Kügler  ---
Thanks! Let's close this bug then, if the problem persists, we can always
re-open it and investigate further.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 386900] KScreen picks wrong resolution in QEMU on wayland

[Fabian Vogt]

https://bugs.kde.org/show_bug.cgi?id=386900

Fabian Vogt  changed:

   What|Removed |Added

URL||https://phabricator.kde.org
   ||/D8828

--- Comment #3 from Fabian Vogt  ---
(In reply to Martin Flöser from comment #2)
> The protocol provides a preferred flag on the mode. You might be able to
> verify with weston_info that KWin sets the preferred flag correctly.

I skipped that step as it has to be added to kscreen anyway and it looks like
it works fine: https://phabricator.kde.org/D8828

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 386900] KScreen picks wrong resolution in QEMU on wayland

[Martin Flöser]

https://bugs.kde.org/show_bug.cgi?id=386900

--- Comment #2 from Martin Flöser  ---
The protocol provides a preferred flag on the mode. You might be able to verify
with weston_info that KWin sets the preferred flag correctly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 386900] KScreen picks wrong resolution in QEMU on wayland

[Fabian Vogt]

https://bugs.kde.org/show_bug.cgi?id=386900

Fabian Vogt  changed:

   What|Removed |Added

 CC||mgraess...@kde.org
  Component|kded|common

--- Comment #1 from Fabian Vogt  ---
Looks like this is a bug in QEMU, some kind of allocation failure. Probably
some kind of internal buffer is too small... Anyway, this shouldn't be
triggered at all automaticaly.

I can easily explain the difference to X now: It seems like libkscreen does not
handle the preferred attribute on kwayland modes yet, so it always picks the
one with the biggest area (+ refresh rate).

I suggest adding the current mode as preferred mode on startup - this should be
the native resolution (or at least a mode that works) in most cases anyway and
can easily be overwritten on the kernel cmdline.

-- 
You are receiving this mail because:
You are watching all bug changes.