[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable
https://bugs.kde.org/show_bug.cgi?id=399167 David Faure changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #20 from David Faure --- Both fixes have been pushed in Applications/19.04 branch. (The fix for canceling is https://phabricator.kde.org/D19488) -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405440] Kontact crash when click on configure kontact
https://bugs.kde.org/show_bug.cgi?id=405440 Laurent Montel changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #11 from Laurent Montel --- *** Bug 405729 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405729] Kontact 5.10.3 crashes trying to "configure Kontact"
https://bugs.kde.org/show_bug.cgi?id=405729 Laurent Montel changed: What|Removed |Added Resolution|--- |DUPLICATE CC||mon...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Laurent Montel --- *** This bug has been marked as a duplicate of bug 405440 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Thomas Monjalon changed: What|Removed |Added CC||tho...@monjalon.net --- Comment #27 from Thomas Monjalon --- Adding one more feedback about this annoying bug. This is what I see when running "akonadictl start": org.kde.pim.davresource: Error when uploading item: 420 "There was a problem with the request. The item was not modified on the server.\nThe file or folder caldav.fastmail.com does not exist. (0)." In case I can help, I am on IRC (tmonjalo). -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405729] New: Kontact 5.10.3 crashes trying to "configure Kontact"
https://bugs.kde.org/show_bug.cgi?id=405729 Bug ID: 405729 Summary: Kontact 5.10.3 crashes trying to "configure Kontact" Product: kontact Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: piedro.kul...@gmail.com Target Milestone: --- SUMMARY Kontact crashes with segmentation fault when entering "configure kontact". STEPS TO REPRODUCE 1. open kontact, any section... 2. open menu "settings" 3. choose "configure kontact" OBSERVED RESULT Kontact crashes immediateley with a segfault EXPECTED RESULT Kontact shouldn't crash, obviously SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch linux fully updates (available in About System) Kontact 5.10.3 KDE Frameworks 5.56.0 Qt 5.12.2 (built against 5.12.1) ADDITIONAL INFORMATION This is serious. It makes Kontact unconfigurable. Since a "Personal" information maneger has to be configured to individual needs this is a complete showstopper rendering kontact basically unusable for any real life work scenario. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #28 from Christoph Feck --- The name was replaced because it was wrong. It didn't return the width, but the number of pixels the cursor advances. If you wanted the width, you had to use boundingRect().width(). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #19 from David Faure --- Git commit 8ff596c4fe15199b66262c624d8b7c8d8ec7368f by David Faure. Committed on 21/03/2019 at 15:50. Pushed by dfaure into branch 'Applications/19.04'. Akonadi: fix dangling transaction after itemsync failure Summary: TransactionSequence was emitting result() twice when rolling back. * How did this happen? The TransactionRollbackJob is (automatically) added as a subjob of the TransactionSequence, so when it finishes, slotResult is called (like for all subjobs), as well as rollbackResult(). Since the latter emits result() already [mostly for symmetry with commitResult()], we don't need to do that in slotResult (which doesn't do it for the case of committing, either). * Why is it a problem to emit result() twice? Well, first, it's against the law in KJob world. In practice, ItemSyncPrivate::slotTransactionResult was called twice (for the same TransactionSequence job) which made it decrement mTransactionJobs one time too many. As a result, checkDone() finished too early and didn't go into the "commit transaction" branch for other transactions. Leaving a transaction "open" is a good recipe for database deadlocks further down the line. * Why did the TransactionSequence roll back in the first place? In my case because of the infamous and not-yet fixed "Multiple merge candidates" problem, but it seems that it can also happen when having items without a part, according to Volker's investigations. All of these issues still need to be fixed, but at least akonadi seems to be still usable after they happen. Test Plan: Ctrl+L in kmail, with a folder having multiple items for the same RID Reviewers: dvratil, vkrause Reviewed By: dvratil Subscribers: kfunk, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D19487 (cherry picked from commit f1281cf18f40fd69acd61c31b48f5ce43e138eea) M +0-2src/core/jobs/transactionsequence.cpp https://commits.kde.org/akonadi/8ff596c4fe15199b66262c624d8b7c8d8ec7368f -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #18 from David Faure --- Git commit f1281cf18f40fd69acd61c31b48f5ce43e138eea by David Faure. Committed on 21/03/2019 at 15:49. Pushed by dfaure into branch 'master'. Akonadi: fix dangling transaction after itemsync failure Summary: TransactionSequence was emitting result() twice when rolling back. * How did this happen? The TransactionRollbackJob is (automatically) added as a subjob of the TransactionSequence, so when it finishes, slotResult is called (like for all subjobs), as well as rollbackResult(). Since the latter emits result() already [mostly for symmetry with commitResult()], we don't need to do that in slotResult (which doesn't do it for the case of committing, either). * Why is it a problem to emit result() twice? Well, first, it's against the law in KJob world. In practice, ItemSyncPrivate::slotTransactionResult was called twice (for the same TransactionSequence job) which made it decrement mTransactionJobs one time too many. As a result, checkDone() finished too early and didn't go into the "commit transaction" branch for other transactions. Leaving a transaction "open" is a good recipe for database deadlocks further down the line. * Why did the TransactionSequence roll back in the first place? In my case because of the infamous and not-yet fixed "Multiple merge candidates" problem, but it seems that it can also happen when having items without a part, according to Volker's investigations. All of these issues still need to be fixed, but at least akonadi seems to be still usable after they happen. Test Plan: Ctrl+L in kmail, with a folder having multiple items for the same RID Reviewers: dvratil, vkrause Reviewed By: dvratil Subscribers: kfunk, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D19487 M +0-2src/core/jobs/transactionsequence.cpp https://commits.kde.org/akonadi/f1281cf18f40fd69acd61c31b48f5ce43e138eea -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #27 from Kamil Dudka --- Comment on attachment 118961 --> https://bugs.kde.org/attachment.cgi?id=118961 patch to reenable numbers, v18.12 Works perfectly. Thanks for the quick fix! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #26 from Éric Brunet --- Created attachment 118961 --> https://bugs.kde.org/attachment.cgi?id=118961=edit patch to reenable numbers, v18.12 Sorry, I was slow with updating this patch. The method horizontalAdvance seems to replace nicely the method width. Probably that they changed it because "width" was so difficult to remember... -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521
--- Comment #25 from Kamil Dudka ---
Comment on attachment 114942
--> https://bugs.kde.org/attachment.cgi?id=114942
patch to reenable numbers, v18.04.3
I am not able to compile kmail-18.12.3 with this patch against up2date qt. The
build fails with this error:
/var/tmp/paludis/kde-apps-kmail-18.12.3/work/kmail-18.12.3/src/kmsystemtray.cpp:
In member function 'void KMail::KMSystemTray::updateCount(int)':
/var/tmp/paludis/kde-apps-kmail-18.12.3/work/kmail-18.12.3/src/kmsystemtray.cpp:175:31:
error: 'class QFontMetrics' has no member named 'width'; did you mean
'maxWidth'?
const int width = qfm.width(count < 100 ? QStringLiteral("99")
^
maxWidth
I was able to google up a page saying that QFontMetrics::width() is obsolete:
https://doc.qt.io/qt-5/qfontmetrics-obsolete.html
... but the page does not suggest any replacement for that method.
Any idea how to make it build again?
--
You are receiving this mail because:
You are the assignee for the bug.
[kontact] [Bug 405720] New: Crash when going through new emails
https://bugs.kde.org/show_bug.cgi?id=405720 Bug ID: 405720 Summary: Crash when going through new emails Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: hka...@redhat.com Target Milestone: --- Application: kontact (5.9.3) Qt Version: 5.11.3 Frameworks Version: 5.55.0 Operating System: Linux 4.20.14-100.fc28.x86_64 x86_64 Distribution: "Fedora release 28 (Twenty Eight)" -- Information about the crash: - What I was doing when the application crashed: The application crashed when I was going through new (unread) emails; I was either using the mouse or switching to the next bug using the + and - keys on numpad -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb5310a4980 (LWP 4500))] Thread 31 (Thread 0x7fb4ddffb700 (LWP 11371)): #0 0x7fb5200119d8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb524374897 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7fb52437655a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /lib64/libQt5WebEngineCore.so.5 #3 0x7fb524376642 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #4 0x7fb52437b401 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7fb52437c6ff in base::internal::SchedulerWorker::Thread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #6 0x7fb524386d11 in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #7 0x7fb52000b594 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb52a310f4f in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7fb3bc513700 (LWP 11369)): #0 0x7fb5200119d8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb524374897 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7fb52437655a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /lib64/libQt5WebEngineCore.so.5 #3 0x7fb524376642 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #4 0x7fb52437b401 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7fb52437c6ff in base::internal::SchedulerWorker::Thread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #6 0x7fb524386d11 in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #7 0x7fb52000b594 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb52a310f4f in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7fb4b552f700 (LWP 10683)): #0 0x7fb5200119d8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb524374897 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7fb52437655a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /lib64/libQt5WebEngineCore.so.5 #3 0x7fb524376642 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #4 0x7fb52437b401 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7fb52437c8e1 in base::internal::SchedulerWorker::Thread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #6 0x7fb524386d11 in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #7 0x7fb52000b594 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb52a310f4f in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7fb3c0274700 (LWP 10131)): #0 0x7fb5200119d8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb524374897 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7fb52437655a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /lib64/libQt5WebEngineCore.so.5 #3 0x7fb524376642 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #4 0x7fb52437b401 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7fb52437c8e1 in base::internal::SchedulerWorker::Thread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #6 0x7fb524386d11 in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #7 0x7fb52000b594 in
[kontact] [Bug 405440] Kontact crash when click on configure kontact
https://bugs.kde.org/show_bug.cgi?id=405440 Christoph Feck changed: What|Removed |Added CC||johannesfa...@googlemail.co ||m --- Comment #10 from Christoph Feck --- *** Bug 405712 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405712] "Configure Kontact" leads to crash
https://bugs.kde.org/show_bug.cgi?id=405712 Christoph Feck changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 405440 *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 405714] New: trivial appearance bug
https://bugs.kde.org/show_bug.cgi?id=405714 Bug ID: 405714 Summary: trivial appearance bug Product: korganizer Version: 5.7.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: agendaview (weekview) Assignee: kdepim-bugs@kde.org Reporter: dav1dblunk...@hotmail.com Target Milestone: --- If your screen is sufficiently big that all 24 hours are visible then the scroll bar on the RHS disappears. when this happens the "day" panel at the top doesn't align with the "hours" pane below. Trivial but a little messy. Any chance someone has fixed the start day of the week issue yet? -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405712] "Configure Kontact" leads to crash
https://bugs.kde.org/show_bug.cgi?id=405712 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||mon...@kde.org --- Comment #1 from Laurent Montel --- bug in kf5.56 fixed in 5.56.2 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405712] New: "Configure Kontact" leads to crash
https://bugs.kde.org/show_bug.cgi?id=405712 Bug ID: 405712 Summary: "Configure Kontact" leads to crash Product: kontact Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: johannesfa...@googlemail.com Target Milestone: --- Application: kontact (5.10.3) Qt Version: 5.12.2 Frameworks Version: 5.56.0 Operating System: Linux 5.0.2-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: opened Kontact, pressed "Configure Kontact..." - Occurs every time Likely duplicate: https://bugs.kde.org/show_bug.cgi?id=405695 The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fec3214d380 (LWP 2875))] Thread 30 (Thread 0x7feafea13700 (LWP 2988)): #0 0x7fec445afef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fec3c7067c7 in base::ConditionVariable::TimedWait () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #2 0x7fec3c70712a in base::WaitableEvent::TimedWaitUntil () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #3 0x7fec3c707212 in base::WaitableEvent::TimedWait () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161 #4 0x7fec3c6c44c1 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:37 #5 0x7fec3c6c5bd7 in base::internal::SchedulerWorker::RunWorker () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:296 #6 0x7fec3c6c61c4 in base::internal::SchedulerWorker::RunPooledWorker () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:224 #7 0x7fec3c7091a1 in ThreadFunc () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/threading/platform_thread_posix.cc:76 #8 0x7fec445a9a9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fec4575eb23 in clone () from /usr/lib/libc.so.6 Thread 29 (Thread 0x7feaff214700 (LWP 2987)): #0 0x7fec445afef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fec3c7067c7 in base::ConditionVariable::TimedWait () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #2 0x7fec3c70712a in base::WaitableEvent::TimedWaitUntil () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #3 0x7fec3c707212 in base::WaitableEvent::TimedWait () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161 #4 0x7fec3c6c44c1 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:37 #5 0x7fec3c6c5f06 in base::internal::SchedulerWorker::RunWorker () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:324 #6 0x7fec3c6c61c4 in base::internal::SchedulerWorker::RunPooledWorker () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:224 #7 0x7fec3c7091a1 in ThreadFunc () at ./../../../../qtwebengine-everywhere-src-5.12.2/src/3rdparty/chromium/base/threading/platform_thread_posix.cc:76 #8 0x7fec445a9a9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fec4575eb23 in clone () from /usr/lib/libc.so.6 Thread 28 (Thread 0x7feb2889a700 (LWP 2984)): #0 0x7fec201610fe in pa_pstream_ref () from /usr/lib/pulseaudio/libpulsecommon-12.2.so #1 0x7fec20161cb2 in ?? () from /usr/lib/pulseaudio/libpulsecommon-12.2.so #2 0x7fec2016254a in ?? () from /usr/lib/pulseaudio/libpulsecommon-12.2.so #3 0x7fec203c4d18 in pa_mainloop_dispatch () from /usr/lib/libpulse.so.0 #4 0x7fec203c4fef in pa_mainloop_iterate () from /usr/lib/libpulse.so.0 #5 0x7fec203c5091 in pa_mainloop_run () from /usr/lib/libpulse.so.0 #6 0x7fec203d35ae in ?? () from /usr/lib/libpulse.so.0 #7 0x7fec201729fc in ?? () from /usr/lib/pulseaudio/libpulsecommon-12.2.so #8 0x7fec445a9a9d in start_thread () from /usr/lib/libpthread.so.0 #9
[kontact] [Bug 405711] Kontact crash after chainging UI language
https://bugs.kde.org/show_bug.cgi?id=405711 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #2 from Laurent Montel --- #9 QMessageLogger::fatal (this=this@entry=0x7fff09ab6ba0, msg=msg@entry=0x7facf3b5e258 "KSycoca unavailable. Kontact will be unable to find plugins.") at global/qlogging.cpp:887 qfatal. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405711] Kontact crash after chainging UI language
https://bugs.kde.org/show_bug.cgi?id=405711 --- Comment #1 from Mathias Homann --- switching to US english instead of UK english worked fine. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405711] New: Kontact crash after chainging UI language
https://bugs.kde.org/show_bug.cgi?id=405711 Bug ID: 405711 Summary: Kontact crash after chainging UI language Product: kontact Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.10.3) Qt Version: 5.12.2 Frameworks Version: 5.56.0 Operating System: Linux 4.12.14-lp150.12.48-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: I changed the interface language for kontact from german (my desktop default) to english (UK), now it crashes on start. Can't even reset that switch. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7facf410a940 (LWP 16943))] Thread 17 (Thread 0x7fabdd05a700 (LWP 16971)): #0 0x7facec4f389d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7face15e23d9 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7face15e2e4c in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7face15e2edf in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7face159ea58 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7face15a1526 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7face15a18c4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7face15e5311 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7facec4ed559 in start_thread () from /lib64/libpthread.so.0 #9 0x7facf09fb81f in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7fabdd85b700 (LWP 16970)): #0 0x7facf0a0897c in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7facf0a0a6d4 in __fprintf_chk () from /lib64/libc.so.6 #2 0x7facd90d507d in event_logv_ () from /usr/lib64/libevent-2.1.so.6 #3 0x7facd90d5214 in event_warn () from /usr/lib64/libevent-2.1.so.6 #4 0x7facd90d6b3c in ?? () from /usr/lib64/libevent-2.1.so.6 #5 0x7facd90cc7e4 in event_base_loop () from /usr/lib64/libevent-2.1.so.6 #6 0x7face15e91a4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7face157c38b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7face15b0368 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7face15e5311 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7facec4ed559 in start_thread () from /lib64/libpthread.so.0 #11 0x7facf09fb81f in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7fac5700 (LWP 16967)): #0 0x7facec4f389d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7facda2fd7a4 in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7facda2fd7e9 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7facec4ed559 in start_thread () from /lib64/libpthread.so.0 #4 0x7facf09fb81f in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7fac9c8bb700 (LWP 16965)): #0 0x7facf09f107b in poll () from /lib64/libc.so.6 #1 0x7facb0142831 in ?? () from /usr/lib64/libpulse.so.0 #2 0x7facb01341f0 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0 #3 0x7facb0134880 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7facb0134910 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7facb0142779 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7fac9d5ce438 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #7 0x7facec4ed559 in start_thread () from /lib64/libpthread.so.0 #8 0x7facf09fb81f in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7fac9d575700 (LWP 16964)): #0 0x7facf09ecc0b in write () from /lib64/libc.so.6 #1 0x7facf097e19d in _IO_file_write@@GLIBC_2.2.5 () from /lib64/libc.so.6 #2 0x7facf097d47f in new_do_write () from /lib64/libc.so.6 #3 0x7facf097e95e in __GI__IO_file_xsputn () from /lib64/libc.so.6 #4 0x7facf09548db in buffered_vfprintf () from /lib64/libc.so.6 #5 0x7facf0951b4e in vfprintf () from /lib64/libc.so.6 #6 0x7facf0a0a726 in __fprintf_chk () from /lib64/libc.so.6 #7 0x7facd90d507d in event_logv_ () from /usr/lib64/libevent-2.1.so.6 #8 0x7facd90d5214 in event_warn () from /usr/lib64/libevent-2.1.so.6 #9 0x7facd90d6b3c in ?? () from /usr/lib64/libevent-2.1.so.6 #10 0x7facd90cc7e4 in event_base_loop () from /usr/lib64/libevent-2.1.so.6 #11 0x7face15e9061 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7face157c38b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #13 0x7face15b0368 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #14 0x7face15e5311 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #15 0x7facec4ed559 in start_thread () from /lib64/libpthread.so.0 #16
[kmail2] [Bug 402577] Empty To/Cc field are not reported
https://bugs.kde.org/show_bug.cgi?id=402577 Laurent Montel changed: What|Removed |Added Version Fixed In||5.11.0 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kma ||il/372107d791c7f74900db6e08 ||c6c45d41259140ab Status|REPORTED|RESOLVED --- Comment #2 from Laurent Montel --- Git commit 372107d791c7f74900db6e08c6c45d41259140ab by Laurent Montel. Committed on 21/03/2019 at 07:51. Pushed by mlaurent into branch 'Applications/19.04'. Fix Bug 402577 - Empty To/Cc field are not reported FIXED-IN: 5.11.0 M +1-0src/editor/potentialphishingemail/potentialphishingemailjob.cpp https://commits.kde.org/kmail/372107d791c7f74900db6e08c6c45d41259140ab -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 402258] fatal error "could not create collection outbox, resourceId: 7"
https://bugs.kde.org/show_bug.cgi?id=402258 --- Comment #3 from k...@jason-wong.org --- Same problem here. I'm not sure whether it is version specific. Some background: I have a bunch of filters that move emails into folders. Some months ago I noticed that they started playing up. They were pointing to different destination folders. Each time a filter got "corrupted" I reselected the correct destination folder. About 2 weeks ago a similar thing happened with sent messages - in my account settings I have configured that Sent messages gets put into Inbox (rather than into Sent) - when I went into the account I saw that it was pointing to some other folder, I corrected it by pointing it back to Inbox. So this was working for a few days until there was kmail update. After update kmail no longer starts and gives the error: org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Could not create collection outbox, resourceId: 16" org.kde.pim.mailcommon: "The Email program encountered a fatal error and will terminate now.\nThe error was:\nCould not create collection outbox, resourceId: 16" My guess is that there is a bug or something that is changing/corrupting the resourceId of folders, which is why my filters are pointing to different folders. Is there a quick fix for this? IE a workaround to fix the "Could not create collection outbox" so that I can continue to use kmail whilst the bug is tracked down. Right now I having to use webmail which is not as convenient. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 402258] fatal error "could not create collection outbox, resourceId: 7"
https://bugs.kde.org/show_bug.cgi?id=402258 k...@jason-wong.org changed: What|Removed |Added CC||k...@jason-wong.org --- Comment #2 from k...@jason-wong.org --- Created attachment 118956 --> https://bugs.kde.org/attachment.cgi?id=118956=edit akonadiserver log -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 402577] Empty To/Cc field are not reported
https://bugs.kde.org/show_bug.cgi?id=402577 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I confirm it. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 404704] Kmail has no option to show complete message header
https://bugs.kde.org/show_bug.cgi?id=404704 Laurent Montel changed: What|Removed |Added Status|REPORTED|RESOLVED CC||mon...@kde.org Resolution|--- |FIXED --- Comment #1 from Laurent Montel --- You can click on "v" you will see source of mail. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 405455] Replace smileys with emojis
https://bugs.kde.org/show_bug.cgi?id=405455 --- Comment #3 from Laurent Montel --- In progress I think that it will finish for 19.04 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 405530] no "ham" status icon
https://bugs.kde.org/show_bug.cgi?id=405530 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #5 from Laurent Montel --- I need an mail example as I don't understand your bug report. You have mail without Ham or Unsure info in header ? -- You are receiving this mail because: You are the assignee for the bug.
