Updating from Tumbleweed 20260331 to 20260415, zypper dup fails at accountsservice :(

error: lsetfilecon: (11 /usr/share/accountsservice, system_u:object_r:accountsd_share_t:s0) Invalid argument  
error: Plugin selinux: hook fsm_file_prepare failed  
error: unpacking of archive failed on file /usr/share/accountsservice: cpio: (error 0x2)  
error: accountsservice-23.13.9-11.3.x86_64: install failed  
error: accountsservice-23.13.9-11.2.x86_64: erase skipped  
(557/916) Installing: accountsservice-23.13.9-11.3.x86_64 ..................................................................................................[error]  
Installation of accountsservice-23.13.9-11.3.x86_64 failed:  
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.  
Abort, retry, ignore? [a/r/i] (a): a  
Warning: %posttrans and %transfiletrigger scripts are not executed when aborting!  

What should I do?

  • skyline2@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    4
    ·
    22 days ago
    1. Remember that a rolling distro is bleeding edge. That means that from time to time you WILL encounter some issues.
    2. Tumbleweed is (somewhat) unique in its approach to rolling. The quality checks that occur on openQA partially mitigate failures by withholding the next distro upgrades until they can be reviewed. However, the openSUSE devs are not perfect, openQA is not perfect, and some times rolling forward with a known issues is deemed acceptable.
    3. This is where btrfs comes in. The answer to your question of what to do if zypper dup fails is two part: A) roll back to the automatic “pre” snapshot taken by snapper before the dup. B) Just wait for the devs to fix the issue!
    4. If you are impatient, you can check for progress on a specific issue by searching the issue on https://bugzilla.opensuse.org/, or chat up the community either on the forums or on the matrix space in the support room.

    Feel free to ask questions anytime!