[kmail2] [Bug 411150] New: KMail crash when restoring from systray
https://bugs.kde.org/show_bug.cgi?id=411150 Bug ID: 411150 Summary: KMail crash when restoring from systray Product: kmail2 Version: 5.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: invictustiber...@gmail.com Target Milestone: --- Application: kmail (5.12.0) Qt Version: 5.12.3 Frameworks Version: 5.61.0 Operating System: Linux 4.15.0-58-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Clicked on KMail icon on system tray to show its window (previously closed to systray, not minimized) - Unusual behavior I noticed: KMail crashed, leaving Dr Konqi notification to Restart Application or send this bug report. - Custom settings of the application: Enabled systray icon. The crash can be reproduced every time. -- 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 0x7f5ac91f9bc0 (LWP 1795))] Thread 23 (Thread 0x7f59f2b6a700 (LWP 2349)): #0 0x7f5abb7f89f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f5aa7663fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f5abb7f89f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f5aa7663f68, cond=0x7f5aa7663f90) at pthread_cond_wait.c:502 #2 0x7f5abb7f89f3 in __pthread_cond_wait (cond=0x7f5aa7663f90, mutex=0x7f5aa7663f68) at pthread_cond_wait.c:655 #3 0x7f5aa736d844 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f5aa736d889 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f5abb7f26db in start_thread (arg=0x7f59f2b6a700) at pthread_create.c:463 #6 0x7f5ac622d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f59fb7fe700 (LWP 2301)): #0 0x7f5ac621c0b4 in __GI___libc_read (fd=89, buf=0x7f59fb7fd7d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f5ab996a2d0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5ab99250b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5ab9925570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5ab99256dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f5ac6b63dcb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f59ec000c80, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f5ac6b0503a in QEventLoop::exec(QFlags) (this=this@entry=0x7f59fb7fd9e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f5ac692c4ca in QThread::exec() (this=) at thread/qthread.cpp:531 #8 0x7f5ac692dc72 in QThreadPrivate::start(void*) (arg=0x5595c484e080) at thread/qthread_unix.cpp:361 #9 0x7f5abb7f26db in start_thread (arg=0x7f59fb7fe700) at pthread_create.c:463 #10 0x7f5ac622d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f5a18c5a700 (LWP 1999)): #0 0x7f5abb7f89f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f5a18c59908) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f5abb7f89f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f5a18c598b8, cond=0x7f5a18c598e0) at pthread_cond_wait.c:502 #2 0x7f5abb7f89f3 in __pthread_cond_wait (cond=0x7f5a18c598e0, mutex=0x7f5a18c598b8) at pthread_cond_wait.c:655 #3 0x7f5ab0678a49 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f5ab0679478 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f5ab067950f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f5ab0639fc8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f5ab063c7f6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f5ab063cb34 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f5ab067b561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f5abb7f26db in start_thread (arg=0x7f5a18c5a700) at pthread_create.c:463 #11 0x7f5ac622d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f5a1b7fe700 (LWP 1971)): #0 0x7f5aa89a4d95 in pa_mainloop_poll () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #1 0x7f5aa89a54d0 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f5aa89a5560 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f5aa89b33c9 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f5aa075e318 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #5 0x7f5abb7f26db in start_thread (arg=0x7f5a1b7fe700) at pthread_create.c:463 #6 0x7f5ac622d88f in clone () at
[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file
https://bugs.kde.org/show_bug.cgi?id=411093 --- Comment #6 from Dan --- So, this worked for me, but after rebooting my machine, akonadi did not start, and a manual start with akonadictl resulted in the same old failure and error messages, and I had to tear down and restart apparmor again. I assume I'll have to do this every time I start my desktop or laptop. So, this is an ugly work-around, not really a solution. Any idea how to get apparmor to permit access to the required files permanently? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411147] New: IMAP resource permanently offline "Cannot read password. User denied access to wallet"
https://bugs.kde.org/show_bug.cgi?id=411147 Bug ID: 411147 Summary: IMAP resource permanently offline "Cannot read password. User denied access to wallet" Product: kmail2 Version: 5.11.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: matthias.h.na...@gmail.com Target Milestone: --- After upgrading to version 5.1.3 (kde-apps/kmail-19.04.3 in Gentoo) the IMAP resource for my Gmail IMAP account is permanently offline. When I try to restart the akonadi resource, try to toggle the online/offline state, I get the error "Cannot read password. User denied access to wallet." Then the resource turns offline again. I already have tried to re-enter the password in the settings. I also tried to entirely delete the IMAP resource and re-create it again, in case there is some odd configuration error. The error remains. Interestingly, this only happens with Gmail. I have three other IMAP accounts at different providers that all work and use Kwallet as the password storage. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.60.0 Qt Version: 5.12 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 411141] New: too long header lines generated when bouncing mail
https://bugs.kde.org/show_bug.cgi?id=411141 Bug ID: 411141 Summary: too long header lines generated when bouncing mail Product: kontact Version: 5.7.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: k...@opensource.sf-tec.de Target Milestone: --- I have received a mail with many recipient in To: as well as a "X-YMail-OSG:" header (from AOL). Both headers are long, but correctly folded. When I now bounce that mail these lines get unfolded, breaking the 1000 char length limit of SMTP and are correctly rejected by my mail server. KDE Frameworks Version: 5.45.0 Qt Version: 5.9.4 This could be related to bug 409169, I'm unsure if it hits the same code paths. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 411137] New: Esc key closes the editor without saving
https://bugs.kde.org/show_bug.cgi?id=411137 Bug ID: 411137 Summary: Esc key closes the editor without saving Product: korganizer Version: 5.11.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: incidence editors Assignee: kdepim-bugs@kde.org Reporter: m...@bowtie.nl Target Milestone: --- SUMMARY When editing an event and, for example, hitting a wrong key which displays the search window, one needs to press ESC to leave the popup and return to the event editor, however if one is too diligent and presses ESC more than once, the event editor is closed without saving. Above popup is just an example how one might need to press the ESC key while editing an event. STEPS TO REPRODUCE 1. Start editing/adding an event 2. Hit ESC 3. Event editor closes without saving OBSERVED RESULT The work entered is lost EXPECTED RESULT If changes have been made either don't close the editor, or ask confirmation. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux (x86_64) release 5.2.1-arch1-1-ARCH (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 411131] New: kmail crashed when scrolling in the viewer window
https://bugs.kde.org/show_bug.cgi?id=411131 Bug ID: 411131 Summary: kmail crashed when scrolling in the viewer window Product: kontact Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: stefan.schwar...@gmx.net Target Milestone: --- Application: kontact (5.9.3) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-5-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: kmail segfaulted when scrolling in the viewer window. The message was signed, had both a text and html message and contained two encapsulated forwarded text emails. I cannot always reproduce this behavior, but it happens frequently also on other messages to me, mostly (as it of course the most probable) when the message looked at is not the first. There are bugreports about kmail crashing when closing subwindows and this may be duplicate. However, as I got a reasonable stacktrace, the report may be of help. 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 0x7fb1a499c440 (LWP 10471))] Thread 31 (Thread 0x7fb1857fa700 (LWP 11350)): #0 0x7fb1b76193f9 in futex_reltimed_wait_cancelable (private=0, reltime=0x7fb1857f9400, expected=0, futex_word=0x7fb1857f95e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fb1b76193f9 in __pthread_cond_wait_common (abstime=0x7fb1857f94a0, mutex=0x7fb1857f9598, cond=0x7fb1857f95c0) at pthread_cond_wait.c:533 #2 0x7fb1b76193f9 in __pthread_cond_timedwait (cond=0x7fb1857f95c0, mutex=0x7fb1857f9598, abstime=0x7fb1857f94a0) at pthread_cond_wait.c:667 #3 0x7fb1b15a5a37 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fb1b15a830a in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fb1b15a83f2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fb1b15ac981 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fb1b15ade61 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fb1b15b6c81 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fb1b7612fa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7fb1b87d04cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7fb16700 (LWP 11285)): #0 0x7fb1b76193f9 in futex_reltimed_wait_cancelable (private=0, reltime=0x7fb16fffe400, expected=0, futex_word=0x7fb16fffe5e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fb1b76193f9 in __pthread_cond_wait_common (abstime=0x7fb16fffe4a0, mutex=0x7fb16fffe598, cond=0x7fb16fffe5c0) at pthread_cond_wait.c:533 #2 0x7fb1b76193f9 in __pthread_cond_timedwait (cond=0x7fb16fffe5c0, mutex=0x7fb16fffe598, abstime=0x7fb16fffe4a0) at pthread_cond_wait.c:667 #3 0x7fb1b15a5a37 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fb1b15a830a in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fb1b15a83f2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fb1b15ac981 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fb1b15ade61 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fb1b15b6c81 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fb1b7612fa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7fb1b87d04cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7fb07affd700 (LWP 10565)): #0 0x7fb1b6cd4829 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb1b6c89d08 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb1b8d473e3 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fb1b8cf4cfb in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb1b8b44d8e in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb1b8b4ea07 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb1b7612fa3 in start_thread (arg=) at pthread_create.c:486 #7 0x7fb1b87d04cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fb0866a6700 (LWP 10538)): #0 0x7fb1b8d471c5 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fb1b6c895d1 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb1b6c89ba0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb1b6c89d1c in g_main_context_iteration () at
[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file
https://bugs.kde.org/show_bug.cgi?id=411093 Daniel Kraus changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Daniel Kraus --- The problem was solved by tearing down AppArmor, then restarting it. ``` sudo service apparmor teardown sudo service apparmor start ``` (NB: `systemctl` cannot handle the `teardown` task, and `stop` won't do it) -- You are receiving this mail because: You are the assignee for the bug.
