Comment 22 for bug 433851

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

The reason it's marked as NEW in software center is because this issue has been identified as being caused (or at least solvable) in the policykit package - as far as the software-center package goes it is currently unsure or not researched whether this can be solved there. The status of this bug in software-center has changed several times. You can see a full log of changes by clicking the link 'See full activity log' at the bottom of the comments list.

Also I notice that this is only marked as affecting 8 people - please remember to add yourself if you're affected by this. It helps developers prioritize their time.