06-08-2024, 06:55 PM
(06-08-2024, 01:46 PM)trinidad link Wrote: Did you use the erase disk and install use whole disk option when you installed 7? Also Linux Lite can only be upgraded within a series. If you tried saving a seperate previous home partition through the upgrade process, like can be done in Debian, file path mismatches would bork the desktop. Do you have more than one .bashrc file/s in your home folder?
TC
I use a /home partition for years and every time when I do a clean Install, even on a brand new media, the first thing is to restore the /home from a low-level backup.
Only after the restore, I go to BootInstall, etc.
I usually keep the same partitioning scheme, made prior to any other job, with GPartEd.
Next step is to restore the /home and then proceed with the install steps.
For years, all went as expected.
Anyway, if the Terminal customization was lost, I remember that happened some years ago and then I discovered why.
I've been using a Multiboot (MultiSys I guess) and its setup required the xterm.
The same situation described below, happened but I knew that must have been due to xterm installation.
So, it is possible that for whatever reason, that somehow the Terminal configuration file was rewritten, or changed.
But as described before, on a new installation includin formatting the /home, this is impossible.
I just installed LL 7.0 on a "clean slate" (a new SSD with a new partitioning and formatting) and the result was the Lite Terminal, as seen in the screen captures.
This must have been generated by a PPA that used somehow an xterm that now overrides the Lite Terminal config file.
"It's easy to die for an idea. It's way harder TO LIVE for your idea!"
Current Machine:
Dell Precision T1700, 16 GB RAM, SSD Kingston A400, 480 GB.
Laptop:
ASUS X200MA , IntelĀ® CeleronĀ® N2830, 2 GB RAM, SSD Kingston A400, 480 GB.
Current Machine:
Dell Precision T1700, 16 GB RAM, SSD Kingston A400, 480 GB.
Laptop:
ASUS X200MA , IntelĀ® CeleronĀ® N2830, 2 GB RAM, SSD Kingston A400, 480 GB.