After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 410324 - configure doesn't find gpg2
configure doesn't find gpg2
Status: RESOLVED FIXED
Product: seahorse
Classification: Applications
Component: general
git master
Other All
: Normal normal
: 1.0.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2007-02-21 09:29 UTC by christopher taylor
Modified: 2007-08-21 00:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Attempt one (460 bytes, patch)
2007-02-21 16:37 UTC, Adam Schreiber
none Details | Review
Now one that builds (1.14 KB, patch)
2007-02-21 16:43 UTC, Adam Schreiber
none Details | Review
updated patch (1.07 KB, patch)
2007-02-22 08:32 UTC, christopher taylor
none Details | Review

Description christopher taylor 2007-02-21 09:29:38 UTC
Please describe the problem:
gnupg 2.0.x installs bin/gpg2 instead of bin/gpg. Since seahorse supports the 2.0 version it should consider the different name.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Adam Schreiber 2007-02-21 16:37:12 UTC
Created attachment 83049 [details] [review]
Attempt one

Please try this patch.  I don't have gpg2 installed to test it.  If it doesn't work let me know, some messing with the sed lines may be required.
Comment 2 Adam Schreiber 2007-02-21 16:43:36 UTC
Created attachment 83050 [details] [review]
Now one that builds

Sorry, the last one didn't even build.  Here's one that builds and with changes to the sed magic.
Comment 3 Stef Walter 2007-02-21 16:44:08 UTC
Something else to check, perhaps you already have ... When we actually run gpg, is the executable name ever hard coded? 
Comment 4 Adam Schreiber 2007-02-21 16:56:45 UTC
I think as long as gpgme_get_engine_info returns the correct information we're good to go.  I'm not sure if we need to bump the minimum gpgme version for this to work properly.
Comment 5 christopher taylor 2007-02-22 08:32:02 UTC
Created attachment 83095 [details] [review]
updated patch

The patch on comment 2 didn't work for, but this one does.
Comment 6 Adam Schreiber 2007-02-22 12:33:36 UTC
Given this link, I'm thinking that currently gpgme doesn't work with gpg2. 

http://www.gossamer-threads.com/lists/gnupg/gpa/38078

Christopher,  Does your new patch just allow configure to proceed or does seahorse behave normally when run?
Comment 7 christopher taylor 2007-02-22 15:29:02 UTC
You're right Adam, gpgme doesn't yet support gpg2 and seahorses crashes on startup.
Comment 8 Adam Schreiber 2007-02-22 16:11:36 UTC
If you add a symbolic link from /usr/bin/gpg2 to /usr/bin/gpg does everything work properly?
Comment 9 christopher taylor 2007-02-22 17:20:57 UTC
It keeps crashing. Here comes a stacktrace:

Distribution: Slackware Slackware 10.1.0
Gnome Release: 2.17.91 2007-02-19 (GNOME.Org)
BugBuddy Version: 2.17.3

System: Linux 2.6.20 #53 PREEMPT Mon Feb 5 23:42:05 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 23650304 vsize: 23650304 resident: 7495680 share: 6332416 rss: 7495680 rss_rlim: 4294967295
CPU usage: start_time: 1172162667 rtime: 6 utime: 5 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/local/bin/seahorse'

Using host libthread_db library "/lib/tls/i686/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1223969088 (LWP 3483)]
0xb7f33410 in __kernel_vsyscall ()

Thread 1 (Thread -1223969088 (LWP 3483))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/libc.so.6
  • #6 abort
    from /lib/tls/i686/libc.so.6
  • #7 IA__g_logv
    at gmessages.c line 497
  • #8 IA__g_log
    at gmessages.c line 517
  • #9 IA__g_return_if_fail_warning
  • #10 init_gpgme
    at seahorse-pgp-source.c line 87
  • #11 seahorse_pgp_source_init
    at seahorse-pgp-source.c line 263
  • #12 IA__g_type_create_instance
    at gtype.c line 1569
  • #13 g_object_constructor
    at gobject.c line 1041
  • #14 IA__g_object_newv
    at gobject.c line 937
  • #15 IA__g_object_new_valist
    at gobject.c line 981
  • #16 IA__g_object_new
    at gobject.c line 795
  • #17 seahorse_pgp_source_new
    at seahorse-pgp-source.c line 1073
  • #18 seahorse_context_new
    at seahorse-context.c line 218
  • #19 main
    at main.c line 82
  • #0 __kernel_vsyscall

Comment 10 Stef Walter 2007-03-10 16:57:02 UTC
As as been determined on the seahorse-devel mailing list, seahorse doesn't support GPG2. This is because a GPG library called 'gpgme' which seahorse uses doesn't support it. 
Comment 11 Adam Schreiber 2007-03-15 13:59:51 UTC
Chris, I just built gpg-2.0.3 and all it's dependencies on Slackware 11.0.  I symlinked gpg2 to gpg and everything appears to be working properly with the exception that it's complaining about the validity of my keyring.

Could you upgrade to the latest gpg2 and all of it's dependencies(pth, libgpg-error, libassuan, libksba) and let us know if you're still having this crash?

----8<-----
an mpi of size 0 is not allowed
an mpi of size 0 is not allowed
gpg: keyring_get_keyblock: read error: Invalid packet
gpg: keyring_get_keyblock failed: Invalid keyring
gpg: failed to rebuild keyring cache: Invalid keyring
gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model
an mpi of size 0 is not allowed
an mpi of size 0 is not allowed
gpg: keyring_get_keyblock: read error: Invalid packet
gpg: keydb_get_keyblock failed: Invalid keyring
gpg: validate_key_list failed
----8<-----
Comment 12 christopher taylor 2007-03-16 14:11:16 UTC
Hi,

I just installed:
libgcrypt 1.2.4
libassuan 1.0.1 trunk
gpgme 1.1.5 trunk
gnupg 2.0.4 trunk
libgpg-error 1.6 trunk
libkasba 1.0.2 trunk
opencdk 0.5.13
gnutls 1.6.1

I had to create the symlink you mentioned to compile gpgme and to delete it to compile seahorse. Unfortunatly I still get the same error. I installed all packages from source.
Comment 13 Gilles Dartiguelongue 2007-08-20 22:35:55 UTC
this is fixed since bug #444259 is closed right ?
Comment 14 Adam Schreiber 2007-08-21 00:04:04 UTC
Should be.