22 Mar
2012
22 Mar
'12
12:16 p.m.
On Wednesday 21 March 2012 19:58:40 Werner Joss wrote:
On Wednesday 21 March 2012 20:50:03 Dan Youngquist
wrote:
I very strongly agree with Dan about this.
I wouldn't describe the the repo/mirror problems, soon after 3.5.13 was
released, as an issue with 3.5.13 itself; that was just a bit frustrating for
those of us waiting to try out 3.5.13. Far more important was the
KDM-greeter cpu race condition (bug 690), which was a complete a show stopper
for anyone hit by it (which seemed to be the majority of us).
The mirrors do not appear to have been updated since the initial release of
3.5.13 (dates and versions are unchanged) so anyone installing it is very
likely to be hit by 690 and, not knowing how to regress to 3.5.12, will
simply uninstall it and try something else.
In view of this, leaving the installation instructions as they are and telling
Squeeze users to install 3.5.13 seems extremely unwise.
In addition, on the three systems I tried it on (two i386 + one amd64) ,
ksysguard didn't detect the (lm-sensors) hardware sensors, which is also
quite a big issue for me.
LeeE
On a related note, given the problems many have
had with 3.5.13, I think
it would be a good idea to have instructions to install 3.5.12 on current
distros like Oneiric, Squeeze, etc. If new users install "stable" 3.5.13
and have the problems many of us have had, many of them will never try
Trinity again.
I think the main problems with 3.5.13 were the repo failures due to server
problems short after 3.5.13 was out.
3.5.13 as such is more functional (e.g. flash plugin in konqueror working)
than 3.5.12.
at least, this is my experience.
werner