ReillyBrogan Delete ~/.config/bluedevilglobalrc and reboot

Thanks - that fixed it. I'm still hoping for some help with the "dock." Replacing the missing solitaire icon seems to have survived a reboot, so it's possible that I accidentally removed it myself. But this is how the dock looks after I click on the colored dot that represent Spectacle (so I could take the screenshot).

After I took the screenshot, it went back to 12 colored dots representing the icons. And after I clicked to "Enter edit mode," all back to normal.

    EbonJaeger Last, but certainly not least, we'd like to give a shoutout to the people that have been steadily working through the repository and adding homepages to package.yml files, doing cleanup, and adding monitoring.yml files. We started this initiative at the end of September 2023, and since then, almost 1700 packages have been cleaned up, the majority of which have been done by community contributors. This work may not be glamorous, but your efforts are greatly appreciated. Thank you all very much!

    I've noticed the mass deprecation of useless debris thru devtracker everyday for months. Incredible. Feng Shui is what the Japanese call it and it means, in one sense, clearing the clutter out of one's life, letting go of artifacts rarely used---this purging of the dead-weight is a mechanism to moving forward freely in one's life.
    As a forum user I, too, want to shoutout "to the people that have been steadily working" on clearing the way forward. It's cool and necessary.

    EbonJaeger This is a significant milestone, and we are glad to open up testing for everyone!

    I agree. Fond of SC out of sentiment but time to move on. Sky's the limit. I'm really proud of all you and all of this.

          JTCPingas I can report this on the issue tracker if you need me to.

          Please do, so there is issue we can track. We kind of know it, the progress bar work on packagekit backend is still ongoing (Joey knows about it more).

            • [deleted]

            • Post #16

            Still unable to launch Element without forcing xwayland.

            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

            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

              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?

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

                    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.

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

                          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?

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

                              sudo clr-boot-manager mount-boot

                                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.

                                    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.

                                      TraceyC
                                      Thanks.

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