Bug 251180

Please try the following steps:

- Quit akonadi tray
- in a terminal, run 'kdebugdialog' and look for 'akonaditray' check the box then 'ok'

- Now run akonaditray for the terminal and try to reproduce.

Akonaditray should be more verbose

Created attachment 51651 [details]
conslle output of Akonadi starting and when a backup is attempted.

I get the following output:

akonaditray(26196) Backup::possible: mysqldump: "/usr/bin/mysqldump" bzip2: "/bin/bzip2" tar: "/bin/tar"
akonaditray(26196) KFileItemPrivate::init: "akonadibackup-20101112.tar.bz2" does not exist anymore
akonaditray(26196) KSharedUiServerProxy::KSharedUiServerProxy: kuiserver registered
akonaditray(26196) Backup::create: Executing:  "/usr/bin/mysqldump" ("--single-transaction", "--master-data=2", "--flush-logs", "--triggers", "--result-file=/tmp/kde-janet/akonadiDA3v1a/db/database.sql", "--socket=/home/janet/.local/share/akonadi/db_misc/mysql.socket", "akonadi")
mysqldump: Error: Binlogging on server not active
akonaditray(26196) Backup::create: Executed:  "/usr/bin/mysqldump" ("--single-transaction", "--master-data=2", "--flush-logs", "--triggers", "--result-file=/tmp/kde-janet/akonadiDA3v1a/db/database.sql", "--socket=/home/janet/.local/share/akonadi/db_misc/mysql.socket", "akonadi") Result:  2

It did work before. I have a backup from May. Must have been made with KDE SC 4.4.x.

I get a similar output, the backup tar.bz2 file gets deleted. It even gets deleted when I create it in advance.

What I get:
akonaditray(29274)/kio (KDirListerCache) KDirListerCache::slotResult: finished listing KUrl("file:///home/peter/Backup")
akonaditray(29274)/kio (KIOJob) KIO::SlaveInterface::dispatch: error  111   "akonadibackup-20101112.tar.bz2"
akonaditray(29274)/kio (Scheduler) KIO::SchedulerPrivate::jobFinished: KIO::StatJob(0x8aaafc0) KIO::Slave(0x8a82fd0)
akonaditray(29274) KFileItemPrivate::init: "akonadibackup-20101112.tar.bz2" does not exist anymore
akonaditray(29274)/kio KNFSShare::KNFSSharePrivate::findExportsFile: Could not find exports file! /etc/exports doesn't exist. Configure it in share/config/knfsshare, [General], exportsFile=....
[...]
To shorten it a bit: for all subfolders in /home/peter/Backup I get the following (it's not possible to create a thumnail for the folder):
akonaditray(29274)/kio (KIOJob) KIO::SlaveInterface::dispatch: error  104   "Für den Ordner kann kein Miniaturbild erzeugt werden."
[...]
akonaditray(29274) Backup::create: Executing:  "/usr/bin/mysqldump" ("--single-transaction", "--master-data=2", "--flush-logs", "--triggers", "--result-file=/tmp/kde-peter/akonadie3KwoJ/db/database.sql", "--socket=/home/peter/.local/share/akonadi/db_misc/mysql.socket", "akonadi")
mysqldump: Error: Binlogging on server not active
akonaditray(29274) Backup::create: Executed:  "/usr/bin/mysqldump" ("--single-transaction", "--master-data=2", "--flush-logs", "--triggers", "--result-file=/tmp/kde-peter/akonadie3KwoJ/db/database.sql", "--socket=/home/peter/.local/share/akonadi/db_misc/mysql.socket", "akonadi") Result:  2 
akonaditray(29274)/kio (Slave) KIO::Slave::kill: killing slave pid 30096 ( "file://" )
akonaditray(29274)/kio (Slave) KIO::Slave::kill: killing slave pid 30095 ( "trash://" )
akonaditray(29274)/kio (Slave) KIO::Slave::kill: killing slave pid 30098 ( "thumbnail://" )
akonaditray(29274)/kio (Slave) KIO::Slave::kill: killing slave pid 30097 ( "file://" )

looks like the generation of $HOME/.local/share/akonadi/mysql.conf is broken, it comments the log_bin line. there are two of them, didn't test which one is needed, just uncommented both of them.

workaround:
# execute
sed -i -e 's/#log_bin/log_bin' $HOME/.local/share/akonadi/mysql.conf
akonadictl restart
# now do your backup

still present with Akonadi 1.4.90 and KDE 4.6.0.

This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.