[korganizer] [Bug 422783] Filtering tasks by category crashes Korganizer (Kontact)
https://bugs.kde.org/show_bug.cgi?id=422783 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Backtrace please -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #28 from Laurent Montel --- Yep confirmed. It created too many encoding problem so I decided to reverse this patch. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 109413] Wishlist - Event triggers To-do Item
https://bugs.kde.org/show_bug.cgi?id=109413 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 --- Comment #27 from Greg Rivers --- (In reply to Rodney Baker from comment #26) Confirmed. I see this regression as well. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 Rodney Baker changed: What|Removed |Added Version|5.6.0 |5.14.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 Rodney Baker changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #26 from Rodney Baker --- REGRESSION - this was fixed but the issue has recurred in version 5.14.1 (20.04.0). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 Rodney Baker changed: What|Removed |Added Summary|Large messages don't|REGRESSION: Large messages |display in the viewer pane |don't display in the viewer |(eg. New Tumbleweed |pane (eg. New Tumbleweed |snapshot 20171117 |snapshot 20171117 |released!) |released!) -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 360730] Tasklist and the Tooltip displays wrong timezone
https://bugs.kde.org/show_bug.cgi?id=360730 Allen Winter changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/pim/ ||kcalutils/commit/d0d2c30657 ||becf33e7854a6ebcb5ba26acb33 ||d7f Resolution|--- |FIXED --- Comment #1 from Allen Winter --- Git commit d0d2c30657becf33e7854a6ebcb5ba26acb33d7f by Allen Winter, on behalf of Glen Ditchfield. Committed on 10/06/2020 at 22:03. Pushed by winterz into branch 'master'. Improve tool tips for to-dos There are several problems with tool tips for recurring multi-day to-dos: * The due date is wrong. * The start date is just a date, without a time. * The to-do is displayed in the agenda view on the start date. * The agenda view passes the start date down to `dateRangeText()`, which expects the due date. * `dateRangeText()` calls `getNextDateTime()` expecting a due date, but `getNextDateTime()` returns start dates. This patch adjusts `dateRangeText()` to accept any date between the to-do's start and end dates, adjusts the tool tip contents, and incidentally fixes M +2-1autotests/CMakeLists.txt A +397 -0autotests/testtodotooltip.cpp [License: LGPL (v2+)] A +44 -0autotests/testtodotooltip.h [License: LGPL (v2+)] M +40 -26 src/incidenceformatter.cpp M +2-2src/incidenceformatter.h https://invent.kde.org/pim/kcalutils/commit/d0d2c30657becf33e7854a6ebcb5ba26acb33d7f -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 345565] completed recurring to-do recurs on wrong date
https://bugs.kde.org/show_bug.cgi?id=345565 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/kcalendarcore/commit ||/dc7b1865c3bff04d0173505335 ||da22cefa3b5f5f Resolution|--- |FIXED --- Comment #6 from gjditchfi...@acm.org --- Git commit dc7b1865c3bff04d0173505335da22cefa3b5f5f by Glen Ditchfield. Committed on 10/06/2020 at 15:17. Pushed by winterz into branch 'master'. Fix serialization of recurring to-do's start date KCalendarCore uses Todo::Private::mDtRecurrence to hold the start date and time of the next uncompleted occurrance of a recurring Todo, and deserializes it from the X-KDE-LIBKCAL-DTRECURRENCE property of iCalendar files. However, ICalFormatImpl::writeTodo() serializes dtDue() into that property, not dtStart(). When KOrganizer creates a new recurring to-do, it serializes the to-do, then deserializes it to populate the To-Do List view, so the view shows an incorrect start date (and an incorrect due date, which is calculated from the start date). Related: bug 345498 M +1-0autotests/CMakeLists.txt A +83 -0autotests/testdateserialization.cpp [License: LGPL(v3.0+)] A +19 -0autotests/testdateserialization.h [License: LGPL(v3.0+)] M +2-3src/icalformat_p.cpp https://invent.kde.org/frameworks/kcalendarcore/commit/dc7b1865c3bff04d0173505335da22cefa3b5f5f -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 345498] monthly To-do given incorrect start and due dates
https://bugs.kde.org/show_bug.cgi?id=345498 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/kcalendarcore/commit ||/dc7b1865c3bff04d0173505335 ||da22cefa3b5f5f --- Comment #6 from gjditchfi...@acm.org --- Git commit dc7b1865c3bff04d0173505335da22cefa3b5f5f by Glen Ditchfield. Committed on 10/06/2020 at 15:17. Pushed by winterz into branch 'master'. Fix serialization of recurring to-do's start date KCalendarCore uses Todo::Private::mDtRecurrence to hold the start date and time of the next uncompleted occurrance of a recurring Todo, and deserializes it from the X-KDE-LIBKCAL-DTRECURRENCE property of iCalendar files. However, ICalFormatImpl::writeTodo() serializes dtDue() into that property, not dtStart(). When KOrganizer creates a new recurring to-do, it serializes the to-do, then deserializes it to populate the To-Do List view, so the view shows an incorrect start date (and an incorrect due date, which is calculated from the start date). Related: bug 345565 M +1-0autotests/CMakeLists.txt A +83 -0autotests/testdateserialization.cpp [License: LGPL(v3.0+)] A +19 -0autotests/testdateserialization.h [License: LGPL(v3.0+)] M +2-3src/icalformat_p.cpp https://invent.kde.org/frameworks/kcalendarcore/commit/dc7b1865c3bff04d0173505335da22cefa3b5f5f -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 422783] Filtering tasks by category crashes Korganizer (Kontact)
https://bugs.kde.org/show_bug.cgi?id=422783 mull...@adelie.io changed: What|Removed |Added CC||mull...@adelie.io Platform|Other |Fedora RPMs OS|Other |Linux -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 422783] New: Filtering tasks by category crashes Korganizer (Kontact)
https://bugs.kde.org/show_bug.cgi?id=422783 Bug ID: 422783 Summary: Filtering tasks by category crashes Korganizer (Kontact) Product: korganizer Version: 5.13.2 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: todoview Assignee: kdepim-bugs@kde.org Reporter: mull...@adelie.io Target Milestone: --- SUMMARY When filtering tasks by category in Kontact, Kontact momentarily hangs then crashes. The following message is displayed in the console (when Kontact is launched from the console): kf5.kxmlgui: KActionCollection::setComponentName does not work on a KActionCollection containing actions! "korganizer" STEPS TO REPRODUCE 1. Select "Select Categories" drop-down 2. Select category 3. Watch productivity dreams die OBSERVED RESULT Program crashes EXPECTED RESULT Task filtering by category SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 32 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 422775] KMail chrashes after jump from one imap recousrce-folder to another
https://bugs.kde.org/show_bug.cgi?id=422775 Kerler Marian changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Kerler Marian --- Is duplicate from *** This bug has been marked as a duplicate of bug 422433 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 422433] akonadi constanly crash when updating database (due to rollback)
https://bugs.kde.org/show_bug.cgi?id=422433 Kerler Marian changed: What|Removed |Added CC||marianker...@gmail.com --- Comment #2 from Kerler Marian --- *** Bug 422775 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 422775] New: KMail chrashes after jump from one imap recousrce-folder to another
https://bugs.kde.org/show_bug.cgi?id=422775 Bug ID: 422775 Summary: KMail chrashes after jump from one imap recousrce-folder to another Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: marianker...@gmail.com Target Milestone: --- Application: kontact (5.13.3 (19.12.3)) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-37-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04 LTS -- Information about the crash: I have 3 resources from IMAP, if I joum 2 or 3 times from one folder of resource 2 to a folder of resource 3 end back, then kmail chrashes 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 0x7fad378c1f00 (LWP 21721))] Thread 25 (Thread 0x7facd4bf9700 (LWP 25312)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7facd4bf84a0, clockid=, expected=0, futex_word=0x7facd4bf85e8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7facd4bf84a0, clockid=, mutex=0x7facd4bf8598, cond=0x7facd4bf85c0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7facd4bf85c0, mutex=0x7facd4bf8598, abstime=0x7facd4bf84a0) at pthread_cond_wait.c:656 #3 0x7fad4407ab2e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fad4407b51f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fad4407b615 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fad4403cda6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fad4403fc48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fad4403fef8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fad4407db63 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fad49ad7609 in start_thread (arg=) at pthread_create.c:477 #11 0x7fad4aaec103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fad117fa700 (LWP 25306)): #0 0x7fad4913d09d in g_source_ref () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fad4913d168 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fad4913e66b in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fad4913f0db in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fad4913f2e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fad4b098583 in QEventDispatcherGlib::processEvents (this=0x7facf40062d0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fad4b03f4db in QEventLoop::exec (this=this@entry=0x7fad117f96a0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7fad4ae77785 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7fad4ae789d2 in QThreadPrivate::start (arg=0x564b0031d850) at thread/qthread_unix.cpp:361 #9 0x7fad49ad7609 in start_thread (arg=) at pthread_create.c:477 #10 0x7fad4aaec103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7fac93276700 (LWP 21777)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fad4ae7add1 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:105 #2 QtLinuxFutex::futexWait > (expectedValue=, futex=...) at thread/qfutex_p.h:107 #3 futexSemaphoreTryAcquire_loop (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:219 #4 futexSemaphoreTryAcquire (timeout=-1, n=, u=...) at thread/qsemaphore.cpp:262 #5 QSemaphore::acquire (this=0x564aff9955b8, n=) at thread/qsemaphore.cpp:326 #6 0x7faca00c372c in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so #7 0x7fad4ae789d2 in QThreadPrivate::start (arg=0x564aff995580) at thread/qthread_unix.cpp:361 #8 0x7fad49ad7609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fad4aaec103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7fac93fff700 (LWP 21775)): #0 0x7fad4913f2b0 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fad4b098583 in QEventDispatcherGlib::processEvents (this=0x7fac8c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #2 0x7fad4b03f4db in QEventLoop::exec (this=this@entry=0x7fac93ffe6a0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #3 0x7fad4ae77785 in QThread::exec (this=) at
[Akonadi] [Bug 422336] kmail: the access and reading of the received messages is often very slow
https://bugs.kde.org/show_bug.cgi?id=422336 --- Comment #14 from Marc Mezzarobba --- Another, possibly more informative, perf report on the akonadi_maildir_resource process. (I don't understand why perf no longer manages to resolve the symbols are those from libQt5Core; I tried purging the buildid cache, to no avail.) 99.62%99.11% SessionThreadlibQt5Core.so.5.12.5 | |--92.11%--QApplication::notify | QApplicationPrivate::notify_helper | QReadNotifier::event | QAbstractSocketPrivate::canReadNotification | QAbstractSocketPrivate::emitReadyRead | 0x7effbccc1385 | 0x7effbccc14e3 | Akonadi::Connection::handleIncomingData | | | --92.05%--0x7effbccc3bd2 | | | --92.05%--0x7effbccc3240 | |--2.16%--0x7effbcc956d6 | 0x7effbccec7bc | g_main_context_iteration | | | --2.16%--0x7effbb02519b | g_main_context_dispatch | 0x7effbcced3c0 | 0x7effbcc96a50 | QApplication::notify | QApplicationPrivate::notify_helper | QReadNotifier::event | QAbstractSocketPrivate::canReadNotification | | | --2.15%--QAbstractSocketPrivate::emitReadyRead |0x7effbccc1385 || | --2.15%--0x7effbcbd9560 | |--1.99%--g_main_context_iteration | 0x7effbb02519b | g_main_context_dispatch | 0x7effbcced3c0 | 0x7effbcc96a50 | QApplication::notify | QApplicationPrivate::notify_helper | QReadNotifier::event | QAbstractSocketPrivate::canReadNotification | QAbstractSocketPrivate::emitReadyRead | 0x7effbccc1385 | 0x7effbccc14e3 | Akonadi::Connection::handleIncomingData | 0x7effbccc3bd2 | 0x7effbccc3240 | |--1.77%--Akonadi::Connection::handleIncomingData | 0x7effbccc3bd2 | 0x7effbccc3240 | --1.08%--0x7effbcc96a50 QApplication::notify QApplicationPrivate::notify_helper QReadNotifier::event QAbstractSocketPrivate::canReadNotification QAbstractSocketPrivate::emitReadyRead 0x7effbccc1385 0x7effbccc14e3 Akonadi::Connection::handleIncomingData | --1.08%--0x7effbccc3bd2 0x7effbccc3240 97.82% 0.00% SessionThreadlibQt5Widgets.so.5.12.5 | ---QApplication::notify QApplicationPrivate::notify_helper QReadNotifier::event QAbstractSocketPrivate::canReadNotification | --97.82%--QAbstractSocketPrivate::emitReadyRead 0x7effbccc1385 | |--95.66%--0x7effbccc14e3 | | | --95.66%--Akonadi::Connection::handleIncomingData | | | --95.45%--0x7effbccc3bd2 || | --95.44%--0x7effbccc3240 | --2.15%--0x7effbcbd9560 97.82% 0.00% SessionThreadlibQt5Network.so.5.12.5 | --97.82%--QReadNotifier::event QAbstractSocketPrivate::canReadNotification | --97.81%--QAbstractSocketPrivate::emitReadyRead 0x7effbccc1385 | |--95.66%--0x7effbccc14e3 |
[Akonadi] [Bug 422458] Multiple akonadi processes crash
https://bugs.kde.org/show_bug.cgi?id=422458 Nicolas Fella changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Nicolas Fella --- seems fixed -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 422746] Mail Header layout broken
https://bugs.kde.org/show_bug.cgi?id=422746 Christophe Giboudeaux changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||5.14.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 422746] Mail Header layout broken
https://bugs.kde.org/show_bug.cgi?id=422746 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #1 from Wolfgang Bauer --- Will probably be fixed by https://invent.kde.org/pim/messagelib/-/commit/1f2548805df60707ffba2bba27d35d441232d140 in the upcoming 20.04.2 release. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 422746] New: Mail Header layout broken
https://bugs.kde.org/show_bug.cgi?id=422746 Bug ID: 422746 Summary: Mail Header layout broken Product: kmail2 Version: 5.14.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: matrixfuel...@gmail.com Target Milestone: --- Created attachment 129198 --> https://bugs.kde.org/attachment.cgi?id=129198=edit KMail Bug Mail Header UI SUMMARY STEPS TO REPRODUCE 1. Open any Mail you recieved 2. Look at the top where the header summary is normally visible. OBSERVED RESULT See attachment EXPECTED RESULT A non broken UI. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20200604 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70 Qt Version: 5.15 ADDITIONAL INFORMATION The previous snapshot I was on has worked. I can't say which one this was. I know although that it was not older then 2 weeks. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 421930] Crash when asking to input password
https://bugs.kde.org/show_bug.cgi?id=421930 --- Comment #1 from Szőts Ákos --- Application: akonadi_maildispatcher_agent (5.14.1 (20.04.0)) Qt Version: 5.15.0 Frameworks Version: 5.70.0 Operating System: Linux 5.6.14-1-default x86_64 Windowing system: X11 Distribution: openSUSE Tumbleweed -- Information about the crash: - What I was doing when the application crashed: GMail was asking for SMTP password and because of that a password input window was shown. Some seconds later, the agent crashed after it had shown that the remote machine closed the connection. -- Backtrace: Application: akonadi_maildispatcher_agent (akonadi_maildispatcher_agent), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7f52dea77900 (LWP 6863))] Thread 4 (Thread 0x7f52d5f69700 (LWP 6923)): #0 0x7f52e19fba4c in __GI___libc_read (nbytes=16, buf=0x7f52d5f68a80, fd=13) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f52e19fba4c in __GI___libc_read (fd=13, buf=buf@entry=0x7f52d5f68a80, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f52e002e15f in read (__nbytes=16, __buf=0x7f52d5f68a80, __fd=) at /usr/include/bits/unistd.h:44 #3 0x7f52e002e15f in g_wakeup_acknowledge (wakeup=0x7f52c8003590) at ../glib/gwakeup.c:210 #4 0x7f52dffe512e in g_main_context_check (context=context@entry=0x7f52cc000c20, max_priority=2147483647, fds=fds@entry=0x7f52cc004e60, n_fds=n_fds@entry=1) at ../glib/gmain.c:3825 #5 0x7f52dffe5585 in g_main_context_iterate (context=context@entry=0x7f52cc000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4044 #6 0x7f52dffe56ff in g_main_context_iteration (context=0x7f52cc000c20, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #7 0x7f52e1fd0f6b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f52cc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7f52e1f784cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f52d5f68ca0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #9 0x7f52e1d9a73e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #10 0x7f52e1d9b871 in QThreadPrivate::start(void*) (arg=0x5630d2ab31d0) at thread/qthread_unix.cpp:342 #11 0x7f52e09b5eaa in start_thread (arg=) at pthread_create.c:477 #12 0x7f52e1a0ab1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f52d676a700 (LWP 6892)): #0 0x7f52e19fba4c in __GI___libc_read (nbytes=16, buf=0x7f52d6769a80, fd=8) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f52e19fba4c in __GI___libc_read (fd=8, buf=buf@entry=0x7f52d6769a80, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f52e002e15f in read (__nbytes=16, __buf=0x7f52d6769a80, __fd=) at /usr/include/bits/unistd.h:44 #3 0x7f52e002e15f in g_wakeup_acknowledge (wakeup=0x7f52d00039a0) at ../glib/gwakeup.c:210 #4 0x7f52dffe512e in g_main_context_check (context=context@entry=0x7f52c8000c20, max_priority=2147483647, fds=fds@entry=0x7f52d0021020, n_fds=n_fds@entry=1) at ../glib/gmain.c:3825 #5 0x7f52dffe5585 in g_main_context_iterate (context=context@entry=0x7f52c8000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4044 #6 0x7f52dffe56ff in g_main_context_iteration (context=0x7f52c8000c20, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #7 0x7f52e1fd0f6b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f52c8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7f52e1f784cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f52d6769ca0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #9 0x7f52e1d9a73e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #10 0x7f52e1d9b871 in QThreadPrivate::start(void*) (arg=0x5630d2a94d90) at thread/qthread_unix.cpp:342 #11 0x7f52e09b5eaa in start_thread (arg=) at pthread_create.c:477 #12 0x7f52e1a0ab1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f52d6f6b700 (LWP 6891)): #0 0x7f52e19fffef in __GI___poll (fds=0x7f52d0035590, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f52dffe55de in g_main_context_poll (priority=, n_fds=1, fds=0x7f52d0035590, timeout=, context=0x7f52dc20) at ../glib/gmain.c:4346 #2 0x7f52dffe55de in g_main_context_iterate (context=context@entry=0x7f52dc20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4042 #3 0x7f52dffe56ff in g_main_context_iteration (context=0x7f52dc20, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #4 0x7f52e1fd0f6b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f52db60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5
[Akonadi] [Bug 421930] Crash when asking to input password
https://bugs.kde.org/show_bug.cgi?id=421930 Szőts Ákos changed: What|Removed |Added CC||szots...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 422092] Akonadi Server crashing in ItemRetrievalManager while syncing GMail
https://bugs.kde.org/show_bug.cgi?id=422092 --- Comment #7 from Stephan Diestelhorst --- Created attachment 129188 --> https://bugs.kde.org/attachment.cgi?id=129188=edit New crash information added by DrKonqi akonadiserver (5.14.1 (20.04.0)) using Qt 5.14.2 - What I was doing when the application crashed: Same thing, syncing my mailbox with GMail. System freshly updated to 5.19, and crash still happens. -- Backtrace (Reduced): #4 0x7fa092076d1c in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x3030305c3030305c) at /usr/include/c++/7/bits/atomic_base.h:396 #5 QAtomicOps::loadRelaxed (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0x3030305c3030305c) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 [...] #8 QString::operator= (this=this@entry=0x7fa01c159e58, other=...) at text/qstring.cpp:2398 #9 0x55b66cde in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x55b66d219810, request=0x7fa01c159e40, errorMsg=...) at ./src/server/storage/itemretrievalmanager.cpp:176 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 422659] quoted multipart MIME message incorrectly displayed
https://bugs.kde.org/show_bug.cgi?id=422659 Jiaxin Han changed: What|Removed |Added Version|unspecified |5.7.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 422659] quoted multipart MIME message incorrectly displayed
https://bugs.kde.org/show_bug.cgi?id=422659 --- Comment #2 from Jiaxin Han --- the quoted message is a long multipart mime message, which could be displayed correctly in plain text mode. when html display is enabled, the entire quoted message collapses to a single line of cluttered texts. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 422659] quoted multipart MIME message incorrectly displayed
https://bugs.kde.org/show_bug.cgi?id=422659 --- Comment #1 from Jiaxin Han --- Created attachment 129186 --> https://bugs.kde.org/attachment.cgi?id=129186=edit quoted multipart MIME message cluttered -- 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 --- Comment #17 from Diego Ercolani --- Finally I think I've found my hickup: There was a package installed akonadi-search-18.12.3-lp151.1.3.x86_64 /etc/xdg/akonadi-search.categories /etc/xdg/akonadi-search.renamecategories /usr/bin/akonadi_indexing_agent /usr/lib64/qt5/plugins/akonadi /usr/lib64/qt5/plugins/akonadi/akonadi_search_plugin.so /usr/lib64/qt5/plugins/akonadi/calendarsearchstore.so /usr/lib64/qt5/plugins/akonadi/contactsearchstore.so /usr/lib64/qt5/plugins/akonadi/emailsearchstore.so /usr/lib64/qt5/plugins/akonadi/notesearchstore.so /usr/lib64/qt5/plugins/kcm_krunner_pimcontacts.so /usr/lib64/qt5/plugins/krunner_pimcontacts.so /usr/share/akonadi /usr/share/akonadi/agents /usr/share/akonadi/agents/akonadiindexingagent.desktop /usr/share/kservices5/plasma-krunner-pimcontacts.desktop /usr/share/kservices5/plasma-krunner-pimcontacts_config.desktop /usr/share/licenses/akonadi-search /usr/share/licenses/akonadi-search/COPYING /usr/share/licenses/akonadi-search/COPYING.LIB Installed which akonadi consumes all the memory I just removed the package -- You are receiving this mail because: You are the assignee for the bug.
