penny-farthing of the Nvidia pilot (V 470.182.03-29),
how does that work?
penny-farthing of the Nvidia pilot (V 470.182.03-29),
how does that work?
Wonderful update just now.
Thank you so much Solus team.
Hi all! Sorry for the issues with this sync. It came down to an innocent change (nvidia-drm) going rogue. On my test system everything went fine, on community testing it went to crap, and we tried running to get it going to no avail. I bumped the kernel and reverted the changes (for now) this morning.
Context: We're looking to finally bring functioning GNOME+Wayland to Solus and we're busy fighting the NVIDIA drivers.
Sorry that we slipped on communication, we're working together to determine a better path forward
I didn't plan to write anything more on this subject, but I wanted to leave it with one more post.
I was able to create an account very easily, just by using an email account from a different domain. It's from vivaldi.net, in fact, an account I created a while ago in case I ever needed it. Looks like I finally did.
I haven't a clue why Element's email couldn't be delivered to my wetgeek.net account. That shouldn't have happened. When I used the vivaldi.net address, it arrived immediately, and there were no further issues. Thanks to anyone and everyone who helped me with this.
Update all three of my machines . all updates went okay.
thanks again to development team .
Update went smooth on all my Solus machines. Thanks a lot !
I really don`t understand this every week updates.
For me it is ready when it is ready.
Everyone knows the devs are working on other things so what ?
brent It seems to be working fine, no difference in picture quality, no distortion or jerkiness in videos so far.
MikeK61 I really don`t understand this every week updates.
For me it is ready when it is ready.
That's the way it works elsewhere. During the three months of the Solus Troubles, I used two other distros, Sparky Linux and Siduction OS, both with the Plasma DE and both configured the same way I configure Solus Plasma. Both are Debian-based, and both are at least semi-rolling releases. I could almost forget that that I wasn't using Solus, but neither of those had the Solus Forum, so they just didn't feel like home to me.
Anyway, they both received updates frequently and at various times, not according to any set schedule, but just when things became available. A popup notification (like Solus') would let users know that there were upgraded packages available, and users could decide whether it was a good time to update, or we would rather wait a while.
Solus could easily adopt such a scheme. It would totally releive any undue pressure on the dev team. It would not affect Solus' "rolling release" reputation. It wouldn't prevent us from an occasional milestone release (like Solus 4.4, for example). And since everyone would be notified whenever there are upgraded packages available, that would totally elimate our collective anticipation of a sync every Friday and disappointment when it doesn't happen on Friday, or Saturday, or Sunday ...
WetGeek I have no doubt, in the growth plan going forward, that all automated updates of things that get fixed or patched daily will likely occur in Solus. All to come and I'm also sure all things like that are on the table.
Even Fedora is daily or 'as they come' as you say.
Right now we do extensive testing on each updated package and the final yea/nea goes thru 1-2 people. This is a proven system so far and more suited for a team all over the planet with jobs and lives outside Solus. RHEL (Fedora) and Debian are virtual nation states with fulltime crews.
I'm sure Solus updates will evolve to a more consistent model eventually, Baby steps.
In this debate on the information of users concerning Solus updates (quite understandable), it should also be remembered that Solus is a volunteer project, not a company as Beatrice wrote in a post of 01/26/2022 . The seriousness and professionalism of development and management teams are no longer to be demonstrated. Perhaps, we should also meditate on a cardinal virtue in the Far East : patience...
Updated this morning. As soon as the update finished, I was kicked to the log-in screen. Logged back in and none of the programs I had open were running anymore. Restarted and everything appears to be fine, but as this is not common behavior and for me has not happened before, just wanted to report. I appreciate everyone's work on this distro. I'm using the Plasma edition.
WetGeek Forgive me if I misunderstood you but, for me, I installed Solus with the Budgie desktop and when updates are available, I receive a popup informing me of their arrival and so, I don't not need to go and check if they are here.
penny-farthing I don't not need to go and check if they are here.
I'm not suggesting that you should do anything differently than you now do.
WetGeek OK thank you, understood.
Synced this week by @EbonJaeger - current sync conductor =)
ikey With the valuable assistance of yourself. Thanks again!
I have just update my system Solus with 16 packages (315.59 MiB).
But I noticed that Solus had moved to version 4.4:
administrateur@solus-pc ~ $ lsb_release -a
LSB Version: 1.4
Distributor ID: Solus
Description: Solus
Release: 4.4
Codename: fortitude
And nothing reported since (for my part) : congratulations to the whole team !
penny-farthing same here. Budgie. 17 packages. reboot. cool. Observation: Budgie not getting many updated packages lately. KDE is getting a ton. Just the way the worm turns.