Puppy Linux Discussion Forum

@Anacleto
I tried the above but it did not work. I deleted the "test" save file. I don't know where to go from here.

Regards,

Ken.

Hi keniv.

@keniv

I have also tried several things but in the end what I get is a beautiful screen in black.

I extracted the file Puppy_quickpup64_22.01.sfs and I was able to check that JWM files are already included in their great majority, but there is a problem that causes them to work properly, maybe an error in compilation. I continue to investigate having what may be happening, but it seems that it is what happens with some Puppy distributions that are not able to start on some computers because the system is not well adapted. Maybe it necessary has compile again JWM within QuickPub64.

The problem you have is that you can not start the system?

You said you had saved the QuickPup64Save-SDR folder in a safe place. (Very good)

In the worst case if you can not recover it, reinstall the QUICKPUB64 with ISO file and the copy the QuickPup64Save-SDR folder within the created directory.

Regards.

@Anacleto
Hi Anacleto,

I extracted the file Puppy_quickpup64_22.01.sfs and I was able to check that JWM files are already included in their great majority, but there is a problem that causes them to work properly, maybe an error in compilation. I continue to investigate having what may be happening, but it seems that it is what happens with some Puppy distributions that are not able to start on some computers because the system is not well adapted. Maybe it necessary has compile again JWM within QuickPub64.

Thank for all the effort you are putting into this. I wouldn't know where to start.

In the worst case if you can not recover it, reinstall the QUICKPUB64 with ISO file and the copy the QuickPup64Save-SDR folder within the created directory.

Yeah, when I tested the last time I made a new clean save file for the test. When it did not work I deleted it. I think I will do the same again in any further testing though I have still got a copy of the beta6 iso and the SDR save file so I can recover everything no matter what happens.

Regards,

Ken.

QuickPup64 22.01 BETA 7 released

Changes:
* Linux kernel 5.16.10-lxpup64 (thanks @peebee)
* Glibc 2.35
* Bugfix on slackware package updater
* More bugfixes

Download: https://drive.google.com/file/d/169ekQv ... MaZUuxRr2V
MD5 Checksum: ed665e80ff446d7da2bb9b0ca29f05d2

mistfire wrote: ↑Wed Feb 23, 2022 7:25 am

QuickPup64 22.01 BETA 7 released

Changes:
* Linux kernel 5.16.10-lxpup64 (thanks @peebee)
* Glibc 2.35
* Bugfix on slackware package updater
* More bugfixes

Just downloaded and installed beta7. All that was working in beta6 is still working as far as I can see on limited testing. Also all SDR software is still working. I've still not found a way to go from double clicking desktop icons to single clicking. Has anybody got Redshift GUI working?

Regards,

Ken.

@keniv
here is the setting for single click navigation
For desktop
* Right click the desktop and select Desktop Settings
* Click ICONS tab
* Put check on SINGLE CLICK TO ACTIVATE ITEMS

For thunar, go to thunar settings

mistfire wrote: ↑Wed Feb 23, 2022 10:09 pm

@keniv
here is the setting for single click navigation
For desktop
* Right click the desktop and select Desktop Settings
* Click ICONS tab
* Put check on SINGLE CLICK TO ACTIVATE ITEMS

For thunar, go to thunar settings

Thanks for the above. All now working with single clicks.

Has anybody got Redshift GUI working?

Have just tried the version from this thread viewtopic.php?t=573 and it appears to be working but have no idea why the version in the OS does not. I also like pwidgets. I tried this version http://wikka.puppylinux.com/Pwidgets which I think is fairly up to date version. It is supposed to work in most pups. It's nearly working in Quickpup (see attached image). I wondered if you had any ideas on this.

Thanks again,

Ken.

Hi mistfire.

All is working well in you new Beta 7 like others.

I have continued trying to run QuickPup64 with JWM Deskop, and I can open it but with problems, without icons on the desk and several several broken menu accesses. I have fixed it but I still have not found solutions.

Requires a lot of adjustments.

Regards.

Hi.

I do not know if you'll occur to someone else but in the new beta 7 when I want to change the desktop theme does not change or change only for a moment and then when you restart the system just some things change and others do not.

Remember that when the theme is changed, we get into the menu: Applications> Desktop> Appearance.

This is what it does is open the program:

/ursr/bin/xfce4-appearance-settings

What I did is replace the program "xfce4-appearance-settings" by the same executable from the QuickPup64 version 4.

And then it worked correctly.

Regards

Anacleto wrote: ↑Tue Mar 01, 2022 8:32 pm

Hi.

