Sync Updates for Week 9 and 10, 2024

ReillyBrogan

I would like to note that Plasma 5.27.11 was released today. Just to set expectations here Solus WILL NOT be updating to that version. There's no real critical bugfixes in it and we're going to be updating to Plasma 6 sooner rather later anyway.

How soon you might ask? 🤫

WetGeek

I'm having an issue connecting with my NAS on the Plasma laptop. When I rebooted after installing the update, I next invoked a mount -a to connect with all the NAS shares, and got an error telling me that "server DiskStation415 not found." Could be a DNS problem of some kind?

To find out whether the NAS was okay without running upstairs to check it, I tried accessing it with my travel laptop, which hadn't been updated yet, and there was no problem. Plasma is the DE on the laptop that failed and the travel laptop that hadn't been updated, so the problem appears to be update-related.

To determine whether it was a KDE issue, I next tested the Xfce laptop (which had also been updated). There was no problem with the Xfce laptop. the mount -a command completed successfully, and I was able to access my ISOs share when I tried. So, this appears to be an updated-related problem that affects only Plasma.

EDIT: On the Plasma laptop where I discovered this problem, I launched a Budgie VM. I was able to connect with the NAS without an issue, and access one of its shares. So no problem there.

Justin

WetGeek what is the contents of your /etc/fstab for this mounted NAS?

WetGeek

Justin what is the contents of your /etc/fstab for this mounted NAS?

DiskStation415:/volume1/Videos /mnt/Videos nfs defaults 0 0
DiskStation415:/volume1/Torrents /mnt/Torrents nfs defaults 0 0
DiskStation415:/volume1/SourceControl /mnt/SourceControl nfs defaults 0 0
DiskStation415:/volume1/SourceArchives /mnt/SourceArchives nfs defaults 0 0
DiskStation415:/volume1/Pictures /mnt/Pictures nfs defaults 0 0
DiskStation415:/volume1/Music /mnt/Music nfs defaults 0 0
DiskStation415:/volume1/Keys /mnt/Keys nfs defaults 0 0
DiskStation415:/volume1/ISOs /mnt/ISOs nfs defaults 0 0
DiskStation415:/volume1/Downloads/Linux /mnt/Downloads/Linux nfs defaults 0 0
DiskStation415:/volume1/Documents /mnt/Documents nfs defaults 0 0
DiskStation415:/volume1/Books /mnt/Books nfs defaults 0 0
DiskStation415:/volume1/Backups/Linux /mnt/Backups/Linux nfs defaults 0 0

(next day)

It gets even stranger. I attempted this backup just before I retired for the night, and I didn't think of everything I could have tested. Here's how it looked at the time in Terminology:

But this morning, I can access these shares quite normally on that machine using Dolphin, either via smb or nfs.
And without doing anything else in the terminal, it's now working there as well.

Sorry to sound the alarm. This is the weirderst thing that's happened to me since I started using Solus. I'll change my survey to indicate no issues. And thanks for responding quickly.

(later)

Naturally, I can't stop thinking about what might have happened here. The only thing I did between the mount -a that failed and the mount -a that succeeded was to try accessing these shares in Dolphin. And Dolphin is able to mount things. I suppose it's possible that Dolphin did what the terminal command was unable to do. That's the only possible explanation I've been able to come up with.

Axios

2 comp updated very smoooothhhhhhhhhhhh update!
Thanks devs

Solarmass

thanks, nothing to report 👍️

penny-farthing

264 Solus updates (1.66 GiB) today and nothing special to report either.

Once again, I'd like to salute the @EbonJaeger 's remarkable effort in writing a documented commentary for Solus update each week, which will undoubtedly delight its users.

Cheers! 😃

tiberiy0

Thanks guys, everything seems to be going well.

JTCPingas

Everything went well. No problems to report.

ReillyBrogan

