MX-19.2 KDE Beta 2 Feedback Thread

[kangburra]

This is just semantics, JayM and kangburra.

When you rename the home directory, it is just to tell the installer not to wipe it but to set it aside under a different name. Meanwhile, the installer will then create a fresh /home for the current installation being done.

Is renaming the old /home "backup"? Yes and no. Yes because you are setting it aside/preserving it for future use. No because often when people think of backup, they are thinking of a new copy being created. Here no new copy of the old partition is made.

The point is, it doesn't work! It created a file, not a directory and then the GUI login fails. I reported it earlier.

[JayM]

It's not just semantics. Words have meanings. Telling the installer to preserve /home isn't the same thing as performing a backup of /home. The latter gives you a second copy of /home's contents saved in another location in case something happens to the original. Edit: Such as preserving /home in the installer not working for some odd reason, though I've never seen that happen unless it was an encrypted installation.

[kangburra]

It's not just semantics. Words have meanings. Telling the installer to preserve /home isn't the same thing as performing a backup of /home. The latter gives you a second copy of /home's contents saved in another location in case something happens to the original.

The point is, it doesn't work! It created a file, not a directory and then the GUI login fails. I reported it earlier.

[tony37]

@leslie1017: You could try looking at /home/user/.config/plasma-org.kde.plasma.desktop-appletsrc and see if libreoffice is mentioned there, and remove it. Or more radical: backup that file, then delete it (or simply rename it), and relogin. You'll have to redo a lot of changes you made, but maybe it solves the problem.

[tony37]

Following bash aliases have a # before them in ~/.bashrc, but Bash Config wrongly suggests they are active: dir='dir --color=auto', vdir='vdir --color=auto', grep='grep --color=auto', fgrep='fgrep --color=auto', egrep='egrep --color=auto'

[dolphin_oracle]

we are looking at that installer problem.

if the OP with that problem would post the /var/log/minstall.log, that would be very helpful.

also checking the permissions on the /home, /home/$USER and whatever file got created would be good too.

[kangburra]

we are looking at that installer problem.

if the OP with that problem would post the /var/log/minstall.log, that would be very helpful.

also checking the permissions on the /home, /home/$USER and whatever file got created would be good too.

Here is the log, I don't have access to the file created as I removed in order to create the directory and populate it, which did work.

[dolphin_oracle]

we are looking at that installer problem.

if the OP with that problem would post the /var/log/minstall.log, that would be very helpful.

also checking the permissions on the /home, /home/$USER and whatever file got created would be good too.

Here is the log, I don't have access to the file created as I removed in order to create the directory and populate it, which did work.

was the file "simon.001" or just "simon"?

I think I see what may have happened, but would like to confirm those points.

[kangburra]

we are looking at that installer problem.

if the OP with that problem would post the /var/log/minstall.log, that would be very helpful.

also checking the permissions on the /home, /home/$USER and whatever file got created would be good too.

Here is the log, I don't have access to the file created as I removed in order to create the directory and populate it, which did work.

was the file "simon.001" or just "simon"?

I think I see what may have happened, but would like to confirm those points.

The old home was moved simon.001 and the file was simon.

[dolphin_oracle]

Here is the log, I don't have access to the file created as I removed in order to create the directory and populate it, which did work.

was the file "simon.001" or just "simon"?

I think I see what may have happened, but would like to confirm those points.

The old home was moved simon.001 and the file was simon.

Great thanks that's what we thought we were seeing in the logs.

This one is a bug across the whole mx/antix family and will be fixed shortly.