BionicPup32 (UPupBB) (27 June 2020)

[john4gaming]

Why can't I install chromium_77.0.3865.75 + pepper_32.0.0.255_lx_spot.sfs with the root password

[OscarTalks]

Is this a frugal install of BionicPup32 (or full install or 64bit)?
You don't really "install" packages that are .sfs
You "load" them with right-click and sfs-load or using sfs-load from menu.
I tested that chromium in BionicPup32 and it loaded and ran.
No root password was needed (it hardly ever is).

[john4gaming]

I could already install it, I don't remember if it's Frugal, it's BionicPup32, but it asked me for several things the password
For example when wanting to install spotify-client-i386-0.9.4.183.pet asks me for the root password

[Gera]

Hi everyone,

Help me to install Windscribe on Bionic32 Puppy 8.0 [august 2019 edition taken from 1st post here].
I put in LXTerminal
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-key FDC247B7
and got "apt-key command not found"

I also tried to download binary file "windscribe-cli-1.4-52.i386.rpm" for mine 32-bit version but I don't know how to install it in Puppy.

And I can't find file "/etc/apt/sources.list.d/windscribe-repo.list" to fulfill the commands from Windscribe. (I see for Ubuntu 18.04 if I'm not mistaken)

[bigpup]

I could already install it, I don't remember if it's Frugal, it's BionicPup32, but it asked me for several things the password
For example when wanting to install spotify-client-i386-0.9.4.183.pet asks me for the root password

The default root password is woofwoof.
But installing a pet should not ask for it.
Where are you getting spotify-client-i386-0.9.4.183.pet?

[john4gaming]

I tried with woofwoof but it doesn't take it
I got it in the forum.

[williams2]

sudo asks for a password.

sudo asks for spot's password.
root's password will not work.

In BionicPup64 spot's privlieges are truly limited so spot
can not use commands like su or passwd
because the suid bit is not set.

Also, spot can not use sudo
unless you edit the sudoers file.

In BionicPup64 spot's password does not seem to be set.
root needs to set spot's password if you want it set.

It's easier for root to install software.

[bigpup]

I tried with woofwoof but it doesn't take it
I got it in the forum.

If you want some help, you have to provide useful information.
Give us a link to the spotify-client-i386-0.9.4.183.pet you are trying to install.

[john4gaming]

http://www.murga-linux.com/puppy/viewtopic.php?t=82034
http://www.smokey01.com/tempestuous/spo ... .4.183.pet

[TiredPup]

@john4gaming wrote:

http://www.murga-linux.com/puppy/viewtopic.php?t=82034
http://www.smokey01.com/tempestuous/spo ... .4.183.pet

@tempestous wrote:

Spotify client for Tahrpup 6 & Slacko 5.7

Here is the official Linux Spotify client.
UPDATE Aug 19 2015 - now at version 0.9.4.183.

Under Linux one of the dependencies is Qt4

Bionicpup 32 does not have QT4. Bionicpup32 has QT5. QT4 is an older version of t he QT libraries and was current at the time Ubuntu Trusty Tahr and Tahrpup 6.0 were released in 2014. The version of Spotify provided in that post was provided in 2015.

The short of it is that version of Spotify will not run on Bionicpup out of the box and it may not run at all on Bionicpup given the age of the software.

[TiredPup]

@williams2 wrote:

sudo asks for a password.

sudo asks for spot's password.
root's password will not work.

I don't understand. Why use sudo on puppy linux?

[mikeslr]

@ gera,

Puppies neither require sudo, su nor similar as they already run as root; neither do they use apt (or synaptic). Perhaps someone else can advise you how to install a key. I've never been able to figure it out.

However, if you already have a Windscribe account probably the easiest way to use it under Puppies is to use a firefox-quantum web-browser and the Windscribe addon. https://addons.mozilla.org/en-US/firefo ... ppver=69.0.

I can think of several alternatives. One is to switch to a DebianDog --look in the Projects Section. DebianDogs closely follow debian's/ubuntu's installation routines including (I think) how to add repositories.

Another alternative is to install Pkg - CLI package manager if it's not already in Bionicpup32. http://murga-linux.com/puppy/viewtopic. ... 531#985531. See that thread for instructions.

The third is to use OpenVPN, then follow the instructions of this thread, http://murga-linux.com/puppy/viewtopic. ... 88#1017988. I think this version, http://www.murga-linux.com/puppy/viewto ... 455#986455, is 32-bit and may work with Bionicpup32. If not, ask on that thread.

[john4gaming]

I understand and some way to install Spotify on BionicPup32?

[perdido]

@john4gaming wrote:

