Launchpad has imported 35 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=326480.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2013-10-23T04:34:30+00:00 Glentadakis Dimitrios wrote: Since 1 month, akonadi fails to start after boot I deleted the content of the folders .local/share/akonadi and .configure/akonadi, it works for a few days and after it stops again Reproducible: Always Steps to Reproduce: After boot Actual Results: Akonadi doesn't start Expected Results: Akonadi start up Akonadi Server Self-Test Report =============================== Test 1: SUCCESS -------- Database driver found. Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system. File content of '/home/dglent/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL [QMYSQL] Name=akonadi Host= Options="UNIX_SOCKET=/home/dglent/.local/share/akonadi/socket-localhost.localdomain/mysql.socket" ServerPath=/usr/sbin/mysqld StartServer=true [Debug] Tracer=null Test 2: SUCCESS -------- Akonadi is not running as root Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system. Test 3: SUCCESS -------- MySQL server found. Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld'. Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution. Test 4: SUCCESS -------- MySQL server is executable. Details: MySQL server found: 131019 14:08:14 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead. /usr/sbin/mysqld Ver 5.5.33a-MariaDB for Linux on x86_64 (Mageia MariaDB Server) Test 5: SUCCESS -------- MySQL server log contains no errors. Details: The MySQL server log file '<a href='/home/dglent/.local/share/akonadi/db_data/mysql.err'>/home/dglent/.local/share/akonadi/db_data/mysql.err</a>' does not contain any errors or warnings. File content of '/home/dglent/.local/share/akonadi/db_data/mysql.err': 131019 13:59:17 InnoDB: The InnoDB memory heap is disabled 131019 13:59:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins 131019 13:59:17 InnoDB: Compressed tables use zlib 1.2.7 131019 13:59:17 InnoDB: Using Linux native AIO 131019 13:59:17 InnoDB: Initializing buffer pool, size = 80.0M 131019 13:59:17 InnoDB: Completed initialization of buffer pool 131019 13:59:17 InnoDB: highest supported file format is Barracuda. 131019 13:59:18 InnoDB: Waiting for the background threads to start 131019 13:59:19 Percona XtraDB (http://www.percona.com) 5.5.33a-MariaDB-31.1 started; log sequence number 21404448 131019 13:59:19 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.33a-MariaDB' socket: '/home/dglent/.local/share/akonadi/socket-localhost.localdomain/mysql.socket' port: 0 Mageia MariaDB Server Test 6: SUCCESS -------- MySQL server default configuration found. Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>. File content of '/etc/akonadi/mysql-global.conf': # # Global Akonadi MySQL server settings, # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf # # Based on advice by Kris Köhntopp <k...@mysql.com> # [mysqld] # strict query parsing/interpretation # TODO: make Akonadi work with those settings enabled # sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat # sql_mode=strict_trans_tables # DEBUGGING: # log all queries, useful for debugging but generates an enormous amount of data # log=mysql.full # log queries slower than n seconds, log file name relative to datadir (for debugging only) # log_slow_queries=mysql.slow # long_query_time=1 # log queries not using indices, debug only, disable for production use # log_queries_not_using_indexes=1 # # mesure database size and adjust innodb_buffer_pool_size # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema"); # NOTES: # Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables) #expire_logs_days=3 #sync_bin_log=0 # Use UTF-8 encoding for tables character_set_server=utf8 collation_server=utf8_general_ci # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M) innodb_additional_mem_pool_size=1M # memory buffer InnoDB uses to cache data and indexes of its tables (default:128M) # Larger values means less I/O innodb_buffer_pool_size=80M # Create a .ibd file for each table (default:0) innodb_file_per_table=1 # Write out the log buffer to the log file at each commit (default:1) innodb_flush_log_at_trx_commit=2 # Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin) # larger values means less I/O innodb_log_buffer_size=1M # Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery. innodb_log_file_size=64M # # error log file name, relative to datadir (default:hostname.err) log_error=mysql.err # print warnings and connection errors (default:1) log_warnings=2 # Convert table named to lowercase lower_case_table_names=1 # Maximum size of one packet or any generated/intermediate string. (default:1M) max_allowed_packet=32M # Maximum simultaneous connections allowed (default:100) max_connections=256 # The two options below make no sense with prepared statements and/or transactions # (make sense when having the same query multiple times) # Memory allocated for caching query results (default:0 (disabled)) query_cache_size=0 # Do not cache results (default:1) query_cache_type=0 # Do not use the privileges mechanisms skip_grant_tables # Do not listen for TCP/IP connections at all skip_networking # The number of open tables for all threads. (default:64) table_cache=200 # How many threads the server should cache for reuse (default:0) thread_cache_size=3 # wait 365d before dropping the DB connection (default:8h) wait_timeout=31536000 [client] default-character-set=utf8 Test 7: SKIP -------- MySQL server custom configuration not available. Details: The custom configuration for the MySQL server was not found but is optional. Test 8: SUCCESS -------- MySQL server configuration is usable. Details: The MySQL server configuration was found at <a href='/home/dglent/.local/share/akonadi/mysql.conf'>/home/dglent/.local/share/akonadi/mysql.conf</a> and is readable. File content of '/home/dglent/.local/share/akonadi/mysql.conf': # # Global Akonadi MySQL server settings, # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf # # Based on advice by Kris Köhntopp <k...@mysql.com> # [mysqld] # strict query parsing/interpretation # TODO: make Akonadi work with those settings enabled # sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat # sql_mode=strict_trans_tables # DEBUGGING: # log all queries, useful for debugging but generates an enormous amount of data # log=mysql.full # log queries slower than n seconds, log file name relative to datadir (for debugging only) # log_slow_queries=mysql.slow # long_query_time=1 # log queries not using indices, debug only, disable for production use # log_queries_not_using_indexes=1 # # mesure database size and adjust innodb_buffer_pool_size # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema"); # NOTES: # Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables) #expire_logs_days=3 #sync_bin_log=0 # Use UTF-8 encoding for tables character_set_server=utf8 collation_server=utf8_general_ci # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M) innodb_additional_mem_pool_size=1M # memory buffer InnoDB uses to cache data and indexes of its tables (default:128M) # Larger values means less I/O innodb_buffer_pool_size=80M # Create a .ibd file for each table (default:0) innodb_file_per_table=1 # Write out the log buffer to the log file at each commit (default:1) innodb_flush_log_at_trx_commit=2 # Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin) # larger values means less I/O innodb_log_buffer_size=1M # Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery. innodb_log_file_size=64M # # error log file name, relative to datadir (default:hostname.err) log_error=mysql.err # print warnings and connection errors (default:1) log_warnings=2 # Convert table named to lowercase lower_case_table_names=1 # Maximum size of one packet or any generated/intermediate string. (default:1M) max_allowed_packet=32M # Maximum simultaneous connections allowed (default:100) max_connections=256 # The two options below make no sense with prepared statements and/or transactions # (make sense when having the same query multiple times) # Memory allocated for caching query results (default:0 (disabled)) query_cache_size=0 # Do not cache results (default:1) query_cache_type=0 # Do not use the privileges mechanisms skip_grant_tables # Do not listen for TCP/IP connections at all skip_networking # The number of open tables for all threads. (default:64) table_cache=200 # How many threads the server should cache for reuse (default:0) thread_cache_size=3 # wait 365d before dropping the DB connection (default:8h) wait_timeout=31536000 [client] default-character-set=utf8 Test 9: SUCCESS -------- akonadictl found and usable Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully. Result: Akonadi 1.9.1 Test 10: ERROR -------- Akonadi control process not registered at D-Bus. Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 11: ERROR -------- Akonadi server process not registered at D-Bus. Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 12: ERROR -------- Nepomuk search service not registered at D-Bus. Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 13: SKIP -------- Protocol version check not possible. Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements. Test 14: ERROR -------- No resource agents found. Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share:/usr/share:/usr/local/share'; make sure this includes all paths where Akonadi agents are installed. Directory listing of '/usr/share/akonadi/agents': akonadinepomukfeederagent.desktop akonotesresource.desktop archivemailagent.desktop birthdaysresource.desktop contactsresource.desktop davgroupwareresource.desktop facebookresource.desktop googlecalendarresource.desktop googlecontactsresource.desktop icaldirresource.desktop icalresource.desktop imapresource.desktop invitationsagent.desktop kabcresource.desktop kalarmdirresource.desktop kalarmresource.desktop kcalresource.desktop kdeaccountsresource.desktop knutresource.desktop kolabproxyresource.desktop localbookmarksresource.desktop maildirresource.desktop maildispatcheragent.desktop mailfilteragent.desktop mboxresource.desktop microblog.desktop mixedmaildirresource.desktop mtdummyresource.desktop nepomuktagresource.desktop nntpresource.desktop notesresource.desktop openxchangeresource.desktop pop3resource.desktop vcarddirresource.desktop vcardresource.desktop Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share:/usr/local/share' Test 15: SUCCESS -------- No current Akonadi server error log found. Details: The Akonadi server did not report any errors during its current startup. Test 16: SUCCESS -------- No previous Akonadi server error log found. Details: The Akonadi server did not report any errors during its previous startup. Test 17: SUCCESS -------- No current Akonadi control error log found. Details: The Akonadi control process did not report any errors during its current startup. Test 18: SUCCESS -------- No previous Akonadi control error log found. Details: The Akonadi control process did not report any errors during its previous startup. Installed packages: [dglent@localhost ~]$ rpm -qa | grep akonadi akonadiconsole-4.10.5-1.1.mga3 lib64akonadi-devel-1.9.1-2.mga3 lib64akonadi-xml4-4.10.5-1.1.mga3 lib64akonadi_socialutils4-4.10.5-1.1.mga3 lib64akonadi-kabc4-4.10.5-1.1.mga3 lib64akonadi-notes4-4.10.5-1.1.mga3 lib64akonadi-filestore4-4.10.5-1.1.mga3 lib64akonadi-kde4-4.10.5-1.1.mga3 lib64akonadi-next4-4.10.5-1.1.mga3 lib64akonadi-kmime4-4.10.5-1.1.mga3 lib64akonadi-kcal4-4.10.5-1.1.mga3 lib64akonadi-contact4-4.10.5-1.1.mga3 akonadi-kde-4.10.5-1.1.mga3 lib64akonadiprotocolinternals1-1.9.1-2.mga3 akonadi-1.9.1-2.mga3 lib64akonadi-calendar4-4.10.5-1.1.mga3 [dglent@localhost ~]$ rpm -qa | grep sql qt4-database-plugin-sqlite-4.8.5-1.2.mga3 qt4-database-plugin-mysql-4.8.5-1.2.mga3 lib64sqlite3-devel-3.8.0.2-1mgr3 postgresql-jdbc-9.2.1002-3.mga3 python-qt4-sql-4.9.6-4.mga3 lib64qtsql4-4.8.5-1.2.mga3 lib64sqlite3_0-3.8.0.2-1mgr3 [dglent@localhost ~]$ rpm -qa | grep maria mariadb-client-5.5.33a-1.mga3 mariadb-core-5.5.33a-1.mga3 lib64mariadb18-5.5.33a-1.mga3 mariadb-common-5.5.33a-1.mga3 mariadb-common-core-5.5.33a-1.mga3 Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/0 ------------------------------------------------------------------------ On 2013-10-24T15:26:08+00:00 Dvratil wrote: Can you please provide output of "ps x | grep -i akonadi" ? Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/1 ------------------------------------------------------------------------ On 2013-10-28T14:23:36+00:00 Graeme Hewson wrote: I have this problem after upgrading Kubuntu 13.04 to 13.10, but not always. Sometimes after rebooting and logging in, Akonadi starts properly, but most often, although akonadi_control and akonadiserver are running, I see the messages in tests 10 and 11: Akonadi control process not registered at D-Bus. Akonadi server process not registered at D-Bus. (Unlike the above log, though, test 12 for me says "Nepomuk search service registered at D-Bus.") The solution for me is: pkill akonadi_control pkill akonadiserver akonadictl start I guess it's a timing problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/2 ------------------------------------------------------------------------ On 2013-10-28T14:25:53+00:00 Graeme Hewson wrote: I forgot to mention that I had the KDE 4.11.2 PPA installed under Kubuntu 13.04, so the KDE version didn't change with the upgrade to 13.10. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/3 ------------------------------------------------------------------------ On 2013-10-28T14:44:34+00:00 Cgiboudeaux wrote: (In reply to comment #3) > I forgot to mention that I had the KDE 4.11.2 PPA installed under Kubuntu > 13.04, so the KDE version didn't change with the upgrade to 13.10. no message from apparmor in the dmesg output ? can you also check if the mysql version changed when your switched to kubuntu 13.10 ? are the mysql-upgrade and mysqladmin still installed ? Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/4 ------------------------------------------------------------------------ On 2013-10-28T15:43:15+00:00 Graeme Hewson wrote: Messages from apparmor are: apparmor="DENIED" operation="file_perm" info="Failed name lookup - disconnected path" error=-13 parent=1 profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name=".local/share/akonadi/db_data/mysql.err" pid=2813 comm="mysqld" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 apparmor="DENIED" operation="file_perm" info="Failed name lookup - disconnected path" error=-13 parent=1 profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name=".local/share/akonadi/db_data/mysql.err" pid=2813 comm="mysqld" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Mysql changed from 5.5.32 to 5.5.34. mysqladmin is installed, but not mysql-upgrade. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/5 ------------------------------------------------------------------------ On 2013-10-28T18:33:07+00:00 Cgiboudeaux wrote: ok, please try: sudo aa-complain mysqld-akonadi sudo /etc/init.d/apparmor reload akonadictl start Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/6 ------------------------------------------------------------------------ On 2013-10-31T19:11:22+00:00 Giovanni Escobar Sosa wrote: After installing Kubuntu 13.10 from Kubuntu 13.04 I have found the same problem with Akonadi. After deleting ~/.local/share/akonadi and ~/.config/akonadi I could reload the calendar I have in KOrganizer, but the events are not loaded until I restart the session. I too had KDE 4.11.2, but from a PPA, ppa:kubuntu-ppa/backports. Just today the same happened after several days of normal use. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/12 ------------------------------------------------------------------------ On 2013-11-01T10:17:02+00:00 Graeme Hewson wrote: (In reply to comment #6) > ok, please try: > sudo aa-complain mysqld-akonadi > sudo /etc/init.d/apparmor reload > akonadictl start I didn't try this because the apparmor messages haven't reappeared after several reboots. I guess they only appeared because I was struggling to get kmail working after the Kubuntu upgrade. Still akonadi sometimes starts properly after rebooting and logging in, but mostly it doesn't. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/13 ------------------------------------------------------------------------ On 2013-11-01T18:54:24+00:00 Giovanni Escobar Sosa wrote: Again Akonadi fail to load. After using $ pkill akonadi_control $ pkill akonadiserver $ akonadictl start I got this exit Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) search paths: ("/home/giovanni/bin", "/usr/lib/lightdm/lightdm", "/usr/local/sbin", "/usr/local/bin", "/usr/sbin", "/usr/bin", "/sbin", "/bin", "/usr/games", "/usr/local/games", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin") akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontable OK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.pimitemflagrelation OK akonadi.pimitemtable OK akonadi.resourcetable OK akonadi.schemaversiontable OK mysql.columns_priv OK mysql.db OK mysql.event OK mysql.func OK mysql.general_log OK mysql.help_category OK mysql.help_keyword OK mysql.help_relation OK mysql.help_topic OK mysql.host OK mysql.ndb_binlog_index OK mysql.plugin OK mysql.proc OK mysql.procs_priv OK mysql.proxies_priv OK mysql.servers OK mysql.slow_log OK mysql.tables_priv OK mysql.time_zone OK mysql.time_zone_leap_second OK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_type OK mysql.user OK Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) search paths: ("/home/giovanni/bin", "/usr/lib/lightdm/lightdm", "/usr/local/sbin", "/usr/local/bin", "/usr/sbin", "/usr/bin", "/sbin", "/bin", "/usr/games", "/usr/local/games") Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. search paths: ("/home/giovanni/.kde/lib/kde4/plugins/", "/usr/lib/kde4/plugins/", "/usr/lib/x86_64-linux-gnu/qt4/plugins", "/usr/lib/qt4/plugins", "/usr/bin", "/usr/lib/kde4/plugins", "/home/giovanni/.kde/lib/kde4/", "/usr/lib/kde4/") search paths: ("/home/giovanni/.kde/lib/kde4/plugins/", "/usr/lib/kde4/plugins/", "/usr/lib/x86_64-linux-gnu/qt4/plugins", "/usr/lib/qt4/plugins", "/usr/bin", "/usr/lib/kde4/plugins", "/home/giovanni/.kde/lib/kde4/", "/usr/lib/kde4/") "Cannot connect to agent instance with identifier 'akonadi_maildir_resource_0', error message: 'Could not get owner of name 'org.freedesktop.Akonadi.Resource.akonadi_maildir_resource_0': no such name'" Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. akonadi_nepomuk_feeder(10690) FeederPluginloader::feederPluginsForMimeType: No feeder for type "text/calendar" found Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. And it stayed there until I hit enter again. Akonadi is working and I can see my programmed events. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/14 ------------------------------------------------------------------------ On 2013-11-02T11:46:07+00:00 Graeme Hewson wrote: I've noticed that akonadi usually starts OK when I log in after being logged in previously for several days. When this happens, nepomuk seems to be working hard (catching up on the work it didn't do in the previous login session?). Incidentally, in comment 2 I neglected to show a clean shutdown of mysql. The full sequence of commands is: pkill akonadi_control pkill akonadiserver mysqladmin shutdown --socket ~/.local/share/akonadi/socket-$(hostname)/mysql.socket akonadictl start Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/16 ------------------------------------------------------------------------ On 2013-11-02T12:20:33+00:00 Glentadakis Dimitrios wrote: The output of ps x | grep -i akonadi: [dglent@localhost ~]$ ps x | grep -i akonadi 1673 ? Sl 0:00 /usr/bin/akonadi_control 1675 ? Sl 0:00 akonadiserver 1677 ? Sl 0:00 /usr/sbin/mysqld --defaults-file=/home/dglent/.local/share/akonadi/mysql.conf --datadir=/home/dglent/.local/share/akonadi/db_data/ --socket=/home/dglent/.local/share/akonadi/socket-localhost.localdomain/mysql.socket Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/17 ------------------------------------------------------------------------ On 2013-11-03T04:59:41+00:00 Glentadakis Dimitrios wrote: I can reproduce it with mariadb 5.5.33a but i cannot reproduce it with mariadb-5-5-28. I will continue the test and i will confirm it later. I remarked with mariadb 5.5.33a i have the process mysqlcheck as zombie Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/18 ------------------------------------------------------------------------ On 2013-11-04T05:30:36+00:00 Glentadakis Dimitrios wrote: This morning i had again the symptome with mariadb 5.5.28 :( Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/19 ------------------------------------------------------------------------ On 2013-11-04T12:12:44+00:00 Dvratil wrote: The problem appears to be that sometimes (?) Akonadi is unable to start any resources or agents. Akonadi requires at least one agent or resource to run. Apparently the resources are available (judging from content of /usr/share/akonadi/agents). Please enable ibakonadi in kdebugdialog and start Akonadi from console (akonadictl start) and paste here the output. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/20 ------------------------------------------------------------------------ On 2013-11-05T15:13:39+00:00 japs_it88 wrote: *** Bug 327159 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/25 ------------------------------------------------------------------------ On 2013-11-07T15:40:50+00:00 Glentadakis Dimitrios wrote: The output of akonadictl start: [dglent@localhost ~]$ akonadictl start Unable to register service as "org.freedesktop.Akonadi.Control.lock" Maybe it's already running? "[ 0: /usr/bin/akonadi_control(_Z11akBacktracev+0x33) [0x43e943] 1: /usr/bin/akonadi_control() [0x43ec9a] 2: /lib64/libc.so.6(+0x34ae0) [0x7f949291bae0] 3: /lib64/libc.so.6(gsignal+0x35) [0x7f949291ba65] 4: /lib64/libc.so.6(abort+0x148) [0x7f949291d0c8] 5: /lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7f949392a224] 6: /usr/bin/akonadi_control(_ZN15FileDebugStream9writeDataEPKcx+0x9b) [0x440a0b] 7: /lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb4) [0x7f94939c4af4] 8: /lib64/libQtCore.so.4(+0x11682f) [0x7f94939cf82f] 9: /lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x7f94939d7e2b] 10: /usr/bin/akonadi_control(_ZN6QDebugD1Ev+0x3f) [0x41c48f] 11: /usr/bin/akonadi_control(main+0x350) [0x419230] 12: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f9492908ba5] 13: /usr/bin/akonadi_control() [0x4193f9] ] " Error: akonadi_control was started but didn't register at D-Bus session bus. Make sure your system is set up correctly! Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/27 ------------------------------------------------------------------------ On 2013-11-10T13:29:27+00:00 Graeme Hewson wrote: Created attachment 83470 libakonadi debug output Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/28 ------------------------------------------------------------------------ On 2013-11-10T13:30:26+00:00 Graeme Hewson wrote: I directed libakonadi debug output to disk while I logged in to KDE (file attached). The messages make reference to /tmp/akonadi- ghewson.ws0sFY/akonadiserver.socket, but there is no such file. This is after a reboot (on Kubuntu, where /tmp is cleared between reboots). However, the file /did/ exist in the previous session, and in the current session ~/.local/share/akonadi/socket-$(hostname) is a link to /tmp/akonadi-ghewson.ws0sFY/akonadiserver.socket. The messages also say "Akonadi server is already starting up", but before logging in to KDE I started a terminal session and verified that Akonadi wasn't running. (It's very hard to see how it could have been!) To reiterate: sometimes Akonadi does start properly. In fact, while I was debugging, it usually did (presumably due to a change in the timing), and I had to try several times before it failed to start properly. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/29 ------------------------------------------------------------------------ On 2013-11-11T16:23:45+00:00 Dvratil wrote: Could any of you please try whether the problem is fixed with this [0] patch for kdepimlibs? The patch addresses a DBus-timing problem that could be the same as yours. I'm just not very happy about how it fixes the problem. We will work on it with Guy this weekend on the PIM sprint and get it to next KDE update. [0] https://git.reviewboard.kde.org/r/112062/ Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/30 ------------------------------------------------------------------------ On 2013-11-29T14:01:06+00:00 Tsu Jan wrote: *** Bug 328201 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/39 ------------------------------------------------------------------------ On 2013-11-29T15:07:58+00:00 Tsu Jan wrote: @Daniel Vrátil Sadly, the patch didn't fix the problem. After the first reboot, Akonadi started normally but after another reboot, the same issue happened again. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/40 ------------------------------------------------------------------------ On 2013-11-30T11:40:52+00:00 Elsevier wrote: *** This bug has been confirmed by popular vote. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/41 ------------------------------------------------------------------------ On 2013-11-30T11:49:30+00:00 Elsevier wrote: Hi Guys - I filed one bug report on Kubuntu-launchpad for this bug before we realized that this affects not only Kubuntu users. I cannot follow any more which of the various things I did changed my situation, but now under KDE 4.11.3 my akonadi almost always starts on booting (not always though, but mostly compared to almost never before). If akonadi fails to start, the three pkill commands mentioned above remedy this problem. However, if I get akonadi started I now always observe serious CPU consumption of both mysql and akonadi on working with kontact. reading emails and managing them is very slow, but sending is impossible. Kontact always becomes unresponsive and eventually crashed on this step. However, I found an advice to remedy this problem by "cleaning up the profile" and want to give this a try. However, how exactly do I COMPLETELY clean up kontact/akonadi/whatever else profile and start completely clean. No worries about backup here - everything is IMAP and calender is back-uped already. Thanks Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/42 ------------------------------------------------------------------------ On 2013-11-30T12:22:09+00:00 Bartosz Kwitniewski wrote: I have moved akonadi database from ~/.local/share/akonadi to another directory few days ago but it didn't help - I still have to kill and start akonadi every time. Note that removing database will at least mess up directories settings (sent, trash, etc. in identities and filters), so filters can move Your mail to more or less random directories. I have tried patching (https://git.reviewboard.kde.org/r/112062/) - Kmail did start about 15 seconds after logging in and I was able to read mail but I couldn't mark it as read or delete it - as if database became read-only. Also, I still wasn't able to stop and start akonadi from akonaditray - I had to kill it. There are so many corpses laying around. Arch Linux 64 bit, KDE 4.11.3, KMail 4.11.3, mysql 5.5.30 Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/43 ------------------------------------------------------------------------ On 2013-11-30T13:48:37+00:00 Tsu Jan wrote: I don't know if this info is helpful in debugging but I see such a randomness in some other parts of KDE-4.11 too: Bug 328023, Bug 317894, random crashes in Plasma after log-in, random freezes after changing Desktop Effects with System Settings. Except for Bug 317894, none of them happened in KDE-4.10. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/44 ------------------------------------------------------------------------ On 2013-12-04T13:44:30+00:00 Manfred-1980 wrote: I have the same problem since updating to Kubuntu 13.10. Since I found the pkill sequence mentioned I use it and it works. But its about 1 of 4 times I start my computer, that akonadi doesn't work. If there is anything I could test, please ask. I dont know if this is related to the problem: Starting Kontact I often get a message, that kmail incoming email filters missing an mail account to use. It shows a window asking to choose the account, but all my accounts are not shown. Either I click ok or esc afterwards the filter is deleted in kmail. I was wondering if that is connected to the problem, that akonadi recources doesn't sucessfully announce its service at the dbus. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/45 ------------------------------------------------------------------------ On 2013-12-06T02:32:26+00:00 Manfred-1980 wrote: I just realized I have another problem, not related to akonadi but to iBus. I use an input method called fcitx for chinese input. After I installed Kubuntu 13.10 it has just the same problem like akonadi- server. It needs to get killed and started again, afterwards just running fine. Which means, this bug might be wrong here. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/47 ------------------------------------------------------------------------ On 2013-12-06T02:37:17+00:00 Manfred-1980 wrote: sorry, I meant dBus, not iBus Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/48 ------------------------------------------------------------------------ On 2013-12-06T09:32:41+00:00 Weigelt-bernd wrote: i see this bug only on one of my systems, my workaround is to kill akonadi_control and akonadiserver, but i have to do this after every reboot. My system is openSUSE 13.1, updated from 12.3 with 'zypper dup' Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/49 ------------------------------------------------------------------------ On 2013-12-07T23:07:12+00:00 Dvratil wrote: Guys, can you please remove (or rename) file /usr/share/dbus-1/services/org.freedesktop.Akonadi.Control.service ? I found out that the auto-start does not work (probably because env is not passed correctly with dbus invocation) and in some cases I believe it could lead to the situation when only akonadi_control and akonadiserver are running with broken dbus services. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/50 ------------------------------------------------------------------------ On 2013-12-08T06:26:09+00:00 Glentadakis Dimitrios wrote: I renamed it but it didn't help The only difference is that now i have a second mysqld process that i have to kill Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/51 ------------------------------------------------------------------------ On 2013-12-08T10:58:46+00:00 Graeme Hewson wrote: Renaming it didn't work for me, either (though Akonadi successfully came up 4 out 5 times). I only had one mysqld process when it failed though, as before. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/52 ------------------------------------------------------------------------ On 2013-12-08T11:08:12+00:00 Manfred-1980 wrote: Same here, renaming didn't change anything. After renaming the first start the problem appeared again. Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/53 ------------------------------------------------------------------------ On 2013-12-10T11:20:36+00:00 Dvratil wrote: *** Bug 328119 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1245979/comments/54 ** Changed in: akonadi Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1245979 Title: After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus session, making kde-pim suit unusable Status in Akonadi - The PIM Storage Service: Unknown Status in “akonadi” package in Ubuntu: Confirmed Bug description: Upon opening Kontact akonadi is supposed to be loaded but fails with the following error: Akonadi fails to register at d-bus session. I safed the self-test protocoll of the akonadi server and attached the report. I already deleted all my akonadi config files but it did not resolve the error. To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/1245979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
