[frameworks-kcompletion] [Bug 370947] line edits 'delete' icon too big and pixalated with bigger fonts settings (11 instead 10pt). Uncovers a second icon below

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370947

Christoph Feck  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|WONTFIX |---
Version|Git (master)|unspecified
 CC||kdelibs-b...@kde.org
Product|kmail2  |frameworks-kcompletion
   Assignee|kdepim-bugs@kde.org |davidgilol...@gmail.com
  Component|general |general

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 370937] Kmail crashes on first run

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370937

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Christoph Feck  ---
This is a bug in the nouveau GL driver. If this is reproducible, please report
this issue to nouveau developers via https://bugs.freedesktop.org/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 343034] KMail insists on offline mode, even when network connection is available

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343034

Christoph Feck  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|UPSTREAM|---
 CC||cf...@kde.org

--- Comment #17 from Christoph Feck  ---
Andre, ntrack is not used, KF5 solid simply has no network status API any
longer. Reopening.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 370980] New: Space Key Doesn't Show Next Unread Message

[Garry Williams via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370980

Bug ID: 370980
   Summary: Space Key Doesn't Show Next Unread Message
   Product: kmail2
   Version: 5.3.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-bugs@kde.org
  Reporter: gtwilli...@gmail.com

The space key has always paged the message until the bottom and then displays
the next unread message.  This behavior has been how kmail has worked since the
beginning, as far as I know.

Please restore this behavior.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kleopatra] [Bug 370976] New: not able to convert certficate or secret keys to PKCS12

[Rich via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370976

Bug ID: 370976
   Summary: not able to convert certficate or secret keys to
PKCS12
   Product: kleopatra
   Version: 2.2.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: rio...@yahoo.com
CC: kdepim-bugs@kde.org, m...@kde.org

getting error that the exported cert files from kloepatra have bad end of lines
in them when trying to convert to PKCS12, I have used openssl and keystore
explorer with the same result. I'm not able to figure out what the formatting
issue is, I tired every file type available in app and all the same results.

Reproducible: Always

Steps to Reproduce:
1. export a certficate and export a secret key into any format given
2. attempt to convert those into the PKCS12 format with openssl or keystore
explorer
3.

Actual Results:  
errors out everytime stating bad end of line in the key file

Expected Results:  
what should happen is files should be converted int0p PKCS #12

have tried making new key file with copy paste but no success

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[kontact] [Bug 370965] New: kontact crash when selecting specific eMail

[rainer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370965

Bug ID: 370965
   Summary: kontact crash when selecting specific 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.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.7.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
When selecting a specific eMail in kontact, it crashes reproducible.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa9aad89e00 (LWP 3453))]

Thread 42 (Thread 0x7fa84285d700 (LWP 3583)):
#0  0x7fa9a77b26ed in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa9a147b876 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7fa834002a20, timeout=, context=0x7fa834000990)
at gmain.c:4226
#2  0x7fa9a147b876 in g_main_context_iterate
(context=context@entry=0x7fa834000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3922
#3  0x7fa9a147b98c in g_main_context_iteration (context=0x7fa834000990,
may_block=may_block@entry=1) at gmain.c:3988
#4  0x7fa9a82e879b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fa8340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fa9a82921ea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fa84285cc80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#6  0x7fa9a80c08b3 in QThread::exec() (this=) at
thread/qthread.cpp:507
#7  0x7fa9a80c5558 in QThreadPrivate::start(void*) (arg=0x31e0a40) at
thread/qthread_unix.cpp:344
#8  0x7fa9a3665454 in start_thread (arg=0x7fa84285d700) at
pthread_create.c:333
#9  0x7fa9a77bb3ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 41 (Thread 0x7fa843fff700 (LWP 3572)):
#0  0x7fa9a14c0ea4 in g_mutex_unlock (mutex=0x7fa83c000990) at
gthread-posix.c:1348
#1  0x7fa9a147a7ce in g_main_context_acquire (context=0x7fa83c000990) at
gmain.c:3281
#2  0x7fa9a147b725 in g_main_context_iterate
(context=context@entry=0x7fa83c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3877
#3  0x7fa9a147b98c in g_main_context_iteration (context=0x7fa83c000990,
may_block=may_block@entry=1) at gmain.c:3988
#4  0x7fa9a82e879b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fa83c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fa9a82921ea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fa843ffec80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#6  0x7fa9a80c08b3 in QThread::exec() (this=) at
thread/qthread.cpp:507
#7  0x7fa9a80c5558 in QThreadPrivate::start(void*) (arg=0x3309a90) at
thread/qthread_unix.cpp:344
#8  0x7fa9a3665454 in start_thread (arg=0x7fa843fff700) at
pthread_create.c:333
#9  0x7fa9a77bb3ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 40 (Thread 0x7fa85114b700 (LWP 3564)):
#0  0x7fa9a366b10f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa99a812659 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fa99a812c79 in base::SequencedWorkerPool::Worker::Run() () at
/usr/lib64/libQt5WebEngineCore.so.5
#3  0x7fa99a812e30 in base::SimpleThread::ThreadMain() () at
/usr/lib64/libQt5WebEngineCore.so.5
#4  0x7fa99a80fab7 in base::(anonymous namespace)::ThreadFunc(void*) () at
/usr/lib64/libQt5WebEngineCore.so.5
#5  0x7fa9a3665454 in start_thread (arg=0x7fa85114b700) at
pthread_create.c:333
#6  0x7fa9a77bb3ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 39 (Thread 0x7fa852fdb700 (LWP 3519)):
#0  0x7fa9a14c0ea4 in g_mutex_unlock (mutex=0x7fa844000990) at
gthread-posix.c:1348
#1  0x7fa9a147ad6c in g_main_context_prepare
(context=context@entry=0x7fa844000990, priority=priority@entry=0x7fa852fdab40)
at gmain.c:3497
#2  0x7fa9a147b79b in g_main_context_iterate
(context=context@entry=0x7fa844000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3907
#3  0x7fa9a147b98c in g_main_context_iteration (context=0x7fa844000990,
may_block=may_block@entry=1) at gmain.c:3988
#4  0x7fa9a82e879b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fa8440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fa9a82921ea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fa852fdac80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#6  0x7fa9a80c08b3 in QThread::exec() (this=) at
thread/qthread.cpp:507
#7  

