End of F8 install -- frustratation !

[Craig White]

On Mon, 2007-12-17 at 08:24 -0500, William Case wrote:
> Hi;
> On Mon, 2007-12-17 at 01:11 -0800, Tod Merley wrote:
> > On Dec 16, 2007 7:11 PM, William Case <billlinux at rogers.com> wrote:
> > >
> > > 1) When I first login I get a dialogue that doesn't let me proceed until
> > > I put in a password that I just made up on the spot.
> > > "Enter password for default keyring to unlock"  What keyring -- its new
> > > to me.  The rest of the message is:
> > > "The application 'evolution' (/usr/bin/evolution) wants access to the
> > > default keyring, but it is locked".  I betja it wants access.  What
> > > keyring and how do I unlock it.
----
easy enough to delete your keyrings...

rm ~/.gnome2/keyrings/*
----
> 
> > #2.  My guess is that you are on the right track.
> 
> Not much point setting one without first fixing the other.
> 
> I did come up with this error last night.
> 
> ~]$ system-config-firewall
> 
> (system-config-firewall.py:9848): libglade-WARNING **: Error loading
> image: Failed to open file
> '/usr/share/system-config-firewall/system-config-firewall_48.png': No
> such file or directory
> 
> (system-config-firewall.py:9848): libglade-WARNING **: could not convert
> string to type `GdkPixbuf' for property `logo'
> Traceback (most recent call last):
>   File "/usr/share/system-config-firewall/system-config-firewall.py",
> line 41, in <module>
>     ui.run()
>   File "/usr/share/system-config-firewall/fw_gui.py", line 1223, in run
>     self.setupScreen()
>   File "/usr/share/system-config-firewall/fw_gui.py", line 79, in
> setupScreen
>     self.icon = icon_theme.load_icon("%s_48" % APP_NAME, 48, 0)
> gobject.GError: Icon 'system-config-firewall_48' not present in theme
> 
> Maybe its related.
> 
> P.S.  Could this be a ndiswrapper thing (or whatever).  I have noticed a
> lot of discussion on the list re: wireless, although I am not.
----
I note that the 'prompt' to your command system-config-firewall was '$'
and not a '#' where the '$' indicates that it is a 'user' where the '#'
would indicate superuser or what we know as root. I don't think
'system-config-firewall' can be run as a 'user' but if it invokes the
GUI, it may ask you to authenticate as root...perhaps you want to 'su -'
to root before invoking the command 'system-config-firewall' and see if
there's a difference.

Craig