[Akonadi] [Bug 392092] akonadi_control crash on first start
https://bugs.kde.org/show_bug.cgi?id=392092 --- Comment #11 from PK --- After starting up kmail I get this grey screen. But I can access the settings. When I start the account-wizzard from there after a while the akonadi self-test starts. And again it says that "akonadi is not registered at dbus". -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 392092] akonadi_control crash on first start
https://bugs.kde.org/show_bug.cgi?id=392092 PK changed: What|Removed |Added CC||pieterkristen...@gmail.com --- Comment #10 from PK --- I have the same experience. I think it started from the moment I installed plasma 5.13 on my system. I'm using KDE Neon user build. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 395131] Akonadi consumes all memory
https://bugs.kde.org/show_bug.cgi?id=395131 Karthik Periagaram changed: What|Removed |Added CC||karthik.periaga...@gmail.co ||m -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395538] (Version 5.8.1) KMail wizards are missing
https://bugs.kde.org/show_bug.cgi?id=395538 --- Comment #1 from Christophe Giboudeaux --- Are the plugins enabled ? (in settings / plugins) -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 374761] Event/To-do/Journal editor fails to populate calendar combo box
https://bugs.kde.org/show_bug.cgi?id=374761 --- Comment #6 from Alex Dănilă --- Note: go to Settings->General->Calendar, select "Personal Calendar" click modify, press OK in the calendar modification window without actually modifying anything. The new calendar may be available for use. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 374761] Event/To-do/Journal editor fails to populate calendar combo box
https://bugs.kde.org/show_bug.cgi?id=374761 Alex Dănilă changed: What|Removed |Added CC||nuor...@gmail.com --- Comment #5 from Alex Dănilă --- Can confirm with 5.7.3. What is a good workaround? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395538] New: (Version 5.8.1) KMail wizards are missing
https://bugs.kde.org/show_bug.cgi?id=395538 Bug ID: 395538 Summary: (Version 5.8.1) KMail wizards are missing Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- On KDE Neon, with kdepim-addons installed, the anti-spam/anti-virus wizards do not appear in the Tools menu of KMail. Package status: $ apt-cache policy kdepim-addons spamassassin bogofilter kdepim-addons: Installed: 18.04.1-0neon+16.04+xenial+build39 Candidate: 18.04.1-0neon+16.04+xenial+build39 Version table: *** 18.04.1-0neon+16.04+xenial+build39 500 500 http://archive.neon.kde.org/user xenial/main amd64 Packages 100 /var/lib/dpkg/status 18.04.0-0neon+16.04+xenial+build38 500 500 http://archive.neon.kde.org/user xenial/main amd64 Packages 17.12.3-0neon+16.04+xenial+build36 500 500 http://archive.neon.kde.org/user xenial/main amd64 Packages 17.12.2-0neon+16.04+xenial+build34 500 500 http://archive.neon.kde.org/user xenial/main amd64 Packages spamassassin: Installed: 3.4.1-3 Candidate: 3.4.1-3 Version table: *** 3.4.1-3 500 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu xenial/main i386 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status bogofilter: Installed: 1.2.4+dfsg1-4build1 Candidate: 1.2.4+dfsg1-4build1 Version table: *** 1.2.4+dfsg1-4build1 500 500 http://es.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 392948] Akonadi fails to start on a fresh system (cannot create directory)
https://bugs.kde.org/show_bug.cgi?id=392948 --- Comment #5 from BAKfr --- I dig into this issue and think I've found the root of the problem. On first run, Akonadi is supposed to initialize the database. To do so, it checks the presence of mysql_install_db, and executes it with different arguments depending of the software (mysql or mariadb) and the version. Since MySQL 5.7, mysql_install_db is deprecated. There is a new '--initialize' argument available to replace it, (present in both mysql and mariadb). KDE Neon (and probably others Ubuntu-based distributions) does not include this script in all mysqld package anymore. mysql_install_db isn't present in the path, and so the database initialization is never executed. >From KDE Neon User Edition, the packages "mariadb-server-10.0", "mysql-server-core-5.7" include the script. The packages "mariadb-server-10.0" and "mysql-server-core-5.7" does not. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Matěj Laitl changed: What|Removed |Added CC|ma...@laitl.cz | -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[korganizer] [Bug 283337] Kontact crash after try to open event in calendar
https://bugs.kde.org/show_bug.cgi?id=283337 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com --- Comment #9 from Filipus Klutiero --- Karel, do you still experience this? If so, do you think this is a duplicate of issue #280313? That one talks about clicking Apply, but if I read this one fine, your crash happens before that. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 388019] Korganizer crashes when choosing enter new event.
https://bugs.kde.org/show_bug.cgi?id=388019 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com --- Comment #2 from Filipus Klutiero --- Can you describe how this issue started? Does this happen on a fresh KOrganizer, or were you using it fine before? And can you describe exactly when (at which point of the "event" creation procesure) the crash happens? -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 395526] kontact crashing at start
https://bugs.kde.org/show_bug.cgi?id=395526 --- Comment #1 from Soenke Dibbern --- FWIW: I can start kmail but not korganizer in stand-alone mode. KOrganizer also crashes immediately at start-up. Here's a korganizer crash report: Application: KOrganizer (korganizer), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f474fea2840 (LWP 12244))] Thread 6 (Thread 0x7f4713056700 (LWP 12267)): #0 0x7f474359b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55fc4abb3370) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55fc4abb3320, cond=0x55fc4abb3348) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55fc4abb3348, mutex=0x55fc4abb3320) at pthread_cond_wait.c:655 #3 0x7f4718387b2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f4718387857 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f47435956db in start_thread (arg=0x7f4713056700) at pthread_create.c:463 #6 0x7f474b69f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f4726dee700 (LWP 12259)): #0 0x7ffef5893979 in ?? () #1 0x7ffef5893c30 in clock_gettime () #2 0x7f474b6aeea6 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7f4726dedad0) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7f474c1f8221 in qt_clock_gettime (ts=0x7f4726dedad0, clock=) at kernel/qelapsedtimer_unix.cpp:111 #4 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #5 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #6 0x7f474c1f6a59 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f4714004cf0) at kernel/qtimerinfo_unix.cpp:91 #7 0x7f474c1f7035 in QTimerInfoList::timerWait (this=0x7f4714004cf0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #8 0x7f474c1f867e in timerSourcePrepareHelper (timeout=0x7f4726dedb94, src=) at kernel/qeventdispatcher_glib.cpp:132 #9 timerSourcePrepare (source=, timeout=0x7f4726dedb94) at kernel/qeventdispatcher_glib.cpp:165 #10 0x7f4741736998 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f474173736b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f474173754c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f474c1f890b in QEventDispatcherGlib::processEvents (this=0x7f4714000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #14 0x7f474c19d9ea in QEventLoop::exec (this=this@entry=0x7f4726dedd60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #15 0x7f474bfbc22a in QThread::exec (this=) at thread/qthread.cpp:515 #16 0x7f474bfc116d in QThreadPrivate::start (arg=0x55fc4aafe1a0) at thread/qthread_unix.cpp:368 #17 0x7f47435956db in start_thread (arg=0x7f4726dee700) at pthread_create.c:463 #18 0x7f474b69f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f47275ef700 (LWP 12251)): #0 0x7f474173695e in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f474173736b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f474173754c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f474c1f890b in QEventDispatcherGlib::processEvents (this=0x7f471c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f474c19d9ea in QEventLoop::exec (this=this@entry=0x7f47275eed60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f474bfbc22a in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f474bfc116d in QThreadPrivate::start (arg=0x55fc4aaa8730) at thread/qthread_unix.cpp:368 #7 0x7f47435956db in start_thread (arg=0x7f47275ef700) at pthread_create.c:463 #8 0x7f474b69f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f472c9ea700 (LWP 12246)): #0 0x7f474177ccd9 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f474173741f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f474173754c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f474c1f890b in QEventDispatcherGlib::processEvents (this=0x7f472b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f474c19d9ea in QEventLoop::exec (this=this@entry=0x7f472c9e9d30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f474bfbc22a in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f474ab43d45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f474bfc116d in QThreadPrivate::start (arg=0x7f474adb6d60) at thread/qthread_unix.cpp:368 #8 0x7f47435956db in start_thread (arg=0x7f472c9ea700) at pthread_create.c:463 #9 0x7f474b69f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f472f952700 (LWP 12245)): #0
[korganizer] [Bug 392043] Korganizer crash
https://bugs.kde.org/show_bug.cgi?id=392043 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com --- Comment #1 from Filipus Klutiero --- Please clarify what you mean by "Periodically changing any values in tasks". -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 395526] New: kontact crashing at start
https://bugs.kde.org/show_bug.cgi?id=395526 Bug ID: 395526 Summary: kontact crashing at start Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: s_dibb...@web.de Target Milestone: --- Application: kontact (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.46.0 Operating System: Linux 4.15.0-23-generic x86_64 Distribution: Ubuntu 18.04 LTS -- Information about the crash: - What I was doing when the application crashed: starting kontact when starting from command line, i get something like kf5.kxmlgui: cannot find .rc file "kontactsummary_part.rc" for component "kontact" No such XML file "/home/me/.local/share/kontact/default-.rc" parse error from icalcomponent_new_from_string. string= "87015_r0" Failed to parse incidence! Item id = 43916 Storage collection id 221 parentCollectionId = 221 "87015_r0" org.kde.pim.akonadicore: Unable to deserialize payload part: "RFC822" in item 43916 collection 221 org.kde.pim.akonadicore: Payload data was: "87015_r0" ASSERT: "uint(i) < uint(size())" in file /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h, line 887 *** KMail got signal 6 (Exiting) *** Dead letters dumped. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kontact path = /usr/bin pid = 11917 KCrash: Arguments: /usr/bin/kontact KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1004/kdeinit5__0 QSocketNotifier: Invalid socket 9 and type 'Read', disabling... QSocketNotifier: Invalid socket 67 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... and after a short while >1000 lines saying [warn] epoll_wait: Ungültiger Dateideskriptor the last words meaning "invalid file descriptor" The crash can be reproduced every time. -- 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 0x7f8d0ba91b80 (LWP 10963))] Thread 29 (Thread 0x7f8bb69be700 (LWP 11011)): #0 0x7f8d08436bf9 in __GI___poll (fds=0x7f8ba8004a10, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8d02140439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8d0214054c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8d08f9c90b in QEventDispatcherGlib::processEvents (this=0x7f8ba8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8d08f419ea in QEventLoop::exec (this=this@entry=0x7f8bb69bda20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f8d08d6022a in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f8d08d6516d in QThreadPrivate::start (arg=0x556f2cc02bf0) at thread/qthread_unix.cpp:368 #7 0x7f8d041c06db in start_thread (arg=0x7f8bb69be700) at pthread_create.c:463 #8 0x7f8d0844388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7f8bb71bf700 (LWP 11008)): #0 0x7f8d08436bf9 in __GI___poll (fds=0x7f8bb0003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8d02140439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8d0214054c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8d08f9c90b in QEventDispatcherGlib::processEvents (this=0x7f8bbb20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8d08f419ea in QEventLoop::exec (this=this@entry=0x7f8bb71bea20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f8d08d6022a in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f8d08d6516d in QThreadPrivate::start (arg=0x556f2cbb22d0) at thread/qthread_unix.cpp:368 #7 0x7f8d041c06db in start_thread (arg=0x7f8bb71bf700) at pthread_create.c:463 #8 0x7f8d0844388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f8bbef0b700 (LWP 10999)): #0 0x7f8d02185cd9 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f8d021403fe in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8d0214054c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8d08f9c90b in QEventDispatcherGlib::processEvents (this=0x7f8bb8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8d08f419ea in QEventLoop::exec (this=this@entry=0x7f8bbef0aa20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f8d08d6022a in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f8d08d6516d in QThreadPrivate::start (arg=0x556f2c8c79e0) at thread/qthread_unix.cpp:368 #7 0x7f8d041c06db in start_thread (arg=0x7f8bbef0b700)
[korganizer] [Bug 381166] korganizer crashes on startup, evey time on a Fedora 25 system.
https://bugs.kde.org/show_bug.cgi?id=381166 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com --- Comment #5 from Filipus Klutiero --- So you are saying that KOrganizer crashes immediately at startup, but Kontact for its part does not, and only crashes when choosing calendar, to-do's or journal. Is that correct? If so, issue #388019, which was marked as a duplicate, seems different. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 392948] Akonadi fails to start on a fresh system (cannot create directory)
https://bugs.kde.org/show_bug.cgi?id=392948 BAKfr changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||kde-bugzi...@ebak.fr Ever confirmed|0 |1 --- Comment #4 from BAKfr --- This bug is present in KDE Neon User edition, and according to bug #393817, in several others distributions. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 392948] Akonadi fails to start on a fresh system (cannot create directory)
https://bugs.kde.org/show_bug.cgi?id=392948 BAKfr changed: What|Removed |Added CC||przem...@gmail.com --- Comment #3 from BAKfr --- *** Bug 393817 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 393817] Akonadi does not start
https://bugs.kde.org/show_bug.cgi?id=393817 BAKfr changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||kde-bugzi...@ebak.fr Resolution|--- |DUPLICATE --- Comment #9 from BAKfr --- A workaround is to manually create the folder ~/.local/share/akonadi/db_data/ *** This bug has been marked as a duplicate of bug 392948 *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 394483] Korganzier crashed at start
https://bugs.kde.org/show_bug.cgi?id=394483 BAKfr changed: What|Removed |Added CC||kde-bugzi...@ebak.fr --- Comment #1 from BAKfr --- The missing folder is an Akonadi bug #392948 The crash seems unrelated. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 392948] Akonadi fails to start on a fresh system (cannot create directory)
https://bugs.kde.org/show_bug.cgi?id=392948 BAKfr changed: What|Removed |Added CC||guent...@gmx.de --- Comment #2 from BAKfr --- *** Bug 395453 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 392092] akonadi_control crash on first start
https://bugs.kde.org/show_bug.cgi?id=392092 BingMyBong changed: What|Removed |Added CC||bingmyb...@btinternet.com --- Comment #9 from BingMyBong --- Happening on opensuse:tumbleweed:20180613 as well Qt: 5.11.0 KDE Frameworks: 5.46.0 - KDE Plasma: 5.13.0 - kwin 5.13.0 kmail2 5.8.2 - akonadiserver 5.8.2 - Kernel: 4.16.12-3-default - Application: akonadi_control (akonadi_control), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5d3dff6800 (LWP 9255))] Thread 2 (Thread 0x7f5d310ee700 (LWP 9256)): #0 0x7f5d3bb3c5d9 in poll () from /lib64/libc.so.6 #1 0x7f5d381ea377 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f5d381ebf8a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f5d340c8939 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f5d3c47993c in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f5d3b834554 in start_thread () from /lib64/libpthread.so.0 #6 0x7f5d3bb46fdf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f5d3dff6800 (LWP 9255)): [KCrash Handler] #6 0x7f5d3ba8424b in raise () from /lib64/libc.so.6 #7 0x7f5d3ba6d4f1 in abort () from /lib64/libc.so.6 #8 0x7f5d3c43a22b in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5 #9 0x562e57e1d93b in ?? () #10 0x562e57e40402 in ?? () #11 0x562e57e1daa8 in ?? () #12 0x7f5d3ba6f11b in __libc_start_main () from /lib64/libc.so.6 #13 0x562e57e1e1aa in _start () -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 394554] Regression: kMail 5.8.1 Information Leak: kMail loads external references in HTML mails without asking
https://bugs.kde.org/show_bug.cgi?id=394554 Christophe Giboudeaux changed: What|Removed |Added CC||axel.br...@gmx.de --- Comment #20 from Christophe Giboudeaux --- *** Bug 395448 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395448] kmail 5.8.1: Auto-load of web-content after first HTML mail
https://bugs.kde.org/show_bug.cgi?id=395448 Christophe Giboudeaux changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christophe Giboudeaux --- *** This bug has been marked as a duplicate of bug 394554 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #102 from Allan Sandfeld --- I also see this on a regular basis, though it doesn't always completely stall imap account, or at least didn't with my last version, but now does so again. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Allan Sandfeld changed: What|Removed |Added CC||k...@carewolf.com -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
