Cannot update akonadi & kwin6-x11 from latest slowroll update

When trying to update the packages of akonadi and kwin6-x11 through Myrlyn, I get these errors:

Subprocess failed. Error: RPM failed: Command exited with status 1.
History:
 - error: unpacking of archive failed on file /usr/share/kf6/akonadi_knut_resource: cpio: lstat failed - Directory not empty
   error: akonadi-25.12.1-1.1.x86_64: install failed
   error: akonadi-25.12.0-1.1.x86_64: erase skipped
Subprocess failed. Error: RPM failed: Command exited with status 1.
History:
 - error: unpacking of archive failed on file /usr/lib64/qt6/plugins/kwin-x11: cpio: lstat failed - No data available
   error: kwin6-x11-6.5.5-1.1.x86_64: install failed
   error: kwin6-x11-6.5.4-1.1.x86_64: erase skipped

All my other packages have managed to update, so I was wondering how I can get these to successfully update too.

Try
sudo rpm --rebuilddb

The command did not seem to work

sudo rpm --rebuilddb
[sudo] password for root: 
sudo zypper dup
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...

The following 2 packages are going to be upgraded:
  akonadi kwin6-x11

The following 5 packages are going to be downgraded:
  dbus-1 dbus-1-common dbus-1-tools libdbus-1-3 libdbus-1-3-32bit

The following package is going to be REMOVED:
  libgps31

2 packages to upgrade, 5 to downgrade, 1 to remove.

Package download size:
            |       6.4 MiB  overall package size
       0 B  |  -    6.4 MiB  already in cache

Package install size change:
              |      15.6 MiB  required by packages that will be installed
  -230.8 KiB  |  -   15.8 MiB  released by packages that will be removed

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y
In cache akonadi-25.12.1-1.1.x86_64.rpm                                                                          (1/7),   1.4 MiB    
In cache kwin6-x11-6.5.5-1.1.x86_64.rpm                                                                          (2/7),   4.5 MiB    
In cache dbus-1-common-1.14.10-5.1.noarch.rpm                                                                    (3/7),  29.0 KiB    
In cache libdbus-1-3-32bit-1.14.10-5.1.x86_64.rpm                                                                (4/7), 164.5 KiB    
In cache libdbus-1-3-1.14.10-5.1.x86_64.rpm                                                                      (5/7), 151.8 KiB    
In cache dbus-1-tools-1.14.10-5.1.x86_64.rpm                                                                     (6/7),  51.3 KiB    
In cache dbus-1-1.14.10-5.1.x86_64.rpm                                                                           (7/7),  85.7 KiB    

Checking for file conflicts: ..................................................................................................[done]
error: unpacking of archive failed on file /usr/share/kf6/akonadi_knut_resource: cpio: lstat failed - Directory not empty
error: akonadi-25.12.1-1.1.x86_64: install failed
error: akonadi-25.12.0-1.1.x86_64: erase skipped
(1/8) Installing: akonadi-25.12.1-1.1.x86_64 .................................................................................[error]
Installation of akonadi-25.12.1-1.1.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a): r
error: unpacking of archive failed on file /usr/share/kf6/akonadi_knut_resource: cpio: lstat failed - Directory not empty
error: akonadi-25.12.1-1.1.x86_64: install failed
error: akonadi-25.12.0-1.1.x86_64: erase skipped
(1/8) Installing: akonadi-25.12.1-1.1.x86_64 .................................................................................[error]
Installation of akonadi-25.12.1-1.1.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a): a
Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.

I’ve never seen this type of error message.

In the past, I’ve seen errors when a symlink couldn’t replace an existing directory of the same name or the other way round; that happens in rare cases. But this looks like corrupted archives. Did you check if you maybe ran out of disk space in the libzypp download / cache directory? That might explain it.

BTW I downloaded both akonadi RPMs manually and unpacked them with unrpm - no problem. Also with unpacking the older one first and then the newer one over the older one - no problem.

