IopenSUSE 12.2 got released some days ago and it seems that the plymouth integration is received very well. Even the openSUSE theme got good comments and is seen as sophisticated. This to my big surprise. 🙂 But i am very happy about it as that it proofs that we all did a good job. Unfortunately it seems that plymouth in combinztion with NVIDIA chipset can sometimes cause some unpleasant surprises. But lets hope we cn sort this out with the next release.
As that the pressure ix off again, i started to work on updates of KDE:Unstable:SC again. Yesterday kdegames was moved from svn to git and split out in seperate repositories. So a lot of new packages have to be created. Hopefully i can finish this soon, so that i can create a new snapshot this coming weekend.
Also Chromium saw a big chance recently. A couple of builds ago we noticed that chromium started to behave rathar crashy. Investigations showed that the our attempt to build with as much system libraries as possible failed. The chromium developers seemed to hsve r3ached the point where the system libraries are no longer compatible with the ones shipped with the chromium source. So as of two build, Chromium is now switched to utilize its full sourcecode. This resolved the issues and also the wotk required in keeping the opensuse patches up to date.
Tittiatcoke's Blog 
We were experiencing some issues in our lab and decided to switch to OpenSuSE — later that week 12.2 came out. I have NEVER seen a more polished and usable installation tool. The NIS and NFS configuration options are excellent — exactly what I needed. I love the new release and we will be using it in our department for some time. Great work!
Thanks for the heads up about Chromium. I really do like the plymouth in 12.2, I have to use an external monitor since my screen is broken and until now the bottom half was cut off in splash. Now it uses full screen. 🙂
Maybe OpenSuSE has done a better job of integrating Plymouth than Kubuntu, it has never given me more than a moment of splashy screen an the inablility to read the boot messages. And that’s when it was at it’s best. Often it has done a total kernel panick lock with filesystems to repair and hairs to pull out. I now use a meta-package which doesn’t require Plymouth even though I’m not actually affected by all the crashes it can give. And yes, I had an NVIDIA card before, but no luck with either proprietary or open drivers.
As for Chromium I have to admit that they did a smashing job making it the really fast in rendering and js interpreting, but they did it at the expense you now experience – no thinking about compatability – just fork whatever you can without thinking about community effords.
I fire up Chromium to test if everything renders as it’s supposed to do, but otherwise I prefer Firefox as it is open and gives back even more than it loans.
Sorry for being so negative – you just hit two of my sore spots 😉
No Problem 🙂 Everybody has it’s own experiences with the product. At the moment we are also experiencing issues with the NVidia drivers which fortunately doesn’t crash the boot process, but garbles the graphical plymouth splash screen or the login manager.
For Chromium switching to the internal libs that the google developers forked, resolved most of the build issues. Life after that became a little easier for me as that I have less patches to take care off. But as you indicated it is not nice that the Chromium binary gets that big just because it can not use the standard system libraries.