Puppy Linux Discussion Forum

this is the continuation of the dpupbuster thread.
.
http://murga-linux.com/puppy/viewtopic. ... 16#1031716.

Those who use the previous version is no longer compatible with this because they changed the places of the bookstores. so the devx will not work either.

It is the new base dpup Buster 64, using the latest woof-ce.
I really like this woo-ce. They are doing a great job. All congratulations deserve.

the kernel he uses is 4.19.23 dpupbuster64
As everyone will know, this is based on Debian Buster.

Arrow Minimalist desk JWM .

Use PULSEAUDIO.
RETROVOL was replaced by PASYTRAY.
Pulseaudio is more compatible, many programs use it (skype, firefox, Simplescreen recorder).
It should be clear that pulseaudio is only working in root. is not walking in SPOT..

Pkg - CLI package manager ( Thank you sc0ttman).
I love this program, and it works great. You can use apt-get to install programs.
Also Pkg as the PPM, they use only Debian Buster repo.

Download Dpupbuster

Dpupbuster 32 no-pae JWM
https://sourceforge.net/projects/dpup/f ... 072020.iso

Dpupbuster 32 PAE JWM
https://sourceforge.net/projects/dpup/f ... 072020.iso

Dpupbuster 32 XFCE Desktop
https://sourceforge.net/projects/dpup/f ... 092020.iso

Dpupbuster 32 no-pae openbox
https://sourceforge.net/projects/dpup/f ... 072020.iso

Dpupbuster 32 PAE openbox
https://sourceforge.net/projects/dpup/f ... 072020.iso

Dpupbuster 32 Intel Atom
https://sourceforge.net/projects/dpup/f ... 072020.iso

Dpupbuster 64 Mate Desktop
https://sourceforge.net/projects/dpup/f ... 092020.iso

Dpupbuster 64 JWM
https://sourceforge.net/projects/dpup/f ... 082020.iso

Dpupbuster 64 XFCE Desktop
https://sourceforge.net/projects/dpup/f ... 092020.iso

Dpupbuster 64 LXDE Desktop
https://sourceforge.net/projects/dpup/f ... 122020.iso

Dpupbuster 64 Openbox Desktop
https://sourceforge.net/projects/dpup/f ... 122020.iso

Dpupbuster 64 Fluxbox Desktop
https://sourceforge.net/projects/dpup/f ... 112019.iso

Repo dpup 64
https://sourceforge.net/projects/dpup/files/64bit/

Repo dpup 32
https://sourceforge.net/projects/dpup/files/32bit/

TerryH wrote: ↑Tue Aug 25, 2020 10:47 pm Last week I updated the rc 2 version of the basic DpupBuster64 JWM release to the RC3 release. The Seamonkey 2.53.2 included in this release lags so much on my laptop (details in signature), it is unusable. Other software is functioning OK.

Seamonkey Versions 2.49.5 (Fatdog64 810) & 2.53.3 (EasyOS / EasyPup) are working well. I was pleased when I saw that seamonkey was now included, but it is not functioning well in this installation.

darry19662018 wrote: ↑Sat Oct 03, 2020 7:15 am Congrats Jose on the new releases - this should be an official Pup - hint hint especially for 32bit especially.

thinkpadfreak wrote: ↑Fri Oct 09, 2020 1:37 am When run as root, Chrome produces sound.

josejp2424 wrote: Use PULSEAUDIO.
RETROVOL was replaced by PASYTRAY.
Pulseaudio is more compatible, many programs use it (skype, firefox, Simplescreen recorder).
It should be clear that pulseaudio is only working in root. is not walking in SPOT..

TerryH wrote: ↑Fri Oct 09, 2020 2:11 am from the first post on this thread:

josejp2424 wrote:
Use PULSEAUDIO.
RETROVOL was replaced by PASYTRAY.
Pulseaudio is more compatible, many programs use it (skype, firefox, Simplescreen recorder).
It should be clear that pulseaudio is only working in root. is not walking in SPOT..

pcm.spot { type hw; card PCH; }
ctl.spot { type hw; card PCH; }

pcm.!default pcm.spot
ctl.!default ctl.spot

thinkpadfreak wrote: ↑Fri Oct 09, 2020 6:48 amThanks, TerryH.
It was careless of me to overlook the piece of information.

I wonder if pulseaudio is not available to non-administrator on other distributions, either.
It is a pity that Chrome run as spot doesn't produce sound, though I myself don't mind running Chrome as root.
So I searched the Internet and found a solution.

https://superuser.com/questions/273561/ ... lsa-device
...
(Edit: The above method is bypassing pulseaudio.)

wiak wrote: ↑Sat Oct 10, 2020 6:51 am

thinkpadfreak wrote: ↑Fri Oct 09, 2020 6:48 amThanks, TerryH.
It was careless of me to overlook the piece of information.

I wonder if pulseaudio is not available to non-administrator on other distributions, either.
It is a pity that Chrome run as spot doesn't produce sound, though I myself don't mind running Chrome as root.
So I searched the Internet and found a solution.

https://superuser.com/questions/273561/ ... lsa-device
...
(Edit: The above method is bypassing pulseaudio.)

Actually, TerryH identified this issue to me some months ago on WeeDogLinux forum, albeit the other way round, with WeeDogLinux Arch64. Running pulseaudio/Chromium as non-admin user login actually works fine on WDL Arch64. Also, if the user chooses to autoboot as root user then Chromium works fine with pulseaudio (daemon started by root), as long as Chromium is itself run as root user. Trying to run Chromium as any non-root user (e.g. weedog), when logged in as root, pulseaudio sound stream can't be found, which makes sense per my answer to TerryH here:

https://weedoglinux.rockedge.org/viewto ... p=213#p213

I've never looked into the issue further since, as I say, if user instead autoboots as weedog normal user, both pulseaudio sound and Chromium work fine (since both then started by normal user weedog), or if user autoboots as root user again pulseaudio and Chromium work fine.

i.e. the issue only arises if you try to run Chromium as weedog say, but pulseaudio has been started as root - i.e. don't mix the two since normal user doesn't have access to the sound stream started/owned by root, but no issue finding pulseaudio sound stream if that also started as normal user weedog. So regareding question above "I wonder if pulseaudio is not available to non-administrator on other distributions, either(?) - the answer is that pulseaudio IS available to non-administrotor in most other distros than Puppy (such as full-multiuser capable WeeDogLinux), just don't mix starting up one with root and the other with non-admin user... I suspect therefore that pulseaudio will work with Chromium run as spot in Puppy as long as you startup pulseaudio as user spot as well.

wiak

login spot

export DISPLAY=:0

killall pulseaudio && pulseaudio -D

passwd spot

blackgatonegro wrote: ↑Sat Oct 03, 2020 2:32 am Thanks Jose, I no longer have a 32 bit computer, the one I had died, but I will be testing the Mate 64 version of this puppy. Thank you for making a 32 bit puppy, many people still do need those.

darry19662018 wrote: ↑Sat Oct 03, 2020 7:15 am Congrats Jose on the new releases - this should be an official Pup - hint hint especially for 32bit especially.

TerryH wrote: ↑Sat Oct 03, 2020 10:40 pm

darry19662018 wrote: ↑Sat Oct 03, 2020 7:15 am Congrats Jose on the new releases - this should be an official Pup - hint hint especially for 32bit especially.

Thanks for posting this information. Without your post I and probably everybody else wouldn't have known that there are updated releases available. I hope that future releases will have a post advising of new releases, rather than people just finding that the first post has been updated.

That being said, I downloaded the 64 bit Mate iso and did a new frugal install to to my internal SSD with USB UEFI boot device. This is a brilliant release. It is so polished and runs so well from initial booting. Wifi connected withoout issue, Seamonkey running very smoothly. Due to inclusion of pulseaudio, I connected bluetooth ear phones without issue. Everything else run so far works without issue.
Only minor issue, some fonts are not clearly readable on the backgrounds of message boxes. This seems to occur in other default Mate distributions also, not only this distribution.

@josejp2424 Congratulations, this is an excellent release. Thank you for continuing to work on these DPup Buster releases.

thinkpadfreak wrote: ↑Sun Oct 11, 2020 7:29 amFirefox and SeaMonkey require pulseaudio (or apulse) and Chrome (and clones) requires --no-sandbox option [...] I feel it is necessary to have some knowledge [...]

thinkpadfreak wrote: ↑Sun Oct 11, 2020 7:29 amI am afraid that newcomers will be a little confused.

I'm wondering how hard it would be to upgrade qt5. [s]Two[/s] (Correction:)One package[s]s[/s] I want to install appear to require a newer version of qt5 than is available on dpup buster. The packges I tried to install which require a newer version of qt5 are:

[s]

maestral[gui]

[/s] Requires: PyQt5>=5.9[/s] Correction: should be okay with buster.

and

guiscrcpy requries PyQt5<5.16,>=5.14 (see post)

Here is my pip output:

