Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Apr 2008 20:14:06 -0400
From:      Joe Marcus Clarke <marcus@marcuscom.com>
To:        cokane@freebsd.org
Cc:        gnome@freebsd.org
Subject:   Re: Seahorse issues
Message-ID:  <1207872846.87478.38.camel@shumai.marcuscom.com>
In-Reply-To: <47FD34E8.2000005@FreeBSD.org>
References:  <47FD09AC.2020907@FreeBSD.org> <1207776230.61729.28.camel@shumai.marcuscom.com> <47FD34E8.2000005@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-/yjPDfDlC9x1KoiSwiOi
Content-Type: multipart/mixed; boundary="=-km5TzIBqhRnZBhuU9PqS"


--=-km5TzIBqhRnZBhuU9PqS
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2008-04-09 at 17:28 -0400, Coleman Kane wrote:
> Joe Marcus Clarke wrote:
> > On Wed, 2008-04-09 at 14:23 -0400, Coleman Kane wrote:
> >  =20
> >> I recently updated to GNOME 2.22, and ever since I have not been able =
to=20
> >> have seahorse work, breaking application integration with GPG, etc....
> >>
> >> I filed a bug with the GNOME project, but perhaps someone else is=20
> >> running into this:
> >> http://bugzilla.gnome.org/show_bug.cgi?id=3D527193
> >>    =20
> >
> > They will most likely come back and tell you to get a backtrace with
> > symbols.  It looks like a problem with either missing headers or a
> > missing cast, though.  If I'm right, this would only affect 64-bit
> > platforms.
> >
> > Joe
> >  =20
> Thanks, I pre-empted that by rigging the seahorse build so that it built=20
> with -g -O0, and copied the non-stripped seahorse-agent binary into=20
> /usr/local/bin for my submitted backtrace. Amazingly enough, it turns=20
> out that even if you specify --enable-debug on the configure line, the=20
> installation step still decided to strip the binaries after=20
> installation. nice.
>=20
> Anyhow, there is hopefully enough info in there for them to figure out=20
> what's up (my guess is that the missing cast is the likely culprit, as=20
> it caused similar misbehavior in evolution some time back).

Undo all your seahorse changes, then try this patch to gnome-keyring.

Joe

--=20
PGP Key : http://www.marcuscom.com/pgp.asc

--=-km5TzIBqhRnZBhuU9PqS
Content-Disposition: attachment; filename=patch-library_gnome-keyring-memory.c
Content-Transfer-Encoding: base64
Content-Type: text/x-patch; name=patch-library_gnome-keyring-memory.c;
	charset=ISO-8859-1

LS0tIGxpYnJhcnkvZ25vbWUta2V5cmluZy1tZW1vcnkuYy5vcmlnCTIwMDgtMDQtMTAgMjA6MTI6
NDAuMDAwMDAwMDAwIC0wNDAwDQorKysgbGlicmFyeS9nbm9tZS1rZXlyaW5nLW1lbW9yeS5jCTIw
MDgtMDQtMTAgMjA6MTM6MDguMDAwMDAwMDAwIC0wNDAwDQpAQCAtMTM1LDcgKzEzNSw3IEBAIGdu
b21lX2tleXJpbmdfbWVtb3J5X2FsbG9jIChndWxvbmcgc3opDQogZ3BvaW50ZXINCiBnbm9tZV9r
ZXlyaW5nX21lbW9yeV90cnlfYWxsb2MgKGd1bG9uZyBzeikNCiB7DQotCXJldHVybiBna3Jfc2Vj
dXJlX2FsbG9jX2Z1bGwgKHN6LCAwKTsNCisJcmV0dXJuIGdrcl9zZWN1cmVfYWxsb2NfZnVsbCAo
c3osIEdLUl9TRUNVUkVfVVNFX0ZBTExCQUNLKTsNCiB9DQogDQogLyoqDQo=


--=-km5TzIBqhRnZBhuU9PqS--

--=-/yjPDfDlC9x1KoiSwiOi
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (FreeBSD)

iEYEABECAAYFAkf+rU4ACgkQb2iPiv4Uz4fBgwCffNvsucUfcJXjXqFT4DbqDDTF
URUAnjiykM7+YBvOr1tXlgZX/WUwjzB9
=8iqV
-----END PGP SIGNATURE-----

--=-/yjPDfDlC9x1KoiSwiOi--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1207872846.87478.38.camel>