Lucid Puppy Revitalized as 5.2.8.7 - Nov., 2017 - Final

[Moose On The Loose]

I propose for testing the following seamonkey2.48 working for me in my lucid 2016 install.

seamonkey2.48-en_US-lucid-glibc219tweak.pet:

https://drive.google.com/file/d/0B9iMb4 ... sp=sharing

It works in racy, too. Not in wary.

A glibc tweak is needed: glibc>=2.12 required. I added libxcb-shm.so from centos 6 but it would work from racy, too.

I was about to start on the same effort.
I am very glad you did this. I am using 2.46 that this moment.

BTW: May attempt to compile seamonkey failed with a syntax error in python. Did you compile?

[watchdog]

BTW: May attempt to compile seamonkey failed with a syntax error in python. Did you compile?

No, I didn't. I used the precompiled binaries from mozilla with en_US localization.

[rerwin]

watchdog,
Thanks for helping us out with this issue. I will adopt your solution, to keep lupu up to date with SM.

EDIT, after examining the pet package:
It appears that I could extract the glibc219 directory to, say, /usr/lib and modify the /usr/bin/seamonkey(2.48) script to match, but add code to test for the presence of the /usr/local/seamonkey directory before going to it. That script name would become just seamonkey, to be permanent and generic.

Maybe all of the added code could reside in its own package, so normal updating of SM would work. Or maybe just put it into lupu as architecture stuff (the zz_lupu_5.2.8.7-delta package). Do you see any problems with that approach?
Richard

[tallboy]

If you also include all the network updates you have been working with, you could name it 5.2.8.7.2...
Just my 2c.

tallboy

[watchdog]

watchdog,


Maybe all of the added code could reside in its own package, so normal updating of SM would work.

I think it would not work because there also is a glibc tweak for the plugin-container: the original plugin-container is renamed plugin-container-exec and plugin-container is a script with glibc tweak in order to use the included up-to-date flashplayer. The update process of seamonkey could be done manually or by a script.

[Moose On The Loose]

BTW: May attempt to compile seamonkey failed with a syntax error in python. Did you compile?

No, I didn't. I used the precompiled binaries from mozilla with en_US localization.

Small suggested changes:

Currently when you first start it after the install, it goes to their default page. If a new user is confronted with that page with the big red message, they may feel that there is something they must do. This seems bad. Perhaps, an additional tweak to make it go to a different default page is in order.

In /user/local/bin/defaultbrowser
The line with the exec that you commented out may be a problem. A few of the scripts elsewhere look at that script to see if a default browser has been set. They look for the "exec" line and then parse it. There may be one that can be confused by the exec comment

I made the attached from their icon. I did a few slight tweaks as I scaled it.
/usr/local/lib/pixmaps/seamonkey24.xpm
/usr/local/lib/mini-icons/seamonkey16.xpm

[watchdog]

You can do these changes by yourself: I'm not jealous. I use palemoon as main browser and my package of seamonkey 2.48 is enough for my use. I shared it but it's all open source.

[rerwin]

It appears that I could extract the glibc219 directory to, say, /usr/lib and modify the /usr/bin/seamonkey(2.48) script to match, but add code to test for the presence of the /usr/local/seamonkey directory before going to it. That script name would become just seamonkey, to be permanent and generic.

Maybe all of the added code could reside in its own package, so normal updating of SM would work. Or maybe just put it into lupu as architecture stuff (the zz_lupu_5.2.8.7-delta package).

I have now done just that! Watchdog's added logic is now in its own package, glibc219_runtime-lucid-20170808.pet. I adapted his interface scripts to fit the current invocation of "seamonkey" and to work with future updates offered by seamonkey. If you have not installed watchdog's SM 2.48...tweak package and can use the SM Update option, 'glibc219_runtime' is the only package you need to install, to get 2.48 working.

The packages are here:

• http://www.mediafire.com/file/7u9i5eru9 ... 170829.pet (EDIT)
  
  [EDIT] Two Seamonkey packages replaced by single package that does not contain preset user data, but automatically creates a new set when necessary. The seamonkey interface in glibc219_runtime-lucid presets the start page and suppresses a pop-up about setting a default browser. (There is no need to replace 2.48 if you have it already installed.)
  http://www.mediafire.com/file/t3qcf3ku6 ... -lucid.pet
  
  [EDIT] Palemoon link removed. See the Palemoon posting on the next page, for a more complete implementation of Palemoon for Lucid Pup.