I do not know if you'll occur to someone else but in the new beta 7 when I want to change the desktop theme does not change or change only for a moment and then when you restart the system just some things change and others do not.

Remember that when the theme is changed, we get into the menu: Applications> Desktop> Appearance.

This is what it does is open the program:

/ursr/bin/xfce4-appearance-settings

What I did is replace the program "xfce4-appearance-settings" by the same executable from the QuickPup64 version 4.

And then it worked correctly.

Regards

That's weird, it works nice for me. I will check it further

Hi mistfire.

The problem occurs when I install themes that I put in the post:

https://www.forum.puppylinux.com/viewto ... 935#p49935

Maybe that is not well adapted to this new beta. But in the previous betas they worked well.

However, I have observed that depending on the hardware we have, the programs of some distributions such as QuickPu64, FOSSA, LXPUP, etc ... have a behavior that may be different.

Regards.

Anacleto wrote: ↑Tue Mar 01, 2022 8:32 pm

Hi.

I do not know if you'll occur to someone else but in the new beta 7 when I want to change the desktop theme does not change or change only for a moment and then when you restart the system just some things change and others do not.

Remember that when the theme is changed, we get into the menu: Applications> Desktop> Appearance.

Hi Anacleto,
Is what you are talking about changing that which is shown in the attached image. If it is it is still working for me in beta7. I've just tried changing from Raleigh to Icelake then rebooted and the change persisted.

However, I have observed that depending on the hardware we have, the programs of some distributions such as QuickPu64, FOSSA, LXPUP, etc ... have a behavior that may be different.

I only have one 64bit machine so I can't try it on any other hardware. Sorry, this is probably not much help to you. Hope you get it sorted out.

Regards,

Ken.

Anacleto wrote: ↑Wed Mar 02, 2022 8:19 am

... I have observed that depending on the hardware we have, the programs of some distributions such as QuickPu64, FOSSA, LXPUP, etc ... have a behavior that may be different. ...

Yes, this would be true of both OSes as well as distros. Reason: 2 specifics I can think of

• program version-release differences

• tweaking that devs will do of some programs within their distros for various needs.

This would be cases when used on the same hardware. If one moves from PC to PC, the hardware can also be impactful.

FYI

Hi keniv and Clarity .

Keniv:

In the Samples window In the previous post there are never problems, behaves correctly, for me the problem is in the file browser in this case Thunar.
When I change the theme in this case I use "Classiclook Graphite" shows the following screen.

With dark tone so as not to burn my eyes. But when I re-restart the computer there are windows like the ones that showed in the previous post that keep the configuration, but others like a Thunar who does not keep it.

This is what happens to me, but even though overwrite the file:

/usr/bin/xfce4-appearance-settings

It happens to me again, I do not know what is the reason.

Observe it to see if the same thing happens to you.

Clarity

Everything you say is true. How you say:

If one moves from PC to PC, the hardware can also be impactful.

Using the same distribution as, for example, this is when we find ourselves quickpup64_v22.01 beta 7 using it in two different computers some programs can have different behaviors.

Programs that would not have to behave differently because they are not related to graphic cards, sound cards, wifi ...

Regards.

@Anacleto

for me the problem is in the file browser in this case Thunar

I selected "Classiclook Graphite" then took a screenshot in the file browser (see "Graphite1" image). I then rebooted and took a second screenshot (see "Graphite2" image) I think there is a difference i.e. "Graphite2" is lighter. I repeated this same process with Icelake and I do not see a difference. Is this what you are seeing with "Classiclook Graphite"?

Regards,

Ken.

Hi keniv
@keniv

Then the same problem is happening to you, it don't save you the configuration of Thunar.

It may be that the problem is in Themes created for QuickPup64 do not adapt well to the distribution.

Anyway there is one thing that I come watching from the Betas of QuickPup64 and when I get into some directories I find myself when opening a terminal and typing
for example command :

ls -l 

I get the following response in most executables:

