Here are the answer to your commands systemctl status snapd.service ● snapd.service - Snap Daemon Loaded: loaded (/usr/lib/systemd/system/snapd.service; enabled; preset: en> Active: active (running) since Tue 2024-09-10 07:08:19 CEST; 1h 1min ago TriggeredBy: ● snapd.socket Main PID: 912 (snapd) Tasks: 15 (limit: 9186) Memory: 44.3M (peak: 48.0M) CPU: 994ms CGroup: /system.slice/snapd.service └─912 /usr/lib/snapd/snapd
sept. 10 07:08:19 portable snapd[912]: overlord.go:271: Acquiring state lock fi> sept. 10 07:08:19 portable snapd[912]: overlord.go:276: Acquired state lock file sept. 10 07:08:19 portable snapd[912]: daemon.go:247: started snapd/2.63.1+24.0> sept. 10 07:08:19 portable snapd[912]: daemon.go:340: adjusting startup timeout> sept. 10 07:08:19 portable snapd[912]: backends.go:58: AppArmor status: apparmo> sept. 10 07:08:19 portable systemd[1]: Started snapd.service - Snap Daemon. sept. 10 07:08:20 portable snapd[912]: udevmon.go:149: udev event error: Unable> sept. 10 07:08:20 portable snapd[912]: udevmon.go:149: udev event error: Unable> sept. 10 07:08:20 portable snapd[912]: udevmon.go:149: udev event error: Unable> sept. 10 07:13:19 portable snapd[912]: storehelpers.go:923: cannot refresh: sna> le-henaff@portable:~$ systemctl status snapd.apparmor.service ● snapd.apparmor.service - Load AppArmor profiles managed internally by snapd Loaded: loaded (/usr/lib/systemd/system/snapd.apparmor.service; enabled; p> Active: active (exited) since Tue 2024-09-10 07:08:19 CEST; 1h 2min ago Main PID: 739 (code=exited, status=0/SUCCESS) CPU: 318ms sept. 10 07:08:18 portable systemd[1]: Starting snapd.apparmor.service - Load A> sept. 10 07:08:19 portable snapd-apparmor[739]: main.go:124: Loading profiles [> sept. 10 07:08:19 portable systemd[1]: Finished snapd.apparmor.service - Load A> Regard Le 09/09/2024 à 14:18, Amin Bandali a écrit : > Thank you for your reply and explanation (and no worries, your English > is perfectly understandable!). I'm sorry to hear about the troubles, but > I'm glad to hear that at least a fresh installation worked. > > It would have been interesting to see if the main snapd service and > other related services were running okay in the environment > before/during upgrade, using commands like: > > systemctl status snapd.service > systemctl status snapd.apparmor.service > > And also have a look at their logs. But considering you likely no longer > have access to the environment (due to reinstalling) we can't find that > out. > > Since this seems like a possible snapd issue rather than a firefox one, > I'll reassign the bug accordingly. > > Thanks again. > > ** Package changed: firefox (Ubuntu) => snapd (Ubuntu) > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078413 Title: package firefox 1:1snap1-0ubuntu2 [modified: usr/bin/firefox usr/share/applications/firefox.desktop] failed to install/upgrade: le sous-processus nouveau firefox paquet pre-installation script a renvoyé un état de sortie d'erreur 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2078413/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
