Sync Updates for Week 22, 2024

stalebrim

Still unable to launch Element without forcing xwayland.

Lucien_Lachance

hmm this grub stuff
1 i mounted the boot partition in gnome disks
2 i ran sudo grub-install --boot-directory=/boot/ --target=i386-pc --recheck --force /dev/nvme0n1
output: grub-install: error: attempt to install to encrypted disk without cryptodisk enabled. SetGRUB_ENABLE_CRYPTODISK=y' in file /etc/default/grub'.
3 added that as instructed
4 ran the install command again and got

Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub-install: error: embedding is not possible, but this is required for RAID and LVM install.

anyway, i took a chance and rebooted and it worked fine

edit: why grub is isntalled on my desktop but not on my laptop i do now know

SethStorm666

Plasma 6 works without any hitch on my part. 🙂

snowee

How do I check whether if my Solus Budgie is using Grub or something else?

I am on Budgie 4.5, on a clean install using the v4.5 ISO.
Ryzen 7, Asrock AM5 motherboard, and a NVME disk.

alfisya

snowee You are most likely on UEFI. What is the output of ls /boot ? If it contains grub then you are using grub, if not you are on UEFI and using systemd-boot.

snowee

alfisya

Hello alfisya, thanks very much for providing this helpful tip.

I did the ls /boot like you said but there was no output, the terminal just moved to the next line.
So that means I'm on UEFI boot?

Lucien_Lachance

alfisya
my ls /boot only contains
EFI loader solus-enroll-me.cer
yet i have grub installed and it was updated..

alfisya

snowee Then you most likely have separate boot partition. Check lsblk -f , see which partition(sdX or nvmeX) has vfat filesystem. Then you mount it to /boot, sudo mount /dev/sdX /boot. After that you can do ls /boot.

snowee

alfisya
how do I mount it to /boot ?
I'm very new to mounting disks, so will appreciate detailed guidance on this, thank you.

penny-farthing

alfisya

For me, the terminal ls /boot command output is EFI (I installed Solus with Budgie Desktop on my computer).
Just to understand: why does an EFI computer not need GRUB to boot, while a BIOS computer requires GRUB to boot?

I'd also like to ask another question.
I have 2 hard disks on my computer: an SDD which has the installed operating systems (/sda) and an HDD for data (/sdb). But sometimes, for some reason I don't understand, when I query the Disks application, the drive letters are reversed: the SDD becomes /sdb and the HDD becomes /sda. Then later, the SDD and HDD find their original drive (respectively /sda and /sdb). What is this due to?

silke

penny-farthing

For me, the terminal ls /boot command output is EFI (I installed Solus with Budgie Desktop on my computer).

That means you're on an EFI system. This should also be apparent from the output of bootctl.

Just to understand: why does an EFI computer not need GRUB to boot, while a BIOS computer requires GRUB to boot?

Short answer: because EFI systems use systemd-boot instead. The reasons for this is that this is a simpler bootloader that integrates well with modern Linux installations. GRUB is used on legacy BIOS systems because systemd-boot doesn't support those.

I have 2 hard disks on my computer: an SDD which has the installed operating systems (/sda) and an HDD for data (/sdb). But sometimes, for some reason I don't understand, when I query the Disks application, the drive letters are reversed: the SDD becomes /sdb and the HDD becomes /sda. Then later, the SDD and HDD find their original drive (respectively /sda and /sdb). What is this due to?

This is usually because the kernel discovers the disks in a different order. Why they are discovered in a different order is often hard to say (and hardware dependent). This is one of the reasons why /etc/fstab contains the UUID instead of the drive letter. The same happens with various other devices in Linux, such as network adapters (which are renamed during boot because of this) and USB devices.

TraceyC

For anyone who needs it, here's one easy way to mount your boot partition:

sudo clr-boot-manager mount-boot

snowee

TraceyC
Thanks.

Can I check what is the command to unmount the boot partition?

penny-farthing

silke
silke

Thank you for your explanations.

silke

For everyone unsure if you're using Grub (legacy BIOS) or systemd-boot (EFI): use bootctl to see this (errors can be ignored):

On a Grub/BIOS system:

System:
Not booted with EFI

On an EFI system (output will differ depending on your firmware):

System:
      Firmware: UEFI 2.80 (American Megatrends 5.26)

I have updated the sync notes to clarify this.

silke

snowee There's no need to unmount! This is because the system might expect it to be mounted for various reasons.

catfishsushi

I am seeing this, but not sure what it means.
any ideas or possible advise?

Staudey

catfishsushi Sounds like your EFI partition is too small.

Harvey

Cherry-picked plasma-workspace 6.0.5.1 (Thanks @Justin)

presianbg

I've skipped Week 21 updated and just installed Week 22 updates, so far everything works flawlessly... except spotify-qt:

[1]    5300 segmentation fault (core dumped)  spotify-qt

Am I the only one having this issue ?

Harvey

presianbg Am I the only one having this issue ?

I can not reproduce so possibly.

Staudey

presianbg Unfortunately I also can't reproduce this (on Budgie). Is there anything else printed to the terminal? Do you perhaps see additional information in journalctl (e.g. by running sudo journalctl -f and then launching spotify-qt in parallel)

brent

presianbg it's a silly question but did you reboot after you did the updates?

« Previous Page Next Page »