-rwxr-xr-x 1 root root    40472 Oct  3 10:45 xdpyinfo
-rwxr-xr-x 1 root root    14384 Oct  3 10:45 xdriinfo
-rwxr-xr-x 1 root root    35528 Oct  3 10:44 xev
-rwxr-xr-x 1 root root   275448 Jan 29  2021 xfburn
-rwxr-xr-x 1 root root   101688 Oct  3 10:44 xfce4-about
-rwxr-xr-x 1 root root    55776 Oct  3 10:44 xfce4-accessibility-settings
-rwxr-xr-x 1 root root    73864 Oct  3 10:44 xfce4-appearance-settings
-rwxr-xr-x 1 root root   136896 Oct  3 10:45 xfce4-appfinder
-rwxr-xr-x 1 root root   361920 Oct  3 10:45 xfce4-display-settings
-rwxr-xr-x 1 root root    18760 Oct  3 10:45 xfce4-find-cursor
-rwxr-xr-x 1 root root    94080 Oct  3 10:45 xfce4-keyboard-settings
-rwxr-xr-x 1 root root    61248 Oct  3 10:45 xfce4-mime-helper
-rwxr-xr-x 1 root root    91152 Oct  3 10:45 xfce4-mime-settings
-rwxr-xr-x 1 root root    85504 Oct  3 10:44 xfce4-mouse-settings
-rwxr-xr-x 1 root root     1496 May  6  2021 xfce4-popup-directorymenu
-rwxr-xr-x 1 root root     1540 Nov 15 20:35 xfce4-popup-whiskermenu

There should not be a problem because Puppy runs as root, but could happen that some intermediate process does not have those privileges and maybe there are problems.

In any case if I click inside the terminal folder:

chmod 777 *

Then I get :

-rwxrwxrwx 1 root root    40472 Oct  3 10:45 xdpyinfo
-rwxrwxrwx 1 root root    14384 Oct  3 10:45 xdriinfo
-rwxrwxrwx 1 root root    35528 Oct  3 10:44 xev
-rwxrwxrwx 1 root root   275448 Jan 29  2021 xfburn
-rwxrwxrwx 1 root root   101688 Oct  3 10:44 xfce4-about
-rwxrwxrwx 1 root root    55776 Oct  3 10:44 xfce4-accessibility-settings
-rwxrwxrwx 1 root root    73864 Oct  3 10:44 xfce4-appearance-settings
-rwxrwxrwx 1 root root   136896 Oct  3 10:45 xfce4-appfinder
-rwxrwxrwx 1 root root   361920 Oct  3 10:45 xfce4-display-settings
-rwxrwxrwx 1 root root    18760 Oct  3 10:45 xfce4-find-cursor

Maybe I am giving the possibility for anyone entering my computer.

Regards.

mistfire wrote: ↑Wed Feb 23, 2022 7:25 am

QuickPup64 22.01 BETA 7 released

Changes:
* Linux kernel 5.16.10-lxpup64 (thanks @peebee)
* Glibc 2.35
* Bugfix on slackware package updater
* More bugfixes

Download: https://drive.google.com/file/d/169ekQv ... MaZUuxRr2V
MD5 Checksum: ed665e80ff446d7da2bb9b0ca29f05d2

Manual update from beta 6 to 7.

I am having what appears to be an issue with 5.16.10-lxup kernel loading drivers, specifically wifi (also sound). When I run dmesg | grep -i firmware , I don't get any information regarding the iwlwifi driver being displayed. I also couldn't use modprobe. I swapped out the kernel (vmlinuz and zdrv) to use peebee's earlier 5.16.4-lxpup version, wifi connection is established.

Otherwise all working well. Thank you.

QuickPup64 22.01 BETA 8 released

Changes:
* Improved, overhauled, and robust package management.
* Linux kernel 5.16.12-lxpup64
* Updated builtin packages

Download: https://drive.google.com/file/d/1CxF-VZ ... COVWaqa_re
MD5 Checksum: 748cc8abe0e3f11be355be2c2e9b8af7

Downloaded and manual frugal install, all OK.

Note: Th above post has kernel version shown as 5.15.12, it is 5.16.12.

Hi

Trying to find a solution for the problem of failure in the change of theme in Thunar, I think I can have solved it.
What I do is remove the original installation of XFE4-Power-Manager,
We can do it in two ways:

1) Go to Applications> Setup> Remove Builtin Packages and remove the package -- xfe4-power-manager

2) The second method is that I made a script that eliminates all the files from XFE4-Power-Manager, we give you all permissions through:

chmod 777 xfe4_rm.sh

and then execute it.

Then I install the XFE4-Power-Manager PET file:

At the moment it seems that it keeps me the configuration of theme in Thunar.

Regards

TerryH wrote: ↑Wed Mar 09, 2022 8:49 pm

Downloaded and manual frugal install, all OK.

Note: Th above post has kernel version shown as 5.15.12, it is 5.16.12.

Typographical error has been fixed.

Just tested quickpup64_22.01-beta-8

"Icon artifacts on system-tray on xfce4-panel." looks like overlap icons.

"remaster puppy" is not working properly since 21.08-beta6.
After remastering the sound is totally dead.
Is there any fix for it?
Thanks!

