[Akonadi] [Bug 333514] Maildir items are never expired from Akonadi cache because of Baloo
https://bugs.kde.org/show_bug.cgi?id=333514 --- Comment #15 from Knut Hildebrandt knut.hildebra...@gmx.de --- (In reply to Tim Eberhardt from comment #14) Current status: folder is still growing and now 2 days later at 63GB! I think I need a cronjob that deletes the folder every 1-2 days. be careful when deleting. May can disappear. See my above post. -- 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 333514] Maildir items are never expired from Akonadi cache because of Baloo
https://bugs.kde.org/show_bug.cgi?id=333514 --- Comment #14 from Tim Eberhardt tim.eberha...@tu-bs.de --- Current status: folder is still growing and now 2 days later at 63GB! I think I need a cronjob that deletes the folder every 1-2 days. -- 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 333514] Maildir items are never expired from Akonadi cache because of Baloo
https://bugs.kde.org/show_bug.cgi?id=333514 --- Comment #16 from Knut Hildebrandt knut.hildebra...@gmx.de --- Just checked my ~/.local/share/akonadi/file_db_data/. It holds now more than 3.000 files and about 350 MB. I've got three IMAP accounts which together hold less than 1.500 mails that sum up to about 75 MB. Yesterday Akonadi had stored 111 new files in the directory, all of them mails. Some of these mails were definitely deleted from the accounts, like all spam. And quite a few of them - I'm not sure if all - exist in various versions, like one with the whole body of the message and one without. Moreover, of these messages exists something that looks like revisions with almost the same file name but marked _r0 _r1 _r2. Event though these files differ slightly in size in KMail-View they look the same. A closer look in Kate revealed that they hold different contents. Hope these comments help track down the bug(s) that make ~/.local/share/akonadi/file_db_data/ grow so fast and limitless. -- 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 346064] New: imap mail agent assertion failure/crash at wake
https://bugs.kde.org/show_bug.cgi?id=346064 Bug ID: 346064 Summary: imap mail agent assertion failure/crash at wake Product: Akonadi Version: 4.13 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: rjvber...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.13) KDE Platform Version: 4.14.4 (Compiled from sources) Qt Version: 4.8.6 Operating System: Linux 3.13.11.15-ckt15-ck1-kubuntu-amdf10-rjvb x86_64 Distribution: Ubuntu 14.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: I woke the computer after it had been suspended for the night. Sadly I cannot find the assertion message that must have been printed (drowned in too much other output). -- Backtrace: Application: RJVB@gmail of type IMAP E-Mail Server (akonadi_imap_resource), signal: Aborted Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f8b577ee7c0 (LWP 5236))] Thread 13 (Thread 0x7f8b4259e700 (LWP 32751)): #0 pthread_mutex_lock (mutex=0x7f8b3401f790) at forward.c:192 #1 0x7f8b517fe981 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8b517bc699 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8b517bcf03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8b517bd0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8b56b861ee in QEventDispatcherGlib::processEvents (this=0x7f8b3401a7c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x7f8b56b5204f in QEventLoop::processEvents (this=this@entry=0x7f8b4259de20, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f8b56b52395 in QEventLoop::exec (this=this@entry=0x7f8b4259de20, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f8b56a3496d in QThread::exec (this=optimized out) at thread/qthread.cpp:538 #9 0x7f8b56a375a3 in QThreadPrivate::start (arg=0x1296100) at thread/qthread_unix.cpp:349 #10 0x7f8b520e6182 in start_thread (arg=0x7f8b4259e700) at pthread_create.c:312 #11 0x7f8b52cc247d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 12 (Thread 0x7f8b3affd700 (LWP 18607)): #0 0x7f8b517fe61a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f8b517fe979 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8b517bced5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8b517bd0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8b56b861ee in QEventDispatcherGlib::processEvents (this=0x7f8b2c028ee0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #5 0x7f8b56b5204f in QEventLoop::processEvents (this=this@entry=0x7f8b3affce20, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f8b56b52395 in QEventLoop::exec (this=this@entry=0x7f8b3affce20, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f8b56a3496d in QThread::exec (this=optimized out) at thread/qthread.cpp:538 #8 0x7f8b56a375a3 in QThreadPrivate::start (arg=0x118cf50) at thread/qthread_unix.cpp:349 #9 0x7f8b520e6182 in start_thread (arg=0x7f8b3affd700) at pthread_create.c:312 #10 0x7f8b52cc247d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 11 (Thread 0x7f8b3bfff700 (LWP 22955)): #0 0x7f8b52cb511d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f8b517bcfe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8b517bd0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8b56b861ee in QEventDispatcherGlib::processEvents (this=0x7f8b30003c60, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x7f8b56b5204f in QEventLoop::processEvents (this=this@entry=0x7f8b3bffee20, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f8b56b52395 in QEventLoop::exec (this=this@entry=0x7f8b3bffee20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f8b56a3496d in QThread::exec (this=optimized out) at thread/qthread.cpp:538 #7 0x7f8b56a375a3 in QThreadPrivate::start (arg=0xfff740) at thread/qthread_unix.cpp:349 #8 0x7f8b520e6182 in start_thread (arg=0x7f8b3bfff700) at pthread_create.c:312 #9 0x7f8b52cc247d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 10 (Thread 0x7f8b3b7fe700 (LWP 25176)): #0 0x7fff0ddf97c8 in clock_gettime () #1 0x7f8b52cd092d in __GI___clock_gettime (clock_id=optimized out, tp=optimized out) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f8b56a97229 in do_gettime (frac=synthetic pointer, sec=synthetic pointer) at tools/qelapsedtimer_unix.cpp:127 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:144 #4 0x7f8b56b87015 in
[kontact] [Bug 346065] Kmail crashed with no user action
https://bugs.kde.org/show_bug.cgi?id=346065 Laurent Montel mon...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Version Fixed In||4.14.7 Resolution|--- |FIXED --- Comment #1 from Laurent Montel mon...@kde.org --- Activate favorite folder in settings is the workaround -- 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 236600] KMimeType Crash
https://bugs.kde.org/show_bug.cgi?id=236600 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|REOPENED|RESOLVED CC||mollek...@kolabsys.com Resolution|--- |WORKSFORME -- 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
[kontact] [Bug 346065] New: Kmail crashed with no user action
https://bugs.kde.org/show_bug.cgi?id=346065 Bug ID: 346065 Summary: Kmail crashed with no user action Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: k...@meurisse.org Application: kontact (4.14.6) KDE Platform Version: 4.14.6 Qt Version: 4.8.6 Operating System: Linux 3.19.0-12-generic x86_64 Distribution: Ubuntu Vivid Vervet (development branch) -- Information about the crash: - What I was doing when the application crashed: I was doing some unrelated task and kmail was in the background when it suddenly crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7fb166222800 (LWP 19292))] Thread 5 (Thread 0x7fb14628c700 (LWP 19335)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb160ec581d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fb160ec5859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fb15d5c36aa in start_thread (arg=0x7fb14628c700) at pthread_create.c:333 #4 0x7fb163703eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fb105981700 (LWP 19351)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb160c0620d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fb160ef4fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fb15d5c36aa in start_thread (arg=0x7fb105981700) at pthread_create.c:333 #4 0x7fb163703eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fb0f5ce3700 (LWP 19557)): #0 0x7fb15d1227a4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb15d0dd3f0 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb15d0ddde8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb15d0ddfcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb163e8c82e in QEventDispatcherGlib::processEvents (this=0x7fb0f8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #5 0x7fb163e5bcd1 in QEventLoop::processEvents (this=this@entry=0x7fb0f5ce2dd0, flags=...) at kernel/qeventloop.cpp:149 #6 0x7fb163e5c035 in QEventLoop::exec (this=this@entry=0x7fb0f5ce2dd0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7fb163d4fe89 in QThread::exec (this=optimized out) at thread/qthread.cpp:538 #8 0x7fb163d526ff in QThreadPrivate::start (arg=0x1277aa0) at thread/qthread_unix.cpp:349 #9 0x7fb15d5c36aa in start_thread (arg=0x7fb0f5ce3700) at pthread_create.c:333 #10 0x7fb163703eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb0ef987700 (LWP 19823)): #0 0x7fb1636f449d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fb15d1212f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb15d0dd96c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb15d0dde60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb15d0ddfcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb163e8c82e in QEventDispatcherGlib::processEvents (this=0x7fb0e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #6 0x7fb163e5bcd1 in QEventLoop::processEvents (this=this@entry=0x7fb0ef986d80, flags=...) at kernel/qeventloop.cpp:149 #7 0x7fb163e5c035 in QEventLoop::exec (this=this@entry=0x7fb0ef986d80, flags=...) at kernel/qeventloop.cpp:204 #8 0x7fb163d4fe89 in QThread::exec (this=this@entry=0x2d956c0) at thread/qthread.cpp:538 #9 0x7fb163e3c443 in QInotifyFileSystemWatcherEngine::run (this=0x2d956c0) at io/qfilesystemwatcher_inotify.cpp:265 #10 0x7fb163d526ff in QThreadPrivate::start (arg=0x2d956c0) at thread/qthread_unix.cpp:349 #11 0x7fb15d5c36aa in start_thread (arg=0x7fb0ef987700) at pthread_create.c:333 #12 0x7fb163703eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fb166222800 (LWP 19292)): [KCrash Handler] #6 0x7fb162670039 in Akonadi::FavoriteCollectionsModel::removeCollection (this=0x0, collection=...) at ../../akonadi/favoritecollectionsmodel.cpp:294 #7 0x7fb0fb7ec4cc in KMMainWidget::slotCollectionRemoved (this=optimized out, col=...) at ../../kmail/kmmainwidget.cpp:4501 #8 0x7fb0fb8ec92e in KMMainWidget::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=optimized out) at moc_kmmainwidget.cpp:488 #9 0x7fb163e7219c in QMetaObject::activate (sender=0x11d4290,
[Akonadi] [Bug 346066] New: crash on click on subfolder of kmail folder ressource
https://bugs.kde.org/show_bug.cgi?id=346066 Bug ID: 346066 Summary: crash on click on subfolder of kmail folder ressource Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: akonadiconsole Assignee: kdepim-bugs@kde.org Reporter: criss...@gmx.de I have the problem that I cant read some messages from kmail folder ressource cant retrieve item. For that I started akonadi-console to clear akonadi cache and let resync it. I selected the kmail folder ressource and it shows some subfolders. After click on a subfolder akondi-console crashed. akonadi version: 0.99 running on kde 4.14.2 Reproducible: Always -- 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 346067] New: crash on click on subfolder of kmail folder ressource
https://bugs.kde.org/show_bug.cgi?id=346067 Bug ID: 346067 Summary: crash on click on subfolder of kmail folder ressource Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: akonadiconsole Assignee: kdepim-bugs@kde.org Reporter: criss...@gmx.de I have the problem that I cant read some messages from kmail folder ressource cant retrieve item. For that I started akonadi-console to clear akonadi cache and let resync it. I selected the kmail folder ressource and it shows some subfolders. After click on a subfolder akondi-console crashed. akonadi version: 0.99 running on kde 4.14.2 Reproducible: Always -- 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
