After the recent gnome-shell updates, pop-upgrade stopped working.

[oguzkarayemis]

After the recent gnome-shell updates, pop-upgrade stopped working.

[leviport]

Interesting, I think the problem might be with pop-upgrade then. I'll transfer it to that repo.

[oguzkarayemis]

I did it! systemctl unmask pop-upgrade.service did the trick! But I don't have any slightest idea why the service masked at first...

[leviport]

I don't think that recovery thing is related to gnome-shell. They're pretty separate entities. Can you share the output from pop-upgrade recovery check?

[oguzkarayemis]

Here it is:

pop-upgrade recovery check
checking if pop-upgrade requires an update

[leviport]

Huh, there should be more after that. Does it just hang forever?

[oguzkarayemis]

No, no hangs, it just returns this and then exists.

[oguzkarayemis]

Additional note about other notes: I said,

Additionally after same gnome-shell updates, I'm experiencing system slow downs at the first 5-10 minutes after login into the desktop. I don't know this two issues are related though. If you want, I will add more detailed logs. Thanks.

Today I figured out this is not related to the gnome-shell, or other updates. It's the hidpi-deamon that I had activated after or just before the updates. I disabled that, and everything is just fine now.

[oguzkarayemis]

Issue persists. Is there any progress on your side?

[leviport]

I'm still unable to reproduce the behavior you're seeing. My recovery partition is upgrading as expected.

[oguzkarayemis]

Oh, that's not nice. What would you suggest me to look at or try?

[oguzkarayemis]

Ok I have some news. I could upgrade my recovery partition by starting pop-upgrade manually.

1. I became root in a terminal.
2. In this terminal window, I started pop-upgrade as a daemon with this command: /usr/bin/pop-upgrade daemon
3. After the daemon started, I opened a new terminal and updated the recovery partition with this command: pop-upgrade recovery upgrade from-release

I'm quite happy to upgrade my recovery partition. But what I don't understand is why I cannot use the usual way.

[leviport]

Interesting, it is definitely strange that it got masked. Glad you found the problem though.

[oguzkarayemis]

Yes, it is quite strange. Thanks for your help though, I'm closing this issue.

[HarlemSquirrel]

FYI just noticed this on my Lemur Pro and searching through my logs it looks like it got masked at least a few weeks ago.

╰─➤  journalctl  -g "The systemd unit 'pop-upgrade.service' is masked" 
-- Boot e5d91ae3526447c7ad2ac3cca7582683 --
Mar 27 08:57:36 orcrist dbus-broker-launch[1143]: Activation request for 'com.system76.PopUpgrade' failed: The systemd unit 'pop-upgrade.service' is masked.
-- Boot 5ffc74ec5c5c4eb999aab89f3245af3d --
Apr 03 09:22:54 orcrist dbus-broker-launch[1141]: Activation request for 'com.system76.PopUpgrade' failed: The systemd unit 'pop-upgrade.service' is masked.
-- Boot f7f050e448f24d8a801d8c3686be0512 --
Apr 17 08:28:04 orcrist dbus-broker-launch[1589]: Activation request for 'com.system76.PopUpgrade' failed: The systemd unit 'pop-upgrade.service' is masked.
-- Boot f2b162c111b64d84a0d81edb89c79848 --
Apr 20 15:10:42 orcrist dbus-broker-launch[1141]: Activation request for 'com.system76.PopUpgrade' failed: The systemd unit 'pop-upgrade.service' is masked.