I've got a serious gpg problem on one workstation. I've spent hours trying to solve it, and need to get some ideas from someone experienced. I'll give full details if anyone volunteers.
Anne
Anne Wilson wrote:
I've got a serious gpg problem on one workstation. I've spent hours trying to solve it, and need to get some ideas from someone experienced. I'll give full details if anyone volunteers.
Anne
go for it, you never know :)
On Saturday 04 November 2006 11:41, Thierry Sayegh De Bellis wrote:
Anne Wilson wrote:
I've got a serious gpg problem on one workstation. I've spent hours trying to solve it, and need to get some ideas from someone experienced. I'll give full details if anyone volunteers.
Anne
go for it, you never know :)
OK - fingers crossed :-) Before tying this down to gpg I thought it was a kmail problem, then I thought it was a postfix problem, so all the messages I have posted over the last couple of days are related to this. Here is the scenario.
This laptop ran rawhide, and is now running FC6. As you can see, gpg is working perfectly with kmail. I use kgpg to manage keys.
My main workstation has a clean install of FC6, and from day one I have not been able to run kmail. Eventually I tied it down to a gpg problem. Running gkrellm shows that on boot-up the cpu is using 99-100% and staying there. Top shows that it is gpg at fault and I have to killall -9 to stop it. It may be relevant that killall gpg does not stop it.
I have checked everything in the various conf files under .gnupg and they match the ones on the well-behaved laptop. I've checked permissions and altered as necessary to match this laptop. I copied all the contents of .gnupg on the laptop and moved them onto the workstation. Nothing makes any difference.
I moved the env and startup directories out of .kde, and there is no undue cpu usage.
I renamed .gnupg, uninstalled all things gpg then reinstalled them. No new .gnupg directory was created, so I had to put the old one back.
I'm out of ideas. If I can run kmail/gpg/kgpg on the FC6 laptop I should be able to do the same on the workstation with a clean-install FC6. It can't be a bug as such, or it would affect both.
Any ideas where I can go next?
Anne
Thierry Sayegh De Bellis wrote:
Anne Wilson wrote:
I've got a serious gpg problem on one workstation. I've spent hours trying to solve it, and need to get some ideas from someone experienced. I'll give full details if anyone volunteers.
Anne
go for it, you never know :)
One new piece of evidence. Running 'gpg --list-keys' returns many lines like
$ gpg --list-keys gpg: checking the trustdb gpg: [don't know]: invalid packet (ctb=00) gpg: keydb_search failed: invalid packet
then correctly lists a few. It looks as though the database is corrupt. Now if I knew what it is called, or where it lives, I could restore a backup copy. Does anyone know? Thanks
Anne
On Sat, 2006-11-04 at 17:06 +0000, Anne Wilson wrote:
Thierry Sayegh De Bellis wrote:
Anne Wilson wrote:
I've got a serious gpg problem on one workstation. I've spent hours trying to solve it, and need to get some ideas from someone experienced. I'll give full details if anyone volunteers.
Anne
go for it, you never know :)
One new piece of evidence. Running 'gpg --list-keys' returns many lines like
$ gpg --list-keys gpg: checking the trustdb gpg: [don't know]: invalid packet (ctb=00) gpg: keydb_search failed: invalid packet
then correctly lists a few. It looks as though the database is corrupt. Now if I knew what it is called, or where it lives, I could restore a backup copy. Does anyone know? Thanks
Anne
On my fc4 system, it live in the .gnupg directory in my home directory.
Warren Sturm wrote:
On Sat, 2006-11-04 at 17:06 +0000, Anne Wilson wrote:
Thierry Sayegh De Bellis wrote:
Anne Wilson wrote:
I've got a serious gpg problem on one workstation. I've spent hours trying to solve it, and need to get some ideas from someone experienced. I'll give full details if anyone volunteers.
Anne
go for it, you never know :)
One new piece of evidence. Running 'gpg --list-keys' returns many lines like
$ gpg --list-keys gpg: checking the trustdb gpg: [don't know]: invalid packet (ctb=00) gpg: keydb_search failed: invalid packet
then correctly lists a few. It looks as though the database is corrupt. Now if I knew what it is called, or where it lives, I could restore a backup copy. Does anyone know? Thanks
Anne
On my fc4 system, it live in the .gnupg directory in my home directory.
I presume you mean the trustdb.gpg. I copied that from my old install directory, but then the messages seemed to indicate that pubring.gpg could be the problem, so I copied pubring.gpg and pubring.kbx. Now attempting to list keys gives me many more than previously, but then ends with
gpg: [don't know]: invalid packet (ctb=00) gpg: keydb_search_next failed: invalid packet
Anne
On Saturday 04 November 2006 18:06, Anne Wilson wrote:
Warren Sturm wrote:
On my fc4 system, it live in the .gnupg directory in my home directory.
I presume you mean the trustdb.gpg. I copied that from my old install directory, but then the messages seemed to indicate that pubring.gpg could be the problem, so I copied pubring.gpg and pubring.kbx. Now attempting to list keys gives me many more than previously, but then ends with
gpg: [don't know]: invalid packet (ctb=00) gpg: keydb_search_next failed: invalid packet
Anne
An off-list message told me to rename ~/.gnupg, then run gpg from the CLI. I had actually done this once before, but I must have done something wrong the first time, because this time a new ~/.gnupg folder was created. I copied all files except backup ones from my old home directory, and now everything appears to be working correctly.
Just what was corrupted, and why, I have no idea, but I'm so glad to be able to work on this box again.
Thanks to all who tried to help.
Anne
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Anne Wilson wrote:
One new piece of evidence. Running 'gpg --list-keys' returns many lines like
$ gpg --list-keys gpg: checking the trustdb gpg: [don't know]: invalid packet (ctb=00) gpg: keydb_search failed: invalid packet
then correctly lists a few. It looks as though the database is corrupt. Now if I knew what it is called, or where it lives, I could restore a backup copy. Does anyone know? Thanks
trustdb.gpg resides in ~/.gnupg, you probably would have previously backed up that directory in order to replace that file.
ciao, furlan
- --
Music: http://www.myspace.com/acidredux
Links: http://del.icio.us/furlan
Home: http://flprim.us/index.html
"Play--more than piety, more than charity or vigilance--is what allows human beings to transcend evil." - -- Tom Robbins (Jitterbug Perfume)
On Sunday 05 November 2006 10:37, magicus wrote:
Anne Wilson wrote:
One new piece of evidence. Running 'gpg --list-keys' returns many lines like
$ gpg --list-keys gpg: checking the trustdb gpg: [don't know]: invalid packet (ctb=00) gpg: keydb_search failed: invalid packet
then correctly lists a few. It looks as though the database is corrupt. Now if I knew what it is called, or where it lives, I could restore a backup copy. Does anyone know? Thanks
trustdb.gpg resides in ~/.gnupg, you probably would have previously backed up that directory in order to replace that file.
Hi, Furlan. Yes, I knew that, but that wasn't where the problem was. It was actually in pubring.gpg and/or pubring/kbx. I restored backups and now all is well.
Thanks for trying to help.
Anne
-
Anne Wilson -
magicus -
Thierry -
Warren Sturm