startupmanager doesnt use policykit

Hi,

This is not something that can be fixed in policykit, so I have
invalidated that part of the task.

This is a valid wishlist bug in startupmanager I think.

If you would like to see this fixed then it is probably
best to approach the upstream developer of the software
and request the feature.

Thanks,

James

This should be forwarded upstream

Thanks James. Should all bugs of any apps on Ubuntu that are related to not using PolicyKit be filled separately?

Emilio, do I need to do any thing more, or since you added the upstream team, I should just wait for this to be fixed?

BUGabundo wrote:
> Emilio, do I need to do any thing more, or since you added the upstream
> team, I should just wait for this to be fixed?

That's enough, I didn't realize in the beginning that upstream uses Launchpad

should a bug be filled to update the maintainer contact of it?

BUGabundo wrote:
> should a bug be filled to update the maintainer contact of it?

What do you mean?

Hi,

Using policykit in an application requires changes to the application,
rather than to policykit, so it requires a separate bug against each
application that you wish to use it.

Thanks,

James

On Mon, Jun 9, 2008 at 6:58 PM, Emilio Pozuelo Monfort wrote:
> What do you mean?

On the side it says:
"startupmanager" source package in ubuntu
Latest release: 1.9.11-1
Uploaded By: Ubuntu Archive Auto-Sync
Maintainer: Python Applications Packaging Team

But since upstream is already on LP, shouldnt they be the Maintainers?

--
BUGabundo :o)
(``-_-´´)
Linux user #443786 GPG key 1024D/00967685
The body of this email is licensed under a Creative Commons
Attribution-Noncommercial-Share Alike 3.0
http://BUGabundo.net

BUGabundo wrote:
> On Mon, Jun 9, 2008 at 6:58 PM, Emilio Pozuelo Monfort wrote:
>> What do you mean?
>
> On the side it says:
> "startupmanager" source package in ubuntu
> Latest release: 1.9.11-1
> Uploaded By: Ubuntu Archive Auto-Sync
> Maintainer: Python Applications Packaging Team
>
> But since upstream is already on LP, shouldnt they be the Maintainers?
>

No, that's the Debian maintainer, which is a different thing.

Now, this depends on if anyone can show me how to implement this....
Tried looking at other apps to see how it is done, but it got too messy.

If I understand how PolicyKit works, it would be pointless to try to use it without having DBus interfaces for GRUB configuration first. PolicyKit can only only automatically escalate privileges for accessing methods on a DBus interface, not for the running process. I think the way it is in the repository right now (trying to call gksu, &c) is the correct way to handle the problem.

This package has been removed from Ubuntu. Closing all related bugs.