Following Stable Update 2026-02-23, default DE and home directory changed?

Hi all, the update failed :smiley:
I did an update on a laptop. It seems to have reverted to all vanilla settings (XFCE) while it was using KDE.
I can log in, and there is a user folder, though empty.
In de file explorer, I can see a 79Gb device that I can access after I enter my password. All my files are there.
I assume that the home partition somehow got disconnected and Pacman made a new and empty home folder. I cannot, however, select KDE in the login screen.
I think I may need to reinstall GRUB, but that still does not explayn why KDE was replaced with XFCE…
I’m still in deep meditation…care to meditate with me?
Thanks
:peace_symbol: Melissa :rose:
(always eager to learn something)

Hello Mellisa.

Please use ā€œjournalctlā€ to check why your home partition was not mounted.

Can you mount your partition with your home using ā€œsudo mount /dev/$HOMEPARTITION /home/testā€ (please adjust and create accordingly)?

If so, enter ā€œidā€ and compare the id displayed with the one under ā€œ/home/test.ā€ If your username is displayed there directly, it’s fine.

You also need to compare the path ā€œ/dev/$HOMEPARTITIONā€ with your /etc/fstab. If it differs, you must correct your fstab and restart. Consider using UUID there if you don’t already.

Have you converted your /etc/mkinitcpio.conf to systemd?
Is your home partition encrypted?

T-Yes I can, I have to enter my password…

I checked, and the UUID checks out…

Ehm…I dont know what you mean by that, sorry

Nope, seemed useless, since the laptop never leaves the house…
Thanks

I 'm reading the pages on that…
Edit : I tried FSCK, and that came back with parse errors in FSTAB…

That’s a strong indication. What is the specific error message?

Since you can mount it manually, compare the contents of ā€œ/etc/mtabā€ with ā€œ/etc/fstabā€ for your home partition after mounting.

Something is obviously wrong. Did you make any changes to fstab during your initial troubleshooting?

Yes, I (did) make a copy of FSTAB, though. I followed these hints…
Ow, we may not have met. I’m Melissa and I’m the ā€œweird oneā€ :rofl:…I’m happy about this situation, it’s educational. It’s a secondary laptop (thanks to the Holy cup o’ Coffee it’s not my main box)…but I am learning. That’s good.
I’ll paste the backup back and try to reboot.
The user space is blank (no startable/listable applications and no functionality)
Thanks.
I already installed KDE, but I remember that I opted for XFCE initially (this being an older mac) so THAT mystery is solved, there never was a KDE to start with… :wink:

Edit : looking at the ā€œgeneratedā€ FSTAB some lines were commented out and the UUID was not used…clearly, the ā€œtipsā€ were not very useful.
The system is up now, but the link to the /home partition is still ā€œout thereā€ā€¦ :wink:

Hi @ButterflyMelissa I have moved your posts and the replies into a dedicated thread.

From what I can see, it looks like, at some point, you have installed Xfce alongside Plasma (or maybe the other way round). Is this the case? :wink:

Hi, thanks for moving the post :smiley:
Well, in my confusion, I did. XFCE (ht eorigianal system) now runs, I did have to redo some settings (minor stuff, all educational)…
The link to the /home partition is still missing.
This is a secondary laptop, I hope this does not happen to my main box. That is why I have these secondary system…to do a dry-run before tackling the main box :grinning_cat:

The update never changes anything user related.

That means it won’t change your desktop from Plasma to vanilla XFCE.

Something else is in play - the empty home folder point toward filesystem errors - from the top of my head

  • btrfs?
  • filesystem error?
  • partition layout?
  • forgotten multiboot?
1 Like

Hmm, it worked before the update, so (it being an older Macbook) - it could be a filssystem error, so I did a FSCK, that gave no errors, I may need to dive deeper in. Could be that the /home foled needs to be empty before I tinker…there is a new/recent user folder in there…and that is weird.
The logs are still in there. I’ll dig in to look in there.
:drooling_face: More learning :drooling_face:
:smile: thanks :wink:
Melissa

Well, I’m doing my best with the information you’ve provided. Questions have been ignored, and I can’t read minds.

For example, the exact error message regarding fstab that you had or the error message in journalctl. There was also no feedback on the comparison between fstab and mtab after manually mounting your home partition. The difference should be noticeable by then at the latest.

Good luck.

Hi,
Finally got to the laptop…okay,
Error message:

