https://bugs.kde.org/show_bug.cgi?id=390453
--- Comment #3 from Syfer Polski <syfe...@gmail.com> --- (In reply to Julian Schraner from comment #2) > Please paste the contents of /etc/fstab so that we can further investigate > this crash. Thanks! On the 29th of March GHO(s...@iforma.net) emailed me about this bug, attaching his fstab. Since it doesn't contain any private information, I'm including it here. It supports the running theory that this problem only happens to people who don't have their UID and GID specified in the mount options. # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=a427a420-3799-41aa-8d0d-5655b7ef7860 / ext4 errors=remount-ro 0 1 # /DATA was on /dev/sdc6 during installation UUID=28813ACA21F76D42 /DATA ntfs defaults,umask=007,gid=46 0 0 # /home was on /dev/sdc3 during installation UUID=bdd16a4e-5e3a-4afe-9b80-166707be5b1d /home ext4 defaults 0 2 # swap was on /dev/sdc5 during installation UUID=15765e70-613f-498b-9b25-fed28d13b99e none swap sw 0 0 -- You are receiving this mail because: You are watching all bug changes.
