[kontact] [Bug 368252] New: Crash during KMail usage

2016-09-04 Thread Hatl via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368252

Bug ID: 368252
   Summary: Crash during KMail usage
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: h...@gmx.net

Application: kontact (5.1.3)

Qt Version: 5.5.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.0-36-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:

not 100% sure, but i think it crashed while using the jump window

The crash can be reproduced sometimes.

-- 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 0x7f87e7a49940 (LWP 3993))]

Thread 20 (Thread 0x7f871e85d700 (LWP 4064)):
#0  0x7f87de5f93d7 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f87de5fb8cb in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f87de5fc2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f87de5fc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f87e592ea9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f87e58d5dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f87e56f28a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f87e56f784e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f87dee266fa in start_thread (arg=0x7f871e85d700) at
pthread_create.c:333
#9  0x7f87e4df7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7f871700 (LWP 4061)):
#0  0x7f87de640ae4 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f87de5fb920 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f87de5fc2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f87de5fc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f87e592ea9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f87e58d5dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f87e56f28a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f87e56f784e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f87dee266fa in start_thread (arg=0x7f871700) at
pthread_create.c:333
#9  0x7f87e4df7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7f8740fb3700 (LWP 4032)):
#0  0x7f87e4de79cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f87de63f740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f87de5fbe84 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f87de5fc340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f87de5fc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f87e592ea9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f87e58d5dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f87e56f28a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f87e56f784e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f87dee266fa in start_thread (arg=0x7f8740fb3700) at
pthread_create.c:333
#10 0x7f87e4df7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7f87417b4700 (LWP 4030)):
#0  0x7f87de5d0220 in g_ptr_array_set_size () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f87de5fb881 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f87de5fc2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f87de5fc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f87e592ea9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f87e58d5dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f87e56f28a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f87e56f784e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f87dee266fa in start_thread (arg=0x7f87417b4700) at
pthread_create.c:333
#9  0x7f87e4df7b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7f8742ffd700 (LWP 4028)):
#0  0x7f87de5f9430 in ?? () from /lib/x86_

[akregator] [Bug 368242] Default feeds still use kde-apps and kde-look

2016-09-04 Thread Laurent Montel via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368242

