[kontact] [Bug 409708] New: kjots kontact
https://bugs.kde.org/show_bug.cgi?id=409708 Bug ID: 409708 Summary: kjots kontact 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: antonio@debianport.cloud 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 10 (buster) -- Information about the crash: debian stable with only main in apt. in kontact inserted note in kjots when I click on the kontact home page the application crasch 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 0x7fa78cb75f00 (LWP 2353))] Thread 34 (Thread 0x7fa6413a7700 (LWP 5918)): #0 0x7fa78d912494 in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fa77725ffc1 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #2 0x7fa7772e54fe in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fa7772e5f60 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fa7772e6020 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fa7772f4049 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fa77728f4f8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #7 0x7fa78c70ffa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7fa78d9214cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 33 (Thread 0x7fa63bfff700 (LWP 5873)): #0 0x7fa78bbafe84 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa78bb66266 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa78de5387b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fa78de0127b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa78dc50ec6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa78dc5aaa7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa78c70ffa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x7fa78d9214cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 32 (Thread 0x7fa75700 (LWP 3873)): #0 0x7fa78d912494 in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fa78bbabaa0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa78bb65c0f in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa78bb660e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa78bb6625c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa78de5387b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa78de0127b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa78dc50ec6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa78dc5aaa7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fa78c70ffa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7fa78d9214cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 31 (Thread 0x7fa71b7fe700 (LWP 3862)): #0 0x7fa78bbafe69 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa78bb654d7 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa78bb6606b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa78bb6625c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa78de5387b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa78de0127b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa78dc50ec6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa78dc5aaa7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa78c70ffa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7fa78d9214cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 30 (Thread 0x7fa75effd700 (LWP 3859)): #0 0x7fa78d916819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fa78bb66136 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa78bb6625c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa78de5387b in
[kmail2] [Bug 81778] KMail should not always reply to mailing lists by default
https://bugs.kde.org/show_bug.cgi?id=81778 --- Comment #16 from gjditchfi...@acm.org --- I attached two messages for test cases, one that fails and one that passes. "List-Post and Reply-To" contains a List-Post header with a mailing list address and a Reply-To header with a different address. That is the test case that Denis Kurz needed in comment 13. Using Kmail 5.7.3, when I select that message and press the "Reply" button, the reply's To address is set to the reply-to address, not the list's address, so this bug is fixed for that case. The attachment "List-Post and no Reply-To" matches the original problem reported by Peter, 15 years ago. It contains a List-Post header with a mailing list address, a Sender header with a different address, a From header with a third address, and no Reply-To header. When I reply to it, the reply's To addresses are set to the original To and CC addresses, not the From address! This behavior is different from the original report, but it is still incorrect. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 81778] KMail should not always reply to mailing lists by default
https://bugs.kde.org/show_bug.cgi?id=81778 --- Comment #15 from gjditchfi...@acm.org --- Created attachment 121459 --> https://bugs.kde.org/attachment.cgi?id=121459=edit List-Post and Reply-To -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 81778] KMail should not always reply to mailing lists by default
https://bugs.kde.org/show_bug.cgi?id=81778 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org --- Comment #14 from gjditchfi...@acm.org --- Created attachment 121458 --> https://bugs.kde.org/attachment.cgi?id=121458=edit List-Post and no Reply-To -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 409704] New: Kontact's settings-window is taller than screenheight and cannot resize
https://bugs.kde.org/show_bug.cgi?id=409704 Bug ID: 409704 Summary: Kontact's settings-window is taller than screenheight and cannot resize Product: kontact Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ilove...@mojo.cc Target Milestone: --- The Kontact's settings-window cannot be resized in height to fit screen .. STEPS TO REPRODUCE 1. Kontact > Settings 2. Window opens but cannot fit screen OBSERVED RESULT i cannot resize the window in heigth lesser than 1481 or so on a hidpi screen EXPECTED RESULT beeing able fit window to scrren SOFTWARE/OS VERSION opensuse 15.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376032] Emails not being moved from "new" to "cur"
https://bugs.kde.org/show_bug.cgi?id=376032 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409695] New: pasting URI in composer doesnt add href in richtextmode
https://bugs.kde.org/show_bug.cgi?id=409695 Bug ID: 409695 Summary: pasting URI in composer doesnt add href in richtextmode Product: kmail2 Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: ilove...@mojo.cc Target Milestone: --- Pasting an (https://) URI into the composingeditor does not handle href in richtext-mode STEPS TO REPRODUCE 1. paste an URI 2. send mail 3. URI recieved doesnot implement
[kmail2] [Bug 409692] New: Problem sending messages and emptying the recycle bin
https://bugs.kde.org/show_bug.cgi?id=409692 Bug ID: 409692 Summary: Problem sending messages and emptying the recycle bin Product: kmail2 Version: 5.11.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: xiberra...@outlook.com Target Milestone: --- Hello Sending messages is not always done: so the error does not come from me. The message basket empties well but immediately fills up with the same messages. On this same pc Thunderbird works well but I would have liked to use kmail on Archlinux kde plasma. My greetings to you -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 345979] kmail stucks reegualary when syncing a gmail-imap-akonadi-ressource
https://bugs.kde.org/show_bug.cgi?id=345979 --- Comment #6 from avlas --- This happens to me (in KDE neon) most of the times after "Accepting a Google Calendar Invitation Request" in my gmail account. The email that is sent (not always but very frequently, I would say 80% of the times or more) gets stuck and then no more emails can be sent from any account (gmail and others). Saying because if you could reproduce this behavior, it may help to debug and fix the issue. [Note: I have the feeling that this happens more frequently if the akonadi process has been running for a while] -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 409656] Unable to get feeds
https://bugs.kde.org/show_bug.cgi?id=409656 --- Comment #4 from Manuel Alcaraz --- Hello. I don't use a proxy server and I don't have the ad blocker plugin enabled. After some tests, I think that the error is caused after resuming from hibernation. I installed kdebugsettings and I get this error: kf5.syndication: Retriever error: 114 This time a could fetch my feeds after manually clicking on the "Fetch All Feeds" button, but auto update didn't work. Note: > This happened since Akregator updated to 5.11.2 I'm not sure -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 345979] kmail stucks reegualary when syncing a gmail-imap-akonadi-ressource
https://bugs.kde.org/show_bug.cgi?id=345979 Tom Kijas changed: What|Removed |Added CC||t.ki...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Version|5.6.0 |5.11.2 --- Comment #5 from Tom Kijas --- I have same experience for months and THANK YOU for workaround - akonadictl restart in konsole. I use latest KDE NEON (Ubuntu based) User edition KMail 5.11.2 KDE Frameworks 5.59.0 Qt 5.12.3 regularly the akonadi dies and emails stays in Outgoing folder forever. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409679] New: Kmail crash when open through a mailto link
https://bugs.kde.org/show_bug.cgi?id=409679 Bug ID: 409679 Summary: Kmail crash when open through a mailto link Product: kmail2 Version: 5.11.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: sylv...@sbx.pm Target Milestone: --- Application: kmail (5.11.2) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.15.0-54-generic x86_64 Distribution: KDE neon Plasma LTS Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: I clicked on a link like mailto:x...@yyy.com, in Firefox. Kmail never opened but the error reporting tool was shown. I tried twice and the error was thrown each times. 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 0x7f898767bbc0 (LWP 26688))] Thread 20 (Thread 0x7f88cbfff700 (LWP 27595)): #0 0x7f8979e31ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f88cbffe710, expected=0, futex_word=0x7f88cbffe8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f88cbffe7b0, mutex=0x7f88cbffe8a8, cond=0x7f88cbffe8d0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7f88cbffe8d0, mutex=0x7f88cbffe8a8, abstime=0x7f88cbffe7b0) at pthread_cond_wait.c:667 #3 0x7f896ef0cb17 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f896ef0d46a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f896ef0d552 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f896eecdfb1 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f896eed04c7 in base::internal::SchedulerWorker::RunWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f896eed0ab4 in base::internal::SchedulerWorker::RunPooledWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f896ef0f561 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8979e2b6db in start_thread (arg=0x7f88cbfff700) at pthread_create.c:463 #11 0x7f89846b688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f88f8ff9700 (LWP 27552)): #0 0x7f8979e319f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f88f8ff8908) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f88f8ff88b8, cond=0x7f88f8ff88e0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f88f8ff88e0, mutex=0x7f88f8ff88b8) at pthread_cond_wait.c:655 #3 0x7f896ef0ca49 in base::ConditionVariable::Wait() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f896ef0d478 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f896ef0d50f in base::WaitableEvent::Wait() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f896eecdfc8 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f896eed07f6 in base::internal::SchedulerWorker::RunWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f896eed0b34 in base::internal::SchedulerWorker::RunDedicatedWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f896ef0f561 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8979e2b6db in start_thread (arg=0x7f88f8ff9700) at pthread_create.c:463 #11 0x7f89846b688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f88f97fa700 (LWP 27549)): #0 __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7f89846c7474 in ___fprintf_chk (fp=0x7f89849828b0 <_IO_stdfile_2_lock>, flag=1, format=0x7f89645d06a8 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7f89645b89ad in event_logv_ () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7f89645b8b44 in event_warn () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7f89645ba46c in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7f89645b0114 in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7f896ef12db4 in
[Akonadi] [Bug 409666] New: e-Mail archive doesn't if KMail2 (Kontact) isn't running
https://bugs.kde.org/show_bug.cgi?id=409666 Bug ID: 409666 Summary: e-Mail archive doesn't if KMail2 (Kontact) isn't running Product: Akonadi Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Archive Mail Agent Assignee: kdepim-bugs@kde.org Reporter: bugrprt21...@online.de Target Milestone: --- SUMMARY After logging in the the KDE Plasma session, if Akonadi begins to automatically archive e-Mails before the KMail2 client is started, in my case by means of Kontact and, I also didn't start Kontact, then, the automatic e-Mail archive fails with "Can't open Mail Folder". Manually triggering the planned e-Mail Archive via KMail2 results in the planned Archive being successfully executed. STEPS TO REPRODUCE 1. Login to a KDE Plasma session where Akonadi is automatically started. 2. Don't start Kontact. 3. Wait. OBSERVED RESULT The automatic, planned, e-Mail Archive errors and, the bzip2 Archive file contains only a few bytes of rubbish. The expected Archive size is several hundred MBytes. EXPECTED RESULT The planned automatic e-Mail Archive should be executed by Akonadi without having to rely on the KDE Plasma session user starting either the KMail2 or Kontact application. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap 15.1 KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 ADDITIONAL INFORMATION An unexpected, from an archiving view, more than fatal, Akonadi behaviour. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 383885] CLI start: 0xca83b8 deleted without having been removed from the factory first.
https://bugs.kde.org/show_bug.cgi?id=383885 Don Curtis changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #5 from Don Curtis --- No longer an issue, therefore closed. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 383885] CLI start: 0xca83b8 deleted without having been removed from the factory first.
https://bugs.kde.org/show_bug.cgi?id=383885 Don Curtis changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Don Curtis --- Two year on, no longer an issue. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 409656] Unable to get feeds
https://bugs.kde.org/show_bug.cgi?id=409656 --- Comment #3 from Christophe Giboudeaux --- and to check the output, install and run kdebugsettings, in the search field, type "kio" then click on the "enable all debug" button, do the same thing after replacing "kio" with "akregator" then "syndication". To get the application output, run 'akregator' from a terminal -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 409656] Unable to get feeds
https://bugs.kde.org/show_bug.cgi?id=409656 --- Comment #2 from Christophe Giboudeaux --- If this affects any feeds, can you tell if you're using a proxy server and if you enabled the ad blocker plugin in akregator? -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 409656] Unable to get feeds
https://bugs.kde.org/show_bug.cgi?id=409656 --- Comment #1 from Christophe Giboudeaux --- > Could not fetch feed. Could not read feed (invalid XML) which URL? -- You are receiving this mail because: You are the assignee for the bug.
