https://bugs.kde.org/show_bug.cgi?id=431968
Zamundaaa changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/k
https://bugs.kde.org/show_bug.cgi?id=431968
Zamundaaa changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
|
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #27 from Zamundaaa ---
If you have more questions not directly related to this bug you can use the
direct message function on Reddit. Thanks again for testing :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #26 from Zamundaaa ---
I honestly skipped installation of dependencies and just built things with
kdesrc-build and installed non-KDE dependencies as needed. No idea if that
could lead to problems but worked fine for the last year or so.
If
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #25 from Tito ---
Thanks so mutch for the help!
I've been trying to install and compile everything from source with
kdesrc-build, but i ran in a lot of dependencies even after following this
guide
https://community.kde.org/Guidelines_and_HOW
https://bugs.kde.org/show_bug.cgi?id=431968
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #24 from Zamundaaa ---
Thank you so much for your patience and testing! The patches are up and should
get merged soon.
For the problem with the desktop not starting (or crashing) you should make a
bug report for plasmashell, although it's p
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #23 from Tito ---
Now it works! as far as i can test tho, as i still cat get to the desktop.
but on the igpu side everything is fine, rendering correctly, no tearing, no
glitches!
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #22 from Zamundaaa ---
Sorry about that, I forgot to remove that line. Instead of downloading it again
you can just remove it yourself.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #21 from Tito ---
it gives me some compilation errors and it stops. i did the same thing for the
previous patches, might it be a but in the code?
kwin/build/plugins/platforms/drm/KWinWaylandDrmBackend_autogen/EWIEGA46WW/../../../../../../pl
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #20 from Zamundaaa ---
I believe those glitches are caused by missing VSync, which should be fixed by
https://invent.kde.org/plasma/kwin/-/merge_requests/642. If you could test that
as well that would be very nice.
I put both of these patch
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #19 from Tito ---
Great progress!
Now it kinda works, i still have problems with plasma, as i cant really get to
the desktop, but thanks to the drop-down terminal i can run something like
chromium and move it in to every monitor to see if it
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #18 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/kwin/-/merge_requests/649
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #17 from Zamundaaa ---
Hmm so I did find some more information on the function I was using and one's
not supposed to use it directly, it'll only cause problems.
I'm rather confident to have found the actual source of the problem with the
or
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #16 from Zamundaaa ---
The CPU usage is definitely from the beta - I had such things happen with my
git master installation a while ago. You just need to reboot and it will go
away, at least until you log in and out again.
About the black s
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #15 from Tito ---
I might add that i got the same behavior with the cpu usage, and the top cpu
intensive programs are this.
as i never got anything like this, might this be another bug with the beta or
the patch?
https://imgur.com/R62OXCc
T
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #14 from Tito ---
Attached the log file to the thread.
This time the behavior war different, the two screens black from no signal, no
deskop, but yukuake was working and applications opened from the console too
(chromium).
i dont thin this
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #13 from Tito ---
Created attachment 135313
--> https://bugs.kde.org/attachment.cgi?id=135313&action=edit
Wayland session log file
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #12 from Zamundaaa ---
Well, that's good news then! I'll have to ask if the function I used has any
caveats (there is effectively 0 documentation about it) but hopefully we can
get this in for the release of 5.21 then :)
I believe some of t
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #11 from Tito ---
This patch seems to behave a bit better:
First try the two screens connected to the igpu didnt have any graphical
issues, although i didnt managed to go all the way to the desktop as it stalled
to a black screen with the cu
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #10 from Zamundaaa ---
Okay, that's not good but I kinda expected it. No need to try the other method,
the result won't be any different.
I have one more easy thing to try that might work. For testing that use
git clone https://invent.kde.o
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #9 from Tito ---
i followed the second method, and the result was pretty similar.
the screens connected to the intel igpu behaved like shown before, tho after
the loading of the logo finished, the desktop remained black, and any attempt
at
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #8 from Zamundaaa ---
That reference is for KDE4, I'm not surprised that it doesn't work. You should
probably remove env file, it could potentially cause problems.
For compiling KWin you can either use kdesrc-build
(https://community.kde.or
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #7 from Tito ---
As of right now it just crashed to the login manager a few seconds after i try
to login. although i dont really know if i did the stuff right, heres it what i
did:
applied the pach using the file provided.
compiled and inst
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #6 from Zamundaaa ---
It's possible that this patch could affect your setup:
https://invent.kde.org/plasma/kwin/-/merge_requests/642
It most likely won't solve your problem but if you can test if it changes
anything that would be nice.
--
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #5 from Zamundaaa ---
Okay, that looks all good, and reinforces my suspicions about the linear
format. I'll see what I can do
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #4 from Tito ---
All good. Here is the new file:
https://pastebin.com/fDGGTMyS
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #3 from Zamundaaa ---
It looks like the environment variable is missing; I probably got it wrong,
sorry about that. Try with "QT_LOGGING_RULES=kwin_*.debug=true" instead, that
will enable all debugging
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=431968
--- Comment #2 from Tito ---
Here is attached the log file.
https://pastebin.com/EZC1mMhs
i needet to use pastebin because the Add an attachment function gives me a
permession error. (ERR_ACCESS_DENIED)
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=431968
Zamundaaa changed:
What|Removed |Added
Assignee|kwin-bugs-n...@kde.org |xaver.h...@gmail.com
Ever confirmed|0
30 matches
Mail list logo
