Description of problem: Unable to layer `solarr` on Silverblue 31 Version-Release number of selected component (if applicable): How reproducible: Install `solaar` via `rpm-ostree install solaar` Steps to Reproduce: 1. `rpm-ostree install solaar` Actual results: `error: Running %posttrans for solaar-udev: Executing bwrap(/bin/sh): Child process killed by signal 1; run `journalctl -t 'rpm-ostree(solaar-udev.posttrans)'` for more information` Expected results: Solaar is installed correctly Additional info: Output of `journalctl -t 'rpm-ostree(solaar-udev.posttrans)'` ``` Oct 23 12:26:50 rauros.figura.io rpm-ostree(solaar-udev.posttrans)[3380]: Failed to write 'add' to '/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-11/1-11.1/1-11.1:1.2/0003:046D:C52B.0006/0003:046D:101A.0008/hidraw/hidraw5/uevent': Read-only file system Oct 23 12:26:50 rauros.figura.io rpm-ostree(solaar-udev.posttrans)[3380]: Failed to write 'add' to '/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-11/1-11.1/1-11.1:1.2/0003:046D:C52B.0006/0003:046D:2010.0007/hidraw/hidraw4/uevent': Read-only file system Oct 23 12:26:50 rauros.figura.io rpm-ostree(solaar-udev.posttrans)[3380]: Failed to write 'add' to '/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-11/1-11.1/1-11.1:1.2/0003:046D:C52B.0006/hidraw/hidraw3/uevent': Read-only file system Oct 23 12:26:50 rauros.figura.io rpm-ostree(solaar-udev.posttrans)[3380]: Failed to write 'add' to '/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-8/1-8:1.0/0003:1B1C:1C05.0001/hidraw/hidraw0/uevent': Read-only file system ```
I think I'm hitting the same issue now that I've installed SB31. It worked fine in SB30. I've got a little more info: I _can_ install solaar, as long as I've disconnected the receiver before I try to install with rpm-ostree. That's not enough though, because Once it's installed, even though I can see my mouse in solaar (after rebooting and reconnecting the receiver), I can't change any settings for it, because of seemingly similar issues (can't write those changes). I also see issues if I now try an `rpm-ostree upgrade` with solaar installed and my receiver connected.
I'm not familiar with SilverBlue, but if you have suggestions on how to fix this in the current package (patch or PR welcome!), I'd be happy to review and apply.
(In reply to Dominik 'Rathann' Mierzejewski from comment #2) > I'm not familiar with SilverBlue, but if you have suggestions on how to fix > this in the current package (patch or PR welcome!), I'd be happy to review > and apply. Jonathan Lebon has updated the GitHub ticket and suggested to have a look at: https://src.fedoraproject.org/rpms/udisks2/pull-request/3 Perhaps you can use a similar solution? Thanks!
Thanks for the pointers. This should be easy to implement, then. You're welcome to open a PR. I don't expect having time to do this in the next few days.
(In reply to Dominik 'Rathann' Mierzejewski from comment #4) > Thanks for the pointers. This should be easy to implement, then. You're > welcome to open a PR. I don't expect having time to do this in the next few > days. Here you go. This is my first commit to a Fedora package. Hope I have not messed anything. I have built the packages and installed them on both Silverblue 31 and Fedora 30 Workstation without issues.
Apologies, forgot the link https://src.fedoraproject.org/rpms/solaar/pull-request/3
I totally missed this bug and PR. I'll apply this before F32 final freeze.
FEDORA-2020-672e031b5e has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-672e031b5e
FEDORA-2020-50adbb4b1f has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-50adbb4b1f
FEDORA-2020-60cb1985ff has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-60cb1985ff
FEDORA-2020-672e031b5e has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-672e031b5e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-672e031b5e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-50adbb4b1f has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-50adbb4b1f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-50adbb4b1f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-60cb1985ff has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-60cb1985ff` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-60cb1985ff See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-50adbb4b1f has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-672e031b5e has been pushed to the Fedora 30 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-60cb1985ff has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.