[Akonadi] [Bug 368376] New: Imap Push stopped working after wake up from Suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=368376 Bug ID: 368376 Summary: Imap Push stopped working after wake up from Suspend to RAM Product: Akonadi Version: 16.04 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: hla...@hlavki.eu CC: kdepim-bugs@kde.org, vkra...@kde.org Push-IMAP stopped working after wake up from Suspend to RAM Reproducible: Always Steps to Reproduce: 1. Suspend to RAM 2. Wake up from Suspend to RAM -- You are receiving this mail because: You are on the CC list for the bug.
[akregator] [Bug 368242] Default feeds still use kde-apps and kde-look
https://bugs.kde.org/show_bug.cgi?id=368242 Denis Kurz changed: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #5 from Denis Kurz --- > Do you know url for rss or rdf file ? https://store.kde.org/content.rdf <-- This one? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368378] New: Regression in kMail 5.3.x: Drag and drop of attachments from a received mail into the composer does not work any more
https://bugs.kde.org/show_bug.cgi?id=368378 Bug ID: 368378 Summary: Regression in kMail 5.3.x: Drag and drop of attachments from a received mail into the composer does not work any more Product: kmail2 Version: Git (master) Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: kdeb...@customcdrom.de Note: I'm using the plain text composer, just in case this makes a difference. In previous versions, it was possible to drag and drop attachments from any mail into a new composer window. This does not work any more for me with kMail 5.3.x - instead of adding the dragged attachment, text similar to the following is pasted into the editor window if I drop the attachment: attachment:2?place=header or attachment:2?place=body depending on if a drag from the mails header area or body area. Copy/paste of attachments using the context menu still works as a workaround. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 330472] ownCloud News App support
https://bugs.kde.org/show_bug.cgi?id=330472 David Heidelberg changed: What|Removed |Added CC||da...@ixit.cz --- Comment #3 from David Heidelberg --- ping, have nextCloud* News support would be nice! * or formely ownCloud - same API -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 311456] imap idle is not working with GSSAPI
https://bugs.kde.org/show_bug.cgi?id=311456 Dennis Schridde changed: What|Removed |Added CC||dennis.schridde@uni-heidelb ||erg.de -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 284172] Kmail does not correctly recognize some IMAP-Inbox-Folders
https://bugs.kde.org/show_bug.cgi?id=284172 Dennis Schridde changed: What|Removed |Added CC||dennis.schridde@uni-heidelb ||erg.de -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 k...@mail.orbitel.bg changed: What|Removed |Added CC||k...@mail.orbitel.bg --- Comment #23 from k...@mail.orbitel.bg --- Thanks Christian! I also just updated my Tumbleweed using your repo and the issue seems to be gone. I am crossing fingers in hope this nasty bug could be fixed till the next Tumbleweed update. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368380] New: Kmail crashing when moving mails from inbox to subdirectories
https://bugs.kde.org/show_bug.cgi?id=368380 Bug ID: 368380 Summary: Kmail crashing when moving mails from inbox to subdirectories Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: franz.berges...@gmail.com Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.2-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: I use kmail for my work emails via imaps - What I was doing when the application crashed: Moving multiple emails from the inbox to the directory it belongs to. I have been on vacation for the past two weeksand had to go through and sort >200 e-mails. I moved the mails in small bunches (a few to about 10 at a times) and since this morning I got probably 5-10 crashes. I don't recal similar issues before. I have the impression that most of crashes happend when moving *only some messages* of a thread into one directory, leaving the others in the inbox. The crash happens right after the messages are moved, since I don't see them anymore in the inbox. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff131a5e940 (LWP 2319))] Thread 39 (Thread 0x7fef987f0700 (LWP 15113)): #0 0x7ff12e7f77fd in read () at /lib64/libc.so.6 #1 0x7ff123eb2c00 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff123e6fae6 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff123e6ffb4 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff123e7012c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7ff12f33eaab in QEventDispatcherGlib::processEvents(QFlags) (this=0x7ff08c331f30, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #6 0x7ff12f2e66fa in QEventLoop::exec(QFlags) (this=this@entry=0x7fef987efc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7ff12f10c3c3 in QThread::exec() (this=) at thread/qthread.cpp:500 #8 0x7ff12f1112e8 in QThreadPrivate::start(void*) (arg=0x1866020) at thread/qthread_unix.cpp:341 #9 0x7ff124693454 in start_thread () at /lib64/libpthread.so.0 #10 0x7ff12e80415d in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7fef99ac5700 (LWP 15112)): #0 0x7ff12469907f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff11f5e1363 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7ff11f917981 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7ff124693454 in start_thread () at /lib64/libpthread.so.0 #4 0x7ff12e80415d in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7fef9a2c6700 (LWP 15111)): #0 0x7ff12469907f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff11f5e1363 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7ff11f917981 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7ff124693454 in start_thread () at /lib64/libpthread.so.0 #4 0x7ff12e80415d in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7fefdaeda700 (LWP 15110)): #0 0x7ff12469907f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff11f5e1363 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7ff11f917981 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7ff124693454 in start_thread () at /lib64/libpthread.so.0 #4 0x7ff12e80415d in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7ff0caffd700 (LWP 15109)): #0 0x7ff12469907f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff11f5e0211 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7ff11f917981 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7ff124693454 in start_thread () at /lib64/libpthread.so.0 #4 0x7ff12e80415d in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7ff0cbfff700 (LWP 15108)): #0 0x7ff12469907f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff11f8e6c5b in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7ff11f8e6c99 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7ff124693454 in start_thread () at /lib64/libpthread.so.0 #4 0x7ff12e80415d in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7fefdb6db700 (LWP 3217)): #0 0x7ff12469907f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff11ab65d49 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7ff11ab66460 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7ff11ab66630 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7ff11ab6323d in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7ff124693454 in start_thread () at /lib64/libpthread.so.0 #6 0x7ff12e80415d in clone () at
[kmail2] [Bug 368381] New: KMail 5.2.3 / Akonadi 16.04.3 shows no quota warnings
https://bugs.kde.org/show_bug.cgi?id=368381
Bug ID: 368381
Summary: KMail 5.2.3 / Akonadi 16.04.3 shows no quota warnings
Product: kmail2
Version: 5.2.1
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: UI
Assignee: kdepim-bugs@kde.org
Reporter: dennis.schri...@uni-heidelberg.de
KMail 5.2.3 / Akonadi 16.04.3 provides me with no warning about exceeded quota
or failing uploads due to exceeded quota.
Reproducible: Always
Steps to Reproduce:
1. Exceeded IMAP quota on the server.
2. Fill folders with new emails (e.g. in the \Sent folder after sending
emails).
Actual Results:
1. KMail stops uploading messages to the server, without notifying me that it
was unable to synchronise completely.
2. Deleting messages also becomes impossible, presumably because they are first
copied to \Trash, which will fail due to the exceeded quota.
Expected Results:
KMail should display a warning when I am at e.g. 90% of my IMAP quota, a very
noticable error message when I am above 99% (i.e. when it becomes impossible to
store a reasonably sized email), and very noticable error messages for every
mail that cannot be uploaded to the server for whatever reason. It should also
mark such not-synchronised messages with a warning in the message list and
folders containing such messages (and folders containing folders containing
such messages) in the folder list.
I am using KMail 5.2.3 (the "version" list here in bugzilla allows me to select
only 5.2.1).
The server is running (response to the ID IMAP command from RFC 2971 [2]):
Cyrus IMAPD v2.4.17-Fedora-RPM-2.4.17-8.el7_1 d1df8aff 2012-12-01
Trojita displays a modal warning dialogue that "quota exceeded" (or similar).
This might be a message coming from the server, probably via the OVERQUOTA
response code from RFC 5530 [1], which is handled in
src/Imap/Parser/Response.{cpp,h} in the Trojita source code.
[1]: https://tools.ietf.org/html/rfc5530
[2]: https://tools.ietf.org/html/rfc2971
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 368378] Regression in kMail 5.3.x: Drag and drop of attachments from a received mail into the composer does not work any more
https://bugs.kde.org/show_bug.cgi?id=368378 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- know bug. In investigation -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 368242] Default feeds still use kde-apps and kde-look
https://bugs.kde.org/show_bug.cgi?id=368242 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/akre ||gator/004f0852e2d6a7c080396 ||b1dfb97d42802e04610 Version Fixed In||5.3.1 --- Comment #6 from Laurent Montel --- Git commit 004f0852e2d6a7c080396b1dfb97d42802e04610 by Montel Laurent. Committed on 07/09/2016 at 11:53. Pushed by mlaurent into branch 'master'. Fix Bug 368242 - Default feeds still use kde-apps and kde-look FIXED-IN: 5.3.1 M +1-1src/akregator_part.cpp http://commits.kde.org/akregator/004f0852e2d6a7c080396b1dfb97d42802e04610 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 368242] Default feeds still use kde-apps and kde-look
https://bugs.kde.org/show_bug.cgi?id=368242 Laurent Montel changed: What|Removed |Added Latest Commit|http://commits.kde.org/akre |http://commits.kde.org/kdep |gator/004f0852e2d6a7c080396 |im/3f3265e99cdf57659aed826d |b1dfb97d42802e04610 |5e19878e41d446a2 --- Comment #7 from Laurent Montel --- Git commit 3f3265e99cdf57659aed826d5e19878e41d446a2 by Montel Laurent. Committed on 07/09/2016 at 11:53. Pushed by mlaurent into branch 'Applications/16.08'. Fix Bug 368242 - Default feeds still use kde-apps and kde-look FIXED-IN: 5.3.1 M +1-1akregator/src/akregator_part.cpp http://commits.kde.org/kdepim/3f3265e99cdf57659aed826d5e19878e41d446a2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368387] New: KMail crashes when I filter a Mail
https://bugs.kde.org/show_bug.cgi?id=368387 Bug ID: 368387 Summary: KMail crashes when I filter a Mail Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: achim.her...@wodca.de Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.2-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was applying a filter (Ctrl-J) to a Mail when KMail crashed. It looked like it only crashed when trying to show the next mail, not in the filtering. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa4c29f9940 (LWP 5593))] Thread 54 (Thread 0x7fa2e3fff700 (LWP 8287)): #0 0x7ffcc0b3e989 in () #1 0x7ffcc0b3ec61 in clock_gettime () #2 0x7fa4bf7b0de6 in clock_gettime () at /lib64/libc.so.6 #3 0x7fa4c015cd96 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fa4c02dc639 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #5 0x7fa4c02dcbe5 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #6 0x7fa4c02ddf9e in () at /usr/lib64/libQt5Core.so.5 #7 0x7fa4b4e0f569 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #8 0x7fa4b4e0ff3b in () at /usr/lib64/libglib-2.0.so.0 #9 0x7fa4b4e1012c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #10 0x7fa4c02deaab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7fa4c02866fa in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #12 0x7fa4c00ac3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #13 0x7fa4c00b12e8 in () at /usr/lib64/libQt5Core.so.5 #14 0x7fa4b5633454 in start_thread () at /lib64/libpthread.so.0 #15 0x7fa4bf7a415d in clone () at /lib64/libc.so.6 Thread 53 (Thread 0x7fa308d41700 (LWP 8285)): #0 0x7fa4bf79b78d in poll () at /lib64/libc.so.6 #1 0x7fa4b4e10016 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa4b4e1012c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa4c02deaab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa4c02866fa in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa4c00ac3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa4c00b12e8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fa4b5633454 in start_thread () at /lib64/libpthread.so.0 #8 0x7fa4bf7a415d in clone () at /lib64/libc.so.6 Thread 52 (Thread 0x7fa309542700 (LWP 8283)): #0 0x7fa4b4e53fc0 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fa4b4e0fa29 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa4b4e0ffb4 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa4b4e1012c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fa4c02deaab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa4c02866fa in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fa4c00ac3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fa4c00b12e8 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fa4b5633454 in start_thread () at /lib64/libpthread.so.0 #9 0x7fa4bf7a415d in clone () at /lib64/libc.so.6 Thread 51 (Thread 0x7fa35b7fe700 (LWP 8281)): #0 0x7fa4bf79b78d in poll () at /lib64/libc.so.6 #1 0x7fa4b4e10016 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa4b4e1012c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa4c02deaab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa4c02866fa in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa4c00ac3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa4c00b12e8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fa4b5633454 in start_thread () at /lib64/libpthread.so.0 #8 0x7fa4bf7a415d in clone () at /lib64/libc.so.6 Thread 50 (Thread 0x7fa30affb700 (LWP 8279)): #0 0x7fa4b4e0f520 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7fa4b4e0ff3b in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa4b4e1012c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa4c02deaab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa4c02866fa in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fa4c00ac3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fa4c00
[kontact] [Bug 367597] kontakt crash / loop after update
https://bugs.kde.org/show_bug.cgi?id=367597 Paolo Pedroni changed: What|Removed |Added CC||paolo.pedr...@iol.it -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 367808] kontact crashed when closing
https://bugs.kde.org/show_bug.cgi?id=367808 Paolo Pedroni changed: What|Removed |Added CC||paolo.pedr...@iol.it -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368387] KMail crashes when I filter a Mail
https://bugs.kde.org/show_bug.cgi?id=368387 Paolo Pedroni changed: What|Removed |Added CC||paolo.pedr...@iol.it -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 359964] "Kmailleaks", or what to improve to make Kmail more privacy friendly.
https://bugs.kde.org/show_bug.cgi?id=359964 Johannes Klick changed: What|Removed |Added CC||johannes.kl...@fu-berlin.de --- Comment #9 from Johannes Klick --- HI, i totally agree with Thomas Pfeiffer. Kmail sends by default the OS type, kernel version and the desktop environment by default. It is very useful for an attacker, who wants to send you an email with a malicious attachment... Please remove the User-Agent field by default or is it really necessary? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 359964] "Kmailleaks", or what to improve to make Kmail more privacy friendly.
https://bugs.kde.org/show_bug.cgi?id=359964 --- Comment #10 from Johannes Klick --- (In reply to Luca Beltrame from comment #5) > (In reply to eemantsal from comment #3) > > > identities' and accounts' preferences but haven't found it. Also, don't you > > think that if it can be disabled or customized with a generic name like > > You can find it in Configure KMail > Composer > Headers. For making it more precise: It is possible to override the User-Agent field by adding the field "User-Agent" under "Configure KMail > Composer > Headers" but this is not intuitive. Disable User-Agent field by default and provide a menu that shows all default Headers and its values. This would make it easy for an user to edit the values. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368400] New: KMail sometimes crashes
https://bugs.kde.org/show_bug.cgi?id=368400 Bug ID: 368400 Summary: KMail sometimes crashes Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: vojtech.zei...@opensuse.org Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.2-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Without any aparent reason or user intervention, KMail sometimes crashes. It is running in background and the user can do whatever different. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7efe4be75940 (LWP 2315))] Thread 41 (Thread 0x7efcad21c700 (LWP 4911)): #0 0x7efe48c20a1d in poll () at /lib64/libc.so.6 #1 0x7efe3e296036 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7efe3e29614c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7efe49763aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7efe4970b76a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7efe495313b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7efe495362d8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7efe3eab9474 in start_thread () at /lib64/libpthread.so.0 #8 0x7efe48c293ed in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7efdfe17e700 (LWP 4532)): #0 0x7efe3e2da034 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7efe3e294fde in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #2 0x7efe3e295ee5 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7efe3e29614c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7efe49763aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7efe4970b76a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7efe495313b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7efe495362d8 in () at /usr/lib64/libQt5Core.so.5 #8 0x7efe3eab9474 in start_thread () at /lib64/libpthread.so.0 #9 0x7efe48c293ed in clone () at /lib64/libc.so.6 Thread 39 (Thread 0x7efcafffd700 (LWP 4486)): #0 0x7efe3eabf09f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efe34f91129 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7efe34f91840 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7efe34f91a10 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7efe34f8e5cd in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7efe3eab9474 in start_thread () at /lib64/libpthread.so.0 #6 0x7efe48c293ed in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7efd78d59700 (LWP 4485)): #0 0x7efe3eabf09f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efe34f91129 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7efe34f91840 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7efe34f91a10 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7efe34f8e5cd in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7efe3eab9474 in start_thread () at /lib64/libpthread.so.0 #6 0x7efe48c293ed in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7efd7995a700 (LWP 4419)): #0 0x7efe3eabf09f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efe39a13163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7efe39d49781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7efe3eab9474 in start_thread () at /lib64/libpthread.so.0 #4 0x7efe48c293ed in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7efd7a15b700 (LWP 4418)): #0 0x7efe3eabf09f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efe39a13163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7efe39d49781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7efe3eab9474 in start_thread () at /lib64/libpthread.so.0 #4 0x7efe48c293ed in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7efd7a95c700 (LWP 4417)): #0 0x7efe3eabf09f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efe39a13163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7efe39d49781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7efe3eab9474 in start_thread () at /lib64/libpthread.so.0 #4 0x7efe48c293ed in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7efd7b15d700 (LWP 4416)): #0 0x7efe3eabf09f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efe39a13163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7efe39d49781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7efe3e
[kmail2] [Bug 359964] "Kmailleaks", or what to improve to make Kmail more privacy friendly.
https://bugs.kde.org/show_bug.cgi?id=359964 --- Comment #11 from mal...@w4eg.de --- (In reply to Johannes Klick from comment #10) > > You can find it in Configure KMail > Composer > Headers. > > For making it more precise: > It is possible to override the User-Agent field by adding the field > "User-Agent" under "Configure KMail > Composer > Headers" but this is not > intuitive. Does this also allow the user to completely remove the User-Agent header? (Which I also think should be the default nowadays.) -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 276707] Main progress meter does not correspond to individual feed meters properly
https://bugs.kde.org/show_bug.cgi?id=276707 Christian Boltz changed: What|Removed |Added CC||kde-b...@cboltz.de --- Comment #1 from Christian Boltz --- In the meantime (5 years later, Akregator 5.2.3), the main progress meter just shows a running bar (without any progress indication or percentage), which means it isn't too useful. I agree with the initial bugreport that the progress meter should show a percentage that is based on "x of y feeds fetched successfully". -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 368417] New: adding IMAP account causing akonadi_imap_resource segmentation faults
https://bugs.kde.org/show_bug.cgi?id=368417 Bug ID: 368417 Summary: adding IMAP account causing akonadi_imap_resource segmentation faults Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: bor...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.14) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-35-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: just finished adding an imap account. The exact same account config info is working fine on my mobile phone, also just set up. This is not a new install of kontact/kmail, it's been running for a couple of years. I just changed web hosting services and had to reconfigure the email account to match the new server. I had the same setup on the old servers, only the server address has changed. The imap gmail account has not changed and is working fine with no errors. When I go into Configure Kmail, the account is stuck on "Syncing folder 'inbox' (100%)" The crash can be reproduced every time. -- Backtrace: Application: icb@wavefront of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbd32c3e780 (LWP 2672))] Thread 3 (Thread 0x7fbd1f724700 (LWP 2728)): #0 0x7fbd2e58988d in poll () at /lib64/libc.so.6 #1 0x7fbd2d511be4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fbd2d511cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbd3226b0de in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7fbd3223ce6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7fbd3223d165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7fbd3213a0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7fbd3213c79f in () at /usr/lib64/libQtCore.so.4 #8 0x7fbd2dbf60a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fbd2e591cbd in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fbd17fff700 (LWP 2763)): #0 0x7fbd2d5538e9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fbd2d51152e in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7fbd2d511b7b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbd2d511cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fbd3226b0de in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7fbd3223ce6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7fbd3223d165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7fbd3213a0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #8 0x7fbd3213c79f in () at /usr/lib64/libQtCore.so.4 #9 0x7fbd2dbf60a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fbd2e591cbd in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fbd32c3e780 (LWP 2672)): [KCrash Handler] #5 0x0045cd3b in () #6 0x7fbd3271a0cf in () at /usr/lib64/libakonadi-kde.so.4 #7 0x7fbd3268706c in Akonadi::CollectionModifyJob::doStart() () at /usr/lib64/libakonadi-kde.so.4 #8 0x7fbd32700367 in () at /usr/lib64/libakonadi-kde.so.4 #9 0x7fbd3274cf39 in () at /usr/lib64/libakonadi-kde.so.4 #10 0x7fbd3274d6d5 in () at /usr/lib64/libakonadi-kde.so.4 #11 0x7fbd3225659e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #12 0x7fbd315d776c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #13 0x7fbd315ddcad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #14 0x7fbd2f6ede0a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #15 0x7fbd3223e2ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #16 0x7fbd3224157d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4 #17 0x7fbd3226b8fe in () at /usr/lib64/libQtCore.so.4 #18 0x7fbd2d511a04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #19 0x7fbd2d511c48 in () at /usr/lib64/libglib-2.0.so.0 #20 0x7fbd2d511cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #21 0x7fbd3226b0be in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #22 0x7fbd31674676 in () at /usr/lib64/libQtGui.so.4 #23 0x7fbd3223ce6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #24 0x7fbd3223d165 in QEventLo
[kmail2] [Bug 368387] KMail crashes when I filter a Mail
https://bugs.kde.org/show_bug.cgi?id=368387 Denis Kurz changed: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 364994 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368400] KMail sometimes crashes
https://bugs.kde.org/show_bug.cgi?id=368400 Denis Kurz changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 364994 *** -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 364994] Kmail crash when deleting message in thread view
https://bugs.kde.org/show_bug.cgi?id=364994 Denis Kurz changed: What|Removed |Added CC||vojtech.zei...@opensuse.org --- Comment #10 from Denis Kurz --- *** Bug 368400 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 364994] Kmail crash when deleting message in thread view
https://bugs.kde.org/show_bug.cgi?id=364994 Denis Kurz changed: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #11 from Denis Kurz --- Judging from all the other bug reports, this seems to be triggered by the removal of a message from a threaded message list. It has been reported for manual deletion of a message, manual moves of a message to another folder, applying a filter manually and "crashing in the background" (automatically applied filter on incoming mail, I guess). Suggestions for workarounds: avoid threaded view for a while, or at least don't move mails while in threaded view. This includes mail filters. Of course, I know that these are not very practical, sorry... -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 364994] Kmail crash when deleting message in thread view
https://bugs.kde.org/show_bug.cgi?id=364994 --- Comment #12 from Achim Herwig --- Thanks for the heads-up - a bad workaround is still better than none. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 364994] Kmail crash when deleting message in thread view
https://bugs.kde.org/show_bug.cgi?id=364994 Denis Kurz changed: What|Removed |Added CC||achim.her...@wodca.de --- Comment #9 from Denis Kurz --- *** Bug 368387 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 362420] DAV Resource 16.04.0: Segfaults randomly
https://bugs.kde.org/show_bug.cgi?id=362420 --- Comment #1 from Till Schäfer --- the bug is still valid on 16.08.0 (Frameworks 5.25), although the stack trace changed slightly: Application: akonadi_davgroupware_resource (akonadi_davgroupware_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57b9ca37c0 (LWP 4953))] Thread 1 (Thread 0x7f57b9ca37c0 (LWP 4953)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/include/g++-v4/bits/atomic_base.h:500 #7 QAtomicOps::load (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:96 #8 QBasicAtomicInteger::load (this=) at /usr/include/qt5/QtCore/qbasicatomic.h:116 #9 QtPrivate::RefCount::isShared (this=) at /usr/include/qt5/QtCore/qrefcount.h:95 #10 QMap::detach (this=) at /usr/include/qt5/QtCore/qmap.h:360 #11 QMap::operator[] (akey=..., this=) at /usr/include/qt5/QtCore/qmap.h:658 #12 EtagCache::setEtag (this=this@entry=0x0, remoteId=..., etag=...) at /var/tmp/portage/kde-apps/kdepim-runtime-16.08.0/work/kdepim-runtime-16.08.0/resources/dav/common/etagcache.cpp:38 #13 0x0045569d in DavGroupwareResource::onItemFetched (this=0x1a7abc0, job=, updateType=DavGroupwareResource::ItemUpdateAdd) at /var/tmp/portage/kde-apps/kdepim-runtime-16.08.0/work/kdepim-runtime-16.08.0/resources/dav/resource/davgroupwareresource.cpp:959 #14 0x7f57d55ef882 in QtPrivate::QSlotObjectBase::call (a=0x7fff13f158e0, r=0x1a7abc0, this=0x1c82ad0) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #15 QMetaObject::activate (sender=sender@entry=0x1cacf60, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff13f158e0) at kernel/qobject.cpp:3715 #16 0x7f57d55efdb7 in QMetaObject::activate (sender=sender@entry=0x1cacf60, m=m@entry=0x7f57d6cee2e0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff13f158e0) at kernel/qobject.cpp:3595 #17 0x7f57d6a98682 in KJob::result (this=this@entry=0x1cacf60, _t1=_t1@entry=0x1cacf60) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.25.0/work/kcoreaddons-5.25.0_build/src/lib/moc_kjob.cpp:568 #18 0x7f57d6a99da1 in KJob::finishJob (this=this@entry=0x1cacf60, emitResult=emitResult@entry=true) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.25.0/work/kcoreaddons-5.25.0/src/lib/jobs/kjob.cpp:109 #19 0x7f57d6a99e2a in KJob::emitResult (this=this@entry=0x1cacf60) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.25.0/work/kcoreaddons-5.25.0/src/lib/jobs/kjob.cpp:293 #20 0x00421bf9 in DavItemFetchJob::davJobFinished (this=0x1cacf60, job=) at /var/tmp/portage/kde-apps/kdepim-runtime-16.08.0/work/kdepim-runtime-16.08.0/resources/dav/common/davitemfetchjob.cpp:92 #21 0x7f57d55ef882 in QtPrivate::QSlotObjectBase::call (a=0x7fff13f15b50, r=0x1cacf60, this=0x1d06670) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #22 QMetaObject::activate (sender=sender@entry=0x1ca8a60, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff13f15b50) at kernel/qobject.cpp:3715 #23 0x7f57d55efdb7 in QMetaObject::activate (sender=sender@entry=0x1ca8a60, m=m@entry=0x7f57d6cee2e0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff13f15b50) at kernel/qobject.cpp:3595 #24 0x7f57d6a98682 in KJob::result (this=this@entry=0x1ca8a60, _t1=_t1@entry=0x1ca8a60) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.25.0/work/kcoreaddons-5.25.0_build/src/lib/moc_kjob.cpp:568 #25 0x7f57d6a99da1 in KJob::finishJob (this=this@entry=0x1ca8a60, emitResult=emitResult@entry=true) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.25.0/work/kcoreaddons-5.25.0/src/lib/jobs/kjob.cpp:109 #26 0x7f57d6a99e2a in KJob::emitResult (this=this@entry=0x1ca8a60) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.25.0/work/kcoreaddons-5.25.0/src/lib/jobs/kjob.cpp:293 #27 0x7f57d7ebc7e2 in KIO::SimpleJob::slotFinished (this=this@entry=0x1ca8a60) at /var/tmp/portage/kde-frameworks/kio-5.25.0/work/kio-5.25.0/src/core/simplejob.cpp:230 #28 0x7f57d7ec5b86 in KIO::TransferJob::slotFinished (this=0x1ca8a60) at /var/tmp/portage/kde-frameworks/kio-5.25.0/work/kio-5.25.0/src/core/transferjob.cpp:166 #29 0x7f57d7ec5311 in KIO::TransferJob::qt_static_metacall (_o=, _c=, _id=, _a=) at /var/tmp/portage/kde-frameworks/kio-5.25.0/work/kio-5.25.0_build/src/core/moc_transferjob.cpp:155 #30 0x7f57d55ef21c in QMetaObject::activate (sender=sender@entry=0x1a7b1f0, signalOffset=, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x0) at kernel/qobject.cpp:3730 #31 0x7f57d55efdb7 in QMetaObject::activate (sender=sender@entry=0x1a7b1f0, m=m@entry=0x7f57d8164180 , local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x0) at kernel/qobject.cpp:3595 #32 0x7f57d7e9df13 in KIO::SlaveInterface::finished (this=this@entry=0x1a7b1f0) at /var/tmp/portage/kde-frameworks/kio
[Akonadi] [Bug 362420] DAV Resource 16.08.0: Segfaults randomly
https://bugs.kde.org/show_bug.cgi?id=362420 Till Schäfer changed: What|Removed |Added Summary|DAV Resource 16.04.0: |DAV Resource 16.08.0: |Segfaults randomly |Segfaults randomly Version|16.04 |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368434] New: Kontact crash when filing through eMail
https://bugs.kde.org/show_bug.cgi?id=368434 Bug ID: 368434 Summary: Kontact crash when filing through eMail Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kdeb...@munin-soft.de Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.2-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I just upgraded and stared Kontact. When selecting the first of my folders with new mail, Kontact was hanging. After a minute or so it reacted again. When selecting now a different folder, it crashed. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f11437bd940 (LWP 9166))] Thread 43 (Thread 0x7f0f937fe700 (LWP 9335)): #0 0x7f113c01e07f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f10218a1363 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f1021bd7981 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f113c018454 in start_thread (arg=0x7f0f937fe700) at pthread_create.c:333 #4 0x7f114017015d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 42 (Thread 0x7f0f98922700 (LWP 9334)): #0 0x7f113c01e07f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f10218a1363 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f1021bd7981 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f113c018454 in start_thread (arg=0x7f0f98922700) at pthread_create.c:333 #4 0x7f114017015d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 41 (Thread 0x7f0f99123700 (LWP 9333)): #0 0x7f113c01e07f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f10218a1363 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f1021bd7981 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f113c018454 in start_thread (arg=0x7f0f99123700) at pthread_create.c:333 #4 0x7f114017015d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 40 (Thread 0x7f0f93fff700 (LWP 9332)): #0 0x7f113c01e07f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f10218a1363 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f1021bd7981 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f113c018454 in start_thread (arg=0x7f0f93fff700) at pthread_create.c:333 #4 0x7f114017015d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 39 (Thread 0x7f0f99924700 (LWP 9331)): #0 0x7f113c01e07f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f10218a1363 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f1021bd7981 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f113c018454 in start_thread (arg=0x7f0f99924700) at pthread_create.c:333 #4 0x7f114017015d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 38 (Thread 0x7f0f9a125700 (LWP 9330)): #0 0x7f113c01e07f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f10218a1363 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f1021bd7981 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f113c018454 in start_thread (arg=0x7f0f9a125700) at pthread_create.c:333 #4 0x7f114017015d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 37 (Thread 0x7f0fdaad7700 (LWP 9329)): #0 0x7f113c01e07f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f10218a0211 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f1021bd7981 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f113c018454 in start_thread (arg=0x7f0fdaad7700) at pthread_create.c:333 #4 0x7f114017015d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 36 (Thread 0x7f0fdb7eb700 (LWP 9328)): #0 0x7f113c01e07f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1021ba6c5b in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f1021ba6c99 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f113c018454 in start_thread (arg=0x7f0fdb7eb700) at pthread_create.c:333 #4 0x7f114017015d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 35 (Thread 0x7f0fed009700 (LWP 9291)): #0 0x7f11401637fd in read () at ../sysdeps/unix/syscall-template
