What is planned for gnome 3.34?
It would be really nice if it could be deployed on Solus soon.
@JoshStrobl
Gnome 3.34
- Edited
Solus does not do ETAs and usually waits for the .1 regardless for gnome.
- Edited
kaliangel but I'm still asking if it's planned to spend a day on GNOME 3.34
It's not really "a day", it's going to take several days to perform a local upgrade and testing of several hundred packages, determine what I need to hold back (such as what GNOME has tried to shove libhandy into this cycle), and if Budgie is in a sufficient state for it. From what I've seen, very little of the Mutter ABI has changed, so it shouldn't be problematic with the patches we already have in git. That isn't usually the case, typically they like to break the world, so given the history @kyrios is pretty spot on.
The last GNOME stack upgrade was delayed significantly because when the .0 was released when we were working to get infrastructure migrated and people moved over to new repos, so it was just bad timing in general.
I will be updating us to 3.34.0 though, to answer your question. This GNOME release is pretty tame, so it's more just a time sink than anything else.
[deleted]
I am always keen for an upgrade, but take your time, guys. From what I understand is that Gnome upgrades are tricky with breakages and whatnot?
Please, please guys. Don't let yourself get mad. First it was Gnome 3.1 then 3.2 etc. etc. It will come in time. I am sure that my beloved Solus Gnome won't run better (after so many years) before the newest Gnome-version is installed. Remember to everyone: Solus will not ever, never give you ETA's. Take it easy. It will come in time.
5 days later
[deleted]
evert I am in no hurry. I have faith in the solus team 
You can watch JoshStrobl build it for us here:
As GNOME 3.34 worked on Nvidia problems, i hope the gaming on GNOME based environments can get better.
On Arch Linux, installing the updates to Gnome 3.34 breaks the Budgie DE really bad, it crashes with 'oops something gone wrong' on a white screen when logging in.
So be careful when implementing
Well, it's a good thing I'm the developer of Budgie then, right? 
TarsolyGer This also shows the difference between bleeding edge and curated rolling releases.
Personally, I would advise to prefer using the DE at the source (Budgie on Solus, Cinammon on LinuxMint, Pantheon on ElementaryOS, ...). If you don't, then use them on Fixed point release distros to make sure it's properly tested.
Running after new versions is always a risk, unless you stick to the main Arch repo, avoid Community and AUR, you'll always have to refrain updating, checking carefully what's going to be updated and waiting for community bug reports.
That's one of the reason ArchLinux isn't targeted for anyone.
Regarding Budgie, you should follow this: https://bugs.archlinux.org/task/63849?project=5&string=budgie-desktop
- Edited
JoshStrobl That's why I thought to give you a heads-up on the issue that's going on 
kyrios Thanks, I'm on the bug report and also following up the forum discussions. The beauty of Arch Linux is that I could just roll back my stuff to a date when everything worked even without a system backup (silly me), so I don't lose productivity while these issues are ironed out. I understand that Arch's assumption that "all software should always work with the newest version of its dependencies" is not something that is easy to follow or would ever be followed with all the software that's out, so these issues are to be expected there I guess.
- Edited
From the report:
Sep 19 16:06:55 arch-laptop gnome-session[919]: gnome-session-binary[919]: WARNING: Unable to find required component 'org.gnome.SettingsDaemon.Clipboard'
Sep 19 16:06:55 arch-laptop gnome-session-binary[919]: WARNING: Unable to find required component 'org.gnome.SettingsDaemon.Clipboard'
Sep 19 16:06:55 arch-laptop gnome-session[919]: gnome-session-binary[919]: WARNING: Unable to find required component 'org.gnome.SettingsDaemon.Mouse'
Sep 19 16:06:55 arch-laptop gnome-session-binary[919]: WARNING: Unable to find required component 'org.gnome.SettingsDaemon.Mouse'These were moved out of GSD in 3.33.90+ and Budgie is already patched to not require those: https://github.com/solus-project/budgie-desktop/blob/master/src/session/meson.build#L57 Furthermore, gnome-session was already updated to reflect the GSD changes.
Not to mention we don't actually need those, we never utilize them in Budgie. Someone is reporting the same issue but on GNOME, so very much not a Budgie issue but rather something on Arch Linux's end. Not my problem, use Solus 
The beauty of Arch Linux is that I could just roll back my stuff to a date when everything worked
The beauty of Solus is this update wouldn't ever get to you in a broken state in the first place...
Yea, 100% an Arch Linux issue
Good job @JoshStrobl 
- Edited
This thread really makes me appreciate that I switched to Solus from an Arch base (the previous distro I've used the longest was Antergos) even more 
[feelsgoodman]
I'm looking forward to when it's finally available.
Your work is greatly appreciated @JoshStrobl
That's the beauty of a curated rolling release. You get to use mostly new stuff, but without the headache of bleeding out on the edge like on something Arch-based.
It's VERY nice to feel safe when performing updates.
Tbh before I had found Solus, I never would've even guessed I could be so happy with a distro. Even then I had been using Linux for a while and I was happy with it, but it was Solus that somehow miraculously managed to push it to over 9000.
Junglist Love Solus 3,000 
Upgrade is now available for those on unstable. see this task on our development tracker.
Now I shall wait a bit for someone on unstable to update, report back, then I'll be off to bed. Just pushing the packages took 14 hours (not to mention the days of actually working on the package updates, testing, etc.) and I'm tired >.<