Hi; I'm on Ubuntu 10.10. Several weeks ago the Update Manager stopped functioning. When I go to click on the "Authentication" button, the dialog box will shake and then do nothing. Any ideas what the problem is and how I can fix it? Thanks. |
FYI, not to be lame, but 10.10 is a non-LTS version of Ubuntu and thus has a shorter lifecycle than the LTS version does (which also has better support)..... so why not put 12.04LTS on it in 7 days when it comes out on the 26th of April? 10.10 is EOL (End-of-Life), but aside from that, you could do the following: sudo dpkg-reconfigure update-manager && sudo apt-get update && sudo apt-get upgrade. I will try those commands when I get home, thanks. I've avoided upgrading after 10.10 because I read bad things about the versions that followed. I will eventually try 12.04LTS, but I've been burned in the past by upgrading the moment a new version of Ubuntu is released. I will wait and let other people work out bugs that slipped through testing.
(19 Apr '12, 10:57)
tinker123
I agree. Really, even upgrading from LTS to LTS (like 10.04 to 12.04) is a bad idea. (Getting updates are ok, but be wary of upGRADES.) Better off to reformat and install new.Using the non-LTS versions of Ubuntu are fine, if you don't need a stable system with longer support lifecycles.
(19 Apr '12, 17:24)
Ron ♦
Didn't work. I'll try 12.04 in about two weeks.
(19 Apr '12, 18:39)
tinker123
Ok. Please mark my answer as accepted.
(20 Apr '12, 10:22)
Ron ♦
|
Check out .xession-errors. If it shakes and does nothing, that sounds like maybe your username is no longer allowed to su. Can you access other control panels that authenticate? You can also do from the console "aptitude update" and "aptitude upgrade". I assume that works for ubuntu. I can login with my username via "sudo bash" just fine. Yes, I have fallen back to "aptitude upate", "aptitude upgrade" from the CLI as I haven't been able to find an answer to this issue.
(19 Apr '12, 10:55)
tinker123
Have you tried reinstalling or upgrading just update-manager? I remember having some problem with this a year or so ago with debian, I just can't remember how I fixed it. It might have been a group thing, or maybe just a bug and updating fixed it. What does .xsession-errors say?
(19 Apr '12, 21:48)
peterius
|