If you have installed watchdog's package, you need to uninstall the seamonkey2.48-en_US-lucid-glibc219tweak.pet package, then install the glibc219_runtime-lucid pet and Seamonkey-2.48-update-lucid.pet, in either order.

The other package, Seamonkey-2.48-lucid.pet, is intended for a first-time installation of seamonkey, as would be done from quickpet. The 'glibc219_runtime' and Seamonkey-2.48-lucid packages (but not Seamonkey-2.48-update-lucid) should get uploaded to the pet_packages-lucid repository (ibiblio, etc.) (by peebee?).

When you run seamonkey you might find in the xerrs.log file, the message:

Code: Select all

(seamonkey:21099): Pango-WARNING **: libthai.so.0: cannot open shared object file: No such file or directory

This appears to be harmless, but can be eliminated by installing from the ubuntu-main repo: libthai0_0.1.13 and its dependencies, libthai-data_0.1.13 and libdatrie1_0.2.2-3. However, that may be something unique to my particular pupsave.

There is another warning I have seen, that maybe watchdog can address, although I am unaware of any impact:

Code: Select all

(ROX-Filer:5914): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.0/gobject/gsignal.c:3079: signal name `depressed' is invalid for instance `0x8432098'

More about this in my next message, below.

EDIT: Replaced glibc_subset-2.19-lucid.pet with glibc219_runtime-lucid-20170808.pet and changed its references in this message. Improves the install script and adds an uninstall script.

EDIT 8/16/17: Added support for Palemoon browser. Updated glibc219_runtime-lucid and added the latest version of Palemoon.
Richard

[rerwin]

Report on my experience with updating seamonkey, with the glibc addition:

In a fresh puppy environment, I first installed SM 2.40, then glibc_subset. Here are the messages I get when testing seamonkey with the glibc_subset package installed:

• Clicked on 'browse' icon and responded to configuration pop-up, then saw:

  Code: Select all

  (seamonkey:3122): GLib-GIO-WARNING **: Failed to execute child process "update-desktop-database" (No such file or directory)

  Clicked on 'Continue' on the first page displayed, then saw:

  Code: Select all

  (seamonkey:3122): GLib-GIO-WARNING **: Failed to execute child process "update-mime-database" (No such file or directory)
  
  (seamonkey:3122): GLib-GIO-WARNING **: Failed to execute child process "update-mime-database" (No such file or directory)
  
  (seamonkey:3122): GLib-GIO-WARNING **: Failed to execute child process "update-mime-database" (No such file or directory)

  On the "Seamonkey 2.40" page, I clicked on the Help menu and noticed the item "Downloading Seamonkey 2.48"; clicked on it and watched the progress until I saw "Update Ready to Install", then clicked 'Restart Seamonkey'; it apparently installed but did not restart, reporting:

  Code: Select all

  XPCOMGlueLoad error for file /usr/lib/seamonkey/libxul.so:
  libxcb-shm.so.0: cannot open shared object file: No such file or directory
  Couldn't load XPCOM.

  This was due to its not using the new seamonkey link that set up the glibc libraries, and is to be expected.
  
  Started SM from the 'browse' icon and saw the SM 2.48 page, with its alarming red message about automatic upgrades not working (but apparently they do -- in another test, it first made a "partial" upgrade, then reinstalled with a full upgrade)

When I installed glibc_subset in my regular pupsaves and ran the update option, all went well except that I saw something strange regarding the menu bar and Back and Forward button drop-down lists. Some of them displayed with the characters slanted. The distorted drop-downs occurred on different menus after each SM restart, and sometimes none were distorted. I am hoping that that is related to SM 2.48 and not the glibc implementation.

[rerwin]

More on the Seamonkey-2.48 distortion problem:
Today, when I started up one of my regular pupsave environments, the entire window was slanted except for the window title bar! This was much more than only the menu problem reported above. See attachment.

