Update via terminal of 108 went fine here except for wesnoth where it hanged a little. I did ctrl-c and try to update again and it went ok. Maybe it was because of weak wifi signal...

What a boring update, everything is working. 😝 I think I have to start steam or do some productive work.

New user here. Two weeks, updated with no problems.
Thanks.

im using solus gnome version, since the update my sound volume level doesn't change via the upper right sound controls, i looked in the settings sound menu and it keeps switching to hdmi/displayport sound
edit: i did update via the software center, it hanged at the brave browser download, so i closed the software center and did the update via the terminal, which was successful

    Over here (Gnome) NO problems at all.

    I didn't restart immediately after updates cause i was on youtube.. but i left the computer to do something for like 5 mins and when i came back, I found my desktop completely black with a message saying "my screen locker got broken".
    I restarted my computer and noticed my audio was out and both full and force full composition pipeline were unchecked for some reason.
    After i checked both of them solved the jittering I was experiencing. I also unplugged and plugged my headphones back which fixed my audio issue. Idk why this happened and don't know how to reproduce the effect again but just want to let you know in hopes it can help others.

    Other than that.. everything is back to normal with this amazing OS. I'm on Plasma btw.

    I've done the update (from the GUI). Nothing reported, so I've expected that the update finished successfully.
    But, at the restart, whatever I do it defaults to the LTS kernel. Manually selecting the current one works.
    I've tried to update it with clr-boot-manager; I've tried to mount the boot partition, thinking that maybe the problem is connected to this; nothing. Even if the default kernel is the current one it keeps loading with the LTS one.

    Actually I would say that the thing is not so dramatic, because I can set a small timeout and choose the correct kernel at start. The main problem is that if I start with the dock connected (a USB-3 connected to a shared Thunderbolt/USB-3 port), both the keyboards freeze and I can't select anything. Hence I've to restart the notebook without dock connected; choose the correct kernel; connect the dock; start working. A bit complicated way to start the day (or the week).

    Before the update everything was working. I was used to work with the LTS kernel, but since the previous update I've had to switch to the current (that on the Dell 9560 has some small problems, but I can live with them).

    Everything went fine. If I might, do we still need the openssl package after update, since we now have the openssl-11 one which seems to handle the correct system paths (ie openssl installs files in openssl-1.0) ?

      barbaros83 ive had the same sound switching issue since updating. so far its done its done it every time i restart my pc. im using solus budgie. other than that its been a smooth update

        I had an update of more than 150 packages today...smooth as usual 😃 Thanks @ the Solus team for this awesome job and updating openssl to 1.1. Now I can play Chronicon's native linux build. 😄

        Everything seems to be working fine after the update, except for Opera. When I try to launch it, it just starts and closes immediately a few times before the process hangs with no window visible (have to kill it manually).

        When launching Opera from the terminal, the output is:
        nathan at computer in ~
        ↪ opera
        [12093:1:0703/191907.705022:ERROR:child_thread_impl.cc(792)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
        fish: “opera” terminated by signal SIGILL (Illegal instruction)
        nathan at computer in ~
        ↪ [12587:1:0703/191910.605440:ERROR:child_thread_impl.cc(792)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
        Discarded=1
        Discarded=1
        [13172:1:0703/191914.688738:ERROR:child_thread_impl.cc(792)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
        CrashID=48329e87-a0bf-4d4e-bf91-991012200703
        Discarded=1
        [12296:12300:0703/191914.927711:ERROR:broker_posix.cc(40)] Recvmsg error: Connection reset by peer (104)
        [13681:1:0703/191918.044410:ERROR:child_thread_impl.cc(792)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
        CrashID=5520e77b-a33d-4092-bdad-dd50f2200703
        CrashID=6b4a4f92-4c53-4b56-9a6b-99c482200703
        [12914:12918:0703/191918.512821:ERROR:broker_posix.cc(40)] Recvmsg error: Connection reset by peer (104)
        CrashID=8b6102e6-f38d-42f9-bc1a-a2e302200703
        Discarded=1
        There's no more output when I kill the process with Ctrl+C. I tried rebooting, and the problem persists. Anyone got clues? Congrats for the otherwise massive bug-free updated! 🙂
        Edit: Also ran sudo eopkg check and can confirm that all packages on my system are OK.

          nathanpainchaud
          Just double check that everything was updated:
          sudo eopkg up -y
          And reinstall opera anyway:
          sudo eopkg it --reinstall opera-stable

          Because I can not reproduce it.

              Full update on my work machine with both budgie and gnome DE's installed, both are still working great without any issues regardless of which de I log into.

              Harvey I've double checked and everything is up-to-date. I've reinstalled it (and even tried clearing eopkg's cache in case something went wrong with the download), and I still had the same issue. I fixed the problem by deleting ~/.config/opera and ~/.cache/opera and reinstalling. Some of that might have been overkill, but now everything seems to be working. Some of my local config must have got corrupted was not recognized anymore after the update?

                  nathanpainchaud
                  Glad you were able to fix it 🙂

                  Clearing the config was going to be my next suggestion, it is possible that the config had become corrupted some how or an extension / setting you had enabled has issues with the newer version. I've tried 3 different systems and it's been fine so hopefully no one else encounters it.

                    The update did not go quite as smooth for me. Lightdm / x server won't start now. I made a ticket for that here.

                    Hi everyone, I seem to be having some trouble getting Solus to boot after yesterday's sync. I'm getting that blinking cursor and I can only get past it if I use nomodeset. So once I accessed the TTY, here's what inxi -G says:

                    Graphics:
                    Device-1: NVIDIA GP104 [GeForce GTX 1070] driver: nvidia v: 440.82
                    Display: server: X.org 1.20.8 driver: nvidia note: display driver n/a
                    FAILED: nvidia tty: 80x25
                    Message: Advanced graphics data unavailable in console

                    I'm running kernel 5.6.4-152.current and I seem to be up to date with all Nvidia drivers. Any idea what I can do? I'm a pretty average user and I don't usually go into the depths of Linux, so any help will be greatly appreciated 😅