** Changed in: gnome-shell (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/2077232
Title:
Security update 42.9-
i386 has been enabled by default on amd64 for quite some time.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/2077232
Title:
Security update 42.9-0ubuntu2.2 uninstalls GDM
> The only thing is, installing updates through the GUI default upgrader
is NOT supposed to accept solutions that require removing packages.
If having multiple architectures enabled was a factor here then surely
we're already outside the realm of a bug that can be reached through GUI
interactions
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/2077232
Title:
Security update 42.9-0ubuntu2.2 uninstalls GDM
To manage notifications about t
The only thing is, installing updates through the GUI default upgrader
is NOT supposed to accept solutions that require removing packages. So
this really needs to be tracked down and fixed. I don't think there's
anything further to be done in gnome-shell.
** Also affects: gnome-software (Ubuntu)
I suppose we *could* do the same in Jammy and Noble updates. But again
that only prevents the issue from recurring and doesn't fix the
brokenness if it's already in that state.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shel
I'm going to declare this done for Oracular, but we can't fix the hard
dependencies that already exist up to and including Noble. Because those
dependencies are already on peoples' hard disks.
https://salsa.debian.org/gnome-team/gnome-
shell/-/commit/40849f7efd55e48346ecb9ed3e171ae1ad75adb0
No lo
> My current libshumate proposal still wouldn't help to solve this class
of problem if we update gnome-shell 42.8 to 42.9; it would only help for
something like 42.9-0ubuntu2.1 to 42.9-0ubuntu2.2
Good point. I think we'll need to use hardcoded ">= MAJORVERSION" or ">=
LASTSCHEMACHANGE", not ">= ${
> How did you trigger the actual update? Was this through the update-
manager GUI? Did it offer to install gnome-shell-common for you and
remove the other packages? Or did you use apt directly to do this?
It was a recommended upgrade, suggested by one of the GUIs that
sometimes come up automatical
My current libshumate proposal still wouldn't help to solve this class
of problem if we update gnome-shell 42.8 to 42.9; it would only help for
something like 42.9-0ubuntu2.1 to 42.9-0ubuntu2.2
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
Cool, that's what I was thinking of in UDENG-4068. I too was thinking an
upper bound would be preferable but if lack of an upper bound isn't
causing problems yet then at least ">= ${upstream:Version}" doesn't
require any maintenance.
--
You received this bug notification because you are a member
Daniel, see https://salsa.debian.org/gnome-
team/libshumate/-/merge_requests/4
I didn't get any feedback on that proposal. If successful, I was
intending to copy that pattern to other Debian GNOME packages.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
Removed tag 'regression-update' because this sounds like it's correlated
with the unusual state of this machine, and could in fact happen in any
gnome-shell update.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Tags removed: regression-update
--
You received this bug n
** Changed in: gnome-shell (Ubuntu)
Importance: Critical => High
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net
This is the second time in recent memory that gnome-shell-common has
caused upgrades grief. In this case, I don't think requiring equal
versions is sensible:
Package: gnome-shell
...
gnome-shell-common (= ${source:Version}),
The main ABIs of gnome-shell-common are /usr/share/glib-2.0/schemas
Ok, sorry for overlooking.
Here's what it should look like:
$ apt policy gnome-shell
gnome-shell:
Installed: (none)
Candidate: 42.9-0ubuntu2.2
Version table:
42.9-0ubuntu2.2 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://security.u
> What does `apt policy` show for these two packages?
See the bug description.
I found this StackExchange question:
https://askubuntu.com/questions/1477377/gnome-shell-broken-after-the-latest-update
which reports a similar error, but for an older upgrade a year ago.
--
You received this bug no
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2077232
Title:
Security update 42.9-0ubuntu2.2 uninsta
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.ne
Upgrade: gnome-shell-common:amd64 (42.9-0ubuntu2.1, 42.9-0ubuntu2.2)
Remove: gnome-shell:amd64 (42.9-0ubuntu2.1),
This shows only gnome-shell-common being installed and gnome-shell being
removed. What does `apt policy` show for these two packages?
--
You received this bug notification because
I'm running gnome-shell 42.9-0ubuntu2.2 right now and didn't encounter
any problems, so I wonder what's different...
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Critical
** Tags added: jammy regression-update
--
You received this bug notification because you are a member of
I could restore the old state by running
sudo apt install gnome-shell-common=42.9-0ubuntu2.1
sudo apt install gnome-shell ubuntu-desktop gdm3
gnome-shell-extension-desktop-icons-ng gnome-shell-extension-appindicator
chrome-gnome-shell ubuntu-session gnome-shell-extension-manager
gnome-sh
22 matches
Mail list logo
