[frameworks-solid] [Bug 418906] UDI (Unique Device Identifier) provided by solid is not actually unique, entry gets overwritten

2020-04-01 Thread Méven Car
https://bugs.kde.org/show_bug.cgi?id=418906 Méven Car changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit|

[frameworks-solid] [Bug 418906] UDI (Unique Device Identifier) provided by solid is not actually unique, entry gets overwritten

2020-04-01 Thread Méven Car
https://bugs.kde.org/show_bug.cgi?id=418906 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #3 from Méven Car

[frameworks-solid] [Bug 418906] UDI (Unique Device Identifier) provided by solid is not actually unique, entry gets overwritten

2020-03-15 Thread Bernard Gray
https://bugs.kde.org/show_bug.cgi?id=418906 --- Comment #2 from Bernard Gray --- Further clarification: When mounting the network share, use `sudo mount.cifs` (not the KDE userspace way). In my specific use case, users mount network shares using mount.cifs called by the pam_mount module at

[frameworks-solid] [Bug 418906] UDI (Unique Device Identifier) provided by solid is not actually unique, entry gets overwritten

2020-03-15 Thread Bernard Gray
https://bugs.kde.org/show_bug.cgi?id=418906 --- Comment #1 from Bernard Gray --- To extend ADDITIONAL INFORMATION section: ...making the shortcut inaccessible to user1 via the Devices panel list. Note that user1 still *sees* the share/Device listed (which is expected), but clicking on it