Requirement already satisfied, skipping upgrade: pathtools>=0.1.1 in /usr/local/lib/python3.7/dist-packages (from watchdog>=0.10.0->maestral[gui]) (0.1.2)
Collecting PyQt5>=5.9 (from maestral-qt>=1.2.2; sys_platform == "linux" and extra == "gui"->maestral[gui])
  Using cached https://files.pythonhosted.org/packages/1d/31/896dc3dfb6c81c70164
019a6cbba6ab037e3af7653d9ca60ccc874ee4c27/PyQt5-5.15.1.tar.gz
  Installing build dependencies ... done
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/usr/lib/python3.7/tokenize.py", line 447, in open
        buffer = _builtin_open(filename, 'rb')
    FileNotFoundError: [Errno 2] No such file or directory: '/initrd/mnt/tmpfs/tmp/pip-install-cziiwqcl/PyQt5/setup.py'
    
    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /initrd/mnt/tmpfs/tmp/pip-install-cziiwqcl/PyQt5/

I'm also wondering how feasible it is to have more than one version of qt5 on ones system. For instance can we do something like this:

        LIBDIR=lib64
        export PATH="$PATH:/opt/qt5/bin"
        export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/qt5/$LIBDIR"
        export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:/opt/qt5/$LIBDIR/pkgconfig"
        export QT5_PATH="/opt/qt5/bin"
        export QT5_LD_LIBRARY_PATH="/opt/qt5/$LIBDIR"
        export QT5_PKG_CONFIG_PATH="/opt/qt5/$LIBDIR/pkgconfig"
        export QT5_CPLUS_INCLUDE_PATH="/opt/qt5/include"

viewtopic.php?p=9771#p9771

but with a specific qt version.

