https://bugs.kde.org/show_bug.cgi?id=450337
--- Comment #20 from Nate Graham ---
Also, remember to submit one bug report per issue, rather than lumping
everything into a single bug report. Thanks again!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450337
--- Comment #19 from Nate Graham ---
This is a fairly old bug report and the code has changed a lot since you
reported it. There's a very good chance the issue you're now experiencing is
caused by something else, even if the outward symptoms look and
https://bugs.kde.org/show_bug.cgi?id=450337
--- Comment #18 from Dick Tracey ---
Can we open this bug? This is still happening on kwin-5.27.9 with
qt5-base-5.15.11+kde+r138
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450337
--- Comment #17 from Dick Tracey ---
I haven't been able to reproduce this bug on Wayland.
(Unfortunately, Wayland isn't a viable workaround at the moment, because
kwin_wayland+nvidia has its own set of more serious problems: on wake up, the
screen
https://bugs.kde.org/show_bug.cgi?id=450337
Nate Graham changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=450337
--- Comment #15 from Bruno Friedmann ---
Created attachment 148115
--> https://bugs.kde.org/attachment.cgi?id=148115=edit
New crash information added by DrKonqi
kwin_x11 (5.24.4) using Qt 5.15.2
- What I was doing when the application crashed:
With
https://bugs.kde.org/show_bug.cgi?id=450337
Bruno Friedmann changed:
What|Removed |Added
CC||br...@ioda-net.ch
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=450337
--- Comment #14 from Dick Tracey ---
More kwin crashes trigger by monitor wake up, from CLI:
Unable to start Dr. Konqi
Re-raising signal for core dump handling.
Application::crashHandler() called with signal 11; recent crashes: 1
22 --
https://bugs.kde.org/show_bug.cgi?id=450337
Dick Tracey changed:
What|Removed |Added
Version|5.24.1 |5.24.3
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=450337
Dick Tracey changed:
What|Removed |Added
Summary|Crash in|Multiple issues when
https://bugs.kde.org/show_bug.cgi?id=450337
--- Comment #9 from Dick Tracey ---
I originally experienced the problems in my original report with 495 drivers,
and upgrading to 510 didn't fix, so that appears to be a different bug.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=450337
--- Comment #8 from Krzysztof Kundzicz ---
(In reply to Dick Tracey from comment #6)
> Thanks! Can you try setting the primary monitor that is being turned on/off
> to be on the right in Display Configuration, and doing the experiment again?
> I only
https://bugs.kde.org/show_bug.cgi?id=450337
--- Comment #7 from Ilya Bizyaev ---
Created attachment 146958
--> https://bugs.kde.org/attachment.cgi?id=146958=edit
New crash information added by DrKonqi
kwin_x11 (5.24.1) using Qt 5.15.2
- What I was doing when the application crashed:
My
https://bugs.kde.org/show_bug.cgi?id=450337
Ilya Bizyaev changed:
What|Removed |Added
CC||bizy...@zoho.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=450337
--- Comment #6 from Dick Tracey ---
Thanks! Can you try setting the primary monitor that is being turned on/off to
be on the right in Display Configuration, and doing the experiment again? I
only get the crash if that monitor is located at (1920,0) and
https://bugs.kde.org/show_bug.cgi?id=450337
Krzysztof Kundzicz changed:
What|Removed |Added
CC||athantor+kdeb...@athi.pl
--- Comment #5
https://bugs.kde.org/show_bug.cgi?id=450337
--- Comment #4 from Dick Tracey ---
It doesn't appear this is related to 450068, I get the same output
$ ls /sys/class/drm
card0 card0-HDMI-A-1 card0-HDMI-A-2 card0-VGA-1 renderD128 version
before & after. I discovered something weird though. In
https://bugs.kde.org/show_bug.cgi?id=450337
--- Comment #3 from Dick Tracey ---
Yes, indeed! Apologies for forgetting to mention in the first place. The
primary/slow MSI monitor is connected through DisplayPort whereas the other one
is HDMI.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=450337
Nate Graham changed:
What|Removed |Added
Target Milestone|1.0 |---
CC|
19 matches
Mail list logo
