[kleopatra] [Bug 355298] New: Outlook 2013 hangs after Kleopatra 2.2.0 asks for passphrase when performing signing, encryption, verification, etc.

via KDE Bugzilla bugzilla_noreply at kde.org
Fri Nov 13 17:24:27 GMT 2015


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

            Bug ID: 355298
           Summary: Outlook 2013 hangs after Kleopatra 2.2.0 asks for
                    passphrase when performing signing, encryption,
                    verification, etc.
           Product: kleopatra
           Version: git master
          Platform: MS Windows
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: aheinecke at intevation.de
          Reporter: guzjd at hotmail.com
                CC: kdepim-bugs at kde.org, mutz at kde.org

Installed Kleopatra as part of GPG4Win (vice Gnu Privacy Assistant - GPA).
Kleopatra component allowed me to perform signing and encryption for some time,
but has stopped working in the past few months. When attempting to sign,
encrypt, or verify messages, I am prompted for a passphrase which I enter and
upon submission of the passphrase Outlook 2013 message composition screen hangs
immediately (Not Responding in title bar). I initially thought the issue was
with GpgOL, but found if I terminate Kleopatra using the task manager, I get
control of Outlook again, but have to log out and back in to reproduce (or
terminate other running processes associated with Gpg4win). I upgraded to
latest release of GPG4Win 2.2.6 and found that the issue persisted with
Kleopatra 2.2.0.  I am able to work around this by removing and reinstalling
Gpg4win and using GPA but wanted to take the time to report this to see if
others are affected. I have captured some logs for Kleopatra and other
components in case the problem lies with another application component.

Reproducible: Always

Steps to Reproduce:
1. Create a new message in Outlook 2013. 
2. Click the GpgOL tab in the ribbon bar.
3. Attempt to sign or encrypt a message.
4. Enter and submit passphrase.


Actual Results:  
Outlook message editor screen hangs (Outlook message displays Not Responding in
Title Bar).

Expected Results:  
Message should be signed or encrypted and display public key in message body.

chan_000005FC -> OK GPG UI server (Kleopatra/2.2.0-git49bbf03 (2015-08-20))
ready to serve
chan_000005FC <- GETINFO pid
chan_000005FC -> D 5024
chan_000005FC -> OK
chan_000005FC <- OPTION window-id=1
chan_000005FC -> OK
chan_000005FC <- RESET
chan_000005FC -> OK
chan_000005FC <- [error: Resource temporarily unavailable]
chan_000005FC <- SESSION 1 GpgOL
chan_000005FC -> OK
chan_000005FC <- SENDER -- <sender e-mail omitted>
chan_000005FC -> # ok, parsed as "<sender e-mail omitted>"
count_signing_certificates(  OpenPGP, <sender e-mail omitted> ) ==  1
count_signing_certificates(      CMS, <sender e-mail omitted> ) ==  0
chan_000005FC -> S PROTOCOL OpenPGP
chan_000005FC -> OK
chan_000005FC <- INPUT FD=1472
KDPipeIODevice::doOpen (0x45eb4e8): created reader (0x45f2290) for fd -1
chan_000005FC -> OK
chan_000005FC <- OUTPUT FD=1416
KDPipeIODevice::doOpen (0x45eb178): created writer (0x45f4af0) for fd -1
chan_000005FC -> OK
chan_000005FC <- SIGN --protocol=OpenPGP
0x45d9270: KDPipeIODevice::readData: data=0x45d0ac0, maxSize=512
KDPipeIODevice::Private::startReaderThread(): locking reader (CONSUMER THREAD)
KDPipeIODevice::Private::startReaderThread(): locked reader (CONSUMER THREAD)
KDPipeIODevice::Private::startReaderThread(): waiting for hasStarted (CONSUMER
THREAD)
0x45f2290: Reader::run: started
0x45f2290: Reader::run: rptr=0, wptr=0 -> numBytes=4096
0x45f2290: Reader::run: trying to read 4096 bytes from fd -1
KDPipeIODevice::Private::startReaderThread(): returned from hasStarted
(CONSUMER THREAD)
0x45d9270: KDPipeIODevice::readData: try to lock reader (CONSUMER THREAD)
0x45d9270: KDPipeIODevice::readData: locked reader (CONSUMER THREAD)
0x45d9270: KDPipeIODevice::readData: waiting for bufferNotEmptyCondition
(CONSUMER THREAD)

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



More information about the Kdepim-bugs mailing list