https://bugs.kde.org/show_bug.cgi?id=383004
Aleix Pol changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=383004
--- Comment #5 from Fabian Vogt ---
(In reply to Albert Vaca from comment #4)
> Why the heck is Bluetooth enabled is Suse packages?
Only in the KDE:Unstable:Extra repositories for testing - which is a good thing
as otherwise this bug wouldn't have been
https://bugs.kde.org/show_bug.cgi?id=383004
--- Comment #4 from Albert Vaca ---
Why the heck is Bluetooth enabled is Suse packages?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383004
--- Comment #3 from Fabian Vogt ---
(In reply to Albert Vaca from comment #2)
> If kdeconnect is already running, launching kdeconnectd again should just
> exit immediately. I'm not sure why this is not happening. Can you check if,
> while your desktop
https://bugs.kde.org/show_bug.cgi?id=383004
--- Comment #2 from Albert Vaca ---
If kdeconnect is already running, launching kdeconnectd again should just exit
immediately. I'm not sure why this is not happening. Can you check if, while
your desktop is already up, running kdeconnectd by hand also
https://bugs.kde.org/show_bug.cgi?id=383004
--- Comment #1 from Fabian Vogt ---
I debugged a bit further and found the issue.
Both /etc/xdg/autostart/kdeconnect.desktop org.kde.plasmashell.desktop are
autostart phase 0, so they might be started in either order. If plasmashell is
started first, i
https://bugs.kde.org/show_bug.cgi?id=383004
kishor...@gmail.com changed:
What|Removed |Added
CC||kishor...@gmail.com
--
You are receiving
