Yes.

I installed Salix 15 for the first time a few months ago, and have been using it since. Back then I created an extra partition for /home. This I called my 'old' home. After the upgrade crashed Xfce and I re-installed Salix, I let the installer mount my old home partition instead of creating a new ...

Not sharing between distributions, there is only one Salix on this machine.

But I have my umask set to 0077, could that be an issue? It's just that I have it still set to 0077, and after upgrading I switched to my old home, where some stuff (not all) was created with umask 0077, and all is running ...

I kind of found my way around it, but I am not really satisfied because I don't understand what is going, and I fear all that might happen again.

So what I did with today's re-install was not to reuse my old home partition, but let the installer create a new /home in my root partition and populate ...

Gave the upgrade another try, this time unchecked all big packages (llvm, libreoffice, ...). gslapt reported around 80MB will be downloaded, and some 180MB additional space will be required. Had a console open to df periodically, went from 2.5GB free space on / to 2.4GB, but never lower. Right in ...

@gapan So the additional space required that gslapt reports before doing the updates is meaningless? Becaus in my case with the previous update that was around 700MB.

@gapan After a fresh install I have 2.6G left in / (and /usr, same fs). So with the first time, disk space could have been an issue, but not with the second and the third re-install.

I installed from the install ISO, not from the live ISO, could there be any difference?

I also did not change the default exclusions (kernel, glibc) of gslapt, could that make a difference (given that they contain only lower level infrastructure, and XFCE worked as root)?

tl;dr
Upgrading Salix 15 or installing Audacity renders XFCE disfunctional, while a few months ago installing Audacity (and VLC) worked.

(sorry for the rather long history I am giving in the following, but since I have no clue *what* went wrong *when*, I thought it might help to pin down any nasty ...