[kmail2] [Bug 372708] Kmail stopped working
https://bugs.kde.org/show_bug.cgi?id=372708 --- Comment #3 from Ekkehard Blanz --- Sorry Justin, I have long abandoned Kmail when its (and Akonadi's) issues with gmail became unbearable, I have no current installation of Kmail anymore. A status of "Abandoned" would be appropriate, but I don't think it exists. > On Nov 10, 2022, at 00:51, Justin Zobel wrote: > > https://bugs.kde.org/show_bug.cgi?id=372708 > > Justin Zobel changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #2 from Justin Zobel --- > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 415596] Kontact crashes on re-opening
https://bugs.kde.org/show_bug.cgi?id=415596 --- Comment #2 from Ekkehard Blanz --- Justin, there were simply too many issues with Kontact and gmail, so I moved on and switched to thunderbolt. The look-and-feel is a bit "clunkier" - but it works Later yet, I switched to a Mac completely and was never looking back. The downside: I cannot reproduce anything with Kontact anymore 😪 For the bug state, is there such a thing as "abandoned"? It would fit perfectly. Ekkehard > On Sep 29, 2022, at 21:37, Justin Zobel wrote: > > https://bugs.kde.org/show_bug.cgi?id=415596 > > Justin Zobel changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Justin Zobel --- > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 329496] Kontact crashed on exit
https://bugs.kde.org/show_bug.cgi?id=329496 Ekkehard Blanz changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #10 from Ekkehard Blanz --- Kontact sill has lots of "issues," i.e. it hangs when updating (BIG) folders a lot, but this particular bug did not occur anymore for me. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 415596] New: Kontact crashes on re-opening
https://bugs.kde.org/show_bug.cgi?id=415596 Bug ID: 415596 Summary: Kontact crashes on re-opening Product: kontact Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ekkehard.bl...@gmail.com Target Milestone: --- Application: kontact (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-72-generic x86_64 Distribution: Ubuntu 18.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: I closed Kontact - then I tried to re-open it. I never saw it reappear, but instead the bug reporter popped up. -- 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 0x7f25fc872600 (LWP 13661))] Thread 31 (Thread 0x7f24794c9700 (LWP 1323)): #0 0x7f25f4fd2ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f24794c87e0, expected=0, futex_word=0x7f25a40045e0) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f25f4fd2ed9 in __pthread_cond_wait_common (abstime=0x7f24794c8880, mutex=0x7f25a4004590, cond=0x7f25a40045b8) at pthread_cond_wait.c:533 #2 0x7f25f4fd2ed9 in __pthread_cond_timedwait (cond=0x7f25a40045b8, mutex=0x7f25a4004590, abstime=0x7f24794c8880) at pthread_cond_wait.c:667 #3 0x7f25e9ff3652 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f25e9fc9799 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f25e9fc9cfb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f25e9fc25eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f25f4fcc6db in start_thread (arg=0x7f24794c9700) at pthread_create.c:463 #8 0x7f25f924d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7f24b05aa700 (LWP 1319)): #0 0x7f25f9240bf9 in __GI___poll (fds=0x7f24a80030e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f25f2f4b5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f25f2f4b6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f25f9da199b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f25f9d469fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f25f9b6523a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f25f9b6a17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f25f4fcc6db in start_thread (arg=0x7f24b05aa700) at pthread_create.c:463 #8 0x7f25f924d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7f24c20ee700 (LWP 1316)): #0 0x7f25f2f91649 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f25f2f4a470 in g_main_context_acquire () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f25f2f4b485 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f25f2f4b6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f25f9da199b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f25f9d469fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f25f9b6523a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f25f9b6a17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f25f4fcc6db in start_thread (arg=0x7f24c20ee700) at pthread_create.c:463 #9 0x7f25f924d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7f247db2b700 (LWP 7074)): #0 0x7f25f2f4aa7c in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f25f2f4b4fb in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f25f2f4b6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f25f9da199b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f25f9d469fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f25f9b6523a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f25f9b6a17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f25f4fcc6db in start_thread (arg=0x7f247db2b700) at pthread_create.c:463 #8 0x7f25f924d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f24449ad700 (LWP 4505)): #0 0x7f25f2f91649 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f25f2f4ab33 in g_main_context_prepare () at /usr/lib/x86_64-linux-
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #44 from Ekkehard Blanz --- > Tldr: It's not a bug in KMail or Akonadi but a Google not being happy with > KMail privacy policy. I don't understand what this means in practical terms. Does it matter whether we call it a Kmail / Akonadi bug or Google being unhappy with what it does? After all, we are talking about gmail. The way I see it (and maybe I am wrong, then tell me) it can be fixed two ways: One is to convince Google that they are wrong and change their ways, the other would be to say we accept it as a feature bug and we fix it to make Google happy. I frankly don't care which route is taken as long as it gets done. If it was me, I knew which basket to put my eggs in, but I wouldn't impose... On Friday, August 16, 2019 5:14:22 AM PDT carl wrote: > https://bugs.kde.org/show_bug.cgi?id=404990 > > carl changed: > >What|Removed |Added > > CC||schwanc...@protonmail.com > > --- Comment #43 from carl --- > https://www.reddit.com/r/kde/comments/cj7t7c/kmail_doesnt_let_me_sign_in_wit > h_gmail/evccssj/ > > Tldr: It's not a bug in KMail or Akonadi but a Google not being happy with > KMail privacy policy. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #35 from Ekkehard Blanz --- Yup - I could have made that clearer. I mentioned the "other bug" just to help prioritize this bug, as "my bug" annihilates the only workaround. > I'll reopen your report then (you should have been able to do that yourself btw... ;-) ) I didn't know that I could do that. But let me take this opportunity to say that here my ignorance is really bliss, as this ignorance stems from having to file KDE bug reports only VERY rarely (once in several years as a moderate user), which, and that cannot be stressed enough, is a darn good thing!!! On Fri, Aug 9, 2019 at 5:28 AM Wolfgang Bauer wrote: > https://bugs.kde.org/show_bug.cgi?id=404990 > > --- Comment #34 from Wolfgang Bauer --- > (In reply to Ekkehard Blanz from comment #33) > > But what > > about the "Custom Account" route not letting me fully customize the > > settings, but instead forcing me to use the (broken) Google > authentication > > method as soon as it detects the Google IMAP server? In "Custom" mode, I > > should be in full control of all settings, even to mess them up royally > if > > I so desire - no? > I see, so your bug report actually was about not being able to change the > settings, which of course is not a duplicate of this. > I'll reopen your report then (you should have been able to do that yourself > btw... ;-) ) > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #33 from Ekkehard Blanz --- Sure Wolfgang, the Google authentication not working I can see as an issue between the Google Goliath and the Akonadi PIM David (guess who's gonna win). But what about the "Custom Account" route not letting me fully customize the settings, but instead forcing me to use the (broken) Google authentication method as soon as it detects the Google IMAP server? In "Custom" mode, I should be in full control of all settings, even to mess them up royally if I so desire - no? Ekkehard On Thu, Aug 8, 2019 at 2:57 AM Wolfgang Bauer wrote: > https://bugs.kde.org/show_bug.cgi?id=404990 > > Wolfgang Bauer changed: > >What|Removed |Added > > > CC||wba...@tmo.at > > --- Comment #32 from Wolfgang Bauer --- > Apparently it's not really a bug in the software, but rather a policy > problem > that needs to be solved. > https://mail.kde.org/pipermail/kde-pim/2019-August/042400.html > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 410700] New: kmail no longer allows addition of gmail account
https://bugs.kde.org/show_bug.cgi?id=410700 Bug ID: 410700 Summary: kmail no longer allows addition of gmail account Product: kontact Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: ekkehard.bl...@gmail.com Target Milestone: --- SUMMARY kmail no longer allows me to create a new gmail account using the standard method where authentication is "gmail," giving me the following error message: "Sign in with Google temporarily disabled for this app This app has not been verified yet by Google in order to use Google Sign In." The workaround, using a "Custom Account..." also does not work as it insists that the authentication method be "gmail" as soon as I enter imap.gmail.com as the IMAP server, but, as mentioned above, this method does not work. I need it to be "PLAIN" to work. STEPS TO REPRODUCE 1. Select "Configure KMail" 2. Click "Add..." 3. Select "Custom Account..." and select IMAP E-Mail Server 4. Enter "imap.gmail.com" as the IMAP Server 5. Since every further choice is grayed out, click "OK" 6. Go through the Google sign-in process and observes the error message "Sign in with Google temporarily disabled for this app This app has not been verified yet by Google in order to use Google Sign In." OBSERVED RESULT As soon as "imap.gmail.com" is entered as the IMAP Server, the Password field is grayed out, and in the "Advanced" field, "Authentication" is fixed to "Gmail", which then fails to authenticate EXPECTED RESULT a) When Google authentication is offered, it should work. b) In the "manual" or "Custom" mode, I should be in full control and enter "Plain" in the authentication method instead of "gmail," so I can work around the bug in a) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 Kernel Version: 4.15.0-55-generic ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 388331] New: Kontact crashes when trying to savelist of emails to address book
https://bugs.kde.org/show_bug.cgi?id=388331 Bug ID: 388331 Summary: Kontact crashes when trying to savelist of emails to address book Product: kontact Version: 5.1.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ekkehard.bl...@gmail.com Target Milestone: --- Application: kontact (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-83-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: I wrote an email to a list of three recipients. Then I tried to save this recipient list to the address book, which cause Kontact to segfault. -- 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 0x7f9481d7c940 (LWP 7384))] Thread 38 (Thread 0x7f936adec700 (LWP 19589)): #0 0x7f949b02370d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f949483e38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f949483e49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f949bb667eb in QEventDispatcherGlib::processEvents (this=0x7f9354011650, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f949bb0db4a in QEventLoop::exec (this=this@entry=0x7f936adebc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f949b92a834 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f949b92f7be in QThreadPrivate::start (arg=0x9370360) at thread/qthread_unix.cpp:331 #7 0x7f94950686ba in start_thread (arg=0x7f936adec700) at pthread_create.c:333 #8 0x7f949b02f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 37 (Thread 0x7f9370bac700 (LWP 19588)): #0 0x7f949483d990 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f949483e2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f949483e49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f949bb667eb in QEventDispatcherGlib::processEvents (this=0x7f933c0077e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f949bb0db4a in QEventLoop::exec (this=this@entry=0x7f9370babc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f949b92a834 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f949b92f7be in QThreadPrivate::start (arg=0x93ca2d0) at thread/qthread_unix.cpp:331 #7 0x7f94950686ba in start_thread (arg=0x7f9370bac700) at pthread_create.c:333 #8 0x7f949b02f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 36 (Thread 0x7f9387fff700 (LWP 3518)): #0 0x7f9494882a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f949483db41 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f949483e307 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f949483e49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f949bb667eb in QEventDispatcherGlib::processEvents (this=0x7f937c11bfe0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f949bb0db4a in QEventLoop::exec (this=this@entry=0x7f9387ffec80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f949b92a834 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f949b92f7be in QThreadPrivate::start (arg=0x9160a90) at thread/qthread_unix.cpp:331 #8 0x7f94950686ba in start_thread (arg=0x7f9387fff700) at pthread_create.c:333 #9 0x7f949b02f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 35 (Thread 0x7f939db05700 (LWP 20859)): #0 0x7f9494882a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f949483d464 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f949483e346 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f949483e49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f949bb667eb in QEventDispatcherGlib::processEvents (this=0x7f938c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f949bb0db4a in QEventLoop::exec (this=this@entry=0x7f939db04c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f949b92a834 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f949b92f7be in QThreadPrivate::start (arg=0x8e256e0) at thread/qthread_unix.cpp:331 #8 0x7f94950686ba in start_thread (arg=0x7f939db05700) at pthread_create.c:333 #9 0x7f949b02f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 34 (Thread 0x7f939e306700 (LWP 20857)): #0 0x7f9494882a79 in g_mutex_lock () from /lib/x86_6
[kmail2] [Bug 372708] New: Kmail stopped working
https://bugs.kde.org/show_bug.cgi?id=372708 Bug ID: 372708 Summary: Kmail stopped working Product: kmail2 Version: 5.1.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ekkehard.bl...@gmail.com Target Milestone: --- Kmail was working fine for me using a gmail IMAP account - for years. After upgrading to Kubuntu 16.04 LTS it started to show occasional problems loading emails in the preview pane. Double clicking on the mail item to display it in its own window usually fixed the problem temporarily. But the time it took to do that got longer and longer. Now it stopped working entirely (I know it sounds a little weird and amateurish - but this is what I observed). After a reboot, I get all my mail, but not after that anymore (without additional akonadi restarting actions). Restarting kmail won't help - "akonadictl restart" does fix the problem. The error message (at the bottom of the kmail window) is "Unable to fetch item from backend (collection -1): Unable to retrieve item from resource: Job cancelled" If I would not know how to restart akonadi, this would render the kmail version that comes with 16.04 LTS useless. With restarting akonadictl, I have a usable workaround. Please let me know if you need any additional information, logs, etc. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368349] New: Kmail failed to display new emails and crashed upon exit
https://bugs.kde.org/show_bug.cgi?id=368349 Bug ID: 368349 Summary: Kmail failed to display new emails and crashed upon exit Product: kmail2 Version: 5.1.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ekkehard.bl...@gmail.com Application: kmail (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-36-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: After running over night, kmail failed to show newly arrived emil messages the next morning. When I closed it (in hopes a restart would solve the problem - which it did), kmail crashed. I am afraid, that's all I can say about this crash. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6424e18940 (LWP 13311))] Thread 19 (Thread 0x7f6370951700 (LWP 14125)): #0 0x7f643bbaeaf0 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f643bb6a24d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f643bb6a4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6445f86a9b in QEventDispatcherGlib::processEvents (this=0x7f636c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f6445f2ddea in QEventLoop::exec (this=this@entry=0x7f6370950c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f6445d4a8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f6445d4f84e in QThreadPrivate::start (arg=0x867600) at thread/qthread_unix.cpp:331 #7 0x7f643c08b6fa in start_thread (arg=0x7f6370951700) at pthread_create.c:333 #8 0x7f644544fb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7f6386470700 (LWP 13360)): #0 0x7f644543f9cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f643bbad740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f643bb69e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f643bb6a340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f643bb6a4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6445f86a9b in QEventDispatcherGlib::processEvents (this=0x7f63780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f6445f2ddea in QEventLoop::exec (this=this@entry=0x7f638646fc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f6445d4a8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7f6445d4f84e in QThreadPrivate::start (arg=0xcc2f80) at thread/qthread_unix.cpp:331 #9 0x7f643c08b6fa in start_thread (arg=0x7f6386470700) at pthread_create.c:333 #10 0x7f644544fb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7f6387055700 (LWP 13356)): #0 0x7f643bb69802 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f643bb6a2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f643bb6a4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6445f86a9b in QEventDispatcherGlib::processEvents (this=0x7f63740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f6445f2ddea in QEventLoop::exec (this=this@entry=0x7f6387054c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f6445d4a8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f6445d4f84e in QThreadPrivate::start (arg=0xf6c030) at thread/qthread_unix.cpp:331 #7 0x7f643c08b6fa in start_thread (arg=0x7f6387055700) at pthread_create.c:333 #8 0x7f644544fb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7f6387ded700 (LWP 13351)): #0 0x7f643bbaeae7 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f643bb69c09 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f643bb6a317 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f643bb6a4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6445f86a9b in QEventDispatcherGlib::processEvents (this=0x7f637c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f6445f2ddea in QEventLoop::exec (this=this@entry=0x7f6387decc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f6445d4a8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f6445d4f84e in QThreadPrivate::start (arg=0xbb8b00) at thread/qthread_unix.cpp:331 #8 0x7f643c08b6fa in start_thread (arg=0x7f6387ded700) at pthread_create.c:333 #9 0x7f644544fb5d in clone () at ../sysdeps/unix/sys
[kontact] [Bug 336361] New: Kmail crashes while trying to open the gmail inbox
https://bugs.kde.org/show_bug.cgi?id=336361 Bug ID: 336361 Summary: Kmail crashes while trying to open the gmail inbox Classification: Unclassified Product: kontact Version: 4.13.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ekkehard.bl...@gmail.com Application: kontact (4.13.1) KDE Platform Version: 4.13.1 Qt Version: 4.8.6 Operating System: Linux 3.13.0-29-generic x86_64 Distribution: Ubuntu 14.04 LTS -- Information about the crash: After a Kmail upgrade/restart, two Kmail windows opened even though only one was up before the restart. I closed the one labeled <2>, then tried to open my gmail inbox in the other. This is when it crashed on me. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f631393e800 (LWP 2972))] Thread 5 (Thread 0x7f62f3b65700 (LWP 2977)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f630e6e981d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f630e6e9859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f630ae0b182 in start_thread (arg=0x7f62f3b65700) at pthread_create.c:312 #4 0x7f6310ebd30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f62b3262700 (LWP 3015)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f630e42a20d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f630e718fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f630ae0b182 in start_thread (arg=0x7f62b3262700) at pthread_create.c:312 #4 0x7f6310ebd30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f62a9df7700 (LWP 3352)): #0 0x7f6310eaffbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f630a92bfe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f630a92c0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f63116367be in QEventDispatcherGlib::processEvents (this=0x7f62a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x7f63116080af in QEventLoop::processEvents (this=this@entry=0x7f62a9df6de0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f63116083a5 in QEventLoop::exec (this=this@entry=0x7f62a9df6de0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f6311504c5f in QThread::exec (this=) at thread/qthread.cpp:537 #7 0x7f631150732f in QThreadPrivate::start (arg=0x14563d0) at thread/qthread_unix.cpp:349 #8 0x7f630ae0b182 in start_thread (arg=0x7f62a9df7700) at pthread_create.c:312 #9 0x7f6310ebd30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f6298c11700 (LWP 3830)): #0 0x7f6310eaffbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f630a92bfe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f630a92c0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f63116367be in QEventDispatcherGlib::processEvents (this=0x7f62940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x7f63116080af in QEventLoop::processEvents (this=this@entry=0x7f6298c10da0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f63116083a5 in QEventLoop::exec (this=this@entry=0x7f6298c10da0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f6311504c5f in QThread::exec (this=this@entry=0x225fae0) at thread/qthread.cpp:537 #7 0x7f63115e9823 in QInotifyFileSystemWatcherEngine::run (this=0x225fae0) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7f631150732f in QThreadPrivate::start (arg=0x225fae0) at thread/qthread_unix.cpp:349 #9 0x7f630ae0b182 in start_thread (arg=0x7f6298c11700) at pthread_create.c:312 #10 0x7f6310ebd30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f631393e800 (LWP 2972)): [KCrash Handler] #6 0x7f6310df8f79 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x7f6310dfc388 in __GI_abort () at abort.c:89 #8 0x7f63111e86b5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7f63111e6836 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f63111e6863 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7f63111e733f in __cxa_pure_virtual () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x7f62a2cc4b28 in MailCommon::FolderCollection::FolderCollection (this=0x132e430, col=..., writeconfig=) at ../../mailcommon/folder/foldercollection.cpp:73 #13 0x0
[Akonadi] [Bug 325478] New: Kontact crashed while sending queued message
https://bugs.kde.org/show_bug.cgi?id=325478 Bug ID: 325478 Summary: Kontact crashed while sending queued message Classification: Unclassified Product: Akonadi Version: 4.10 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: er...@kde.org Reporter: ekkehard.bl...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.10) KDE Platform Version: 4.10.5 Qt Version: 4.8.4 Operating System: Linux 3.8.0-31-generic x86_64 Distribution: Ubuntu 13.04 -- Information about the crash: I was trying to send a message queued in the outbox when Kontact suddenly crashed. The WLAN connection was very flaky at the time - may have had something to do with it? -- Backtrace: Application: Google Mail (Ekkehard.Blanz) of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0abf1487c0 (LWP 2720))] Thread 6 (Thread 0x7f0aab890700 (LWP 2763)): #0 0x7f0abab7cb0d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f0ab99086cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0ab98c9d3c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0ab98ca175 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0ab98ca304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0abe574036 in QEventDispatcherGlib::processEvents (this=0x7f0aa40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f0abe54438f in QEventLoop::processEvents (this=this@entry=0x7f0aab88fda0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f0abe544618 in QEventLoop::exec (this=this@entry=0x7f0aab88fda0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f0abe446410 in QThread::exec (this=this@entry=0xe8f570) at thread/qthread.cpp:542 #9 0x7f0abd1a9b2a in KIMAP::SessionThread::run (this=0xe8f570) at ../../kimap/sessionthread.cpp:184 #10 0x7f0abe448bec in QThreadPrivate::start (arg=0xe8f570) at thread/qthread_unix.cpp:338 #11 0x7f0aba1e3f8e in start_thread (arg=0x7f0aab890700) at pthread_create.c:311 #12 0x7f0abab8ae1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 5 (Thread 0x7f0aab08f700 (LWP 4417)): #0 0x7f0abab7e3cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f0ab98ca1dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0ab98ca304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0abe574036 in QEventDispatcherGlib::processEvents (this=0x7f0a9c002a20, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f0abe54438f in QEventLoop::processEvents (this=this@entry=0x7f0aab08eda0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f0abe544618 in QEventLoop::exec (this=this@entry=0x7f0aab08eda0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f0abe446410 in QThread::exec (this=this@entry=0xf33bd0) at thread/qthread.cpp:542 #7 0x7f0abd1a9b2a in KIMAP::SessionThread::run (this=0xf33bd0) at ../../kimap/sessionthread.cpp:184 #8 0x7f0abe448bec in QThreadPrivate::start (arg=0xf33bd0) at thread/qthread_unix.cpp:338 #9 0x7f0aba1e3f8e in start_thread (arg=0x7f0aab08f700) at pthread_create.c:311 #10 0x7f0abab8ae1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 4 (Thread 0x7f0aaa26a700 (LWP 4453)): #0 0x7f0ab99095d8 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0ab98c9493 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0ab98ca188 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0ab98ca304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0abe574036 in QEventDispatcherGlib::processEvents (this=0x7f0aa000a030, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f0abe54438f in QEventLoop::processEvents (this=this@entry=0x7f0aaa269da0, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f0abe544618 in QEventLoop::exec (this=this@entry=0x7f0aaa269da0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f0abe446410 in QThread::exec (this=this@entry=0x101c300) at thread/qthread.cpp:542 #8 0x7f0abd1a9b2a in KIMAP::SessionThread::run (this=0x101c300) at ../../kimap/sessionthread.cpp:184 #9 0x7f0abe448bec in QThreadPrivate::start (arg=0x101c300) at thread/qthread_unix.cpp:338 #10 0x7f0aba1e3f8e in start_thread (arg=0x7f0aaa26a700) at pthread_create.c:311 #11 0x7f0abab8ae1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7f0aa9655700 (LWP 6242)): #0 0x7f0abab7e3cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1
[Bug 304449] New: kontact crashes upon exit after failed move
https://bugs.kde.org/show_bug.cgi?id=304449 Bug ID: 304449 Severity: crash Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kontact crashes upon exit after failed move Classification: Unclassified OS: Linux Reporter: ekkehard.bl...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.4) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.1 Operating System: Linux 3.2.0-27-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: I was trying to move an E-mail from my gmail inbox to a different gmail folder. This operation failed for unknown reasons. Then I tried to close kontact, since I didn't trust it anymore. When I closed it, it 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 0x7ffa825227c0 (LWP 14545))] Thread 6 (Thread 0x7ffa6584b700 (LWP 14546)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7ffa7ed20dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7ffa7ed20f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7ffa7a1e4e9a in start_thread (arg=0x7ffa6584b700) at pthread_create.c:308 #4 0x7ffa7fa524bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 5 (Thread 0x7ffa64f4a700 (LWP 14547)): #0 0x7ffa7fa46b03 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7ffa79d18036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffa79d18164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffa801c7426 in QEventDispatcherGlib::processEvents (this=0x7ffa68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7ffa80196c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7ffa80196ed7 in QEventLoop::exec (this=0x7ffa64f49dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7ffa80095fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7ffa80098fcb in QThreadPrivate::start (arg=0x733860) at thread/qthread_unix.cpp:298 #8 0x7ffa7a1e4e9a in start_thread (arg=0x7ffa64f4a700) at pthread_create.c:308 #9 0x7ffa7fa524bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 4 (Thread 0x7ffa0d988700 (LWP 14565)): #0 0x7ffa7fa46b03 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7ffa79d18036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffa79d18164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffa801c7426 in QEventDispatcherGlib::processEvents (this=0x7ffa040008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7ffa80196c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7ffa80196ed7 in QEventLoop::exec (this=0x7ffa0d987d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7ffa80095fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7ffa801769ff in QInotifyFileSystemWatcherEngine::run (this=0x29372c0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7ffa80098fcb in QThreadPrivate::start (arg=0x29372c0) at thread/qthread_unix.cpp:298 #9 0x7ffa7a1e4e9a in start_thread (arg=0x7ffa0d988700) at pthread_create.c:308 #10 0x7ffa7fa524bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 3 (Thread 0x7ffa03fff700 (LWP 15480)): #0 0x7ffa79d5334f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ffa79d53599 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffa79d17ff1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffa79d18164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffa801c7426 in QEventDispatcherGlib::processEvents (this=0x7ff9fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7ffa80196c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x7ffa80196ed7 in QEventLoop::exec (this=0x7ffa03ffed90, flags=...) at kernel/qeventloop.cpp:204 #7 0x7ffa80095fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x7ffa801769ff in QInotifyFileSystemWatcherEngine::run (this=0x3813740) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x7ffa80098fcb in QThreadPrivate::start (arg=0x3813740) at thread/qthread_unix.cpp:298 #10 0x7ffa7a1e4e9a in start_thread (arg=0x7ffa03fff700) at pthread_create.c:308 #11 0x7ffa7fa524bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x00
[Bug 300727] New: kmail crashes upon start up
https://bugs.kde.org/show_bug.cgi?id=300727 Bug ID: 300727 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail crashes upon start up Classification: Unclassified OS: Linux Reporter: ekkehard.bl...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.2.0-24-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: When I was trying to open Kontact, there were lots of Ubuntu sorry messages concerning virtuoso-t and friends and then kmail 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 0x7fca9211d7c0 (LWP 3682))] Thread 5 (Thread 0x7fca75459700 (LWP 3683)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fca8e923dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fca8e923f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fca89deae9a in start_thread (arg=0x7fca75459700) at pthread_create.c:308 #4 0x7fca8f6554bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7fca74b58700 (LWP 3684)): #0 0x7fffa0dff70c in ?? () #1 0x7fffa0dff959 in ?? () #2 0x7fca8814e15d in __GI_clock_gettime (clock_id=, tp=) at ../sysdeps/unix/clock_gettime.c:116 #3 0x7fca8fcf2bb4 in do_gettime (frac=0x7fca74b57ba8, sec=0x7fca74b57ba0) at tools/qelapsedtimer_unix.cpp:123 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #5 0x7fca8fdcab8d in QTimerInfoList::updateCurrentTime (this=0x7fca70002860) at kernel/qeventdispatcher_unix.cpp:343 #6 0x7fca8fdcaec3 in QTimerInfoList::timerWait (this=0x7fca70002860, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #7 0x7fca8fdc997c in timerSourcePrepareHelper (src=, timeout=0x7fca74b57c5c) at kernel/qeventdispatcher_glib.cpp:136 #8 0x7fca8991d71e in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7fca8991df1b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7fca8991e124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fca8fdca426 in QEventDispatcherGlib::processEvents (this=0x7fca78c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #12 0x7fca8fd99c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #13 0x7fca8fd99ed7 in QEventLoop::exec (this=0x7fca74b57dc0, flags=...) at kernel/qeventloop.cpp:204 #14 0x7fca8fc98fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #15 0x7fca8fc9bfcb in QThreadPrivate::start (arg=0xe3a900) at thread/qthread_unix.cpp:298 #16 0x7fca89deae9a in start_thread (arg=0x7fca74b58700) at pthread_create.c:308 #17 0x7fca8f6554bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #18 0x in ?? () Thread 3 (Thread 0x7fca275d1700 (LWP 3703)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:39 #1 0x7fca8fc9aa9b in _q_futex (val2=0, addr2=0x0, timeout=0x0, val=2, op=0, addr=0x121b200) at thread/qmutex_unix.cpp:99 #2 QMutexPrivate::wait (this=0x121b200, timeout=) at thread/qmutex_unix.cpp:113 #3 0x7fca8fc9686d in QMutex::lockInternal (this=) at thread/qmutex.cpp:450 #4 0x7fca837210fa in ?? () from /usr/lib/libsopranoclient.so.1 #5 0x7fca837211c9 in ?? () from /usr/lib/libsopranoclient.so.1 #6 0x7fca8fc9a2a0 in QThreadStorageData::finish (p=0x1510cf8) at thread/qthreadstorage.cpp:203 #7 0x7fca8fc9adf7 in QThreadPrivate::finish (arg=0x1511580) at thread/qthread_unix.cpp:321 #8 0x7fca8fc9bfd3 in ~__pthread_cleanup_class (this=, __in_chrg=) at /usr/include/pthread.h:545 #9 ~__pthread_cleanup_class (this=, __in_chrg=) at thread/qthread_unix.cpp:716 #10 QThreadPrivate::start (arg=0x1511580) at thread/qthread_unix.cpp:300 #11 0x7fca89deae9a in start_thread (arg=0x7fca275d1700) at pthread_create.c:308 #12 0x7fca8f6554bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 2 (Thread 0x7fca260e8700 (LWP 3718)): #0 0x7fca8991d620 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fca8991df1b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fca8991e124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fca8fdca426 in QEventDispatcherGlib::processEvents (this=0x7fca180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fca8fd99c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fca8fd99ed7 in QEven
[Bug 299642] New: Kontact crashes when moving a file from one folder to another in an IMAP setting
https://bugs.kde.org/show_bug.cgi?id=299642 Bug ID: 299642 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashes when moving a file from one folder to another in an IMAP setting Classification: Unclassified OS: Linux Reporter: ekkehard.bl...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.7.3) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-19-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: just moved a piece of E-mail from the inbox to another folder - kontact crashed. -- Backtrace: Application: Kontact (kontact), signal: Aborted [Current thread is 1 (Thread 0x7fcfc91457a0 (LWP 27850))] Thread 6 (Thread 0x7fcfaef22700 (LWP 27851)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fcfc599fc2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fcfc599fd59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fcfc0d97efc in start_thread (arg=0x7fcfaef22700) at pthread_create.c:304 #4 0x7fcfc66af59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 5 (Thread 0x7fcfae621700 (LWP 27852)): #0 0x7fcfc66a3473 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fcfc02c9f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcfc02ca429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcfc7aebf3e in QEventDispatcherGlib::processEvents (this=0x1dbf880, flags=) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fcfc7abfcf2 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fcfc7abfef7 in QEventLoop::exec (this=0x7fcfae620de0, flags=...) at kernel/qeventloop.cpp:201 #6 0x7fcfc79d727f in QThread::exec (this=) at thread/qthread.cpp:498 #7 0x7fcfc79d9d05 in QThreadPrivate::start (arg=0x1db12c0) at thread/qthread_unix.cpp:331 #8 0x7fcfc0d97efc in start_thread (arg=0x7fcfae621700) at pthread_create.c:304 #9 0x7fcfc66af59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 4 (Thread 0x7fcf5e0ed700 (LWP 27873)): #0 0x7fcfc66a3473 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fcfc02c9f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcfc02ca429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcfc7aebf3e in QEventDispatcherGlib::processEvents (this=0x7fcfa8012be0, flags=) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fcfc7abfcf2 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fcfc7abfef7 in QEventLoop::exec (this=0x7fcf5e0ecdb0, flags=...) at kernel/qeventloop.cpp:201 #6 0x7fcfc79d727f in QThread::exec (this=) at thread/qthread.cpp:498 #7 0x7fcfc7aa2cbf in QInotifyFileSystemWatcherEngine::run (this=0x3e730e0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fcfc79d9d05 in QThreadPrivate::start (arg=0x3e730e0) at thread/qthread_unix.cpp:331 #9 0x7fcfc0d97efc in start_thread (arg=0x7fcf5e0ed700) at pthread_create.c:304 #10 0x7fcfc66af59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 3 (Thread 0x7fcf598e4700 (LWP 30313)): #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 #1 0x7fcfc664c62f in _L_lock_10501 () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7fcfc664a9c1 in __GI___libc_free (mem=0x7fcfc69681c0) at malloc.c:3736 #3 0x7fcfc7aeb665 in socketNotifierSourceCheck (source=0x6d524b0) at kernel/qeventdispatcher_glib.cpp:92 #4 0x7fcfc02c9734 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fcfc02c9f82 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fcfc02ca429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fcfc7aebed6 in QEventDispatcherGlib::processEvents (this=0x6d4b010, flags=) at kernel/qeventdispatcher_glib.cpp:422 #8 0x7fcfc7abfcf2 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #9 0x7fcfc7abfef7 in QEventLoop::exec (this=0x7fcf598e3db0, flags=...) at kernel/qeventloop.cpp:201 #10 0x7fcfc79d727f in QThread::exec (this=) at thread/qthread.cpp:498 #11 0x7fcfc7aa2cbf in QInotifyFileSystemWatcherEngine::run (this=0x6d4a4c0) at io/qfilesystemwatcher_inotify.cpp:248 #12 0x7fcfc79d9d05 in QThreadPrivate::start (arg=0x6d4a4c0) at thread/qthread_unix.cpp:331 #13 0x7fcfc0d97efc in start_thread (arg=0x7fcf598e4700) at pthread_create.
[Bug 296519] Kontact crashed upon exit after spooling hundrets of IMAP errors in the notification area
https://bugs.kde.org/show_bug.cgi?id=296519 --- Comment #1 from Ekkehard Blanz --- Created attachment 70019 --> https://bugs.kde.org/attachment.cgi?id=70019&action=edit New crash information added by DrKonqi akonadi_imap_resource (4.7) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4 - What I was doing when the application crashed: I was restarting the whole computer because the IMAP error messages kept popping up even after I had shut down Kmail. - Unusual behavior I noticed: literally hundreds of IMAP error messages saying that the connection to the server was lost. -- Backtrace (Reduced): #6 0x7f551efef712 in QObject::disconnect (sender=0x1e2d7c0, signal=0x19f5f69 "connectionLost()", receiver=0x19f76b0, method=0x19f5dd9 "onEarlyConnectionLost()") at kernel/qobject.cpp:2728 #7 0x00453931 in SessionPool::killSession (this=0x19f76b0, session=0x1e2d7c0, termination=SessionPool::LogoutSession) at ../../../resources/imap/sessionpool.cpp:177 #8 0x00453ef5 in SessionPool::disconnect (this=0x19f76b0, termination=SessionPool::LogoutSession) at ../../../resources/imap/sessionpool.cpp:119 #9 0x00453ff7 in SessionPool::~SessionPool (this=0x19f76b0, __in_chrg=) at ../../../resources/imap/sessionpool.cpp:56 #10 0x004540e9 in SessionPool::~SessionPool (this=0x19f76b0, __in_chrg=) at ../../../resources/imap/sessionpool.cpp:57 -- 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 296519] Kontact crashed upon exit after spooling hundrets of IMAP errors in the notification area
https://bugs.kde.org/show_bug.cgi?id=296519 Ekkehard Blanz changed: What|Removed |Added CC||ekkehard.bl...@gmail.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 294401] New: Kontact crashed upon exit
https://bugs.kde.org/show_bug.cgi?id=294401 Summary: Kontact crashed upon exit Product: Akonadi Version: 4.7 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: IMAP resource AssignedTo: er...@kde.org ReportedBy: ekkehard.bl...@gmail.com CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_imap_resource (4.7) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-16-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: I was trying to shut down Kontact because something was eating up all the CPU cycles on two of my six cores. Top didn't show what it was, but Kontact (Kmail had been the culprit before). When I tried to shut it down, it crashed,. -- Backtrace: Application: Google Mail of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault [Current thread is 1 (Thread 0x7f65884a7780 (LWP 2516))] Thread 2 (Thread 0x7f6567fff700 (LWP 27631)): #0 0x7f6583ecd773 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f658281ff68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6582820429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6587919f3e in QEventDispatcherGlib::processEvents (this=0x178c250, flags=) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f65878edcf2 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f65878edef7 in QEventLoop::exec (this=0x7f6567ffede0, flags=...) at kernel/qeventloop.cpp:201 #6 0x7f658780527f in QThread::exec (this=) at thread/qthread.cpp:498 #7 0x7f658652bc13 in KIMAP::SessionThread::run (this=0x1781740) at ../../kimap/sessionthread.cpp:169 #8 0x7f6587807d05 in QThreadPrivate::start (arg=0x1781740) at thread/qthread_unix.cpp:331 #9 0x7f6583788efc in start_thread (arg=0x7f6567fff700) at pthread_create.c:304 #10 0x7f6583ed989d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f65884a7780 (LWP 2516)): [KCrash Handler] #6 0x0067db00 in vtable for __cxxabiv1::__si_class_type_info () #7 0x7f6587901714 in QObject::disconnect (sender=0x7f6568023f50, signal=0x171fef9 "connectionLost()", receiver=0x15d84c0, method=0x16446c9 "onEarlyConnectionLost()") at kernel/qobject.cpp:2728 #8 0x00453931 in SessionPool::killSession (this=0x15d84c0, session=0x7f6568023f50, termination=SessionPool::LogoutSession) at ../../../resources/imap/sessionpool.cpp:177 #9 0x00453ef5 in SessionPool::disconnect (this=0x15d84c0, termination=SessionPool::LogoutSession) at ../../../resources/imap/sessionpool.cpp:119 #10 0x004168c3 in ImapResource::doSetOnline (this=0x15c3ff0, online=false) at ../../../resources/imap/imapresource.cpp:421 #11 0x7f6587f19ee8 in Akonadi::AgentBase::setOnline (this=0x15c3ff0, state=false) at ../../akonadi/agentbase.cpp:630 #12 0x7f658804f9c0 in Akonadi__StatusAdaptor::qt_metacall (this=0x15aacf0, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7fffd4856950) at statusadaptor.moc:129 #13 0x7f6587c460e9 in QDBusConnectionPrivate::deliverCall (this=0x1509760, object=0x15aacf0, msg=..., metaTypes=..., slotIdx=12) at qdbusintegrator.cpp:942 #14 0x7f6587c4725c in QDBusConnectionPrivate::activateCall (this=0x1509760, object=0x15aacf0, flags=273, msg=...) at qdbusintegrator.cpp:852 #15 0x7f6587c47b22 in QDBusConnectionPrivate::activateObject (this=0x1509760, node=..., msg=..., pathStartPos=) at qdbusintegrator.cpp:1410 #16 0x7f6587c47bf8 in QDBusActivateObjectEvent::placeMetaCall (this=0x15ce280) at qdbusintegrator.cpp:1524 #17 0x7f6587905a5e in QObject::event (this=0x15c3ff0, e=) at kernel/qobject.cpp:1217 #18 0x7f6586c9e474 in notify_helper (e=0x15ce280, receiver=0x15c3ff0, this=0x143a450) at kernel/qapplication.cpp:4486 #19 QApplicationPrivate::notify_helper (this=0x143a450, receiver=0x15c3ff0, e=0x15ce280) at kernel/qapplication.cpp:4458 #20 0x7f6586ca32e1 in QApplication::notify (this=0x7fffd4857430, receiver=0x15c3ff0, e=0x15ce280) at kernel/qapplication.cpp:4365 #21 0x7f6584db5466 in KApplication::notify (this=0x7fffd4857430, receiver=0x15c3ff0, event=0x15ce280) at ../../kdeui/kernel/kapplication.cpp:311 #22 0x7f65878eeafc in QCoreApplication::notifyInternal (this=0x7fffd4857430, receiver=0x15c3ff0, event=0x15ce280) at kernel/qcoreapplication.cpp:787 #23 0x7f65878f251f in sendEvent (event=0x15ce280, receiver=0x15c3ff0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1410800) at kernel/qcoreapplication.cpp:1428 #25 0x7f6587919a73 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:2
[Bug 285999] "Nepomuk Indexing Agents Have Been Disabled" error at startup
https://bugs.kde.org/show_bug.cgi?id=285999 Ekkehard Blanz changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 --- Comment #9 from Ekkehard Blanz 2011-12-26 21:12:45 --- *** This bug has been confirmed by popular vote. *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 286203] New: Crashes for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=286203 Summary: Crashes for no apparent reason Product: Akonadi Version: 4.7 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Nepomuk Feeder Agents AssignedTo: to...@kde.org ReportedBy: ekkehard.bl...@gmail.com CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_nepomuk_email_feeder (4.7) KDE Platform Version: 4.7.2 (4.7.2) Qt Version: 4.7.4 Operating System: Linux 3.0.0-12-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: This crash happened while the machine was idle, possibly synchronising the IMAP system. -- Backtrace: Application: Nepomuk EMail Feeder (akonadi_nepomuk_email_feeder), signal: Aborted [KCrash Handler] #7 0x00465416 in __kernel_vsyscall () #8 0x065e2c8f in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #9 0x065e62b5 in __GI_abort () at abort.c:92 #10 0x00bf74ed in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #11 0x00bf5283 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #12 0x00bf52bf in std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #13 0x00bf5464 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #14 0x05d79569 in QEventLoop::exec (this=0xbfc0cb04, flags=...) at kernel/qeventloop.cpp:214 #15 0x05d7e19d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #16 0x01fd78f4 in QApplication::exec () at kernel/qapplication.cpp:3760 #17 0x0025cc91 in Akonadi::AgentBase::init (r=0x8b51ab8) at ../../akonadi/agentbase.cpp:554 #18 0x080553e7 in Akonadi::AgentBase::init (argc=3, argv=0xbfc0cc74) at /usr/include/akonadi/agentbase.h:342 #19 0x0805307b in main (argc=3, argv=0xbfc0cc74) at ../../nepomuk_email_feeder/nepomukemailfeeder.cpp:133 Possible duplicates by query: bug 286172, bug 284718, bug 284551, bug 284524, bug 284453. Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 185544] Kontact is sometimes started twice and crashes when closing the 2nd instance
https://bugs.kde.org/show_bug.cgi?id=185544 --- Comment #156 from Ekkehard Blanz 2011-09-14 17:40:00 --- Created an attachment (id=63648) --> (http://bugs.kde.org/attachment.cgi?id=63648) New crash information added by DrKonqi kontact (4.4.10) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2 - What I was doing when the application crashed: Kontact opens two instances upon login - closing one of them results in crash. -- Backtrace (Reduced): #7 0xb32958a5 in KMFolder::noContent (this=0x9661478) at ../../kmail/kmfolder.cpp:359 #8 0xb32453a1 in KMail::FolderViewItem::updateCounts (this=0x9af8588) at ../../kmail/folderview.cpp:2850 #9 0xb3245738 in KMail::FolderView::updateCountsForChildren (this=0x9aa9780, it=0x91a1b18, tStart=...) at ../../kmail/folderview.cpp:871 #10 0xb32456ba in KMail::FolderView::updateCountsForChildren (this=0x9aa9780, it=0x9aaf248, tStart=...) at ../../kmail/folderview.cpp:843 #11 0xb32457de in KMail::FolderView::slotUpdateCounts (this=0x9aa9780) at ../../kmail/folderview.cpp:904 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 185544] Kontact is sometimes started twice and crashes when closing the 2nd instance
https://bugs.kde.org/show_bug.cgi?id=185544 Ekkehard Blanz changed: What|Removed |Added CC||ekkehard.bl...@gmail.com -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 275420] Sometimes Kontact and dbus-daemon hog two of my 6 cores with 100% each - killing Kontact solves this
https://bugs.kde.org/show_bug.cgi?id=275420 Ekkehard Blanz changed: What|Removed |Added CC||ekkehard.bl...@gmail.com -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 275420] New: Sometimes Kontact and dbus-daemon hog two of my 6 cores with 100% each - killing Kontact solves this
https://bugs.kde.org/show_bug.cgi?id=275420 Summary: Sometimes Kontact and dbus-daemon hog two of my 6 cores with 100% each - killing Kontact solves this Product: kontact Version: 4.4.10 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: ekkehard.bl...@gmail.com Version: 4.4.10 (using KDE 4.6.2) OS:Linux When Kontact runs for more than a day on my otherwise very stable Kubuntu 11.04 64-bit system, it causes dbus-daemon and itself to hog all the CPU cycles they can get. Two of my 6 cores are completely pegged at 100%. When I then kill Kontact, the problem is temporarily solved. Unfortunately, starting Kontact again will bring me right back to that situation. Sometimes Kontact won't even start again while dbus-daemon hogs 100% of a core. I have to restart to be able to run Kontact normally again. Please let me know if there is any other information I should provide the next time it does that. Reproducible: Sometimes Steps to Reproduce: Let sit Kontact for some time - often happens when I come back to the computer in the morning. Actual Results: Two CPU cores are pegged at 100% - would render a single core machine useless. Expected Results: Kontact and dbus-daemon behaving "nice"ly, using less than solid 100% CPU. OS: Linux (x86_64) release 2.6.38-8-generic Compiler: cc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