[kmail] [Bug 143263] check-in after working offline kills inbox

[Laurent Montel via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=143263

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org
 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Laurent Montel  ---
You never gave info from 2009
so for sure we can't help you.
And for sure all code changed from 2009
Regards

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 370646] Crash because of stale (dangling) pointers in the attribute registry

[RJVB via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370646

RJVB  changed:

   What|Removed |Added

URL||http://arstechnica.com/civi
   ||s/viewtopic.php?p=32070659#
   ||p32070659

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 370646] Crash because of stale (dangling) pointers in the attribute registry

[RJVB via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370646

--- Comment #8 from RJVB  ---
This bug has gotten under my skin. Having looked at this a bit more and asking
around a bit, the most likely explanation for the crash is this:

- KCModuleLoader::loadModule() loads the library to get a pointer to the
create_ function. The library registers its attributes.
- libnoteshared (or the kcm depending on it) doesn't have such a function, and
so KCModuleLoader::loadModule() unloads the library again
- somewhat thereafter, the library (and/or the kcm depending on it) is loaded
once more, and again registers its attributes
- the attribute factory finds a previous registration, and attempts to delete
the registered attributes
- since the library was unloaded and reloaded since those attributes were
"new'ed", the dtor lives (potentially) at a different address.
- delete *it invokes the dtor ... which may SEGV if the dtor address has
changed.

I see that `KCModuleLoader::loadModule()` has hardly changed and not at all in
the aspects outlined above. IOW, this bug is likely to occur in KDE PIM5 too if
libnoteshared hasn't obtained a create_ function since.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail] [Bug 143263] check-in after working offline kills inbox

[Stephan Herrmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=143263

--- Comment #2 from Stephan Herrmann  ---
(In reply to Martin Koller from comment #1)
> Can you still reproduce this with a current version of KDE (4.3) ?

That kind of catastrophe you don't want to reproduce in your life time.

Feel free to close. 

After seeing no action for some years I had no other option than moving away
from kmail. I liked it back then, but deleting inbox is unforgivable, if you
ask me.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 370646] Crash because of stale (dangling) pointers in the attribute registry

[RJVB via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370646

RJVB  changed:

   What|Removed |Added

Summary|Crash when opening Kontact  |Crash because of stale
   |preferences |(dangling) pointers in the
   ||attribute registry

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kdepimlibs] [Bug 359708] Updated holiday file for Ukraine

[Allen Winter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359708

Allen Winter  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---
 Ever confirmed|0   |1

--- Comment #8 from Allen Winter  ---
re-opening because we never added the conditionals as discussed in Comment 6.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[kdepim] [Bug 349353] error building kdepim (KF5 port) with undefined reference to PimCommon::SyntaxHighlighterBase

[Allen Winter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=349353

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org

--- Comment #10 from Allen Winter  ---
over 1 year since this was first reported.
has it been resolved yet?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 89237] gpg signing preference not honoured when composing mail to somebody

[Allen Winter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=89237

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org
Product|kmail   |kmail2
   Target Milestone|--- |15.08
  Component|encryption  |crypto
 Status|RESOLVED|REOPENED
 Resolution|UNMAINTAINED|---
Version|SVN (3.5 branch)|unspecified

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 287514] mail check not working after hibernation of a laptop

[Allen Winter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=287514

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org
 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 365803] Akonadi prevents speedy GUI creation

[Allen Winter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365803

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org
   Version Fixed In||16.10
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 368498] Kmail does not open links with target="_blank"

[Allen Winter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=368498

Allen Winter  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED
 CC||win...@kde.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[neon] [Bug 370498] KMail crashes when pressing SPACE while displaying a message

[Allen Winter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370498

Allen Winter  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||win...@kde.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 370947] line edits 'delete' icon too big and pixalated with bigger fonts settings (11 instead 10pt). Uncovers a second icon below

[Laurent Montel via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370947

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX
 CC||mon...@kde.org

--- Comment #3 from Laurent Montel  ---
it's not a kmail bug it's a kf5 bug.
kcompletion I will told you.

Please reassign

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 361157] Akonadi does not work properly after Update to KDE FW 5.20, Plasma 5.6 and Qt5.6 on Opensuse Leap 42.1

[Oliver Winker via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361157

Oliver Winker  changed:

   What|Removed |Added

 CC||oliver...@oli1170.net

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 366002] kmail does not respect the use HTML instead of plain text setting

[Maxim Vasilyev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366002

Maxim Vasilyev  changed:

   What|Removed |Added

 CC||mxmvasily...@gmail.com

--- Comment #2 from Maxim Vasilyev  ---
This bug is still intact in KDE Neon as of October 2016, KMail 16.04.2. All
messages are displayed as plain text regarless of the settings (global or per
folder).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 346135] Kmail support for DarkThemes and HTML-Mails

[Maxim Vasilyev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346135

Maxim Vasilyev  changed:

   What|Removed |Added

 CC||mxmvasily...@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 370947] line edits 'delete' icon too big and pixalated with bigger fonts settings (11 instead 10pt). Uncovers a second icon below

[Achim Bohnet via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370947

Achim Bohnet  changed:

   What|Removed |Added

Summary|line edits 'delete' icon|line edits 'delete' icon
   |too big and pixalated with  |too big and pixalated with
   |bigger von fonts settings   |bigger fonts settings (11
   |(11 instead 10pt).  |instead 10pt).  Uncovers a
   |Uncovers a second icon  |second icon below
   |below   |

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 370947] line edits 'delete' icon too big and pixalated with bigger von fonts settings (11 instead 10pt). Uncovers a second icon below

[Achim Bohnet via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370947

--- Comment #2 from Achim Bohnet  ---
While reverting the font change I've found a simpler way to reproduce:

1. kmail --composer
2. Type a view chars in the 'To:' line edit
3.  Set the 'General' font in system settings from 10 pt to 11pt and apply
-> 'delete' icons in the composer window is pixalated and too big.

Changing font size back to 10 pt 'fixes' the pixalation.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 370947] line edits 'delete' icon too big and pixalated with bigger von fonts settings (11 instead 10pt). Uncovers a second icon below

[Achim Bohnet via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370947

--- Comment #1 from Achim Bohnet  ---
Created attachment 101581
  --> https://bugs.kde.org/attachment.cgi?id=101581=edit
oversized and pixalated 'delete' icons in kmail inline search and composer
address field

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 370947] New: line edits 'delete' icon too big and pixalated with bigger von fonts settings (11 instead 10pt). Uncovers a second icon below

[Achim Bohnet via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370947

Bug ID: 370947
   Summary: line edits 'delete' icon too big and pixalated with
bigger von fonts settings (11 instead 10pt).  Uncovers
a second icon below
   Product: kmail2
   Version: Git (master)
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: a...@mpe.mpg.de

My fonts are all + 1pt compared the default.   Now the quick search line edit
above message list and
e.g. address fields in the composer show a IMHO unproportional big icon that is
pixaled (see screenshot).

Further in the quick search line edit one sees below the pixalated delete icons
the right parts of the normal sized delete icons

Reproducible: Always

Steps to Reproduce:
1.  Quit kmail
2. open fonts in system settings
3. set all fonts size to 11 (alternatively add 1pt to each fonts size)
4. start kmail.
5a.  type some text in the quick search like edit
5b. open composer and start typing an address

Actual Results:  
An pixalated (oversized)  delete icons appear on the right of the line edit.

Expected Results:  
a) Icons is not pixalated
b) Icons size should be a bit smaller   (ditto for the sharp icons and the lock
icon)

I had a quick look at ohter apps:

kate open dialog:  delete icons sharp and unchanged with 11pt compared to 10
ptle
konsole change tab text dialog:  too big and pixalated like kmail composer

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 370646] Crash when opening Kontact preferences

[RJVB via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370646

--- Comment #7 from RJVB  ---
I see there's been a chronological glitch in my comments :-/

I wonder: shouldn't it be more elegant to do the actual unregistering
(attributes.erase(x)) in the Attribute dtor? I'll need to check if the
Attribute dtor is actually called when libnoteshared is unloaded and that
apparently leads to freeing memory allocated ("new'ed") by that library. If it
is, a lot of the above patches will be handled automatically.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 370938] New: Kmail loses connection to akonadi every few seconds

[Achim Herwig via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370938

Bug ID: 370938
   Summary: Kmail loses connection to akonadi every few seconds
   Product: kmail2
   Version: 5.3.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: achim.her...@wodca.de

When browsing through emails (IMAP-accounts, one zimbra, one dovecot, working
for years), kmail will lose the connection to akonadi every few seconds. It
will re-establish the connection immediately, but refresh the display so that
the folder tree is collapsed again and the current mail shown is some other
mail kmail remembers for some reason as being the current one.

As this happens every few seconds when using kmail, it is basically unusable.

Reproducible: Always

Steps to Reproduce:
1. open kmail
2. browse mails in sub-folders
3.

Actual Results:  
kmail loses connection to akonadi (or at least it claims so). It reconnects
immediately, but jumps out of the current mail and collapses the folder
structure. 

Expected Results:  
Not lose the connection.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 370937] New: Kmail crashes on first run

[Kosmas Mackrogamvrakis via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370937

Bug ID: 370937
   Summary: Kmail crashes on first run
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kos...@kosmas.gr

Application: kmail (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.7-200.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
After first time configuration of a clean plasma installation kmail crashes as
soon as it tries to open any email.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3b049ec940 (LWP 2669))]

Thread 32 (Thread 0x7f3a3bfff700 (LWP 2734)):
#0  0x7f3af3c3bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3afab18e79 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7f3afab19540 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f3afab19710 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f3afab160fd in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f3af3c365ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f3b02b41f6d in clone () at /lib64/libc.so.6

Thread 31 (Thread 0x7f3a4affc700 (LWP 2726)):
#0  0x7f3af3c3bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3ae7580bc4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f3ae7580c09 in  () at /lib64/libQt5Script.so.5
#3  0x7f3af3c365ca in start_thread () at /lib64/libpthread.so.0
#4  0x7f3b02b41f6d in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7f3a4b7fd700 (LWP 2724)):
#0  0x7f3b02b3204d in read () at /lib64/libc.so.6
#1  0x7f3af27eb660 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f3af27a84d6 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f3af27a89a4 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f3af27a8b1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f3b0394a24b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f3b038f95ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f3b03758343 in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f3b0375c99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f3af3c365ca in start_thread () at /lib64/libpthread.so.0
#10 0x7f3b02b41f6d in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7f3a4bffe700 (LWP 2712)):
#0  0x7f3af27eca09 in g_mutex_lock () at /lib64/libglib-2.0.so.0
#1  0x7f3af27a7f65 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7f3af27a892b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f3af27a8b1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f3b0394a24b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f3b038f95ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f3b03758343 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f3b0375c99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f3af3c365ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f3b02b41f6d in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7f3a57ffe700 (LWP 2704)):
#0  0x7f3af3c3bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3afaa28b90 in mojo::system::Waiter::Wait(unsigned long, unsigned
int*) () at /lib64/libQt5WebEngineCore.so.5
#2  0x7f3afaa1448c in mojo::system::Core::WaitManyInternal(unsigned int
const*, unsigned int const*, unsigned int, unsigned long, unsigned int*,
mojo::system::HandleSignalsState*) () at /lib64/libQt5WebEngineCore.so.5
#3  0x7f3afaa1498c in
mojo::system::Core::WaitMany(mojo::system::UserPointer,
mojo::system::UserPointer, unsigned int, unsigned long,
mojo::system::UserPointer,
mojo::system::UserPointer) () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f3afaa10de5 in MojoWaitMany () at /lib64/libQt5WebEngineCore.so.5
#5  0x7f3afc08ae47 in
mojo::common::MessagePumpMojo::DoInternalWork(mojo::common::MessagePumpMojo::RunState
const&, bool) () at /lib64/libQt5WebEngineCore.so.5
#6  0x7f3afc08b07e in
mojo::common::MessagePumpMojo::DoRunLoop(mojo::common::MessagePumpMojo::RunState*,
base::MessagePump::Delegate*) () at /lib64/libQt5WebEngineCore.so.5
#7  0x7f3afc08b1b9 in