Bionicpup64 8.0 CE

[zigbert]

Something weird with the 'kill' command in bionic64.

Code: Select all

kill -19 12345

Works as expected (pauses the prosess), while the command to continue fails. Tried all documented variations

Code: Select all

kill -18 12345
kill -n 18 12345
kill -s CONT 12345
kill -s SIGCONT 12345

Works in every other Puppy I've tried - Bionic32, ScPup, Slacko, RasPup

hi zigbert,

just tried this on htop and it paused and restarted.

Maybe htop has an alternative kill... No...
I tested htop too (with the same test as before), and it failed.
playing an audio file:

Code: Select all

ffmpeg -i "/path/file.mp3" -f s16le -acodec pcm_s16le -ar 44100 -ac 2 - | aplay -f S16_LE -c2 -r44100

Now, trying to pause and continue in htop kills the process. This is unique behavior for Bionic64... Hmmm, this is strange

[linuxcbon]

Bionicpup64 8.0 CE
when I use quickpet, in "useful" section, I cannot download "devx" or "kernel src" SFSs. I tried different URLs from the list, but none works.

550 Failed to change directory.
No such directory 'pub/gnu+linux/puppylinux/puppy-bionic/bionicpup64/'.

[linuxcbon]

Bionicpup64 8.0 CE
when running steam for 1st time, it shows an error :

# steam
Repairing installation, linking /root/.steam/steam to /root/.local/share/Steam
File "/usr/bin/steamdeps", line 367

^
SyntaxError: EOF while scanning triple-quoted string literal
Running Steam on puppy 8 64-bit
STEAM_RUNTIME is enabled automatically
Installing breakpad exception handler for appid(steam)/version(0)
/root/.local/share/Steam/ubuntu12_32/steam: symbol lookup error: /usr/lib/i386-linux-gnu/libxcb-dri3.so.0: undefined symbol: xcb_send_request_with_fds
/root/.local/share/Steam/steam.sh: line 444: no match: ssfn*

solution :

LIBGL_DRI3_DISABLE=1 steam

see https://github.com/ValveSoftware/steam- ... ssues/4816
They closed the issue, but it doesnt seem to be fixed.

[linuxcbon]

Bionicpup64 8.0 CE
installed conky from quickpet, useful tab. Many configurations of conkyswitcher are buggy. For example conky_grey :

Code: Select all

root# conkyswitcher 
/usr/sbin/set_bg: line 8: pcmanfm: command not found
conky: Syntax error (/root/.conky/conky_grey/conkyrc:2: unexpected symbol near '#') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: Invalid value 'undecorate' for setting 'own_window_hints'. Valid values are: 'undecorated', 'below', 'above', 'sticky', 'skip_taskbar', 'skip_pager'.
conky: desktop window (4c8) is root window
conky: window type - override
(...)
conky: can't load Xft font 'Ubuntu:size=7,weight:bold'

[bigpup]

Bionicpup64 8.0 CE
when I use quickpet, in "useful" section, I cannot download "devx" or "kernel src" SFSs. I tried different URLs from the list, but none works.

550 Failed to change directory.
No such directory 'pub/gnu+linux/puppylinux/puppy-bionic/bionicpup64/'.

Do Quickpet ->Info ->Bionicpup updates
Reboot so the updates get saved.
Try getting the devx or kernel src again.

[linuxcbon]

Do Quickpet ->Info ->Bionicpup updates
Reboot so the updates get saved.
Try getting the devx or kernel src again.

My pup is always updated.
Did you try it at least ? I cannot count on you, so I tested again :

For devx :
It worked for this servers :
distro.ibiblio.org
ftp.cc.uoc.gr (very slow)
ftp.nluug.nl
mirror.internode.on.net

It failed with this servers :
ftp.vcu.edu
1st mirror.aarnet.edu.au
2nd mirror.aarnet.edu.au (timed out)

Note : mirror.aarnet.edu.au is duplicated in the list, why ?