So far, I conclude that 2.48 seems to behave itself in fresh puppy environments, so probably has a problem with older Seamonkey "profiles", the directory containing all of the user's Seamonkey information (e.g., /root/.mozilla/seamonkey/agi9ixk5.default). I have not found any mention of that problem online. But I have some suggestions for those of you considering upgrading and existing installation to 2.48.

If you use the Mail part of Seamonkey, you might consider waiting until I or someone figures out the issues with email. I'll give details below, but I want to first give you information if you have already upgraded and are seeing the kind of problems I see. If you are not using Seamonkey Mail, you can revert to 2.46 by installing the 2.46-update .pet I posted here:
http://www.murga-linux.com/puppy/viewto ... 665#962665.

• 1. When you install the 2.46 update, it will not use the glibc update but should still work.
  2. To have it use the glibc update, simply delete or rename /usr/bin/seamonkey link (to -.bak?); that will use the new interface, which seems to work OK for 2.46.
  3. To avoid the temptation to allow an automatic update to 2.48, you can disable that through Edit > Preferences > Advanced (expand its list) > Software Installation, then uncheck the item "Automatically check for updates".

For those using Seamonkey Mail, note this item in the 2.48 Release Notice:

• Data loss warning: If you use a profile with this or any later version and then try to go back to SeaMonkey 2.40 or earlier, SeaMonkey will rename your history file to places.sqlite.corrupt and create a new places.sqlite file, effectively resetting your browsing history. This is because the internal format changed and the upgrade process only works in one direction.
  
  Additionally, running MailNews with local folders and POP3 mail filters may produce summary files that are not correctly read by previous versions of SeaMonkey. If you decide to go back to a previous version of SeaMonkey, you should delete the .msf files for your local folders and POP3 accounts or repair the folders using the folder properties dialog in order to avoid potential data loss.

This tells me that we should not revert to Seamonkey 2.40 or earlier, but that 2.46 is OK (except for the email issue, which appears to be fixable).

Under 2.48, my Mail function initially shows a momentary black area as it starts, but otherwise seems to work correctly. But I use only its basic capabilities.

If anyone is encountering these or other issues, please report them here, so that I might determine what to include in the next Lucid release, relative to Seamonkey support.
Richard

[rerwin]

I have "fine tuned" the glibc 2.19 interface and seamonkey 2.46 packages to make transitioning from SM 2.48 back to SM 2.46 reliable. I updated the above links to glibc219_runtime-lucid and SM 2.46-update to new versions.

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

HTH

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.

[Mike Walsh]

Hallo, Richard.

I figure this is probably the best place to ask this. I'm kinda 'consolidating' things across the kennels, and was wondering; is there any screen-recording app for Lucid (similar to SimpleScreenRecorder)?

I'm afraid I've never been much of one for CLI interfaces (a GUI of some kind is far preferable for me), and as for attempting to compile SSR for Lucid, well.....my compiling 'skills' are absolutely abysmal. I thought it would be far simpler to ask the 'head honcho', as it were!

-----------------------------------------------------------------------------

