KDE applications can not select anymore fstab or cifs mounted NTFS partions

Bug #1782880 reported by Harald
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I’m using dual boot systems with kubuntu and windows. The common data partitions are NTFS partitions. Most were mounted in fstab already during installation; like: /home/user/ntfspartion.

All kubuntu application like dolphin, digikam, kdenlive did recognize these partitions correctly as mounted in users home folder. Other, not fstab mounted NTFS partions, but mounted by cifs were correctly recognized by apps in /media/user/ntfspartion.

However since a few weeks kubuntu applications of ubuntu versions 16.04 and 18.04 do not know anymore NTFS mounting points!

Dolphin does not show anymore fstab mounted NFTS partitions in the personal folder, only in the places sidebar. Partitions mounted by cifs still displayed by dolphin in the sidebar but not in the directory /media/user/. While the XFCE file manager thunar still works as required.

Kubuntu applications like digikam or kdenlive can not select anymore fstab or cifs mounted NTFS partions, so KDE applications can not used anymore.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: a1 1714 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-10-05 (294 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 350V5C/351V5C/3540VC/3440VC
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=5ca944c9-9bd2-46f6-a7c1-bc4c7104239e ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-29-generic N/A
 linux-backports-modules-4.15.0-29-generic N/A
 linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-29-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-07-13 (13 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/04/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P10AAL
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP350V5C-S05DE
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: BOARD REVISION 00
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP10AAL:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/351V5C/3540VC/3440VC:pvrP10AAL.032.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-S05DE:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: Eureka
dmi.product.name: 350V5C/351V5C/3540VC/3440VC
dmi.product.version: P10AAL.032.CP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6

affects: linux-firmware (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1782880

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Harald (harald-voigt) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected bionic
description: updated
Revision history for this message
Harald (harald-voigt) wrote : CRDA.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote : IwConfig.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote : Lspci.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote : Lsusb.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote : ProcEnviron.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote : ProcModules.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote : PulseList.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote : RfKill.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote : UdevDb.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote : WifiSyslog.txt

apport information

Revision history for this message
Harald (harald-voigt) wrote :

Thanks for answer. Command apport-collect 1782880 has been executed successfully.
The problem seems not to be related to any kernel version. It looks like that it is a plasma issue only.
The reported problem pop up after an update some time ago, also on another computer that contains kubuntu 16.04.1, kubuntu 18.04 and windows 8.1.

If I execute KDE applications on running plasma desktop, they fail at selection NTFS mounted partions. If I execute the same KDE applications on ubuntu-desktop, they do as expected.
Means, on ubuntu-desktop, NTFS mounted partitions are displayed and can be selected, e.g. by digikam, while digikam running on plasma-desktop.

Test scenario:
original installed desktop: kubuntu-desktop
additional installed desktop: ubuntu-desktop

fstab:
# / was on /dev/sda5 during installation
UUID=5ca944c9-9bd2-46f6-a7c1-bc4c7104239e / ext4 errors=remount-ro 0 1
# /home/a1/Data was on /dev/sda2 during installation
UUID=02181F59181F4B55 /home/user/Data ntfs defaults,umask=007,gid=46 0 0

While the file open dialog of digikam on ubuntu-desktop knows the nTFS mounted partition “Data”, the file open dialog of digikam on kubuntu-desktop does not display partition “Data”. I included a picture of the digikam file open dialog about to select the picture folder.

Additional plasma bug: the application on kubuntu-desktop do not consider the change of language to english. Just the KDE Application Launcher menu changed the language from german to english.
In opposite, applications on ubuntu-desktop consider the new language setting to english.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Harald (harald-voigt) wrote :

After apt-get update on 18.04.1 the problem still existed.

Than, I performed a complete new installation of kubuntu 18.04.1 from CDROM on the same computer(s), empty home directory too. The issue disappeared on all computers?!

The fresh kubuntu 18.04.1 installation fixed the bag. No idea why.

Revision history for this message
Harald (harald-voigt) wrote :
Download full text (6.1 KiB)

Unfortunately after system update the bug appeared again!

Kubuntu applications hide mounted NTFS folders so that the the data can not be accessed by Kubuntu applications. GTK Applications do work as expected.

Test fstab:
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda8 during installation
UUID=ac1d18ac-8ad5-4565-997e-59c90bd00e71 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda2 during installation
UUID=C4DD-77E3 /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda7 during installation
UUID=21b47237-4d1b-4eac-8f72-a96e8d323c91 /home ext4 defaults 0 2
# --> mount instructions ignored and modified, see below mount -l
UUID=BA702B4E702B10A5 /home/a1/DatenAllg ntfs defaults,umask=007,gid=46 0 0
# --> mount instructions ignored and modified, see below mount -l
UUID=802A9A512A9A43D6 /home/a1/SSD-SYS ntfs defaults,umask=007,gid=46 0 0
# --> mount instructions ignored and modified, see below mount -l
#UUID=272007F45F29DEA2 /ntfs/Video ntfs rw,auto,gid=1000,uid=1000,nls=utf8 0 0
# swap was on /dev/sda6 during installation
UUID=8ad70c4f-10d1-4ce5-ab5b-828bfd4a2f56 none swap sw 0 0
# mount instructions correct taken
UUID=b8c34934-ab20-479a-9861-18fdd1211bf6 /home/a1/Video ext4 defaults 0 2

Lines starting with # - - > are mounted but can not seen and not accessed by kubuntu applications. The last fstab line, ext4, does a correct mounting.
It looks like that ntfs mount instructions are ignored and replaced by somewhat else.

~$ mount -l
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=16408676k,nr_inodes=4102169,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=3295220k,mode=755)
/dev/sda8 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.