https://bugs.kde.org/show_bug.cgi?id=469160
Nate Graham changed:
What|Removed |Added
Component|common |kscreen-doctor
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=469160
Nate Graham changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=469160
David Edmundson changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
CC|
https://bugs.kde.org/show_bug.cgi?id=469160
--- Comment #11 from Misha Labjuk ---
(In reply to Nate Graham from comment #10)
> Thanks for the patches, Misha! Can you submit them at
> https://invent.kde.org/frameworks/kwayland/-/merge_requests so they get seen
> by
> developers?
Done.
https://bugs.kde.org/show_bug.cgi?id=469160
--- Comment #10 from Nate Graham ---
Thanks for the patches, Misha! Can you submit them at
https://invent.kde.org/frameworks/kwayland/-/merge_requests and
https://invent.kde.org/plasma/kscreen/-/merge_requests so they get seen by
developers?
--
You
https://bugs.kde.org/show_bug.cgi?id=469160
--- Comment #9 from Misha Labjuk ---
This two patches works for me.
Main reason for this issue is kwayland cleanup called by
QCoreApplication::quit() signal free registry structure.
Registry is a wayland proxy object and it can't be freed before
https://bugs.kde.org/show_bug.cgi?id=469160
--- Comment #8 from Misha Labjuk ---
Created attachment 160373
--> https://bugs.kde.org/attachment.cgi?id=160373=edit
kscreen use kwayland registry with foreign support
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469160
--- Comment #7 from Misha Labjuk ---
Created attachment 160372
--> https://bugs.kde.org/attachment.cgi?id=160372=edit
kwayland patch to support foreing connection by reister
Do not break foreign wayland connection during registry destroy.
--
You
https://bugs.kde.org/show_bug.cgi?id=469160
Misha Labjuk changed:
What|Removed |Added
Keywords||wayland
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=469160
Misha Labjuk changed:
What|Removed |Added
CC||spiked@gmail.com
--- Comment #6 from Misha
https://bugs.kde.org/show_bug.cgi?id=469160
--- Comment #5 from mooodyhun...@outlook.com ---
Tested with `KSCREEN_BACKEND=KWayland` vs QScreen... and yes the problem has
never occurred with QScreen backend.
> i feel like our backtraces are maybe a red herring?
Yes so do I
--
You are
https://bugs.kde.org/show_bug.cgi?id=469160
--- Comment #4 from Ryan Rix ---
```
~ $ KSCREEN_BACKEND=QScreen kscreen-doctor --json | jq .outputs[0].name
kscreen.qscreen: Screen added QScreen(0x12e4010, name="DSI-1") "DSI-1"
warning: queue 0x12f48e0 destroyed while proxies still attached:
https://bugs.kde.org/show_bug.cgi?id=469160
Ryan Rix changed:
What|Removed |Added
CC||r...@n.rix.si
--- Comment #3 from Ryan Rix ---
https://bugs.kde.org/show_bug.cgi?id=469160
--- Comment #2 from mooodyhun...@outlook.com ---
This looks strange to me as well, after digging into the problem, it seems to
be:
- We are using `QGuiApplication`, so that Qt's platform theme is loaded (in my
case it's
https://bugs.kde.org/show_bug.cgi?id=469160
Nate Graham changed:
What|Removed |Added
Summary|kscreen-doctor segmentation |kscreen-doctor segmentation
15 matches
Mail list logo
