[akregator] [Bug 408869] New: Akregator krash at starup on remote X session
https://bugs.kde.org/show_bug.cgi?id=408869 Bug ID: 408869 Summary: Akregator krash at starup on remote X session Product: akregator 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: k...@itr.no Target Milestone: --- Application: akregator (5.11.2) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.18.0-21-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Trying to start Akregator over ssh -X session running akregator results in crash trying kstart and dbus-launch same result deleteting all akregtor related setups / caches / db etc , same result The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f588e8e7bc0 (LWP 31988))] Thread 22 (Thread 0x7f575ed7b700 (LWP 32041)): #0 0x7f587df38ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f575ed7a710, expected=0, futex_word=0x7f575ed7a8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f587df38ed9 in __pthread_cond_wait_common (abstime=0x7f575ed7a7b0, mutex=0x7f575ed7a8a8, cond=0x7f575ed7a8d0) at pthread_cond_wait.c:533 #2 0x7f587df38ed9 in __pthread_cond_timedwait (cond=0x7f575ed7a8d0, mutex=0x7f575ed7a8a8, abstime=0x7f575ed7a7b0) at pthread_cond_wait.c:667 #3 0x7f5884233b17 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f588423446a in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f5884234552 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f58841f4fb1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f58841f74c7 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f58841f7ab4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f5884236561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f587df326db in start_thread (arg=0x7f575ed7b700) at pthread_create.c:463 #11 0x7f588a68488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f575f7fe700 (LWP 32027)): #0 0x7f587df389f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f575f7fd908) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f587df389f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f575f7fd8b8, cond=0x7f575f7fd8e0) at pthread_cond_wait.c:502 #2 0x7f587df389f3 in __pthread_cond_wait (cond=0x7f575f7fd8e0, mutex=0x7f575f7fd8b8) at pthread_cond_wait.c:655 #3 0x7f5884233a49 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f5884234478 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f588423450f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f58841f4fc8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f58841f77f6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f58841f7b34 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f5884236561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f587df326db in start_thread (arg=0x7f575f7fe700) at pthread_create.c:463 #11 0x7f588a68488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f575700 (LWP 32026)): #0 0x7f588a6936ac in __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7f588a695474 in ___fprintf_chk (fp=0x7f588a9508b0 <_IO_stdfile_2_lock>, flag=1, format=0x7f58765756a8 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7f587655d9ad in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7f587655db44 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7f587655f46c in () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7f5876555114 in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7f5884239c79 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f58841d42db in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f5884206311 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f5884236561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f587df326db in start_thread (arg=0x7f575700) at pthread_create.c:463 #11 0x7f588a68488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f57f8a31700 (LWP 32025)): #0 0x7f587df38ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f57f8a30710, expected=0, futex_word=0x7f57f8a308f8) a
[kmail2] [Bug 399815] Unable to disssable delete confirmation
https://bugs.kde.org/show_bug.cgi?id=399815 Kim Lilliestierna changed: What|Removed |Added Summary|Unable to disssable delte |Unable to disssable delete |confirmation|confirmation -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 399815] New: Unable to disssable delte confirmation
https://bugs.kde.org/show_bug.cgi?id=399815 Bug ID: 399815 Summary: Unable to disssable delte confirmation Product: kmail2 Version: 5.9.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: k...@itr.no Target Milestone: --- SUMMARY No option for disabling delete message confirmation popup the "Delete Item" command previously silently deleted a message without annoying "Are you sure..." poppups, this is no longer the case and there seems to be no options in setting to turn off this irritating behaviour. STEPS TO REPRODUCE 1. Add "Delete Item" to menu 2. Press the above "Delete Item" or press 3. The confirmation pop up appears. OBSERVED RESULT The confirmation pop up appears. EXPECTED RESULT The message should silently be deleted. SOFTWARE VERSIONS Kmail version 5.9.1 Neon: KDE neon 5.13 KDE Plasma: 5.13.5 KDE Framevork 5.50.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 394886] New: "Pipe Through" not piping
https://bugs.kde.org/show_bug.cgi?id=394886 Bug ID: 394886 Summary: "Pipe Through" not piping Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: k...@itr.no Target Milestone: --- The "Pipe Through" filter action does not pipe the email to the external program, not even on manual filtering. It is ofc intermittent and hard to reproduce reliably. I have the following script for running crm114 #!/bin/bash TIME=$(date +"%d/%m/%Y %H:%M:%S") LOG=~/logs/crmlog mkdir ~/logs &>/dev/null touch $LOG echo $TIME >>$LOG cp /dev/null ~/logs/copy exec crm -u $HOME/.crm114 mailreaver.crm | tee ~/logs/copy 2>> $LOG This will enter a time stamp in the log file and copy any data from the pipe into the "copy" file. When Kmail starts failing the filtering, the logs shows that the action was run, but the "copy" file only contains the crm114 header message indicating that the pipe was empty. there seems to be 3 workarounds none that work reliably all the time.. 1. remake the filter rule, its enough to edit the rule and resave. 2. stop and start akonadi, making sure the filter agent is restarted. 3. log out from the kde session or reboot One would think that rebooting would fix it, but have had cases where the filtering fails on a fresh reboot / login first time kmail session, where resaving the rule fixed it... -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 389675] Filters work only when a message arrives
https://bugs.kde.org/show_bug.cgi?id=389675 Kim Lilliestierna changed: What|Removed |Added CC||k...@itr.no --- Comment #1 from Kim Lilliestierna --- Same behaviour here, my spam filter action is a shellscript runing crm114, adding some logging to it shows that the filter is run, the mail is marked, but kmail is not reading back the output of the filter. same for both imap and pop. distro: ubuntu 17.10 Kmail: 5.5.3 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 386348] XML format not recognized
https://bugs.kde.org/show_bug.cgi?id=386348 --- Comment #2 from Kim Lilliestierna --- Created attachment 108654 --> https://bugs.kde.org/attachment.cgi?id=108654&action=edit dent xml rss aquired by curl http://www.webtoons.com/en/sf/dents/rss?title_no=671 > dents -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 386348] New: XML format not recognized
https://bugs.kde.org/show_bug.cgi?id=386348 Bug ID: 386348 Summary: XML format not recognized Product: akregator Version: 5.4.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: feed parser Assignee: kdepim-bugs@kde.org Reporter: k...@itr.no Target Milestone: --- The rss feed from webtoons,com does not seem to be recognized as valid url: http://www.webtoons.com/en/sf/dents/rss?title_no=671 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 381816] New: Crash on closing tab in feed reader
https://bugs.kde.org/show_bug.cgi?id=381816 Bug ID: 381816 Summary: Crash on closing tab in feed reader Product: kontact Version: 5.2.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: k...@itr.no Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.6.1 Frameworks Version: 5.34.0 Operating System: Linux 4.4.0-78-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: Closed a tab in feed ( Akregator). Hapens with increasing frequency. not allways on the same feed, clearing out the corupted cash file sometimes helps for some time. The crash can be reproduced sometimes. -- 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 0x7fd84bd2a940 (LWP 25556))] Thread 30 (Thread 0x7fd7737fe700 (LWP 26258)): #0 0x7fd86207db5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd85b7e938c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd85b7e949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd862bbb37b in QEventDispatcherGlib::processEvents (this=0x7fd7640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7fd862b63ffa in QEventLoop::exec (this=this@entry=0x7fd7737fdc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fd86298c9e4 in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7fd862991808 in QThreadPrivate::start (arg=0x4b4fe80) at thread/qthread_unix.cpp:341 #7 0x7fd85c0136ba in start_thread (arg=0x7fd7737fe700) at pthread_create.c:333 #8 0x7fd86208982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 29 (Thread 0x7fd773fff700 (LWP 26256)): #0 0x7fd864d24ab8 in update_get_addr (ti=0x7fd862daf748) at dl-tls.c:805 #1 0x7fd862990706 in get_thread_data () at thread/qthread_unix.cpp:184 #2 QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at thread/qthread_unix.cpp:215 #3 0x7fd862bba9da in postEventSourcePrepare (s=0x7fd76c0012d0, timeout=0x7fd773ffeab4) at kernel/qeventdispatcher_glib.cpp:246 #4 0x7fd85b7e891d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fd85b7e92bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fd85b7e949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fd862bbb37b in QEventDispatcherGlib::processEvents (this=0x7fd76c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #8 0x7fd862b63ffa in QEventLoop::exec (this=this@entry=0x7fd773ffec80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #9 0x7fd86298c9e4 in QThread::exec (this=) at thread/qthread.cpp:500 #10 0x7fd862991808 in QThreadPrivate::start (arg=0x4968840) at thread/qthread_unix.cpp:341 #11 0x7fd85c0136ba in start_thread (arg=0x7fd773fff700) at pthread_create.c:333 #12 0x7fd86208982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 28 (Thread 0x7fd780fe4700 (LWP 26254)): #0 0x7fd86207db5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd85b7e938c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd85b7e949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd862bbb37b in QEventDispatcherGlib::processEvents (this=0x7fd7780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7fd862b63ffa in QEventLoop::exec (this=this@entry=0x7fd780fe3c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fd86298c9e4 in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7fd862991808 in QThreadPrivate::start (arg=0x49b5930) at thread/qthread_unix.cpp:341 #7 0x7fd85c0136ba in start_thread (arg=0x7fd780fe4700) at pthread_create.c:333 #8 0x7fd86208982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 27 (Thread 0x7fd7834ed700 (LWP 25786)): #0 0x7fd86207db5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd85b7e938c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd85b7e949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd862bbb37b in QEventDispatcherGlib::processEvents (this=0x7fd7740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7fd862b63ffa in QEventLoop::exec (this=this@entry=0x7fd7834ecc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fd86298c9e4 in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7fd862991808 in QThreadPrivate::start (arg=0x45e7390) at thread/qthread_unix.cpp:341 #7 0x7fd85c0136ba in start_thread (arg=0x7fd7834ed700) at pth
[kontact] [Bug 380387] New: Crash on marking feed read
https://bugs.kde.org/show_bug.cgi?id=380387 Bug ID: 380387 Summary: Crash on marking feed read Product: kontact Version: 5.2.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: k...@itr.no Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.6.1 Frameworks Version: 5.33.0 Operating System: Linux 4.4.0-78-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: Crashes semi consitently when wrying to mark a feed read. Usually ends up with several cash entries corrupted. Not allways the same feed. The crash can be reproduced sometimes. -- 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 0x7fc7c57d5940 (LWP 28431))] Thread 40 (Thread 0x7fc6a8bfc700 (LWP 31581)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fc6fa3a5cbc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa06674d in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6a8bfc700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 39 (Thread 0x7fc6a93fd700 (LWP 31580)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fc6fa3a5cbc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa06674d in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6a93fd700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 38 (Thread 0x7fc6aa20a700 (LWP 31579)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fc6fa3a5cbc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa06674d in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6aa20a700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 37 (Thread 0x7fc6aaa0b700 (LWP 31578)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fc6fa3a5cbc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa06674d in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6aaa0b700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 36 (Thread 0x7fc6ab4fe700 (LWP 31573)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc6fa3a5cfc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa15e93c in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6ab4fe700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 35 (Thread 0x7fc6abcff700 (LWP 31572)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc6fa3a5cfc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa15e93c in ?? () from /usr/lib/adobe-flashplug
[akregator] [Bug 374250] New: Article list empty
https://bugs.kde.org/show_bug.cgi?id=374250 Bug ID: 374250 Summary: Article list empty Product: akregator Version: 5.2.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: k...@itr.no Target Milestone: --- No articles are shown in the article list, even though the feed lists as having several, this is true for all feeds. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 --- Comment #38 from Kim Lilliestierna --- This has been resolved in the latest kmail version (5.1.3) and kde framework (5.18.0) -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056
--- Comment #13 from Kim Lilliestierna ---
Created attachment 95789
--> https://bugs.kde.org/attachment.cgi?id=95789&action=edit
Log of imap delete on Courier and Dovecot
The tar file contains separate sets of log files from two different delete
cases, one for a courier server , and the other for a dovecot server. the
settup was from a freshly added user, with a virgin Kmail config. System:
Kubuntu 15.10 (Wily) and Kmail 5.0.2 , Kde Frameworks 5.10.0, QT 5.4.2.
New email accounts on both servers, one mail in inbox, nothing else. Imap
accounts identically configured, ie, only change was on "General" tab for
server and login and on "Advanced" tab to enable tls ("Auto test")
Observe that the capability report from each are different:
Courier:
OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT
THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready.
Copyright 1998-2011 Double Precision, Inc. See COPYING for distribution
information
Dovecot:
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE
STARTTLS LOGINDISABLED] Cyclops ready
And that the way the akonadi imap client goes about deleting mail is also quite
different. but the greatest difference are the lack of EXPUNGE commands in the
Courier case:
Courier delete:
C: A16 UID FETCH 1 (BODY.PEEK[] UID)
S: * 1 FETCH ( BODY[] Return-Path:
... Mail content deleted for brevity
UID 1 )
S: A16 OK FETCH completed.
C: A17 UID STORE 1 +FLAGS (\Seen)
S: * 1 FETCH ( UID 1 FLAGS (\Seen) )
S: A17 OK STORE completed.
C: A18 UID STORE 1 +FLAGS (\Deleted)
S: * 1 FETCH ( UID 1 FLAGS (\Seen \Deleted) )
S: A18 OK STORE completed.
C: A19 SELECT "INBOX.Trash"
S: * FLAGS ( \Draft \Answered \Flagged \Deleted \Seen \Recent )
Dovecot
C: A05 UID FETCH 1 (BODY.PEEK[] UID)
S: * 1 FETCH ( UID 1 BODY[]
... mail content deleted for brevity
)
S: A05 OK Fetch completed.
C: A06 UID STORE 1 +FLAGS (\Seen)
S: * 1 FETCH ( UID 1 FLAGS (\Seen) )
S: A06 OK Store completed.
C: A07 EXPUNGE
S: A07 OK Expunge completed.
C: A08 SELECT "INBOX" (CONDSTORE)
S: * OK Previous mailbox closed. [ CLOSED ]
S: * FLAGS ( \Answered \Flagged \Deleted \Seen \Draft )
S: * OK Flags permitted. [ PERMANENTFLAGS ( \Answered \Flagged \Deleted \Seen
\Draft \* ) ]
S: * 1 EXISTS
S: * 0 RECENT
S: * OK UIDs valid [ UIDVALIDITY 1448727510 ]
S: * OK Predicted next UID [ UIDNEXT 2 ]
S: * OK Highest [ HIGHESTMODSEQ 3 ]
S: A08 OK Select completed ( 0.000 secs ) . [ READ-WRITE ]
C: A09 UID FETCH 1:2 (FLAGS UID) (CHANGEDSINCE 2)
S: * 1 FETCH ( UID 1 FLAGS (\Seen) MODSEQ (3) )
S: A09 OK Fetch completed.
C: A10 UID STORE 1 +FLAGS (\Deleted)
S: * 1 FETCH ( UID 1 MODSEQ (4) FLAGS (\Deleted \Seen) )
S: A10 OK Store completed.
C: A11 EXPUNGE
S: * 1 EXPUNGE
S: A11 OK Expunge completed.
C: A12 SELECT "INBOX" (CONDSTORE)
--
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 --- Comment #31 from Kim Lilliestierna --- Mucked around a bit with this, I have access to 2 different imap servers on is a Dovecot the other A Courier, it works ok on the Dovecot not on the Courier, After enabling debugging on the akonadi IMAP resource i see one very important difference: on the Dovecot case the EXPUNGE command is sent regularly, on the Courier it does not. This explains the behavior: Deleting a message in IMAP only marks it as \DELETED but it still exists and Kmail vill act upon it as if it where a regular message, to really get rid of the message a EXPUNGE command need to be sent to the IMAP server for the folder in question. Moving a file entails first copying it and then deleting the original. And since the original only gets marked and Kmail is a bit stupid there, any auto scripts that you might be running goes nuts with the moving. I asume that the above 1/2 solution with an alternate mail client works since they probably send of the EXPUNGE and cleans out the crap :) So why the different behavior on different servers?, im guessing some (not) so smart decision is being made based on the servers capability report. So, either add a "force EXPUNGE" command/button/menu entry/whatever and have Kmail ignore mails with the \DELETED flag set, at the least when scripts are running. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 Kim Lilliestierna changed: What|Removed |Added CC||k...@itr.no --- Comment #8 from Kim Lilliestierna --- I can confirm the same on kubuntu Willy (15.10) kmai 5.0.2, Moving or deleting a mail in a IMAP folder marks the original as deleted and creates a copy in the destination folder, but the source folder does not seem to be "expunged". this a real problem, it is no longer possible to run any filters, since moved mails are no longer beeing purged from original folder, resulting in the orignal folder growing, and the destination folder getting dublicates. Specially bad on accounts that get a large amount of spam. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 Kim Lilliestierna changed: What|Removed |Added CC||k...@itr.no --- Comment #27 from Kim Lilliestierna --- Bug confirmed on Kubuntu 15.10 as well, would humbly appreciate a patch for this rather sooner than later, spam filtering is currently a paradox, since it is constantly doubling the spam int the "Spam" folder :), so for now have to turn of automatic filtering -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 299490] New: Akregator crashin consistently after extened period idle
https://bugs.kde.org/show_bug.cgi?id=299490 Bug ID: 299490 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Akregator crashin consistently after extened period idle Classification: Unclassified OS: Linux Reporter: k...@itr.no Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: akregator Application: akregator (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.0.0-17-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: Nothing, machine left idel over night, found akregator crashed in the morning. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [Current thread is 1 (Thread 0xb7739730 (LWP 5175))] Thread 7 (Thread 0xaf222b70 (LWP 5188)): #0 0x00ef6d10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x04ad03a5 in do_gettime (frac=0xaf221f30, sec=0xaf221f28) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x04bba3d6 in QTimerInfoList::updateCurrentTime (this=0xbbb8e84) at kernel/qeventdispatcher_unix.cpp:343 #4 0x04bba72a in QTimerInfoList::timerWait (this=0xbbb8e84, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0x04bb8f43 in timerSourcePrepareHelper (src=, timeout=0xaf22203c) at kernel/qeventdispatcher_glib.cpp:136 #6 0x04bb8fdd in timerSourcePrepare (source=0xbbb8e50, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #7 0x03d6988c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x03d6a637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x03d6ac2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0x04bb9a97 in QEventDispatcherGlib::processEvents (this=0xa7211f8, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #11 0x04b855ed in QEventLoop::processEvents (this=0xaf2221d0, flags=...) at kernel/qeventloop.cpp:149 #12 0x04b85889 in QEventLoop::exec (this=0xaf2221d0, flags=...) at kernel/qeventloop.cpp:204 #13 0x04a6e9dc in QThread::exec (this=0xacd09f0) at thread/qthread.cpp:501 #14 0x04b62b5d in QInotifyFileSystemWatcherEngine::run (this=0xacd09f0) at io/qfilesystemwatcher_inotify.cpp:248 #15 0x04a71e70 in QThreadPrivate::start (arg=0xacd09f0) at thread/qthread_unix.cpp:298 #16 0x03ea49cd in ?? () from /usr/lib/nvidia-current/libGL.so.1 #17 0x00dc046e in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 6 (Thread 0xb10f7b70 (LWP 28983)): #0 0x002ed416 in __kernel_vsyscall () #1 0x01ea1a5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x00dce09c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb4892883 in WTF::TCMalloc_PageHeap::scavengerThread (this=0xb4fae340) at wtf/FastMalloc.cpp:2495 #4 0xb489299f in WTF::TCMalloc_PageHeap::runScavengerThread (context=0xb4fae340) at wtf/FastMalloc.cpp:1618 #5 0x03ea49cd in ?? () from /usr/lib/nvidia-current/libGL.so.1 #6 0x00dc046e in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 5 (Thread 0xaea21b70 (LWP 29040)): #0 0x00ef6d10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x04ad03a5 in do_gettime (frac=0xaea20fc0, sec=0xaea20fb8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x04bba3d6 in QTimerInfoList::updateCurrentTime (this=0xb1100afc) at kernel/qeventdispatcher_unix.cpp:343 #4 0x04bb9fc6 in timerSourceCheckHelper (src=0xb1100ac8) at kernel/qeventdispatcher_glib.cpp:150 #5 timerSourceCheckHelper (src=0xb1100ac8) at kernel/qeventdispatcher_glib.cpp:144 #6 0x03d69f24 in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x03d6a8f0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x03d6ac2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x04bb9a97 in QEventDispatcherGlib::processEvents (this=0x9c31330, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0x04b855ed in QEventLoop::processEvents (this=0xaea21200, flags=...) at kernel/qeventloop.cpp:149 #11 0x04b85889 in QEventLoop::exec (this=0xaea21200, flags=...) at kernel/qeventloop.cpp:204 #12 0x04a6e9dc in QThread::exec (this=0xbd29df8) at thread/qthread.cpp:501 #13 0x04a6eacb in QThread::run (this=0xbd29df8) at thread/qthread.cpp:568 #14 0x04a71e70 in QThreadPrivate::start (arg=0xbd29df8) at thread/qthread_unix.cpp:298 #15 0x03ea49cd in ?? () from /usr/lib/nvidia-current/libGL.so.1 #16 0x00dc046e in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 4 (Thread 0xaddb7b70 (LWP 29926)): #0 0x002ed416 in __kernel_vsyscall () #1 0x01e
[Bug 295009] New: akregator crashing after time
https://bugs.kde.org/show_bug.cgi?id=295009 Summary: akregator crashing after time Product: akregator Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: k...@itr.no Application: akregator (4.8.0) KDE Platform Version: 4.8.00 (4.8.0 Qt Version: 4.7.4 Operating System: Linux 3.0.0-15-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: Akregator will crash daily if left running over night for example The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [Current thread is 1 (Thread 0xb7716730 (LWP 24822))] Thread 7 (Thread 0xb0c77b70 (LWP 25849)): #0 0x005d4d10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x002e77d5 in do_gettime (frac=0xb0c76f50, sec=0xb0c76f48) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x003ba4b6 in QTimerInfoList::updateCurrentTime (this=0x995cab4) at kernel/qeventdispatcher_unix.cpp:339 #4 0x003ba80a in QTimerInfoList::timerWait (this=0x995cab4, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0x003b9053 in timerSourcePrepareHelper (src=, timeout=0xb0c7705c) at kernel/qeventdispatcher_glib.cpp:136 #6 0x003b90ed in timerSourcePrepare (source=0x995ca80, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #7 0x071ab88c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x071ac637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x071acc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0x003b9b37 in QEventDispatcherGlib::processEvents (this=0x9520a70, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0x0038a1dd in QEventLoop::processEvents (this=0xb0c771e0, flags=...) at kernel/qeventloop.cpp:149 #12 0x0038a421 in QEventLoop::exec (this=0xb0c771e0, flags=...) at kernel/qeventloop.cpp:201 #13 0x0028d90b in QThread::exec (this=0x973e508) at thread/qthread.cpp:498 #14 0x0036ae2d in QInotifyFileSystemWatcherEngine::run (this=0x973e508) at io/qfilesystemwatcher_inotify.cpp:248 #15 0x002907b3 in QThreadPrivate::start (arg=0x973e508) at thread/qthread_unix.cpp:331 #16 0x031049cd in ?? () from /usr/lib/nvidia-current/libGL.so.1 #17 0x04ba30ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 6 (Thread 0xafbe0b70 (LWP 28482)): #0 0x005d0416 in __kernel_vsyscall () #1 0x0078ca5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x04bb0cfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb56bc883 in WTF::TCMalloc_PageHeap::scavengerThread (this=0xb5dd8340) at wtf/FastMalloc.cpp:2495 #4 0xb56bc99f in WTF::TCMalloc_PageHeap::runScavengerThread (context=0xb5dd8340) at wtf/FastMalloc.cpp:1618 #5 0x031049cd in ?? () from /usr/lib/nvidia-current/libGL.so.1 #6 0x04ba30ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 5 (Thread 0xaf2dfb70 (LWP 28553)): #0 0x005d0416 in __kernel_vsyscall () #1 0x0078ca5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x04bb0cfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0x0028f5b3 in QMutexPrivate::wait (this=0x972c5b8, timeout=-1) at thread/qmutex_unix.cpp:84 #4 0x0028b7ea in QMutex::lock (this=0x966ff10) at thread/qmutex.cpp:204 #5 0x003a0813 in QMutexLocker (m=, this=0xaf2de498) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:102 #6 QMetaObject::activate (sender=0xa1b2b88, m=0x3d6a56c, local_signal_index=3, argv=0x0) at kernel/qobject.cpp:3217 #7 0x03cbe205 in QBearerEngine::updateCompleted (this=0xa1b2b88) at .moc/release-shared/moc_qbearerengine_p.cpp:114 #8 0x028bd1b2 in QGenericEngine::doRequestUpdate (this=0xa1b2b88) at qgenericengine.cpp:308 #9 0x028c0e0c in QGenericEngine::qt_metacall (this=0xa1b2b88, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0xaf2de6dc) at .moc/release-shared/moc_qgenericengine.cpp:79 #10 0x00391b7d in metacall (argv=0xaf2de6dc, idx=11, cl=QMetaObject::InvokeMetaMethod, object=0xa1b2b88) at kernel/qmetaobject.cpp:237 #11 QMetaObject::metacall (object=0xa1b2b88, cl=QMetaObject::InvokeMetaMethod, idx=11, argv=0xaf2de6dc) at kernel/qmetaobject.cpp:232 #12 0x00393670 in QMetaMethod::invoke (this=0xaf2de83c, object=0xa1b2b88, connectionType=Qt::DirectConnection, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1597 #13 0x00395b57 in QMetaObject::invokeMethod (obj=0xa1b2b88, member=0x3d2bb60 "requestUpdate", type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., v
