Re: JammyPup32 (UPupJJ+D-22.04) JammyJellyfish+Debian Woof-CE build 25-Apr-2022
Fixed.
Discussion, talk and tips
https://forum.puppylinux.com/
Fixed.
another problem I noticed vivaldi_3.7.2218.58-1_lxsc_spot.sfs fails to start...
I've got same problem as >@gychang : PPM fails to update, get an error "Packages -puppy-upupjj+d-extra, Location: http;//smokey01.com/peebee/upupjj_d-extra +Downloading...
failed to download, ERROR: Packages-uppy-upupjj_d-extra is missing"
in PPM, when I search for "korean font", about 20 packages show up but NONE can be installed, all fails...
In 32bit PPM, is it possible to download more than one app at a time, like in fossapup64?
disabling touchpad is not retained on reboot... psynclient.conf has the line but touchpad again is active on reboot.
TouchpadOff=1
gychang wrote: Mon May 02, 2022 12:45 pmanother problem I noticed vivaldi_3.7.2218.58-1_lxsc_spot.sfs fails to start...
Vivaldi runs OK for me ..... so its probably an issue with your hardware - maybe your cpu does not have the necessary instructions?
Have you had Vivaldi running on that hardware under any other 32-bit Puppy?
Or any other Chromium derivative?
Have you run Vivaldi in a terminal to see error messages?
I noticed an oddity.
i downloaded and loaded the chromium sfs and it ran perfectly,Then i resized my personal storage and upon reboot chromium was continually crashing.
So my thinking is that perhaps i should of resized "first" before employing the chromium sfs.I have not tried it yet and intend to do so.
Just an observation to make people aware of my own personal experience with jammy so far.Otherwise great puppy as usual.
can't install any korean fonts from PPM. Now the can update the repositories but can't seem to install any korean fonts, there are about 20 if I search but all of them I get an error. "Missing Shared Libraries Existing Libraries that may be in a location other than /lib and /usr/lib" after downloading.
any fix for this ?
Does the method for installing korean fonts work in other Puppies? Could be a bug I guess. I have no experience of such things, but can confirm the same message when I tried via PPM. I don't think fonts depend on shared libraries in the way that the message suggests. I tried grabbing the package font-baekmuk as a .deb from packages.ubuntu.com (as opposed to using PPM). No dependency libraries are listed. Actually I converted it to a .pet but the .deb would probably be OK without conversion. Anyway, I installed it by clicking on the .pet and it does appear in the font selector via pTheme and the GTK theme changer dialog. I don't know how to test it with korean language, but selecting it I see that the english letters look different.
OscarTalks wrote: Tue May 03, 2022 10:45 pmDoes the method for installing korean fonts work in other Puppies? Could be a bug I guess. I have no experience of such things, but can confirm the same message when I tried via PPM. I don't think fonts depend on shared libraries in the way that the message suggests. I tried grabbing the package font-baekmuk as a .deb from packages.ubuntu.com (as opposed to using PPM). No dependency libraries are listed. Actually I converted it to a .pet but the .deb would probably be OK without conversion. Anyway, I installed it by clicking on the .pet and it does appear in the font selector via pTheme and the GTK theme changer dialog. I don't know how to test it with korean language, but selecting it I see that the english letters look different.
Thanks for your efforts, in Bionicpup32, Korean fonts install without any problems, I may just have to copy the *.ttf files in BP32 to Jammy to get the fonts.
Run ppm in terminal - any errors reported?
Maybe try:
Peter:
starts fine from the terminal, tried clicking on PPM configuration as u suggested but no joy. Another of your distro with better PPM (can install multiple files at noce) in bionicpup32 works downloading so I was able to copy the files into Jammy and can read Korean now... Problems solved for now.
Hi, Everything seems to work fine but I have no sound with firefox
petihar wrote: Fri May 06, 2022 2:56 pmHi, Everything seems to work fine but I have no sound with firefox
How did you install? Use the .sfs from Ģet Webbrowser
I wonder if using @fredx181's script that gets Firefox and builds a portable out it which the audio components are all added in, would be a help?
I ran across the script I think on the old forum and I have it somewhere that I will find. Because a very updated Firefox stopped doing sound even with apulse on a Bionic64 that I use as a main work horse daily driver, I ran the script and it ran and built the Firefox portable app and very importantly, the audio worked right away.
move command in JWM crashes. Command in jwmrc-personal allows for a window to be moved without using a mouse. I use "CS-m" keybinding and in fossapup64 works well, but in Jammy it crashes to a blank screen with prompt, tried assigning other keybinding and still crashes. Identical problem has been reported here: https://github.com/joewing/jwm/issues/550
Is there a solution for this problem in Jammy?
I installed Firefox with 'Get Web Browser' from the Internet menu. Sound is working fine here.
Only noticed that there is no icon for Firefox in the menu, just the text 'Firefox'. The icons are located in /opt/firefox/browser/chrome/icons/default, but the icon entry in mozilla-firefox.desktop specifies:
Code: Select all
Icon=/usr/lib/firefox/browser/chrome/icons/default/default48.png
After changing to /opt/firefox/... the icon shows up in the menu.
gychang wrote: Fri May 06, 2022 7:40 pmmove command in JWM crashes.
Is there a solution for this problem in Jammy?
JammyPup uses JWM-2.3.7 by Woof-CE petbuild............ any problems would have to be fixed there............
https://github.com/puppylinux-woof-CE/w ... builds/jwm
JWM-2.4 cannot be used as pthemes are not conpatible.
As an experiment you could try:
http://ftp.de.debian.org/debian/pool/ma ... 1_i386.deb
I seem to vaguely recall this problem surfacing in the past - maybe on the old forum??
peebee wrote: Sat May 07, 2022 6:02 amJammyPup uses JWM-2.3.7 by Woof-CE petbuild............ any problems would have to be fixed there............
https://github.com/puppylinux-woof-CE/w ... builds/jwmJWM-2.4 cannot be used as pthemes are not conpatible.
As an experiment you could try:
http://ftp.de.debian.org/debian/pool/ma ... 1_i386.debI seem to vaguely recall this problem surfacing in the past - maybe on the old forum??
Peter: rebooting after installing the above .deb file, there is no more crashing!. Interestingly in bionicpup32 default jwm no crashing with move command in jwmrc-personal keybinding.
gychang wrote: Sun May 08, 2022 12:17 amPeter: rebooting after installing the above .deb file, there is no more crashing!. Interestingly in bionicpup32 default jwm no crashing with move command in jwmrc-personal keybinding.
@gychang Thank you for testing.
I have raised a Woof-CE issue: https://github.com/puppylinux-woof-CE/w ... ssues/3073
The old-forum link to a similar problem is: https://oldforum.puppylinux.com/viewtopic.php?p=1057882
Can you run dmesg after the crash and report any errors shown?
Thanks
peebee
if happens again will run dmesg...
gychang wrote: Sun May 08, 2022 12:17 amPeter: rebooting after installing the above .deb file, there is no more crashing!. Interestingly in bionicpup32 default jwm no crashing with move command in jwmrc-personal keybinding.
my mistake, it does crash on bionicpup32 also.
Hi peebee, indeed you are right the sfs works very well. It's a mistake on my part, I installed a portable firefox that was lying around on one of my usb keys.... without looking "further than the end of my nose". thank you really for everything you do!
7c949f954a7176e47ee54d6ab1f580a6 JammyPup32-22.04+2.iso
see post #1
- kernel reverts to 5.10 (should now boot from ntfs partition)
- JWM updated to fix move crash
- Woof-CE & Ubuntu updates
Tried the +2, but no joy with the 5.10 kernel on my hardware. Have to use back the 5.4, which is booting fine. No idea what is the culprit.
MagicZaurus wrote: Mon May 09, 2022 2:15 pmTried the +2, but no joy with the 5.10 kernel on my hardware. Have to use back the 5.4, which is booting fine. No idea what is the culprit.
I also tried to frugal install the +2 and failed..., grub error, on 2nd try installs fine. Not sure what I did wrong on 1st try...
Hi!
Installation without problems. Small problem with JWM (frequent error code) when I install the following french langpack. viewtopic.php?t=5166
I installed an older one and everything is back to normal. I will test more deeply in the next few days.
Still great work!
Voila!
Hello.
I tried JammyPup32-22.04+2 and confirmed that it boots from an ntfs partition.
However, the recognition of the touchpad is unstable. The touchpad is sometimes recognized and sometimes isn't. This issue began at the 5.10.106 kernel of JammyPup32 RC. The 5.10.101 kernel was OK as to the touchpad, but it turned out later that it was not capable of booting from an ntfs partition. The 5.10.112 kernel by ozsouth seems better for my machine.
You said before that you switched to the woof-CE kernel-kit. It seems to me that something has gone wrong with kernels since then.
Edit:
The run-as-spot script has been modified, hasn't it? I wonder if the modification is based on woof-CE updates.
Slimjet from the official site failed to start. It started fine on JammyPup32 before.
71826ce039c25bd18a82a308c012080a JammyPup32-22.04+3.iso
see post #1
- busybox and gtkdialog updated - run-as-spot should be fixed
Hello.
I have tried JammyPup32-22.04+3. Slimjet browser run as spot starts fine. Thanks.
Upgraded JammyPup to the latest .iso on the eeepc 701, by booting the previous version to RAM and copying the relevant files from the .iso to the internal SSD, which is way too cramped for large file juggling.
Works great and is surprisingly usable, for a single core Celeron downclocked to 630 Mhz. Hardware is well supported except for the ridicolous 0.2Mp camera, which was pretty useless to begin with. I think this one will be a keeper
EDIT: even the camera is actually detected correctly and all the relevant modules are installed. The built-in apps don't see it however, the workaround I found is to install VLC that works like a charm.