Bug 483426 - Run Commands stopped working after updating the client
Summary: Run Commands stopped working after updating the client
Status: RESOLVED DUPLICATE of bug 479464
Alias: None
Product: kdeconnect
Classification: Applications
Component: windows-application (other bugs)
Version First Reported In: 24.02.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: brute4s99
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-13 10:33 UTC by blahblahbrian
Modified: 2024-04-15 22:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description blahblahbrian 2024-03-13 10:33:31 UTC 
SUMMARY
***
Run Commands stopped working after I updated the KDE Connect on my Windows to the current version. It had been working for years before today.
***

System Details: Desktop running Windows 11, KDE Connect version 24.02.0
Connect with Samsung Galaxy running Android 14.

STEPS TO REPRODUCE
1. Set up a run command on your windows desktop running KDE Connect version 24.02.0. The only remote command I had been using before it stopped working after the update is "rundll32.exe user32.dll,LockWorkStation"
2. Go to your mobile > Open KDE Connect
3. Click on Run Command > Click on the command you just set up.

OBSERVED RESULT
The command no longer works and windows desktop screen does not lock anymore. It used to work before the update.

EXPECTED RESULT
Locking the screen of Windows Desktop.

SOFTWARE/OS VERSIONS
Windows: 11
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1

ADDITIONAL INFORMATION
Comment 1 tremolo4 2024-04-15 22:13:14 UTC 
I was using the shutdown command on Windows: shutdown /t 30 /s
No longer works, since at least a month.

Using KDE Connect from Microsoft Store with the Android app from Play Store.
Comment 2 tremolo4 2024-04-15 22:20:40 UTC 

*** This bug has been marked as a duplicate of bug 479464 ***