[kontact] [Bug 405052] sieve editor can't be opened
https://bugs.kde.org/show_bug.cgi?id=405052 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 405005] Disappearing menu (edited)
https://bugs.kde.org/show_bug.cgi?id=405005 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 406167] New: Show all messages in mbox
https://bugs.kde.org/show_bug.cgi?id=406167 Bug ID: 406167 Summary: Show all messages in mbox Product: kmail2 Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: jsc...@posteo.net Target Milestone: --- I find it handy to download mbox files with multiple messages, mostly for the sake of working with Debian's BTS. Opening an mbox for a bug shows "The file contains multiple messages. Only the first message is shown." It would be nice to see the other messages inside. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 406165] New: KOrganizer crashed
https://bugs.kde.org/show_bug.cgi?id=406165 Bug ID: 406165 Summary: KOrganizer crashed Product: korganizer 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: reinhardau...@gmx.at Target Milestone: --- Application: korganizer (5.10.3) Qt Version: 5.9.7 Frameworks Version: 5.55.0 Operating System: Linux 5.0.5-lp151.23-default x86_64 Distribution: "openSUSE Leap 15.1Beta" -- Information about the crash: - What I was doing when the application crashed: I was using KOrganizer and trying to add a new appointment, when, suddenly, KOrganizer crashed. -- Backtrace: Application: KOrganizer (korganizer), 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 0x7fb2f1de9940 (LWP 314))] Thread 9 (Thread 0x7fb2ae73f700 (LWP 407)): #0 0x7fb2e50258ad in futex_wait_cancelable (private=, expected=0, futex_word=0x7fb2de370fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fb2de370f68, cond=0x7fb2de370f90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fb2de370f90, mutex=0x7fb2de370f68) at pthread_cond_wait.c:655 #3 0x7fb2de07b574 in ?? () from /usr/lib64/libQt5Script.so.5 #4 0x7fb2de07b5b9 in ?? () from /usr/lib64/libQt5Script.so.5 #5 0x7fb2e501f569 in start_thread (arg=0x7fb2ae73f700) at pthread_create.c:465 #6 0x7fb2ed5389af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fb2bb93f700 (LWP 401)): #0 0x7fb2c0318b17 in pa_srbchannel_read () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #1 0x7fb2c03150c0 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #2 0x7fb2c0317dbb in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #3 0x7fb2c0318159 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #4 0x7fb2c03189df in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #5 0x7fb2c057e4e8 in pa_mainloop_dispatch () from /usr/lib64/libpulse.so.0 #6 0x7fb2c057e8be in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #7 0x7fb2c057e940 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #8 0x7fb2c058c7a9 in ?? () from /usr/lib64/libpulse.so.0 #9 0x7fb2c0328428 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #10 0x7fb2e501f569 in start_thread (arg=0x7fb2bb93f700) at pthread_create.c:465 #11 0x7fb2ed5389af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fb2c375f700 (LWP 350)): #0 0x7fb2e50258ad in futex_wait_cancelable (private=, expected=0, futex_word=0x55a2650827a8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55a265082758, cond=0x55a265082780) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55a265082780, mutex=0x55a265082758) at pthread_cond_wait.c:655 #3 0x7fb2c8e6088b in ?? () from /usr/lib64/dri/r600_dri.so #4 0x7fb2c8e60597 in ?? () from /usr/lib64/dri/r600_dri.so #5 0x7fb2e501f569 in start_thread (arg=0x7fb2c375f700) at pthread_create.c:465 #6 0x7fb2ed5389af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fb2c40df700 (LWP 349)): #0 0x7fb2e50258ad in futex_wait_cancelable (private=, expected=0, futex_word=0x55a265081c14) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55a265081bc0, cond=0x55a265081be8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55a265081be8, mutex=0x55a265081bc0) at pthread_cond_wait.c:655 #3 0x7fb2c8e6088b in ?? () from /usr/lib64/dri/r600_dri.so #4 0x7fb2c8e60597 in ?? () from /usr/lib64/dri/r600_dri.so #5 0x7fb2e501f569 in start_thread (arg=0x7fb2c40df700) at pthread_create.c:465 #6 0x7fb2ed5389af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fb2d01ff700 (LWP 330)): #0 0x7fb2e318bfd9 in g_mutex_lock (mutex=mutex@entry=0x55a264a47950) at gthread-posix.c:1336 #1 0x7fb2e31451d4 in g_main_context_release (context=0x55a264a47950) at gmain.c:3242 #2 0x7fb2e3146166 in g_main_context_iterate (context=context@entry=0x55a264a47950, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3870 #3 0x7fb2e31462bc in g_main_context_iteration (context=0x55a264a47950, may_block=may_block@entry=1) at gmain.c:3929 #4 0x7fb2ee09796b in QEventDispatcherGlib::processEvents (this=0x55a264ad2590, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fb2ee03c90a in QEventLoop::exec (this=this@entry=0x7fb2d01fec70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7fb2ede5adaa in
[Akonadi] [Bug 395131] Akonadi consumes all memory
https://bugs.kde.org/show_bug.cgi?id=395131 --- Comment #12 from Dennis Schridde --- I also notice regularly (maybe related?) that `akonadictl fsck` finds a lot of "Cleaning up missing external file: ..." and "Found unreferenced external file: ...". ~/.local/share/akonadi/file_lost+found/ contains 3.5 million files. Akonadi regularly re-downloads entire folders via IMAP, after printing on the console that it detected a mismatch in the number of emails in that folder between itself and the IMAP server. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 367892] During folder synchronisation Akonadi blocks out other operations like deleting or viewing mails
https://bugs.kde.org/show_bug.cgi?id=367892 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 397580] Write / flush emails that are missing at disk
https://bugs.kde.org/show_bug.cgi?id=397580 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 405975] Crash when changing Mail Folder name in KMail
https://bugs.kde.org/show_bug.cgi?id=405975 --- Comment #3 from Allen Winter --- https://phabricator.kde.org/D20207 has a possible patch -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 406154] New: kmail closes too early
https://bugs.kde.org/show_bug.cgi?id=406154 Bug ID: 406154 Summary: kmail closes too early Product: kmail2 Version: 5.10.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kwanza.p...@virginmedia.com Target Milestone: --- Application: kmail (5.10.3) (Compiled from sources) Qt Version: 5.12.2 Frameworks Version: 5.56.0 Operating System: Linux 4.19.23-1.1 x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: Every time I close kmail, I get this error "application terminated unexpectedly" I think this is caused by some code deleting data too early (as suggested by some QT developers). The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4bc7c6fc40 (LWP 27443))] Thread 26 (Thread 0x7f4b10687700 (LWP 28142)): #0 0x7f4bf4e48609 in syscall () at /lib64/libc.so.6 #1 0x7f4bf55659a4 in QSemaphore::acquire(int) () at /opt/kde/lib64/libQt5Core.so.5 #2 0x7f4bec058ae4 in () at /opt/kde/lib64/libQt5Network.so.5 #3 0x7f4bf5563723 in () at /opt/kde/lib64/libQt5Core.so.5 #4 0x7f4beaab9d95 in start_thread () at /lib64/libpthread.so.0 #5 0x7f4bf4e4d6ef in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f4b92dc3700 (LWP 27933)): #0 0x7f4beaabfc7c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4bdab32ada in () at /opt/kde/lib64/libQt5Script.so.5 #2 0x7f4bdab32af9 in () at /opt/kde/lib64/libQt5Script.so.5 #3 0x7f4beaab9d95 in start_thread () at /lib64/libpthread.so.0 #4 0x7f4bf4e4d6ef in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f4b962a5700 (LWP 27869)): #0 0x7ffc77ab29fd in clock_gettime () #1 0x7f4bf4e5af76 in clock_gettime () at /lib64/libc.so.6 #2 0x7f4bf575a001 in () at /opt/kde/lib64/libQt5Core.so.5 #3 0x7f4bf57588e9 in QTimerInfoList::updateCurrentTime() () at /opt/kde/lib64/libQt5Core.so.5 #4 0x7f4bf5758e95 in QTimerInfoList::timerWait(timespec&) () at /opt/kde/lib64/libQt5Core.so.5 #5 0x7f4bf575a39e in () at /opt/kde/lib64/libQt5Core.so.5 #6 0x7f4be8456f41 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f4be84578d3 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f4be8457aac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f4bf575a5fb in QEventDispatcherGlib::processEvents(QFlags) () at /opt/kde/lib64/libQt5Core.so.5 #10 0x7f4bf5708d3b in QEventLoop::exec(QFlags) () at /opt/kde/lib64/libQt5Core.so.5 #11 0x7f4bf55624b6 in QThread::exec() () at /opt/kde/lib64/libQt5Core.so.5 #12 0x7f4bf5563723 in () at /opt/kde/lib64/libQt5Core.so.5 #13 0x7f4beaab9d95 in start_thread () at /lib64/libpthread.so.0 #14 0x7f4bf4e4d6ef in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f4b99c6e700 (LWP 27685)): #0 0x7f4beaac0046 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4bdfe19d37 in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #2 0x7f4bdfe1a68a in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #3 0x7f4bdfe1a772 in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #4 0x7f4bdfdd8111 in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #5 0x7f4bdfdda727 in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #6 0x7f4bdfddad14 in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #7 0x7f4bdfe1c891 in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #8 0x7f4beaab9d95 in start_thread () at /lib64/libpthread.so.0 #9 0x7f4bf4e4d6ef in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f4b9a46f700 (LWP 27676)): #0 0x7f4beaabfc7c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4bdfe19c69 in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #2 0x7f4bdfe1a698 in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #3 0x7f4bdfe1a72f in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #4 0x7f4bdfdd8128 in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #5 0x7f4bdfddaa56 in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #6 0x7f4bdfddad94 in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #7 0x7f4bdfe1c891 in () at /opt/kde/lib64/libQt5WebEngineCore.so.5 #8 0x7f4beaab9d95 in start_thread () at /lib64/libpthread.so.0 #9 0x7f4bf4e4d6ef in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f4baa443700 (LWP 27630)): #0 0x7f4bf4e3f1f4 in read () at /lib64/libc.so.6 #1 0x7f4bd15f5601 in pa_read () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7f4bd87280be in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0 #3 0x7f4bd8728ae0 in
[Akonadi] [Bug 395131] Akonadi consumes all memory
https://bugs.kde.org/show_bug.cgi?id=395131 Hans-Peter Jansen changed: What|Removed |Added CC||h...@urpla.net -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 406142] New: Kontact crashes after accepting meeting invitation
https://bugs.kde.org/show_bug.cgi?id=406142 Bug ID: 406142 Summary: Kontact crashes after accepting meeting invitation Product: kontact Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tonym...@gmail.com Target Milestone: --- Application: kontact (5.10.1) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 5.0.5-050005-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: Accepting the meeting invitation from my emails and select to store it in my personal calendar. - Custom settings of the application: Using davmail setup to connect to Exchange server The crash can be reproduced every time. -- Backtrace: 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 0x7f5bc41e6bc0 (LWP 7755))] Thread 27 (Thread 0x7f5a5956f700 (LWP 31689)): #0 0x7f5bbc422ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f5a5956e710, expected=0, futex_word=0x7f5a5956e8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f5bbc422ed9 in __pthread_cond_wait_common (abstime=0x7f5a5956e7b0, mutex=0x7f5a5956e8a8, cond=0x7f5a5956e8d0) at pthread_cond_wait.c:533 #2 0x7f5bbc422ed9 in __pthread_cond_timedwait (cond=0x7f5a5956e8d0, mutex=0x7f5a5956e8a8, abstime=0x7f5a5956e7b0) at pthread_cond_wait.c:667 #3 0x7f5bb1a82177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f5bb1a82ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f5bb1a82bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f5bb1a40851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f5bb1a43387 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f5bb1a43974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f5bb1a84cd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f5bbc41c6db in start_thread (arg=0x7f5a5956f700) at pthread_create.c:463 #11 0x7f5bc0b2788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f5a59d70700 (LWP 31688)): #0 0x7f5bbc422ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f5a59d6f710, expected=0, futex_word=0x7f5a59d6f8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f5bbc422ed9 in __pthread_cond_wait_common (abstime=0x7f5a59d6f7b0, mutex=0x7f5a59d6f8a8, cond=0x7f5a59d6f8d0) at pthread_cond_wait.c:533 #2 0x7f5bbc422ed9 in __pthread_cond_timedwait (cond=0x7f5a59d6f8d0, mutex=0x7f5a59d6f8a8, abstime=0x7f5a59d6f7b0) at pthread_cond_wait.c:667 #3 0x7f5bb1a82177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f5bb1a82ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f5bb1a82bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f5bb1a40851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f5bb1a436b6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f5bb1a43974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f5bb1a84cd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f5bbc41c6db in start_thread (arg=0x7f5a59d70700) at pthread_create.c:463 #11 0x7f5bc0b2788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f5b637fe700 (LWP 31687)): #0 0x7f5bbc422ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f5b637fd710, expected=0, futex_word=0x7f5b637fd8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f5bbc422ed9 in __pthread_cond_wait_common (abstime=0x7f5b637fd7b0, mutex=0x7f5b637fd8a8, cond=0x7f5b637fd8d0) at pthread_cond_wait.c:533 #2 0x7f5bbc422ed9 in __pthread_cond_timedwait (cond=0x7f5b637fd8d0, mutex=0x7f5b637fd8a8, abstime=0x7f5b637fd7b0) at pthread_cond_wait.c:667 #3 0x7f5bb1a82177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f5bb1a82ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f5bb1a82bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f5bb1a40851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f5bb1a436b6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f5bb1a43974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f5bb1a84cd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f5bbc41c6db in start_thread (arg=0x7f5b637fe700) at pthread_create.c:463 #11 0x7f5bc0b2788f in clone () at
[kmail2] [Bug 406141] New: Kmail crash with nouveau driver
https://bugs.kde.org/show_bug.cgi?id=406141 Bug ID: 406141 Summary: Kmail crash with nouveau driver Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: sergusha...@yahoo.com Target Milestone: --- Application: kmail (5.10.2) Qt Version: 5.11.3 Frameworks Version: 5.55.0 Operating System: Linux 5.0.4-200.fc29.x86_64 x86_64 Distribution: "Fedora release 29 (Twenty Nine)" -- Information about the crash: Hi guys, Kmail crashes happens everytime. When I open Kmal and try to read some message, when I open Kmail and try to open mailbox, when I try to scroll messages, it seems like does not matter what I do, just fact that I do. When I dont do any actions with Kmail windows crash does not happen. Some time I can open mailbox, read some letter, but then it happens again. I have no this troubles when I using nvidia driver, only with nouveau and new Kmail. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd84a47d980 (LWP 26465))] Thread 33 (Thread 0x7fd7078a6700 (LWP 26559)): #0 0x7fd856addb28 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd851635607 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #2 0x7fd8516372ca in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #3 0x7fd8516373b2 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161 #4 0x7fd85163c171 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171 #5 0x7fd85163d46f in base::internal::SchedulerWorker::Thread::ThreadMain () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:42 #6 0x7fd851647a81 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75 #7 0x7fd856ad758e in start_thread () from /lib64/libpthread.so.0 #8 0x7fd857b276a3 in clone () from /lib64/libc.so.6 Thread 32 (Thread 0x7fd797496700 (LWP 26558)): #0 0x7fd856addb28 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd851635607 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #2 0x7fd8516372ca in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #3 0x7fd8516373b2 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161 #4 0x7fd85163c171 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171 #5 0x7fd85163d46f in base::internal::SchedulerWorker::Thread::ThreadMain () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:42 #6 0x7fd851647a81 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75 #7 0x7fd856ad758e in start_thread () from /lib64/libpthread.so.0 #8 0x7fd857b276a3 in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7fd7959f2700 (LWP 26538)): #0 0x7fd856addb28 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd851635607 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120 #2 0x7fd8516372ca in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221 #3 0x7fd8516373b2 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161 #4 0x7fd85163c171 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171 #5 0x7fd85163d651 in base::internal::SchedulerWorker::Thread::ThreadMain () at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:68 #6 0x7fd851647a81 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75 #7 0x7fd856ad758e in start_thread () from /lib64/libpthread.so.0 #8 0x7fd857b276a3 in clone () from /lib64/libc.so.6 Thread 30 (Thread 0x7fd7961f3700 (LWP 26536)): #0 0x7fd856add73c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd84b041fda in ?? () from /lib64/libQt5Script.so.5 #2 0x7fd84b042045 in ?? () from /lib64/libQt5Script.so.5 #3
[Akonadi] [Bug 394839] pimitemtable.remoteid Column Too Small For Exchange Calendar Via davmail
https://bugs.kde.org/show_bug.cgi?id=394839 Christophe Giboudeaux changed: What|Removed |Added CC||dvra...@kde.org -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 406133] knotes 18.12.3 can't start after update
https://bugs.kde.org/show_bug.cgi?id=406133 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Antonio Rojas --- Packaging issue -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406136] New: DAV resource syncs too eagerly, causing dirty entries
https://bugs.kde.org/show_bug.cgi?id=406136 Bug ID: 406136 Summary: DAV resource syncs too eagerly, causing dirty entries Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: k...@equaeghe.nospammail.net Target Milestone: --- I use Zanshin to manage my todos stored in Akonadi. Zanshin saves as-you-type and therefore a lot of updates happen subsequently in Akonadi. The DAV resource then apparently tries to sync all of those short after each other. This is too fast for the network connection or server and then the edited entry becomes dirty. (Any entry edited or added after that also becomes dirty.) This is unrecoverable in Zanshin or the standard todo application and so I need to do a time-consuming cleanup: 1. Using Akonadiconsole, find the dirty entries, copy their content to a file somewhere and delete them from Akonadi 2. Stop Akonadi 3. Delete the agent_config_akonadi_davgroupware_resource_xy_changes.dat file from ~/.config/akonadi. (N.B.: This file should be placed in ~/.local/share/akonadi I think, but that's another issue.) 4. Restart Akonadi 5. Manually re-edit or re-add the entries that were dirty. I think that it is a bug that Akonadi syncs so eagerly as to cause dirty entries. It's a major issue, because it requires a cleanup procedure non-skilled people will not be able to find. I think that as long as Akonadi allows Zanshin to write so eagerly to the database, it should handle such additions intelligently. Probably this means adding a minimal time between syncs or disallow concurrent syncing. SOFTWARE/OS VERSIONS Akonadi: 18.12.3 (qtsqlite) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 394839] pimitemtable.remoteid Column Too Small For Exchange Calendar Via davmail
https://bugs.kde.org/show_bug.cgi?id=394839 Erik Quaeghebeur changed: What|Removed |Added CC||ad1r...@hotmail.fr --- Comment #6 from Erik Quaeghebeur --- *** Bug 406106 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406106] RemoteID is too small MYSQL error
https://bugs.kde.org/show_bug.cgi?id=406106 Erik Quaeghebeur changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||k...@equaeghe.nospammail.net --- Comment #1 from Erik Quaeghebeur --- *** This bug has been marked as a duplicate of bug 394839 *** -- You are receiving this mail because: You are the assignee for the bug.
