https://bugzilla.suse.com/show_bug.cgi?id=1193706 Bug ID: 1193706 Summary: pkcon reporting a (spurious?) read-only fs error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: dfaggioli@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Hey! So, since some users were complaining about pkcon throwing errors on MicroOS, I decided to try myself (I just installed snapshot 20211211). It is, in fact, the case that the following shows up: dario@localhost:~> pkcon install rclone Fatal error: Failed to create directory "/.snapshots/4/snapshot/etc/dnf/modules.d": 30 - Read-only file system However, if I try again, it seems the package was installed inside of the snapshot: dario@localhost:~> pkcon -v install rclone 22:33:59 PackageKit Verbose debugging enabled (on console 1) 22:34:00 PackageKit role now resolve PackageKit adding state 0x559f4fd43be0 PackageKit notify::connected PackageKit remove state 0x559f4fd43be0 Fatal error: rclone-1.57.0-1.1.x86_64 is already installed And if I reboot, rclone is there: dario@localhost:~> rclone -h Rclone syncs files to and from cloud storage providers as well as mounting them, listing them in lots of different ways. See the home page (https://rclone.org/) for installation, usage, documentation, changelog and configuration walkthroughs. Usage: rclone [flags] rclone [command] ... ... ... So, is that "Fatal error" just some spurious message we should suppress? Or has something really gone bad, despite the package ending up being installed (from what I can tell) correctly? Neal, any idea? -- You are receiving this mail because: You are the assignee for the bug.