Typical

I hate it when this happens but it happens far too often with upgrades.  I upgraded my laptop to Ubuntu 12.04 (which is another post to be made).  About a month later (today) I need to put some photos from my camera into digikam.  When I start up digikam I get this error:


You have insufficient privileges on the database.
Following privileges are not assigned to you:
CREATE TRIGGER
Check your privileges on the database and restart digiKam.

A google search turns up https://bugs.kde.org/show_bug.cgi?id=262321 ( a Jan 2011 bug)

Basically, some change was made to digikam in how it uses the database, but it doesn't quite work right with mysql.  The work around is to give the digikam user full privs on the entire mysql database.

There is this comment:

--- Comment #15 from davidebasilio <marsicanbear gmail com>  2011-11-07 16:12:55 --- 
Digikam 2.3.0 is out http://www.digikam.org/drupal/node/632
But it looks like noone took care of this bug since 2.0.0 
Will it ever be fixed? 
BTW, this is tagged as wishlist, but I do not really think that's correct. This 
is a bug. 


</end comment>


So, it's almost 18 months later and this is a still an issue!  The glacial pace at which these fixes get introduced combined with the super fast pace new features (and bugs) get introduced really frustrates me.  Now I have to do a work around which some years later will cause some problem and I'll never make the connection.


Check out this comment from the bug:

Bruno Friedmann 2011-03-31 08:13:20 UTC

Marcel, in fact I don't know how you can do that, due to upstream (bug/feature) the creation of triggers apparently are root reserved in mysql, due to replication feature of the database engine. ref http://dev.mysql.com/doc/refman/5.0/en/stored-programs-logging.html So for the "normal" embedded mysql there's no troubles as it's run like superuser by end user. The real impact is about using digikam in shared mode (centralized mysql server). So digikam can said : hey we didn't support that, but as it has, it will become a big regression. Time to interface digikam to virtuozzo ? :D

I mean, why do they offer the option to run shared mode if they aren't going to make sure it works on every release?  This is one of my big gripes about FOSS software - they build lots and lots of doors that you can open, but only a few will lead you to safety and many lead you to your doom (although they appear perfectly safe).  I chose the door to using a shared mysql server and I am now paying the price.




UPDATE (6/25)--
I finally got digikam working again.  There were numerous issues and I am not sure which one was the culprit.  First, some operations in mysql gave me errors or warnings about some mysql internal tables that had the wrong number of fields (20 vs 16).  It seemed this was due to an upgrade that didn't complete normally.  I ran mysql_upgrade --force and complained about some ampache tables that needed repairing.  After that it gave me this error:

Error: Incorrect database name '#mysql50#mysql.orig'

I had to remove the mysql.orig directory from /var/lib/mysql

 After fixing those, it seemed to update the database correctly.  The other thing I did (and maybe this wasn't required) was add the
create_index_if_not_exists() proc to the digikam databases per this bug (https://bugs.kde.org/show_bug.cgi?id=276052).

Now digikam works again.  But if you search for "digikam failed to upgrade" you will see lots of threads talking about failures to upgrade the schema for digikam from 5 to 6.