[linuxcbon]

Bionicpup64 8.0 CE
Feature request : can you add python3 by default please ?
It is needed by some games in Steam, like "path of exile".

Code: Select all

env: can't execute 'python3': No such file or directory

I found it at /usr/bin/python3

Code: Select all

root# /usr/bin/python3
bash: /usr/bin/python3: No such file or directory

Bug : The symlink is broken. /usr/bin/python3.6 doesn't exist.

[bigpup]

For devx :
It worked for this servers :
distro.ibiblio.org
ftp.cc.uoc.gr (very slow)
ftp.nluug.nl
mirror.internode.on.net

It failed with this servers :
ftp.vcu.edu
1st mirror.aarnet.edu.au
2nd mirror.aarnet.edu.au (timed out)

Puppy Linux has no control over these repositories.
If they are down, up, or working.

Usually, if they have problems. It is because, the people that own the repository, are working on it.

That is why, several of them are listed, to choose from.

ibiblio.org is usually working, most of the time.

[linuxcbon]

Puppy Linux cannot control these repositories.
If they are down, up, or working.

Usually, if they have problems. It is because, the people that own the repository, are working on it.

That is why, several of them are listed, to choose from.

ibiblio.org is usually working, most of the time.

I know but I had to report it anyway, so it's a known problem now.

[Revolverve]

Anybody know who create the google-chrome run-as-spot script ?

edit;bump...never mind

Bionicpup64 ,daily workhorse here.

[belham2]

(posted something similar to this in a recent "Hardware" thread about bluetooth)
http://murga-linux.com/puppy/posting.ph ... &p=1041279

Any Xenial/Bionic pup user ever get a USB Bluetooth Dongle (based on the all-pervasive Broadcom crappy ships) to work in Xenial and/or Bionic? Just for something simple like a recent Mpow bluetooth headset (not even trying bluetooth speakers, phones, or even sending files via bluetooth).

If you did get bluetooth to work, can you be specific about how you did it Neither Mistfire's excellent p3bluetooth app nor Rsrcn51's excellent app work when it seems to be an issue with these seemingly amazon-supplied everywhere Broadcom dongles.

Thanks for any feedback/tips/etc.



P.S. Both Broadcom and Intel chip-based bluetooth dongles work in all DebianDog and variations thereof. Debian overall takes care of the libraries and firmware. But across Pupland and variations thereof, Broadcom USB Bluetooth dongles---in my experience and testing---just work like crap, if they work at all.

[linuxcbon]

Bionicpup64 8.0 CE

I am testing games in Steam, so can you please add "xdg-utils" package (to get xdg-icon-resource, xdg-user-dir etc).
Can you also make "nvdia" driver default, instead of "nouveau" driver ? Reason ? "nouveau" is extremly slow for games, unfortunately.
PS : for testing, I just installed nvidia 440.31, it works OK except that I had to set up the keyboard language to french again.

Cheers

[bigpup]

Nouveau is used by default, because it will work with any Nvidia graphics hardware.
It is a generic Linux Nvidia driver.
It does supply basic operations, but not as good as Nvidia's specific driver packages.

Specific Nvidia hardware, will need a specific Nvidia driver, if you want to use Nvidia supplied driver software.
Yes, their driver packages do support multiple devices.
However, they add support and delete support each time they make a new driver package.
Also, an older Nvidia driver package, is not going to support Nvidia hardware, developed after the driver was released.

The program:
Quickpet->Drivers->
Has Nvidia driver packages for download and install.
They support a lot of the Nvidia hardware, but not every possible one.
Some very old Nvidia hardware, is only supported by much older Nvidia drivers.

Here is information on compiling your own Nvidia driver packages.
http://www.murga-linux.com/puppy/viewtopic.php?t=110611

[Revolverve]

