Hi again.
I’m still here ti ask for your advices because I Stille having issues with my tumbleweed.
It is installed in a desktop computer ryzen9 7900x, Asus rog strix b650e-f, Radeon rx6650xt.
Lady days I’ve a very strange issue: suddenly there is a freezing of desktop, KDE menu, brave browser or whatever software i’m using. I can click over anything but nothing appens. Mouse pointer moves, music still play, I can open yakuake by shortcut and launch softwares (Dolphin or an other brave browser session etc) and they works but every things was open “before” thé freezing stops work.
I can also open another tty.
Just a reboot can “unfreeze”
I am an astrophotographer and I had the first “freeze” while I was editing in pixinsight: this is very very very annoying.
Moreover, sometimes if I click on “suspend” thé entire computer still works but screen, mouse and keyboard.
Hard reset mandatory.
So, I am.disappointed by opensuse. On mu laptop It works very well but in m’y desktop the expérience Just now isn’t nice.
Most messages are now logged to the systemd journal. The journal is kept in binary format, use the journalctl command to examine it. Depending on how your account is setup your account may only be able to review the user-level messages, you may need to use sudo journalctl to also see the system level messages.
For X11 and wayland, there may be some additional info in various log files, which can be found under the user’s .local directory:
I’m testing a new user and suspension seems to works well. I can’t tell about freezings because they are so random that’s impossible to predict them.
but, I have not issues with kde menu at all (in the main user I have)
maybe I messed up something in my kde conf??
where could I find the bug?
Most things that are logged, including errors, are likely not to be significant, they’re often just general chatter.
I would not restrict the search to just err messages. Developers can be quite arbitrary about what level things are logged at, you should look for all messages at the commencement time of the freeze. That should hopefully narrow the text down to something that can be inserted into a post.
You might have to wait for it to next happen, note the time, and then go looking. If you see anything interesting/related to the freeze, you might start by googling the generic parts of the text.
Sorry, I have no laptop experience, so I’m not in a position to interpret the entirety of these logs. Perhaps someone else will chime in.
There are a lot of errors in your logs, it really would be better to focus on all messages that are logged around the time or an actual freeze (with a few seconds/minutes) .
A lot of errors are just noise and not real errors. I don’t think you can expect many here to wade through hours worth of logs picking out the wheat from the chaff. Concentrate on the content around the time of a freeze.
By only including crit/err messages you are potentially omitting messages that might detail the cause of any crit/err messages. By presenting them separately across two files, you’re making it hard to determine the temporal/causal relationships between the messages in the files. It would be better to select all output for few seconds or minutes around a freeze, so no -p restrictions. (You could direct the output to a file and then edit out anything above and below the area of interest, as well as removing anything sensitive).
I suspect others might be better able to help with a little more info about the machine, for example, perhaps some inxi output, such as from inxi -bMG or similar.
thank you @mchnz
the logs are about a desktop, not a laptop.
here the output of inxi -bMG
(yes I use liquorix kernel since some day but no issues with it)
Process 30010 (VirtualBoxVM) of user 1000 dumped core. – better disable any virtual machines while debugging
The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing /sbin/vboxconfig, If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.
Way too many other errors.
On VirtualBox: Please disable that while debugging, it is not configured correctly but that is another issue, focus first on the most important issue, the freezing
virtualbox was uninstalled after (I use Qemu), and I have some suspect that it was involved in the freeze. I’d like to know how to erase every trace about (services or kernel modules or somewhat)
I don’t know neither what postfix is
I noticed a lot of errors about bluez/bluetooth and I disable it from bios and uninstalled bluez.
a lot of warns about issues with kde plasma main menu (just Laucher or Cockpit menu worked, not the Application Menu) it seems going fine after restoring of default icons set.
I have exactly the same thing with slowroll for about two weeks now.
Only a reset works.
I have no idea what causes it.
Doesn’t matter if I use wayland or x11.
Sometimes it just happens out of the blue?
Very strange.
I keep a close eye on it to see if I notice anything.
Read something about Virtualbox… Given problems I added a line to the kernel parameter in the bootloader (kvm.enable_virt_at_load=0) Then Virtualbox at least works again, see also: Warning for VirtualBox users and Kernel 6.12
