Re: Failure of rpmdrake/urpmi and other applications

On 26/09/10 17:38, Rick Kunath wrote:
> On Sunday, September 26, 2010 12:12:44 pm Len Lawrence wrote:
>> Closed down and next
>> day booted up and tried the update applet, which showed a red
>> exclamation mark (that is not right is it?) and attempted to update
>> rpmdrake as instructed.  That failed and every attempt at using urpmi
>> came up with the message that rpmdrake needed to be updated first.  Each
>> time it failed.  So how come urpmi worked immediately post install but
>> fails now?
>
> Yes, that's right. If there are updates available for your system, the
> Mandriva Update applet checks the mirrors after a time period that is
> settable, it's 5 minutes after boot as I recall by default, and then if there
> are updates available, the red exclamation point appears. This then allows you
> to update the system.
>
> I prefer the interface of the MCC, Mandriva Control Center, so I use the red
> exclamation point as a cue to open the full updater.
>
>
> Start ->  Tools ->  System Tools ->  Configure your computer, and then click
> Update your system.
>
> I believe that you will find an icon to quick launch this in your systray also.
>
> It'll ask permission to check the mirrors for updates, tell it yes, and then
> display a list of updates available, with a lower panel that is clickable to
> see the details on any update, etc.
>
> In the case of rpmdrake itself being updated, this has to be upodated first.
> After it is installed, the update applet will relaunch itself with the new
> rpmdrake. At this point, I always close the update caplet completely, re-open
> it, and go from there. At that point, you will see any additional updates that
> are available and can continue the update process.
>
> It may be that somehow this is confusing the tray update applet. I never use
> it except for a cue to the fact that there are updates available, so don't
> have any experience with the issue you reported. I do know that I was away for
> a while and performed the above procedure last night, and all went as I
> described.
>
> Once I am updated, I right click the online updater applet and tell it to look
> for updates. It does so, and finding none now, goes away.
>
> Hope that helped.
>
> Rick Kunath
>
Not really but thanks for the reply.  This was the first time I have 
ever responded to the update applet.  Like you I have always used mcc.  
But mcc fails now because the first thing it needs to do is update 
rpmdrake and that always fails so it keeps going around in a circle.  
Command line attempts also fail, urpme and urpmi.  Anything rpm related 
requires rpmdrake to be updated apparently and the failure always hinges 
on the libnssutil error.  I have done some googling and found two or 
three people with very similar problems and they all point to 
libnssutil3 being an old version.  One correspondent had this trouble on 
2010.0 and also failed to get Thunderbird and Firefox going.  One 
solution which worked for these people was to reinstall (ughh!) but I 
hesitate to do that.  If the libnssutil3 library is out of date I don't 
see how that helps.  I will try to find out what version should be used 
and wget it and run rpm -Uvh in the hope that the raw command will work.

Apart from this trouble I am really impressed with this release.  It 
booted me straight into my GNOME desktop without my having to fiddle 
with kdm.  It installed the proprietary nvidia driver with no hiccups.  
Sound worked fine. Up to the point where urpmi failed I had firefox 
running and xmarks synchronizing my bookmarks.  Initial configurations 
usually need a couple of days work but this time it took less than three 
hours.

Len