JammyPup32 (UPupJJ+D-22.04) JammyJellyfish+Debian Woof-CE build

[Zedward]

I have trouble with ACPI on mt MacBook Air A1466 laptop. At previous kernel on BionicPup32 when I closed the cover, laptop went to sleep. And here it doesn't react and continues to work

[Zedward]

Package Manager don't work on different machines. It shows apllications, but no result when clicking install.
I updated databases of course...

[peebee]

@Zedward

acpi - suggest you try reverting to the BionicPup32 kernel - just copy and rename the zdrv and vmlinuz files into your frugal install directory and reboot

PPM - works OK for me..... what were you trying to install? from which repo? what errors did you see?

Screenshot051122.png (81.46 KiB) Viewed 3753 times

[Zedward]

I updated databases in PPM, then search for acpitool, for example.
PPM finds it, but then I press to autoinstall or step-by-step install and nothing going on, no reaction from PPM.
I installed it to another machine and get the same

[Zedward]

It was some kind of wierd system errors.
I reinstalled Puppy and now ACPi works correctly.
Problem with PPM was in incorrect russian localisation from TahrPup file (because we have no newest langpack).
Now I have another one problem: I can't disable screensaver after wake up

[peebee]

459778ee5cdc44f4da7a4dfa909173e4 JammyPup32-22.04+8.iso

[proebler]

Notecase configuring window is not showing the check boxes .
How can I fix this?
Thanks
proebler

notecase-options.jpg (37.92 KiB) Viewed 2943 times

[peebee]

Not sure - maybe it needs to be rebuilt..... it's a very old petbuild:
:notecase:|pet|Packages-puppy-tahr-official

https://github.com/puppylinux-woof-CE/p ... 2/notecase

Does it show any errors if run in a terminal??

Meantime............
You could just edit /root/.notecase/notecase.ini

Could maybe try one of the later versions at:
http://distro.ibiblio.org/puppylinux/pe ... lacko15.0/

[proebler]

Not sure - maybe it needs to be rebuilt..... it's a very old petbuild:
:notecase:|pet|Packages-puppy-tahr-official

https://github.com/puppylinux-woof-CE/p ... 2/notecase

Does it show any errors if run in a terminal??

Meantime............
You could just edit /root/.notecase/notecase.ini

Could maybe try one of the later versions at:
http://distro.ibiblio.org/puppylinux/pe ... lacko15.0/

Thank you peebee.
notecase-1.9.8-i686_s700 from /pet_packages-slacko15.0/ fixed the problem.
Lots of error messages from terminal with the original notecase.
Examples:

Code: Select all

** (notecase:12341): WARNING **: 17:11:11.119: Invalid borders specified for theme pixmap:
        /usr/share/themes/Windoz10/gtk-2.0/menu.png,
borders don't fit within the image

(notecase:13162): GdkPixbuf-CRITICAL **: 17:16:19.390: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

** (notecase:13162): WARNING **: 17:16:19.392: Pixbuf theme: Cannot load pixmap file /usr/share/themes/Windoz10/gtk-2.0/select.png: Failed to load image “/usr/share/themes/Windoz10/gtk-2.0/select.png”: Fatal error in PNG image file: bad parameters to zlib

Regards proebler

[peebee]

Lots of error messages from terminal with the original notecase.
Examples:** (notecase:12341): WARNING **: 17:11:11.119: Invalid borders specified for theme pixmap:
/usr/share/themes/Windoz10/gtk-2.0/menu.png,

Maybe just for interest try a different theme?

[proebler]

Maybe just for interest try a different theme?

I have done some testing, going through the offered themes.
431 and Dark Blue do not show the tick boxes (for NoteCase), but allow to toggle the settings nevertheless.
The UPupJJ+D theme does not show the tick boxes and does not toggle the settings.
With the other themes the NoteCase configuring works ok.
Regards proebler

[proebler]

Upupjj+D-22.04
Problem with pMount.
After booting, pMount incorrectly displays and mixes up partition sda9 with sda8.

In pMount, when I click sda9 to 'Show Location', sda8 is shown.
In pMount, when I (un)Mount sda9, then sda8 gets unmounted.
In pMount, when I (un)Mount sda8, then sda9 (un)Mount remains highlighted but sda9 'Show Location' is now empty.
Re-mounting sda8 brings back the incorrect sda9.

pMount-problem.jpg (215.08 KiB) Viewed 3086 times

sda8 gets mounted with rc.local.
/mnt is correct, GParted also is correct.
If I choose to have icons for each partition displayed on the desktop, they display correctly , i.e. sda9 is not mounted but will mount the correct location when clicked.

