KDE broken after dist-upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdebase (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
I've just upgraded KDE from Kubuntu's default repositories (ran sudo apt-get dist-upgrade) and now KDE Is completely broken. The session doesn't have a panel, there are no plasmoids and the right-click menu on the desktop doesn't open a right-click menu. Then I log into KDE the first thing that pops up is Akonadi error message, which displays a error log whose report I'll paste below:
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/
[%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload
[QMYSQL]
Name=akonadi
User=
Password=
Options=
ServerPath=
StartServer=true
Host=
[Debug]
Tracer=null
Test 2: SUCCESS
--------
MySQL server found.
Details: You currently have configured Akonadi to use the MySQL server '/usr/sbin/
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 locations varies depending on the distribution.
Test 3: SUCCESS
--------
MySQL server is executable.
Details: MySQL server found: /usr/sbin/
Test 4: ERROR
--------
MySQL server log contains errors.
Details: The MySQL server error log file '<a href='/
File content of '/home/
100219 14:59:24 [Note] Plugin 'FEDERATED' is disabled.
100219 14:59:27 InnoDB: Started; log sequence number 0 1812182
100219 14:59:27 [Warning] Can't open and lock time zone table: Table 'mysql.
100219 14:59:27 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
100219 14:59:27 [ERROR] Cannot open mysql.db
100219 14:59:27 [ERROR] Cannot open mysql.user
100219 14:59:27 [ERROR] Cannot open mysql.event
100219 14:59:27 [ERROR] Event Scheduler: An error occurred when initializing system tables.
100219 14:59:27 [Note] /usr/sbin/
Version: '5.1.37-
Test 5: SUCCESS
--------
MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/
File content of '/etc/akonadi/
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.
#
# Based on advice by Kris Köhntopp <email address hidden>
#
[mysqld]
skip_grant_tables
skip_networking
# strict query parsing/
# TODO: make Akonadi work with those settings enabled
#sql_mode=
#sql_mode=
# use InnoDB for transactions and better crash recovery
default_
# case-insensitive table names, avoids trouble on windows
lower_case_
character_
collation_
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# 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_
#long_query_time=1
# log queries not using indices, debug only, disable for production use
#log_queries_
# maximum blob size
max_allowed_
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0
innodb_
innodb_
innodb_
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_
innodb_
# size of average write burst, keep Innob_log_waits small, keep Innodb_
innodb_
innodb_
Test 6: SKIP
--------
MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.
Test 7: SUCCESS
--------
MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/
File content of '/home/
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.
#
# Based on advice by Kris Köhntopp <email address hidden>
#
[mysqld]
skip_grant_tables
skip_networking
# strict query parsing/
# TODO: make Akonadi work with those settings enabled
#sql_mode=
#sql_mode=
# use InnoDB for transactions and better crash recovery
default_
# case-insensitive table names, avoids trouble on windows
lower_case_
character_
collation_
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# 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_
#long_query_time=1
# log queries not using indices, debug only, disable for production use
#log_queries_
# maximum blob size
max_allowed_
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0
innodb_
innodb_
innodb_
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_
innodb_
# size of average write burst, keep Innob_log_waits small, keep Innodb_
innodb_
innodb_
Test 8: SUCCESS
--------
akonadictl found and usable
Details: The program '/usr/bin/
Result:
Akonadi 1.3.1
Test 9: SUCCESS
--------
Akonadi control process registered at D-Bus.
Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational.
Test 10: SUCCESS
--------
Akonadi server process registered at D-Bus.
Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational.
Test 11: 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 12: SUCCESS
--------
Server protocol version is recent enough.
Details: The server Protocol version is 23, which equal or newer than the required version 23.
Test 13: 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/
Directory listing of '/usr/share/
birthdaysresour
contactsresourc
icalresource.
imapresource.
kabcresource.
kcalresource.
knutresource.
kolabproxyresou
localbookmarksr
maildirresource
maildispatchera
mboxresource.
microblog.desktop
mtdummyresource
nepomukcalendar
nepomukcontactf
nepomuktagresou
nntpresource.
notesresource.
pop3resource.
vcarddirresourc
vcardresource.
Directory listing of '/usr/share/
birthdaysresour
contactsresourc
icalresource.
imapresource.
kabcresource.
kcalresource.
knutresource.
kolabproxyresou
localbookmarksr
maildirresource
maildispatchera
mboxresource.
microblog.desktop
mtdummyresource
nepomukcalendar
nepomukcontactf
nepomuktagresou
nntpresource.
notesresource.
pop3resource.
vcarddirresourc
vcardresource.
Environment variable XDG_DATA_DIRS is set to '/usr/share:
Test 14: SUCCESS
--------
No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.
Test 15: ERROR
--------
Previous Akonadi server error log found.
Details: The Akonadi server did report error during its previous startup into <a href='/
File content of '/home/
Control process died, committing suicide!
Test 16: SUCCESS
--------
No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.
Test 17: ERROR
--------
Previous Akonadi control error log found.
Details: The Akonadi control process did report error during its previous startup into <a href='/
File content of '/home/
D-Bus session bus went down - quitting
It appears that this problem was caused by a botched upgrade to KDE 4.4.0.