I Just installed opensuse and add software… No special configuration
I rebooted with the standard kernel and I had another freeze few minutes ago.
here the output of:
sudo journalctl --since "2025-01-02 22:36"
I hope it can helps.
if you need other logs ask me please.
thank you
The log is from 22:38:52 to 22:45:50, does the include the freeze, if so when?
It would not surprise if your are problems are linked to:
gen 02 22:42:52 visione brave-browser-stable[3332]: [3333:3333:0102/224252.319876:ERROR:gpu_process_host.cc(982)] GPU process exited unexpectedly: exit_code=512
So can you reproduce the problem not running the brave browser?
The freeze was about 22:40
Have a look at 22:40 and see what I wrote earlier.
mmm I see…at 22:40 there is another brave issue.
oh man, never had a single problem with this browser; but why if it’s a brave’s issues the effect is to freeze kde?
I noticed in the log that the error touch the gpu too: maybe a driver issue?
more: it’s a coincidence that the freeze appeared right when I switch to the standard kernel?
I think it’s good practice when sharing journalctl logs to figure out “how many boots ago” the issue happened, and then fetch the logs for that boot only.
journalctl -b will only take messages since last boot, but if you use -b -1 or -2… -n you can go back with previous boots.
Gives the full picture from boot to shutdown (whether graceful or hard) and makes it easier to investigate.
@Gaiden I have these freezes, too. On a laptop, Lenovo ThinkPad W530 i7 (2013) with 3y over EOL openSUSE Leap 15.2 (yes I know I shouldn’t). For some years now, I had the KDE Plasma freezed say once a month.
Since summer 2024 I have brave browser installed and I use it extensively to binge watch YouTube. Now, after about 2h of watching nearly every time I would get the KDE freeze, symptoms just as you described, only remedy is to restart x11 within F1 terminal, say, or reboot, obviously.
However, after restarting x11 I get a window saying akonadi server crashed, send bug report , restart, cancel, OK. I would choose to restart akonadi. After that I am mostly good for 2 more hours of YouTube on brave, I guess.
I know that’s very preliminary and my EOL Leap 15.2 is not worth to be mentioned here, but what if you, too, would find some issue with akonadi and with that a door opens for a remedy?
That’s all for today, maybe it is of some help. - Regards, M.
I have not akonadi in my installation.
thank you however for the try
Okay, so a clear link to the brave browser. Would be good to know also the graphics card @christomonte11 has (inxi -bMG) and have the journal for when the crash happens so it is clear that there is also an overlap on graphics or not.
I have a AMD RX6650XT VGA, always in xorg session
gaiden@visione:~> glxinfo | grep “OpenGL version”
OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.3.1
gaiden@visione:~> glxinfo | grep "renderer string"
OpenGL renderer string: AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 19.1.6, DRM 3.59, 6.12.6-lqx1-2-liquorix)
ho una ati rx6650xt e come sessione è sempre Xorg
the last log I added was taken while the freeze.
You need som different log as dmesg maybe? or differents flags in systemctl?
I’m use Nvidia GPU’s on X11, so I’m not sure if this is relevant, but…
I think brave is based on chromium, so it’s related to chrome. I have had occasions in the past where viewing Youtube videos in chrome would cause my desktop to hang (not always, but after I’d been viewing a while). I have always been able to stabilise the situation by temporarily disabling the browsers use of GPU acceleration (in chrome that’s under Settings->System->Use graphics acceleration).
Eventually a new GPU driver, new chrome, or new kernel seemed to make the issue go away. But similar crashes or hangs would pop up again under some later new GPU driver, new chrome, or new kernel. It hasn’t happened to me for quite some months - perhaps even a year. But over the last year I’ve been far more careful around driver and kernel upgrades - I often defer them - which might have helped with stability.
@mchnz this could match with no issues when I use liquorix kernel.
however, yesterday at 00:11 I had another “partial suspension” (screen, keyboard, mouse go off and stop work but not the case. long pression start button needed to shutdown):
here’s the log: gaiden@visione:~> sudo journalctl --since "2025-01-05"gen 05 00:00:00 visione - Pastebin.com
@mchnz: good to know that at least for you disabling graphic acceleration did prevent the login.
These kind of crashes happen typically random, whenever somebody can make it reproducible it will be easier to debug. The kind of graphic acceleration a browser does can I think reproduced by transcoding video, so running a test suite like “phoronix-test-suite benchmark video-encoding” might be a start.
@Gaiden: Your latest log shows only:
gen 05 00:11:12 visione systemd-logind[1240]: The system will suspend now!
strange, the link shows me the entire log in pastebin…
ok, I joint a txt here
https://www.dropbox.com/scl/fi/qpgy9i9gq34qvpcb1lolb/suspension_issue.txt?rlkey=vi750u37jctdn3cvl6p4iq5qw&st=a8eazl73&dl=0
Could KDE Power Management going into suspend be confusing the issue?
Under System Settings → Power Management, check Suspend Session and also Switch to power profile and maybe disable them until the issue is sorted. Depending on drivers/hardware/BIOS some systems may have issues coming back from suspend.
auto suspension is disabled yet.
I prefer to suspend manually when I end my tasks
I thought this could be interesting:
* gen 05 00:11:12 visione systemd-sleep[79557]: User sessions remain unfrozen (add $SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=1 to override),
* gen 05 00:11:12 visione systemd-sleep[79557]: relying on kernel to perform the freeze.
* gen 05 00:11:12 visione systemd-sleep[79557]: This is a temporary downstream workaround for https://github.com/systemd/systemd/issues/33083.
* gen 05 00:11:12 visione PackageKit[79556]: daemon start
Not sure what systemd-sleep is doing on your system, on my system:
> sudo systemctl status systemd-sleep
Unit systemd-sleep.service could not be found.
What does this command give for you?
it gives me:
Unit systemd-sleep .service could not be found