Bug 424875 - Dolphin ignoring fstab "x-gvfs-name" since update
Summary: Dolphin ignoring fstab "x-gvfs-name" since update
Status: RESOLVED FIXED
Alias: None
Product: frameworks-solid
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.72.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Lukáš Tinkl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-31 18:09 UTC by David R
Modified: 2020-08-17 17:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot to illustrate the issue (95.68 KB, image/png)
2020-07-31 18:09 UTC, David R
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David R 2020-07-31 18:09:56 UTC
Created attachment 130541 [details]
Screenshot to illustrate the issue

Hello,

I didn't notice exactly when it happened but Dolphin does not display anymore the "x-gvfs-name" from fstab since a recent update.
See attachment screenshot.

After some research, I think this is handled by solid.

I found the code of file "src/solid/devices/backends/fstab/fstabdevice.cpp" on github https://github.com/KDE/solid/commit/cdbfb3e799c72742163ecf6a6bdf073aeed874c3

It was modified 2 months ago and the part managing GVFS was modified :

    for  (const QString &option : gvfsOptions) {
        if (option.startsWith(QLatin1String("x-gvfs-name="))) {
            QStringRef encoded = option.midRef(12);
    -       m_description = QUrl::fromPercentEncoding(encoded.toLatin1());
    +       m_displayName = QUrl::fromPercentEncoding(encoded.toLatin1());
        } else if (option.startsWith(QLatin1String("x-gvfs-icon="))) {
            QStringRef encoded = option.midRef(12);
            m_iconName = QUrl::fromPercentEncoding(encoded.toLatin1());
        }
    }

Can you please fix the issue, it's really not nice for NFS share in Dolphin.

Regards,

David

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.72.0
Qt Version: 5.15.0
Comment 1 David R 2020-08-17 17:43:08 UTC
Has been fixed with a recent update