Linked by Thom Holwerda on Tue 22nd Aug 2006 17:10 UTC, submitted by dhaneshr
Ubuntu, Kubuntu, Xubuntu Even though by now the bug is fixed, many people alerted us about the fact that updates to Xorg in Ubuntu broke X, leaving users with a command-line machine. If you happen to be one of the unhappy few, Ubuntu user tseliot provides the commands to fix your system. In the meantime, others are wondering how such a bug got past testing.
Thread beginning with comment 155079
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[10]: The Horror
by Jack Burton on Wed 23rd Aug 2006 08:02 UTC in reply to "RE[9]: The Horror"
Jack Burton
Member since:
2005-07-06

"The devs were on top of it pretty quickly and I'm very happy to hear that they acknowledged it. I think an official word to this site might not be a bad thing, along with a basic explaination of what happened and why it won't happen again. Being on top of a problem is good, being on top of a problem and everyone knowing it is better."

You fail to see the real problem: the borked update stayed up for many hours after the problem was acknowledged, possibly (and certainly) breaking many and many systems out there.

Reply Parent Score: 1

RE[11]: The Horror
by cptnapalm on Wed 23rd Aug 2006 16:14 in reply to "RE[10]: The Horror"
cptnapalm Member since:
2006-08-09

Apparently it took a VERY long time for everything to get sorted out.

Its one thing if Solitaire has problems, due to not being tested extensively.

Its is a whole different thing when X goes. I did read that the maintainer tested it on a few of his own systems, but, again, this is X. Almost everyone using Ubuntu depends on this package working.

"It works for me" doesn't really cut it on this one.

And they still haven't done anything to get some press out to let people know what happened, how it happened and how it will never happen again.

And now its on Linux.com too.

*sigh*

Reply Parent Score: 1