[kleopatra] [Bug 408168] New: symbol lookup error in kleopatra
https://bugs.kde.org/show_bug.cgi?id=408168 Bug ID: 408168 Summary: symbol lookup error in kleopatra Product: kleopatra Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: storan...@gmail.com CC: kdepim-bugs@kde.org, m...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. installed kleopatra via dnf 2. tried to open kleopatra via gnome menu 3. tried via terminal OBSERVED RESULT terminal output kleopatra: symbol lookup error: /lib64/libKF5KCMUtils.so.5: undefined symbol: _ZN12KQuickAddons12ConfigModule10pagePushedEP10QQuickItem EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are on the CC list 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 #133 from Søren Holm --- Great work Daniel. I switched from kmail to thunderbird some months ago and I hate it. I look forward to this automatic repair getting into my distribution :) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[kmail2] [Bug 400838] Crash when closing message window with Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=400838 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #5 from Wolfgang Bauer --- (In reply to Erik Quaeghebeur from comment #2) > Me (and others) are hitting this bug with 18.12.3 and Qt 5.12.3, so > reopening. (Updating version/platform/importance) According to https://bugs.gentoo.org/686842 this should be fixed already, no? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 408121] abily to control "unread"-message overlay in tasklist
https://bugs.kde.org/show_bug.cgi?id=408121 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED CC||mon...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Laurent Montel --- (In reply to Christoph from comment #0) > I like the new feature of the overlayed unreadmessage-count in Tasklist , > but it would be nice to have more to say on this, like: > > -) disable it at all you can kmail->apperance->systemtray->show unread in taskbar > -) only count specify folders (like Inboxes only) you can disable counting in specific folder -> on each folder you can disable it "see folder right click -> property -> general -> act on new/unread mail in this folder" > > actually it counts all unready messages in all folder , resulting in a > permanent "9.999+" - reading > > thanks for support > > -c- Regards -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 408145] New: CRash on selecting folder with unread mail
https://bugs.kde.org/show_bug.cgi?id=408145 Bug ID: 408145 Summary: CRash on selecting folder with unread mail Product: kmail2 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: criss...@gmx.de Target Milestone: --- Application: kmail (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.47.0 Operating System: Linux 4.18.0-17-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: I opened kmail and i downloaded new mail from POP3 server. Some mail was moved into sub folder by filter rule. I clicked on that folder and kmail crashed. -- 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 0x7f92185e9b80 (LWP 4728))] Thread 29 (Thread 0x7f90b666c700 (LWP 5643)): #0 0x7f920afdeed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f90b666b8c0, expected=0, futex_word=0x7f90a8006df0) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f920afdeed9 in __pthread_cond_wait_common (abstime=0x7f90b666b980, mutex=0x7f90a8006da0, cond=0x7f90a8006dc8) at pthread_cond_wait.c:533 #2 0x7f920afdeed9 in __pthread_cond_timedwait (cond=0x7f90a8006dc8, mutex=0x7f90a8006da0, abstime=0x7f90b666b980) at pthread_cond_wait.c:667 #3 0x7f9215dee468 in QWaitConditionPrivate::wait_relative(unsigned long) (time=3, this=0x7f90a8006da0) at thread/qwaitcondition_unix.cpp:133 #4 0x7f9215dee468 in QWaitConditionPrivate::wait(unsigned long) (time=3, this=0x7f90a8006da0) at thread/qwaitcondition_unix.cpp:141 #5 0x7f9215dee468 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x7f90a8006ab0, mutex=mutex@entry=0x7f90a8003fb0, time=3) at thread/qwaitcondition_unix.cpp:215 #6 0x7f9215dea53d in QThreadPoolThread::run() (this=0x7f90a8006aa0) at thread/qthreadpool.cpp:144 #7 0x7f9215ded17d in QThreadPrivate::start(void*) (arg=0x7f90a8006aa0) at thread/qthread_unix.cpp:368 #8 0x7f920afd86db in start_thread (arg=0x7f90b666c700) at pthread_create.c:463 #9 0x7f92156e888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7f90b8688700 (LWP 5637)): #0 0x7f920afde9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x564aafdf0b68) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f920afde9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x564aafdf0b18, cond=0x564aafdf0b40) at pthread_cond_wait.c:502 #2 0x7f920afde9f3 in __pthread_cond_wait (cond=0x564aafdf0b40, mutex=0x564aafdf0b18) at pthread_cond_wait.c:655 #3 0x7f91ffe79c95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f91ffe7a177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f91ffe7af11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f91ffe775eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f920afd86db in start_thread (arg=0x7f90b8688700) at pthread_create.c:463 #8 0x7f92156e888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f9139f2f700 (LWP 5636)): #0 0x7f920afde9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f91fc740fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f920afde9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f91fc740f68, cond=0x7f91fc740f90) at pthread_cond_wait.c:502 #2 0x7f920afde9f3 in __pthread_cond_wait (cond=0x7f91fc740f90, mutex=0x7f91fc740f68) at pthread_cond_wait.c:655 #3 0x7f91fc44a5f4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f91fc44a639 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f920afd86db in start_thread (arg=0x7f9139f2f700) at pthread_create.c:463 #6 0x7f92156e888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f9141e06700 (LWP 5617)): #0 0x7f92156dbbf9 in __GI___poll (fds=0x7f913c001cb0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f92093825c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f92093826dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f92160249bb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f913c000cc0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f9215fc9a1a in QEventLoop::exec(QFlags) (this=this@entry=0x7f9141e05a20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f9215de823a in QThread::exec() (this=) at thread/qthread.cpp:515 #6 0x7f9215ded17d in QThreadPrivate::start(void*) (arg=0x564ab2b4e6a0) at thread/qthread_unix.cpp:368 #7 0x7f920afd86db in start_thread (arg=0x7f9141e06700
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #132 from Daniel Vrátil --- Git commit 8f230d7d7f8a4e2b97273585374a68902b5ef6cf by Daniel Vrátil. Committed on 31/05/2019 at 11:21. Pushed by dvratil into branch 'master'. Automatic recovery from Multiple Merge Candidates error Summary: Introduce a recovery codepath when Multiple Merge Candidates error occurs during Item merging. Since clients generally do not use merging, this really only happens during ItemSync. In such case we quitely delete all the conflicting items from the database and reschedule the collection sync. The next sync should then succeed and bring the collection into a consistent state. Note that this does not fix the Multiple Merge Candidates bug - it can still happen (and we still don't know how), but Akonadi should now be able to recover from it automatically without user intervention, thus making this issue less of a PITA. Test Plan: Successfuly auto-recovered a broken collection on my setup. Reviewers: #kde_pim, dfaure Reviewed By: dfaure Subscribers: vkrause, dfaure, ngraham, asturmlechner, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D21455 M +3-3autotests/server/fakedatastore.cpp M +1-1autotests/server/fakedatastore.h M +65 -4src/server/handler/itemcreatehandler.cpp M +4-0src/server/handler/itemcreatehandler.h M +18 -16 src/server/storage/datastore.cpp M +3-1src/server/storage/datastore.h https://commits.kde.org/akonadi/8f230d7d7f8a4e2b97273585374a68902b5ef6cf -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
