There’s a list of things that don’t work now. Most of them I can fix or maybe do without, but there’s one that looks like it will be a problem.
My KeyRing doesn’t recognize the password.
I thought maybe I’d just uninstall it and re-install, but the list of things that would be re-architechted scares me. Is there another way?
“re-architechted” Ok not a word but I get you. Mm this sounds scary I can only come up with two scenarios one you had one arch and upgraded to another arch(Always was going to end in a mess). Two you’re trying some kind of manual re-install and have inadvertently choose the wrong arch.
But even with the above I’m not sure that this would make password not accepted, in my limited knowledge I can think of 2 things one different tech(Mmm struggling here with the tech words sha vs md5 not quite but an example I hope you grasp). The other keyboard input is different though then I suppose one more but unlikely it really is the wrong password.
Jimmus wrote:
> There’s a list of things that don’t work now. Most of them I can fix or
> maybe do without, but there’s one that looks like it will be a problem.
>
> My KeyRing doesn’t recognize the password.
>
> I thought maybe I’d just uninstall it and re-install, but the list of
> things that would be re-architechted scares me. Is there another way?
>
>
10.3 to 11.0 works pretty well. Lots of radical changes (btw, this is VERY typical with SUSE going from .0 to .1) with 11.1. Even upgrading from
11.0 to 11.1 is fraught with issues.
I wish I had better news. So with openSUSE. X.0 -> X.1 danger! Whereas X.n -> X+1.0 is ok.
The reason is that traditionally, the X.1 release forms the basis for the next generation of the enterprise product line. And as others will testify,
things get reasonably rock solid by .2 or .3. BUT, realize that .1, because of its importance is usually fairly good… in the past it was usually
just messed up update mgmt… 11.1 sort of makes me concerned about SLES/SLED 11.
cjcox,
I wish I had known that two days earlier. >:(
On Thu, 2009-07-16 at 15:26 +0000, karx11erx wrote:
> cjcox,
>
> I wish I had known that two days earlier. >:(
>
>
Of course, that .0 vs. .1 is tradition right now. Not sure if that will
always be the case.
Jimmus wrote:
> There’s a list of things that don’t work now. Most of them I can fix or
> maybe do without, but there’s one that looks like it will be a problem.
>
> My KeyRing doesn’t recognize the password.
>
> I thought maybe I’d just uninstall it and re-install, but the list of
> things that would be re-architechted scares me. Is there another way?
Just try to change the keyring password by running “seahorse”.
Greetings,
–
Camaleón
“Enter password for default keyring to unlock”
But it doesn’t seem to recognize my password. That’s the problem.
Thanks for the idea though. Any other ideas?
Can I revert to 10.3? Will I run into even more bigger problems?
Jimmus wrote:
> Camaleón;2013293 Wrote:
>>
>> Just try to change the keyring password by running “seahorse”.
>>
> “Enter password for default keyring to unlock”
>
> But it doesn’t seem to recognize my password. That’s the problem.
>
> 
>
> Thanks for the idea though. Any other ideas?
Yes 
To “reset” keyring password just rename (or remove) the file located on
~/.gnome2/keyrings/default.keyring
Make a copy of that file before removing.
Greetings,
–
Camaleón
This worked like a charm. After I logged out and back in, of course.
Thank you very much.