I recently broke my LEAP42.2 beyond repair while attempting to minimize the software bulking it up, and my only efficient option was to perform a clean install.
Upon installing 42.3 I’ve encountered a problem that I just cannot for the life of me find a forum on so I’ve decided to post my first
The initial restart after first setting the OS up was all well and good but when i started the system the next day., it lagged on the login screen and eventually went black. I miraculously stumbled into Ctrl Alt Backspacing on the black screen (Extremely lucky) which when performed multiple times is enough to jostle the system out of whatever hangup it has.
Since I can (eventually) get to my login, this is more a curiosity than a desperate need for help however it is a tad inconvenient so I’d be appreciative if somebody could shed some light on the situation.
Please supply a few details about the hardware which is running the Leap 42.3.
At least, the CPU manufacturer and type, the disk’s capacity and manufacturer, the graphics hardware and, the amount of main memory installed.
When installing openSUSE from an ISO image either on a DVD or a USB-Stick, there’s a tool available to check the target hardware. Does the execution of that tool indicate any issues with the target hardware.
There’s another tool on the installation media to check the installation media itself – checksum and so on.
A “clean install” would require you to wipe the disk properly.
I’m guessing you didn’t do that…
You might or might not have removed the partitions, but that wouldn’t be sufficient if you accepted all install default layout options…
If you don’t wipe the disk,
The removing partitions (or not) leaves the data on disk, and if the partitions are set up exactly like before… voila! Data from your old install can re-appear magically.
Assuming this is your situation,
I highly recommend you do a re-install, but prepare your disk first by either…
Boot to a LiveCD and <reformat> or zero out the data on the disk
or
During your install, don’t accept the default layout exactly. Modify the partitions, even by a single block is usually sufficient to re-map the disk blocks in each partition. But, this is less preferable to the first recommendation.
What ??? I’ve been reusing my homedir for ages, this is nonsense. Once the partioning is done properly, and you want a clean install ( which is about the OS, not about data ) you can import the previous partitioning, only format / and you can import the users, This feature has been there at least as long as openSUSE exists.
If it is a “data” issue, data in your conception, the user should be advised to create a new user account, and test whether the issue exists for that new user,
I’m not talking about the /home partition, particularly in this case.
I’m using the “data” term to loosely describe all files in the relevant partition which in this case is the root (/) partition which includes the boot files.
That would be up to the User.
His situation has 2 big issues related to his original install
He had a significant problem he was unable to resolve
His original system was a different version altogether
Either and both reasons are significant enough to make sure nothing from the old system might re-appear in a new system.
As for the /home directory, it’s YMMV.
As we know, it may be a nice result to retain original User settings, but that is only if the same Desktop is instlled anew, and oftentimes an old /home can be “forklifted” into a newer system. If the User had problems in /home, then of course than what I described for the root applies to /home, too.
So,
If a User wanted to be perfectly safe with a new, “clean” install the <entire disk> should be prepared so that nothing is unintentionally preserved.
But, if a User wanted to tinker with preserving anything intentionally, then that’s a personal decision.
I’ve been on Linux for a few years with a rough start in which I learned very quick to always format before a fresh iso install. I also did not accept the default layout as I wanted a larger root partition than it was originally slated for.
I do not have that file, my tree stops at /usr/lib/systemd/user/(and theres a sockets.target file)
linux:// # rm /usr/lib/systemd/user/sockets.target.wants/dbus.socket
rm: cannot remove ‘/usr/lib/systemd/user/sockets.target.wants/dbus.socket’: No such file or directory
(Before anyone asks, no i do not su in Konsole without good reason)
