https://bugs.kde.org/show_bug.cgi?id=479013

cyberfe...@proton.me <cyberfe...@proton.me> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cyberfe...@proton.me

--- Comment #2 from cyberfe...@proton.me <cyberfe...@proton.me> ---
I found a solution for this in my case. Maybe just a quick fix and not
something to use for patching? Anyway, seems like if the daemon is started too
early in the boot process it will ask for permission. I followed instructions
from this Reddit comment:
https://www.reddit.com/r/kde/comments/12x3drp/comment/jhhweyl/?utm_source=share&utm_medium=mweb3x&utm_name=mweb3xcss&utm_term=1&utm_content=share_button

"You can get around it by disabling KDE Connect's autostart file (do cp
/etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop ~/.config/autostart in a
terminal and then edit the
~/.config/autostart/org.kde.kdeconnect.daemon.desktop file by adding
Hidden=true to it), if you have the KDE Connect plasmoid/applet set up it
should still start on boot anyway. Without rebooting/logging out you can just
kill the kdeconnectd process and then run kdeconnect-cli --refresh to start it
back up, and from then on it should just pop up a notification on remote input
instead of that permission prompt."

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to