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?

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

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

                                  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 ?

                                    presianbg Am I the only one having this issue ?

                                    I can not reproduce so possibly.

                                      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)

                                          Staudey

                                          Process 20503 (spotify-qt) of user 1000 dumped core.

Stack trace of thread 20503:
#0  0x00007fd7bf94ca38 _ZN7QObject11deleteLaterEv (libQt6Core.so.6 + 0x34ca38)
#1  0x000055affefaac57 n/a (spotify-qt + 0x15ec57)
#2  0x000055affefa9a77 n/a (spotify-qt + 0x15da77)
#3  0x000055affefa8b00 n/a (spotify-qt + 0x15cb00)
#4  0x00007fd7bf04030e n/a (libc.so.6 + 0x2a30e)
#5  0x00007fd7bf0403c9 __libc_start_main (libc.so.6 + 0x2a3c9)
#6  0x000055affeefac55 n/a (spotify-qt + 0xaec55)

Stack trace of thread 20506:
#0  0x00007fd7bf12444d syscall (libc.so.6 + 0x10e44d)
#1  0x00007fd7bf57436c g_cond_wait (libglib-2.0.so.0 + 0xba36c)
#2  0x00007fd7bf4dc72c n/a (libglib-2.0.so.0 + 0x2272c)
#3  0x00007fd7bf545507 n/a (libglib-2.0.so.0 + 0x8b507)
#4  0x00007fd7bf544d18 n/a (libglib-2.0.so.0 + 0x8ad18)
#5  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#6  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20505:
#0  0x00007fd7bf11997f __poll (libc.so.6 + 0x10397f)
#1  0x00007fd7be550773 n/a (libxcb.so.1 + 0xc773)
#2  0x00007fd7be5531eb xcb_wait_for_event (libxcb.so.1 + 0xf1eb)
#3  0x00007fd7bb3c594f n/a (libQt6XcbQpa.so.6 + 0x6594f)
#4  0x00007fd7bfabf3cf n/a (libQt6Core.so.6 + 0x4bf3cf)
#5  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#6  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20511:
#0  0x00007fd7bf51548a n/a (libglib-2.0.so.0 + 0x5b48a)
#1  0x00007fd7bf515cf1 g_main_context_iteration (libglib-2.0.so.0 + 0x5bcf1)
#2  0x00007fd7bfbebca2 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x5ebca2)
#3  0x00007fd7bf9021ba _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3021ba)
#4  0x00007fd7bfa160d6 _ZN7QThread4execEv (libQt6Core.so.6 + 0x4160d6)
#5  0x00007fd7bfabf3cf n/a (libQt6Core.so.6 + 0x4bf3cf)
#6  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#7  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20512:
#0  0x00007fd7bf11997f __poll (libc.so.6 + 0x10397f)
#1  0x00007fd7bf5155c7 n/a (libglib-2.0.so.0 + 0x5b5c7)
#2  0x00007fd7bf515cf1 g_main_context_iteration (libglib-2.0.so.0 + 0x5bcf1)
#3  0x00007fd7b83a03a6 n/a (libdconfsettings.so + 0xb3a6)
#4  0x00007fd7bf544d18 n/a (libglib-2.0.so.0 + 0x8ad18)
#5  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#6  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20507:
#0  0x00007fd7bf11997f __poll (libc.so.6 + 0x10397f)
#1  0x00007fd7bf5155c7 n/a (libglib-2.0.so.0 + 0x5b5c7)
#2  0x00007fd7bf515cf1 g_main_context_iteration (libglib-2.0.so.0 + 0x5bcf1)
#3  0x00007fd7bf515d42 n/a (libglib-2.0.so.0 + 0x5bd42)
#4  0x00007fd7bf544d18 n/a (libglib-2.0.so.0 + 0x8ad18)
#5  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#6  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20508:
#0  0x00007fd7bf11997f __poll (libc.so.6 + 0x10397f)
#1  0x00007fd7bf5155c7 n/a (libglib-2.0.so.0 + 0x5b5c7)
#2  0x00007fd7bf515fd7 g_main_loop_run (libglib-2.0.so.0 + 0x5bfd7)
#3  0x00007fd7bbc82f10 n/a (libgio-2.0.so.0 + 0x121f10)
#4  0x00007fd7bf544d18 n/a (libglib-2.0.so.0 + 0x8ad18)
#5  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#6  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20513:
#0  0x00007fd7bf12913b __socket (libc.so.6 + 0x11313b)
#1  0x00007fd7bf13afa5 n/a (libc.so.6 + 0x124fa5)
#2  0x00007fd7bf1555e6 getaddrinfo (libc.so.6 + 0x13f5e6)
#3  0x00007fd7c0712846 n/a (libQt6Network.so.6 + 0xdc846)
#4  0x00007fd7c07bd1d8 n/a (libQt6Network.so.6 + 0x1871d8)
#5  0x00007fd7c071377c n/a (libQt6Network.so.6 + 0xdd77c)
#6  0x00007fd7bfac6d52 n/a (libQt6Core.so.6 + 0x4c6d52)
#7  0x00007fd7bfabf3cf n/a (libQt6Core.so.6 + 0x4bf3cf)
#8  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#9  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20510:
#0  0x00007fd7bf12444d syscall (libc.so.6 + 0x10e44d)
#1  0x00007fd7bf57436c g_cond_wait (libglib-2.0.so.0 + 0xba36c)
#2  0x00007fd7bf4dc72c n/a (libglib-2.0.so.0 + 0x2272c)
#3  0x00007fd7bf4dcbe9 g_async_queue_pop (libglib-2.0.so.0 + 0x22be9)
#4  0x00007fd7bb22aa75 n/a (libpangoft2-1.0.so.0 + 0xda75)
#5  0x00007fd7bf544d18 n/a (libglib-2.0.so.0 + 0x8ad18)
#6  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#7  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20504:
#0  0x00007fd7bf11997f __poll (libc.so.6 + 0x10397f)
#1  0x00007fd7bf5155c7 n/a (libglib-2.0.so.0 + 0x5b5c7)
#2  0x00007fd7bf515cf1 g_main_context_iteration (libglib-2.0.so.0 + 0x5bcf1)
#3  0x00007fd7bfbebca2 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x5ebca2)
#4  0x00007fd7bf9021ba _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3021ba)
#5  0x00007fd7bfa160d6 _ZN7QThread4execEv (libQt6Core.so.6 + 0x4160d6)
#6  0x00007fd7c10cb92a n/a (libQt6DBus.so.6 + 0x4e92a)
#7  0x00007fd7bfabf3cf n/a (libQt6Core.so.6 + 0x4bf3cf)
#8  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#9  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)
ELF object binary architecture: AMD x86-64

                                              Since week 22 update all three versions of the firefly iota wallet (firefly-iota-desktop-2.0.10.AppImage; firefly-shimmer-desktop-2.1.15; firefly-canary-desktop-3.0.1.AppImage) crash on start. The apps work normal in Windows Virtual Machine. I think the AppImages are Electron based . Budgie Desktop. Any ideas?