[WhiteCloud ~]# fsck /dev/sda2
fsck from util-linux 2.41.3
fsck: /etc/fstab: parse error at line 10 -- ignored
fsck: /etc/fstab: parse error at line 11 -- ignored
e2fsck 1.47.3 (8-Jul-2025)
/dev/sda2: clean, 42969/4808704 files, 3557401/19206144 blocks
[WhiteCloud ~]# ^C

the Fstab, however:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=1e41e35c-483e-45dd-9d35-e457823b7651   /               ext4    noatime             0 1 
tmpfs                                       /tmp            tmpfs   noatime,mode=1777   0 0 
UUID=d7d06065-9aee-4d12-9733-cb81a7c45ccb /home 	 ext4	 nosuid, nodev, noatime 0 2
UUID=2e624803-7c7f-44c5-9e19-000a896f3f29 swap		 swap	 defaults, noatime, mode=1777 0 0 
[WhiteCloud ~]#

and the weird thing is that the UUID of the /home matches with the FSTAB…

ah, so THAT’s how you do it! Okay…let’s see…thanks

Edit :

Mounting

 sudo mount /sda2/melissa /home/melissa
[sudo] password for melissa: 
mount: /home/melissa: fsconfig() failed: /sda2/melissa: Can't lookup blockdev.
       dmesg(1) may have more information after failed mount system call.

/dev/sda2 is not mentioned in the mtab (mount table? Is that what this file is?)

And…of course I had to enter

mount /dev/sda2 /home

After that, it mounted…

Let’s see the mtab, then…

This line got added…

/dev/sda2 /home/melissa ext4 rw,relatime,errors=remount-ro 0 0

UUID=d7d06065-9aee-4d12-9733-cb81a7c45ccb /home 	 ext4	 nosuid, nodev, noatime 0 2
UUID=2e624803-7c7f-44c5-9e19-000a896f3f29 swap		 swap	 defaults, noatime, mode=1777 0 0 

This should be:

UUID=d7d06065-9aee-4d12-9733-cb81a7c45ccb /home 	 ext4	 nosuid,nodev,noatime 0 2
UUID=2e624803-7c7f-44c5-9e19-000a896f3f29 none		 swap	 defaults 0 0 
1 Like

The label shouldn’t matter; in fact swap isn’t even defined in the fstab on this particular system and hibernate etc. works just fine¹.

¹ Maybe I’ll get faster resume-from-hibernate (or cold boot) if I do define that. :man_shrugging:

These lines in /etc/fstab are these here:

The fourth field, the mount options, are supposed to be
a comma separated list

What you have there is a comma and then a space before the next option.
for instance:

UUID=d7d06065-9aee-4d12-9733-cb81a7c45ccb /home 	 ext4	 nosuid, nodev, noatime 0 2

vs. what should be:

UUID=d7d06065-9aee-4d12-9733-cb81a7c45ccb /home 	 ext4	 nosuid,nodev,noatime 0 2

I do not know whether that could be part of the problem,
but I have never put a space after the comma …

This looks like syntax errors in /etc/fstab …

3 Likes

Definetly…either that or…this


:rofl:
(the mods already know me, I’m personally having fun, no kidding and no sarcasm… :face_savoring_food:)
…the login screen… :wink:

… technically I’m one of them :wink:
and I indeed do know you (from your posts here only)

… does that mean that you don’t want your requests to be taken seriously?
I’m a bit confused. :slightly_smiling_face:

1 Like

I cannot be taken serously - I’m way too crazy for that :wink: - I choose Manjaro so I could have a challenge once in a while, and now…I got one…lovely.
By the way, the login is solved, I removed SDDM and some orphans, reinstalled SDDM, cleaned out the pacman cache and did what a normal sane Linux user does: keep cool and totally enjoy the ride.
On to our quest, I cleaned up the FSTAB and rebooted. Thenā€¦ā€œthatā€ screen. WOW! Reboot, login to a console (as root) and do some ā€œplumbingā€ā€¦
Everything is back…
Thanks so much! I have learned a lot, again.
:heart: Love you, gang :heart:
Melissa

So:
when did you decide to change that there in that way?
… I suppose I shouldn’t ask ā€œWhy?ā€ :wink:
If cleaning that up cleared up the issue, you should have remembered doing it.

I’ll try to remember and not take your future issues too seriously. :wink:

Well, Linux gives me a means to look more stoically at thing. It helps me to place things in perspective.
Of course, if that had been my main box, I would probably need a tranquilizer…anyway, thanks for meditating with me and guiding me through this adventure :smiley: