https://bugs.kde.org/show_bug.cgi?id=386490
--- Comment #13 from Martin Flöser ---
(In reply to Bhushan Shah from comment #12)
> Can I re-open this bug, the commit above fixes the issue of crash, but right
> after starting plasma kwin_wayland is hung, and there is no mouse pointer as
> well, so i
https://bugs.kde.org/show_bug.cgi?id=386490
--- Comment #12 from Bhushan Shah ---
Can I re-open this bug, the commit above fixes the issue of crash, but right
after starting plasma kwin_wayland is hung, and there is no mouse pointer as
well, so it's still impossible to interact with Plasma.. or s
https://bugs.kde.org/show_bug.cgi?id=386490
Martin Flöser changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kwi
|
https://bugs.kde.org/show_bug.cgi?id=386490
--- Comment #10 from Martin Flöser ---
Thanks for testing. Looks like init on DrmOutput fails. I'll have a look.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=386490
--- Comment #9 from Fabian Vogt ---
(In reply to Martin Flöser from comment #8)
> Possible patch at: https://phabricator.kde.org/D8752
I tried this patch and kwin still crashes in QEMU, but at a different place now
at least:
#0 KWin::DrmOutput::pixel
https://bugs.kde.org/show_bug.cgi?id=386490
Martin Flöser changed:
What|Removed |Added
URL||https://phabricator.kde.org
|
https://bugs.kde.org/show_bug.cgi?id=386490
Bhushan Shah changed:
What|Removed |Added
CC||bhus...@gmail.com
--- Comment #7 from Bhushan Sh
https://bugs.kde.org/show_bug.cgi?id=386490
--- Comment #6 from Martin Flöser ---
As a workaround you could also
export KWIN_DRM_NO_AMS=1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=386490
Fabian Vogt changed:
What|Removed |Added
CC||fab...@ritter-vogt.de
--- Comment #5 from Fabian
https://bugs.kde.org/show_bug.cgi?id=386490
Martin Flöser changed:
What|Removed |Added
Component|wayland-generic |platform-drm
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=386490
--- Comment #4 from Martin Flöser ---
I would say all access needs guarding. My interpretation of
https://01.org/linuxgraphics/gfx-docs/drm/drm-kms-properties.html is that the
properties are not mandatory. For our usage rotation is clearly optional so w
https://bugs.kde.org/show_bug.cgi?id=386490
--- Comment #3 from Roman Gilg ---
Yes, that's a good idea. We could then decide to not use this
plane/crtc/connector.
That said, my assumption is that for an atomic mode property this should never
happen. But since we would do this check only once at
https://bugs.kde.org/show_bug.cgi?id=386490
--- Comment #2 from David Edmundson ---
That still leaves an inconsistency where you're guarding the insert in
initProps but not guarding access.
If you're gonna do that, you should error on initProps if one of the other
props doesn't exist.
--
You a
https://bugs.kde.org/show_bug.cgi?id=386490
--- Comment #1 from Roman Gilg ---
The problem seems to be, that not all drivers export the newly queried
"rotation" property to user space in contrast to the atomic mode setting
propertiers, which are expected to all get exported to my knowledge.
The
https://bugs.kde.org/show_bug.cgi?id=386490
David Edmundson changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
15 matches
Mail list logo
