the_glu wrote:
And in key's description (Your name / Your email) ?
nope
I send you privately my keyid
1 2007-06-05 19:35:24
Re: crash trying to open options (6 replies, posted in Bugs & problems)
2 2007-06-05 11:28:18
Re: crash trying to open options (6 replies, posted in Bugs & problems)
the_glu wrote:
Do you have stranges (not a-Z0-9) caracteres into your private key ?
do you mean in the KeyId? there are only hex digits
3 2007-06-04 17:08:17
Re: crash trying to open options (6 replies, posted in Bugs & problems)
the_glu wrote:
Try to delete ALL firegpg's option in the page about:config (use filter with firegpg). What did you change ?
deleting the options in about:config worked
the problem is related to my default private key,
other private keys are working
4 2007-06-04 16:36:46
Topic: crash trying to open options (6 replies, posted in Bugs & problems)
Hi,
after installing the extension I was able to edit the options but now if I click on options Firefox crashes.
I'm using
Mozilla/5.0 (X11; U; Linux x86_64; it; rv:1.8.1.3) Gecko/20070310 Iceweasel/2.0.0.3 (Debian-2.0.0.3-1)
and I get the following error
GCJ PLUGIN: thread 0x14a6590: NP_GetMIMEDescription
GCJ PLUGIN: thread 0x14a6590: NP_GetMIMEDescription return
GCJ PLUGIN: thread 0x14a6590: NP_GetValue
GCJ PLUGIN: thread 0x14a6590: NP_GetValue: returning plugin name.
GCJ PLUGIN: thread 0x14a6590: NP_GetValue return
GCJ PLUGIN: thread 0x14a6590: NP_GetValue
GCJ PLUGIN: thread 0x14a6590: NP_GetValue: returning plugin description.
GCJ PLUGIN: thread 0x14a6590: NP_GetValue return
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:34: error: unexpected character `@', expected string constant
(npviewer.bin:31951): Gtk-CRITICAL **: gtk_window_resize: assertion `width > 0' failed
The program 'npviewer.bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 10071 error_code 3 request_code 3 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Segmentation fault