https://bugs.kde.org/show_bug.cgi?id=429191
--- Comment #17 from Andrius Štikonas <andr...@stikonas.eu> --- (In reply to Rik from comment #15) > I'm sorry perhaps I am a bit dim but I'm confused by the information > presented here. > > If I enter p=in a console window: > $ partitionmanager -v > I get the response... > partitionmanager 4.2.0 > > Is this version supplied with FC33 KDE spin a prehistoric one? > > B.t.w. I have no # characters, except the ones at the start of the comment > lines in my fstab. I do not have sshfs entries, nor mhddfs. > > I added the last line myself and have tested the result, before, with > partitionmanager without problems. > > But now it does crash on me, My report was marked as duplicate of bug 429191 > but I have difficulty to see the similarities and don't see how the 429191 > resolution can be applied for my application. > > My fstab: > > # > # /etc/fstab > # Created by anaconda on Fri Feb 19 16:44:13 2021 > # > # Accessible filesystems, by reference, are maintained under '/dev/disk/'. > # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info. > # > # After editing this file, run 'systemctl daemon-reload' to update systemd > # units generated from this file. > # > UUID=0e0895f8-822c-4e21-a311-d33c46842e59 / btrfs > subvol=root00 0 0 > UUID=52c60c51-fe54-4d90-b6d6-13e5eb7e429b /boot ext4 > defaults 1 2 > UUID=0e0895f8-822c-4e21-a311-d33c46842e59 /home btrfs > subvol=home00 0 0 > UUID=eccfb380-faf0-4b3c-a700-6c299e5f1da6 /home/Gedeeld btrfs As a workaround add defaults for the last entry in 4th field. It's the same bug though (out of bounds array access), although triggered by slightly different cause. -- You are receiving this mail because: You are watching all bug changes.
