1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#264404: seahorse: freeze when using gpg

    From Jose Carlos Garcia Sogo@1:229/2 to Laurent Hausermann on Thu Aug 12 14:00:16 2004
    From: [email protected]

    On Sun, Aug 08, 2004 at 08:13:50PM +0200, Laurent Hausermann wrote:
    Package: seahorse
    Version: 0.7.3-5
    Severity: important

    Seahorse seems to freeze when using gpg to have an action over a key.
    For exemple, if I choose a friend of mine key, push the "Sign" Button and validate my action, apps freeze, I have no UI feedback and must kill the
    app.
    Please note, that I am able to generate a new key pair.

    I am running seahorse on a existing gpg installation, but I made no customizations
    on it...

    Can you reproduce the bug? I mean, does this happen to you every time
    you want to sign a key, or only sometimes?

    I'm thinking that the "hang" you have seen is due gpg reconstructing
    trust database, which is usually triggered by new keys and keys being
    signed.
    If it happens to you again, don't kill seahorse and check if you have
    a file named ~/.gnupg/trustdb.gpg.lock

    But of couse, this only will seem like a lock if you have a hughe
    public keyring, or you load external public keyrings like Debian one
    (or if your computer is quite slow)

    Is there a "debug" mode, where I could have more output ?

    Not easy. You should recompile both libgpgme6 and seahorse with the
    variable DEB_BUILD_OPTIONS=nostrip. This way you will get all
    symbols, and you can use easily gdb to trace where the bug is.

    Thanks

    --
    Jose Carlos Garcia Sogo
    [email protected]

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.2.5 (GNU/Linux)

    iD8DBQFBG0SpS+BYJZB4jhERArv9AJ9/S5ggeHbg0xi6ZW4n5r4Sg4qi4wCgsvpP /pvs4OWLc3lq1D7yk30zvUw=
    =oZBF
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Laurent Hausermann@1:229/2 to All on Sat Aug 14 14:30:12 2004
    From: [email protected]

    Can you reproduce the bug? I mean, does this happen to you every time
    you want to sign a key, or only sometimes?

    Everytime, I want to sign a key I have imported from a key server, I got
    this "hang"


    I'm thinking that the "hang" you have seen is due gpg reconstructing
    trust database, which is usually triggered by new keys and keys being
    signed.
    If it happens to you again, don't kill seahorse and check if you have
    a file named ~/.gnupg/trustdb.gpg.lock

    I have no trustdb.gpg.lock

    But of couse, this only will seem like a lock if you have a hughe
    public keyring, or you load external public keyrings like Debian one
    (or if your computer is quite slow)

    My personal trust database is quite small... To be sure I made the test :

    # mv $HOME/.gpg $HOME/GPG
    Then I run seahorse, regenerate a key (DSA ElGamal 2048 bit) and next I
    have imported a key with gpg command line from wwwkeys.pgp.net
    I run again seahorse, and sign the key I have imported.
    Seahorse "hang" (no response from the app, and empty widgets), looking
    at the process running I have :
    "hauser 17240 1 0 14:09 pts/0 00:00:00 gpg --comment
    --status-fd 17 --no-tty --charset utf8 --command-fd 18 --verbose
    --with-colons -u YYYYY --edit-key -- XXXXXX"

    After a kill on seahorse, the key is not signed ....

    If I could do more debug ... Thanks !

    Laurent

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
    <HTML>
    <HEAD>
    <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
    <META NAME="GENERATOR" CONTENT="GtkHTML/3.0.10">
    </HEAD>
    <BODY>
    <BLOCKQUOTE TYPE=CITE>
    <PRE><FONT COLOR="#737373"><I> Can you reproduce the bug? I mean, does this happen to you every time
    &nbsp; you want to sign a key, or only sometimes?</I></FONT></PRE> </BLOCKQUOTE>
    Everytime, I want to sign a key I have imported from a key server, I got this &quot;hang&quot;<BR>

    <BLOCKQUOTE TYPE=CITE>
    <PRE><FONT COLOR="#737373"><I> I'm thinking that the &quot;hang&quot; you have seen is due gpg reconstructing
    trust database, which is usually triggered by new keys and keys being
    signed.
    If it happens to you again, don't kill seahorse and check if you have
    &nbsp; a file named ~/.gnupg/trustdb.gpg.lock</I></FONT></PRE>
    </BLOCKQUOTE>
    I have no trustdb.gpg.lock
    <BLOCKQUOTE TYPE=CITE>
    <PRE><FONT COLOR="#737373"><I> But of couse, this only will seem like a lock if you have a hughe
    public keyring, or you load external public keyrings like Debian one
    (or if your computer is quite slow)</I></FONT></PRE>
    </BLOCKQUOTE>
    <PRE>My personal trust database is quite small... To be sure I made the test :</PRE>
    # mv $HOME/.gpg $HOME/GPG<BR>
    Then I run seahorse, regenerate a key (DSA ElGamal 2048 bit) and next I have imported a key with gpg command line from wwwkeys.pgp.net<BR>
    I run again seahorse, and sign the key I have imported. <BR>
    Seahorse &quot;hang&quot; (no response from the app, and empty widgets), looking at the process running&nbsp; I have : <BR>
    &quot;hauser&nbsp;&nbsp; 17240&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp; 0 14:09 pts/0&nbsp;&nbsp;&nbsp; 00:00:00 gpg --comment&nbsp; --status-fd 17 --no-tty --charset utf8 --command-fd 18 --verbose --with-colons -u YYYYY&nbsp; --edit-key -- XXXXXX&quot;<BR>

    After a kill on seahorse, the key is not signed ....<BR>

    If I could do more debug ... Thanks !<BR>

    Laurent
    </BODY>
    </HTML>

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)