Bug 27662

This all happened after kernel desktop 5.9.9  was updated to Kernel desktop 5.9.10.1.mga8.

The time for the O/S to start from initial start up and reach the GUI was approximately 36 seconds and now it is approximately 90 seconds.

Created attachment 12016 [details]
png image of start up problems

This is an image of the time out and dependency problems.

Had to uninstall Glibc version 2.31 to allow 2.32 to install.

Have also noticed when the PC is put into sleep mode the screen comes back in multi colour display only with no screen display of the O/S login screen.

Hi, thanks for reporting this.

Cauldron is not intended to be used on production systems.
If this is pure testing, I will help you.

What kind of ISO have you used to install Cauldron?
What is the Desktop Environment you have choose?

After seen your attached file, it appears that systemd can't seen your swap partition by UUID. This could be a result of a wrong installation over an existing one and a corrupted /etc/fstab file.

If there is no critical files on this system, I will recommend to FORMAT all partitions at install time. Please make sure all your files are in a backup drive.

Summary: mageia 8 beta 1 start up is slow to GUI with 1 x time out and 2 x failed dependency problems, plus can not access mageia control centre or network center from the net app in task bar unless log out then log back in again. => [M8-B1] systemd timeout to mount swap partition by uuid
Keywords: (none) => NEEDINFO

The ISO used was was Mageia-8-beta1-x86_64.iso and the desktop environment is KDE plasma. 

The updates have appeared to not affect the system until now. 

This is not used as my main system as I use Mageia 7 on another drive for that.

I simply install the software from the repositories for testing purposes and ensure the hardware and everything else works OK, for example documents, photos, music, internet connections and so on.

I do have another Linux O/S on this drive that I also use. I have to update that as well so not sure if that could be the in any way related.

I have myself now have come to the conclusion that a format and fresh install would be required as you say.

Please advise if using the two O/S on the same drive is OK.

Either the other linux system was installed after Mageia and reformatted the
swap, or something happened to cause it to be reformatted.

I use nofail for my swap partitions ...
# grep swap /etc/fstab
LABEL=a3swap swap swap defaults,nofail,noauto 0 0

That way it doesn't stop the boot if it cannot be found, though the nofail
option must be present when creating the bootloader.

Fixing it means reinstalling the bootloader (dracut -f and grub-install).
One of the easiest ways to do that is to reinstall without formatting anything.
The older packages from the iso will not overwrite the currently installed
packages so it will go fairly quickly.

CC: (none) => davidwhodgins

Have reinstalled bootloader from system rescue on the installation disk.

This unfortunately has not resolved the issue.

Have now resolved start up issue.

Have changed label for swap partition to (a3swap swap swap defaults,nofail,noauto 0 0), and saved /etc/fstab in manage disk partitions of control center.

The system now reboots without the problems and it now only takes about twelve seconds to boot into the GUI.Job done there. Thank you.

There is now still the problem of only accessing the mageia control center and network app in the taskbar by logging out and then logging back into the O/S again.

Usually, installing multiples Linux distributions on same disk and sharing same swap partition should not overwrite UUID on that partition, until you use an exotic one.

DrakX (our installer) handles this very well.
Ubiquity (Ubuntu and derivatives), Debian Installer, Yast2 (openSUSE, SUSE) and Anaconda (RedHat, Fedora) too. They all recognize a swap signature and don't overwrite it.
This can also be avoided by adding a LABEL to filesystem and by manually adding "nofail" to each /etc/fstab file mentioning this partition under all your Linux systems.

As long as this is resolved, I invite you to open a new bug report with screenshots about Mageia Control Center and Network applet.

One bug, One report. This is not a forum, thank you by advance.

Resolution: (none) => WORKSFORME
Status: NEW => RESOLVED

(In reply to ian trump from comment #8)
> Have now resolved start up issue.
> Have changed label for swap partition to (a3swap swap swap
> defaults,nofail,noauto 0 0), and saved /etc/fstab in manage disk partitions
> of control center.

Note that I use labels for all of my partitions in fstab, as they are not
affected by disk detection order and are easier to read/remember than uuids.

When I formatted the swap partition I used "mkswap -L a3swap /dev/sda3" to
format it.

# blkid|grep swap
/dev/sda3: LABEL="a3swap" UUID="9af64cdc-a611-47c3-821e-94a9fd60251e" TYPE="swap""

# grep swap /etc/fstab
LABEL=a3swap swap swap defaults,nofail,noauto 0 0

The string a3swap is just something I chose and other then matching what is
used in fstab and the partition has no special meaning to the system.

Just like a universally UNIQUE identifier it must only exist in one file system
present in the computer during boot, so must be modified if a disk or file
system is copied, before the next boot. If it is not unique, which one will
be used may change from one boot to the next.

If the label specified in the fstab entry does not exist in any file system,
due to the nofail option the entry will just be ignored and no swap used.