https://bugs.kde.org/show_bug.cgi?id=432707
Zamundaaa changed:
What|Removed |Added
Version Fixed In|5.23|5.22.0
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=432707
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=432707
Nate Graham changed:
What|Removed |Added
Version Fixed In||5.23
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=432707
Zamundaaa changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=432707
Shawn Starr changed:
What|Removed |Added
Attachment #137848|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #82 from Shawn Starr ---
With latest changes to dumb-import both displays turn on now!
Attached outputs
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #81 from Shawn Starr ---
Created attachment 137851
--> https://bugs.kde.org/attachment.cgi?id=137851=edit
dumb-import - April 23rd - log - Latest
dumb-import - April 23rd - log - Latest
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=432707
Shawn Starr changed:
What|Removed |Added
Attachment #137810|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #79 from Shawn Starr ---
Created attachment 137838
--> https://bugs.kde.org/attachment.cgi?id=137838=edit
dumb-import branch only - latest test
dumb-import branch only - latest test
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=432707
Shawn Starr changed:
What|Removed |Added
Attachment #137797|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=432707
Shawn Starr changed:
What|Removed |Added
Attachment #137782|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=432707
Shawn Starr changed:
What|Removed |Added
Attachment #137697|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #75 from Shawn Starr ---
Created attachment 137781
--> https://bugs.kde.org/attachment.cgi?id=137781=edit
New log from latest testing - dumb-import + primary-gpu-context + fix-hotplug
New log from latest testing - dumb-import +
https://bugs.kde.org/show_bug.cgi?id=432707
Shawn Starr changed:
What|Removed |Added
Attachment #136854|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #73 from Shawn Starr ---
Interesting results with kwin branches:
work/zamundaaa/dumb-import + work/primary-gpu-context
merged together with latest kwayland-server master + protocols.
I *DO* get the DisplayPort turning on, although only
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #72 from Shawn Starr ---
Created attachment 137698
--> https://bugs.kde.org/attachment.cgi?id=137698=edit
Coredump from Kwin
Coredump from the session tested,segfaulted
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #71 from Shawn Starr ---
Created attachment 137697
--> https://bugs.kde.org/attachment.cgi?id=137697=edit
New log from latest code changes
New log from latest code changes
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #70 from Shawn Starr ---
Coming back to the KDE side of things.. right now nothing works for me. I can
wait and will have to wait. I would prefer we have a common EDID/display
detection framework not one for every DE though...
--
You are
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #69 from Fervi ---
Sway supports Nvidia, but without support
https://github.com/swaywm/sway/blob/master/sway/main.c#L103
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #68 from Shawn Starr ---
You should sort that out with them. Upon installing Sway for Fedora, starting
Sway from SDDM, both displays turned on immediately.
So...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #67 from Neal Gompa ---
(In reply to Shawn Starr from comment #66)
> That's not confirmed... and wlroots devs dispute this im told on IRC so...
* https://github.com/swaywm/sway/wiki#nvidia-users
*
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #66 from Shawn Starr ---
That's not confirmed... and wlroots devs dispute this im told on IRC so...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #65 from Neal Gompa ---
(In reply to Shawn Starr from comment #64)
> I hate to bring this up but: https://gitlab.com/kwinft/kwinft/-/issues/137
>
> Why exactly are we not using wlroots? It's not exactly 'fun' to have to
> implement your
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #64 from Shawn Starr ---
I hate to bring this up but: https://gitlab.com/kwinft/kwinft/-/issues/137
Why exactly are we not using wlroots? It's not exactly 'fun' to have to
implement your own drm plugin for kwin, deal with all the
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #63 from Zamundaaa ---
The laptop display not turning on is unexpected... Maybe I can still find a
solution that can be implemented somwhat quickly but it looks like it's gonna
take a while
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #62 from Shawn Starr ---
Created attachment 137443
--> https://bugs.kde.org/attachment.cgi?id=137443=edit
Wayland Errors Log - Existing user - Laptop screen made primary - with
work/zamundaaa/dumb-import branch for kwin
Wayland Errors
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #61 from Shawn Starr ---
Created attachment 137442
--> https://bugs.kde.org/attachment.cgi?id=137442=edit
Wayland Errors Log - New user - with work/zamundaaa/dumb-import branch for kwin
Wayland Errors Log - New user - with
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #60 from Shawn Starr ---
Results:
In the first log, I created a new user
- Started Plasma Wayland session, Laptop screen and DisplayPort didnt turn on,
VT switched, the DisplayPort turned on saw an X cursor but nothing else, laptop
screen
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #59 from Shawn Starr ---
Created attachment 137423
--> https://bugs.kde.org/attachment.cgi?id=137423=edit
Wayland Errors Log - with work/zamundaaa/dumb-import branch for kwin
Wayland Errors Log - with work/zamundaaa/dumb-import branch
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #58 from Shawn Starr ---
Well, something appeared but it was garbage output on the DisplayPort.
I had to alt-tab to switch VT then back and then I noticed my laptop display
lit up.
Attached is log.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #57 from Shawn Starr ---
Will compile and report back today
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #56 from Zamundaaa ---
Can you test if https://invent.kde.org/plasma/kwin/-/merge_requests/832 works?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
Nate Graham changed:
What|Removed |Added
CC||slackma...@gmail.com
--- Comment #55 from Nate
https://bugs.kde.org/show_bug.cgi?id=432707
Alex changed:
What|Removed |Added
CC||alex...@protonmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=432707
Nate Graham changed:
What|Removed |Added
CC||thunderstormpol...@o2.pl
--- Comment #54 from
https://bugs.kde.org/show_bug.cgi?id=432707
Nate Graham changed:
What|Removed |Added
Priority|NOR |VHI
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=432707
Nate Graham changed:
What|Removed |Added
See Also|https://bugs.kde.org/show_b |
|ug.cgi?id=425586
https://bugs.kde.org/show_bug.cgi?id=432707
Nate Graham changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #53 from Shawn Starr ---
I should note when I moved the screen to the DisplayPort, then maximized it was
returned to the laptop screen. So it was not allowing it to be displayed on the
DisplayPort output which didn't light up.
I did see in
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #52 from Shawn Starr ---
Created attachment 137046
--> https://bugs.kde.org/attachment.cgi?id=137046=edit
Kwin Kwayland-server new log
Kwin Kwayland-server new log
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #51 from Shawn Starr ---
I tried again, explicitly even set DRI_PRIME to right GPU, attached is new
wayland-errors log file.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #50 from Shawn Starr ---
>From my Xorg config I have DRI_PRIME=0
OpenGL renderer string: AMD Radeon HD 8950 (BONAIRE, DRM 3.40.0,
5.10.14-200.fc33.x86_64, LLVM 11.1.0)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 21.0.0
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #49 from Shawn Starr ---
Should be, DRI_PRIME is set, but I'll double check and or enforce if its not.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #48 from Zamundaaa ---
Are you sure the game ran on the dedicated GPU? The log suggests to me that it
probably wasn't
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
Shawn Starr changed:
What|Removed |Added
Attachment #136828|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #46 from Shawn Starr ---
Does not work.
I even tried Wine with League of Legends, moved window to other screen,
alt+enter but it moved the full screen to the laptop output.
Attached the is the log with League of Legends
--
You are
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #45 from Shawn Starr ---
I will try that in a moment...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #44 from Zamundaaa ---
Okay now the interesting bit would be if fullscreen apps running through
Xwayland make the display work - with direct scanout they bypass the normal
multi-GPU mechanism. So just use any game from Steam or install
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #43 from Shawn Starr ---
I even tried disconnecting from my DisplayPort KVM switch, same result, so that
eliminates that.
If this is a kernel bug, why does this only manifest with XWayland and not X11?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #42 from Shawn Starr ---
Yes, if I make a new user, XWayland starts only on the Laptop display, I *can*
drag windows to the external display.
Kscreen does detect this but no display, I do see attempts to power it on then
it fails the
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #41 from Shawn Starr ---
Well, right now when i try starting with XWayland via SDDM, it just locks up
the screen I can VT switch however..
I will create a new user and see if any .config from KDE is causing
XWayland/X11 confusion with
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #40 from Zamundaaa ---
I know that the display doesn't turn on but you should be able to move windows
to it on master.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #39 from Shawn Starr ---
Well, its not even a game that works, Plasma/Kscreen doesnt detect the screen.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #38 from Zamundaaa ---
I'll be adding a CPU fallback mode for multi-GPU soon™, that would definitely
work.
Ideally we can still get it working with hardware acceleration for 5.22
though...
Could you check if on master a fullscreen game
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #37 from Shawn Starr ---
Oh there's no coredump now, systemd coredumpctl shows none.
This core issue remains, I just happened to crash kwin before the above commit
is already in the master branch.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=432707
Aleix Pol changed:
What|Removed |Added
CC||aleix...@kde.org
--- Comment #36 from Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=432707
Shawn Starr changed:
What|Removed |Added
Attachment #136749|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #34 from Shawn Starr ---
Well, the coredump is fixed, and it shows a lot more of the error...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #33 from Zamundaaa ---
Test https://invent.kde.org/plasma/kwin/-/merge_requests/756 that's rebased.
The crash should be fixed, the behavior of the monitor will most likely not
change though
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #32 from Shawn Starr ---
Will test this commit and report back
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #31 from Zamundaaa ---
Git commit 6569bf80c37ea46e7507fac17b9f1162b9a9978e by Xaver Hugl.
Committed on 18/03/2021 at 14:22.
Pushed by zamundaaa into branch 'master'.
EglGbmBackend: use output reference
M +2-2
https://bugs.kde.org/show_bug.cgi?id=432707
Shawn Starr changed:
What|Removed |Added
Attachment #136070|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #29 from Shawn Starr ---
Created attachment 136749
--> https://bugs.kde.org/attachment.cgi?id=136749=edit
Stack dump
Stack dump
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #28 from Shawn Starr ---
GDB stack dump
$ sudo gdb --core
core.kwin_wayland.1000.55d0822d350d434bb3a76b384eae7800.1445.161592086800
GNU gdb (GDB) Fedora 10.1-14.fc35
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #27 from Shawn Starr ---
I tried using:
gdb -batch -ex "set logging file kwin_wayland.gdb" -ex "set logging on" -ex
"continue" -ex "thread apply all backtrace"-ex quit --args kwin_wayland
--libinput --drm
While that worked, oddly the
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #26 from Zamundaaa ---
Log one is from 5.21, and log two is from my merge request.
As I undertand it, 5.21 doesn't show anything and my merge request makes the
session crash? It would be interesting if master crashes as well.
You can get
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #25 from Shawn Starr ---
KWin debugging isntructions:
echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
sudo gdb -pid $(pidof kwin_wayland) -batch -ex "set logging file
kwin_wayland.gdb" -ex "set logging on" -ex "continue" -ex "thread
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #24 from Shawn Starr ---
This was from master branch, in this case how can I get a gdb crash dump? Are
you on IRC? :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #23 from Zamundaaa ---
Can you get a backtrace of the crash? And can you reproduce it on master?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #22 from Shawn Starr ---
Created attachment 136708
--> https://bugs.kde.org/attachment.cgi?id=136708=edit
Wayland Error log #2
Wayland Error log #2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #21 from Shawn Starr ---
Well I got built, it is failing attached is wayland-errors log.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
Neal Gompa changed:
What|Removed |Added
CC||ngomp...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #20 from Shawn Starr ---
Or if I can apply this patch as part of building the Fedora RPM.. might try
that first
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #19 from Shawn Starr ---
I need to refresh my KDE build outside of using Fedora RPMs, ill gget back to
you on this,
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #18 from Zamundaaa ---
Does the patch fix the problem (or at least change anything)? In theory the two
function calls should do the same but it's worth a try
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
Bug Janitor Service changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #16 from Shawn Starr ---
I use amdgpu, disabled radeon for CIK.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #15 from Zamundaaa ---
What I mean is that there's probably some edge-case or assumption about the
driver that we're not handling correctly.
Are you using the amdgpu or radeon kernel driver? IIRC for a few of those old
cards radeon is
https://bugs.kde.org/show_bug.cgi?id=432707
--- Comment #14 from Shawn Starr ---
hmm, well since it works with Xorg, the driver seems ok, both the DRM kernel,
DRI side at least.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432707
Zamundaaa changed:
What|Removed |Added
Product|KScreen |kwin
Version|git
80 matches
Mail list logo
