[kleopatra] [Bug 358666] New: Short dates are used everywhere in the UI
https://bugs.kde.org/show_bug.cgi?id=358666 Bug ID: 358666 Summary: Short dates are used everywhere in the UI Product: kleopatra Version: 2.2.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: kokotokos...@yopmail.fr CC: kdepim-bugs@kde.org, m...@kde.org The user interface uses the short date format (e.g., Thu 28 Jan), which is fairly useless if one is trying to ascertain, e.g., how long a certificate has been valid or when it will expire. Reproducible: Always Steps to Reproduce: 1. Ensure at least one certificate has been imported 2. Open the certificate manager 3. Look at any dates, such as "Valid From" / "Valid Until" in the main pane, but also under Certificate Details, and possibly other places. Actual Results: Short dates are used, without the year. Expected Results: I expect a full, unambiguous date. Either a full date according to locale (but that's ambiguous thanks to Americans being weird like that), or perhaps better, an ISO-8601 date, which is what my Enigmail does. -- 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
[akregator] [Bug 358663] New Feature: Enable interface to Owncloud News
https://bugs.kde.org/show_bug.cgi?id=358663 --- Comment #4 from Daniel Lausevic --- . -- 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
[akregator] [Bug 358663] New Feature: Enable interface to Owncloud News
https://bugs.kde.org/show_bug.cgi?id=358663 --- Comment #3 from Daniel Lausevic --- Didn't see an existing request even after a cursory search. Sorry. Closing this as it is a dupe. -- 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
[akregator] [Bug 358663] New Feature: Enable interface to Owncloud News
https://bugs.kde.org/show_bug.cgi?id=358663 --- Comment #2 from Daniel Lausevic --- Didn't see an existing request even after a cursory search. Sorry. Closing this as it is a dupe. -- 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
[akregator] [Bug 358663] New: New Feature: Enable interface to Owncloud News
https://bugs.kde.org/show_bug.cgi?id=358663 Bug ID: 358663 Summary: New Feature: Enable interface to Owncloud News Product: akregator Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: feed parser Assignee: kdepim-bugs@kde.org Reporter: calcman...@gmail.com Please add a function whereby an owncloud server can be added to Akregator such that feeds subscribed from the server will appear in akregator. Downloading and reading feeds should mark the feeds read on the server to enable a snyc with smartphone apps. For reference, Android has an app which serves this purpose called 'ownCloud News Reader.' Wishlist: 1. Add connectivity/sync to owncloud news 2. Disable hostname verification for those of us who operate with a self signed cert. 3. Allow for subscribing to new feeds within Akregator. 4. Allow folder creation/removal within Akregator. 5. Allow 'starring' -- 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
[akregator] [Bug 358663] New Feature: Enable interface to Owncloud News
https://bugs.kde.org/show_bug.cgi?id=358663 --- Comment #1 from Daniel Lausevic --- Thanks in advance -- 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 358658] .desktop files of agents are read in the incorrect encoding
https://bugs.kde.org/show_bug.cgi?id=358658 --- Comment #2 from Alexey Chernov <4er...@gmail.com> --- Here's a review request link: https://git.reviewboard.kde.org/r/126911/ -- 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 358658] New: .desktop files of agents are read in the incorrect encoding
https://bugs.kde.org/show_bug.cgi?id=358658 Bug ID: 358658 Summary: .desktop files of agents are read in the incorrect encoding Product: Akonadi Version: GIT (master) Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: 4er...@gmail.com It turned out that .desktop files which hold settings of Akonadi agents are read in the incorrect encoding which leads to broken strings in applications (e.g. KMail or Akonadiconsole) when using localized version of KDE (see the screenshots). There's a fix for that, so the review request link is about to be applied. Reproducible: Always Steps to Reproduce: 1. Set some non-English locale in System settings. 2. Start e.g. Akonadiconsole. 3. Notice type string of agent summary. 4. Click "Add" button and notice descriptions of agents are with broken symbols. -- 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 358658] .desktop files of agents are read in the incorrect encoding
https://bugs.kde.org/show_bug.cgi?id=358658 --- Comment #1 from Alexey Chernov <4er...@gmail.com> --- Created attachment 96876 --> https://bugs.kde.org/attachment.cgi?id=96876&action=edit Sample screenshot of the issue. -- 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
[kleopatra] [Bug 340227] Unable to trust self-signed root certificate
https://bugs.kde.org/show_bug.cgi?id=340227 Briet changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- 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
[kdepimlibs] [Bug 353326] Korganizer crashed when trying to add a new event.
https://bugs.kde.org/show_bug.cgi?id=353326 eric changed: What|Removed |Added CC||pro...@gmx.net --- Comment #4 from eric --- This still happens with korganizer and kaddresssbook, both version 15.12.1. KDE-5.18 Qt-5.5.1 After importing new *.vcf files: Korganizer crashes when trying to add a new event or after I click on the 'To-Do List' view; Kaddressbook crashes immediately after startup. -- 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
[kontact] [Bug 358650] New: about this error
https://bugs.kde.org/show_bug.cgi?id=358650 Bug ID: 358650 Summary: about this error Product: kontact Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: num...@gmail.com Application: kontact (4.14.2) KDE Platform Version: 4.14.2 (Compiled from sources) Qt Version: 4.8.6 Operating System: Linux 3.19.0-32-generic x86_64 Distribution: Linux Mint 17.3 Rosa -- Information about the crash: - What I was doing when the application crashed: I'm waiting to receive e-mails. I had changed somethings in preferences -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd1e0128800 (LWP 2417))] Thread 7 (Thread 0x7fd1c059d700 (LWP 2541)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd1daec981d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fd1daec9859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fd1d75ea182 in start_thread (arg=0x7fd1c059d700) at pthread_create.c:312 #4 0x7fd1dd69e47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 6 (Thread 0x7fd17fc9a700 (LWP 2565)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd1dac0a20d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fd1daef8fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fd1d75ea182 in start_thread (arg=0x7fd17fc9a700) at pthread_create.c:312 #4 0x7fd1dd69e47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7fd170577700 (LWP 2761)): #0 0x7ffe039abcb6 in ?? () #1 0x7fd1dde18eae in QTimerInfoList::repairTimersIfNeeded (this=0x1) at kernel/qeventdispatcher_unix.cpp:413 #2 0x7fff in ?? () #3 0x7fd170576c30 in ?? () #4 0x7fd1dd6ac92d in __GI___clock_gettime (clock_id=, tp=) at ../sysdeps/unix/clock_gettime.c:115 #5 0x7fd1ddd3cad7 in do_gettime (frac=0x7fd170576bc0, sec=0x7fd170576bb8) at tools/qelapsedtimer_unix.cpp:127 #6 qt_gettime () at tools/qelapsedtimer_unix.cpp:144 #7 0x7fd1dde18b79 in QTimerInfoList::updateCurrentTime (this=0x7fd168003130, this@entry=0x240eeac) at kernel/qeventdispatcher_unix.cpp:354 #8 0x7fd1dde17a4b in timerSourceCheckHelper (src=0x240ee4c) at kernel/qeventdispatcher_glib.cpp:157 #9 0x7fd1d710aa61 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7fd1d710af7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fd1d710b0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fd1dde177be in QEventDispatcherGlib::processEvents (this=0x7fd1680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #13 0x7fd1ddde90af in QEventLoop::processEvents (this=this@entry=0x7fd170576de0, flags=...) at kernel/qeventloop.cpp:149 #14 0x7fd1ddde93a5 in QEventLoop::exec (this=this@entry=0x7fd170576de0, flags=...) at kernel/qeventloop.cpp:204 #15 0x7fd1ddce5c5f in QThread::exec (this=) at thread/qthread.cpp:537 #16 0x7fd1ddce832f in QThreadPrivate::start (arg=0xef32d0) at thread/qthread_unix.cpp:349 #17 0x7fd1d75ea182 in start_thread (arg=0x7fd170577700) at pthread_create.c:312 #18 0x7fd1dd69e47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7fd167fff700 (LWP 2816)): #0 0x7fd1dd69112d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fd1d710afe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd1d710b0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd1dde177be in QEventDispatcherGlib::processEvents (this=0x7fd168c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x7fd1ddde90af in QEventLoop::processEvents (this=this@entry=0x7fd167ffeda0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fd1ddde93a5 in QEventLoop::exec (this=this@entry=0x7fd167ffeda0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fd1ddce5c5f in QThread::exec (this=this@entry=0x1b90260) at thread/qthread.cpp:537 #7 0x7fd1dddca823 in QInotifyFileSystemWatcherEngine::run (this=0x1b90260) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7fd1ddce832f in QThreadPrivate::start (arg=0x1b90260) at thread/qthread_unix.cpp:349 #9 0x7fd1d75ea182 in start_thread (arg=0x7fd167fff700) at pthread_create.c:312 #10 0x7fd1dd69e47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7fd15e68b700 (LWP 2906)): #0 0x7fd1d710a8a2 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd1
[kmail2] [Bug 358633] The editor of the composer changed, no alternative configurable
https://bugs.kde.org/show_bug.cgi?id=358633 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.2 Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kpim ||textedit/dd9eea040c336585bc ||7662aa35e539b425de8222 --- Comment #2 from Laurent Montel --- Git commit dd9eea040c336585bc7662aa35e539b425de8222 by Montel Laurent. Committed on 27/01/2016 at 12:58. Pushed by mlaurent into branch 'master'. Fix Bug 358633 - The editor of the composer changed, no alternative configurable FIXED-IN: 5.2 M +14 -2src/texteditor/plaintexteditor/plaintexteditor.cpp M +2-2src/texteditor/plaintexteditor/plaintexteditor.h M +15 -2src/texteditor/richtexteditor/richtexteditor.cpp M +2-2src/texteditor/richtexteditor/richtexteditor.h http://commits.kde.org/kpimtextedit/dd9eea040c336585bc7662aa35e539b425de8222 -- 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
[kmail2] [Bug 358633] The editor of the composer changed, no alternative configurable
https://bugs.kde.org/show_bug.cgi?id=358633 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- We never used katepart as component in composer. (it will never use it for sure). But I used ktextedit in kde4 and new composer in kf5 so perhaps "ctrl-k deletes the line" was not reimplemented. I will look at it. -- 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 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 --- Comment #49 from RapFan89 --- Following sparhawk's way, i've installed in a virtual box machine arch linux, with the latest kde packages, now i've set my caldav infos in korganizer and tried to add some events and then check them in an other caldav client (lightining) installed in my local machine . The results are quite strange: i can add an event and on the other side, lighiting seems to get it correctly. But if i tried to delete it from korganizer, the change does not affect lightining. Then if i a create a new event in lighting then korganizer doesn't get it at all. So with libical 2.0 a small improvement has been done. Is there a verbose mode into korganizer? i've tried to launch it from cli, but informations are really poor. -- 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
[kleopatra] [Bug 175980] --query and --external command line options missing
https://bugs.kde.org/show_bug.cgi?id=175980 --- Comment #10 from Andre Heinecke --- Git commit 0df8c74d5869612667e6f72b3de368fa8a77c9b4 by Andre Heinecke. Committed on 27/01/2016 at 10:58. Pushed by aheinecke into branch 'vendor/intevation/4.14'. Backport fixes for search external certificates Do not prefix query with 0x and show prefix info. This generalizes the lookupcertificatescommand again so that it can be used with a generic query. Prefixing 0x this low was wrong and is also not necessary at least with SKS Keyservers. Accordingly don't show the information text about how adding or leaving out the 0x prefix might change results. Only show it in case a search for a keyid or fingerprint does not return a result. (cherry picked from commit c2a6ef0c41598ef801a5b8a0438e59a7e2ae9b97) Conflicts: kleopatra/commands/lookupcertificatescommand.cpp Add --search command line option. This option runs the lookupcertificatescommand with the provided search string. This basically opens the external keysearch dialog. The option implements the KDE 3 behavior of kleopatras --query --external but I found it easier to understand if It is named like the GnuPG --search option and does not mix the "open certificate details / search on keyserver" options. Behavior of the --query option is not documented a bit more detailed in the help string. (cherry picked from commit fcf92035b9a44f51d89e02268f1fdbc3e4c2ca3a) Conflicts: kleopatra/kleopatra_options.h kleopatra/kleopatraapplication.cpp Make "Search for External Certificates" work again This uses the newly added search option to open kleopatra's Keyserver search dialog instead of just opening Kleopatra. (cherry picked from commit d591b2bbfa132632901870dedf00994009a37666) Conflicts: libkleo/src/ui/keyselectiondialog.cpp M +43 -34 kleopatra/commands/lookupcertificatescommand.cpp M +30 -14 kleopatra/kleopatraapplication.cpp M +1-6libkleo/ui/keyselectiondialog.cpp http://commits.kde.org/kdepim/0df8c74d5869612667e6f72b3de368fa8a77c9b4 -- 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 358633] New: The editor of the composer changed, no alternative configurable
https://bugs.kde.org/show_bug.cgi?id=358633 Bug ID: 358633 Summary: The editor of the composer changed, no alternative configurable Product: kmail2 Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: r...@w3.org As mentioned in IRC: The composer behavior changed (editor) as ctrl-k doesn't delete the line anymore. Kate has a different behaviour as ctrl-k deletes the line. I would like to use katepart in composer so that I can use all the very advanced features from kate (like word completion). This is not configurable. Reproducible: Always Steps to Reproduce: 1. Type ctrl-k 2. characters are deleted until the end of line 3. cursor remains there 4. with cursor on empty line ctrl-k has no effect Expected Results: ctrl-k should delete the line as in kate Just allowing people to use katepart in composer would be good enough. This should go into the settings -- 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
[kontact] [Bug 356116] Kmail crashes when forwarding mails
https://bugs.kde.org/show_bug.cgi?id=356116 Matthias Kretz changed: What|Removed |Added CC||kr...@kde.org --- Comment #2 from Matthias Kretz --- I just got a very similar crash backtrace on the following activity: * new mail * click 'Select' button on To: field * the dialog opens and is unresponsive, waiting for the contact data to come in (this blocking UI - and the time it takes might be worth a bug report itself). * the dialog shows the contact data for half a second * crash ## Comment on the backtrace The `0x0` in `#31 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0` looks suspicious. ## 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 0x7f885ef7f880 (LWP 25653))] Thread 7 (Thread 0x7f883ce89700 (LWP 25655)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f885b26d48b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f885b26d4c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f88569ec6aa in start_thread (arg=0x7f883ce89700) at pthread_create.c:333 #4 0x7f885c15feed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f87f57d1700 (LWP 25656)): #0 0x7f885c15049d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f8855db24e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8855d6ecd4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8855d6f190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8855d6f2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f885cc9529b in QEventDispatcherGlib::processEvents (this=0x7f87f8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f885cc3b75a in QEventLoop::exec (this=this@entry=0x7f87f57d0d40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f885ca593d4 in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7f885ca5e2be in QThreadPrivate::start (arg=0xb59a60) at thread/qthread_unix.cpp:337 #9 0x7f88569ec6aa in start_thread (arg=0x7f87f57d1700) at pthread_create.c:333 #10 0x7f885c15feed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f87efcb2700 (LWP 25657)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f885af7b5b4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f885b29d341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f88569ec6aa in start_thread (arg=0x7f87efcb2700) at pthread_create.c:333 #4 0x7f885c15feed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f87ef4b1700 (LWP 25658)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f885af7c5e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f885b29d341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f88569ec6aa in start_thread (arg=0x7f87ef4b1700) at pthread_create.c:333 #4 0x7f885c15feed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f87eecb0700 (LWP 25659)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f885af7c5e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f885b29d341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f88569ec6aa in start_thread (arg=0x7f87eecb0700) at pthread_create.c:333 #4 0x7f885c15feed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f87ee4af700 (LWP 25660)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f885af7c5e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f885b29d341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f88569ec6aa in start_thread (arg=0x7f87ee4af700) at pthread_create.c:333 #4 0x7f885c15feed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f885ef7f880 (LWP 25653)): [KCrash Handler] #6 QSortFilterProxyModelPrivate::index_to_iterator (this=0x3609120, proxy_index=...) at itemmodels/qsortfilterproxymodel.cpp:185 #7 QSortFilterProxyModelPrivate::proxy_to_source (proxy_index=..., this=0x3609120) at itemmodels/qsortfilterproxymodel.cpp:375 #8 QSortFilterProxyModel::mapToSource (proxyIndex=..., this=0x70737c0) at itemmodels/qsortfilterproxymodel.cpp:2716 #9 QSortFilterProxyModelPrivate::store_persistent_indexes (this=this@entry=0x3609120) at itemmodels/qsortfilterproxymo
[kmail2] [Bug 352464] Regression kMail 5.0.0: HTML mails do not show external images
https://bugs.kde.org/show_bug.cgi?id=352464 a.skemb...@gmail.com changed: What|Removed |Added CC||a.skemb...@gmail.com --- Comment #18 from a.skemb...@gmail.com --- I get a similar behaviour, on openSUSE RPMs, version 5.1.1. External images are shown but embedded are not. Same issue? -- 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
[kmail2] [Bug 323929] kmail high cpu load, seems stuck looping on fetching mails from akonadi
https://bugs.kde.org/show_bug.cgi?id=323929 --- Comment #41 from Martin Steigerwald --- Also please carefully check whether the issue you see is the same as this issue. I already have the impression that this bug contains more than one issue. If at doubt, please rather open a new issue. Is Akonadi actually fetching mails? If in doubt please open a new mail and include more information. The processlist does not do much to aid in debugging. See for example: https://techbase.kde.org/Projects/PIM/Akonadi/Development_Tools At least some information on what Akonadi is actually doing during high load (debugger) would be interesting. And in case of IMAP issues (you seem to have a huge lot of IMAP accounts configured): https://techbase.kde.org/Projects/PIM/Akonadi/Debug_IMAP As performance fixes are unlikely to be backported, I suggest doing these debugging steps only if the issue persists with KDEPIM 15.12 or later. -- 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