(edit)
more weirdness with pMount
I unmounted sda9 then re-mounted it; with that 'Show Location' sda9 was correct.
BUT now sda8 could no longer be mounted and 'Show Location' sda8 displayed sda7.
To make sd8 accessible again I had to change the desktop to show all partitions.

Any suggestions for remedy?
Thanks proebler

[peebee]

Upupjj+D-22.04
Problem with pMount..

Is this with a pristine install? I.e. with nothing added....?

I can't test as I don't have that many partitions

Have you run pmount from a terminal? Any errors?

[proebler]

Is this with a pristine install? I.e. with nothing added....?

Have you run pmount from a terminal? Any errors?

No, not exactly pristine. I have a 128 MB save file of which 55MB are used. My customizations are mainly in .iwm but have this in rc.local:

Code: Select all

mkdir -p /mnt/sda8; mount -t ext4 /dev/sda8 /mnt/sda8 #pmount

Running a pristine Upupjj+D-22.04, pMount works ok.
So what I am experiencing seems really weird.
There are no errors when running pMount from terminal.
There seems to be some conflict when mounting both sda8 and sda9.
On one occasion I have unmounted both, then mounted sda8 , followed with mounting sda9, this resulted in an error note that sda9 could not be mounted. However it then DID mount.

Exact sequence (after reboot) to confirm:
- accessed a text file on sda8 to write the sequence
- open pMount through 'drives' on desktop, situation is as described/shown in my previous post
- unmount sda9 which makes it grayed out , NOTE: Geany gives me notice that the text file on sda8 is no longer accessible! trying to save fails (see screen shot).
- in pMount, 'Show Location' for sda8 confirms that it is not accessible
- unmount sda8 which makes it grayed out
- mount sda8 mounts it immediately in new rox filer window, closed the window
- mount sda9 mounts it immediately in new rox filer window, closed the window
- 'Show Location' for sda9 opens sda8 in rox filer window i.e. in pMount sda9 has effectively become sda8
- unmount sda8 which makes it grayed out, sda9 remains highlighted
- 'Show Location" for sda9 opens sda8 in rox filer window , BUT it is an empty window without any files or directories, closed the window
- unmount sda9 which makes it grayed out
- mount sda9 > brings up error note (see screen shot) , but it has mounted and is accessible with 'Show Location'; pMount size field for sda8 has turned dark (from gray)
- 'Show Location' for sda8 opens sda7 (!) in rox filer window
- screen shot 'pMount-shows-sda8-as-sda9'
- unmount sda9, pMount size field for sda8 remains dark, sda8 remains inaccessible from pMount.
- get desktop to show all partitions so that I can mount sda8 to save the notes and move the screen shots there too
- refresh pMount , it is correct for sda8 but again sda9 is false.

Geany-error.jpg (27.64 KiB) Viewed 3014 times

sda9mount-fail.jpg (10.76 KiB) Viewed 3014 times

pMount-shows-sda8-as-sda9a.jpg (65.78 KiB) Viewed 3014 times

Regards proebler

[tosim]

@peebee Tried to frugal install on flash drive (holding other Puppies), getting error message re install kernel first. Your suggestions, please. Thanks.

[peebee]

@peebee Tried to frugal install on flash drive (holding other Puppies), getting error message re install kernel first. Your suggestions, please. Thanks.

No idea on scant info provided..... you must be doing "something" wrong.....

[tosim]

@peebee Thanks for the reply. I|'ll try again.

[proebler]

@peebee
pMount problem:
From a pristine boot, nothing set yet.
As long as none of the partitions is mounted, pMount appears normal.
As soon as a partition is mounted via the desktop icon, pMount shows up incorrectly (pristine.jpg); in this case sda6 was mounted.

pristine.jpg (95.54 KiB) Viewed 2947 times

