Ubuntu 6.10 login problem
Thanks for the advice I tried alt control F1 which gave me a command line - and allowed me to log in to a console, however, as I was typing the commands, it then automatically went back to the graphical interface. I then loggin in using the recovery mode which allowed me to run the sudo aptitude update sudo aptitude dist-upgrade this seemed to run until it listed a syntax error with "freemed" which might be an application I tried to install in the past - it then exited back to the command line. When I rebooted, it gave me the same screen - however, it tried to go past it, the screen would flash blank then white and then back to the cream blank screen. Eventually it popped up a box with: "The greeter application appears to be crashing - attempting to use a different one" After I clicked OK, the same thing happened - eventually sticking on the blank cream screen again. Any ideas?
John Torrance wrote:
Thanks for the advice
I tried alt control F1 which gave me a command line - and allowed me to log in to a console, however, as I was typing the commands, it then automatically went back to the graphical interface. I then loggin in using the recovery mode which allowed me to run the sudo aptitude update sudo aptitude dist-upgrade
this seemed to run until it listed a syntax error with "freemed" which might be an application I tried to install in the past - it then exited back to the command line.
Get back to this point, then run sudo aptitude remove freemed Then run the dist-upgrade again.
One also assumes you knew this: I have posted some data here as I missed the issue, of course as the mirrors are fixed a dist upgrade should also fix it, Good luck. at least the system is there, it looks like its just the X server that's been messed up. ----------------------------------------------------------------------- Ubuntu 6.06 LTS users who installed updates between 17:30 UTC on Monday, Aug. 21 and 10:00 UTC on Tuesday, Aug. 22 were the ones affected by this problem. A note to users on Ubuntu's _web site_ <http://www.ubuntu.com/UpgradeIssue> said "An update to the windowing system in Ubuntu was incorrectly released for Ubuntu 6.06 LTS. When applied to Ubuntu 6.06, the patch inadvertently breaks the desktop windowing environment on some systems." It went on, "When we learned of the problem, the patch was immediately withdrawn. Mirrors have also been disabled to ensure that the faulty patch isn't available from them. We have launched an investigation and formal quality process review to understand exactly how this happened and what corrective actions to take." While users could reach a command line interface, many new Ubuntu users were still confused as to what to do about the problem. The solution was to login from the command line. Then, the user must do a: |sudo apt-get update| followed by |sudo apt-get install xserver-xorg-core| In most Debian/Linux distributions, this would be done by logging in as the root user, but Ubuntu discourages the use of root, so the more cumbersome, but also more secure, sudo method must be used instead. You then hold down Control and Alt, and then press Delete, to reboot the xServer into a functional condition. The problem with the "bad" patch was that it was an experimental patch, which wasn't ready for release to the general public. Full details are on the ubuntu website at either : http://www.ubuntu.com/UpgradeIssue http://www.ubuntu.com/FixForUpgradeIssue -------------------------------------------- Daniel Lawson wrote:
John Torrance wrote:
Thanks for the advice
I tried alt control F1 which gave me a command line - and allowed me to log in to a console, however, as I was typing the commands, it then automatically went back to the graphical interface. I then loggin in using the recovery mode which allowed me to run the sudo aptitude update sudo aptitude dist-upgrade
this seemed to run until it listed a syntax error with "freemed" which might be an application I tried to install in the past - it then exited back to the command line.
Get back to this point, then run
sudo aptitude remove freemed
Then run the dist-upgrade again.
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
One also assumes you knew this: I have posted some data here as I missed the issue, of course as the mirrors are fixed a dist upgrade should also fix it,
Good luck. at least the system is there, it looks like its just the X server that's been messed up.
-----------------------------------------------------------------------
Ubuntu 6.06 LTS users who installed updates between 17:30 UTC on Monday, Aug. 21 and 10:00 UTC on Tuesday, Aug. 22 were the ones affected by this problem.
August was a long time ago. I doubt this is the problem :)
On 3/11/2006, at 10:01 PM, Daniel Lawson wrote:
One also assumes you knew this: I have posted some data here as I missed the issue, of course as the mirrors are fixed a dist upgrade should also fix it,
Good luck. at least the system is there, it looks like its just the X server that's been messed up.
---------------------------------------------------------------------- -
Ubuntu 6.06 LTS users who installed updates between 17:30 UTC on Monday, Aug. 21 and 10:00 UTC on Tuesday, Aug. 22 were the ones affected by this problem.
August was a long time ago. I doubt this is the problem :)
Whilst I would like to agree, a lot of copies were floating around. well into late september. We saw users affected with this as late as the 22nd of September .. so its still possible, I think some shipped CD's were also affected. As I said, I came in late .. Ihug have been/might still be having some mail issues lately His problem seemed related, and rather than a full dist upgrade, just replacing X is faster and if it gets the system back .... Well it's worth a crack eh ?
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
On Sat, Nov 04, 2006 at 08:26:39AM +1300, Gavin Denby wrote:
Ubuntu 6.06 LTS users who installed updates between 17:30 UTC on Monday, Aug. 21 and 10:00 UTC on Tuesday, Aug. 22 were the ones affected by this problem.
His problem seemed related, and rather than a full dist upgrade, just replacing X is faster and if it gets the system back ....
This bad patch was only in ubuntu 6.06? But John has already upgraded to 6.10 (according to the subject) and is still having some X-related problem, so I'm guessing he's got a different problem which isn't so easy to fix... John
And this is why we slackware users stay out of these help discussions. It also reminds me why I have my /home directories on a different partition so I can do clean installs if an upgrade fails without loosing anything important. I did say ... assuming you had already tried this, as I was suggesting trying a more limited upgrade rather than a full dist upgrade given that there were issues causing the apt-get to crash. It just seemed like a good thing to try ... Anyway, I'll go back to lurk mode now, and leave this to the Ubuntu/Debian crowd to sort out. I'll play with my new slackware laptop Slackware and Freespire disks some more instead. anyway - All the best with getting it sorted. Later John R. McPherson wrote:
His problem seemed related, and rather than a full dist upgrade, just replacing X is faster and if it gets the system back ....
This bad patch was only in ubuntu 6.06? But John has already upgraded to 6.10 (according to the subject) and is still having some X-related problem, so I'm guessing he's got a different problem which isn't so easy to fix...
John
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
participants (4)
-
Daniel Lawson -
Gavin Denby -
John R. McPherson -
John Torrance