Bug 401501

Summary: "Ambiguous Shortcuts" reported when dolphin launches upon automount of usb thumb drive
Product: [Applications] dolphin Reporter: James Holt <holt_james>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: minor CC: elvis.angelaccio, nate
Priority: NOR    
Version: 18.08.1   
Target Milestone: ---   
Platform: Other   
OS: FreeBSD   
Latest Commit: Version Fixed In:

Description James Holt 2018-11-28 12:33:27 UTC
SUMMARY
"Ambiguous Shortcuts" reported when dolphin launches upon automount of usb thumb drive

STEPS TO REPRODUCE
1. On FreeBSD 11.2-RELEASE-p4 using "pkg install xorg kde5 sddm automount"
2. /etc/rc.conf has: dbus_enable="YES" hald_enable="NO" sddm_enable="YES" autofs_enable="NO"
3. /usr/local/etc/automount.conf configured to launch dolphin for non-root user as per vermaden's recommendations at https://github.com/vermaden/automount/blob/master/README

OBSERVED RESULT
Before automatically opening itself after a USB drive insertion, dolphin reports as follows in a popup window:

"There are two actions (New Tab, New Tab) that want to use the same shortcut (Ctrl+T). This is most probably a bug. Please report it in bugs.kde.org"

EXPECTED RESULT
No popup. This popup only occurs when automounting. It does not occur when dolphin launches normally from an icon click, menu selection, or command line.

SOFTWARE/OS VERSIONS
Windows: No
MacOS: No
Linux/KDE Plasma: No
(available in About System)
KDE Plasma Version: 5.12.5.18.08.1 from x11/kde5 port on FreeBSD 11.2-RELEASE-p4
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION
OS type: 32 bit

It's apparent that KDE/Plasma/qt5 and dolphin still contain a few dependencies on the HAL hardware abstraction layer, although not so many as in kde 4. I'm trying to wean myself away from HAL dependencies, and it's my understanding that you are also trying to wean yourselves off of it. Thus I'm running KDE without enabling HAL, and making do as well as I can with devd and vermaden's automount.conf configuration as documented at https://github.com/vermaden/automount/blob/master/README which for me has been a better workaround than using autofs_enable="YES" with the FreeBSD-recommended /etc/auto_master /media configuration. Also, I've noticed that FreeBSD's man pages for automount, autofs, and auto_master do not mention automount.conf or vermaden's alternative solution. It's quite possible that they're unaware of it, but I simply don't know.

This minor error doesn't occur when HAL is enabled to detect devices and automount usb drives. I can live with this minor error for the time being, and am happy to report it to you as per your request in the popup window. Good luck, be well, and thanks for everything.
Comment 1 Nate Graham 2018-11-28 20:20:51 UTC
Already fixed in 18.12.3 (or if not that, in the next release; can't quite remember but I know this was fixed).
Comment 2 Christoph Feck 2018-11-28 21:22:46 UTC

*** This bug has been marked as a duplicate of bug 398324 ***
Comment 3 James Holt 2018-11-28 21:46:47 UTC
Nice. Thanks.(In reply to Christoph Feck from comment #2)
> 
> *** This bug has been marked as a duplicate of bug 398324 ***