[Akonadi] [Bug 338658] GMail: Multiple merge candidates, aborting

2014-11-25 Thread Paul Gideon Dann
https://bugs.kde.org/show_bug.cgi?id=338658

--- Comment #13 from Paul Gideon Dann pdgiddie+...@gmail.com ---
Sadly, I've had to abandon KMail for the time being, as either this issue or
something related to it is causing the Akonadi agents for my GMail IMAP to stop
responding. I can retrieve e-mail if I kill and restart them, but they only
last for a couple of minutes before freezing up again. I've had to resort to
the GMail web interface for several months now :(

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[akregator] [Bug 336417] Akregator crashes when being closed

2014-11-25 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=336417

Christoph Feck christ...@maxiom.de changed:

   What|Removed |Added

 CC||ur...@online.ms

--- Comment #27 from Christoph Feck christ...@maxiom.de ---
*** Bug 341101 has been marked as a duplicate of this bug. ***

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


Make the world a better place. Donate to our year end fundraiser 
https://www.kde.org/fundraisers/yearend2014/
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[akregator] [Bug 341101] bug wwhen ending programm akregator

2014-11-25 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=341101

Christoph Feck christ...@maxiom.de changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Christoph Feck christ...@maxiom.de ---


*** This bug has been marked as a duplicate of bug 336417 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[akregator] [Bug 341230] Akregator crashes when opening news feed

2014-11-25 Thread Andrea Iacovitti
https://bugs.kde.org/show_bug.cgi?id=341230

Andrea Iacovitti aiacovi...@libero.it changed:

   What|Removed |Added

 CC||aiacovi...@libero.it

--- Comment #2 from Andrea Iacovitti aiacovi...@libero.it ---
I can reproduce the crash accessing the following url:
http://www.computerworld.com/article/2849002/see-they-can-figure-it-outeventually.html
. Prerequisites are having activated AdBlock's options Enable filters and
Hide filtered images.
I'm sorry, was me that introduce this regression :-(
Good news is this issue have already been fixed in kdelibs 4.14 branch by
commit:

http://quickgit.kde.org/?p=kdelibs.gita=commith=570425a30c008297df09ef48b60486108fcf33e9
that should apply just fine over kdelibs version 4.14.3

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[kmail2] [Bug 341257] New: PGP/MIME broken when ~/.gnupg/gpg.conf contains a comment with Unicode characters

2014-11-25 Thread Thorsten Glaser
https://bugs.kde.org/show_bug.cgi?id=341257

Bug ID: 341257
   Summary: PGP/MIME broken when ~/.gnupg/gpg.conf contains a
comment with Unicode characters
   Product: kmail2
   Version: 4.14.2
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: t.gla...@tarent.de

I have this line in my ~/.gnupg/gpg.conf file:

comment ☃ ЦΤℱ—8 ☕☂☄

I added it because of a Kontact (KMail 2) bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754265 (also, with less
context, https://bugs.kde.org/show_bug.cgi?id=248058). This makes the sending
MUA set the MIME charset of the RFC822 message to UTF-8 instead of ASCII, due
to the Unicode characters in the “Comment” field of the ASCII-armoured PGP
message.

But I just found out that, when I set this, any PGP/MIME message gets broken.

Reproducible: Always

Steps to Reproduce:
1. echo 'comment ☃ ЦΤℱ—8 ☕☂☄' ~/.gnupg/gpg.conf
2. in Kontact, send a PGP/MIME encrypted message to myself
3. be unable to read it (Inline PGP works, as does using fnord as comment,
which I used in “Expected Results” below) because, as you can see, the encoding
is trivially wrong (= gets encoded as =3D3D instead of =3D)

Actual Results:  
From: Thorsten Glaser t.gla...@tarent.de
To: Thorsten Glaser t.gla...@tarent.de
Subject: test pgp/mime
Date: Tue, 25 Nov 2014 16:49:09 +0100
Message-ID: 5676877.o3l2uj2...@tglase.lan.tarent.de
Organization: tarent solutions GmbH
X-KMail-Identity: 624161509
User-Agent: KMail/4.14.2 (Linux/3.16.0-4-amd64; KDE/4.14.2; x86_64; ; )
MIME-Version: 1.0
Content-Type: multipart/encrypted; boundary=nextPart1971662.MmlWDFlsHR;
protocol=application/pgp-encrypted


--nextPart1971662.MmlWDFlsHR
Content-Type: application/pgp-encrypted
Content-Disposition: attachment
Content-Transfer-Encoding: 7Bit

Version: 1
--nextPart1971662.MmlWDFlsHR
Content-Type: application/octet-stream
Content-Disposition: inline; filename=msg.asc
Content-Transfer-Encoding: quoted-printable

-BEGIN PGP MESSAGE-
Version: GnuPG v2
Comment: =3DE2=3D98=3D83=3DC2=3DA0=3DD0=3DA6=3DCE=3DA4=3DE2=3D84=3DB1=3D=
E2=3D80=3D94=3DEF=3DBC=3D98=3DE3=3D80=3D80=3D
=3DE2=3D98=3D95=3DE2=3D98=3D82=3DE2=3D98=3D84

hQIMA4lQwYleuNOzAQ//VYkwBTa1oEEL4Kd8/ErEsRTdW21uk8ee/G2s0DgIPoBJ
n1VV2TRheoG5bBI3K9xLEqMJaizWbdWaV8g3tNZpJB9+oibsBGUyZJO+bym07UnQ
iqMVFJ9iZ3iIAT+byNNVc4//t9MJJtrKg3r5HhcAB+eNPOJw+OFjN4KN+cuCxKE/
6sN0jhIRFaVacjgxiuXA0MbZV3T8vhg1kMrHDBmiV7MApnuxcZ+NBZSCxryHCuDI
31eFxW0wjPpOjTqy6rdtv2C5lEuQSbhFedMHawY0ZTYWwEIAGfKjVayGMCjhvCOa
KrVtSuIE2go05tDHYZhPlprdYlU8RhJ10K4SSp2iHPUnKt1tpQUQupaFFU/07GB4
arqzFpn7sbv8scMXOdSWsBX9u2uJNqqHzq2rAVWUqIK0SOotkqAF0Y+n0VYMajPQ
4MlhX8L40KReSHJVudGVMGiaLb98WYqH/EgSndojD/QjsJ4A2U9rsQumdinkLMfY
ITqP2uNHakHIVehA1XgPl72YggUKPi6WRheau9Jn+eTXh/h0/JKQlQVG/Y7x1VIt
SU7pmz4BeKiLtEvWsD5wRVBrOjoztG9AKu8jyXOq/tUvd4oEeT5McdBm7xsLwF8A
cmGyKR49IrFFa3e0Oe3XwX9G5KsHZrNakI2XjqmQpRQgRpw4afpZB7c7P7mIcifS
wKYBKm6xPdYfRtEoy6eIBJCMHjXcZKXtUZzVqSibMNaGTm4OAbgd/610dZR4Xp8j
lGGqeC/jqvHq7sKhImk56KLl3RRsKQY/JZ1ynIVy8lv0VdsboIniPDloJE5DWB20
6jpww7PAY8LmeqgbpQks8SC3+nYhn2dPcS2q05nIUk9qxA0XJZHiurOL/5hhIwYN
vWA7ec33BCnDGAbjYdfrKjnuUFqyX95FmGRGgW5PHEMuTzDPB1HQJnFKmfDkmQ8h
gtbd7fVw9HospOg+xgJp37viZ9yOqi3tRn9+PNz0cN6R8Kr/ZHK4sD709TM5a/IN
IwIvGCeI70c7W7DS/oMAUoXKht+y2ATxasAZ1O6xP9PLI3AYvac3tF4Ach6Vo/yD
TQ5VxWhvXThhJrCVPgAWGGBX5UFJ9bfVOeNwER6/YRGVUtEzdlGNRzW6siksj1oM
DarovPvbPsePs4ZnHZRwm5ulE31HzMPP
=3D3DOK3b
-END PGP MESSAGE-

--nextPart1971662.MmlWDFlsHR--


Expected Results:  
From: Thorsten Glaser t.gla...@tarent.de
To: Thorsten Glaser t.gla...@tarent.de
Subject: test defused pgp/mime
Date: Tue, 25 Nov 2014 17:06:28 +0100
Message-ID: 2010470.gc506rz...@tglase.lan.tarent.de
Organization: tarent solutions GmbH
X-KMail-Identity: 624161509
User-Agent: KMail/4.14.2 (Linux/3.16.0-4-amd64; KDE/4.14.2; x86_64; ; )
MIME-Version: 1.0
Content-Type: multipart/encrypted; boundary=nextPart23624681.54267B9MrA;
protocol=application/pgp-encrypted


--nextPart23624681.54267B9MrA
Content-Type: application/pgp-encrypted
Content-Disposition: attachment
Content-Transfer-Encoding: 7Bit

Version: 1
--nextPart23624681.54267B9MrA
Content-Type: application/octet-stream
Content-Disposition: inline; filename=msg.asc
Content-Transfer-Encoding: 7Bit

-BEGIN PGP MESSAGE-
Version: GnuPG v2
Comment: fnord

hQIMA4lQwYleuNOzAQ//V7Hst5/CXCoOZPL0nRUgi8yvgEviigKHqtYmJ3gob7NB
gcE35UiLNjiH5uxNIz5saCQgeoH/woAHqNOn2FR2NkBHDh0RfIeD8acyMxplYmwg
4ZrqaR975hTeBX7mNVW4hWn6n/k7qDQO10jijC2oqEOLisDtCJ+na9UR6SUl7IYO
3ZEa4MJk8OMwgkx1q++ZqwYmY0UWYtPfdyd3FfyYvD1F3Ogm9s11XpNzPqcECjQg
Pj4wZ/pfo7ua12Uh67n0YlIxhoi6ONuJr5ar7xsLhsdRv0eDH1sqDHBIZpu79x/G
1IDzDthC9oBU6KJiKQiMaI6pJ9hdQ0Yhzm+eFWoRD96x7BHML8iPiKQt0dqMusE3
qC8scMF2HPt2s7xXRp7/HvyKtgLPqS5Tr2A5YdR4Udki6b4oQ2nQKzyhkbwzROZY
FeqTjP92aAbxZUbaksMZ5N6MQhTKdfqsx5+k/vr6T8GIpvZYzR4yff4BjOhbReus

[Akonadi] [Bug 341261] New: Akonadi start fais because InnoDB: Unable to lock ./ibdata1, error: 11

2014-11-25 Thread skaumo
https://bugs.kde.org/show_bug.cgi?id=341261

Bug ID: 341261
   Summary: Akonadi start fais because InnoDB: Unable to lock
./ibdata1, error: 11
   Product: Akonadi
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: ska...@gmail.com

141125 17:07:44 InnoDB: The InnoDB memory heap is disabled
141125 17:07:44 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141125 17:07:44 InnoDB: Compressed tables use zlib 1.2.8
141125 17:07:44 InnoDB: Using Linux native AIO
141125 17:07:44 InnoDB: Initializing buffer pool, size = 80.0M
141125 17:07:44 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
141125 17:07:44  InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process

[Akonadi] [Bug 341261] Akonadi start fais because InnoDB: Unable to lock ./ibdata1, error: 11

2014-11-25 Thread skaumo
https://bugs.kde.org/show_bug.cgi?id=341261

ska...@gmail.com changed:

   What|Removed |Added

Version|unspecified |4.12

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Akonadi] [Bug 341261] Akonadi start fais because InnoDB: Unable to lock ./ibdata1, error: 11

2014-11-25 Thread skaumo
https://bugs.kde.org/show_bug.cgi?id=341261

ska...@gmail.com changed:

   What|Removed |Added

Version|4.12|1.13.0

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Akonadi] [Bug 282160] akoandi does not delete mails from .local/share/akonadi/file_db_data

2014-11-25 Thread George L . Emigh
https://bugs.kde.org/show_bug.cgi?id=282160

George L. Emigh ab...@georgelemigh.com changed:

   What|Removed |Added

 CC||ab...@georgelemigh.com

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs