[kmail2] [Bug 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 Clemens John clemens-j...@gmx.de changed: What|Removed |Added CC||clemens-j...@gmx.de -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 326185] New: KONTACT Crash when sending mail from Libre Office
https://bugs.kde.org/show_bug.cgi?id=326185 Bug ID: 326185 Summary: KONTACT Crash when sending mail from Libre Office Classification: Unclassified Product: kontact Version: 4.11.2 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: awbho...@gmail.com Application: kontact (4.11.2) KDE Platform Version: 4.11.2 (Compiled from sources) Qt Version: 4.8.4 Operating System: Linux 3.11.0-12-generic i686 Distribution: Ubuntu 13.10 -- Information about the crash: - What I was doing when the application crashed: I was trying to email a document from Libre Office Writer. Email was created, written and send clicked. No report of 'sent mail' and then Kontact crashed. Using Kubuntu 13.10 The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb16ce740 (LWP 3352))] Thread 5 (Thread 0xaefa5b40 (LWP 3353)): #0 0xb7718424 in __kernel_vsyscall () #1 0xb31eb84b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb60aa9bc in __pthread_cond_wait (cond=0xb583cd90, mutex=0xb583cd78) at forward.c:149 #3 0xb4fc2a7c in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb4fc2acf in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb31e7d78 in start_thread (arg=0xaefa5b40) at pthread_create.c:311 #6 0xb609d01e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 4 (Thread 0xae67cb40 (LWP 3354)): #0 0xb7718424 in __kernel_vsyscall () #1 0xb31eb84b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb60aa9bc in __pthread_cond_wait (cond=0xae6ea7dc, mutex=0xae6ea7c4) at forward.c:149 #3 0xb4ff1ae3 in WTF::ThreadCondition::wait(WTF::Mutex) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb4ccd744 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb4fd8866 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #6 0xb4ff1459 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #7 0xb31e7d78 in start_thread (arg=0xae67cb40) at pthread_create.c:311 #8 0xb609d01e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 3 (Thread 0xabbd9b40 (LWP 3357)): #0 0xb31e9de3 in __GI___pthread_mutex_lock (mutex=0xab200558) at pthread_mutex_lock.c:95 #1 0xb60aabc4 in pthread_mutex_lock (mutex=0xab200558) at forward.c:192 #2 0xb314cba0 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb3109b08 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb3109c98 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb63ee8df in QEventDispatcherGlib::processEvents (this=0xab200468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0xb63bd9f3 in QEventLoop::processEvents (this=this@entry=0xabbd9228, flags=...) at kernel/qeventloop.cpp:149 #7 0xb63bdd19 in QEventLoop::exec (this=this@entry=0xabbd9228, flags=...) at kernel/qeventloop.cpp:204 #8 0xb62ace3d in QThread::exec (this=this@entry=0x928ac98) at thread/qthread.cpp:542 #9 0xb639de14 in QInotifyFileSystemWatcherEngine::run (this=0x928ac98) at io/qfilesystemwatcher_inotify.cpp:265 #10 0xb62af72f in QThreadPrivate::start (arg=0x928ac98) at thread/qthread_unix.cpp:338 #11 0xb31e7d78 in start_thread (arg=0xabbd9b40) at pthread_create.c:311 #12 0xb609d01e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 2 (Thread 0xab030b40 (LWP 3368)): #0 0xb314cba0 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb310958b in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb3109aea in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb3109c98 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb63ee8df in QEventDispatcherGlib::processEvents (this=0x8e77528, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0xb63bd9f3 in QEventLoop::processEvents (this=this@entry=0xab030258, flags=...) at kernel/qeventloop.cpp:149 #6 0xb63bdd19 in QEventLoop::exec (this=this@entry=0xab030258, flags=...) at kernel/qeventloop.cpp:204 #7 0xb62ace3d in QThread::exec (this=this@entry=0x8f09f28) at thread/qthread.cpp:542 #8 0xb62acf8b in QThread::run (this=0x8f09f28) at thread/qthread.cpp:609 #9 0xb62af72f in QThreadPrivate::start (arg=0x8f09f28) at thread/qthread_unix.cpp:338 #10 0xb31e7d78 in start_thread (arg=0xab030b40) at pthread_create.c:311 #11 0xb609d01e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 1 (Thread 0xb16ce740 (LWP 3352)): [KCrash Handler] #7 QString (other=..., this=0xc6e3090) at /usr/include/qt4/QtCore/qstring.h:725 #8 Mailbox (this=0xc6e3090) at
[kmail2] [Bug 321186] kmail doesn't filter the message, once a month
https://bugs.kde.org/show_bug.cgi?id=321186 Clemens John clemens-j...@gmx.de changed: What|Removed |Added CC||clemens-j...@gmx.de -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 322126] emails get filtered twice and thus duplicated in kmail2
https://bugs.kde.org/show_bug.cgi?id=322126 Clemens John clemens-j...@gmx.de changed: What|Removed |Added CC||clemens-j...@gmx.de -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 281797] kmail2/akonadi handels maildir incorrect
https://bugs.kde.org/show_bug.cgi?id=281797 Marc Mezzarobba m...@mezzarobba.net changed: What|Removed |Added CC||m...@mezzarobba.net -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 326188] New: Akonadi server fails to start when home is in AFS on KDE 4.8.5, Kubuntu 12.04 amd64
https://bugs.kde.org/show_bug.cgi?id=326188 Bug ID: 326188 Summary: Akonadi server fails to start when home is in AFS on KDE 4.8.5, Kubuntu 12.04 amd64 Classification: Unclassified Product: Akonadi Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: u1...@hushmail.com Hi, Akonadi server fails to start on Kubuntu 12.04 amd64 when I try to start KMail and home is in AFS. First I thougt that the folders ~/.config/akonadi and ~/.local/share/akonadi might need to be outside of AFS so I moved them to the local hard drive and added symbolic links, but the problem is still the same. When looking at the akonadi-selftest-report log the problem seem to start at Test 10 which says Akonadi control process not registered at D-Bus.. I would appreciate any hints on how to dig further into the problem to try to solve it, e.g. how do I try to run some of the steps manually with more verbose logging of what goes wrong? 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 '/afs/mydomain/myuser/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL [QMYSQL] Name=akonadi Host= Options=UNIX_SOCKET=/afs/mydomain/myuser/.local/share/akonadi/socket-ledig/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 Ver 5.5.32-0ubuntu0.12.04.1 for debian-linux-gnu on x86_64 ((Ubuntu)) Test 5: SUCCESS No current MySQL error log found. Details: The MySQL server did not report any errors during this startup. The log can be found in '/afs/mydomain/myuser/.local/share/akonadi/db_data/mysql.err'. 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,str ict_error_for_division_by_zero,no_auto_create_user ,no_auto_value_on_zero,no_engine_substitution,no_z ero_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
[Akonadi] [Bug 326188] Akonadi server fails to start when home is in AFS on KDE 4.8.5, Kubuntu 12.04 amd64
https://bugs.kde.org/show_bug.cgi?id=326188 Daniel Vrátil dvra...@redhat.com changed: What|Removed |Added CC||dvra...@redhat.com --- Comment #1 from Daniel Vrátil dvra...@redhat.com --- Could you please verify whether file /afs/mydomain/myuser/.local/share/akonadi/mysql.conf exists and whether it's readable? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 310700] Multiple actions in one filter not applied correctly
https://bugs.kde.org/show_bug.cgi?id=310700 Nick Leverton n...@leverton.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Nick Leverton n...@leverton.org --- Seems to be fixed in 4.11.2, thankyou. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 314123] KMail crash whilst idle
https://bugs.kde.org/show_bug.cgi?id=314123 --- Comment #14 from Lastique andy...@mail.ru --- Created attachment 82920 -- https://bugs.kde.org/attachment.cgi?id=82920action=edit New crash information added by DrKonqi kmail (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.4 - What I was doing when the application crashed: I was working with other applications, KMail was idle, minimized to the tray icon. -- Backtrace (Reduced): #6 0x7f1f9a04ff77 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x7f1f9a0535e8 in __GI_abort () at abort.c:90 [...] #9 0x7f1f9a06 in malloc_printerr (ptr=0x26a8cc0, str=0x7f1f9a19d232 invalid fastbin entry (free), action=3) at malloc.c:4923 #10 _int_free (av=optimized out, p=0x26a8cb0, have_lock=0) at malloc.c:3779 #11 0x7f1f9b670428 in QString::free (d=0x26a8cc0) at tools/qstring.cpp:1235 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 314123] KMail crash whilst idle
https://bugs.kde.org/show_bug.cgi?id=314123 Lastique andy...@mail.ru changed: What|Removed |Added CC||andy...@mail.ru -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 316107] big regression: kmail IMAP connection and message display problems
https://bugs.kde.org/show_bug.cgi?id=316107 --- Comment #26 from Joerg Mertin kdebugs...@solsys.org --- @John Thx. Already had checked it out. Both seem to be linked, however there is no fix available as of now. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 323696] Kmail crashes when trying to display a PGP encrypted message
https://bugs.kde.org/show_bug.cgi?id=323696 --- Comment #7 from sean_mccu...@yahoo.com --- Created attachment 82922 -- https://bugs.kde.org/attachment.cgi?id=82922action=edit New crash information added by DrKonqi kmail (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.5 - What I was doing when the application crashed: Trying to display PGP Encrypted Message, after entering Passphrase KMail crashed. This does not happen everytime. -- Backtrace (Reduced): #6 0x003280e44174 in KMime::Content::parent (this=this@entry=0x4f3b2d0) at /usr/src/debug/kdepimlibs-4.11.2/kmime/kmime_content.cpp:953 #7 0x00328a83b4d7 in MessageCore::NodeHelper::nextSibling (node=node@entry=0x4f3b2d0) at /usr/src/debug/kdepim-4.11.2/messagecore/helpers/nodehelper.cpp:32 #8 0x0032898a5e47 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=this@entry=0x7fff58f2a1b0, node=node@entry=0x4f3b2d0) at /usr/src/debug/kdepim-4.11.2/messageviewer/viewer/objecttreeparser.cpp:296 #9 0x0032898a79c9 in MessageViewer::ObjectTreeParser::parseObjectTree (this=this@entry=0x7fff58f2a1b0, node=node@entry=0x4f3b2d0) at /usr/src/debug/kdepim-4.11.2/messageviewer/viewer/objecttreeparser.cpp:266 #10 0x0032898d5b9b in MessageViewer::ViewerPrivate::parseContent (this=this@entry=0xedc5c0, content=0x4f3b2d0) at /usr/src/debug/kdepim-4.11.2/messageviewer/viewer/viewer_p.cpp:1007 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 323696] Kmail crashes when trying to display a PGP encrypted message
https://bugs.kde.org/show_bug.cgi?id=323696 sean_mccu...@yahoo.com changed: What|Removed |Added CC||sean_mccu...@yahoo.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 311910] kontact segfaults on exit
https://bugs.kde.org/show_bug.cgi?id=311910 Maarten Bezemer maarten.beze...@gmail.com changed: What|Removed |Added CC||maarten.beze...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 311910] kontact segfaults on exit
https://bugs.kde.org/show_bug.cgi?id=311910 --- Comment #2 from Maarten Bezemer maarten.beze...@gmail.com --- Created attachment 82923 -- https://bugs.kde.org/attachment.cgi?id=82923action=edit New crash information added by DrKonqi kontact (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.4 - What I was doing when the application crashed: I quit KMail as I had to restart it to load newly installed dictionary It happened on a freshly installed Kuuntu 13.10 -- Backtrace (Reduced): #7 0x004036a6 in qDeleteAllQListKMainWindow*::const_iterator (end=..., begin=...) at /usr/include/qt4/QtCore/qalgorithms.h:322 #8 qDeleteAllQListKMainWindow* (c=...) at /usr/include/qt4/QtCore/qalgorithms.h:330 #9 main (argc=1, argv=0x7fff7e1e4578) at ../../../kontact/src/main.cpp:220 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 306807] akonadi 4.8.5 states that Nepomuk query server is not available, but there is no further information
https://bugs.kde.org/show_bug.cgi?id=306807 Erik Quaeghebeur kdeb...@equaeghe.nospammail.net changed: What|Removed |Added CC||kdebugs@equaeghe.nospammail ||.net -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 323980] Duplicate messages if antispam filter enabled
https://bugs.kde.org/show_bug.cgi?id=323980 a.skemb...@gmail.com changed: What|Removed |Added CC||a.skemb...@gmail.com --- Comment #1 from a.skemb...@gmail.com --- I have a similar problem with a POP3 account - I have SpamAssassin and Bogofilter installed and I also apply filters on the sender's email address to classify my messages into separate folders. About 1 out of every 3 emails from those that are filtered to go into one of the folders (but not the ones staying into the generic inbox) are duplicated. It seems related to Bug 283682 (but I am not sure). Please let me know what types of log / tests I can provide -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 326205] New: Google Contact subfolders (categories) don't show up in kmail select addresses dialog
https://bugs.kde.org/show_bug.cgi?id=326205 Bug ID: 326205 Summary: Google Contact subfolders (categories) don't show up in kmail select addresses dialog Classification: Unclassified Product: Akonadi Version: 4.11 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Google Resource Assignee: dvra...@redhat.com Reporter: martin.tlus...@gmail.com CC: kdepim-bugs@kde.org I would like to be able to select all addresses from one of my google categories to send an email to, but they don't show up in the select addresses dialog. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 323980] Duplicate messages if antispam filter enabled
https://bugs.kde.org/show_bug.cgi?id=323980 --- Comment #2 from a.skemb...@gmail.com --- Sorry, forgot to specify I am on KDE 4.11.2 on OpenSUSE 12.3 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 326188] Akonadi server fails to start when home is in AFS on KDE 4.8.5, Kubuntu 12.04 amd64
https://bugs.kde.org/show_bug.cgi?id=326188 --- Comment #2 from u1...@hushmail.com --- (In reply to comment #1) Could you please verify whether file /afs/mydomain/myuser/.local/share/akonadi/mysql.conf exists and whether it's readable? Yes it exists and is readable: $ ls -l /afs/mydomain/myuser/.local/share/akonadi/mysql.conf -rw-r--r-- 1 myuser mygroup 3277 Oct 15 17:34 /afs/mydomain/myuser/.local/share/akonadi/mysql.conf Now when I have added a symbolic link for /afs/mydomain/myuser/.local/share/akonadi to the local harddrive (ext4) that file is not stored in AFS. This is how the file lookes like (it was automatically created when I tried to run kmail): $ cat /afs/mydomain/myuser/.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 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 326211] New: Crashes on start
https://bugs.kde.org/show_bug.cgi?id=326211 Bug ID: 326211 Summary: Crashes on start Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ro...@freenet.de Application: kmail (4.10.5) KDE Platform Version: 4.10.5 Qt Version: 4.8.4 Operating System: Linux 3.8.0-19-generic x86_64 Distribution: Ubuntu 13.04 -- Information about the crash: - What I was doing when the application crashed: type kmail into command line to start the application: kmail QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. Enchant dict for en_GB 0x2a224a0 kmail2(9834) MessageViewer::ObjectTreeParser::defaultHandling: no htmlWriter() kmail2(9834) MessageViewer::ObjectTreeParser::defaultHandling: no htmlWriter() kmail2(9834) MessageViewer::ObjectTreeParser::defaultHandling: no htmlWriter() kmail2(9834) MessageViewer::ObjectTreeParser::defaultHandling: no htmlWriter() kmail2(9834) MessageViewer::ObjectTreeParser::defaultHandling: no htmlWriter() kmail2(9834) MessageViewer::ObjectTreeParser::defaultHandling: no htmlWriter() *** Error in `kmail': free(): invalid next size (fast): 0x029a7190 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x80a46)[0x7f9c2f4e2a46] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN11QTextEngine13clearLineDataEv+0x85)[0x7f9c306440d5] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x472895)[0x7f9c3068c895] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x634efb)[0x7f9c3084eefb] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN9QTextEdit11resizeEventEP12QResizeEvent+0x39)[0x7f9c3084f709] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0xaf5)[0x7f9c30432c55] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN6QFrame5eventEP6QEvent+0x26)[0x7f9c307e5486] /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent+0x86)[0x7f9c2febb7a6] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x7c)[0x7f9c303e58bc] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x13b)[0x7f9c303e825b] /usr/lib/libkdeui.so.5(_ZN12KApplication6notifyEP7QObjectP6QEvent+0x36)[0x7f9c31bf71a6] /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e)[0x7f9c2febb63e] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate30sendPendingMoveAndResizeEventsEbb+0x1a6)[0x7f9c304341d6] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x21)[0x7f9c30435ea1] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x162)[0x7f9c304362a2] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x11e)[0x7f9c3043683e] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x3d)[0x7f9c30435ebd] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x162)[0x7f9c304362a2] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x11e)[0x7f9c3043683e] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x3d)[0x7f9c30435ebd] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x162)[0x7f9c304362a2] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x11e)[0x7f9c3043683e] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x3d)[0x7f9c30435ebd] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x162)[0x7f9c304362a2] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x11e)[0x7f9c3043683e] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x3d)[0x7f9c30435ebd] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x162)[0x7f9c304362a2] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x11e)[0x7f9c3043683e] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x3d)[0x7f9c30435ebd] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x162)[0x7f9c304362a2] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x11e)[0x7f9c3043683e] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x3d)[0x7f9c30435ebd] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x162)[0x7f9c304362a2] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x11e)[0x7f9c3043683e]
[kmail2] [Bug 326211] Crashes on start
https://bugs.kde.org/show_bug.cgi?id=326211 --- Comment #1 from ro...@freenet.de --- Solved with this: https://bugs.kde.org/show_bug.cgi?id=324974, removing ~/.kde/share/apps/kmail2/autosave/* -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 326188] Akonadi server fails to start when home is in AFS on KDE 4.8.5, Kubuntu 12.04 amd64
https://bugs.kde.org/show_bug.cgi?id=326188 --- Comment #3 from Daniel Vrátil dvra...@redhat.com --- Bit of a googling revealed ([0], [1]), that MySQL actually might not work on AFS, so there's nothing we can do about this. [0] http://pages.cs.wisc.edu/~bolo/notes/mysql.html [1] http://lists.mysql.com/mysql/16170 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 325899] kmail2 is hanging sometimes
https://bugs.kde.org/show_bug.cgi?id=325899 --- Comment #1 from Carsten Grohmann carstengrohm...@gmx.de --- Created attachment 82933 -- https://bugs.kde.org/attachment.cgi?id=82933action=edit Backtrace of akonadiserver created using gdb bt full at 2013-10-16 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 325899] kmail2 is hanging sometimes
https://bugs.kde.org/show_bug.cgi?id=325899 --- Comment #2 from Carsten Grohmann carstengrohm...@gmx.de --- Created attachment 82934 -- https://bugs.kde.org/attachment.cgi?id=82934action=edit Backtrace of akonadiserver created using gdb bt full at 2013-10-18 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 325899] kmail2 is hanging sometimes
https://bugs.kde.org/show_bug.cgi?id=325899 --- Comment #3 from Carsten Grohmann carstengrohm...@gmx.de --- Today I've added to files with the output of gdb bt full attached to the process akonadiserver. The output created at 2013-10-16 shows a normal situation and the output created at 2013-10-18 shows the hanging situation. The second situation hasn't changed after 30 minutes. Looks like the output from 2013-10-18 shows a classical dead lock situation. It looks like a big locking bug in your code. Regards, Carsten -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 317743] Akonadi Console crash at exit
https://bugs.kde.org/show_bug.cgi?id=317743 Carsten Grohmann carstengrohm...@gmx.de changed: What|Removed |Added CC||carstengrohm...@gmx.de --- Comment #3 from Carsten Grohmann carstengrohm...@gmx.de --- Application: akonadiconsole (0.99) KDE Platform Version: 4.10.5 Qt Version: 4.8.6 Operating System: Linux 3.10-3-686-pae i686 Distribution: Debian GNU/Linux testing (jessie) -- Information about the crash: - What I was doing when the application crashed: I've cleared the Akonadi Cache for my local inbox folder and clicked Synchronize folder. AC crashed during closing. -- Backtrace: Application: Akonadi Console (akonadiconsole), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. [Current thread is 1 (Thread 0xb1f289c0 (LWP 3833))] Thread 3 (Thread 0xaf95eb40 (LWP 3836)): #0 0xb7793424 in __kernel_vsyscall () #1 0xb30c57ab in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb53682ac in __pthread_cond_wait (cond=0xb4b0ae30 WTF::pageheap_memory+20720, mutex=0xb4b0ae18 WTF::pageheap_memory+20696) at forward.c:149 #3 0xb43b3de9 in WTF::TCMalloc_PageHeap::scavengerThread (this=this@entry=0xb4b05d40 WTF::pageheap_memory) at wtf/FastMalloc.cpp:2499 #4 0xb43b3e7f in WTF::TCMalloc_PageHeap::runScavengerThread (context=0xb4b05d40 WTF::pageheap_memory) at wtf/FastMalloc.cpp:1622 #5 0xb30c1cf1 in start_thread (arg=0xaf95eb40) at pthread_create.c:311 #6 0xb535b08e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 2 (Thread 0xaf035b40 (LWP 3837)): #0 0xb7793424 in __kernel_vsyscall () #1 0xb536dc32 in clock_gettime (clock_id=1, tp=0xaf035048) at ../sysdeps/unix/clock_gettime.c:115 #2 0xb55e2f8c in do_gettime (frac=0xaf035040, sec=0xaf035038) at tools/qelapsedtimer_unix.cpp:127 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:144 #4 0xb56cb731 in QTimerInfoList::updateCurrentTime (this=this@entry=0xae702074) at kernel/qeventdispatcher_unix.cpp:354 #5 0xb56ca4be in timerSourceCheckHelper (src=0xae702040) at kernel/qeventdispatcher_glib.cpp:150 #6 0xb2de317f in g_main_context_check (context=context@entry=0xae7004e0, max_priority=2147483647, fds=fds@entry=0xae702160, n_fds=n_fds@entry=1) at /build/glib2.0-Ot8bbC/glib2.0-2.36.4/./glib/gmain.c:3545 #7 0xb2de36ea in g_main_context_iterate (context=context@entry=0xae7004e0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/glib2.0-Ot8bbC/glib2.0-2.36.4/./glib/gmain.c:3698 #8 0xb2de3898 in g_main_context_iteration (context=0xae7004e0, may_block=1) at /build/glib2.0-Ot8bbC/glib2.0-2.36.4/./glib/gmain.c:3762 #9 0xb56ca23f in QEventDispatcherGlib::processEvents (this=0xae700468, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #10 0xb5699163 in QEventLoop::processEvents (this=this@entry=0xaf035258, flags=...) at kernel/qeventloop.cpp:149 #11 0xb5699489 in QEventLoop::exec (this=this@entry=0xaf035258, flags=...) at kernel/qeventloop.cpp:204 #12 0xb55850bd in QThread::exec (this=this@entry=0x9a93ba0) at thread/qthread.cpp:537 #13 0xb558520b in QThread::run (this=0x9a93ba0) at thread/qthread.cpp:604 #14 0xb5587a4f in QThreadPrivate::start (arg=0x9a93ba0) at thread/qthread_unix.cpp:349 #15 0xb30c1cf1 in start_thread (arg=0xaf035b40) at pthread_create.c:311 #16 0xb535b08e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 1 (Thread 0xb1f289c0 (LWP 3833)): [KCrash Handler] #7 data (this=0x4) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135 #8 qGetPtrHelperQScopedPointerQObjectData (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2465 #9 d_func (this=0x0) at itemviews/qitemselectionmodel.h:154 #10 QItemSelectionModel::hasSelection (this=0x0) at itemviews/qitemselectionmodel.cpp:1416 #11 0xb67c9695 in KSelectionProxyModelPrivate::sourceRowsAboutToBeInserted (this=0x991c590, parent=..., start=73, end=73) at ../../kdeui/itemviews/kselectionproxymodel.cpp:984 #12 0xb67d1e34 in KSelectionProxyModel::qt_static_metacall (_o=optimized out, _id=optimized out, _a=0xbff14960, _c=optimized out) at ./moc_kselectionproxymodel.cpp:99 #13 0xb56af825 in QMetaObject::activate (sender=sender@entry=0x9918b58, m=0x80aae20 QAbstractItemModel::staticMetaObject, m@entry=0xb58062f8 QAbstractItemModel::staticMetaObject, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0xbff14960) at kernel/qobject.cpp:3547 #14 0xb56fec15 in QAbstractItemModel::rowsAboutToBeInserted (this=this@entry=0x9918b58, _t1=..., _t2=_t2@entry=73, _t3=_t3@entry=73) at .moc/release-shared/moc_qabstractitemmodel.cpp:189 #15 0xb5690e2c in QAbstractItemModel::beginInsertRows (this=this@entry=0x9918b58, parent=..., first=73, last=73) at kernel/qabstractitemmodel.cpp:2416 #16 0xb760e9b6 in
[kmail2] [Bug 326239] New: Wrong send identity/transport used for non-default account when multiple accounts defined
https://bugs.kde.org/show_bug.cgi?id=326239 Bug ID: 326239 Summary: Wrong send identity/transport used for non-default account when multiple accounts defined Classification: Unclassified Product: kmail2 Version: 4.11.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: mike.cloa...@gmail.com Setup two accounts and two identities. Select a default identity and transport. Now check the second account and its folders - when looking at the folder properties in the non-default account such as the Inbox the Sender identity is the default instead of the second one defined. If it is changed and Kmail restarted then the previous selection is reverted again to the incorrect default Sender identity. If a mail is composed and sent from the non-default account/identity then the default identity and transport are used incorrectly. The selection of the second identity and transport to be used for the non-default account should be allowed to be made permanent. If during a mail compose the identity and transport are set as in view then the non-default choices can be selected and the mail will then send correctly - but these selections cannot be made permanent. Reproducible: Always Steps to Reproduce: 1. Set up two accounts and two identities 2. Select the non-default account - check the folder properties in the Inbox and all other folders - they are wrongly given the default values. 3. Compose an email and make the identity and transport in view. The incorrect default identity and transport are seen - they can be changed but only during sending a single mail. Actual Results: Wrong (default) identity and transport selected for the non-default account when composing an email. Expected Results: Each account should use the correct identity and transport when composing an email. From the default account it should be the default identity and transport, and the non-default used when sending from the non-default account. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 326242] New: akonadi_imap_resource crash when deleting multiple messages
https://bugs.kde.org/show_bug.cgi?id=326242 Bug ID: 326242 Summary: akonadi_imap_resource crash when deleting multiple messages Classification: Unclassified Product: Akonadi Version: 4.11 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: er...@kde.org Reporter: j...@skanes.ca CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.11) KDE Platform Version: 4.11.2 Qt Version: 4.8.4 Operating System: Linux 3.11.0-12-generic i686 Distribution: Ubuntu 13.10 -- Information about the crash: - What I was doing when the application crashed: This crash occurs always when I delete a selection of more than one message. It does not occur when deleting a single message. Deletion is performed using the delete key to send the messages to the trash folder. - Custom settings of the application: The IMAP account in question is hosted on a stock Ubuntu 8.04.4 LTS server running dovecot version 1:1.0.10-1ubuntu5. The crash can be reproduced every time. -- Backtrace: Application: 1 - Windy of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb4a5c740 (LWP 13608))] Thread 3 (Thread 0xb1fe4b40 (LWP 13611)): #0 0xb5604c09 in __pthread_mutex_unlock_usercnt (mutex=0xb1600558, decr=1) at pthread_mutex_unlock.c:36 #1 0xb57bfc04 in pthread_mutex_unlock (mutex=0xb1600558) at forward.c:194 #2 0xb5515be0 in g_mutex_unlock (mutex=mutex@entry=0xb16004e0) at /build/buildd/glib2.0-2.38.0/./glib/gthread-posix.c:232 #3 0xb54d211e in g_main_context_prepare (context=context@entry=0xb16004e0, priority=priority@entry=0xb1fe4148) at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:3337 #4 0xb54d2a4f in g_main_context_iterate (context=context@entry=0xb16004e0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:3692 #5 0xb54d2c98 in g_main_context_iteration (context=0xb16004e0, may_block=1) at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:3773 #6 0xb73378df in QEventDispatcherGlib::processEvents (this=0xb1600468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0xb73069f3 in QEventLoop::processEvents (this=this@entry=0xb1fe4258, flags=...) at kernel/qeventloop.cpp:149 #8 0xb7306d19 in QEventLoop::exec (this=this@entry=0xb1fe4258, flags=...) at kernel/qeventloop.cpp:204 #9 0xb71f5e3d in QThread::exec (this=this@entry=0x9e3e890) at thread/qthread.cpp:542 #10 0xb71f5f8b in QThread::run (this=0x9e3e890) at thread/qthread.cpp:609 #11 0xb71f872f in QThreadPrivate::start (arg=0x9e3e890) at thread/qthread_unix.cpp:338 #12 0xb5601d78 in start_thread (arg=0xb1fe4b40) at pthread_create.c:311 #13 0xb57b201e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 2 (Thread 0xb09ffb40 (LWP 13614)): #0 g_mutex_unlock (mutex=mutex@entry=0xb0b004e0) at /build/buildd/glib2.0-2.38.0/./glib/gthread-posix.c:234 #1 0xb54d2728 in g_main_context_dispatch (context=context@entry=0xb0b004e0) at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:3644 #2 0xb54d2bd8 in g_main_context_iterate (context=context@entry=0xb0b004e0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:3712 #3 0xb54d2c98 in g_main_context_iteration (context=0xb0b004e0, may_block=1) at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:3773 #4 0xb73378df in QEventDispatcherGlib::processEvents (this=0xb0b00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0xb73069f3 in QEventLoop::processEvents (this=this@entry=0xb09ff258, flags=...) at kernel/qeventloop.cpp:149 #6 0xb7306d19 in QEventLoop::exec (this=this@entry=0xb09ff258, flags=...) at kernel/qeventloop.cpp:204 #7 0xb71f5e3d in QThread::exec (this=this@entry=0x9e591d8) at thread/qthread.cpp:542 #8 0xb71f5f8b in QThread::run (this=0x9e591d8) at thread/qthread.cpp:609 #9 0xb71f872f in QThreadPrivate::start (arg=0x9e591d8) at thread/qthread_unix.cpp:338 #10 0xb5601d78 in start_thread (arg=0xb09ffb40) at pthread_create.c:311 #11 0xb57b201e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 1 (Thread 0xb4a5c740 (LWP 13608)): [KCrash Handler] #7 0x0808908e in MoveItemsTask::recordNewUid (this=this@entry=0x9fab1e8) at ../../../resources/imap/moveitemstask.cpp:289 #8 0x080896b0 in MoveItemsTask::onSearchDone (this=0x9fab1e8, job=0x9e10b60) at ../../../resources/imap/moveitemstask.cpp:241 #9 0xb731cfc7 in QMetaObject::activate (sender=sender@entry=0x9e10b60, m=m@entry=0xb5c264cc KJob::staticMetaObject, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0xbfa8d228) at kernel/qobject.cpp:3539 #10 0xb5a809e5 in KJob::result (this=this@entry=0x9e10b60,
[Akonadi] [Bug 326242] akonadi_imap_resource crash when deleting multiple messages
https://bugs.kde.org/show_bug.cgi?id=326242 --- Comment #1 from Jon Skanes j...@skanes.ca --- In previous versions of KDE, I remember getting a taskbar notification mentioning the IMAP server replied there was an invalid argument for the UID sent by Akonadi. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
