Salix Forums

Hey guys,

As usual I saw the slapt-get tray icon letting me know updates were available, so I updated and suddenly I have a new Firefox(4). No problems there.

However, last night I saw the update icon again in my tray, clicked on it, and it said the package to be updated was Firefox4. ("Weird, I just updated that last night...must be a bug fix") So ok, I update it and at the end instead of saying success it said "pkgtools error".

This happened several times over the past 24 hrs. Then tried to come here and the Salix OS server was down. Anyway....

...is this something I should worry about? Everything seems to be working fine, just not used to error messages when I do package updates.

Thanks in advance.

Dennis in New Orleans

Try: check if /usr/lib/firefox is still there. If it is, please check exactly what that is and report back remove it if it is there (rm, rmdir...)
and install the firefox package again You're not the only one having this problem, although I can't duplicate it no matter what I try.

Try: check if /usr/lib/firefox is still there. If it is, please check exactly what that is and report back remove it if it is there (rm, rmdir...)
and install the firefox package again You're not the only one having this problem, although I can't duplicate it no matter what I try.

What salix version are you running? 13.0, 13,1, 13.37beta?

OK, just managed to duplicate this. To solve it, you have to remove /usr/lib/firefox which is a broken symlink, leftover by the previous 3.6.x packages. So... and then the firefox upgrade will work.

Yet another firefox update is now in the i486 repository. Hopefully that will just work and you won't have to do any of that manual tweaking.

Hi Gapan,

I issued the "unlink" command as root, then ran the update again and received a system message that all actions had completed successfully, so I think we are in the clear.

Thank you very much for your immediate series of effective responses, and as always for the work your team does to keep Salix OS alive.

Dennis in New Orleans

I can confirm the existance of this problem in my 13.1 install

also I can confirm that the solution posted by gapan fixed the issue