Amber is well tested and stable. Byzantium is a rolling release, not well tested and unstable.
Was this fixed for anyone yet? I’ve noticed a few more upgraded packages in Byzantrium since when running apt update && apt dist-upgrade (even some gnome things like gnome-terminal), but gdm3 still doesn’t start here.
Nope, it isnt fixed, updated today and nothing changed.
1 Like
The latest GNOME Shell is coming into Byzantium: https://software.pureos.net/package/bin/landing/gnome-shell
Basically the options are;
- install from Debian unstable (this is tricky, but can be done.)
- wait for GNOME Shell 3.36 to come into Byzantium (should be real soon now
) - Install from source package (which requires you build it and have built the dependencies)
There is a bit more of a wait: https://software.pureos.net/package/excuses/1de9ddf6-8502-4216-b5d3-0be977073ae0 (gjs is the blocker).
4 Likes
Just one thing that I don’t understand, this is fixed in Debian Testing now, why not in PureOS Byzantium?
Because there is a few days difference for the packages to transition in PureOS
1 Like
I’m not an expert on this, would it be possible to use Debian Testing repositories as they update and add the software needed for PureOS over that? What need PureOS nowadays to be PureOS?
Thanks for your answer.
Is this not the package which is in landing but not in Byzantium preventing gnome-shell from working
https://software.pureos.net/package/bin/landing/gir1.2-mutter-6
1 Like
I’d say yes, but it’s not really obvious why it’s not in byzantium already
1 Like
Another round of updates yet no working GNOME. I’m starting to consider switching to another distribution. Please fix this.
hi @jeremiah ! in the latest Debian testing i can’t raise the “network connections” front end under GNOME by typing in the CLI nm-connection-editor as non-root-user nor as root-user it’s simply not there … neither is pppoeconf
is this situation the same under PureOS Byzantium ?
i know i shouldn’t be asking this since testing-ANYTHING is recommended to be run under a virtual environment and not directly on bare-metal … but … could you oblige ? 
1 Like
Having backups and another system ready to boot on an USB drive, I don’t care encountering occasional breakage with a testing or bleeding edge distribution, other than the little extra time and loss of comfort it may create. Until this issue with Gnome, I’ve been very happy with updates in Byzantium, e.g. LibreOffice 6.4.
I’m sorry to be too busy with my daily job in this period to help deeply troubleshoot this issue; I’m unsure I could update today without breaking Gnome, as choosing the following dependency conflict mitigation in Aptitude would lead to a cohabitation between two installed versions of libgnome-desktop (3.18 and 3.19):
I’m thinking of not updating my main PureOS installation until the dependency confilcts to be solved in Gnome core and the transition from 3.34 to 3.36 to be almost complete.
2 Likes
Fixed it.
Downloaded manually the packages libgirepository-1.0-1_1.64.1-1, libgjs0g_1.64.1-3_amd64.deb and gjs_1.64.1-3_amd64.deb from https://software.pureos.net/suites, installed it via sudo dpkg -i PACKAGENAME, made an sudo apt --fix-broken install afterwards and upgraded via sudo apt upgrade normally.
Running pretty smooth until now
2 Likes
I tried that, now apt --fix-broken install wants to remove: gdm3 pureos-desktop pureos-gnome
This seems like a bad idea? Did you go ahead? If so, what do you use as display manager now?
Maybe i forgot something, let me check when i am at my computer again.
Oh I did something stupid. One of the packages I downloaded was arm64 instead of amd64 
After installing the following three it seems to go much better:
https://repo.pureos.net/pureos/pool/main/g/gobject-introspection/libgirepository-1.0-1_1.64.1-1_amd64.deb
https://repo.pureos.net/pureos/pool/main/g/gjs/libgjs0g_1.64.1-3_amd64.deb
https://repo.pureos.net/pureos/pool/main/g/gjs/gjs_1.64.1-3_amd64.deb
Edit: yess! that fixed it, GNOME works again, thank you!!!
1 Like
You might be okay using Debian Testing alongside PureOS, but it’s a Frankendebian that can possibly break things in the same way that waiting for updates from unstable can. Okay, your software breaks earlier, but it will still break. This is what we saw with Debian Testing and this GNOME transition.
I don’t know if this is the same under Byzantium but I’ll test.
1 Like
Yesterday, I started selectively picking package updates in aptitude, and today there are still conflicts if I select all available updates, and gjs update that solved the broken state of Gnome for @peterpan and @vmedea is not officially available yet in Byzantium. I chose not to update the following packages (I’m not sure why Aptitude pretends they are automatically held back, as I picked most package updates manually):
I write this not for a complaint, but for Byzantium users who want to and can take the path of selectively picking packages to update, until the transition of Gnome from 3.34 to 3.36 gets smoother. 
1 Like
This will take a little I suppose.
I have a fully upgraded system now, but had to install libhandy from amber-updates manually to get seahorse and gnome contacts back (because several gnome apps do have this dependency now)
And I can’t get gnome-control-center running because this seems to be a package which was changed by Purism - so it has to be updated first from them i. e. integrating their changes to the new 3.36 release
1 Like