Ubuntu quality: security upgrade breaks mysql-server!!!

Wow, Ubuntu!
I just started to believe the quality is not that bad, no this:

I did a security update yesterday (admittedly way too late, as always), and now, my mysql system, which I "only" use for such things as todo management and timetracking on the local machine, refuses to start!

henning@xnote:~$ sudo /etc/init.d/mysql restart
* Stopping MySQL database server mysqld /usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
[ OK ]
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
* Starting MySQL database server mysqld /usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted

/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 20)
Fatal error in defaults handling. Program aborted


O.K., then thing can be fixed by creating the directory with

mkdir /etc/mysql/conf.d

But WTF - how do these guys test their quality?! I'm pretty sure I did not delete this directory - it's really a default install! And how can a security upgrade introduce funcationality to expect a directory, containing OPTIONAL config stuff, and otherwise make the whole daemon startt fail!

Ubuntu loses large trust points from me now! Imagine such a bullshit happens on a server...
So, my opinion about running Ubuntu on a server being quite dangerous is still correct!