[Akonadi] [Bug 373111] Crash During Start Up After Login
https://bugs.kde.org/show_bug.cgi?id=373111 --- Comment #8 from bj.kdede...@bkaj.org --- The issue also seems resolved for me with the latest round of Tumbleweed updates. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 374006] New: Kontact crashes when pressing "New" without any app (mail, calendar) open
https://bugs.kde.org/show_bug.cgi?id=374006 Bug ID: 374006 Summary: Kontact crashes when pressing "New" without any app (mail, calendar) open Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kurt_seeba...@yahoo.de Target Milestone: --- Application: kontact (5.4.0) Qt Version: 5.7.0 Frameworks Version: 5.29.0 Operating System: Linux 4.8.13-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I started Kontact and immediately pressed the "New" dropdown button on the top left. It does not crash if i select Mail in the list of applications and press "New" then. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f73ae0e9e80 (LWP 6000))] Thread 27 (Thread 0x7f72718eb700 (LWP 6072)): #0 0x7f73a69bb10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f739db880d9 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f739db88719 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f739db888d0 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f739db8546c in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f73a69b5454 in start_thread () at /lib64/libpthread.so.0 #6 0x7f73aab1737f in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f7278c0d700 (LWP 6041)): #0 0x7f73aab0e66d in poll () at /lib64/libc.so.6 #1 0x7f73a47c7876 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f73a47c798c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f73ab64479b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f73ab5ee1ea in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f73ab41c8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f73ab421558 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f73a69b5454 in start_thread () at /lib64/libpthread.so.0 #8 0x7f73aab1737f in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f73327fc700 (LWP 6036)): #0 0x7f73a69bb10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f73979f7834 in () at /usr/lib64/libQt5Script.so.5 #2 0x7f73979f7879 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f73a69b5454 in start_thread () at /lib64/libpthread.so.0 #4 0x7f73aab1737f in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f7332ffd700 (LWP 6029)): #0 0x7f73a69bb10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f739d656d00 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f739d63fb30 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f739d63febb in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f739d63bb4a in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f739e8d18de in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f739e8d3c94 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f739e8d3ce5 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f739e8d3db9 in () at /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f739db70efa in () at /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f739db5b995 in () at /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7f739db88e8a in () at /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7f739db8546c in () at /usr/lib64/libQt5WebEngineCore.so.5 #13 0x7f73a69b5454 in start_thread () at /lib64/libpthread.so.0 #14 0x7f73aab1737f in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f73337fe700 (LWP 6028)): #0 0x7f73a69bb10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f739db880d9 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f739db88719 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f739db888d0 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f739db8546c in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f73a69b5454 in start_thread () at /lib64/libpthread.so.0 #6 0x7f73aab1737f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f7333fff700 (LWP 6027)): #0 0x7f73aab0a6dd in read () at /lib64/libc.so.6 #1 0x7f7386b6d641 in pa_read () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #2 0x7f73871fcfce in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0 #3 0x7f73871fda40 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f73871fdb00 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f738720bb29 in () at /usr/lib64/libpulse.so.0 #6 0x7f7386b9c1e8 in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #7 0x7f73a69b5454 in start_threa
[Akonadi] [Bug 368161] Plasma (plasmashell), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=368161 Sven Eden changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #3 from Sven Eden --- Unfortunately I have to add my backtrace by hand. DrKonqi lets me log in and find this report, but when I want to attach my report and click on "continue", nothing happens. :-( The crashing Thread 1 looks similar, but not exactly equal. However, Plasma crashed after I issued "akonadictl stop" in a console. I think that this is odd. I am using: System : Gentoo x86_64 Framework: 5.29.0 Plasma : 5.8.4 Apps : 16.12.0 QT : 5.7.1 GCC : 5.4.0 GLIBC: 2.23 Could this be some sort of race condition? -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5e9c608780 (LWP 16603))] Thread 9 (Thread 0x7f5dcd141700 (LWP 22436)): #0 0x7f5e92f8e4a9 in g_source_iter_next (iter=iter@entry=0x7f5dcd140c80, source=source@entry=0x7f5dcd140c78) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:982 #1 0x7f5e92f90d9a in g_main_context_check (context=context@entry=0x7f5dc8003200, max_priority=2147483647, fds=fds@entry=0x7f5dc80033e0, n_fds=n_fds@entry=1) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3742 #2 0x7f5e92f91400 in g_main_context_iterate (context=context@entry=0x7f5dc8003200, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3926 #3 0x7f5e92f9156c in g_main_context_iteration (context=0x7f5dc8003200, may_block=may_block@entry=1) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990 #4 0x7f5e97894ccb in QEventDispatcherGlib::processEvents (this=0x7f5dc8002700, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f5e9784654a in QEventLoop::exec (this=this@entry=0x7f5dcd140e40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f5e9769de24 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f5e976a206c in QThreadPrivate::start (arg=0x73ce6a0) at thread/qthread_unix.cpp:368 #8 0x7f5e967503a4 in start_thread (arg=0x7f5dcd141700) at pthread_create.c:333 #9 0x7f5e96f4c50d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f5dd5da3700 (LWP 18808)): #0 0x7f5e96f3f45d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f5e92fd6230 in read (__nbytes=16, __buf=0x7f5dd5da2c00, __fd=) at /usr/include/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7f5dd01b0f90) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gwakeup.c:210 #3 0x7f5e92f90f2e in g_main_context_check (context=context@entry=0x7f5dd000f030, max_priority=2147483647, fds=fds@entry=0x7f5dd0351c00, n_fds=n_fds@entry=1) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3707 #4 0x7f5e92f91400 in g_main_context_iterate (context=context@entry=0x7f5dd000f030, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3926 #5 0x7f5e92f9156c in g_main_context_iteration (context=0x7f5dd000f030, may_block=may_block@entry=1) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990 #6 0x7f5e97894ccb in QEventDispatcherGlib::processEvents (this=0x7f5dd01ae230, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f5e9784654a in QEventLoop::exec (this=this@entry=0x7f5dd5da2e20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #8 0x7f5e9769de24 in QThread::exec (this=this@entry=0x1926330) at thread/qthread.cpp:507 #9 0x7f5e99e72895 in QQmlThreadPrivate::run (this=0x1926330) at qml/ftw/qqmlthread.cpp:147 #10 0x7f5e976a206c in QThreadPrivate::start (arg=0x1926330) at thread/qthread_unix.cpp:368 #11 0x7f5e967503a4 in start_thread (arg=0x7f5dd5da3700) at pthread_create.c:333 #12 0x7f5e96f4c50d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f5dde3ac700 (LWP 16878)): #0 0x7f5e92f8e462 in g_source_iter_next (iter=iter@entry=0x7f5dde3abc40, source=source@entry=0x7f5dde3abc38) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:987 #1 0x7f5e92f90d9a in g_main_context_check (context=context@entry=0x7f5dd8000990, max_priority=2147483647, fds=fds@entry=0x7f5dd80048a0, n_fds=n_fds@entry=1) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3742 #2 0x7f5e92f91400 in g_main_context_iterate (context=context@entry=0x7f5dd8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3926 #3 0x7f5e92f9156c in g_main_context_iteration (context=0x7f5dd8000990, may_block=may_block@entry=1) at /home/portage/dev-li
[kontact] [Bug 363024] Kontact 16.12.0: New contact editor misses options to display messages in HTML
https://bugs.kde.org/show_bug.cgi?id=363024 Till Schäfer changed: What|Removed |Added Summary|Kontact 16.08.1: New|Kontact 16.12.0: New |contact editor misses |contact editor misses |options to display messages |options to display messages |in HTML |in HTML Version|GIT (master)|unspecified -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 373111] Crash During Start Up After Login
https://bugs.kde.org/show_bug.cgi?id=373111 --- Comment #7 from Sebastian Kuhne --- It seems that KDE Applications 16.12 stabilize the system. I have not recognized any further plasmashell crashes after the update. It would be great if someone else could confirm that the issue is vanished, then we should close this bug thread. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 329964] Kmail2 5.3.1 does not show the encryption symbol in message list for inline pgp mails
https://bugs.kde.org/show_bug.cgi?id=329964 Till Schäfer changed: What|Removed |Added Version|unspecified |5.3.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 329961] PGP silently fails to encrypt mails for users with different encryption protocols (pgp/mime vs inline pgp)
https://bugs.kde.org/show_bug.cgi?id=329961 Till Schäfer changed: What|Removed |Added Version|5.2.1 |5.3.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 323113] kmail2 ignores the "per contact" settings randomly
https://bugs.kde.org/show_bug.cgi?id=323113 Till Schäfer changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Till Schäfer --- *** This bug has been marked as a duplicate of bug 346212 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 346212] Kontact/KMail-5.3.1 ignores per contact settings about html and external resources synced over dav resource
https://bugs.kde.org/show_bug.cgi?id=346212 --- Comment #2 from Till Schäfer --- *** Bug 323113 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 358313] Akonadi 15.12.1 - IMAP resource: read status sometimes wrong
https://bugs.kde.org/show_bug.cgi?id=358313 Till Schäfer changed: What|Removed |Added Version|GIT (master)|5.3.2 -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 373989] Kmail 5.4 / akonadi agents hogging cpu cores
https://bugs.kde.org/show_bug.cgi?id=373989 --- Comment #1 from PeterF --- I was able to partially resolve the issue, by issuing "akonadictl stop". I have then deleted the "config" and "dat" files in ~/.config/akonadi (maildespatcher, migration_assistant and notes). When I restarted kmail2 it shows only the "akonadi_notes_agent" with 25% usage. Kindly investigate -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN
https://bugs.kde.org/show_bug.cgi?id=311990 --- Comment #19 from Laurent Montel --- (In reply to Nikolay Brookstein from comment #18) > (In reply to Laurent Montel from comment #17) > > For sure I can't investigate this week (Christmas holidays for me) but > > indeed an account which can provide error will help me to investigate for > > sure. > > That would be great! > > Than I will create an account for you and send you login data. > Can I use your *@kde.org address for this? Yep mon...@kde.org > > Merry Christmas Thanks :) > > P.S. Probably the majority is busy with holidays && famirly && friends this > week :D > So I have expected that only after 1-2 weeks it will be possible to try to > find out what is going wrong here. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[kaddressbook] [Bug 369489] please use openstreetmap instead of mapquest
https://bugs.kde.org/show_bug.cgi?id=369489 --- Comment #6 from Laurent Montel --- 5.4.0 is kaddressbook 16.12. Regards (In reply to Philippe ROUBACH from comment #5) > >> FIXED-IN: 5.4.0 > > 5.4.0 of what? > > kaddressbook5 16.08.2 > i don't see any openstreetmap option > > openmapquest is obsolete? > make an address query with openmapquest > then > you get this message > > This version of MapQuest is going away soon. We apologize for any > inconvenience. If you're using a map generated from this site on your > website, please visit our Developer blog for information on how to > transition your map to our updated tiles. > We aren't going away completely, though. Have you checked out the new > MapQuest.com? With faster loading, sleeker and easier to read maps, along > with less intrusive advertising, it's better than ever. Questions? Please > see our FAQs. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 369489] please use openstreetmap instead of mapquest
https://bugs.kde.org/show_bug.cgi?id=369489 --- Comment #5 from Philippe ROUBACH --- >> FIXED-IN: 5.4.0 5.4.0 of what? kaddressbook5 16.08.2 i don't see any openstreetmap option openmapquest is obsolete? make an address query with openmapquest then you get this message This version of MapQuest is going away soon. We apologize for any inconvenience. If you're using a map generated from this site on your website, please visit our Developer blog for information on how to transition your map to our updated tiles. We aren't going away completely, though. Have you checked out the new MapQuest.com? With faster loading, sleeker and easier to read maps, along with less intrusive advertising, it's better than ever. Questions? Please see our FAQs. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 373989] New: Kmail 5.4 / akonadi agents hogging cpu cores
https://bugs.kde.org/show_bug.cgi?id=373989 Bug ID: 373989 Summary: Kmail 5.4 / akonadi agents hogging cpu cores Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Mail Dispatcher Agent Assignee: kdepim-bugs@kde.org Reporter: peter.fink...@inode.at CC: vkra...@kde.org Target Milestone: --- Created attachment 102916 --> https://bugs.kde.org/attachment.cgi?id=102916&action=edit Screenshot of processes running Running Kmail 5.4 on ArchLinux. I have three akonadi agents running wild (see screenshot). Tried to logoff and login again, but it did not fix the problem. I have also tried to abort the processes via "akonadi-console" but this had no effect either. -- You are receiving this mail because: You are the assignee for the bug.