--- Comment #4 from Laurent Montel  ---
(In reply to Jonathan Riddell from comment #0)
> The default feeds still use kde-apps.org and kde-look.org, these websites
> are deprecated.  The feeds should be updated to use store.kde.org and
> kconf_update or whatever magic being used to remove them for existing uses.
> 
> Reproducible: Always

Do you know url for rss or rdf file ?
I was not able to find it

-- 
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

2016-09-04 Thread Laurent Montel via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368242

--- Comment #3 from Laurent Montel  ---
Git commit 83a20274c8bdbb08d4f27036a1c80854b4cf9e8d by Montel Laurent.
Committed on 05/09/2016 at 04:50.
Pushed by mlaurent into branch 'master'.

Remove obsolete website (and rdf is broken)

M  +0-5src/akregator_part.cpp

http://commits.kde.org/akregator/83a20274c8bdbb08d4f27036a1c80854b4cf9e8d

-- 
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

2016-09-04 Thread Laurent Montel via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368242

--- Comment #2 from Laurent Montel  ---
Git commit 54e6628bcf1bef800eff1b68f88a517e888627db by Montel Laurent.
Committed on 05/09/2016 at 04:49.
Pushed by mlaurent into branch 'Applications/16.08'.

Remove obsolete website (and rdf is broken)

M  +0-5akregator/src/akregator_part.cpp

http://commits.kde.org/kdepim/54e6628bcf1bef800eff1b68f88a517e888627db

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

[kmail2] [Bug 362710] Message list view does not show any text (invisible sender, subject, date etc)

2016-09-04 Thread SuperMarioSF via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362710

SuperMarioSF  changed:

   What|Removed |Added

 CC||qq9977553...@126.com

--- Comment #13 from SuperMarioSF  ---
BTW, there are another problem happend with this one:
KMail startup screen have a introduce page on mail vieweing frame, but it
should be replaced when clicking a mailbox folder. It doesn't being replaced. I
found a way to solve this: 
Settings -> Configure KMail -> Apparence -> Layout,
Mail previewing panel, selecting 'Display beside mail list'. 
BTW, I am using a Chinese translation, So things above may be different with
English, and I cannot change to English because there is no language override
option in Help menu.
After that I finally got access to mail list, but it just a blank. Yup, that is
current issue.

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

[kaddressbook] [Bug 365800] Since I moved to Kubuntu 16.04, kaddressbook crashes.

2016-09-04 Thread Ilpo Kantonen via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=365800

--- Comment #4 from Ilpo Kantonen  ---
The crash occurred also with Tasklist application when started from Kontact.
Maybe same reason to crash?

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

[kaddressbook] [Bug 365800] Since I moved to Kubuntu 16.04, kaddressbook crashes.

2016-09-04 Thread Ilpo Kantonen via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=365800

--- Comment #3 from Ilpo Kantonen  ---
Kmail works fine with contacts. When I write a new email Kmail finds contacts
from addressbook and don't crash.

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

[kaddressbook] [Bug 365800] Since I moved to Kubuntu 16.04, kaddressbook crashes.

2016-09-04 Thread Ilpo Kantonen via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=365800

--- Comment #2 from Ilpo Kantonen  ---
In my case I have upgraded Kubuntu 14.10 -> 16.04.1 if that has some role to
this crash. The 14.10 is not LTS and maybe upgrading from it to 16.04.1 causes
problems to Kaddressbook?

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

[kaddressbook] [Bug 353567] KAddress Book custom fields don't work properly (url data type)

2016-09-04 Thread Tore Havn via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=353567

--- Comment #3 from Tore Havn  ---
I looked through the bug list, and I think all the following unconfirmed bugs
are related to the same problem(s):

https://bugs.kde.org/show_bug.cgi?id=340316
https://bugs.kde.org/show_bug.cgi?id=339959
https://bugs.kde.org/show_bug.cgi?id=299704
https://bugs.kde.org/show_bug.cgi?id=299853
https://bugs.kde.org/show_bug.cgi?id=300087

Additionally, this feature request could probably be implemented easily while
fixing this:
https://bugs.kde.org/show_bug.cgi?id=317774

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

[kaddressbook] [Bug 353567] KAddress Book custom fields don't work properly (url data type)

2016-09-04 Thread Tore Havn via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=353567

Tore Havn  changed:

   What|Removed |Added

 CC||tore.h...@gmail.com

--- Comment #2 from Tore Havn  ---
I have the same (similar?) problem, I think.

I'm running KAddressbook v5.1.3 on Kubuntu 16.04.

My use case has been to try and make a global custom date field. However, I am
constantly running into lots of little bugs surrounding custom fields.

Reproducible: Always

Steps to reproduce:

1. Create a new user, give it a name and create a new Custom Field, setting the
Type to Date and not checking the 'use for all contacts'. This seems to work,
and I input a date and close the contact view.

2. Edit the contact and add one more date field. Still seems to work fine.

3. Make a new contact and give it a name. Everything is still fine with the
first user.

4. Edit the first contact and make a Custom Field of type Date and check 'use
for all contacts', put in a date and save the contact. In the view pane
something looks strange with the new date field (it is formated differently
than the first two). Go back to the contact and the Custom Fields tab. Select
the third custom field and click Edit. In the Edit Custom Field box, the Title
has now been set to the Title of the first custom field, and the Type to Text.

5. Make a new contact, give it a name and save it. When checking the first
contact now, both the first and third custom fields have their Title's set to
the Custom Fields' ID, and their Types have been set to Text. The 'use for all
contacts' field has also been unchecked for both.

6. Furthermore, and Custom Field for all contacts has its Type set to Text when
trying to edit it from another contact.

Finally, I've tried to export my contacts and putting them all in one file.
When looking at the vcf-file, I can see the Custom Fields, but all the values
are formated as if they are Text fields, and there is no information about the
Type of the fields.

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

[kmail2] [Bug 368244] some PGP messages show: Not enough information to check signature validity

2016-09-04 Thread kolAflash via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368244

--- Comment #1 from kolAflash  ---
= Correction =

I still get the message after importing the key.

So:
1. KMail should provide more details about what's going wrong in general.
2. Fix this specific bug.

If you tell me where I can get some debug output (KMail doesn't seem to have an
"-v" verbose option) I'll happily provide it!

Maybe related:
https://bugs.kde.org/show_bug.cgi?id=323168

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

[kmail2] [Bug 368244] some PGP messages show: Not enough information to check signature validity

2016-09-04 Thread kolAflash via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368244

kolAflash  changed:

   What|Removed |Added

Summary|some PGP messages without   |some PGP messages show: Not
   |pubic key: Not enough   |enough information to check
   |information to check|signature validity
   |signature validity  |

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

[kmail2] [Bug 368244] New: some PGP messages without pubic key: Not enough information to check signature validity

2016-09-04 Thread kolAflash via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368244

Bug ID: 368244
   Summary: some PGP messages without pubic key: Not enough
information to check signature validity
   Product: kmail2
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de

This is being displayed on some messages for which I don't have a public key:

"Not enough information to check signature validity."
Screenshot: http://picpaste.com/not_enough.png

German:
"Es sind nicht genügend Informationen zur Überprüfung der Signatur vorhanden."

Instead KMail should tell me that it misses the public key and give me the key
id of that key, so I can start searching for it.

Thunderbird+Enigmail handle the same email much better, telling me "Unverified
signature" and then there's a details button giving me the public key id.
(there's no details button in KMail)

Here's a copy of such an email without private details.
If someone needs an original copy for debugging (without blackened stuff) send
me an email and I'll send it to you. I just don't want to make the whole email
completly public because it wasn't written by me.

--
Return-Path: 
Delivered-To: [...]
Received: from localhost (cubox [127.0.0.1])
by [...] (Postfix) with ESMTP id [...]
for [...]; Tue,  9 Aug 2016 [...]
Received: from [...] ([127.0.0.1])
by localhost ([...] [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id [...] for [...]
Tue,  9 Aug 2016 [...]
Received: from [...] ([...] [[...]])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by [...] (Postfix) with ESMTPS id [...]
for [...]; Tue,  9 Aug 2016 [...]
Received: from [...] ([...] [[...]])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by [...] (Postfix) with ESMTPS id [...];
Tue,  9 Aug 2016 [...]
Received: from [...] (localhost [127.0.0.1])
by [...] (Postfix) with ESMTP id [...];
Tue,  9 Aug 2016 [...]
X-Original-To: mitglie...@lists.fux-eg.org
Delivered-To: [...]
Received: from [...] ([...]
 [[...]])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by h07.hostsharing.net (Postfix) with ESMTPS id 5227AC9436;
 Tue,  9 Aug 2016 [...]
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by [...] (Postfix) with ESMTPS id [...];
 Tue,  9 Aug 2016 [...]
Received: from [192.168.1.4] ([[...]]) by mail.gmx.com [...]
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
In-Reply-To: [...]
Date: Tue, 9 Aug 2016 [...]
Message-Id: [...]
References: [...]
To: [...]
X-Mailer: Apple Mail (2.1510)
X-Provags-ID: [...]
X-UI-Out-Filterresults: notjunk:[...]
Subject: [...]
X-BeenThere: mitglie...@lists.fux-eg.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Mitglieder der Fux Genossenschaft 
List-Unsubscribe: ,
 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: ,
 
From: [...]
Reply-To: [...]
Cc: fux Mitgliederliste 
Content-Type: multipart/mixed; boundary="===[...]=="
Errors-To: mitglieder-boun...@lists.fux-eg.org
Sender: "Mitglieder" 



--===[...]==
Content-Type: multipart/signed; boundary="Apple-Mail=_[...]";
protocol="application/pgp-signature"; micalg=pgp-sha512


--Apple-Mail=_[...]
Content-Type: multipart/alternative;
boundary="Apple-Mail=_[...]


--Apple-Mail=_[...]
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252

[...]
> ___
> Mitglieder mailing list
> mitglie...@lists.fux-eg.org
> http://lists.fux-eg.org/listinfo/mitglieder


--Apple-Mail=_[...]
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=windows-1252


[...]=




___=
Mitglieder mailing listmailto:mitglie...@lists.fux-eg.org";>mitglie...@lists.fux-eg.orghttp://lists.fux-eg.org/listinfo/mitglieder=

--Apple-Mail=_[...]--

--Apple-Mail=_[...]
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-BEGIN PGP SIGNATURE-
Comment: GPGTools - https://gpgtools.org

[...]
-END PGP SIGNATURE-

--Apple-M

[akregator] [Bug 368242] Default feeds still use kde-apps and kde-look

2016-09-04 Thread Laurent Montel via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368242

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
I will update it tomorrow morning.
Thanks for info. no time this night :)

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

[kleopatra] [Bug 322664] Result of file signature verification is misleading/confusing

2016-09-04 Thread kolAflash via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=322664

kolAflash  changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

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

[akregator] [Bug 368242] New: Default feeds still use kde-apps and kde-look

2016-09-04 Thread Jonathan Riddell via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368242

Bug ID: 368242
   Summary: Default feeds still use kde-apps and kde-look
   Product: akregator
   Version: unspecified
  Platform: Other
   URL: http://store.kde.org
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: j...@jriddell.org

The default feeds still use kde-apps.org and kde-look.org, these websites are
deprecated.  The feeds should be updated to use store.kde.org and kconf_update
or whatever magic being used to remove them for existing uses.

Reproducible: Always

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

[Akonadi] [Bug 364045] akonadi_imap_resource crashes synchronizing with imap.kabelmail.de

2016-09-04 Thread via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=364045

--- Comment #2 from franz-joseph.barth...@kabelmail.de ---
Dear Daniel Vratil,

I am a long term KDE user with  some serious problems to set up a special IMAP 
account properly with KMail, see your solution to
https://bugs.kde.org/show_bug.cgi?id=364045
and the next problem behind the first bug, see
https://bugs.kde.org/show_bug.cgi?id=366238

Searching for answers on the web, I got in contact with your blog.
Especially with 
http://www.dvratil.cz/2016/01/kde-pim-still-alive-and-rocking/.

There, you close the article with
"so if you like KDE (PIM) and would like to help us, let’s talk!"

Ok, here I am.
I think that KDE needs a native PIM solution, i.e. KDEPIM.
And I am willing to contribute beyond my personal interest.

Being a professor at a German university,
see also http://www.bauwesen.tu-dortmund.de/nmi/en/chair/index.html,
I am involved in software development
(Fortran, Matlab for Finite Element Method),
I know the problems of software development very well.
Especially in small or even very small groups.

Thus, being overloaded myself, I could not contribute to your daily 
development tasks. Nevertheless, I may contribute at some other place.

What is needed? Today, I could only mention some observations.

If someting is not working with KDEPIM, there are actually only few hints 
about the nature of the problem, i.e.
- wrong local configuration of KDEPIM,
- problems with the e-mail server of the provider
- really a bug in KDEPIM.
It is hardly possible to choose the correct category.

Is it possible to set up a white and black list naming providers or server 
software which are known to work or fail to work?

Is it possible to ask the community in some kind of review reporting positive 
and negative experience?

Would it be helpful to set up a list of test accounts (different providers and 
different server software) where some scenarios are frequently tested?

Ok. Who should do it?
But first of all, what are the best means to optimize the developement (and bug 
tracking) process.

So, I am willing to talk.

Best regards
Franz-Joseph Barthold


Am Sonntag, 12. Juni 2016, 09:46:35 CEST schrieben Sie:
> https://bugs.kde.org/show_bug.cgi?id=364045
> 
> Daniel Vrátil  changed:
> 
>What|Removed |Added
> 
> Version Fixed In||16.04.3
>  Status|UNCONFIRMED |RESOLVED
>   Latest Commit||http://commits.kde.org/kima
>||p/8933e1dcfe7686683c5d804b9
>||68dfc4a3af40f34
> 
>  Resolution|--- |FIXED
> 
> --- Comment #1 from Daniel Vrátil  ---
> Git commit 8933e1dcfe7686683c5d804b968dfc4a3af40f34 by Daniel Vrátil.
> Committed on 11/06/2016 at 09:17.
> Pushed by dvratil into branch 'Applications/16.04'.
> 
> Fix crash when server returns non-standard EXPUNGE response
> 
> Apparently some servers don't mention "EXPUNGE" in untagged EXPUNGE
> response. This wasn't handled correctly due to a typo in response
> length check. The code no longer crashes in such case, but will now
> print "Unhandled response" warning, which is OK, since we don't
> handle results of the EXPUNGE command anyway.
> FIXED-IN: 16.04.3
> 
> M  +1-0autotests/CMakeLists.txt
> A  +89   -0autotests/expungejobtest.cpp [License: GPL (v2+)]
> M  +1-1src/expungejob.cpp
> 
> http://commits.kde.org/kimap/8933e1dcfe7686683c5d804b968dfc4a3af40f34

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

[Akonadi] [Bug 366238] KMail does not fetch mails from imap.kabelmail.de

2016-09-04 Thread via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=366238

--- Comment #1 from franz-joseph.barth...@kabelmail.de ---
Actually opensuse tumbleweed has been updated to KDE Applications 16.08
including KDEPIM.

The reported bug is still existing.

Please advice me what kind of additional information are needed.

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

[kmail2] [Bug 337806] Unable to click on links in "invitations" encrypted with GnuPG

2016-09-04 Thread L via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=337806

--- Comment #7 from L <1passw...@posteo.de> ---
Yes, the inbound email messages get encrypted by a S/MIME milter on the server
(without signing it, obviously) against a stored public key.

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

[Akonadi] [Bug 368096] Unable to load ical over http

2016-09-04 Thread Laurent Montel via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368096

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |NEEDSINFO
   Version Fixed In||5.3.1
 CC||mon...@kde.org

--- Comment #2 from Laurent Montel  ---
Finally it's fixed in 5.3.1

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

[kmail2] [Bug 368231] kmail crashes while downloading from imap server

2016-09-04 Thread Laurent Montel via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368231

Laurent Montel  changed:

   What|Removed |Added

 CC||dvra...@kde.org,
   ||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
it's still a problem with messagelist cache.
I add dan

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

[kmail2] [Bug 368231] New: kmail crashes while downloading from imap server

2016-09-04 Thread via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368231

Bug ID: 368231
   Summary: kmail crashes while downloading from imap server
   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: muzhm...@centrum.sk

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 (20160812) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Open kmail.  Checking mail.
Using a gmail account via imap.
Mails seem to randomly disappear from folders and often kmail closes
unexpectedly.

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 0x7ffaf111b940 (LWP 3304))]

Thread 42 (Thread 0x7ffa266fa700 (LWP 6662)):
#0  0x7ffaeded2a7d in read () at /lib64/libc.so.6
#1  0x7ffae358cc70 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ffae3549b06 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ffae3549fd4 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7ffae354a14c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7ffaeea19aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7ffaee9c176a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7ffaee7e73b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7ffaee7ec2d8 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7ffae3d6d474 in start_thread () at /lib64/libpthread.so.0
#10 0x7ffaededf3ed in clone () at /lib64/libc.so.6

Thread 41 (Thread 0x7ffa31264700 (LWP 6651)):
#0  0x7ffaeded6a1d in poll () at /lib64/libc.so.6
#1  0x7ffae354a036 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ffae354a14c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ffaeea19aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ffaee9c176a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ffaee7e73b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ffaee7ec2d8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7ffae3d6d474 in start_thread () at /lib64/libpthread.so.0
#8  0x7ffaededf3ed in clone () at /lib64/libc.so.6

Thread 40 (Thread 0x7ffa33fff700 (LWP 6617)):
#0  0x7ffaeded6a1d in poll () at /lib64/libc.so.6
#1  0x7ffae354a036 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ffae354a14c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ffaeea19aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ffaee9c176a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ffaee7e73b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ffaee7ec2d8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7ffae3d6d474 in start_thread () at /lib64/libpthread.so.0
#8  0x7ffaededf3ed in clone () at /lib64/libc.so.6

Thread 39 (Thread 0x7ffa9b871700 (LWP 6599)):
#0  0x7ffaeded6a1d in poll () at /lib64/libc.so.6
#1  0x7ffae354a036 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ffae354a14c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ffaeea19aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ffaee9c176a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ffaee7e73b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ffaee7ec2d8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7ffae3d6d474 in start_thread () at /lib64/libpthread.so.0
#8  0x7ffaededf3ed in clone () at /lib64/libc.so.6

Thread 38 (Thread 0x7ffa9c072700 (LWP 6587)):
#0  0x7ffaeded6a1d in poll () at /lib64/libc.so.6
#1  0x7ffae354a036 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ffae354a14c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ffaeea19aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ffaee9c176a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ffaee7e73b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ffaee7ec2d8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7ffae3d6d474 in start_thread () at /lib64/libpthread.so.0
#8  0x7ffaededf3ed in clone () at /lib64/libc.so.6

Thread 37 (Thread 0x7ffab53cd700 (LWP 6572)):
#0  0x7ffaeded2a7d in read () at /lib64/libc.so.6
#1  0x7ffae358cc70 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ffae3549b06 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ffae3549fd4 in  () at