I originally installed Lucid around 15 months ago, in order to try and help TwoPuppies get SlimJet running in Lucid.....a task at which we had no joy in the final outcome, 'cos it's the old story of the glibc again, y'see. I've actually installed battleshooter's 'glibc220' fix (originally for Racy & Carolina), and it's enabled me to get certain things running (scabz's SMPlayer 14.9.0 being one that comes to mind), but, try as I might, I cannot get a later Chrome than version 26 (or later Chromium-based browser of any kind, come to that) 'up-and-running' in Lucid. The fix I've employed in Racy has allowed me to run the final 32-bit Linux Chrome release, 48.0.2564.116.....which I run across all my 32-bit Pups from a remote data partition, sym-linked into each Pup at the appropriate places (courtesy of davids45's thread on the matter). I keep getting a 'g_bytes_unref' error in the terminal, even with the glibc 'upgrade'. Any ideas?

I've rather fallen for Lucid, I must admit! Oh, one other thing, while I think about it. Google Earth, while it does run, displays all kinds of 'artifacts'; radial lines centering on wherever your mouse focus happens to be when you're zooming in.....and 'map tile displacement', too. (That's the best description I can give it.)

It appears to be complaining about the version of OpenGL being too old for it; it wants OpenGL 2.0 or later. Lucid is using, what? 1.75, I think? Is there any way this could be 'upgraded', too? I don't even know if it's possible, and I haven't got a clue what 'modules', or libs, or whatever, would be involved. I've installed the Xorg_High graphics driver, which has helped a little.....but the 'artifacts' remain.....

(I don't think it's anything to do with the integrated ATI Radeon XPress 200 graphics chip on my big old Compaq desktop; it runs the later 7-series Google Earths in both Tahr64 and Xenialpup 7081, which I've recently repackaged, without so much as a peep of complaint! Although I've actually 'standardised' on the same GE as Lucid's, 6.0.3.2197, in all my Pups; it seems to suit my hardware better than the the 7-series. It was the first with the 'Street View' feature, yet isn't as 'heavy' or demanding as the later releases.)


Mike.

[rerwin]

Mike Walsh,
Thanks for your inquiry. I am not aware of any screen-recording app for Lucid, But, then, I never looked for one.

Interesting that you mention your glibc upgrade to get some apps working in racy. Now that I have adapted watchdog's glibc 2.19 technique to keep Seamonkey working in Lucid, I have been wondering what other programs might be made usable with 2.19.

I would consolidate all special interfaces to 2.19 in the new glibc-runtime package. If you are interested in making anything else work in lupu with glibc-runtime 2.19, let's work on it. Or maybe I need to replace 2.19 with 2.20, to satisfy SSR.

As for OpenGL, I know nothing about it, so would need assistance from someone more knowledgeable of it. I suspect it would take a bit of experimentation to get it to work, or at least find why it might not be possible.
Richard

[Mike Walsh]

Hallo again, Richard.

You know, I have to say I admire you for keeping Lucid viable.....given that all the original repositories are long gone..! I may package stuff, and help newbs out with enquiries.....simply giving others the benefits of my own Puppy experience, but in no way do I consider myself any kind of an expert. I consider myself to be a 'bumbler', and an 'eternal noob'; there's always something else to discover, isn't there?

Well, if there ain't a screen-recording app available for Lucid, I shall have to scour the web and see what I can turn up; maybe I can discover something that might work under WINE.....who knows? We shall see, we shall see.

Vis-a-vis the 'glibc' stuff, TBH, I didn't really expect it to work for Lucid at all.....but it surprised me. True, it made things work that I hadn't really considered, but 'every little bit helps', as they say..!

As for the 'OpenGL' stuff, well.....it may be opening a right can of worms. I'm going to do some more research into this, and see what turns up. I'll keep you informed.


Mike.

[watchdog]

I did some progress. The following simplescreenrecorder-0.3.3-glibc219tweak.pet, based on the tahr package, is somehow working for me in lucid:

https://drive.google.com/file/d/0B9iMb4 ... sp=sharing

Use qt-4.8.0 by pemasu:

http://www.murga-linux.com/puppy/viewto ... 518#637518

I have packaged it as sfs. qt-4.8.0-basic-with-qtwebkit-dpup.sfs:

https://drive.google.com/file/d/0B9iMb4 ... sp=sharing

[Mike Walsh]

Morning, watchdog.

I'm......well; speechless, mate, is one way of putting it. I wasn't fishing for anybody to attempt that, but it's very much appreciated!

I trawled the web thoroughly last night; found no end of screen-recording apps. None of the Windows ones will run under WINE (no surprise there), and many of the Linux ones are source-code only, and need compiling. My skills in that area are abysmal, I'm sorry to say.....

I did find one likely-looking candidate, however. ScreenStudio.

http://screenstudio.crombz.com/

It's apparently more for 'vloggers' (video 'bloggers'?) than anyone else, but it does have a screen-recording function as part of its operation. It's Java-based; no biggie, as I have JRE installed for my package of the OpenStreetMaps 'Cruiser' app that Phil B. linked to here:-

http://www.murga-linux.com/puppy/viewto ... 746#943746

.....and which I posted about here:-

http://www.murga-linux.com/puppy/viewtopic.php?t=110875

Richard's own 'GetJava' app for Puppy works a treat!

-----------------------------------------------------------------------

ScreenStudio starts up no problem; you can set everything up as explained in the instructions link, but it just won't actually run. It's supposed to start/stop from the icon in the systray, but I wasn't getting any joy with it. Probably doesn't like the JWM taskbar/tray.....it will have been set up for Ubuntu's 'Unity'. (Damn..!!)

It's based around 'ffmpeg'; specifically, the version from 16.04 LTS 'Xenial Xerus'. So I tried it in Xenialpup, naturally.....

So near....and yet so far. (*sheesh*)

I'm currently having a major re-shuffle of my main hard drive, so when I get things back where I want them, I'll give your packages a try in Lucid, and see how I get on. I'll keep ya posted, mate.

Cheers.


Mike.

[mikeslr]

Hi Mike,

I don't want to discourage current efforts. But it seems you used the wrong google.

Lobster's front end for ffmpeg: http://www.murga-linux.com/puppy/viewto ... 319#613319. Of course, read the whole 3 page thread.

Which also includes Pelo's mention of xvidcap. As far as I know, xvidcap 1.17 will function in almost any Pup. The catch is to get it to record sound as well.

Can't find the post about it, but fortunately I stored a note:

"I had success, getting my microphone to work with xvidcap, by changing
the default input device, from /dev/dsp, to /dev/audio.

& Open Alsamixer, click tab & make sure both capture devices are
unmuted


Hi Guys:

I was playing with Xvidcap. It's never had a problem recording video. But it
wasn't recording audio. A well-minded search revealed that muggins suggested
the default setting of /dev/dsp should be changed to /dev/audio0. See link:
http://www.murga-linux.com/puppy/viewto ... 417#511417

I made that change and it appears to work in all Puplets, although it may also
be necessary to make certain that the capture device(s) are not muted.

Many people installing xvidcap may just figure sound doesn't work and leave it
at that.

I haven't been able to figure out who builds/maintains xvidcap for Puppy.
So I thought it best to alert those who evaluate what pets go into repos (and Lobster
who has expressed an interest in audio/video recording). /dev/audio0 should be
set as default in the build, especially as manually changing the default is
obscure and prone to error."

mikesLr

[Mike Walsh]

Mm. Looks interesting, Mike.

I've read the thread, but I'm still no closer to figuring out where you actually 'install' it to..... /root/my-applications/bin, perhaps? And where does the resulting video get saved to? /Root, I would think..... And what 'format' is the file in? Hmm. Details, details... Actually, scratch that. The only thing I'm not clear on is the relationship between the 'rs' script, and this 'recdesk' mentioned at the very bottom of the pup_rec script.

(Wouldn't take no doing to knock up a menu entry for it, neither.....)

Canst thou perchance enlighten me, young sir? You've been knocking around Puppyland a wee bit longer than me, mate; I'm betting there's more stored up there in your noggin than you're letting on..!

(Or scattered around your desk, scribbled on various bits o' paper... )


Mike.

[Mike Walsh]

Yay! SUCCESS...

Cheers, watchdog. You've done it again, mate. SSR 0.3.3 is working perfectamente in Lucid. You have surpassed yourself, mi amigo...

(And that's good, too, because it hasn't 'interfered' with battleshooter's 'glibc220' stuff I installed to get other things working. Nice one!)

For anybody else wanting SimpleScreenRecorder for Lucid 5287, follow this link >>>--------->

http://www.murga-linux.com/puppy/viewto ... 352#964352

---------------------------------------------

@Richard:-

There you go, mate. SimpleScreenRecorder for Lucid, courtesy of our good friend watchdog. I'd grab this, and stick it in your repos quick, like.....before he changes his mind!

(Not that I think he will...) All helps to keep Lucid more viable than ever. Love it!


Mike.

[mikeslr]

Great that watchdog created the simplescreenrecorder pet. Nice work, Watchdog.

Tahrpup and Slacko 5.7 became my usual OSes a couple years ago. I'm not sure I ever used Lobster's front end to ffmpeg. Nor am I sure I got sound to record under xvidcap more than once using muggins' recommendations. And that once was running Saluki. Really don't do screenrecordings often.

mikesLr