Edit: My PYQT5 should be new enough on dpup buster to support maestral[gui] (note I'm testing this on the 32 bit version) but pip doesn't seem to recognize this.

s243a wrote: ↑Fri Nov 13, 2020 3:48 am

I'm wondering how hard it would be to upgrade qt5. Two (Correction:)One packages I want to install appear to require a newer version of qt5 than is available on dpup buster. The packges I tried to install which require a newer version of qt5 are:

Code: Select all

maestral[gui]

[/s] Requires: PyQt5>=5.9[/s] Correction: should be okay with buster.

and

guiscrcpy requries PyQt5<5.16,>=5.14 (see post)

Here is my pip output:

Code: Select all

Requirement already satisfied, skipping upgrade: pathtools>=0.1.1 in /usr/local/lib/python3.7/dist-packages (from watchdog>=0.10.0->maestral[gui]) (0.1.2)
Collecting PyQt5>=5.9 (from maestral-qt>=1.2.2; sys_platform == "linux" and extra == "gui"->maestral[gui])
  Using cached https://files.pythonhosted.org/packages/1d/31/896dc3dfb6c81c70164
019a6cbba6ab037e3af7653d9ca60ccc874ee4c27/PyQt5-5.15.1.tar.gz
  Installing build dependencies ... done
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/usr/lib/python3.7/tokenize.py", line 447, in open
        buffer = _builtin_open(filename, 'rb')
    FileNotFoundError: [Errno 2] No such file or directory: '/initrd/mnt/tmpfs/tmp/pip-install-cziiwqcl/PyQt5/setup.py'
    
    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /initrd/mnt/tmpfs/tmp/pip-install-cziiwqcl/PyQt5/

I'm also wondering how feasible it is to have more than one version of qt5 on ones system. For instance can we do something like this:

Code: Select all

        LIBDIR=lib64
        export PATH="$PATH:/opt/qt5/bin"
        export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/qt5/$LIBDIR"
        export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:/opt/qt5/$LIBDIR/pkgconfig"
        export QT5_PATH="/opt/qt5/bin"
        export QT5_LD_LIBRARY_PATH="/opt/qt5/$LIBDIR"
        export QT5_PKG_CONFIG_PATH="/opt/qt5/$LIBDIR/pkgconfig"
        export QT5_CPLUS_INCLUDE_PATH="/opt/qt5/include"

viewtopic.php?p=9771#p9771

but with a specific qt version.

Edit: My PYQT5 should be new enough on dpup buster to support maestral[gui] (note I'm testing this on the 32 bit version) but pip doesn't seem to recognize this.

hi s243a
sorry for not responding sooner.
thank you for the tests, and i would like to test your qt5 for 32 bits . if possible.
i have qt5 5.14.2 but for 64 bits.

I like the program you use for cell phone.
and I am currently using it.

josejp2424 wrote: ↑Sun Nov 22, 2020 3:02 pm

s243a wrote: ↑Fri Nov 13, 2020 3:48 am

I'm wondering how hard it would be to upgrade qt5. Two (Correction:)One packages I want to install appear to require a newer version of qt5 than is available on dpup buster. The packges I tried to install which require a newer version of qt5 are:

Code: Select all

maestral[gui]

[/s] Requires: PyQt5>=5.9[/s] Correction: should be okay with buster.

and

guiscrcpy requries PyQt5<5.16,>=5.14 (see post)

Here is my pip output:

Code: Select all

Requirement already satisfied, skipping upgrade: pathtools>=0.1.1 in /usr/local/lib/python3.7/dist-packages (from watchdog>=0.10.0->maestral[gui]) (0.1.2)
Collecting PyQt5>=5.9 (from maestral-qt>=1.2.2; sys_platform == "linux" and extra == "gui"->maestral[gui])
  Using cached https://files.pythonhosted.org/packages/1d/31/896dc3dfb6c81c70164
019a6cbba6ab037e3af7653d9ca60ccc874ee4c27/PyQt5-5.15.1.tar.gz
  Installing build dependencies ... done
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/usr/lib/python3.7/tokenize.py", line 447, in open
        buffer = _builtin_open(filename, 'rb')
    FileNotFoundError: [Errno 2] No such file or directory: '/initrd/mnt/tmpfs/tmp/pip-install-cziiwqcl/PyQt5/setup.py'
    
    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /initrd/mnt/tmpfs/tmp/pip-install-cziiwqcl/PyQt5/

I'm also wondering how feasible it is to have more than one version of qt5 on ones system. For instance can we do something like this:

Code: Select all

        LIBDIR=lib64
        export PATH="$PATH:/opt/qt5/bin"
        export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/qt5/$LIBDIR"
        export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:/opt/qt5/$LIBDIR/pkgconfig"
        export QT5_PATH="/opt/qt5/bin"
        export QT5_LD_LIBRARY_PATH="/opt/qt5/$LIBDIR"
        export QT5_PKG_CONFIG_PATH="/opt/qt5/$LIBDIR/pkgconfig"
        export QT5_CPLUS_INCLUDE_PATH="/opt/qt5/include"

viewtopic.php?p=9771#p9771

but with a specific qt version.

Edit: My PYQT5 should be new enough on dpup buster to support maestral[gui] (note I'm testing this on the 32 bit version) but pip doesn't seem to recognize this.

hi s243a
sorry for not responding sooner.
thank you for the tests, and i would like to test your qt5 for 32 bits . if possible.
i have qt5 5.14.2 but for 64 bits.

I like the program you use for cell phone.
and I am currently using it.

I haven't yet tried upgrading qt5 for buster. It seemed like it would be challenging but if you think it's a good idea I can look into it.

@josejp2424
I downloaded the 64 bit openbox (122020) version of the iso. I have two partitions on an hdd. sda1 is formatted ntsf and sda2 is formatted ext4. I made a manual frugal install on sda1 and booted with grub4dos. This booted up OK. I made a few setup changes and set up wifi them shutdown. On shutdown I was offered the choice to save to a file or folder. I chose a folder. This process seemed to work OK and the folder was made on sda2 (ie on the ext4 partition) as /80dpupbuster64/dpupbuster64save. This file seems to be populated (please see attached image). However, on rebooting this file is not loaded so I get a fresh boot each time. 80dpupbuster64 is the folder on sda1 that contains the frugal install. I did wonder about why this was there but as the process of making the save folder is largely automated I can't see that I've done anything wrong. I'd welcome any ideas as how to fix this.

Regards,

Ken.

@keniv
Can you show the entries for it in menu.lst?

Also, can you put (move or copy) /dpupbuster64save in the root of sda2 to see if it is detected?

@foxpup

Can you show the entries for it in menu.lst?

Here's the menu.lst entry for dpupbuster.

title DpupBuster 8.0 (64bit) (sda1/80dpupbuster64)
  find --set-root uuid () 78F3C2FB524E29F8
  kernel /80dpupbuster64/vmlinuz  pdrv=78F3C2FB524E29F8  psubdir=/80dpupbuster64 pmedia=atahd pfix=fsck
  initrd /80dpupbuster64/initrd.gz

Also, can you put (move or copy) /dpupbuster64save in the root of sda2 to see if it is detected?

Tried this but the save folder was not detected and it booted up into a fresh copy.

Regards,

Ken.

Edit: I just had a thought. I've got the 64 bit version of bionicpup 8.0 installed with a save folder which works. The path to this folder is similar to that in dpupbuster ie /sda2/319bionicpup64/bionicpup64save. The menu.lst entry for bionicpup 8.0 is also similar to that of dpupbuster. It's shown below.

title Bionicpup 319 (64bit) (sda1/319bionicpup64)
  find --set-root uuid () 78F3C2FB524E29F8
  kernel /319bionicpup64/vmlinuz  pdrv=78F3C2FB524E29F8  psubdir=/319bionicpup64 pmedia=atahd pfix=fsck
  initrd /319bionicpup64/initrd.gz

It looks to me as if it should also work in dpupbuster but it doesn't. Hope this helps.

@keniv
It looks like the same, but the behaviour is different.

I would guess if pupsave and frugal install were on the same partition, it could not go wrong.

Have you tried leaving out pdev boot parameter? Maybe psubdir? Even pmedia?

@foxpup

Have you tried leaving out pdev boot parameter? Maybe psubdir? Even pmedia?

Have tried all three of above. Works without pdev and pmedia but does not find save folder. Without psubdir does not boot. Complains that it can't find main .sfs. Menu.lst entry now looks like this.

title DpupBuster 8.0 (64bit) (sda1/80dpupbuster64)
  find --set-root uuid () 78F3C2FB524E29F8
  kernel /80dpupbuster64/vmlinuz psubdir=/80dpupbuster64 pfix=fsck
  initrd /80dpupbuster64/initrd.gz

Tried removing the save folder in sda2 and booting using the above menu entry. I booted into a fresh copy of dpupbuster as you would expect. I made some set up changes including setting up wifi and shutdown going through the process of making a new save folder. This was again successful and was again populated. However, on rebooting this save folder was not recognised and I booted into another fresh copy of dpupbuster.

Can I ask if there is anybody using this or any of the other 64 bit dpupbuster 8.0 isos who have actually managed to to make a save folder which works.

I would guess if pupsave and frugal install were on the same partition, it could not go wrong.

This would presumably mean that the frugal install would also have to be on the sda2 (ext4 partition). I have other pups on this machine all frugal installs to sda1 (ntfs partition). Some are old like Racy and have save files. However, as already said I also have 64bit bionicpup and busterdog the frugal installs for which are on sda1 and the save folders are on sda2 and theses work.

I'd be interested to know if it is the case that dpupbuster is supposed to work with the frugal install on an ntfs partition and it's save folder on an ext4 partition or not.

Regards,

Ken.

Also thought of trying psave. Here's the first thing I tried in the menu entry below.

title DpupBuster 8.0 (64bit) (sda1/80dpupbuster64)
  find --set-root uuid () 78F3C2FB524E29F8
  kernel /80dpupbuster64/vmlinuz psubdir=/80dpupbuster64 psave=/dev/sda2/80dpupbuster64/dpupbuster64save-1 pfix=fsck
  initrd /80dpupbuster64/initrd.gz

Also tried

psave=/mnt/sda2/80dpupbuster64/dpupbuster64save-1

and

psave=/sda2/80dpupbuster64/dpupbuster64save-1

None of these work. I was clutching at straws anyway. I'm really baffled by this now.

Regards,

Ken.

I did expect it not to boot without psubdir. But who knows?

I'd be interested to know if it is the case that dpupbuster is supposed to work with the frugal install on an ntfs partition and it's save folder on an ext4 partition or not.

I would expect so. It is built from woofCE.
But I cannot try it myself.
It really is baffling.
You do not feel like investigating the init to find where it goes wrong, do you?

I think it has to be something like this for psave:

psave=sda2:/80dpupbuster64/dpupbuster64save-1

keniv wrote: ↑Mon Jan 11, 2021 4:56 pm

@josejp2424
I downloaded the 64 bit openbox (122020) version of the iso. I have two partitions on an hdd. sda1 is formatted ntsf and sda2 is formatted ext4. I made a manual frugal install on sda1 and booted with grub4dos. This booted up OK. I made a few setup changes and set up wifi them shutdown. On shutdown I was offered the choice to save to a file or folder. I chose a folder. This process seemed to work OK and the folder was made on sda2 (ie on the ext4 partition) as /80dpupbuster64/dpupbuster64save. This file seems to be populated (please see attached image). However, on rebooting this file is not loaded so I get a fresh boot each time. 80dpupbuster64 is the folder on sda1 that contains the frugal install. I did wonder about why this was there but as the process of making the save folder is largely automated I can't see that I've done anything wrong. I'd welcome any ideas as how to fix this.

Regards,

Ken.

you should create the installation folder on sda2 which is ext4.
and there create the save.

you could look at the file. /etc/rc.d/PUPSTATE .
if the save specifies the correct address.

greetings