I have 2 laptops using Opensuse KDE (one with 13.1, just updated today and one with still 12.3) both get the following error message after they are finished booting:
Sqlite Database Error: Sqlite Driver is not installed
I did not find anyone having the same issue, which i find strange since I got it one 2 Pcs. Can anybody provide me with a solution?
Could you maybe provide a screenshot?
A bit of context would be nice…
Maybe this comes from Akonadi?
Do you have libqt4-sql-sqlite installed?
Try to switch akonadi to the mysql backend (this is recommended anyway).
kcmshell4 akonadi_server
Thanks for the answer
there we go:
http://i.imgur.com/ys1c30L.jpg
if I test Akonadi it throws an error:
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/jakob/.config/akonadi/akonadiserverrc':
%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-jakob.s2Cxa7/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: /usr/sbin/mysqld Ver 5.5.33-MariaDB for Linux on x86_64 (openSUSE package)
Test 5: SUCCESS
--------
MySQL server log contains no errors.
Details: The MySQL server log file '<a href='/home/jakob/.local/share/akonadi/db_data/mysql.err'>/home/jakob/.local/share/akonadi/db_data/mysql.err</a>' does not contain any errors or warnings.
File content of '/home/jakob/.local/share/akonadi/db_data/mysql.err':
140117 19:45:12 InnoDB: The InnoDB memory heap is disabled
140117 19:45:12 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140117 19:45:12 InnoDB: Compressed tables use zlib 1.2.8
140117 19:45:12 InnoDB: Using Linux native AIO
140117 19:45:12 InnoDB: Initializing buffer pool, size = 80.0M
140117 19:45:12 InnoDB: Completed initialization of buffer pool
140117 19:45:12 InnoDB: highest supported file format is Barracuda.
140117 19:45:13 InnoDB: Waiting for the background threads to start
140117 19:45:14 Percona XtraDB (http://www.percona.com) 5.5.33-MariaDB-31.1 started; log sequence number 1739409
140117 19:45:14 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.33-MariaDB' socket: '/tmp/akonadi-jakob.s2Cxa7/mysql.socket' port: 0 openSUSE package
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 <kris@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)
# Deprecated in MySQL >= 5.6.3
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_open_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/jakob/.local/share/akonadi/mysql.conf'>/home/jakob/.local/share/akonadi/mysql.conf</a> and is readable.
File content of '/home/jakob/.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 <kris@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.10.3
Test 10: 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 11: 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 12: SUCCESS
--------
Nepomuk search service registered at D-Bus.
Details: The Nepomuk search service is registered at D-Bus which typically indicates it is operational.
Test 13: SUCCESS
--------
Nepomuk search service uses an appropriate backend.
Details: The Nepomuk search service uses one of the recommended backends.
Test 14: 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 15: SUCCESS
--------
Resource agents found.
Details: At least one resource agent has been found.
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
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
microblog.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomuktagresource.desktop
newmailnotifieragent.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
sendlateragent.desktop
vcarddirresource.desktop
vcardresource.desktop
Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share:/etc/opt/kde3/share:/opt/kde3/share'
Test 16: SUCCESS
--------
No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.
Test 17: ERROR
--------
Previous Akonadi server error log found.
Details: The Akonadi server reported errors during its previous startup. The log can be found in <a href='/home/jakob/.local/share/akonadi/akonadiserver.error.old'>/home/jakob/.local/share/akonadi/akonadiserver.error.old</a>.
File content of '/home/jakob/.local/share/akonadi/akonadiserver.error.old':
Control process died, committing suicide!
Test 18: SUCCESS
--------
No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.
Test 19: SUCCESS
--------
No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.
Well, that still doesn’t tell much unfortunately.
To find out which program produces that error, I would call “ps aux” in Konsole when that error message appears, then click on “OK”, then run “ps aux” again, and compare the two outputs. (maybe redirect the output to a file with “> filename”, or open two Konsole windows)
Or press CTRL+ESC to see the Activity Monitor. Maybe you see a process disappear when you click on OK?
Does the error message also appear when you start KDE with an empty session?
(Configure Desktop->Startup and Shutdown->Session Management)
if I test Akonadi it throws an error:
No, there is no error.
Akonadi uses mysql and is starting fine.
The only error your post shows is from some previous start.
But did you change anything now in the Akonadi settings? I was just guessing that that SQLite error maybe comes from Akonadi.
Another idea:
Run “xprop” in a Konsole (should be installed by default), the mouse cursor should change to a crosshair then.
Move the mouse cursor over that error dialog and click on it.
Now you should get a lot of information about that window, amongst them to which application it belongs.
Maybe post the whole output if it does not give you a clue.
Here is the Output from
xprop
jakob@linux-hkem:~> xpropx
If 'xpropx' is not a typo you can use command-not-found to lookup the package that contains it, like this:
cnf xpropx
jakob@linux-hkem:~> xprop
_NET_WM_ICON_GEOMETRY(CARDINAL) = 1550, 1048, 253, 32
_KDE_NET_WM_ACTIVITIES(STRING) = "00000000-0000-0000-0000-000000000000"
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE
_KDE_NET_WM_FRAME_STRUT(CARDINAL) = 2, 2, 23, 4
_NET_FRAME_EXTENTS(CARDINAL) = 2, 2, 23, 4
_NET_WM_DESKTOP(CARDINAL) = 1
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 67109004
_NET_WM_STATE(ATOM) = _NET_WM_STATE_MODAL
WM_TRANSIENT_FOR(WINDOW): window id # 0x4000076
_KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 53017
XdndAware(ATOM) = BITMAP
_MOTIF_DRAG_RECEIVER_INFO(_MOTIF_DRAG_RECEIVER_INFO) = 0x6c, 0x0, 0x5, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x10, 0x0, 0x0, 0x0
_NET_WM_NAME(UTF8_STRING) = "Sqlite Database Error!"
WM_CLIENT_LEADER(WINDOW): window id # 0x4000076
_NET_WM_PID(CARDINAL) = 1827
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DIALOG, _NET_WM_WINDOW_TYPE_NORMAL
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x7, 0x24, 0x1a, 0x3, 0x0
WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST
WM_NAME(STRING) = "Sqlite Database Error!"
WM_LOCALE_NAME(STRING) = "C"
WM_CLASS(STRING) = "cav", "Cav"
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
window id # of group leader: 0x4000076
WM_NORMAL_HINTS(WM_SIZE_HINTS):
user specified size: 231 by 91
program specified size: 231 by 91
program specified minimum size: 231 by 91
program specified maximum size: 231 by 91
window gravity: NorthWest
WM_CLIENT_MACHINE(STRING) = "linux-hkem.site"
WM_COMMAND(STRING) = { "./cav", "-d" }
jakob@linux-hkem:~>
JakobAbfalter wrote:
> jakob@linux-hkem:~> xprop
> WM_CLASS(STRING) = “cav”, “Cav”
> WM_COMMAND(STRING) = { “./cav”, “-d” }
So what is ‘cav’?
OK, so the dialog is from a program called “./cav”.
Does that ring a bell?
Seems to be in your home directory and either started by KDE’s session restore, or by something in ~/.config/autostart/, ~/.kde4/Autostart/, ~/.kde4/share/autostart/, or ~/.kde4/env/.
i have never heard of cav, neither can i execute it manually.
I checked all of your listed autostart folders, the only thing in them is dropbox.
JakobAbfalter wrote:
> i have never heard of cav, neither can i execute it manually.
> I checked all of your listed autostart folders, the only thing in them
> is dropbox.
Rereading your original message, you say this happens after booting. So
this is before you attempt to login? There is no user session?
I think I’d try getting a terminal session (perhaps from the console
screen rather than the graphics screen) and then look for a process
running cav. I would type
ps -fe | grep cav
But I’m sure there are better ways to get the information. Once I’d
found the process, I would then chase up the process tree to find what
started it.
Does any file under /var/log mention cav?
cav is Comodo AntiVirus… I get the error message: Sqlite Drive not Installed (like the screan shot provided above) I don’t know how to fix it either and I’m not tech-savvy so you guys have to go slow with me
Ok, I think we are getting a bit closer to the solution now…
Comodo AntiVirus apparently uses Qt4, so make sure Qt4’s sqlite plugin is installed (package libqt4-sql-sqlite in openSUSE).
Although the question still is how did you install CAV?
The openSUSE rpm I found contains its own copy of Qt4.
It seems to be missing the sqlite plugin so you have to contact the developers and report that to them, only they can fix it.
I just tried to install it here, and it seems to work despite that error message though.
Deleting /usr/local/Trolltech/ should get rid of the error message, it uses the system’s Qt4 then.
Or uninstall CAV completely and use something else. But then you don’t really need an anti-virus in Linux, they only check for Windows virii anyway.