LWN: Comments on "Announcing the Release Candidate for Ubuntu 6.10"

Announcing the Release Candidate for Ubuntu 6.10

beoba — Sat, 21 Oct 2006 02:02:17 +0000

I'm typing this from said RC. Except for a lack of jfsutils when I formatted / as jfs (leading to a lot of exciting errors when it tried to run fsck during bootup), the install has otherwise been fine.

Announcing the Release Candidate for Ubuntu 6.10

b7j0c — Fri, 20 Oct 2006 18:51:30 +0000

the slowness was just an observation, not the actual bug, which describes
how mutt (and sasl?) have problems accessing imaps hosts:

https://launchpad.net/bugs/65821

i did mark this as impacting mutt

i tried to indicate that the was against edgy BETA

i agree launchpad needs work, but i appreciate you answering me here

Announcing the Release Candidate for Ubuntu 6.10

bronson — Fri, 20 Oct 2006 16:56:41 +0000

Maybe I'm not understanding... How does slowness indicate a security issue? I could not find a bug resembling your description...?

http://launchpad.net/products/mutt/+bugs
https://launchpad.net/distros/ubuntu/+source/mutt/+bugs

(Launchpad is seriously difficult to use so I may not have been looking in the right place)

Mutt is in Ubuntu core so, I agree, I would expect someone to at least look at your report.

Announcing the Release Candidate for Ubuntu 6.10

b7j0c — Fri, 20 Oct 2006 16:38:24 +0000

i found the 6.10 BETA to be slow(er) and buggy in ways that dapper drake
did not exhibit. in particular, mutt imaps access exhibits bugs that dapper
did not and debian etch does not. while i posted a bug to launchpad
regarding this (and flagged it as a security issue, since a secure layer is
failing), no one has commented on it. now i don't want to be narcissistic
and presume the entire world must solve my problems, but no one has even
commented on this bug to tell me to get lost, and this is an app many linux
users use on a daily basis. i find this somewhat troubling, ubuntu seems to
be marching toward a release with some major issues still open.

No way to select install from the start menu :-(

madscientist — Fri, 20 Oct 2006 14:15:14 +0000

> Sorry, the bug I was mentioning is actually not that one.

That's why Ewan was not responding to your post, but rather to Jarto's post.

No way to select install from the start menu :-(

callegar — Fri, 20 Oct 2006 13:31:41 +0000

Sorry, the bug I was mentioning is actually not that one.

What I am referring to is a problem where parameters of the real time clock in some part of the chipset get corrupted to the point that it becomes impossible to boot _any_ operating system, so that the computer becomes completely useless (no way to activate _any_ operating system, it gives a bios error at start up.).

At this point, if you are lucky and the CMOS battery is accessible, you unplug that, you plug it again, the CMOS data is reset and your computer is alive again.

A slightly less lucky option is that you can send your computer to service and after 1 week you get it back alive again... (possibly paying for the service).

So, apparently it is a very critical thing, although I don't know the "statistical impact" of it.

No way to select install from the start menu :-(

ewan — Fri, 20 Oct 2006 12:36:32 +0000

The Release Candidate includes [...] alternate text-mode installation CDs

That would be those.

No way to select install from the start menu :-(

jarto — Fri, 20 Oct 2006 12:15:32 +0000

I reported this also in the Ubuntu forums:

I'm trying to install the release candidate of Edgy Eft on my 1 GHz/128MB test computer. Despite its low specs, it runs the previous version of Ubuntu pretty decently. I noticed that there's no possibility any more to choose installing without booting to the live cd. The problem is:

It's now 18 minutes since I started booting this computer with the live cd.

Can you please bring back a fast way of installing Ubuntu.

Announcing the Release Candidate for Ubuntu 6.10

callegar — Fri, 20 Oct 2006 09:57:19 +0000

Has anybody some info about how 6.10 poses with regard to the following problem?

------
https://launchpad.net/distros/ubuntu/+source/linux-source...

After installing dapper several people have reported their computers have failed to boot with the error 'real-time-clock stopped'
The error prevents the computer entering bios setup or booting from a cd so is fairly fatal.
------

I am on the edge of getting a DELL machine and the following scares me. I couldn't find out the consistency of this bug, neither if it is ubuntu dapper specific or not. Apparently it is DELL specific and regards many of the recent laptops. From what I managed to find out if you are lucky you have the CMOS battery accessible and removable, so you can resuscitate your machine by unplugging and replugging the battery. If you are unlucky the machine is dead and needs to be resuscitated at DELL.

Has anybody some recent information about it?... Maybe it is fixed but the fix received too little publicity.