[WORKAROUND FOUND] Full System Crash (Cannot Alt+F3 to change tty)
Please help if you're able, I've been fighting this for months on other distros, and it was working on Bazzite until 20 min ago, so I don't know what happened 😭
I believe it's a KDE bug, but since it was working until only 20 min ago, it has to be some configuration of some kind.
Solution:Jump to solution
Better workaround is to put
KWIN_DRM_NO_DIRECT_SCANOUT=1 into /etc/environment and then reboot. There is a small hit to performance (I haven't noticed any hit, but KDE says there is), but the issue is now completely gone. I don't have to use gamescope and I can turn the steam overlay back on too224 Replies
try ctrl+alt+f3 for tty
oh oops. Typo. That's the thing that doesn't work
drat. I was hoping it would've been that simple
I'm going to try an
os-tree reset to see if I can fix it, but I really don't know what I did other than install easyeffects
would've loved that 😅
though the bug would've still been presentThis is what happens right before the crash too: https://imgur.com/a/5jTZrSv
Imgur
Untitled Album
the main screen fails to render anything that's happening, but OBS can see it just fine
The bug occured right after I layered
easyeffects, and I know that messes with pipewire stuff, so I'm wondering if it broke something in pipewire and now things are borkedit shouldn't break something in pipewire, but try to uninstall the package first before doing a full
rpm-ostree reset
rpm-ostree uninstall <package>I did 😭 easyeffects is gone, but the issue persists
already rebooted?
yeah
I rebooted and rolled back to previous image technically
but easyeffects wasn't layered anymore
my hardware is a Framework 16 with dGPU, so I'm hoping that someone else with this hardware has a solution
if it's just me, then I'm uber confused
I'm gonna nuclear real quick after my meeting and try the reset
dammit, nuclear option didn't fix anything
I'm putting my two layers back lmao
just tried X11 and it doesn't load at all. Blank screen, can't ctrl+alt+f3 to change tty. Had to power-button
It seems to have 100% everything to do with my monitor. When I play the game on my laptop screen, everything works fine
in fact, if I move Timberborn to my laptop screen first, and then quit. No crash occurs
KDE completely borked lmao
OK so, I tried using HDMI instead of DP-Alt Mode, and THE BUG IS GONE
so it has something to do with the DP-Alt mode or DP itself. I don't have a USB to DP cable, but I'll grab one today and give it a go
however, it does appear that using my USBC dock with an HDMI output also causes a similar bug, so I wonder if the dock is also DP-alt mode or smth
@Kyle Gospo @matt_schwartz (effectively replying here, since it's better to keep the info centralized)
I've narrowed it down to specifically the USB-C port on the dedicated GPU AMD 7700s. If I use the side ports that are connected to the Motherboard, this issue does not occur. I'm going to open a ticket with Framework and possibly AMD? Since it appears that it's specific to the GPU and / or the GPU drivers instead of just a display port bug
for record-keeping: https://community.frame.work/t/usb-c-displayport-on-gpu-module-is-broken-on-linux/57557
Framework Community
USB-C DisplayPort on GPU module is broken on Linux
I have tried both Nobara and Bazzite so far, and these are both based on Fedora. Bazzite is a community-supported OS. When using the USB-C connection on the back of the GPU to connect to an external monitor, running certain games (Timberborn is extremely consistent) on Steam with KDE Wayland causes a full system crash. I cannot ctrl+alt+f3 to c...
is this stuff still happenning?
the first thing id do is just reboot and check what happened in the logs through
journalctl -b -1 -e -k
@Raevenantindeed it is: https://bugs.kde.org/show_bug.cgi?id=492428
That's got the journalctl stuff, though I just did
journalctl -b -1wait is that your bug report?
cool!
yep!
lemme check it out
i wonder what is happening
do you have the kernel dmesg logs?
journalctl -b -1 -k
not from that crash, but I have them from the last crash (literally my previous boot lmao)
its just complaining that its a kernel bug on the logs :p
could you dump that?
there ya go
kinda funny how consistent that is
yeah its insane
literally Turn on Timberborn, turn off timberborn, crash
but like does that only happen on kde?
dunno, haven't tried gnome
I can layer that on if you want me to test it
i think that would be the best first-step to check out what the hell is happening
like
Xwayland coredumps
kwin gets mad
and your system crashes
thats so weird
what image are you on?
looks like there's already a bug report for that speicific part of the issue
(tag in this case)
The problem here is on the kernel driver side, mostly. When a GPU reset happens, Xwayland goes down, and KWin has some blocking calls to Xwayland, so it can hang. Getting rid of those blocking calls is something we can hopefully do at some point, see bug 442846 for that, but the GPU resets should be fixed as well, or the game will still crash. You can report that at https://gitlab.freedesktop.org/mesa/mesa/-/issues
this was commented on my bug report like 10 min ago
oh LOL
lemme see
i wonder if it is xwayland + kwin being weird?
do you have gamescope on ur system?
maybe running the game through gamescope might weild some other results
yeah, seems like basically, the kernel shits itself, makes the GPU reset, killing xwayland. For whatever reason KWin hangs up when that happens
I can try that, is that a flatpak or a
ujust or smth?maybe you already have it on ur system
also, remind me how to get the tag?
oh yep, it came instaleld
try opening a terminal and typing
gamescope --help
sweeet
rpm-ostree status -v
should return a ton of stuff about ur imageso the proglem is. It's not happening right now for some stupid reason lmao
so I can't test anything 😅
it happend 30/30 tries all day, and suddenly it's not happening
jesus christ this is the worst kind of bug
ever
oh I know lmao
let me re-cable things to get the exact setup I had just a sec
wait do you have a broadcom wifi chip?
weird the kernel dump is super goofy
couldn't tell ya
well actually I can, lemme look it up
Xwayland goes down, and KWin has some blocking calls to Xwayland, so it can hang.bro.... try going into the game options and adding "gamescope" into the launch options
looks like it's not
Framework uses mediatek and Intel
The latter is the better one
oh!
I don't think I had an option when I put thogether the 16, so idk which one I've got XD
More than likely it's mediatek
apparently it is mediatek on the photo LOL
Yup
wait why, is that possibly relavent, or just interested?
idk the "wl" driver just showed up on the kernel dump
yeah, but you can buy a bunch of replacements on their website, so idk which one came default XD
imagine this whole time, my graphics card issues are because of the internet lmao
so right now though, I'm jacked in with ethernet, so the card isn't active
well, assuming that's even how that works
It's Ethernet-USBC
Anker dock
ok, we're back to the original buggy setup. USB-C DP Alt mode -> USB-C Input on 1st monitor -> DP Daisy Chain to second monitor
honestly like, i dont have any idea like why the hell your gpu driver segfaults when the gpu resets, but like, maybe using gamescope will be a patchwork solution for that for now
Xwayland goes down, and KWin has some blocking calls to Xwayland, so it can hang. Getting rid of those blocking calls is somet[...]if you are running xwayland while not on kwin itll not bring everything down :p
but of course, it's still not bugging out, so we're out of luck for continuing to debug unfortunately
oh yeah, gamescope is a different compositor, yeah?
yup!
oooooooooh, smart!
I'll give that a go next time this happens and let you know. Good if I ping you about it?
if you just run gamescope nested itll kill gamescope but not kwin
i think
LOL
yup its fine!
just make sure to add the... the....
the thing
gamescope on the game launch options
yuppers!
any particular args, or just the usual
-w -W -h -H etc?nah!
honestly maybe that wont work but lets see
Thanks a bunch! Having someone take a look is honestly a huge relief 😅 I've been having this issue for months, ever since KWin 6.1.2 came out
jeeez thats the worst
I think it's somehow a kwin specific bug, since on Nobara, if I downgraded to KWin 6.1.1, the bugs went away
like it can be so many weird things
oooooh
you couldve done a bisect to figure that out
idk what a bisect is
well, I know what one is in general but not in this case
like, not in the context of packages
literally the general thing
just like
testing 6.1.X breaks or not
and then narrowing down till we get a commit that makes everything break
OH that's exactly what I did more or less 😄
(probably some regression or someything)
downgraded plasma-workspace, kwin, and plasma-desktop, then suddenly wondered to myself if it was all or just one of those
oh LOL
upgraded them one by one, until eventually kwin broke it
ye!!!!
i wonder what regression made it break
beats me XD
like whats the last-known good release?
6.1.1?
6.1.1 for sure
well, idk I wasn't able to upgrade to 6.1.2
I skipped that one lmao
oh LOL shouldve tested that out!
but 6.1.3 definately breaks it
on accident XD
so
I had waited a bit to upgrade and it just skipped a package lmao, then when on 6.1.3, doing a
dnf downgrade dropped down to 6.1.1, so idkone of these releases broke it
also could've been all the way up at 6.1.3, but yeah
since the releases arent thaaaaat far apart it shouldnt be impossible to figure out LOL
but like honestly maybe you should test out GNOME if that happens again
just to see if its actually kwin crapping out
yeah XD I'll try gamescope first, then gnome
yup!!!
oh here's a question actually. So the original reason I switched to kde (apart from not liking Gnome's style in general) was because in X11, there was a very slight additional input lag that Gnome had over KDE. Is that still the case on wayland?
on KDE you could turn of compositing entirely, so I had added that to the gamescope arguments
i havent used X11 enough to have any idea what to tell ya :(
x11 was always kinda laggy on my machine for some reason
probably the latest GNOME is gonna be fine with that
X11 straight up won't boot on mine XD
but like im interested in something like
how long have you been using linux? you seem quite ingrained in the ecossystem honestly
also, what this means is that clearly you're the better IT professional. My PC recognized your power over Discord and started working when you looked at it
like 6 years haha
LOL gotta love these schrodinger's bugs
nice!
i havent been for quite as long but its pretty cool to see that!
did you like bazzite?
I followed the entire journey from
what is this linux thing? Seems neat
oh, the terminal is actually pretty awesome tbh
ubuntu -> mint -> ubuntu -> manjaro -> arch
holy crap its fun to use i3 and just make my own DE that's all my own
... uhh. Actually I kina just want a system that freaking works when I need it to
Fedora -> Nobara -> Bazziteso far so good! I actually installed Bazzite last night XD Took like 4 hours to migrate my Nobara installation over pretty cleanly, (including the bugs unfortunately lmao, I was trying to run from them)
im still on the i3 phase LOL
but I've got my dev environments in distroboxes, I've got 1Password working with fingerprint and SSH
hey, when it works, it works!
im in a super weird setup but gotta love those
im sure ur gonna like bazzite
and lets be honest, when shit hits the fan, it's the i3 vim-ninjas that usually know what's happening XD
its pretty nice having a simple setup because you really really can know what the hell is happening at all times
oh for sure. I had a setup that was pretty slick, and I even learned to use XMonad, which was a trip
but eventually, I just went to an "all defaults only" kind of solution hahaha
change as little as possible on my system so that it's easier to know whats going on when something breaks
oh ofc! makes sense honestly
btw, did you happen to see this video at the top? This is what I've been dealing with XD
oh! didnt see it
lemme see
what the hell
its like
working on the other monitor...?
wha....
thats so weird what
oh it's not even that
I tried to do a screen recording so that I could add it to the bug report
so I captured the screen (not the game)
and instead of recording what was happening, it recorded waht should have been happening
but only the mouse was rendering properly on the screen I was trying to play on
oh that narrows it down a bit
it just must be a kwin bug
so it's like, something weird where the actual visual data is still occuring, and whatever graphics pipeline OBS taps into to record is still sending it, but the monitor doesn't receive it properly
yeah
its so so so so weird
I really hope so
the GPU driver works fine! even the other screen works fine
unless you are using a capture card or something?
nope, no capture card! It's just OBS
and yeah, the laptop monitor works fine too
kwin is exploding trying to send the commits to the other monitor
ALSO also, the bug doesn't happen if I use my HDMI port on the side of the laptop, just the DP Alt-mode USBC cable on the back of my GPU
the HDMI port on the side is still technically USBC though, meaning it's still DP alt-mode, it's just connected to the motherboard instead of the GPU
soooo yeah 😂 a real fun bug, that's for sure
I gtg grab dinner, but thank you, thank you!! It's an insane relief having someone take as much time as you have to help me out 🙏
what a mess LOL
ill be here for a while! most likely asynchronously but ill be here
HOLY SHIT IT WORKS
no fucking way
LOL NO WAY
ooooooooh i dont remember how to fix that
looks like powering through does work, but I'd still love to not have it do that XD
i remember running into that at some point
oh yeah LOL
but like
is the game working fine?
like not breaking your entire pc
it does! (well, in the 20 seconds I tried it), and nope, quitting worked just fine, so it's still working 😄
yep, no bricks here
at the very least thats better LOL
gamescope -H 1080 -f --force-grab-cursor
oh yeah so much better
hey, do you know how to make the mouse speed not change inside gamescope? It's slower inside gamescope for some reasonyou probably dont need the --force-grab-cursor thing
unfortunately, I do 😭 when playing GW2, the mouse escapes the game
i havent ever changed mouse speed on gamescope tho
oh weird?
yeah
wait
are you running gamescope nested or the gamescope session?
uhhhhhhhh
idk
MANGOHUD=1 DRI_PRIME=1 DXVK_ASYNC=1 gamescope -H 1080 -f -- gamemoderun %command% -provider Portalwhen ur running the game, are-
oh ur nested
thats good yea its fine
also bazzite has the BORE scheduler, you dont need the
gamemoderun thing anymoreoh sick 😄
I'll still use it tho, since I actually use gamemoderun to modify my fan profiles in-game XD
and from what i know to use mangohud on gamescope you gotta use the --mangoapp flag now??
idk whats the proper thing tho
oh TRUE I forgot about that. Lemme do that
wait you have a nvidia gpu?
but yeah weird enough, when I add the
--force-grab-cursor thing, the mouse slows down by maybe 10-15%
no?
which flag do I apparetnly not need XDyou dont need DRI_PRIME i think
oh, probly not, that's left over from Nobara. It's an AMD thing too
don't need dri_prime
dxvk_async is dead
gamemoderun is detremental to performance on modern CPUs
LOL gotta love the completely deprecated command then
yeah serious
gamescope --mangoapp -W 1920 -H 1080 -w 1920 -h 1080 -f --force-grab-cursor -- %command% -provider Portal :P
you need the -w / -h flags to force the game to actually use the proper resolution
many games ive tested get super fuzzy? idk, weird somehow when running without those flagsaccording to the documentation, -w/-h should default to whatever -H/-W are, and if you don't specify -W, it assumes 16:9. But honestly the number of times their documentations been wrong 😅
its just that ive seen some of my games looking kinda weird without those
probably isnt necessary but i usually put those
certainly shouldn't hurt
looks like gamescope's got a
-s flag that can manually modify the mouse speed, so I'll probly just add that when necessaryoh!
nice!
now I just gota figure out exactly how much slower it is 😅
OH I think
--force-grab-cursor just fails to apply modifications made by the OS. In this case, I chose 40% faster on KDE, so I bet 1.4 works on gamescopeoh yeah!!!
idk like
it works fine on mine?
idk why it doenst grab yours
yeah beats me
but like first-person games, the mouse just flies off the window and stops working
shrug still better than the linux equivilant of BSOD
yeah 1.4 is perfect
so I was using gamemoderun to activate/deactivate my fan profiles while in-game. Is there an alternative?
how did it do that tho?
afaik gamemoderun doesnt have a gui right?
if you modify the
~/.config/gameode.ini file, theres a custom commands section at the bottom where you can just run whatever you want to trigger before and after gameplaycool!!!
what are the commands tho
you could probably just put like
cooler_thing && gamescopeoh, I have a framework laptop, so in my case
fw-fanctrl set medium
yeah, that could work honestlybut like there must be a way to set that through kde window rules
like getting any gamescope window and setting fw-fanctrl to whatever
right?
idk how window rules work LOL sorry
or like a kwin script maybe?
oh beats me, maybe?
I haven't touched kwin since the bugs started, since I assumed I borked it by changing something haha
oh you know what you can do
you can put a script in /usr/local/bin that does the window control for you automatically
put that on
/usr/local/bin/fan-control-script
then use fan-control-script gamescope --mangoapp -W 1920 -H 1080 -w 1920 -h 1080 -f --force-grab-cursor -- %command% -provider Portal as the commandlmao, this was because I was running mangohud in the unsupported way. Using
--mangoapp instead fixed ityou could even make it a bit more general actually
yeah, just remove the gamescope bit, then I can spin my fans up with the script whenever I want
sweet!
there you go
I assume I could putt
fw-fanctrl set lazy after the $@ to put them back after, ye?the reset_fan thing already takes care of that for you
oh, what's
trap do?whenever the script exits itll run reset_fan
woah
new bash-magic, I love it
trap is for running something whenver a signal is called for bash
LOL
oh, so it'll run regardless of a successful run?
if something goes wrong delete the entire root there you go
LOL
yup!
this is the way
censoring that command so that no one will run that
not exactly the best solution but it kinda works right
well yeah
probably they will fix this regression eventually on kwin
it's a workaround, since the real solution is basically a KDE bug
yup!
thanks so much, that's such a clean workaround too, just stick
gamescope --mangoapp -H 1080 -f --force-grab-cursor -s 1.4 -- in front of literally all my games and I'll never have an issue 😂honestly like
well, knock on wood, I shouldn't have said that out loud lmao
in my system i dont even let steam be on the root xwayland instance
check this out
oh nice, you gamescope steam as a whole?
yup!
it just works better in general on the environment im on
you can just patch the steam desktop file if you wanna do that
try running steam like that and see if it is better for you somehow
(just make sure to remove gamescope from the games' arguments)
-e is designed for running steam in gamescope, right?yup!
without that it breaks gamescope LOL
perf, I'll give that a go, thanks 😄
fan-control-script gamescope -W 1920 -H 1080 -w 1920 -h 1080 -f -e steam would be your commandwell, I'll give it a go when I'm feeling adventurous again 😅 I need to take a break after all this lmao
fair!!
i hope it works fine
just make sure to ping me whenever you wanna mess around with that
:p
thanks a bunch again! 😄 Absolute legend
I will!
have fun!!!
I sent a FR so I can remember 😂
accepted it
also, it seems like the not-grabbing-mouse thing is a known issue. Apparently new versions of proton changed some mouse protocols and gamescope hasn't caught up yet
oh! so its gonna get fixed eventually, sweet!
whats ur gamescope version?
gamescope --version[gamescope] [Info] console: gamescope version 3.15.5+not the best idea but you could try downgrading your version till it gets fixed on the newer ones
not sure I can tbh, gamescope came with Bazzite, so Ithink it's layered in
the --force-grab thing fixes it soooo.....
you can just download a gamescope version and put it in /usr/local/bin
oh tru
that's more trouble than it's worth I think 😂
idk if there are precompiled static binaries tho :p
ye LOL
probably!
I too am very prone to just trying random shit tho 😂
from what im seeing you would need to compile the thing from source
(too much hassle for nothing)
oof, yeah definately not worth lol
I avoid compile from source at almost any cost hahaha
honestly when you have a good build system its super easy
oh fair
gentoo makes it super easy to do that for example
honestly too, with distrobox, I betchu it's super clean to do that too
since the main reason I avoid it is to not have leftover build libraries
oh! so probably distrobox would be super sweet for you then! LOL
compile, get your binary, then throw the box in the trash. there you go!
super sweet isnt it
oh yeah, it's nutty cool
This was a rollercoaster. I think I am experiencing the same issue as you
The display is going black and the system hangs for a bit but then the whole desktop will do a hard restart.
Just tried the workaround though and it is still crashing
do you have any logs?
journalctl -b -1 -e and journalctl -b -1 -e -k
maybe its being caused by some other thing
if it is a graphics driver issue at the absolute worst case you can just install flatpak steam and test if your thing still crashesI will definitely try this the journalctl logs I have posted in the GitHub issue for this on bazzites repo
But when I get back to my desktop I’ll send them here too for continuity
oh! ill check out the issues
might be a good idea to open a new thread then if it's a different issue just to keep this one clear and single-issue if possible
Alright will do! Sorry about that as I was thinking that this was the same initially
no worries at all! 😄 If it turns out to be a variation of this one, for sure it's the right place for it
are you
JustAChucklin on Github?Yep Yep
perf
I created another discussion to be safe if this is intruding on this topic https://discordapp.com/channels/1072614816579063828/1285021394047860757
LMAO DUDE @tulip turning off the steam overlay also fixes it without gamescope 😂
it's a steam bug!
well, steam+wayland I guess
oh amazing LOL
honestly the steam overlay is so buggy god damnnnnnnnnn
honestly though, idk if it even matters XD turning off steam overlay and using gamescope (which has a broken steam overlay) are literally the same thingg at t his point
https://bugs.kde.org/show_bug.cgi?id=492830
GitLab
Atomic Commit Failed when Gaming (#2075) · Issues · drm / amd · Git...
Brief summary of the problem: When playing games on KDE Wayland the game would freeze but not crashed.. so it like...
just for bug references 👆
Solution
Better workaround is to put
KWIN_DRM_NO_DIRECT_SCANOUT=1 into /etc/environment and then reboot. There is a small hit to performance (I haven't noticed any hit, but KDE says there is), but the issue is now completely gone. I don't have to use gamescope and I can turn the steam overlay back on toogod damn!
very nice!
i never knew this was even a thing
very good to know!!!