[Bug 264383] New: akonadiserver uses ~/.my.cnf dangerously

[Ivan Vasin]

https://bugs.kde.org/show_bug.cgi?id=264383

           Summary: akonadiserver uses ~/.my.cnf dangerously
           Product: Akonadi
           Version: 1.4.80
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: server
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: nisavid at gmail.com


Version:           1.4.80 (using KDE 4.6.0) 
OS:                Linux

this is actually with Akonadi 1.4.90, which is not listed in the available
versions.

after upgrading to KDE 4.6.0 today, i had to battle with Akonadi to get it to
work.  kontact wouldn't even start, and kmail would run but eventually show an
Akonadi error dialog and crash after i closed it.

Akonadi's mysqld error log was showing a bunch of error messages like "InnoDB:
Unable to lock ./ibdata1, error: 11", and ``akonadictl start`` was complaining
about some DBUS service already being registered.

after some unhelpful digging and searching, i tried running ``akonadiserver
start`` and was quite disturbed to find that it logged in to my company's
production database server and start running REPAIR TABLE queries against a
whole bunch of my company's tables.  why it even cared to look at those tables
is beyond me, but the most troublesome part was that it was accessing my
company's DB server in the first place, rather than the local mysqld-akonadi.

i found that commenting out the ``[clients]`` section in my ~/.my.cnf caused
akonadiserver to start successfully and Akonadi to function properly.  why was
akonadiserver reading ~/.my.cnf?  surely the settings there should be totally
ignored by Akonadi.  i would like to use ~/.my.cnf for my convenience, not as a
way to silently reconfigure Akonadi to read and modify my company's databases.

the REPAIR TABLE queries continued running until we discovered and killed them
later in the day.

Reproducible: Always

Steps to Reproduce:
1. create a non-trivial ``[clients]`` section in ~/.my.cnf.
2. log in to KDE or run ``akonadiserver start``.

Actual Results:  
akonadiserver attempts to use whatever database is pointed to by ~/.my.cnf and
runs REPAIR TABLE on various tables.

Expected Results:  
akonadiserver ignores ~/.my.cnf and uses its own database connection settings.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.