There are no bionicpup64 problem here,answers to these questions may just help the confused user in sandboxing understanding i am...
Using google-chrome latest run as spot ,which i does not seems to give me trouble,i have those questions that may seems obvious(wishful thinking here...) to some:
- Does it use sandboxing automatically?
I guess so,searching bionicpup64 script for the --no-sandbox argument ,find nothing in scripts and i read a lot out there that the're no such things anymore of chrome/chromium without it!!!
I do see all of jamesbond sandbox scripts build-in/included ,if ever they are here for that purpose or use in the system at all for the browser ..

Trying to explain confusion is not the easy one!!!!
If you think you can hit the switch so that it light up here ...
Oh and while on the subjet;
666philb
I still use google-chrome update_utility..
This must be the ¨magic¨ that keep the google-chrome run as spot script in opt,is that it?
Thanks

[linuxcbon]

Nouveau is used by default, because it will work with any Nvidia graphics hardware.
It is a generic Linux Nvidia driver.
It does supply basic operations, but not as good as Nvidia's specific driver packages.

Specific Nvidia hardware, will need a specific Nvidia driver, if you want to use Nvidia supplied driver software.
Yes, their driver packages do support multiple devices.
However, they add support and delete support each time they make a new driver package.
Also, an older Nvidia driver package, is not going to support Nvidia hardware, developed after the driver was released.

The program:
Quickpet->Drivers->
Has Nvidia driver packages for download and install.
They support a lot of the Nvidia hardware, but not every possible one.
Some very old Nvidia hardware, is only supported by much older Nvidia drivers.

Here is information on compiling your own Nvidia driver packages.
http://www.murga-linux.com/puppy/viewtopic.php?t=110611

You really think I dont know this ? What do you think ? And I wrote I installed the latest nvdia drivers, cant you read ?
I asked to have "nvidia" instead of "nouveau" driver to have better video performances. If it doesnt work with some old hardware (which is rare nowadays), it's easy to use "nouveau" instead. For me it's the best solution.

[bigpup]

Sorry you do not understand that answer is not just for you.

You asked why Nouveau is used by default?
Because it usually just works with any Nvidia hardware.
That is what you want to happen the very first time you try to boot Bionicpup64 8.0.

If Bionicpup64 8.0 was 4GB in size. It could come with every possible driver and firmware, already installed.
Not going to get every possible thing in a 300 to 400 MB OS.

I asked to have "nvidia" instead of "nouveau" driver to have better video performances. If it doesnt work with some old hardware (which is rare nowadays),

I have some old Nvidia hardware that the latest Nvidia driver will not support.
The last driver to support it was the Nvidia 173 series ones.
I can not even compile that driver in Bionicpup64 8.0
The software the diver package wants to use for compiling is too old or no longer used.
Even if it would compile.
Bionicpup64 8.0 is using to new of everything else, to get it to run.

Puppy Linux tries to support as much older hardware as possible.
Generic graphics drivers OTB do that.

[linuxcbon]

"Nouveau" just works with most of the cards but "nouveau" performance is bad.
Nvidia pets are about 50 Mb. So bionicpup can stay small with nvidia drivers.
Nvidia drivers support until GeForce 8 (goes back to 2006). And it's possible to select "nouveau" for older cards with xorgwizzard.

[linuxcbon]

Bionicpup64 8.0 CE

Python2 is coming to end of life on January 1st 2020 and is replaced by python3.
What programs in bionicpup need python2 ? Can they be updated or replaced to use python3 instead ? Then it will be possible to remove python2 and use python3 instead.

Cheers

[cattledog]

I'm running bionicpup64 on a frugal USB install. I didn't encrypt anything during the install. During boot, the only thing I am prompted for is my username and password. Is there a way to encrypt the OS or my current savefile with LUKS? If so, how? Thanks.

[bigpup]

666philb,
This is something you may want to have for Bionicpup64 8.0
http://www.murga-linux.com/puppy/viewto ... 11#1042511
This person needed support for the RTL8188FTV USB wireless adapter.
ozsouth has made and posted the needed driver pet.