I can’t actually believe I’m writing this but, as weird as this sounds, it seems like Facebook and Reddit trigger a full reboot when loading the pages in Cachy Browser
I’ve done a tonne of testing and can reproduce it repeatedly with no other applications running. It doesn’t happen on this forum, Gmail, or Slashdot
It takes a few moments, but once the page loads fully, without any user input, the screen will flash black and come back to the page, then a moment later goes black again and suddenly you’re seeing the BIOS boot screen
Sometimes, if I’m quick, I can close the browser window on the first screen flash and then restart doesn’t happen
Disabling all browser extensions makes no difference
It doesn’t seem like a crash as looking at journalctl -b -1 doesn’t seem to have any entries at the timestamp of the restart (I’ve induced it a couple of dozen times)
Hardware is a GPD Pocket 4, happens both with internal LCD and external HDMI with lid closed
CPU: AMD Ryzen AI 9 HX 370 (24) @ 5.16 GHz GPU: AMD Radeon 880M / 890M [Integrated] Kernel: Linux 6.13.4-2-cachyos DE: KDE Plasma 6.3.1 WM: KWin (Wayland)
Adding to this, what it looks like is happening, is that at some point in the page load the browser is sending a reboot signal to the OS, almost like it is triggering sudo reboot now or sudo shutdown -r now
I’m gonna take a look to see if I can figure out how/when those commands are being triggered and by which user
This looks like the universe telling you to delete Facebook and Reddit to me. IMO, you should ask out all the girls you liked from your High School but didn’t get to date out, then delete it after, that’s what I did with Facebook.
Reddit is just 40% AI arguing with each other, easily deleted. If you need a replacement Lemmy.World is a great open source one.
Thanks! Pretty sure I updated right before posting 2 days ago, but updated again now
I’m gonna tentatively call this resolved for now. It did seem to not happen in Firefox and was only happening on Cachy Browser, but after update I’m not reprpoducing it right away
@Redmage913 So, it appeared to go away when using Firefox, but apparently this is a known AMD bug affecting Cachy Browser which seems be resolved with latest 6.13.5-2 kernel