I'm using Budgie and this is still happening for me.

I have had this issue with snaps, what fixed it for me was reinstalling snapd from the ternimal:

It is a known issue not related to this, the devs are working on a fix: https://discuss.getsol.us/d/58-update-install-errors/4

Dont you mean the boot menu? It is described in the Help Center under "Boot Management": https://getsol.us/articles/troubleshooting/boot-management/en/

Sounds good, just wanted to report it.

Tried to update again, this time the nvidia driver downloaded fine, but then it got stuck at the Vivaldi update:

Fixed for me to with the new aa-lsm-hook package, thanks.

Have tried this on Solus Budgie with my Intel l219V nic, and it works for me with the settings you show in the picture.

Now that you know how to Chroot into your system from a liveusb, have you tried the original suggestion by Girtablulu?:

It looks like your system has 2 kernels installed: 4.18.5-90 and 4.18.16-97

So if you run: CBM_DEBUG=1 clr-boot-manager update do you get the same result as the user gets here?: https://getsol.us/forums/viewtopic.php?t=10871#p34756

Edit< Posted while you provided the picture above, which gives the answer...

This update from unstable fixed my issue: https://dev.getsol.us/R1964:2f721de067b0b9de3ee8c2cab382de6e10d70f12

This update from unstable fixed my issue: https://dev.getsol.us/R1964:2f721de067b0b9de3ee8c2cab382de6e10d70f12

I rolled back to a previous update (with kernel 4.19.8-104 or older) using the help center guide: https://getsol.us/articles/package-management/history-and-rollback/en/
It's important that you read the last line!

Did a sudo eopkg up in the terminal, so i expect it did but did not check it.

Todays update (28/12) did not change anything for me, had to roll back to the update with the 4.19.8-104 kernel, then update everything except todays kernel.

So far it seems like i am the only one able to boot the latest kernel, but not without issues as it was a slideshow.

Looks like the last update are causing different issues for AMD RX560 & RX580 users (Polaris GPU).

I was able to login using the LTS kernel with my RX 560, had no HDMI sound though.

Not sure if what i describe below is related to this issue, just wanted to pitch in...

EDIT: Updated the terminal install commands

If you look at this package request for another app, you can see how your description should look like: https://dev.getsol.us/T7355

In T6020#134310, @grim85 wrote:

In T6020#134308, @DataDrake wrote:

We also removed it because their licensing is cumbersome. Having something stop working between syncs because a license expires is not OK.

So for those who own a license, what is the solution going forward?

This issue have been bugging me to, think i found out about it a couple of months ago, had a look at my NAS permission settings, as i thought it was caused by a software update on the NAS. Have not been able to fix it of course, now that i see it is a samba issue, thanks for filing a bug report.

Thank you for the workaround Kyrios, the drive shows up after reboot now.

Same issue here, think it started after the latest MakeMKV update 9/2-2018, cause it has worked fine not to many months back.

This happened for me from time to time 1 - 2 month's ago, but it went away again. When i left the machine with the blinking cursor in the top left corner, it would eventually shutdown or reboot, but i guess it took 1 - 2 min. for it to do so.

There is an alternative but without a gui, i also used pypar before switching to Solus, but found "par2cmdline" in the software center which is what i am using.

inxi -G
Graphics: Card: Advanced Micro Devices [AMD/ATI] Baffin [Radeon RX 560]

Display Server: x11 (X.Org 1.19.6 )
drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon)
Resolution: 1920x1080@59.94hz
OpenGL: renderer: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.7-60.current, LLVM 5.0.1)
version: 4.5 Mesa 17.3.6

Strange how things work differently on your end, don't understand why you would get everything listed under "Password:" above (i don't), running "sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall" on my system, will give me a blinking cursor after i enter my password, while eopkg is checking for broken packages (this takes some time to complete).

old_curmudgeon did you uninstall 0.13.1 and removed the old config files, before installing 0.14.15 from unstable ?

These parts are different for me:

I'm using Solus Budgie and deleted the Albert config files in the .config & .local folder, before installing and running it again.

Works absolutely perfect for me again, after using sunnyflunk's instructions to install it from unstable.

Yes my system is fully updated. Tried connecting to a few servers yesterday, just to make sure it worked. For me servers in Netherlands, Austria and Belgium worked as they should.

I've used AirVPN on Solus Budgie since may, and upload my config files like you showed in the first post. So far i have no issues connecting, and the connection is never dropped before i choose to.