Now, SM 2.46 runs with or without the glibc219_runtime-lucid package installed, even if the latter has been used previously (say, for 2.48). However, if you want/need to avoid using glibc 2.19, you can rename /usr/bin/seamonkey.bak to seamonkey. That links to /usr/lib/seamonkey/seamonkey instead of the new glibc interface scripts.
I recommend that anyone considering reverting to 2.46 update your version of glibc219_runtime-lucid (or the old glibc_subset-2.19-lucid), to ensure consistant behavior when changing versions of seamonkey between 2.46 and 2.48+.
To summarize the functions of the seamonkey and glibc packages:
- If you have upgraded to SM 2.48 and have problems with it even after installing the glibc runtime package, and need to retain your legacy SM environment, install:
http://www.mediafire.com/file/xrg5mk4j7 ... -lucid.pet
If you want to start with SM 2.46 in a new lucid pup environment, install:
http://www.mediafire.com/file/3l3a7tjxj ... -lucid.pet
If you are currently running with SM 2.46 or older and plan to have it update to SM 2.48, or have updated automatically to 2.48 and see the "glibc" error message, install:
http://www.mediafire.com/file/23etgzj70 ... 170812.pet
You will probably need to delete or rename the link, /usr/bin/seamonkey, in order to have seamonkey use glibc 2.19 and avoid the error that prevents SM from starting.
If you want to start with SM 2.48 in a new lucid pup environment, install:
http://www.mediafire.com/file/23etgzj70 ... 170812.pet
and
http://www.mediafire.com/file/42u1gyxhs ... -lucid.pet
EDIT 8/14/17: These 4 packages are now in the puppylinux lucid repo and are available with the Puppy Package Manager. Thank you, peebee.