Bug 510528

Summary: `pkcon update` asks for pass when there are no updates
Product: [Applications] Discover Reporter: Aaron Wolf <wolftune>
Component: PackageKitAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: minor CC: aleixpol, meven
Priority: NOR    
Version First Reported In: 6.4.5   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Aaron Wolf 2025-10-12 14:41:30 UTC 
SUMMARY

Running `pkcon update` when there *are* updates shows the updates and asks whether to go ahead. If user says yes, *then* it asks for pass appropriately. But if there are *no* updates, it jumps right to asking for pass for no reason in order to *then* show that there are no updates.

STEPS TO REPRODUCE
1. run `pkcon update`  again after already installing any updates

OBSERVED RESULT

asks for pass, shows there are no updates

EXPECTED RESULT

should show no updates and just stop without asking for a pass

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Comment 1 Méven 2025-10-12 17:39:12 UTC 
Checking for updates REQUIRES privilege access in the first place.
That or the bug affects packagekit (pkcon) which isn't a KDE project.

If you use `sudo pkcon update`, sudo retains a sort of root access for 10 minutes.
Comment 2 Aaron Wolf 2025-10-12 23:20:52 UTC 
(In reply to Méven from comment #1)
> Checking for updates REQUIRES privilege access in the first place.

That isn't the case. I can run the pkcon update command without sudo, and it checks for updates and reports *which* packages are to be updated prior to asking for a pass.

> That or the bug affects packagekit (pkcon) which isn't a KDE project.
> 

ah okay, I thought that was KDE because it was being encouraged in KDE Neon, and the "kc" letter order putting "k" first and primary (when "ck" is common generally) made me think it was a KDE thing.