Bug#961551: partitionmanager: Does not start - "Session bus not found"

[scott092707@aol.com]

I am curious about something...

I thought the rationale of using PolicyKit over sudo was, that with sudo, the entire time an app was running,
it was with administrative rights, thus there was a longer time for someone to try and take over in some way...
Whereas with PolicyKit, it would only enter administrative mode when administrative rights were necessary,
and run in user mode the rest of the time.

In this case, I would have expected partitionmanager to run in user mode while looking at the disk(s), and
setting up what changes he/she wished to make, and only enter administrative mode when "Apply" was hit.
Only when Apply had been hit would the PolicyKit step in and require the password (and presumably remember
it if further administrative rights were needed later).
Yet, the password is required immediately upon invoking the app, before any disks were sought and their 
contents displayed.

Is this not almost like using sudo to run it (except that sudo cannot be used, as I found out...)?
It would appear that PM runs under administrative rights from the beginning.