On Tue, 2021-03-30 at 16:14 +0100, Mark @ GMail wrote:
> Seems like /dev/sda1 is /boot based on the mount point and the
> There is probably another /dev/sda1 entry in "sudo df -h" ?
Nope, it's the only one. The full output, err, slightly wrapped, is
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 1.6G 1.6M 1.6G 1% /run
/dev/mapper/ofedora-root 50G 23G 24G 50% /
tempfs 8.0G 20K 8.0G 1% /tmp
/dev/loop0 99M 99M 0 100%
/dev/loop1 176M 176M 0 100%
/dev/mapper/ofedora-alt 50G 53M 47G 1% /alt
/dev/mapper/ofedora-home 1.7T 489G 1.2T 30% /home
tmpfs 783M 208K 783M 1% /run/user/1000
/dev/sda1 477M 155M 293M 35% /run/media/mark/Boot
I see you're using LVM (/dev/mapper), so I'm guessing your F33 was not
a fresh install but an upgrade. F33 installs on BTRFS by default, and
come to think of since I switched to BTRFS I'm fairly sure I haven't
seen this problem. That might be a red herring of course.
I may have fiddled with this at some point, I'm not sure.
> Bottom line is you don't need to mount on KDE startup. You just
> need to
> find what is wanting to mount it though. Does Dolphin start up
> automatically when you login perhaps? Another place to look is in
> /etc/fstab .
I'm *trying* not to load Dolphin, nor any of the Gnome desktop,
Dolphin is part of KDE, not Gnome. The Gnome equivalent is Nautilus.
Do you have the "Restore Manually Saved Session" option set (under
Desktop Session in KDE Settings)? If you save a session with Dolphin
running, it will restart when you log in.
Alternatively, check Autostart (under Workspace in Settings).