I was awaiting .41 update because I was convinced that a properly done upgrade could have revamped my system after a not so happy upgrade from .39 to .40.
Unfortunately things went in a very different way, and now I find myself again with a totally not working system.
Here a brief history.
After .41 announcement I waited a couple of days to be sure that all replacement were properly downloaded.
Yesterday night I rebooted hybrid to let update to take place, but with my great disappointment system started to cycle (reboot, and reboot ....).
So I booted in recovery mode and tried to apt-get upgrade manually, and it turned out that linphone-common was having a problem (problem when overwriting a wav file that was also contained in pluto-linphone).
I removed pluto-linphone, then apt-get upgrade made its course, then the system rebooted properly (no cycling), but now my hybrid is not showing any UI (it is showing a rubbish screen that make me think that video init is not good)
Moreover MDs are not booting over network and this make me think that system is locking in a strange state, even if I still can ssh to hybrid and plutoadmin site is working fine.
I did not dig into logs too much, as I'm afraid that it would take too long (considering my not-so-high knowledge of linux) and my actual concern is to have my system back ASAP.
I think that I will go for a fresh install (preserving media an possibly logs) but I think that this situation may be interesting to investigate.
I think that all Pluto guys will agree on the fact that a system cannot get scr**ed on every upgrade, isn't it ? :wink:
Actually my hardware is not "second choice", my hybrid has an AMD Athlon 3200, 2 GbRam, nVidia integrated video card, 2 X 200 SATA drives, so these failures cannot be charged to insufficient "horse power" or similar.
As I said I will preserve logs. If anyone at Pluto is interested to help me to figure out what the hell happened I will gladly support them.