Hi there! Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.
Thanks! ** Changed in: akonadi (Ubuntu) Status: New => Invalid -- 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/1095429 Title: kontact unusable after kmail crashed trying to show emails Status in “akonadi” package in Ubuntu: Invalid Bug description: I am running Kubuntu 12.10 and KDE 4.9.3. The other day I opened Kmail and when I clicked on each email folders to see my emails, Kmail crashed saying there were no items. I restarted Kontact and the defined email accounts and mail folders were gone. It seems the internal database had been erased and Akonadi Server is not able to start anymore, with the following errors: * akonadiserver.error: Database process exited unexpectedly during initial connection! executable: "/usr/sbin/mysqld-akonadi" arguments: ("--defaults-file=/home/fran/.local/share/akonadi/mysql.conf", "--datadir=/home/fran/.local/share/akonadi/db_data/", "--socket=/home/fran/.local/share/akonadi/socket-fran-Inspiron-6000/mysql.socket") stdout: "" stderr: "" exit code: 1 process error: "Process operation timed out" "[ 0: akonadiserver() [0x805c635] 1: akonadiserver() [0x805c97a] 2: [0xb770e400] 3: [0xb770e424] 4: /lib/i386-linux-gnu/libc.so.6(gsignal+0x4f) [0xb6de51df] 5: /lib/i386-linux-gnu/libc.so.6(abort+0x175) [0xb6de8825] 6: /usr/lib/i386-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x13c) [0xb746b72c] 7: akonadiserver() [0x805e8f8] 8: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xe8) [0xb7513ed8] 9: /usr/lib/i386-linux-gnu/libQtCore.so.4(+0x11112d) [0xb752012d] 10: /usr/lib/i386-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3e) [0xb752937e] 11: akonadiserver() [0x80d3be2] 12: akonadiserver() [0x805f6b1] 13: akonadiserver() [0x8060646] 14: akonadiserver() [0x8061c96] 15: akonadiserver() [0x80559da] 16: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0xb6dd04d3] 17: akonadiserver() [0x8056481] ] " * mysql.error: 121225 21:17:13 [Note] Plugin 'FEDERATED' is disabled. 121225 21:17:13 InnoDB: The InnoDB memory heap is disabled 121225 21:17:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121225 21:17:13 InnoDB: Compressed tables use zlib 1.2.7 121225 21:17:13 InnoDB: Using Linux native AIO 121225 21:17:13 InnoDB: Initializing buffer pool, size = 80.0M 121225 21:17:13 InnoDB: Completed initialization of buffer pool 121225 21:17:13 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 3654932040 121225 21:17:13 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 3655530216 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is A29B00 121225 21:17:14 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 1594, file name ./mysql-bin.000199 121225 21:17:14 InnoDB: Waiting for the background threads to start InnoDB: Starting in background the rollback of uncommitted transactions 121225 21:17:14 InnoDB: Rolling back trx with id A299D6, 1 rows to undo 121225 21:17:14 InnoDB: Assertion failure in thread 2876242752 in file fut0lst.ic line 83 InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 20:17:14 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8388608 read_buffer_size=131072 max_used_connections=0 max_threads=256 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 567120 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x33)[0xb7308e53] /usr/sbin/mysqld(handle_fatal_signal+0x48c)[0xb71ad55c] [0xb6e7b400] /usr/sbin/mysqld(+0x5af939)[0xb744d939] /usr/sbin/mysqld(+0x533dd7)[0xb73d1dd7] /usr/sbin/mysqld(+0x548472)[0xb73e6472] /usr/sbin/mysqld(+0x546b21)[0xb73e4b21] /usr/sbin/mysqld(+0x547003)[0xb73e5003] /usr/sbin/mysqld(+0x53c421)[0xb73da421] /usr/sbin/mysqld(+0x5f37e4)[0xb74917e4] /usr/sbin/mysqld(+0x5f3947)[0xb7491947] /usr/sbin/mysqld(+0x53df5c)[0xb73dbf5c] /usr/sbin/mysqld(+0x53e629)[0xb73dc629] /lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb6e49d4c] /lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb6bedd3e] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1095429/+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