esos wrote: ↑Fri Mar 11, 2022 10:44 pm

Just tested quickpup64_22.01-beta-8

"Icon artifacts on system-tray on xfce4-panel." looks like overlap icons.

"remaster puppy" is not working properly since 21.08-beta6.
After remastering the sound is totally dead.
Is there any fix for it?
Thanks!

What problems did you see on remaster puppy?

QuickPup64 22.01 BETA 9 released

Changes:
* Linux kernel 5.17.1
* Under-the-hood optimization
* Improved NTFS3 mounting
* Pipewire ready. Just install pipewire and the sound server automatically switch to pipewire upon restarting Xorg server.
* Some bugfixes

Download: https://drive.google.com/file/d/1LZyVzM ... OSRz-flAyO
MD5 Checksum: 46e0caad305a74a52eb0d9710162d771

Booted ISO file directly via SG2D. Everything behaves as expected. After initial setup, I shutdown and rebooted by accepting the 1st QuickPUP64's stanza without any changes. QP found its saved session on the HDD's "/Sessions" folder and opens the desktop with all changes from the prior session...as expected. NICE!

Seamonkey is current at v2.53.11.1.

Installed Chrome v100 and QT5. These, along with Multimedia apps, run without issues.

2 ISSUES

• One issue found was attempting to get PPM to install QEMU 6.2: If fails! A resolution that did work is to use a QEMU PET that @norgo has (you'll need to PPM him for it). I needed to install jemalloc from the PPM. I used the PET's qemu_gui, booted this version of QuickPUP64 in a vPC. All is well, responsive, and fast in both the host as well as within the VM.

• The other issue when attempting to setup to allow a folder to be shared, this occurred: Menu>Network>Samba... yields this:

  

  SSM broken.png (8.85 KiB) Viewed 26544 times

Keep it coming.

(post moved)

QuickPup64 22.01 BETA 10 released

Changes:
* Bugfixes on package removal of pkg
* Fixed missing samba simple management tool
* usrmerge file hierarchy ready
* added some samba-utils (e.g. findsmb, mount.smbfs, etc.)
* Improved initrd for handling usrmerge file hierarchy

Download: https://drive.google.com/file/d/1uVfyZM ... 5UcJJiPEcO
MD5 Checksum: f3a3e11558f6d33ea61354877fe77e61

NOTE: QuickPup64 BETA 10 iso file was reuploaded (21:15H GMT+8). Please discard the previously downloaded QuickPup64 Beta 10 due to serious defect

Retested:

• Latest version booting via its ISO as all prior versions have.

• SAMBA util and SSM all are working!

• With no need to interrupt boot at Menu for session changes, boot system finds everything needed, INCLUDING, the save-session from prior Beta 9 changes...Great!

Question: Is it recommended to pristine boot ('RAM only' at boot menu) when going from beta 9 to beta 10 to re-add packages changed from prior session; OR just allow beta 10 to pick up from sessions save in prior beta releases?

Additionally
As I am sure you know, this distro boots directly from its ISO file via both Ventoy as well as SG2D in either a BIOS OR a UEFI PC firmware. No issues in boots.

Thanks for the smooth and cleverly crafted PUP distro.

QuickPup64 22.01 BETA 11 released

Changes:
* Bugfixes on pkg and sfs_load

Download: https://drive.google.com/file/d/1tVPL5K ... InbEy6islJ
MD5 Checksum: 492a34c2c43b329b76aa6b314c516d1d

Same experiences from Beta 10 booting ISO file directly via SG2D USB. It finds the prior save-sessions in the /Sessions folder on my ext4 partiton on the HDD.

The ONLY issue is an older one that exist in the system's "Shutdown app" in the shutdown subsystem. When the Linux formatted partition is selected and a folder approach is chosen, the final screen before exist does NOT allow the user to change the folder.

In the picture, below, the option to allow placement in a folder on the drive is missing. Would be nice if it was available so that user can keep all save-sessions in a folder of choice.

This does NOT affect what happens at boot-time as the QuickPUP64 is finding ALL save-sessions on the drive. BUT, it would be an advantage to direct the shutdown to save it in a user selected folder versus forcing the session into the root of the linix partition. For example, after saving the Beta 11's session, on boot the init processor is showing these boot options:

0 - None
1 - /QuickPup64save-Beta11
2 - /Sessions/QuickPup64save-Beta9
3 - /Sessions/QuickPup64save-Beta10

Can/should this be fixed or reverted to the ability to change the folder on this screen?

All other things seem excellent in behavior