[Bug 302167] mysqld eats up cpu for 5-10s when fetching emails
https://bugs.kde.org/show_bug.cgi?id=302167 Arthur Titeica arthur.tite...@gmail.com changed: What|Removed |Added CC||arthur.tite...@gmail.com --- Comment #2 from Arthur Titeica arthur.tite...@gmail.com --- The same thing happens when deleting mails or when deleting lots of files which makes nepomuk -- 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
[Bug 302167] mysqld eats up cpu for 5-10s when fetching emails
https://bugs.kde.org/show_bug.cgi?id=302167 --- Comment #3 from Arthur Titeica arthur.tite...@gmail.com --- ... to do lots of mysql request. (Sorry about the double message.) -- 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
[Bug 302167] mysqld eats up cpu for 5-10s when fetching emails
https://bugs.kde.org/show_bug.cgi?id=302167 --- Comment #4 from Robby Engelmann robby.engelm...@igfs-ev.de --- The problem considering the mail feeder is gone in recent post beta2 git packages -- 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
[Bug 302283] New: Akregator crashed when closing after reading security report page
https://bugs.kde.org/show_bug.cgi?id=302283 Bug ID: 302283 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Akregator crashed when closing after reading security report page Classification: Unclassified OS: Linux Reporter: r.pflau...@btinternet.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.7.2) KDE Platform Version: 4.7.2 (4.7.2) release 5 Qt Version: 4.7.4 Operating System: Linux 3.1.10-1.9-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: - What I was doing when the application crashed: I was attempting to look at the security updates page for which there is a link The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7ff2af6e7760 (LWP 1980))] Thread 6 (Thread 0x7ff2971b5700 (LWP 1981)): #0 0x7ff2a761fe6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff2abf689dc in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7ff2abf68b09 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7ff2a761bf05 in start_thread () from /lib64/libpthread.so.0 #4 0x7ff2acc7210d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7ff2968b4700 (LWP 1982)): #0 0x7fff707ff98f in clock_gettime () #1 0x7ff2a6559d9a in clock_gettime () from /lib64/librt.so.1 #2 0x7ff2adf9c114 in do_gettime (frac=0x7ff2968b3bf8, sec=0x7ff2968b3bf0) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x7ff2ae05dd2d in QTimerInfoList::updateCurrentTime (this=0x7ff2900020d0) at kernel/qeventdispatcher_unix.cpp:339 #5 0x7ff2ae05d9b1 in timerSourceCheckHelper (src=optimized out) at kernel/qeventdispatcher_glib.cpp:150 #6 timerSourceCheckHelper (src=optimized out) at kernel/qeventdispatcher_glib.cpp:144 #7 0x7ff2a62a5264 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #8 0x7ff2a62a5ab2 in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x7ff2a62a5f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x7ff2ae05d586 in QEventDispatcherGlib::processEvents (this=0x7ff298c0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #11 0x7ff2ae031a32 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #12 0x7ff2ae031c2f in QEventLoop::exec (this=0x7ff2968b3e20, flags=...) at kernel/qeventloop.cpp:201 #13 0x7ff2adf495df in QThread::exec (this=optimized out) at thread/qthread.cpp:498 #14 0x7ff2adf4c025 in QThreadPrivate::start (arg=0x77c040) at thread/qthread_unix.cpp:331 #15 0x7ff2a761bf05 in start_thread () from /lib64/libpthread.so.0 #16 0x7ff2acc7210d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7ff236e7a700 (LWP 2056)): #0 0x7ff2a761fe6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff236e9efc1 in queue_processor(void*) () from /usr/lib64/IcedTeaPlugin.so #2 0x7ff2a761bf05 in start_thread () from /lib64/libpthread.so.0 #3 0x7ff2acc7210d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7ff236679700 (LWP 2057)): #0 0x7ff2a761fe6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff236e9efc1 in queue_processor(void*) () from /usr/lib64/IcedTeaPlugin.so #2 0x7ff2a761bf05 in start_thread () from /lib64/libpthread.so.0 #3 0x7ff2acc7210d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7ff235e78700 (LWP 2058)): #0 0x7ff2a761fe6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff236e9efc1 in queue_processor(void*) () from /usr/lib64/IcedTeaPlugin.so #2 0x7ff2a761bf05 in start_thread () from /lib64/libpthread.so.0 #3 0x7ff2acc7210d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ff2af6e7760 (LWP 1980)): [KCrash Handler] #6 0x in ?? () #7 0x7ff2ac98284e in KParts::StatusBarExtension::statusBar (this=0x111c1a0) at /usr/src/debug/kdelibs-4.7.2/kparts/statusbarextension.cpp:149 #8 0x7ff2ac982d54 in KParts::StatusBarExtension::~StatusBarExtension (this=0x111c1a0, __in_chrg=optimized out) at /usr/src/debug/kdelibs-4.7.2/kparts/statusbarextension.cpp:99 #9 0x7ff2ac983109 in KParts::StatusBarExtension::~StatusBarExtension (this=0x111c1a0, __in_chrg=optimized out) at /usr/src/debug/kdelibs-4.7.2/kparts/statusbarextension.cpp:110 #10 0x7ff2ae044465 in QObjectPrivate::deleteChildren (this=0xec8780) at kernel/qobject.cpp:1964 #11 0x7ff2ae049a09 in QObject::~QObject (this=0x1179170, __in_chrg=optimized out) at kernel/qobject.cpp:946 #12 0x7ff2ac967a98 in KParts::Part::~Part (this=0x1179170, __vtt_parm=0x7ff23d6758f0, __in_chrg=optimized out) at
[Bug 259949] Kmail does not use all addressbooks for autocompletion
https://bugs.kde.org/show_bug.cgi?id=259949 Jeroen van Meeuwen (Kolab Systems) vanmeeu...@kolabsys.com changed: What|Removed |Added CC||vanmeeu...@kolabsys.com Version|2.0.89 |4.9 pre --- Comment #135 from Jeroen van Meeuwen (Kolab Systems) vanmeeu...@kolabsys.com --- I can confirm this bugs exists still in 4.9 pre - setting version accordingly -- 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
[Bug 259949] Kmail does not use all addressbooks for autocompletion
https://bugs.kde.org/show_bug.cgi?id=259949 --- Comment #136 from m.w...@web.de --- I really wish this bug enough priority so that would be fixed for the release of KDE 4.9. It is very enoying and I have to admit that for most of time I am using Thunderbird now. Mainly because of this bug (partly also because Kmail is still very slow (much faster than in the beginning, but very slow compared to Thunderbird)). And I really would prefer a KDE integrated mailer. -- 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
[Bug 259949] Kmail does not use all addressbooks for autocompletion
https://bugs.kde.org/show_bug.cgi?id=259949 --- Comment #137 from Joachim Wilke kde@joachim-wilke.de --- You first need to investigate a cause and a patch to fix it... Votes show that this is important for the users. -- 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
[Bug 259949] Kmail does not use all addressbooks for autocompletion
https://bugs.kde.org/show_bug.cgi?id=259949 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com Assignee|kdepim-bugs@kde.org |mollek...@kolabsys.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
[Bug 290869] Drag'n'Drop mail to another folder: don't offer position in between folders
https://bugs.kde.org/show_bug.cgi?id=290869 --- Comment #3 from Bernd Oliver Sünderhauf pancho...@riseup.net --- Using 4.8.3, there is still something like an in-between state. -- 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
[Bug 302290] New: Account assistant window always on top of other windows
https://bugs.kde.org/show_bug.cgi?id=302290 Bug ID: 302290 Severity: minor Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Account assistant window always on top of other windows Classification: Unclassified OS: Linux Reporter: maris@gmail.com Hardware: Gentoo Packages Status: UNCONFIRMED Component: general Product: kontact When running Kontact for the first time, Account Assistant dialog is provided. This dialog window is always on top of other windows. Error messages are displayed below it and thus might not be noticed. Reproducible: Didn't try Steps to Reproduce: 1. Run Kontact for firs time; 2. Fill bogous information in IMAP server configuration on Account Assistant; 3. Observe how IMAP error is displayed below Account Assistant window. Actual Results: IMAP error, KDE wallet service dialogs where only visible and available after minimising Account Assistant window. Expected Results: Account Assistant shouldn't cover other windows, especially error messages related to account creation. -- 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
[Bug 259355] kmail terminates during startup with Failed to fetch the resource collection.
https://bugs.kde.org/show_bug.cgi?id=259355 Māris Nartišs maris@gmail.com changed: What|Removed |Added CC||maris@gmail.com --- Comment #36 from Māris Nartišs maris@gmail.com --- It's 2012 and it's still not possible to launch mail application on 4.8.3 without reading bugzilla entries. Uh, well -- 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
[Bug 290142] kmail search doesn't work
https://bugs.kde.org/show_bug.cgi?id=290142 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com Resolution|--- |FIXED --- Comment #7 from Christian Mollekopf mollek...@kolabsys.com --- The searching itself has been fixed in the upcomping 4.9 release together with the latest released akonadi 1.7.90. As to your problem, it looks like the feeder is not set online (you can check that in akonadiconsole), also make sure that indexing is enabled in Settings - Desktop Search - Enable Email Indexer -- 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
[Bug 291142] akonadi_nepomuk_email_feeder 500 MB of RAM usage after setting up IMAP account
https://bugs.kde.org/show_bug.cgi?id=291142 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com Resolution|--- |FIXED --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- Fixed in 4.9 -- 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
[Bug 296706] akonadi nepomuk mail feeder collapse cpu and memory usage
https://bugs.kde.org/show_bug.cgi?id=296706 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com Resolution|--- |FIXED --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- Fixed in 4.9 -- 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
[Bug 290142] kmail search doesn't work
https://bugs.kde.org/show_bug.cgi?id=290142 Andrew Gaydenko a...@gaydenko.com changed: What|Removed |Added CC|a...@gaydenko.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
[Bug 223812] Searching doesn't work
https://bugs.kde.org/show_bug.cgi?id=223812 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|NEW |NEEDSINFO CC||mollek...@kolabsys.com Resolution|--- |WORKSFORME --- Comment #17 from Christian Mollekopf mollek...@kolabsys.com --- Has been fixed as far as I know? (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
[Bug 223438] Metabug for KMail 2 release blockers
https://bugs.kde.org/show_bug.cgi?id=223438 Bug 223438 depends on bug 223812, which changed state. Bug 223812 Summary: Searching doesn't work https://bugs.kde.org/show_bug.cgi?id=223812 What|Removed |Added Status|NEW |NEEDSINFO Resolution|--- |WORKSFORME -- 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
[Bug 277366] KMail2 needs a conversation view like GMail oder Apple Mail
https://bugs.kde.org/show_bug.cgi?id=277366 Bug 277366 depends on bug 223812, which changed state. Bug 223812 Summary: Searching doesn't work https://bugs.kde.org/show_bug.cgi?id=223812 What|Removed |Added Status|NEW |NEEDSINFO Resolution|--- |WORKSFORME -- 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
[Bug 278852] Data stored in Nepomuk are not deleted when removing a given item
https://bugs.kde.org/show_bug.cgi?id=278852 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com Assignee|to...@kde.org |mollek...@kolabsys.com -- 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
[Bug 283212] disable nepomuk feeders when nepomuk is disabled
https://bugs.kde.org/show_bug.cgi?id=283212 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|NEW |RESOLVED CC||mollek...@kolabsys.com Resolution|--- |FIXED --- Comment #8 from Christian Mollekopf mollek...@kolabsys.com --- There is a config option to disable the feeder explicitly which should cover the 22 megs ;-) -- 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
[Bug 302296] New: Can't authenticate to imap.seznam.cz service
https://bugs.kde.org/show_bug.cgi?id=302296 Bug ID: 302296 Severity: normal Version: 4.9 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Can't authenticate to imap.seznam.cz service Classification: Unclassified OS: Linux Reporter: jrez...@redhat.com Hardware: Other Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Authentification to imap.seznam.cz fails with KMail 2, it was working flawlesly with old KMail. The server for account re...@seznam.cz refused the supplied username and password. Do you want to go to the settings, have another attempt at logging in, or do nothing? Login failed, server replied: A03 NO LOGIN: mtd: internal error: Cannot get user attributes.408, Waited too long ( 1ms ) for release of memory lock on user 625934 owned by process 4510. Server info: IMAP4REV1 STARTTLS CHILDREN -- 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
[Bug 301625] kmail crashes during startup (segfault)
https://bugs.kde.org/show_bug.cgi?id=301625 --- Comment #25 from Tamás Németh nt1...@gmail.com --- It really seems to be solved now. Doesn't it? -- 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
[Bug 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 sklo...@gmail.com changed: What|Removed |Added CC||sklo...@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
[Bug 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 --- Comment #189 from sklo...@gmail.com --- Created attachment 72014 -- https://bugs.kde.org/attachment.cgi?id=72014action=edit New crash information added by DrKonqi kontact (4.8.3) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1 - What I was doing when the application crashed: viewing html based emails. Kubuntu Virtual Machine (Workstation 8) -- Backtrace (Reduced): #6 QList (l=..., this=0x7fffa28d0150) at ../../include/QtCore/../../src/corelib/tools/qlist.h:122 #7 QNetworkCacheMetaData::rawHeaders (this=0x7fffa28d0460) at access/qabstractnetworkcache.cpp:240 #8 0x7f0c966a57bc in QNetworkAccessHttpBackend::fetchCacheMetaData (this=0x30804b0, oldMetaData=...) at access/qnetworkaccesshttpbackend.cpp:1019 #9 0x7f0c966a6f14 in QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x30804b0, hm=..., sc=optimized out, rp=..., pu=optimized out, db=..., contentLength=-1) at access/qnetworkaccesshttpbackend.cpp:828 #10 0x7f0c96732709 in QNetworkAccessHttpBackend::qt_static_metacall (_o=0x30804b0, _c=optimized out, _id=optimized out, _a=optimized out) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 -- 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
[Bug 283212] disable nepomuk feeders when nepomuk is disabled
https://bugs.kde.org/show_bug.cgi?id=283212 --- Comment #9 from Oliver Henshaw yoho_a...@hotmail.com --- An extra configuration option seems like sweeping the issue under the carpet. Honest questions since I don't know the answer. What use do the feeder agents have with nepomuk disabled? What the utility in requiring two config options to fully turn 'nepomuk' off, rather than one? -- 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
[Bug 283212] disable nepomuk feeders when nepomuk is disabled
https://bugs.kde.org/show_bug.cgi?id=283212 --- Comment #10 from Christian Mollekopf mollek...@kolabsys.com --- The extra configuration is there so you can disable the feeder while leaving the rest of nepomuk running. Entirely disabling nepomuk also stops the feeder. -- 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
[Bug 283212] disable nepomuk feeders when nepomuk is disabled
https://bugs.kde.org/show_bug.cgi?id=283212 --- Comment #11 from Oliver Henshaw yoho_a...@hotmail.com --- OK. Thanks for the clarification. -- 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
[Bug 302265] no incoming email is notified by widget incoming message
https://bugs.kde.org/show_bug.cgi?id=302265 Lamarque V. Souza lamar...@kde.org changed: What|Removed |Added CC||lamar...@kde.org Component|Widgets strip containment |general Assignee|notm...@gmail.com |kdepim-bugs@kde.org Product|Active |kontact -- 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
[Bug 302301] New: DATA LOSS! kmail crashed after trying to move messagess and the source imap folder got all contents deleted
https://bugs.kde.org/show_bug.cgi?id=302301 Bug ID: 302301 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: DATA LOSS! kmail crashed after trying to move messagess and the source imap folder got all contents deleted Classification: Unclassified OS: Linux Reporter: ka...@seznam.cz Hardware: Gentoo Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.1 Operating System: Linux 3.2.12-gentoo x86_64 Distribution: Gentoo Base System release 2.1 -- Information about the crash: - What I was doing when the application crashed: I've tried to move a few messages from an IMAP folder to a local folder via mouse drag. When I've tried to drop the messages onto the destination folder, it didn't react to mouse release and the cursor stayed overimposed with the messages symbol. While holding the cursor over the target folder, I've tried to click. KMail crashed immediatelly. Checking the IMAP server via web interface, I've found that the folder got completely emptied. I've immediately backed up the remnants in the cache ~/.local/share/akonadi/file_db_data and after a few minutes the files corresponding to messages in that folder disappeared from the cache. Unfortunately, not all of the messages were in the cache when I did the backup, so I've LOST MESSAGES PERMANENTLY - no, they are NOT present in the target local folder, however the few messages I've tried to move are there. Note that DrKonqi suggests a lot duplicates, however two things that look quite different - all the other crashes talk about moving folders, I've just moved messages - I haven't found any mention of data loss in other cases -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7f1013452760 (LWP 2537))] Thread 4 (Thread 0x7f0ff2feb700 (LWP 2592)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f1005735514 in scavengerThread (this=0x7f10060f10c0) at wtf/FastMalloc.cpp:2495 #2 WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7f10060f10c0) at wtf/FastMalloc.cpp:1618 #3 0x7f100e57ad0c in start_thread (arg=0x7f0ff2feb700) at pthread_create.c:301 #4 0x7f1010760bed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7f0ff26ea700 (LWP 2595)): #0 0x7f1010757d13 in *__GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f100902eb84 in g_main_context_poll (n_fds=1, fds=0x7f0fec0013d0, timeout=-1, context=0x7f0fec000990, priority=optimized out) at gmain.c:3402 #2 g_main_context_iterate (context=0x7f0fec000990, block=1, dispatch=1, self=optimized out) at gmain.c:3084 #3 0x7f100902f041 in g_main_context_iteration (context=0x7f0fec000990, may_block=1) at gmain.c:3152 #4 0x7f10110e1106 in QEventDispatcherGlib::processEvents (this=0x7f0fec0008b0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f10110b0f92 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f10110b1245 in QEventLoop::exec (this=0x7f0ff26e9e20, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f1010faf0e8 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7f1010fb175b in QThreadPrivate::start (arg=0xb674e0) at thread/qthread_unix.cpp:298 #9 0x7f100e57ad0c in start_thread (arg=0x7f0ff26ea700) at pthread_create.c:301 #10 0x7f1010760bed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f0ff0a6c700 (LWP 7623)): #0 pthread_cond_timedwait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x7f1010fb25d2 in wait (time=3, this=0x2305b40) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x2318ae8, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f1010fa5d9f in QThreadPoolThread::run (this=0x2319d30) at concurrent/qthreadpool.cpp:141 #4 0x7f1010fb175b in QThreadPrivate::start (arg=0x2319d30) at thread/qthread_unix.cpp:298 #5 0x7f100e57ad0c in start_thread (arg=0x7f0ff0a6c700) at pthread_create.c:301 #6 0x7f1010760bed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f1013452760 (LWP 2537)): [KCrash Handler] #6 QModelIndex (other=..., this=0x7fffd5ef8220) at ../../include/QtCore/../../src/corelib/kernel/qabstractitemmodel.h:65 #7 QSortFilterProxyModel::parent (this=0xa07630, child=optimized out) at itemviews/qsortfilterproxymodel.cpp:1659 #8 0x7f1012e0d8df in parent (this=0x7fffd5ef8270) at /usr/include/qt4/QtCore/qabstractitemmodel.h:393 #9 KIdentityProxyModel::parent (this=0x13a3310, child=...) at
[Bug 302303] New: kmail2-4.8.90 does not restore custom email account order on startup
https://bugs.kde.org/show_bug.cgi?id=302303 Bug ID: 302303 Severity: normal Version: 4.9 pre Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail2-4.8.90 does not restore custom email account order on startup Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Gentoo Packages Status: UNCONFIRMED Component: folders Product: kmail2 In kmail settings, account setup, you can choose a custom order in which the various email accounts appear in the folderlist. After setting this and hitting OK this works fine. However if you restart kmail, the old, original account order is in place again. This does NOT seem as a config issue, it seems kmail just does not read that setting on startup because if you enter the config dialog again and hit OK without changing anything, custom reordering will happen immediately to the order I have configured previously. Reproducible: Always Steps to Reproduce: 1. Have several email accounts 2. change order, hit OK - check that order is now different 4. restart kmail - order is in original state again 6. enter config dialog again, hit OK - account orderis changed again to desired setting Actual Results: Wrong account order on startup Expected Results: Configured order of accounts on startup -- 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
[Bug 299923] KMail crashes when deleting email
https://bugs.kde.org/show_bug.cgi?id=299923 Bigey f...@laposte.net changed: What|Removed |Added CC||f...@laposte.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
[Bug 299923] KMail crashes when deleting email
https://bugs.kde.org/show_bug.cgi?id=299923 --- Comment #2 from Bigey f...@laposte.net --- Created attachment 72019 -- https://bugs.kde.org/attachment.cgi?id=72019action=edit New crash information added by DrKonqi kmail (4.8.3) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1 - What I was doing when the application crashed: Cick delete on a message then kmail crashed -- Backtrace (Reduced): #6 QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x4978d40, hm=..., sc=optimized out, rp=..., pu=optimized out, db=..., contentLength=-1) at access/qnetworkaccesshttpbackend.cpp:827 #7 0x7f867e877709 in QNetworkAccessHttpBackend::qt_static_metacall (_o=0x4978d40, _c=optimized out, _id=optimized out, _a=optimized out) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 #8 0x7f86801b7446 in QObject::event (this=0x4978d40, e=optimized out) at kernel/qobject.cpp:1195 #9 0x7f86806c0894 in notify_helper (e=0x7f85f8008180, receiver=0x4978d40, this=0x1d79ef0) at kernel/qapplication.cpp:4559 #10 QApplicationPrivate::notify_helper (this=0x1d79ef0, receiver=0x4978d40, e=0x7f85f8008180) at kernel/qapplication.cpp:4531 -- 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
[Bug 201815] akregator silently falls into offline mode with modem connection
https://bugs.kde.org/show_bug.cgi?id=201815 Lamarque V. Souza lamar...@kde.org changed: What|Removed |Added CC||lamar...@kde.org --- Comment #1 from Lamarque V. Souza lamar...@kde.org --- Is this problem still happening? -- 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
[Bug 302314] New: Kontact crashes when selecting Edit Recent Contacts
https://bugs.kde.org/show_bug.cgi?id=302314 Bug ID: 302314 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashes when selecting Edit Recent Contacts Classification: Unclassified OS: Linux Reporter: jes...@jessieamorris.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.1 Operating System: Linux 3.2.0-25-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: I right clicked the To box and selected the Edit Recent Contacts option. The moment I do this, my whole Kontact crashes instantly. I am using the Google Resources from the Ubuntu 12.04 repo. The crash can be reproduced every time. -- 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 0x7f67d0a8c7c0 (LWP 28740))] Thread 4 (Thread 0x7f67b4029700 (LWP 28741)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f67cd28bdec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f67cd28bf19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f67c8751e9a in start_thread (arg=0x7f67b4029700) at pthread_create.c:308 #4 0x7f67cdfbd4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7f67b3728700 (LWP 28742)): #0 0x7f67c8256930 in pthread_mutex_lock@plt () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f67c82c05a1 in g_mutex_lock (mutex=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gthread-posix.c:208 #2 0x7f67c8284f35 in g_main_context_iterate (context=0x7f67ac0009a0, block=1, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3113 #3 0x7f67c8285164 in g_main_context_iteration (context=0x7f67ac0009a0, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #4 0x7f67ce732426 in QEventDispatcherGlib::processEvents (this=0x7f67ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f67ce701c82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f67ce701ed7 in QEventLoop::exec (this=0x7f67b3727dc0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f67ce600fa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7f67ce603fcb in QThreadPrivate::start (arg=0x1560490) at thread/qthread_unix.cpp:298 #9 0x7f67c8751e9a in start_thread (arg=0x7f67b3728700) at pthread_create.c:308 #10 0x7f67cdfbd4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7f6765f53700 (LWP 28748)): #0 0x7f67cdfb1b03 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f67c8285036 in g_main_context_poll (n_fds=1, fds=0x7f67600029b0, timeout=-1, context=0x7f6769a0, priority=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3440 #2 g_main_context_iterate (dispatch=1, block=optimized out, context=0x7f6769a0, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3141 #3 g_main_context_iterate (context=0x7f6769a0, block=optimized out, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #4 0x7f67c8285164 in g_main_context_iteration (context=0x7f6769a0, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #5 0x7f67ce732426 in QEventDispatcherGlib::processEvents (this=0x7f6768c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f67ce701c82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f67ce701ed7 in QEventLoop::exec (this=0x7f6765f52d90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f67ce600fa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7f67ce6e19ff in QInotifyFileSystemWatcherEngine::run (this=0x1b9dd50) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x7f67ce603fcb in QThreadPrivate::start (arg=0x1b9dd50) at thread/qthread_unix.cpp:298 #11 0x7f67c8751e9a in start_thread (arg=0x7f6765f53700) at pthread_create.c:308 #12 0x7f67cdfbd4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 1 (Thread 0x7f67d0a8c7c0 (LWP 28740)): [KCrash Handler] #6 QMetaObject::changeGuard (ptr=0x4800fc0, o=0x0) at kernel/qobject.cpp:461 #7 0x7f67cf54a296 in operator= (p=0x0, this=0x4800fc0) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:68 #8 QMenuPrivate::activateAction (this=0x4800d00, action=0x4a12120, action_e=QAction::Trigger, self=true)
[Bug 294849] If mysql connection is dropped, all akonadi tasks failed, restart akonadi drive to crash
https://bugs.kde.org/show_bug.cgi?id=294849 Vishesh Handa m...@vhanda.in changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||m...@vhanda.in Resolution|--- |DUPLICATE --- Comment #2 from Vishesh Handa m...@vhanda.in --- *** This bug has been marked as a duplicate of bug 286627 *** -- 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
