Public bug reported:
I'm not sure wheter this is the appropriate place, but after I've fresh-
installed Gusty - or upgraded Feisty to Gutsy - on 7 different systems
(1 server, 4 desktops, 2 laptops), I have felt quite disappointed with
this new release, as each installation or upgrade on each machine
brought me its host of bugs and regressions from Feisty.
So I felt the need of opening this "bug report" for overall release
quality and report most serious trouble as a whole "distro bug".
To make it plain and simple, Feisty worked like a charm on every machine
I used it on, while Gutsy broke something important - or at least
annoying - on each and every machine I tried it on.
The only improvement that matters to me and that Gutsy brought over
Feisty is that, one one laptop, I now have support for the included
SD/MMC card reader where Feisty didn't see it at all.
To be honest, I have mostly tested and used the KDE flavour (Kubuntu)
and not much the Gnome flavour (Ubuntu), so I cannot tell whether there
are significant improvements in the Gnome area.
For the rest... Trouble.
Among the most serious or annoying bugs I fell upon :
- Kubuntu's adept_manager is simply not up to the job of upgrading from Feisty
to Gutsy (where Ubuntu's tool does it quite well). adept_manager systematically
fails during upgrades in plenty of situations ; it's enough that a package
upgrade tries to ask "Do I keep your old config file or install the package
maintainer's new one" ? For adept_manager to fail. All Kubuntu upgrades I
started with adept_manager ended in command-line using aptitude... (Bug #158043)
- Upgrading Feisty to Gutsy doesn't put the "initrd" line for the new kernel in
grub's menu.lst. Seen on 2 machines. Of course then, system boot fails. (Bug
#156058)
- Gutsy breaks encrypted filesystems at boot time if /usr is in a separate
partition, as /sbin/cryptsetup has dependancies with libraries located in
/usr/lib . Encrypted partitions don't mount, system won't boot. (Bug #139635)
- Several daemons don't start anymore as /var/run is now tmpfs but the daemon
startup script doesn't find nor create their /var/run/somedaemon directory.
Suffered from this for 2 daemons (sympa and dspam), seen that same problem has
been reported for more. (Bug #158252 and others)
- A machine that used to shutdown plain good in feisty now sporadically hangs
shutting down in Gutsy, kind of problem reported by several others (Bug #119308)
- Laptops using ATI display driver used to suspend to RAM and hibernate
properly in Feisty. Now they crash trying to suspend or hibernate in Gusty.
(Bug #121653)
- A machine that showed a Wi-Fi connection perfectly stable in Feisty, using
ndiswrapper and a Windows driver, now has an unstable Wi-Fi connection in Gusty
- using the same Windows driver, even reinstalled it - and now happens to hang
completely if losing Wi-Fi link - never happened with Feisty.
What a bunch of serious regressions ! I was really disappointed seing so
many pure regressions from Feisty to Gutsy on each and every machine I
installed or upgraded...
Not even stating that I have installed systems for friends which I
convinced to try to step out of Windows into Linux with the "easy,
polished and stable" Ubuntu, friends who are now laughing at their
instable system that crashes at shutdown, won't hibernate since the
upgrade, etc... I know have to face friends stating I broke their system
"upgrading" it, and well, they're damn right...
I would add to this the poor choice of replacing Good Old Konqueror with
Dolphin as default file manager in Kubuntu - not found yet a single
person preferring Dolphin to Konqueror, whether newbie or experimented
Linux user.
I sincerely hope that the release of "hardy" will pay much more
attention NOT TO REGRESS on so many, and important, points (Geeez !
Daemons that don't start ! Partitions that don't mount ! Systems that
don't even boot !) for my confidence in Ubuntu has been quite undermined
by these recent experiences I had...
** Affects: ubuntu
Importance: Undecided
Status: New
--
Gutsy release overall quality and regressions
https://bugs.launchpad.net/bugs/159015
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
