pWidgets 2.5.8

[Dry Falls]

Hi David. You can also append to your linux/vmlinuz/append line in grub or other boot menu:

Code: Select all

net.ifnames=0

. This will ensure the "wlan" language is used rather than "wpl0..." or "'encap...", etc. This should fix the older widgets.

-df

edit: also, newer versions of conky (in newer pups) require lua (liblua.so.5).

[davids45]

G'day,

Thanks mikeslr and Dry Falls for your interest and replies.
Still thrashing about in 64-bit land without success (or knowledge of what I'm doing - as usual ).

However I did find how to add the wifi IP address to the working 32-bit Wireless widget (added red text to wirelss config file) ......

TEXT
${color white}${font pdingobats2:bold:size=20}0${font DejaVu:bold:size=11}${color yellow} Wireless
${color lightblue}${font DejaVu:size=10}${wireless_essid wlan0}${color orange}${font}${alignr}${wireless_link_qual wlan0}
${color green}${wireless_link_bar 10 wlan0}
${color lightblue}IP Address:${color orange} ${addr wlan0}

Result is in screenshot.

Will continue to try to work out a 64-bit pwidget wireless fix but maybe I just need to use conky-only in 64-bit?

David S.

[mikeslr]

Hi all,

I rather like pWidgets. But I also like DogRadio which has conky as a dependency. On its own, pWidgets-2.5.8-x86_64 worked fine under Xenialpup64. So does DogRadio if Conky is installed via PPM. However, if instead of that Conky pWidgets with its included conky 1.6.1 is used, DogRadio will work, but pWidgets will not start complaining about a missing config file.

The work-around is to first install Conky via PPM as part of the DogRadio install. Then install the pWidgets pet. Both pWidgets and DogRadio will then function.

[ndujoe1]

are these two libs available online, then? thanks

/usr/lib/libpng12.so.0.22.0
/usr/lib/libpng12.so.0

[mikeslr]

Hi ndujoe1,

Which Puppy? Although libraries may have the same name, and sometimes it doesn't make a difference, it's always better to use a library compiled for your operating system.

On xenialpup64 --from which I'm posting-- pfind located both /usr/lib/libpng12.so.0.22.0 and /usr/lib/libpng12.so.0. Examination of these showed that they were symbolic links to /usr/lib/libping12.so.0.54.0.

libraries are almost always backward compatible. That is, when a specific library such as libping12.so.0 is sought by an application, the application will use a later version, such as libping12.so.0.54.0 if you create a symbolic link to it and give the symbolic link the name of the file the application was designed to use. If the symbolic link doesn't already exist, you can create it. OPEN A TERMINAL IN THE FOLDER OF THE RECENT LIBRARY* and use this template:

ln -s NAME_OF_EXISTING_LIBRARY NAME_SOUGHT_BY_APPLICATION

Example

ln -s libping12.so.0.54.0 libping12.so.0

-----
* This isn't absolutely necessary, and sometimes is wrong. But it's easier. When necessary you can similarly create a symbolic link in one folder to a library in another folder. But then you'll have to specify paths, such as:

ln -s /usr/local/lib ABC.so.75 /usr/sbin/lib/ABC.so.76

The above can be entered from anywhere. You don't have to enter the path of the folder in which you've opened the terminal.
--------
Before we go hunting for other versions: Do you already have any libping12.so files on your system? If you open Puppy Package Manager and type libping12 in its search box, what results does it show?

[Mike Walsh]

@ ndujoe1:-

Whilst I do fully agree with Mike that you really ought to use dependencies compiled for your particular Puppy, I've had a rummage around in my big "box of toys" (I have a directory, full to the brim with all kinds of assorted dependencies.....a legacy of many Puppy 'lib-chases' over the years!), and have come across these two:-

A 32-bit libpng12.so.0.27.0, together with "so.0" sym-link
A 64-bit libpng12.so.0.37.0, together with "so.0" sym-link

There's one of each, since we don't know what Pup you're running. Both are slightly newer than that which you say you want, so by the law of averages, backward-compatibility should work in your favour. I've attached them to this post; unzip it, and each is in its own folder.

Can't hurt to try.... (*shrug*)

[For future reference, this:-

http://old-releases.ubuntu.com/ubuntu/pool/

.... is a good place to hunt for older, 'age-related' libs. Canonical's listings for many of these date back to the days of 'Gutsy Gibbon', or earlier - 12 years or more. Mikeslr will also tell you that pkgs.org is another good 'hunting-ground'.....with which I, too, concur:-

https://pkgs.org/ ]


Mike.

[mikeslr]

"[For future reference, this:-

http://old-releases.ubuntu.com/ubuntu/pool/

.... is a good place to hunt for older, 'age-related' libs".

Nice find, Mike. Thanks for posting it. Added to my Bookmarks.

[Mike Walsh]

"[For future reference, this:-

http://old-releases.ubuntu.com/ubuntu/pool/

.... is a good place to hunt for older, 'age-related' libs".

Nice find, Mike. Thanks for posting it. Added to my Bookmarks.

@ Mike:-

I've been using that one for a while. Despite the fact that pkgs.org often comes up trumps when I'm on the hunt for something, they only really publish 'updated' stuff for distros within the last 5 years. 'Old-releases' at /ubuntu/pool is a damn good place to find age-related libs for the older, 'buntu-based Pups like Precise or Lucid.

It's certainly worth having a rummage through, because they give approximate dates when stuff was added to the repo.....so for Precise, look for versions around the 2011/2012 time-frame, and for Lucid, around the 2009/10 mark.

Anything I can use to keep some of the earlier, really good 'buntu-based Pups going, I will make use of. I'm not proud; I'll grab stuff from anywhere I can..!

They do, of course, have stuff in there all the way up to the current releases, too. It all helps.


Mike.