Posted: Wed 04 Sep 2019, 13:30
Now then, boys & girls. I think it best I sound a note of caution here, and report my findings.
From a pristine install of Racy 5.5, I cannot recommend the installation of watchdog's upgraded glib. I'm not finding fault with his work, far from it - he knows I'd never do that - but, as he stated in the previous post, he himself wasn't 100% sure about this.
I merely wish to confirm that, although it's surprised me, I'll admit. Usually, Wary stuff will run OK in Racy (they share much of the same code-base, after all).....but not on this occasion. I assume this particular upgrade must be far more sensitive to specific versions of various items than was assumed.
-------------------------------------------
Install the 'tweaked' Palemoon .pet - no problem. As expected, it won't run; reports the 'XpComGlueLoad' error.
Now; this is where it gets a bit 'odd'. Upon attempting to install the uprated glib .pet, from the moment you click 'OK' to accept installation, Racy becomes pretty well unresponsive.
You can switch screens with the pager, and the main Menu will comeup. You can close anything that's already open. But you can no longer run, or open anything.....and even the shutdown/reboot/X-server sequence no longer responds, necessitating a 'hard' shutdown with the power button.
I tried this 3 times, just to make sure.....in case my elderly hardware had decided to throw a wobbly (she's pretty reliable, but.....it does happen. At nearly 16 years old, what else can you expect?).....but the result was identical in each case.
------------------------------
I know I previously reported success above with this installation. However, I can only assume that already having a newer glibc in place, courtesy of battleshooter's 2.20 'upgrade', had 'moved the goalposts'. Presumably, this gave the new glib .pet something different to work with.
So; I really don't know what to think at this point in time. Perhaps others may have some further insights on this issue? I'd be interested to hear them.
For now, I'm content to remain with running FF68esr from the chroot 'jail'. It'll do.
*Thoughts, anyone?*
Mike.
From a pristine install of Racy 5.5, I cannot recommend the installation of watchdog's upgraded glib. I'm not finding fault with his work, far from it - he knows I'd never do that - but, as he stated in the previous post, he himself wasn't 100% sure about this.
I merely wish to confirm that, although it's surprised me, I'll admit. Usually, Wary stuff will run OK in Racy (they share much of the same code-base, after all).....but not on this occasion. I assume this particular upgrade must be far more sensitive to specific versions of various items than was assumed.
-------------------------------------------
Install the 'tweaked' Palemoon .pet - no problem. As expected, it won't run; reports the 'XpComGlueLoad' error.
Now; this is where it gets a bit 'odd'. Upon attempting to install the uprated glib .pet, from the moment you click 'OK' to accept installation, Racy becomes pretty well unresponsive.
You can switch screens with the pager, and the main Menu will comeup. You can close anything that's already open. But you can no longer run, or open anything.....and even the shutdown/reboot/X-server sequence no longer responds, necessitating a 'hard' shutdown with the power button.
I tried this 3 times, just to make sure.....in case my elderly hardware had decided to throw a wobbly (she's pretty reliable, but.....it does happen. At nearly 16 years old, what else can you expect?).....but the result was identical in each case.
------------------------------
I know I previously reported success above with this installation. However, I can only assume that already having a newer glibc in place, courtesy of battleshooter's 2.20 'upgrade', had 'moved the goalposts'. Presumably, this gave the new glib .pet something different to work with.
So; I really don't know what to think at this point in time. Perhaps others may have some further insights on this issue? I'd be interested to hear them.
For now, I'm content to remain with running FF68esr from the chroot 'jail'. It'll do.
*Thoughts, anyone?*
Mike.