Do you know where I can find said libzypp download / cache directory? If I do find it, do I just delete what is there?

Check /var/cache/zypp/packages. Or /var in general.

I forgot to mention: If you are using Btrfs, see here why it might tell you misleading numbers.

A tool that might help you:

HTH

Try:
sudo zypper clean -a
sudo zypper dup

Unfortunately the commands did not work.

I think this helped. Earlier you mentioned…

And it does seem like that is the case, at least to my knowledge, its currently being filled up by the kwin6-x11 rpm file

But this is just 4.5 MB; nothing to worry about under normal circumstances.
That “100%” means just 100% of that directory level. In your case, if there is nothing else in that subtree, it might also mean 100% of the subtree (/var/cache/zypp/packages). But that doesn’t mean it’s 100% of that whole filesystem outside of this subtree.

Do you have /var on a separate filesystem?

What does df -hT / /var say?

And Ctrl+M (“View” → “Filesystems”) in QDirStat? This tries to eliminate pseudo filesystems and Btrfs subvolumes, so it gives a better impression about your real filesystems.

Ah I see, thank you for teaching me that

I believe I should only have btrfs unless the filesystem windows uses still exists after I overwritten it with my Linux install. I am not completely sure if I understood your question, but I think what I have below should give you more information.

Filesystem          Type   Size  Used Avail Use% Mounted on
/dev/mapper/cr_root btrfs  932G  599G  327G  65% /
/dev/mapper/cr_root btrfs  932G  599G  327G  65% /var

OK, so you don’t have /var on a separate filesystem, it’s on the / Btrfs, and in that case it’s almost certainly a (no-copy-on-write) subvolume.

But this is also when my Btrfs document comes into play: You will need the special Btrfs commands:

  • sudo btrfs fi usage /
  • sudo btrfs fi df /
  • sudo btrfs balance

First of all, you should check with snapper what Btrfs snapshots are consuming disk space. You should already have a strategy in place for cleaning them up, but you may want to check anyway.

Chances are that your root Btrfs has filled up with snapshots, so just btrfs balance may not be able to reclaim much disk space.

But this is when I invite Btrfs expert to join in how exactly to proceed here.

Got around to doing this, and here are my results. First, using all the btrfs commands…

sudo btrfs fi usage /var
Overall:
    Device size:                 931.39GiB
    Device allocated:            631.07GiB
    Device unallocated:          300.32GiB
    Device missing:                  0.00B
    Device slack:                    0.00B
    Used:                        596.37GiB
    Free (estimated):            328.72GiB      (min: 178.57GiB)
    Free (statfs, df):           328.72GiB
    Data ratio:                       1.00
    Metadata ratio:                   2.00
    Global reserve:              512.00MiB      (used: 0.00B)
    Multiple profiles:                  no

Data,single: Size:611.01GiB, Used:582.60GiB (95.35%)
   /dev/mapper/cr_root   611.01GiB

Metadata,DUP: Size:10.00GiB, Used:6.88GiB (68.83%)
   /dev/mapper/cr_root    20.00GiB

System,DUP: Size:32.00MiB, Used:96.00KiB (0.29%)
   /dev/mapper/cr_root    64.00MiB

Unallocated:
   /dev/mapper/cr_root   300.32GiB
sudo btrfs fi df /var
Data, single: total=611.01GiB, used=582.60GiB
System, DUP: total=32.00MiB, used=96.00KiB
Metadata, DUP: total=10.00GiB, used=6.88GiB
GlobalReserve, single: total=512.00MiB, used=0.00B

Now before I did btfs balance I did look at my snapshots, and deleted two months old ones. I never had a strategy in place to routinely clean up snapshots, mostly because I never thought that would be a worry. However now everything is read only, seemingly from doing that :frowning:. I did do btrfs balance after, but it errored saying the folder (/var) was read only.