For me it started when I updated to 23rd Feb build. But I'd been on a December or January build before that as I don't update if I have a active game I'm playing through
here are all my logs from HOME. it includes the log.old files too as my last two boots were a successful gamescope boot and an unsuccessful black screen boot https://we.tl/t-LjH9ZEqvaV
Of those files, .log is the successful gamescope session, .log.old is the black screen gamescope The drm:drm: messages are where the boots differ in the two .gamescope-stdout files I provided
I have been regularly clearing the contents of this folder to get a successful boot but this is the first time I removed the write permission for owner/owning group. It's booted twice fine since. Logs show that it failed to open edid.bin.tmp but then it moved on and boots anyway
I believe that folder is usually how Gamescope corrects your display orientation and presents it as a native landscape display to programs running in Gamescope
Are edid.bin files user readable? I can send a busted one? In gamescope .config folder modes.cfg was blank and bootstrap.cfg just contained set_bootstrap=1set_bootstrap=1
does anybody know how steamos advertises its hostname across your local network? What I mean by this is I can enable sshd on my deck. I can then change its hostname to anything, in this case 'oleddeck'. Then I can go to my workstation computer and type ssh deck@oleddeck and the hostname gets resolved. If I try with my new bazzite install, the hostname fails to resolve, but I can connect normally with the internal IP. (like ssh deck@192.168.1.20 or whatever). Not any issue I've just been curious how this works.