[Akonadi] [Bug 313753] New: Akonadi stops working after using a remote X session

[Denys]

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

            Bug ID: 313753
           Summary: Akonadi stops working after using a remote X session
    Classification: Unclassified
           Product: Akonadi
           Version: 4.9
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: kdepim-bugs at kde.org
          Reporter: rtvd at me.com

Akonadi (?) stops working if I logon from another computer using NX client and
open another KDE session (without logging out from the local KDE session). The
obvious symptoms is that KMail does not show any email accounts.


Reproducible: Always

Steps to Reproduce:
1. Log on to KDE (I use one shipped with Kubuntu 12.10)
2. Lock the screen.
3. Log on to KDE on the same computer under the same user from another machine
(I use NX for that as it works better on thin bandwidth).
4. Open KMail there. Notice that it looks OK.
5. Logout from the remote session.
6. Unlock the local KDE session.
7. Launch KMail and notice that no mail accounts is visible. Stop KMail.
8. Launch Akonadi Server Configuration.
9. Notice that an internal mysql server is used. Click "Stop". Wait till
akonadi stops. Click "Start".
10. Launch KMail again. Notice that KMail shows all mail accounts.
Actual Results:  
KMail stops showing mail accounts. There probably are other issues too.
Also, internal mysqld is not running once the remote KDE sesssion is logged
out.

Expected Results:  
KMail should always be able to talk to akonadi and show mail accounts.
Internal mysqld must be stopped only when the last KDE session of a given user
is logged out. Similarly, it must not be started when additional concurrent KDE
sessions are opened for a user.

After step 7:

$ ps ax|grep -i akonadi
 2522 ?        Sl     0:03 /usr/bin/akonadi_control
 2524 ?        Sl     1:10 akonadiserver
 2562 ?        Sl     0:00 /usr/bin/akonadi_agent_launcher
akonadi_akonotes_resource akonadi_akonotes_resource_0
 2563 ?        S      0:02 /usr/bin/akonadi_archivemail_agent --identifier
akonadi_archivemail_agent
 2564 ?        Sl     0:00 /usr/bin/akonadi_agent_launcher
akonadi_contacts_resource akonadi_contacts_resource_0
 2565 ?        Sl     0:00 /usr/bin/akonadi_agent_launcher
akonadi_ical_resource akonadi_ical_resource_0
 2566 ?        Sl     4:10 /usr/bin/akonadi_imap_resource --identifier
akonadi_imap_resource_0
 2567 ?        Sl     0:00 /usr/bin/akonadi_agent_launcher
akonadi_maildir_resource akonadi_maildir_resource_0
 2568 ?        S      0:00 /usr/bin/akonadi_maildispatcher_agent --identifier
akonadi_maildispatcher_agent
 2569 ?        S      0:02 /usr/bin/akonadi_mailfilter_agent --identifier
akonadi_mailfilter_agent
 2572 ?        Sl     1:00 /usr/bin/akonadi_nepomuk_feeder --identifier
akonadi_nepomuk_feeder

Notice that there is no mysqld process running.

However, after restarting the Akonadi:

 ps ax|grep -i akonadi
12637 ?        Sl     0:00 /usr/bin/akonadi_control
12639 ?        Sl     0:00 akonadiserver
12641 ?        Sl     0:03 /usr/sbin/mysqld
--defaults-file=/home/rtvd/.local/share/akonadi/mysql.conf
--datadir=/home/rtvd/.local/share/akonadi/db_data/
--socket=/home/rtvd/.local/share/akonadi/socket-rtvd-PC/mysql.socket
12674 ?        Sl     0:00 /usr/bin/akonadi_agent_launcher
akonadi_akonotes_resource akonadi_akonotes_resource_0
12675 ?        S      0:00 /usr/bin/akonadi_archivemail_agent --identifier
akonadi_archivemail_agent
12676 ?        Sl     0:00 /usr/bin/akonadi_agent_launcher
akonadi_contacts_resource akonadi_contacts_resource_0
12677 ?        Sl     0:00 /usr/bin/akonadi_agent_launcher
akonadi_ical_resource akonadi_ical_resource_0
12678 ?        Sl     0:00 /usr/bin/akonadi_imap_resource --identifier
akonadi_imap_resource_0
12679 ?        Sl     0:00 /usr/bin/akonadi_agent_launcher
akonadi_maildir_resource akonadi_maildir_resource_0
12680 ?        S      0:00 /usr/bin/akonadi_maildispatcher_agent --identifier
akonadi_maildispatcher_agent
12681 ?        S      0:00 /usr/bin/akonadi_mailfilter_agent --identifier
akonadi_mailfilter_agent
12682 ?        Sl     0:00 /usr/bin/akonadi_nepomuk_feeder --identifier
akonadi_nepomuk_feeder
12732 pts/4    S+     0:00 grep --color=auto -i akonadi


Does Akonadi stop its internal mysqld on logout? If it does, can't it just
track the number of active KDE sessions of a given user and not start/stop its
internal mysqld unless it is necessary?

--------

It may look like a minor issue, however:

1. The case when several KDE sessions is opened is fairly common.
2. The behaviour is very annoying.
3. It takes a while to figure out what is probably broken. For someone who is
not an expert in KDE that can be days.
4. Akonadi is responsible for very important aspect of the desktop: PIM. Hence
it should be rock-solid and always available.

-- 
You are receiving this mail because:
You are the assignee for the bug.