![](https://seccdn.libravatar.org/avatar/150bb68600b6f4527c14c79e81e90f53.jpg?s=120&d=mm&r=g)
On Fri, 08 Sep 2023 16:22:17 +0200 mh@mike.franken.de wrote:
On Freitag, 8. September 2023 15:26:46 CEST Carlos E. R. wrote:
El 2023-09-08 a las 12:33 +0200, mh@mike.franken.de escribió:
On Donnerstag, 7. September 2023 22:33:13 CEST Carlos E. R. wrote:
On 2023-09-07 16:25, mh@mike.franken.de wrote:
On Donnerstag, 7. September 2023 21:53:55 CEST Carlos E. R. wrote:
On 2023-09-07 15:31, mh@mike.franken.de wrote: ...
It can be on a different partition, or openSUSE on a stick. I could suggest the XFCE rescue image on a stick, it is configurable and you can install things.
If problem repeats, chances are it is hardware related.
I have an external disk with Windows 11 and a second one with Leap 15.5. Both don't have the problem. So presumably no hardware problem.
Ok...
Another wild shot.
pm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \
| sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE Leap 15\.5|openSUSE_Leap_15.5|\-lp153|SUSE Linux | Enterprise 15|openSUSE\ Leap\ 15.5" | less -S Try that concoction in a terminal — assuming you have Leap 15.5, if not, edit the strings. The idea is to find any rpm that doesn't belong to Leap 15.5, and if found, you can try to replace it with another version.
Of course, there will be some false triggers, like from packman perhaps.
The system, that has the problem, is Tumbleweed! Leap 15.5 from the external disk doesn't have the problem. And: I have lots of packages, that don't belong to Tumbleweed - from packman, from my own repo, standalone rpms from different sites. But one of the first things I did, was to deactivate all non Tumbleweed repos, and to uninstall all packages without repos, so that I had a system with Tumbleweed packages only. But even that didn't help - the problem was persistent.
Whats more: The problem showed up first this spring - and I am sure, that nothing has changed before besides installing Tumbleweed snapshots. I didn't add foreign repos, didn't install strange packages, ...
Given the somewhat chequered/storied history of the installation, is it worth making a fresh Tumbleweed install (assuming there is space somewhere) to see if the symptoms occur with that? If you do make a fresh install and the problems do not recur then it seems likely some incompatibility in the particular system's history is to blame.