Application: kontact (4.4.6) KDE Platform Version: 4.5.1 (KDE 4.5.1) Qt Version: 4.7.0 Operating System: Linux 2.6.35-23-generic x86_64 Distribution: Ubuntu 10.10 -- Information about the crash: - What I was doing when the application crashed: Openening Kmail with nearly full hard disk (about 1.8 GB left). - Unusual behavior I noticed: My Computer isn't usable for about 6 hours (because of high sys-load: 20+); can't close applicaion because of mouse is so laggy; login to tty1-6 is so slow, that login ends in timeout. - Custom settings of the application: sys-load is caused by kmail and akonadi. -using kolab -diconnected imap -few hdd-space -- Backtrace: Application: Kontact (kontact), signal: Bus error [Current thread is 1 (Thread 0x7f10891b2780 (LWP 16142))] Thread 3 (Thread 0x7f1074725710 (LWP 16143)): #0 0x00007f10861ef203 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007f107ef62009 in ?? () from /lib/libglib-2.0.so.0 #2 0x00007f107ef627b5 in g_main_loop_run () from /lib/libglib-2.0.so.0 #3 0x00007f1074e5c0f4 in ?? () from /usr/lib/libgio-2.0.so.0 #4 0x00007f107ef877e4 in ?? () from /lib/libglib-2.0.so.0 #5 0x00007f10812f1971 in start_thread (arg=<value optimized out>) at pthread_create.c:304 #6 0x00007f10861fb94d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x0000000000000000 in ?? () Thread 2 (Thread 0x7f1045fed710 (LWP 16491)): #0 0xffffffffff60017b in ?? () #1 0x00007f1045feca70 in ?? () #2 0x00007fff14bda852 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0x7f10891b2780 (LWP 16142)): [KCrash Handler] #6 memcpy () at ../sysdeps/x86_64/memcpy.S:67 #7 0x00007f1086e7c98c in KSharedDataCache::insert (this=0x195f6e0, key=<value optimized out>, data=<value optimized out>) at /usr/include/bits/string3.h:52 #8 0x00007f1087fbdb96 in KIconLoaderPrivate::insertCachedPixmapWithPath (this=0x1961070, key=..., data=..., path=<value optimized out>) at ../../kdeui/icons/kiconloader.cpp:835 #9 0x00007f1087fc5498 in KIconLoader::loadIcon (this=0x195ffa0, _name=<value optimized out>, group=KIconLoader::NoGroup, size=64, state=0, overlays=..., path_store=0x0, canReturnNull=true) at ../../kdeui/icons/kiconloader.cpp:1306 #10 0x00007f1087f7d07b in themedMessageBoxIcon (dialog=<value optimized out>, icon=QMessageBox::Critical, text=<value optimized out>, strlist=<value optimized out>, ask=..., checkboxReturn=0x0, options=..., details=...) at ../../kdeui/dialogs/kmessagebox.cpp:102 #11 KMessageBox::createKMessageBox (dialog=<value optimized out>, icon=QMessageBox::Critical, text=<value optimized out>, strlist=<value optimized out>, ask=..., checkboxReturn=0x0, options=..., details=...) at ../../kdeui/dialogs/kmessagebox.cpp:152 #12 0x00007f1087f7ddd0 in KMessageBox::errorListWId (parent_id=0, text=..., strlist=..., caption=..., options=) at ../../kdeui/dialogs/kmessagebox.cpp:847 #13 0x00007f1087f7dfe2 in KMessageBox::error (parent=<value optimized out>, text=..., caption=..., options=<value optimized out>) at ../../kdeui/dialogs/kmessagebox.cpp:814 #14 0x00007f105f1edf97 in KMKernel::emergencyExit(QString const&) () from /usr/lib/libkmailprivate.so.4 #15 0x00007f105f1c9ace in ?? () from /usr/lib/libkmailprivate.so.4 #16 0x00007f105f1b36fe in ?? () from /usr/lib/libkmailprivate.so.4 #17 0x00007f105f2dd143 in ?? () from /usr/lib/libkmailprivate.so.4 #18 0x00007f105f2dee3e in ?? () from /usr/lib/libkmailprivate.so.4 #19 0x00007f108691eb27 in QMetaObject::activate (sender=0x2a894e20, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x24) at kernel/qobject.cpp:3280 #20 0x00007f1086d5c712 in KJob::result (this=0x7f1068b68000, _t1=0x2a894e20) at ./kjob.moc:194 #21 0x00007f1086d5c9b0 in KJob::emitResult (this=0x2a894e20) at ../../kdecore/jobs/kjob.cpp:312 #22 0x00007f1084d10203 in KIO::SimpleJob::slotFinished (this=0x2a894e20) at ../../kio/kio/job.cpp:522 #23 0x00007f1084d10af7 in KIO::TransferJob::slotFinished (this=0x2a894e20) at ../../kio/kio/job.cpp:1111 #24 0x00007f1084d0ea41 in KIO::TransferJob::qt_metacall (this=0x2a894e20, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff14b33e00) at ./jobclasses.moc:367 #25 0x00007f108691eb27 in QMetaObject::activate (sender=0x2b5b8710, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x24) at kernel/qobject.cpp:3280 #26 0x00007f1084dbfc8e in KIO::SlaveInterface::dispatch (this=0x2b5b8710, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175 #27 0x00007f1084dbccc3 in KIO::SlaveInterface::dispatch (this=0x2b5b8710) at ../../kio/kio/slaveinterface.cpp:91 #28 0x00007f1084db0876 in KIO::Slave::gotInput (this=0x2b5b8710) at ../../kio/kio/slave.cpp:344 #29 0x00007f1084db0a5c in KIO::Slave::qt_metacall (this=0x2b5b8710, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff14b34240) at ./slave.moc:82 #30 0x00007f108691eb27 in QMetaObject::activate (sender=0xecd4a70, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x24) at kernel/qobject.cpp:3280 #31 0x00007f1084cdcdf7 in KIO::ConnectionPrivate::dequeue (this=0x2be4bcf0) at ../../kio/kio/connection.cpp:82 #32 0x00007f1084cdcf1d in KIO::Connection::qt_metacall (this=0xecd4a70, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x2b7c3c20) at ./connection.moc:79 #33 0x00007f1086918bde in QObject::event (this=0xecd4a70, e=0x7f1068b68000) at kernel/qobject.cpp:1219 #34 0x00007f10872bcfdc in QApplicationPrivate::notify_helper (this=0x17173f0, receiver=0xecd4a70, e=0x25b53c00) at kernel/qapplication.cpp:4396 #35 0x00007f10872c2aed in QApplication::notify (this=0x7fff14b34d50, receiver=0xecd4a70, e=0x25b53c00) at kernel/qapplication.cpp:4277 #36 0x00007f108800f156 in KApplication::notify (this=0x7fff14b34d50, receiver=0xecd4a70, event=0x25b53c00) at ../../kdeui/kernel/kapplication.cpp:310 #37 0x00007f1086906cdc in QCoreApplication::notifyInternal (this=0x7fff14b34d50, receiver=0xecd4a70, event=0x25b53c00) at kernel/qcoreapplication.cpp:732 #38 0x00007f1086909c22 in sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x16e9380) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #39 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x16e9380) at kernel/qcoreapplication.cpp:1373 #40 0x00007f1086933653 in sendPostedEvents (s=0x171c2a0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #41 postEventSourceDispatch (s=0x171c2a0) at kernel/qeventdispatcher_glib.cpp:277 #42 0x00007f107ef5e342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #43 0x00007f107ef622a8 in ?? () from /lib/libglib-2.0.so.0 #44 0x00007f107ef6245c in g_main_context_iteration () from /lib/libglib-2.0.so.0 #45 0x00007f1086933193 in QEventDispatcherGlib::processEvents (this=0x16e8e90, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415 #46 0x00007f108736fa4e in QGuiEventDispatcherGlib::processEvents (this=0x7f1068b68000, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #47 0x00007f1086905a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #48 0x00007f1086905dec in QEventLoop::exec (this=0x7fff14b34c90, flags=) at kernel/qeventloop.cpp:201 #49 0x00007f1086909ebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #50 0x0000000000403b4e in _start () This bug may be a duplicate of or related to bug 259347. Possible duplicates by query: bug 259347. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 259347 ***
Created attachment 54474 [details] New crash information added by DrKonqi kontact (4.4.6) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0 - What I was doing when the application crashed: previosly had 1.8 GB HDD left (was compleatly full after last kmail start); now cleaned up hard disked: free space before start of kmail (5.5GB) started kontakt (kmail): kmail started in about 10 minutes: free space: 5.1GB. --> HardDisk is not the reason! Now KMail seams to work, but does not fetch new mails! --> So I tried rebuilding IMAP-Cache: KMail did somthing (dont know what): status: "Uploading messages...." toggeled between 5 & 15 % but 'never' get finisched! Finaly Kontact Crashed. - Unusual behavior I noticed: *High load while opening Kontact! (laggy mouse). *KMail did somthing (dont know what): status: "Uploading messages...." toggeled between 5 & 15 % but 'never' get finisched! *Scrollbars in Kontact look usual, but on clicking them they become very small, but still have "collision" from the big ones. -- Backtrace (Reduced): #7 0x00007fbe94c6cf97 in KMail::FolderViewItem::updateCounts (this=0x16d11390) at ../../kmail/folderview.cpp:2849 #8 0x00007fbe94c6d41e in KMail::FolderView::updateCountsForChildren (this=0x16cb9bc0, it=0x16d21010, tStart=...) at ../../kmail/folderview.cpp:871 #9 0x00007fbe94c6d3dc in KMail::FolderView::updateCountsForChildren (this=0x16cb9bc0, it=0x16d1d1f0, tStart=...) at ../../kmail/folderview.cpp:843 #10 0x00007fbe94c6d3dc in KMail::FolderView::updateCountsForChildren (this=0x16cb9bc0, it=0x16cbc7f0, tStart=...) at ../../kmail/folderview.cpp:843 #11 0x00007fbe94c6d4bf in KMail::FolderView::slotUpdateCounts (this=0x16cb9bc0) at ../../kmail/folderview.cpp:904
************************************************ AKONADI_SELFTEST ************************************************ 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/christian/.config/akonadi/akonadiserverrc': [Debug] Tracer=null [QMYSQL] Name=akonadi Host= Options="UNIX_SOCKET=/home/christian/.local/share/akonadi/db_misc/mysql.socket" ServerPath=/usr/sbin/mysqld-akonadi StartServer=true 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-akonadi'. 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-akonadi Ver 5.1.48-1ubuntu4 for debian-linux-gnu on x86_64 ((Ubuntu)) Test 5: ERROR -------- MySQL server log contains errors. Details: The MySQL server error log file '<a href='/home/christian/.local/share/akonadi/db_data/mysql.err'>/home/christian/.local/share/akonadi/db_data/mysql.err</a>' contains errors. File content of '/home/christian/.local/share/akonadi/db_data/mysql.err': 101212 22:22:55 [Note] Plugin 'FEDERATED' is disabled. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. 101212 22:22:55 InnoDB: Retrying to lock the first data file InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. 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] skip_grant_tables skip_networking # 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 # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # case-insensitive table names, avoids trouble on windows lower_case_table_names=1 character_set_server=utf8 collation_server=utf8_general_ci 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_queries=mysql.slow #long_query_time=1 # log queries not using indices, debug only, disable for production use #log_queries_not_using_indexes=1 # maximum blob size max_allowed_packet=32M 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_file_per_table=1 innodb_log_buffer_size=1M innodb_additional_mem_pool_size=1M # messure database size and adjust # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema"); innodb_buffer_pool_size=80M # size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables) innodb_log_file_size=64M innodb_flush_log_at_trx_commit=2 # Do not drop the connection to the DB after 8 hours of inactivity wait_timeout=1296000 [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/christian/.local/share/akonadi/mysql.conf'>/home/christian/.local/share/akonadi/mysql.conf</a> and is readable. File content of '/home/christian/.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] skip_grant_tables skip_networking # 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 # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # case-insensitive table names, avoids trouble on windows lower_case_table_names=1 character_set_server=utf8 collation_server=utf8_general_ci 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_queries=mysql.slow #long_query_time=1 # log queries not using indices, debug only, disable for production use #log_queries_not_using_indexes=1 # maximum blob size max_allowed_packet=32M 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_file_per_table=1 innodb_log_buffer_size=1M innodb_additional_mem_pool_size=1M # messure database size and adjust # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema"); innodb_buffer_pool_size=80M # size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables) innodb_log_file_size=64M innodb_flush_log_at_trx_commit=2 # Do not drop the connection to the DB after 8 hours of inactivity wait_timeout=1296000 [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.4.0 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 /usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share/gnome:/usr/local/share/:/usr/share/'; make sure this includes all paths where Akonadi agents are installed. Directory listing of '/usr/share/akonadi/agents': birthdaysresource.desktop contactsresource.desktop icalresource.desktop imapresource.desktop kabcresource.desktop kcalresource.desktop knutresource.desktop kolabproxyresource.desktop localbookmarksresource.desktop maildirresource.desktop maildispatcheragent.desktop mboxresource.desktop microblog.desktop mtdummyresource.desktop nepomukcalendarfeeder.desktop nepomukcontactfeeder.desktop nepomuktagresource.desktop nntpresource.desktop notesresource.desktop pop3resource.desktop vcarddirresource.desktop vcardresource.desktop Directory listing of '/usr/share/akonadi/agents': birthdaysresource.desktop contactsresource.desktop icalresource.desktop imapresource.desktop kabcresource.desktop kcalresource.desktop knutresource.desktop kolabproxyresource.desktop localbookmarksresource.desktop maildirresource.desktop maildispatcheragent.desktop mboxresource.desktop microblog.desktop mtdummyresource.desktop nepomukcalendarfeeder.desktop nepomukcontactfeeder.desktop nepomuktagresource.desktop nntpresource.desktop notesresource.desktop pop3resource.desktop vcarddirresource.desktop vcardresource.desktop Environment variable XDG_DATA_DIRS is set to '/usr/share/gnome:/usr/local/share/:/usr/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: 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/christian/.local/share/akonadi/akonadiserver.error.old'>/home/christian/.local/share/akonadi/akonadiserver.error.old</a>. File content of '/home/christian/.local/share/akonadi/akonadiserver.error.old': Database error: Cannot open database. Last driver error: "QMYSQL: Unable to connect" Last database error: "Access denied for user 'christian'@'localhost' (using password: NO)" Unable to open database "Access denied for user 'christian'@'localhost' (using password: NO) QMYSQL: Unable to connect" "[ 0: akonadiserver(_Z11akBacktracev+0x39) [0x40af99] 1: akonadiserver() [0x40b4ea] 2: /lib/libc.so.6(+0x33c20) [0x7f5d30575c20] 3: /lib/libc.so.6(gsignal+0x35) [0x7f5d30575ba5] 4: /lib/libc.so.6(abort+0x180) [0x7f5d305796b0] 5: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7f5d31758864] 6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xa8) [0x40c5d8] 7: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x77) [0x7f5d317ea4a7] 8: /usr/lib/libQtCore.so.4(+0x10ba59) [0x7f5d317f7a59] 9: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x39) [0x7f5d317f8c69] 10: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x5e3) [0x7f5d31be6cf3] 11: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8instanceEv+0x4a) [0x7f5d31be81ea] 12: akonadiserver(main+0x404) [0x405df4] 13: /lib/libc.so.6(__libc_start_main+0xfe) [0x7f5d30560d8e] 14: akonadiserver() [0x4058f9] ] " 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. ************************************************ mysql.err (LOG) ************************************************ 101212 22:25:07 [Note] Plugin 'FEDERATED' is disabled. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. 101212 22:25:08 InnoDB: Retrying to lock the first data file InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. ************************************************ akonadiserver.error.old ************************************************ Database error: Cannot open database. Last driver error: "QMYSQL: Unable to connect" Last database error: "Access denied for user 'christian'@'localhost' (using password: NO)" Unable to open database "Access denied for user 'christian'@'localhost' (using password: NO) QMYSQL: Unable to connect" "[ 0: akonadiserver(_Z11akBacktracev+0x39) [0x40af99] 1: akonadiserver() [0x40b4ea] 2: /lib/libc.so.6(+0x33c20) [0x7ffaba6b7c20] 3: /lib/libc.so.6(gsignal+0x35) [0x7ffaba6b7ba5] 4: /lib/libc.so.6(abort+0x180) [0x7ffaba6bb6b0] 5: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7ffabb89a864] 6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xa8) [0x40c5d8] 7: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x77) [0x7ffabb92c4a7] 8: /usr/lib/libQtCore.so.4(+0x10ba59) [0x7ffabb939a59] 9: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x39) [0x7ffabb93ac69] 10: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x5e3) [0x7ffabbd28cf3] 11: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8instanceEv+0x4a) [0x7ffabbd2a1ea] 12: akonadiserver(main+0x404) [0x405df4] 13: /lib/libc.so.6(__libc_start_main+0xfe) [0x7ffaba6a2d8e] 14: akonadiserver() [0x4058f9] ] " -------------------------------------------------------------------------------------------------------------------------------- sorry for adding files this strange way, but i could not find an option to attach files :(
ok - I'm happy again - the problem is solved ---------------------------- but i can't tell ya what the problem was i can tell you, what i have done. 1 . reinstalled all kde packages > problem remained 2. deleted ~/.kde 3.reconfigured >problem remained 4.used kmail in another user-context (same settings) >problem seemed resolved >>but retured partially (fetching new mail failed after some time) 5. migrated to old user-context >reinstalled all kde-packages >deleted all mysql files >installed all libstdc++ from distribution (previously using modified ones) !!!!!!! >reinstalled mysql >reconfigured >the akonadi-error-report remains, but everything is working fine --> kontact works fine again; no more load problem (!!!) because of my buggy libstdc++ packages i think there is _NO_ bug in kmail / kontact. (expect the bug with full hard disk?) Changed to "CLOSED" because of my stupidity (libstdc++) regarding to the title-topic "high-sys-load".