Note to Plasma users, if you notice VLC getting installed during these updates then that's expected behavior. Plasma depends on something called Phonon, which is basically a framework that it uses to integrate media into the DE (notably this is used for notification sounds, not the audio output of the sounds but the reading of the files to get the chimes from and whatnot). There are multiple backends for Phonon, previously we were using the gstreamer one however that one is unmaintained and not compatible with Plasma 6. We thus had to switch to the VLC backend. It's on my todo list to split the VLC package up into a package containing just the libraries that Phonon needs and some core codec support so that Plasma can just depend on that and not need all of VLC installed but for now you'll have to live with having the full VLC package installed. Attempting to remove the VLC package will result in a lot of core Plasma components getting uninstalled, so I would not advice trying that.

WetGeek

ReillyBrogan you'll have to live with having the full VLC package installed

I really like VLC, and always have. After you split off the parts needed for Phonon, will the whole VLC still be available?

larsag

ReillyBrogan Thx for the info. I had to reinstall Solus KDE after having removed VLC . Looking forward to the split so I can remove it without breaking KDE.

Staudey

WetGeek Of course! It will just be possible in the future to install certain components of VLC (like those required by phonon) on their own, without installing the whole player with all bells and whistles included.

EldrinSMP

This was my my first Sync with Solus it was bumpy but I got through it... I think. LOL. I actually had to run the update 3 times, as the first two time the updates didn's "stick: almost like it was done as a dry-run. It was actualyl really weird. I ran the update, then 20 minutes later Software Center is screaming at me that there are 217 NEW updates to install. That's when I went to the command line and rand the update and discovered that my eopkg database somehow got corrupted. Ran the update again as 'sudo eopkg up --debug' and found the issue. A quick sudo eopkg rdb and sudo eopkg rb and everything was fine. The update went through without a hitch on the third try.

I did notice that the search function on the Software Center was not working for a large portion of yesterday, but the CLI search worked fine. Is that normal for an update or was that a symptom of my eopkg problems? I still have a few unresolved issues, (my application launcher, the Kickoff one, is HUGE and in the center of my screen and I can'[t get it back to normal! LOL) and one major one that is actually going to decide whether I stay with Solus or not (NVIDIA Drivers... Uggh). I REALLY hope we can get it fixed, because I really like this distro (granted, it's the second one I've tried, but still... If I leave it's probably to Manjaro or Garuda). Expect a few new posts from me in the next hour or so!

Side note, any housekeeping scripts / cleanup scripts / login or logoff scripts / dear god I sound like an addict / general useful things to make life simpler that your guys have and might like to share would be greatly appreciated. Thanks!

Axios

EldrinSMP Sounds like you ran the first update something happened and you ran it again
not knowing but then fixed it so the third try worked.
This is not typical of updates I would run it from command line next time so you can see
whats going on you for a few times can always go back to gui.

Best way pick up tricks is do forum searches you can usually find what you want then I put them in a text file.

Grami_fr

Freecad Appimage et Freecad Link Branch (RealThunder) no longer works after this update... The appimages launch, we see the Freecad startup image/logo and the scripts load, but after that, no application windows and nothing more. :-( Hum...problem with python?

Grami_fr

Freecad with the classical installation work! It's only the freecad appimages that no longer work.
Here are the errors sent: WebEngineContext used before QtWebEngine::initialize() or OpenGL context creation failed.
QGLXContext: Failed to create dummy context
Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options
/tmp/.mount_FreeCAoi0Qin/AppRun : ligne 43 : 8391 Abandon (core dumped)${MAIN} "$@"

ReillyBrogan

Grami_fr Might be mesa-related. Regardless, we can't really do anything about whatever dependencies some appimage chooses to bundle not being compatible with system dependencies. You should report the issue to whoever provided the appimage or just use a different method to run freecad.

Axios

I dont depend on appimages anymore with all the changes in the linux world Flatpaks are
turning out better and updated better.
I dont let one not working mess up my day.
Freecad has a flatpak.

If its a simple appimage app they usually work

Harvey

discord 0.0.45 cherry-picked.