[akregator] [Bug 379496] New: akregator crashes on startup
https://bugs.kde.org/show_bug.cgi?id=379496 Bug ID: 379496 Summary: akregator crashes on startup Product: akregator Version: 5.4.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: pguec...@gmail.com Target Milestone: --- Application: akregator (5.4.3) Qt Version: 5.7.1 Frameworks Version: 5.33.0 Operating System: Linux 4.11.0-1.fc26.x86_64 x86_64 Distribution: "Fedora release 26 (Twenty Six)" -- Information about the crash: - What I was doing when the application crashed: I clicked the icon in the launcher and the application crashed. This has been going on for about a week, likely since plasma 5.9.5-2 on fedora 26 alpha was in the repo. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f04fc5ba600 (LWP 2164))] Thread 19 (Thread 0x7f047a526700 (LWP 2196)): #0 0x7f05156737db in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0509c66534 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7f0509c66579 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7f051566d36d in start_thread () from /lib64/libpthread.so.0 #4 0x7f051ee86e0f in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7f04a57fa700 (LWP 2191)): #0 0x7f051ee7641d in read () from /lib64/libc.so.6 #1 0x7f050eb0e1e0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f050eaca038 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f050eaca4d0 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f050eaca63c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f051fc96d0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f051fc46b8a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f051fa9befa in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f051faa01ee in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f051566d36d in start_thread () from /lib64/libpthread.so.0 #10 0x7f051ee86e0f in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7f04a6ffd700 (LWP 2188)): #0 0x7f05156737db in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0518a82bb5 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f0518a83009 in base::SequencedWorkerPool::Worker::Run() () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f0518a831b1 in base::SimpleThread::ThreadMain() () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f0518a7fdeb in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f051566d36d in start_thread () from /lib64/libpthread.so.0 #6 0x7f051ee86e0f in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f04a77fe700 (LWP 2187)): #0 0x7f051ee7641d in read () from /lib64/libc.so.6 #1 0x7f05023f40b1 in pa_read () from /usr/lib64/pulseaudio/libpulsecommon-10.0.so #2 0x7f050dd8111e in pa_mainloop_prepare () from /lib64/libpulse.so.0 #3 0x7f050dd81b90 in pa_mainloop_iterate () from /lib64/libpulse.so.0 #4 0x7f050dd81c50 in pa_mainloop_run () from /lib64/libpulse.so.0 #5 0x7f050dd8fab9 in thread () from /lib64/libpulse.so.0 #6 0x7f0502423078 in internal_thread_func () from /usr/lib64/pulseaudio/libpulsecommon-10.0.so #7 0x7f051566d36d in start_thread () from /lib64/libpthread.so.0 #8 0x7f051ee86e0f in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f04a7fff700 (LWP 2186)): #0 0x7f0515673cda in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0518a78be2 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f0518a79412 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f0518a5b00b in base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f0518a6d908 in base::RunLoop::Run() () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f0518a834b5 in base::Thread::Run(base::MessageLoop*) () from /lib64/libQt5WebEngineCore.so.5 #6 0x7f0518a83774 in base::Thread::ThreadMain() () from /lib64/libQt5WebEngineCore.so.5 #7 0x7f0518a7fdeb in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #8 0x7f051566d36d in start_thread () from /lib64/libpthread.so.0 #9 0x7f051ee86e0f in clone () from /lib64/libc.so.6 Thread 14 (Thread
[Akonadi] [Bug 379401] Can't add GMail account
https://bugs.kde.org/show_bug.cgi?id=379401 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 379300 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 379300] Gmail IMAP token/code not saved
https://bugs.kde.org/show_bug.cgi?id=379300 Christoph Feck changed: What|Removed |Added CC||isalgue...@gmail.com --- Comment #6 from Christoph Feck --- *** Bug 379401 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 379320] Akonadi asks GMail for permission to manage account, but has nowhere to paste the code
https://bugs.kde.org/show_bug.cgi?id=379320 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 379300 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 379300] Gmail IMAP token/code not saved
https://bugs.kde.org/show_bug.cgi?id=379300 --- Comment #5 from Christoph Feck --- *** Bug 379320 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #193 from gra...@howlingfrog.com --- Agreed! Exciting to see progress, as KMail is close to unusable at this point. MUCH appreciated! -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #192 from Frits Spieker --- Excellent! Good to know there is some progress. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #191 from Martin Koller --- I am currently looking into this and have already implemented some patches which hopefully improve the situation (although I have no final fix yet). E.g. https://phabricator.kde.org/D5667 It's very complicated and has to do with timing of messages between 3 processes ... -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #190 from Frits Spieker --- But is one of the developers actually looking at this? The duplication of the messages, combined with the akonadi hanging itself out to dry when deleting messages (resulting in the famous "retrieving folder content" screen) makes KMail basically unusable. I'm really baffled how such a crucial piece of software (unless developers use other program to read email) can be so broken for so long. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 379476] Renaming attachments should also change their Content-Disposition/filename attribute
https://bugs.kde.org/show_bug.cgi?id=379476 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org --- Comment #1 from Laurent Montel --- It's already fixed in 5.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 379479] New: Frequent crashes with kmail in Ubuntu 17.04 (updated kmail)
https://bugs.kde.org/show_bug.cgi?id=379479 Bug ID: 379479 Summary: Frequent crashes with kmail in Ubuntu 17.04 (updated kmail) Product: kmail2 Version: 5.4.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: and...@bolager.com Target Milestone: --- Application: kmail (5.4.3) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-20-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: Almost always when selecting a message to view, the program crash. At the longest, I managed to work in it (watching messages, even sending one) for about 20 minutes or so. Usually, it crash right after startup. 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 0x7f093d633b80 (LWP 3388))] Thread 27 (Thread 0x7f086b9c1700 (LWP 3452)): #0 0x7f09301f4510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f09208582c4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f0920858309 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f09301ee6da in start_thread (arg=0x7f086b9c1700) at pthread_create.c:456 #4 0x7f093a5b217f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 26 (Thread 0x7f08719c0700 (LWP 3440)): #0 0x7f093a5a618d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f092e421576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f092e42168c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f093b0e0f2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f093b08a88a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f093aeb7fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f093aebcc98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f09301ee6da in start_thread (arg=0x7f08719c0700) at pthread_create.c:456 #8 0x7f093a5b217f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 25 (Thread 0x7f0896ffd700 (LWP 3420)): #0 0x7f09301f4510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f0925b1dc09 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f0925b1e209 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f0925b1e3c0 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0925b1ad5c in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f09301ee6da in start_thread (arg=0x7f0896ffd700) at pthread_create.c:456 #6 0x7f093a5b217f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 24 (Thread 0x7f08977fe700 (LWP 3419)): #0 0x7f093a5a1cad in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0912b7c611 in pa_read () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #2 0x7f091bdec21e in pa_mainloop_prepare () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f091bdecc90 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f091bdecd50 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f091bdfad39 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f0912bab7d8 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #7 0x7f09301ee6da in start_thread (arg=0x7f08977fe700) at pthread_create.c:456 #8 0x7f093a5b217f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 23 (Thread 0x7f0897fff700 (LWP 3418)): #0 0x7f093a5c013c in __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7f093a5c1d44 in ___fprintf_chk (fp=0x7f093a86d750 <_IO_stdfile_2_lock>, flag=1, format=0x7f0918b737b4 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7f0918b5b51e in () at /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #3 0x7f0918b5b714 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #4 0x7f0918b5fd38 in () at /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #5 0x7f0918b49efa in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #6 0x7f0925ac92aa in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0925b05a84 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f0925aef9d5 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f0925b1e9ea in () at /usr/lib/x86_64-linux-gnu/libQt5Web
[kmail2] [Bug 379476] New: Renaming attachments should also change their Content-Disposition/filename attribute
https://bugs.kde.org/show_bug.cgi?id=379476 Bug ID: 379476 Summary: Renaming attachments should also change their Content-Disposition/filename attribute Product: kmail2 Version: 5.4.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: kdeb...@customcdrom.de Target Milestone: --- 1) Attach a file to a message. 2) Right-click the attachment, choose Properties and change the attachment's name. Result: The "Content-Type" "name" attribute is changed, as follows: Content-Type: application/pdf; name="new_name.pdf" The "Content-Disposition" "filename" attribute stays unchanged, though: Content-Disposition: attachment; filename="orig_name.pdf" Somewhat counter-intuitive, this will in most cases cause the attachment to be called "orig_name.pdf" on the receiver's side, not "new_name.pdf" as one might expect when using the properties dialog. By default, the name and filename attributes are set to the same values by kMail, as far as I can see. Either the "name" field should change both values, or there should be a separate "File Name" property. Maybe interesting in this regard: https://mailarchive.ietf.org/arch/msg/ietf-smtp/KtN0TdoHDayKvKycNbsFD-GB-e4# Wishlist item Bug #311179 may be related. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 332167] KMail is failing to encrypt PGP/Inline for non-signed key
https://bugs.kde.org/show_bug.cgi?id=332167 --- Comment #9 from kolAflash --- Still not working on openSUSE 42.2 with GnuPG-2.0.24 and KMail-16.08.2. http://download.opensuse.org/source/distribution/leap/42.2/repo/oss/suse/src/gpg2-2.0.24-5.5.src.rpm http://download.opensuse.org/update/leap/42.2/oss/src/kdepim-16.08.2-2.2.1.src.rpm -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 379467] Display "Date:" header in sender's local timezone
https://bugs.kde.org/show_bug.cgi?id=379467 Juri Vitali changed: What|Removed |Added CC||j...@dbzero.it -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 379467] New: Display "Date:" header in sender's local timezone
https://bugs.kde.org/show_bug.cgi?id=379467 Bug ID: 379467 Summary: Display "Date:" header in sender's local timezone Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: j...@dbzero.it Target Milestone: --- In the message view the "Date:" header is always shown in user's local timezone, with no reference to sender's original one, so the only possible way to find out the original time is to manually inspect the raw message, and look at the Date: header. It would be useful to give the user the choice to choose whether to display the message date in his own or in the sender's timezone, maybe keeping the local timezone in the message list and the original one in the headers view, so to facilitate the message sorting while avoiding the need to manually inspect the message. Example (my timezone is UTC+2): (header)Date: Thu, 27 Apr 2017 14:19:49 -0400 (message view) 27/04/17 20:19 (message list) giovedì 20:19 -- You are receiving this mail because: You are the assignee for the bug.