http://www.murga-linux.com/puppy/viewtopic.php?t=82034
http://www.smokey01.com/tempestuous/spo ... .4.183.pet

@tempestous wrote:

Spotify client for Tahrpup 6 & Slacko 5.7

Here is the official Linux Spotify client.
UPDATE Aug 19 2015 - now at version 0.9.4.183.

Under Linux one of the dependencies is Qt4

Bionicpup 32 does not have QT4. Bionicpup32 has QT5. QT4 is an older version of t he QT libraries and was current at the time Ubuntu Trusty Tahr and Tahrpup 6.0 were released in 2014. The version of Spotify provided in that post was provided in 2015.

The short of it is that version of Spotify will not run on Bionicpup out of the box and it may not run at all on Bionicpup given the age of the software.

Forum member festus made an .sfs of QT4 for bionicpup 18.05 that would satisfy the QT4 requirement.
It also works ok in bionicpup 19.03
http://murga-linux.com/puppy/viewtopic.php?t=113302

.

[TiredPup]

Perdido wrote:

Forum member festus made an .sfs of QT4 for bionicpup 18.05 that would satisfy the QT4 requirement.
It also works ok in bionicpup 19.03
http://murga-linux.com/puppy/viewtopic.php?t=113302

Perfect! I looked but did not find hoping to be of help. I do know that there is a 64 bit bionicpup derivative by Exton that has Spotify pre-installed.

[glene77is]

to : PeeBee

Thank you for providing such very good UpupBB systems.
I have read through your code, making notes, and adding my echo markers.

EDIT 200108 ***Problem Solved***
Thank you, PeeBee.

###########################################

My file system has this directory:
/initrd/mnt/dev_save/pup_UpupBB+16/upupbbsave-BB19+16-0101

I did find the script:
/initrd/DISTRO_SPECS .

containing this line:
DISTRO_PUPPYDATE='Dec 2019'

I suggest that this system constant
can identify the Build Date of the current UpupBB.
as long as PeeBee produces only one re-build per month.

SO, now I can identify the various running UpupBB systems,
+11, +12, +13, +14, +15, +16 !
at runtime with a "splash"
by reading this constant and displaying it
in my special "system signature" when rc.sysinit is running,
which is documented below.

###########################################

Also,
My UpupBB savefolders are in are in the 30 to 60 MB range
... Very Small !
Very Quick to Backup via my version of 2Byte hot backup.

__________________________________________________
We make use of SFS-load-on-the-fly v.3.0" for
"U-Lite browser" ,
"Iron-56 browser" ,
"Libre-Office 6.3.2",
"Gimp 2.6 for Lucid".
We seldom call for "snapmergepuppy"
in order to reduce internet Browser dumping into the SafeFolder.

__________________________________________________
Tip for Users :
We have, sometimes, three open Puppy systems, just for "tinkering' ,
and in our advancing years, we get them mixed up.

So, we insert a "signature" into the header of each main script
which splashes colorfully each time the script is run:
"rc.sysinit, rc.shutdown, sfs_load, fixmenus, rc.update, etc.
and sometimes little date-time markers so we can mark "time-usage".

For the record, our "System Signature Line"
is pre-pended to each major script ( rc.sysinit, rc.shutdown, rc.update ).
The code is essentially these simple, colorful lines:

lcMsgStr="UpupBB"
lcMsgOS="19.03+16"
/bin/echo -en "\\033[0;39m" > /dev/console ### clear color
/bin/echo -en "\\033[10G\\033" > /dev/console ### left margin
/bin/echo -en "\\033[1;37m*" >> /dev/console
/bin/echo -en "\\033[1;33m*" >> /dev/console
/bin/echo -en "\\033[1;32m*" >> /dev/console
/bin/echo -en "\\033[1;31m[" >> /dev/console
/bin/echo -en "\\033[1;36m : ${lcMsgStr}" >> /dev/console
/bin/echo -en "\\033[1;34m : ${lcMsgOS}" >> /dev/console
/bin/echo -en "\\033[1;31m]" >> /dev/console
/bin/echo -en "\\033[1;32m*" >> /dev/console
/bin/echo -en "\\033[1;33m*" >> /dev/console
/bin/echo -en "\\033[1;37m*" >> /dev/console
/bin/echo -e "\\033[0;39m" > /dev/console

__________________________________________________
Also,
We have been inserting an identifying line into the PUPSTATE file
by inserting simple BASH code into "sysinit"
in order to echo my identifier strings

id='=========================
id='...UpupBB-1903-Kernel=4.9.163'
id='...Distro: BionicPup32 19.03 +12'
id='========================='