I then unmounted the partition(s) and Refreshed pMount, which returned to the normal state (#2.jpg).

#2.jpg (48.71 KiB) Viewed 2947 times

Subsequently mounting a partition with pMount appears to work correctly -sda6 mounted-, but a Refresh of pMount again puts it into an incorrect state (#3+#4.jpg)

#3+#4.jpg (92.21 KiB) Viewed 2947 times

Regards proebler

[proebler]

@peebee
pMount problem:
This may 'nail' it ?
I ran a pristine Dpup Stretch_7.5 and encountered no problem.

pristine_stretch-7.5.jpg (86.16 KiB) Viewed 2910 times

No problem either with ScPup32_20.01
But with S15Pup32 the problem is the same as with Upupjj.
Regards proebler

[peebee]

Both Dpup Stretch_7.5 and ScPup32_20.01 are quite old builds.....

https://github.com/puppylinux-woof-CE/w ... bin/pmount
shows pmount was last changed in 6/2022

I have tried s15pup32_22.12 and ScPup32_22.02 and upupjj+d_22.04
and they all seem to behave consistently on my desktop with 3 drives but less partitions (4 at most) than you have.

In all cases, pmount refresh has to be pressed to reflect changes made via the desktop icons.

Is anybody else (with many or fewer partitions) seeing the problems reported by @proebler ??

Can you provide a step-by-step sequence of actions to demonstrate the problem please? if so, we can raise a GitHub issue.....

[proebler]

@peebee
I have now replaced /usr/sbin/pmount, first with the one from JammyPup32-22.04+0, then with the one from ScPup_20.01.

x3-pmount.jpg (65.96 KiB) Viewed 3200 times

For me, pMount works without problem with the script from ScPup_20.01.
I am happy with that.
Perhaps you can notify the 'dog handlers' at Github.
Perhaps it is an example of: 'if it ain't broke, don't fix it !' ?

It is a great thing to have the save-file for testing. Long live Puppy.

Thanks & woofwoof
proebler

[peebee]

@proebler

Github issue raised:
https://github.com/puppylinux-woof-CE/w ... ssues/4021

[proebler]

@peebee
Thanks.
Re.Github

do not handle his partitions (9 named sda1 to sda10 less sda4) correctly particularly sda8 and sda9

it would be more correct to say, that any of the partitions are handled incorrectly, not just sda8 and sda9.
See the screen shots where sda6 is mounted.

(edit)
It applies even when there are only two partitions.
Best demonstrated by booting Upupjj from a USB drive.
Assuming that no partition of the HDD gets auto mounted:
- open pMount
- from pMount mount the first partition (sda1)
- refresh pMount, it will then be in the erroneous state: 'Show Location' for sda2 will open sda1
- in pMount , unmount sda2 > BOTH sda1 and sda2 will be unmounted

NOTE that if the HDD has only two partitions and the 2nd is mounted first, then pMount will work OK to open the 1st partition also. BUT if the 2nd is subsequently unmounted and pMount refreshed, it will again be in the erroneous state ...etc.

regards proebler
(sorry, I don't mean to be a pain)

[gyrog]

'pkg-chooser.sh' tries to write to '/opt/scpup/'. This directory does not exist.
Perhaps it should be '/opt/upup/'.

The result is that Puppy Package Manager keeps on displaying a hint message, when it says it will do this only once.

Work-around: create a '/opt/scpup/' directory.

[peebee]

@proebler

pmount problem now fixed: (thanks for reporting)
https://github.com/peabee/releases/rele ... anded=true
https://github.com/puppylinux-woof-CE/w ... 76bda4ab7b

also problem reported by @gyrog

[Chelsea80]

Request -

I have had a hunt around, no luck, so -

Is there a version of VLC that would work on JammyPup32 (UPupJJ+D-22.04) JammyJellyfish+Debian -

If so then please provide a link to it -

NB: I have tried the version for BionicPup32, no go -

Thank you -

Best regards

Chelsea80

[peebee]

At:
http://archive.ubuntu.com/ubuntu/pool/universe/v/vlc/

there are still i386 builds - e.g.:
vlc_3.0.18-2build1_i386.deb

but probably many dependencies needed ...... including probably / maybe Qt5

[Chelsea80]

@ peebee

Thank you for your response -

Downloaded the vlc_3.0.18-2build1_i386.deb

Unfortunately it didn't run -

Probably many dependencies needed turns into definitely many .....

So I will have to live without VLC -

Shame really because it's a nice bit of kit -

=========================

Just a fill out -

Had been with BionicPup32 until EOL and you discontinuing your maintenance of it from when I first started using Puppy -

Now with your JammyPup32 LTS -

Many similarities between the two, so I am comfortable to continue with it. I do try other Puppies but always come back to my daily OS -

When I go to : https://github.com/peabee/releases/rele ... anded=true

The time line says 8 days or 2 days or as of now, yesterday, and the date of the ISO changes, as of now 230609 -

So I'm guessing you are updating in some way, although I can't understand what -

Would it be possible to edit your first post each time to include a reference to the changes? -

Thank you for the work you do in providing 32 bit Puppies, I enjoy using it -

Best regards

Chelsea80

[mikeslr]

I don't have a JammyPup32 set up. So I can't test them. But you'll find a vlc-2.1.0-nodebs pet along with several other of oscartalks' builds here, https://smokey01.com/OscarTalks/

[Chelsea80]

@ mikesir

Thanks for your help -

Downloaded vlc-2.1.0-i686-nodeps-s14.sfs -

Unfortunately it didn't run -

It seems that VLC will have to be built specifically for JammyPup32 -

Way, way above my head how to do that -

Still it was worth a try at least -

Again, thanks -

Best regards

Chelsea80