[Bug 1074657] Re: "Authorization failed" when trying to edit anything

2012-12-05 Thread Jacob Winski
This looks to be caused by improper session launch. How to reproduce this problem: 1) open a terminal and check what your DISPLAY variable is set at and write it down: echo $DISPLAY NOTICE: I assume your DISPLAY variable is set to :0 If not, please use the variable that you wrote down instead 2)

[Bug 1074657] Re: "Authorization failed" when trying to edit anything

2012-12-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074657

[Bug 1074657] Re: "Authorization failed" when trying to edit anything

2012-12-05 Thread Jacob Winski
I also have this problem. Steps to reproduce: 1) Open software sources (as regular user) 2) Goto "Other Software" tab 3) Remove entry Result: Authorization failed. Software sources can't be changed without permission. When running Software Sources with massive debug I get no debug error: software

[Bug 1074657] Re: "Authorization failed" when trying to edit anything

2012-11-16 Thread James
Just to be clear, you need to run sudo update-manager It seems like ubuntu is littered with these bugs of not prompting for privilege elevation and when a novice user (like me) needs to 'run it through sudo' it's nice to know what program you need to run (since, after all, the cli executable is n

[Bug 1074657] Re: "Authorization failed" when trying to edit anything

2012-11-04 Thread Marius Kotsbak
That is correct. A workaround is to run it through sudo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1074657 Title: "Authorization failed" when trying to edit anything To manage notifications abo

[Bug 1074657] Re: "Authorization failed" when trying to edit anything

2012-11-04 Thread Edward Donovan
This doesn't help you much, but - I think this problem isn't really related to bug 1058072. The point of that bug is, that if you hit cancel, an error message is unnecessary. The code is working fine; it's a design issue. In this case, you're not hitting cancel, but getting a genuine, unexplain