at the bottom of the PUPSTATE file
and this runs each time I boot UpupBB.

__________________________________________________

Tip for Users :
In the /usr/shared/audio directory,
try renaming a "2barks.mp3" to replace
the M$XP "sys-login.mp3" melody .

__________________________________________________
( Summary )
So, to PeeBee , I say
This is the best written Puppy/Ubuntu system you have put together.

[peebee]

Hi @glene77is

That is tricky as the iso is renamed after the build process....

You can always download:
https://sourceforge.net/projects/zestyp ... t/download
and compare the md5 checksum or the build_date provided by Menu->Notes

[perdido]

This issue is solved - see the edit at the bottom of this post.
--------------------------------------------------------------------------------------

Noticed a tiny issue with the "places" icon placement in the upper-right corner of the screen when using the "Original Pup" desktop theme in BionicPup32
Theme is installed from - Applications-->Desktop-->Puppy Theme Manager-->Original Pup

The "places" icon placement in the "Original Pup" desktop theme becomes an issue when a program window is at full-screen and you try to click the "X" to close
the full-screen program window - the "places" icon can pop up over the "X" and covers up the "X" preventing the mouse pointer from clicking the "X" - so that when you
mouse-click to close the window the "places" menu comes up instead - Especially if you are fast and not real careful with the mouse (like me) all it takes is the
pointer to touch the top edge of the screen and the icon pops up over the "X" that closes the window

The "places icon automatically shows up in the far right-top corner of the screen after choosing the "Original Pup" theme - No way to move or remove it
Maybe someone knows the solution to get the "places" icon repositioned?

See 2nd pic for reference, this happens when trying to close a program window that uses the whole screen area.

EDIT ***Problem Solved***
Found a solution.
The places icon is considered a "tray" when you switch over to "Original Pup" desktop theme. Part of the "new" desktop handling system, I suppose it has to be present so here is how to hide it.

In the Menu-->Desktop-->Desktop Settings-->Tray-->Placement
That will show a grid of 9 squares representing where on desktop you want your tray. In this case it positions the "places" icon thingy and not the tray. I moved the position of the tray to lower left (see top pic)
and the real tray swallowed the "places" icon thingy - it no longer shows in the "Original Pup" theme.

[Mike Walsh]

@ john4gaming:-

The whole 'issue' with running any of the Chromium 'clones' is that there's no consistency with the way they run.

Modern Chromium, along with its 'offspring', Google's Chrome, hasn't run as root since around version 61/2. Flashpeak's SlimJet has only recently switched to insisting on being run as 'a user'.....and SRWare's Iron (a perfect copy of Chrome itself) will still, to this day, run as root. I download the tar.xz packages from the SRWare forum link, then re-build/re-pack them to run as root. And that's the way I run it. Much easier.

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

@ Gera:-

As Mikeslr has said, Pups don't run as a 'normal user', nor do they use the dozy 'sudo' system. Sudo is fine where you've got several different people, all using terminals, and acessing a common system - it's necessary, even - but in Puppy (a 'hobbyist' system, where invariably just one person runs it, along with full admin privileges), there is absolutely sod-all point in having to request access to your own system.....is there? Think about it.

With Pup, you learn to be a bit more careful, that's all. Even so, it's only a 5-minute job to re-install/restore from a backup, so it's not perhaps as critical as with most of the mainstream distros.....

BTW; no Puppy, to the best of my knowledge, uses RPM packages without some modification.


Mike.

[OscarTalks]

DeaDBeeF 1.8.2 compiled from source in BionicPup32 and including all optional dependency libs. Only pulse is disabled. Notify plugin is included but you have to enable it in Preferences if you want it to display pop-ups.

Recent Puppies have Dunst desktop notification daemon included and running. Not sure if people have it doing very much. I might start another thread about it. It does work with DeaDBeeF. I compiled latest version of Dunst (1.4.1) which has better support for displaying icons in pop-ups and I made a few tweaks to the configuration file for it. Restart X after installation, it will display a startup confirmation notification.

@peebee
The package libcurl3-nss (runtime, not -dev) is needed by DeaDBeeF, missing from this Puppy but apparently not missing from others? There is no libcurl3-nss-dev but the corresponding -dev file libcurl-nss.so is supposed to be provided by libcurl4-nss-dev (note the number difference 3 and 4) but that is missing as well, so perhaps check that all files from that package are in the devx.

I am still finding that symlinks (of shared libs) are NOT copied into the new dir when running new2dir make install although they are correctly installed into system. Happens with ScPup as well so something at the WoofCE level perhaps?

Packages uploaded for testing:-
http://smokey01.com/OscarTalks