I got this crash, again, when software sources asked for my password, and I hit ESC. I haven't had a chance to look at the code (and don't know if I could figure anything out). That said... The error says:
In my case, is the code presuming the authorization dialog resulted in a successful authorization? Perhaps it's lacking a check for whether it really got permission, or at least how the dialog exited.
Beyond that, should 'permission denied' cause a crash? That seems like a case we ought to be able to cover. Maybe it's not exactly a crash, in my case: the software-properties-gtk window was still there, and still responsive, I believe. But some internals crashed enough to start apport up. 'Permission denied' does seems like something we should report to the user, perhaps in a dialog, and not have to throw an exception for.
Maybe I can get time to look at the code. Whether I might get anywhere is a crapshoot.
Thanks.
I got this crash, again, when software sources asked for my password, and I hit ESC. I haven't had a chance to look at the code (and don't know if I could figure anything out). That said... The error says:
PermissionDen iedByPolicy: com.ubuntu. softwarepropert ies.applychange s
In my case, is the code presuming the authorization dialog resulted in a successful authorization? Perhaps it's lacking a check for whether it really got permission, or at least how the dialog exited.
Beyond that, should 'permission denied' cause a crash? That seems like a case we ought to be able to cover. Maybe it's not exactly a crash, in my case: the software- properties- gtk window was still there, and still responsive, I believe. But some internals crashed enough to start apport up. 'Permission denied' does seems like something we should report to the user, perhaps in a dialog, and not have to throw an exception for.
Maybe I can get time to look at the code. Whether I might get anywhere is a crapshoot.
Thanks.