[kcontacts] [Bug 370934] Uses invalid vcard names for IM data in XDG_DATA_DIR/contacts
https://bugs.kde.org/show_bug.cgi?id=370934 Jason Fagnere changed: What|Removed |Added CC||jasonx86...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368983] Kmail crashes randomly
https://bugs.kde.org/show_bug.cgi?id=368983 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #1 from DeMus --- SolydKEE 64-bit, based on Debian 9 Testing KMail 5.2.3 KDE Frameworks 5.26.0 Qt 5.6.1 (built against 5.6.1) The xcb windowing system KMail crashes when adding Gmail IMAP account. Did try again and happened again. Crashreport: 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 0x7f3c7c419e40 (LWP 2789))] Thread 25 (Thread 0x7f3b409e4700 (LWP 2851)): #0 0x7f3c73085024 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3c7303f3c1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3c7303f974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3c7303faec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3c7a4a051b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3c7a44819a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3c7a26de53 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3c7a272d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3c73874464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f3c7996d97f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 24 (Thread 0x7f3bc141e700 (LWP 2840)): #0 0x7f3c7387a18f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f3c66a69574 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f3c66a695b9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f3c73874464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f3c7996d97f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 23 (Thread 0x7f3bc2dba700 (LWP 2832)): #0 0x7f3c7a26aea9 in QMutex::unlock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f3c7a49fd25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3c7303f3c9 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3c7303f974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3c7303faec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3c7a4a051b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3c7a44819a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3c7a26de53 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3c7a272d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f3c73874464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f3c7996d97f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 22 (Thread 0x7f3bc35bb700 (LWP 2830)): #0 0x7f3c7996450d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f3c7303f9d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3c7303faec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3c7a4a051b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3c7a44819a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3c7a26de53 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3c7a272d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3c73874464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f3c7996d97f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 21 (Thread 0x7f3bc3dbc700 (LWP 2828)): #0 0x7f3c73085024 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3c7303eecc in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3c7303f8fb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3c7303faec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3c7a4a051b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3c7a44819a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3c7a26de53 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3c7a272d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3c73874464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f3c7996d97f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 20 (Thread 0x7f3bd1bbb7
[kcontacts] [Bug 370934] Uses invalid vcard names for IM data in XDG_DATA_DIR/contacts
https://bugs.kde.org/show_bug.cgi?id=370934 --- Comment #1 from Jason Fagnere --- After further digging, i guess that https://github.com/KDE/kcontacts/blob/b2194dd9d806875122c76220f77660c9de09f14d/src/vcardtool.cpp is the problem, so i moved the bug from kaddressbook to kcontacts (please correct if i'm wrong). I also found another reference to xmessaging in https://github.com/KDE/kcontacts/blob/b2194dd9d806875122c76220f77660c9de09f14d/src/converter/vcardconverter.cpp, but it looks like the code that convert *from* x-messaging to "proper" x-(protocol) when you export vcards. Didn't found any other reference to that x-messaging in KDE's github repos, maybe this line isn't used at all? the only references appear to convert from x-(protocol) to this invalid name (?!?) and convert from it to x-(protocol). so it may only be some legacy code that isn't used nowadays? -- You are receiving this mail because: You are the assignee for the bug.
[kcontacts] [Bug 370934] Uses invalid vcard names for IM data in XDG_DATA_DIR/contacts
https://bugs.kde.org/show_bug.cgi?id=370934 Jason Fagnere changed: What|Removed |Added Component|general |general Product|kaddressbook|kcontacts Version|5.1.3 |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 370934] New: Uses invalid vcard names for IM data in XDG_DATA_DIR/contacts
https://bugs.kde.org/show_bug.cgi?id=370934 Bug ID: 370934 Summary: Uses invalid vcard names for IM data in XDG_DATA_DIR/contacts Product: kaddressbook Version: 5.1.3 Platform: Ubuntu Packages URL: https://github.com/geier/pycarddav/issues/91 OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jasonx86...@gmail.com CC: to...@kde.org The vcards in $XDG_DATA_DIR/contacts contains invalid names for IM data, the RFC (both 2426 and 6250) define the name as 1*(ALPHA / DIGIT / "-"), and KAddressbook (or akonadi?) uses "/", which is invalid, and thus may break some parsers, for example in pycarddav. it also makes these vcards unsuitable for sync between devices (my use case). (Also, it exports vcards 4.0 with X-JABBER instead of IMPP, which isn't invalid per se, but less X- would be great, i guess) Reproducible: Always Steps to Reproduce: 1. Create a contact in KAddressbook with an IM address 2. Read it's vcard in ~/.local/share/contacts Actual Results: BEGIN:VCARD VERSION:3.0 FN:John Doe N:Doe;John;;; X-KADDRESSBOOK-X-IMAddress:john@example.org X-messaging/xmpp-All:john@example.org END:VCARD Expected Results: BEGIN:VCARD VERSION:3.0 FN:John Doe N:Doe;John;;; X-KADDRESSBOOK-X-IMAddress:john@example.org X-JABBER:john@example.org END:VCARD -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 365982] akonadiconsole crash when pressing the "browser" button
https://bugs.kde.org/show_bug.cgi?id=365982 Ilpo Kantonen changed: What|Removed |Added CC||i...@iki.fi --- Comment #2 from Ilpo Kantonen --- Application: akonadiconsole (0.99) Qt Version: 5.5.1 Operating System: Linux 4.4.0-42-generic i686 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: It crashed when I started to browse my own contacts. Also Kaddressbook crashes and Kmail dont find contacts. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Console (akonadiconsole), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xaaf17840 (LWP 29853))] Thread 17 (Thread 0xa0714b40 (LWP 29881)): #0 0xb7766c31 in __kernel_vsyscall () #1 0xb1c7ea8c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187 #2 0xb50e88cd in __pthread_cond_wait (cond=0xa2c2b734, mutex=0xa2c2b71c) at forward.c:149 #3 0xb388b0bc in WTF::ThreadCondition::wait(WTF::Mutex&) () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #4 0xb354ae65 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #5 0xb38736b2 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #6 0xb388aac1 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #7 0xb1c792b5 in start_thread (arg=0xa0714b40) at pthread_create.c:333 #8 0xb50dc16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 16 (Thread 0xa0f34b40 (LWP 29880)): #0 0xb7766c31 in __kernel_vsyscall () #1 0xb1c7ea8c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187 #2 0xb50e88cd in __pthread_cond_wait (cond=0xa2c27138, mutex=0xa2c27120) at forward.c:149 #3 0xb388b0bc in WTF::ThreadCondition::wait(WTF::Mutex&) () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #4 0xb3549d36 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #5 0xb38736b2 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #6 0xb388aac1 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #7 0xb1c792b5 in start_thread (arg=0xa0f34b40) at pthread_create.c:333 #8 0xb50dc16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 15 (Thread 0xa18adb40 (LWP 29878)): #0 0xb1068ef0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb106b55b in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb106c014 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb106c244 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb55fab14 in QEventDispatcherGlib::processEvents (this=0xa7a0ced0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0xb559f953 in QEventLoop::processEvents (this=0xa18ad194, flags=...) at kernel/qeventloop.cpp:128 #6 0xb559fdaa in QEventLoop::exec (this=0xa18ad194, flags=...) at kernel/qeventloop.cpp:204 #7 0xb53c5f1d in QThread::exec (this=0x84687b0) at thread/qthread.cpp:503 #8 0xb53c5ff8 in QThread::run (this=0x84687b0) at thread/qthread.cpp:570 #9 0xb53cb43b in QThreadPrivate::start (arg=0x84687b0) at thread/qthread_unix.cpp:331 #10 0xb1c792b5 in start_thread (arg=0xa18adb40) at pthread_create.c:333 #11 0xb50dc16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 14 (Thread 0xa20aeb40 (LWP 29876)): #0 0xb10b24b8 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb106babf in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb106c0a1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb106c244 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb55fab14 in QEventDispatcherGlib::processEvents (this=0x83add08, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0xb559f953 in QEventLoop::processEvents (this=0xa20ae194, flags=...) at kernel/qeventloop.cpp:128 #6 0xb559fdaa in QEventLoop::exec (this=0xa20ae194, flags=...) at kernel/qeventloop.cpp:204 #7 0xb53c5f1d in QThread::exec (this=0x83ad528) at thread/qthread.cpp:503 #8 0xb53c5ff8 in QThread::run (this=0x83ad528) at thread/qthread.cpp:570 #9 0xb53cb43b in QThreadPrivate::start (arg=0x83ad528) at thread/qthread_unix.cpp:331 #10 0xb1c792b5 in start_thread (arg=0xa20aeb40) at pthread_create.c:333 #11 0xb50dc16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 13 (Thread 0xa28afb40 (LWP 29874)): #0 0xb10b24b8 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb106babf in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb106c0a1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb106c244 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb55fab14 in QEventDispatcherGlib::processEvents (this=0xaa0062f8, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0xb559f953 in
[kaddressbook] [Bug 365800] Since I moved to Kubuntu 16.04, kaddressbook crashes.
https://bugs.kde.org/show_bug.cgi?id=365800 --- Comment #8 from Ilpo Kantonen --- I did it. First backuped .local/share/contacts and then removed them. Then I stopped akonadi. Then I added one vcf file to contacts. And then I started Kmail. All emails were disappeared and the directory structure in Kmail! Fortunately I got emails back restarting machine. How you remove all akonadi related files? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 357541] akonadi_baloo_indexer crashes on akonadi start
https://bugs.kde.org/show_bug.cgi?id=357541 chooks changed: What|Removed |Added CC||chookstwoe...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 357541] akonadi_baloo_indexer crashes on akonadi start
https://bugs.kde.org/show_bug.cgi?id=357541 --- Comment #6 from chooks --- Created attachment 101577 --> https://bugs.kde.org/attachment.cgi?id=101577&action=edit New crash information added by DrKonqi akonadi_baloo_indexer (4.14) on KDE Platform 4.14.16 using Qt 4.8.7 - What I was doing when the application crashed: Started my system and logged into kde, crash of application occurred before I did anything. -- Backtrace (Reduced): #6 0x7f54a3009418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f54a300b01a in __GI_abort () at abort.c:89 [...] #11 0x7f54a6d11db1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x7f54a425ffdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #13 0x7f54a4266f16 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 -- You are receiving this mail because: You are the assignee for the bug.
[neon] [Bug 370498] KMail crashes when pressing SPACE while displaying a message
https://bugs.kde.org/show_bug.cgi?id=370498 --- Comment #3 from Alex Sidorenko --- This was not really a bug in KDE but rather mismatched shared libraries... So Neon/User update of 15 Oct 2016 has fixed the problem as it provides KDE applications 16.08.2 and the new build obviously fixes the issue. Anyway, it is FIXED now -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 370925] New: KMail has crushed after accessing a mail from IMAP draft folder where the mail was just saved
https://bugs.kde.org/show_bug.cgi?id=370925 Bug ID: 370925 Summary: KMail has crushed after accessing a mail from IMAP draft folder where the mail was just saved Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: adund...@gmail.com Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.7.6-200.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: - What I was doing when the application crashed: 1. writing an e-mail and saving it into drafts (ctrl+s) 2. accessing the draft from the IMAP draft folder 3. KMail crushed on retrievening the content of selected mail from the mail list I cannot easily reproduce it, but it seems like a Akonadi-related issue (I use PostgreSQL as the database backend). I don't know how to increase verbosity of this setup (Akonadi/IMAP resource/KMail), any advice? The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa1ee494940 (LWP 14419))] Thread 39 (Thread 0x7fa07eba6700 (LWP 17537)): #0 0x7fa203e8bf79 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa2138d4ff8 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fa2138d192d in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5 #3 0x7fa2138d499a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7fa203e865ca in start_thread () at /lib64/libpthread.so.0 #5 0x7fa212cc7f6d in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7fa07f3a7700 (LWP 27178)): #0 0x7fa203e8bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa20ad0be79 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7fa20ad0c540 in base::SequencedWorkerPool::Worker::Run() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7fa20ad0c710 in base::SimpleThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7fa20ad090fd in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7fa203e865ca in start_thread () at /lib64/libpthread.so.0 #6 0x7fa212cc7f6d in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7fa0c651e700 (LWP 6240)): #0 0x7fa2138cd5c9 in QMutex::lock() () at /lib64/libQt5Core.so.5 #1 0x7fa213ac1fcf in postEventSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #2 0x7fa202a07f59 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #3 0x7fa202a0892b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7fa202a08b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7fa213ac224b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fa213a715ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fa2138d0343 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7fa2138d499a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7fa203e865ca in start_thread () at /lib64/libpthread.so.0 #10 0x7fa212cc7f6d in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7fa0c75f6700 (LWP 6235)): #0 0x7fa203e8bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa206a42203 in JSC::GCThread::waitForNextPhase() () at /lib64/libQt5WebKit.so.5 #2 0x7fa206a42290 in JSC::GCThread::gcThreadMain() () at /lib64/libQt5WebKit.so.5 #3 0x7fa206d48531 in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #4 0x7fa203e865ca in start_thread () at /lib64/libpthread.so.0 #5 0x7fa212cc7f6d in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7fa0c7df7700 (LWP 6234)): #0 0x7fa203e8bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa206a42203 in JSC::GCThread::waitForNextPhase() () at /lib64/libQt5WebKit.so.5 #2 0x7fa206a42290 in JSC::GCThread::gcThreadMain() () at /lib64/libQt5WebKit.so.5 #3 0x7fa206d48531 in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #4 0x7fa203e865ca in start_thread () at /lib64/libpthread.so.0 #5 0x7fa212cc7f6d in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7fa0db6b2700 (LWP 6233)): #0 0x7fa203e8bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa206a42203 in JSC::GCThread::waitForNextPhase() () at /lib64/libQt5WebKit.so.5 #2 0x7fa206a42290 in JSC::GCThread::gcThreadMain() () at /lib64/libQt5WebKit.so.5 #3 0x7fa206d48531 in WTF::wtfThreadEntryPoin
[kmail2] [Bug 330261] New Message from Template only uses default identity
https://bugs.kde.org/show_bug.cgi?id=330261 Allen Winter changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED CC||win...@kde.org -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 370369] Use "message preview pane next to message list" as new default
https://bugs.kde.org/show_bug.cgi?id=370369 --- Comment #2 from Roman --- Sure. ;) I just believe this layout to be objectively better (because of computer screens being more wide than high and therefore using the available space better). In the second place it's of course also a matter of taste, which version you prefer. But it seems natural to prioritize the "objectively better" option and let the user switch to the other one instead of doing it the other way around. But if you don't think one is 'objectively better' than the other, it's also fine and we don't have to argue about it because I don't think changing this is one of the most important things at the moment and I don't have a huge incentive pushing it. This bug/wishlist entry was only meant as a suggestion. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 370911] New: call @1844-722-6675 Quickbooks enterprise support phone number
https://bugs.kde.org/show_bug.cgi?id=370911 Bug ID: 370911 Summary: call @1844-722-6675 Quickbooks enterprise support phone number Product: Akonadi Version: 5.3.0 Platform: Balsam Professional URL: http://call@1844-722-6675-Quickbooks-enterprise-suppor t-phone-number.com OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: Archive Mail Agent Assignee: kdepim-bugs@kde.org Reporter: sekhavatra...@gmail.com @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number@1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number Reproducible: Sometimes Steps to Reproduce: 1.@1844-722-6675 Quickbooks enterprise support phone number 2.@1844-722-6675 Quickbooks enterprise support phone number 3.@1844-722-6675 Quickbooks enterprise support phone number Actual Results: @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number Expected Results: @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number @1844-722-6675 Quickbooks enterprise support phone number -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 343034] KMail insists on offline mode, even when network connection is available
https://bugs.kde.org/show_bug.cgi?id=343034 --- Comment #16 from emili...@gmail.com --- Adittionally, how is one supposed to use ntrack with KF5? from kdelibs4support/src/solid-networkstatus/kded/CMakeLists.txt: # FIXME: Re-enable the above when: # * QNTrack has been ported to Qt5 # * cmake/modules/FindQNtrack.cmake has been adapted to the Qt5 dependency #find_package(QNtrack) #set_package_properties(QNtrack PROPERTIES DESCRIPTION "Network status tracking library" # URL "http://launchpad.net/ntrack"; # TYPE OPTIONAL # PURPOSE "Provides data input for Solid network status" # ) set(QNTRACK_FOUND FALSE) # Forced to false, see above FIXME -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 365991] Starting Kontact/Kmail causes crash. Command line shows - akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection."
https://bugs.kde.org/show_bug.cgi?id=365991 --- Comment #10 from Pip --- (In reply to rndbit from comment #9) > Thanks Pip, you are a life saver. I was struggling with similar issues. > Akonadi had really hard time syncing anything. Switching back to mysql made > problems go away. I'm glad it wasn't just me and that the flailing around blindly helped someone else. -- You are receiving this mail because: You are the assignee for the bug.
