Ticket #1626 (new defect)

Opened 5 months ago

Last modified 4 months ago

Licq (SVN) crashes with Qt4 GUI (SVN) while in GPG passphrase dialog

Reported by: root_42 Owned by:
Priority: high Milestone: 1.3.6
Component: qt4-gui Version: devel
Keywords: Cc:

Description

I think licq crashed while displaying the passphrase dialog for GPG. I was away for half an hour, and then licq had crashed.

Attachments

licq.backtrace (2.1 kB) - added by root_42 5 months ago.
Backtrace
licq.backtrace.gdb (7.4 kB) - added by root_42 5 months ago.
GDB Backtrace
licq.debug_rw_mutex (192 bytes) - added by root_42 4 months ago.
mutex debug

Change History

Changed 5 months ago by root_42

Backtrace

Changed 5 months ago by root_42

GDB Backtrace

  Changed 5 months ago by root_42

  • version changed from 1.3.5 to devel
  • component changed from None to qt4-gui

follow-up: ↓ 3   Changed 4 months ago by root_42

  • priority changed from normal to high

Yup, this is definitely reproduceable. This always happens when the passphrase dialog is not answered quickly enough. I guess it happens when some other event is coming in or something. Friend of mine has the same problem with a slightly older licq svn version.

in reply to: ↑ 2 ; follow-up: ↓ 4   Changed 4 months ago by Crazy_Hopper

Replying to root_42:

Yup, this is definitely reproduceable.

Since you say it's definitely reproducible, and backtrace shows that it's locking-the-locked problem, we're gonna need quite thorough step-by-step way to reproduce it. Please provide us with one. ;-)

in reply to: ↑ 3   Changed 4 months ago by root_42

Replying to Crazy_Hopper:

Replying to root_42:

Yup, this is definitely reproduceable.

Since you say it's definitely reproducible, and backtrace shows that it's locking-the-locked problem, we're gonna need quite thorough step-by-step way to reproduce it. Please provide us with one. ;-)

Ok. :) First, you and your contact have to use the GPG functionality of Licq. Also you will most probably be using the qt-pinentry passphrase dialog of GPG.

Now, the first time you get a GPG message, qt-pinentry will pop up, called by libgpgme, and ask for the passphrase. Parts of Licq will be blocked during this call.

If you do not answer fast enough -- Segfault! After the first passphrase entry my GPG agent caches the passphrase for quite a while, so that the problem does not show again.

I think that's as detailed as I can get...

Changed 4 months ago by root_42

mutex debug

Note: See TracTickets for help on using tickets.