https://bugs.kde.org/show_bug.cgi?id=448778
Zamundaaa changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=448778
aiamuzz changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #29 from aiamuzz ---
@Zamundaaa ... any suggestions on the following ?
https://github.com/linuxdeepin/developer-center/issues/3480#issuecomment-1323123155
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #28 from aiamuzz ---
@Zamundaaa ... firstly apologies for what may seem spamming your thread for
additional help ... it only goes to show my desperation ... apologies for the
same.
Please find the commit from my distro team ...
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #27 from aiamuzz ---
I am guessing my fix lies in the following 3 files ... understanding code and
what it does is way above my paygrade ...
https://github.com/linuxdeepin/deepin-kwin/blob/master/plugins/platforms/drm/screens_drm.cpp
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #26 from aiamuzz ---
I know at the risk of sounding foolish ... will this do the trick ?
your MR ... for the latest version
- props->refreshRate = mode["refresh"].toDouble() * 1000;
+ props->refreshRate =
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #25 from aiamuzz ---
oh ok ... seems like the exact same file ... "drm_backend.cpp" ... the
implementation however seems quite different to the one you have in the latest
version.
***
//2.init wayland output device
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #24 from aiamuzz ---
apologies for trying to be self reliant ... I am the only one facing this
issues it seems ... so trying to help myself ...
could these be the possible file that needs the corrected code ?
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #23 from aiamuzz ---
(In reply to Zamundaaa from comment #22)
> Yes, that looks like the same underlying problem, no further testing is
> needed. We don't support such old versions and especially not forks of them
> though.
>
> The things
https://bugs.kde.org/show_bug.cgi?id=448778
Zamundaaa changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #21 from aiamuzz ---
I notice the following ...
Extended monitor ...
Resolution : 1920 x 1080 (Recommended)
Refresh Rate : 60Hz (Recommended)
Laptop Screen ...
Resolution : 1920 x 1080 (Recommended)
Refresh Rate : 60.01Hz (Recommended)
I
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #20 from aiamuzz ---
(In reply to Zamundaaa from comment #19)
> (In reply to aiamuzz from comment #18)
> > @zamundaaa, I will open another bug if you so wish, but the symptoms are the
> > same as reported by @Matej Mrenica.
>
> Can you
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #19 from Zamundaaa ---
(In reply to aiamuzz from comment #18)
> @zamundaaa, I will open another bug if you so wish, but the symptoms are the
> same as reported by @Matej Mrenica.
Can you test if it happens on Wayland as well?
Also, can you
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #18 from aiamuzz ---
@zamundaaa, I will open another bug if you so wish, but the symptoms are the
same as reported by @Matej Mrenica.
(as replied by Matej Mrenica from comment #8)
> In the log I provided I unplug the cable before 08:52:41,
https://bugs.kde.org/show_bug.cgi?id=448778
aiamuzz changed:
What|Removed |Added
Resolution|FIXED |---
Component|platform-drm
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #16 from Zamundaaa ---
Wayland is not involved with what KWin displays. Please create a new bug report
here
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #15 from Random Guy ---
(In reply to Zamundaaa from comment #14)
> Please open a new bug report for that issue, it doesn't sound related at a
> first glance; KWin crashing does not make your monitors hang
The monitors are not actually
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #14 from Zamundaaa ---
Please open a new bug report for that issue, it doesn't sound related at a
first glance; KWin crashing does not make your monitors hang
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448778
Random Guy changed:
What|Removed |Added
CC||ericgreenwood...@gmail.com
--- Comment #13 from
https://bugs.kde.org/show_bug.cgi?id=448778
Nate Graham changed:
What|Removed |Added
Version Fixed In||5.24
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=448778
Zamundaaa changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=448778
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #10 from Matej Mrenica ---
Latest version of the MR fixes this issue. Unplugging the cable doesn't make
Kwin crash anymore.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #9 from Zamundaaa ---
Sorry, didn't scroll up enough. KWin reads the configuration from KScreen, it
is correct (eDP-1 is supposed to be enabled again) and then it gets applied...
But it silently fails, which it really should not.
I could
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #8 from Matej Mrenica ---
In the log I provided I unplug the cable before 08:52:41, is that what you are
asking? After that only a cursor appears on my laptop screen and after a few
seconds Plasma is restarted (only with systemd startup).
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #7 from Zamundaaa ---
Did you reproduce the crash before getting the log? It only shows the external
output being connected, not removed. Up to that point everything looks correct
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #6 from Matej Mrenica ---
OK, now it gives an output: https://pastebin.com/Jb6T2m5F
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #5 from Zamundaaa ---
Maybe logging in the legacy session is still broken... Try
$ kwriteconfig5 --file startkderc --group General --key systemdBoot true
and reboot.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=448778
Vlad Zahorodnii changed:
What|Removed |Added
Keywords||wayland
Component|wayland-generic
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #4 from Matej Mrenica ---
I must be doing something wrong because neither of those commands produce any
output.
What I did:
I cloned kwin branch Plasma/5.24 and applied your patch.
Then I built and installed kwin with: "cmake -B build
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #3 from Zamundaaa ---
I added a bunch of debugging prints to the MR. Can you trigger the crash with
that and then attach the logs for kwin_wayland_drm here?
You can get them with either
$ grep kwin_wayland_drm
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #2 from Matej Mrenica ---
(In reply to Nate Graham from comment #1)
> Does this happen when *not* running with that merge request? If not, can you
> comment in that merge request instead of here?
Yes: https://pastebin.com/nns7Jn5b I could
https://bugs.kde.org/show_bug.cgi?id=448778
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--- Comment #1 from Nate Graham
https://bugs.kde.org/show_bug.cgi?id=448778
Matej Mrenica changed:
What|Removed |Added
CC||matejm98m...@gmail.com,
|
34 matches
Mail list logo
