Puppy Linux Discussion Forum

Sir Thank you very much for looking into my pending issue. Egarly waiting to test new release with update kernel settings. I googled my issue. But many of suggestions are beyond my capacity. Daily visiting your popular blog several times for update about easyos or other things.

I have 3 laptops. In may office HP laptop (normal HDD) with UFEI, installed easyos working fine with regular updates and connected to static LAN and linked to Canon Network Printer on static socket port. Another laptop HP laptop at my home town with nvme ssd is not booting. Another old compaq (BIOS) at home at work place is also installed easyos and working fine.

EasyOS version 4.5.2 released - 825 MB
md5sum c6913a08091a7e6bb488609dfc5090f9
http://distro.ibiblio.org/easyos/amd64/ ... 022/4.5.2/
___________________________________________________

I use uextract to open the image...

To install EasyOS to the ext4 partition on the computer internal drive, copy those three files 'vmlinuz', 'initrd' and 'easy.sfs' across.

https://easyos.org/install/easy-frugal- ... ation.html

Instead of menu.lst file

title EasyOS Dunfell (partition sda3 folder easyos)
  find --set-root-uuid () 054a04b8-0f00-11ed-aeb9-287fcfeb4376
  kernel /easyos/vmlinuz rw wkg_uuid=054a04b8-0f00-11ed-aeb9-287fcfeb4376 wkg_dir=easyos
  initrd /easyos/initrd

I change to...

title EasyOS Dunfell (partition sda3 folder easyos)
  root (hd0,2)  
  kernel /easyos/vmlinuz rw wkg_uuid=054a04b8-0f00-11ed-aeb9-287fcfeb4376 wkg_dir=easyos
  initrd /easyos/initrd

Yes, 4.5.2 is out. Blog announcement and download links:

https://bkhome.org/news/202211/easyos-d ... eased.html

If you are interested to see more details about the changes since 4.5.1, here are the github commits:

https://github.com/bkauler/woofq/commit ... f328fafafa

No words to describe my gratitude and happiness. This is BIG update in the history of EasyOS. Please accept my millions of my Namaskaram. This is something like happiness when I got dial up internet connection in Puppy Linux very long back. May be more !!!. U can see my posts about my dial up in your previous blog. Your efforts finally reached the result that I did want.
The HP Laptop was purchase during March 2021. Only now booting EasyOS from SSD-NVME.
Due to anxiety, my password got blocked after several attempts to login. Now posting with new ID. Ramachandra Iyer.

RyPuppy wrote: ↑Tue Nov 22, 2022 2:45 am

I have enabled Direct-Write for the session.
SessionSave.png

During Reboot process, system gives me 4 choice like
1. .. use previous session
2. .. go back to pristine...
etc...
I have to go through initial configuration all over again.

What do I need to do to keep the configuration changes every time ?

I don't understand the question.
You just reboot, you don't have to make any choices.

Upgraded from 4.5.1 to 4.5.2 (origonally was 4.4 and upgrades since), when shutting down was ok when I first added the devx, however after setting it to be loaded it is now stoping at shutdown at acpid:exiting and only a power-switch off works (i tried leaving it for a while in case it was just slow), turning off the devx and it's all ok again, turning it back on and it's stopping at the error again. Not sure what to do or if it's even tracable, but "something's not right somewhere" as they say. Any sugestions? I can blow this box clean and load from start as it's a test box, so i'm not really worried about it, but I thought i'd best at least report it.

scsijon wrote: ↑Mon Nov 28, 2022 5:50 am

Upgraded from 4.5.1 to 4.5.2 (origonally was 4.4 and upgrades since), when shutting down was ok when I first added the devx, however after setting it to be loaded it is now stoping at shutdown at acpid:exiting and only a power-switch off works (i tried leaving it for a while in case it was just slow), turning off the devx and it's all ok again, turning it back on and it's stopping at the error again. Not sure what to do or if it's even tracable, but "something's not right somewhere" as they say. Any sugestions? I can blow this box clean and load from start as it's a test box, so i'm not really worried about it, but I thought i'd best at least report it.

There was one other person who reported that problem at shutdown with acpid.
He waited 4 minutes and then it shutdown.

One "solution" is to disable acpid; right-click on /etc/init.d/acpid, select "Properties" then untick all the "exec" checkboxes.

Well, before resorting to that, maybe try something more forceful to kill acpid.
Let's see, /etc/rc.d/rc.shutdown will run this:

/etc/init.d/acpid stop

The "stop" option in that script:

start-stop-daemon -o -K -x /usr/sbin/acpid

The default is that it sends the TERM signal. Edit the script, see if this works:

start-stop-daemon -o -K -s KILL -x /usr/sbin/acpid

...don't know, maybe that needs to be number "9" instead of "KILL".

Review EasyOS version 4.5.2
frugal install dragging 3 files in easyos folder

1) pFind works correctly in this version

2) Wine works with mp3direct cut app
https://mpesch3.de/

3) I couldn't get samba server to work with my chromebook
I noticed on list of tasks that smbd -D is working however
when I checked if nmbd was working here was message in terminal...

# /usr/bin/nmbd -D
bash: /usr/bin/nmbd: No such file or directory

BarryK wrote: ↑Mon Nov 28, 2022 9:39 am

scsijon wrote: ↑Mon Nov 28, 2022 5:50 am

Upgraded from 4.5.1 to 4.5.2 (origonally was 4.4 and upgrades since), when shutting down was ok when I first added the devx, however after setting it to be loaded it is now stoping at shutdown at acpid:exiting and only a power-switch off works (i tried leaving it for a while in case it was just slow), turning off the devx and it's all ok again, turning it back on and it's stopping at the error again. Not sure what to do or if it's even tracable, but "something's not right somewhere" as they say. Any sugestions? I can blow this box clean and load from start as it's a test box, so i'm not really worried about it, but I thought i'd best at least report it.

There was one other person who reported that problem at shutdown with acpid.
He waited 4 minutes and then it shutdown.

One "solution" is to disable acpid; right-click on /etc/init.d/acpid, select "Properties" then untick all the "exec" checkboxes.

Well, before resorting to that, maybe try something more forceful to kill acpid.
Let's see, /etc/rc.d/rc.shutdown will run this:

/etc/init.d/acpid stop

The "stop" option in that script:

Code: Select all

start-stop-daemon -o -K -x /usr/sbin/acpid

The default is that it sends the TERM signal. Edit the script, see if this works:

Code: Select all

start-stop-daemon -o -K -s KILL -x /usr/sbin/acpid

...don't know, maybe that needs to be number "9" instead of "KILL".

Thanks for the answer, adding (-s KILL) seems to have worked ok, tried adding -v for verbose to it in case it still failed and will leave it in in case it does later. I had already tried leaving it longer (~30min while I had tea) without any change, which is why I reported it.

don570 wrote: ↑Mon Nov 28, 2022 9:43 pm

Review EasyOS version 4.5.2
frugal install dragging 3 files in easyos folder

1) pFind works correctly in this version

2) Wine works with mp3direct cut app
https://mpesch3.de/

3) I couldn't get samba server to work with my chromebook
I noticed on list of tasks that smbd -D is working however
when I checked if nmbd was working here was message in terminal...

Code: Select all

# /usr/bin/nmbd -D
bash: /usr/bin/nmbd: No such file or directory

The path is /usr/sbin/nmbd

There is a bug, that is preventing nmbd to start, see the error log, at /var/log/samba/log.nmbd:

[2022/11/29 16:48:33.840971,  0] ../../source3/nmbd/nmbd.c:906(main)
  nmbd version 4.10.18 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2019
[2022/11/29 16:48:33.842704,  0] ../../lib/util/become_daemon.c:121(exit_daemon)
  exit_daemon: daemon failed to start: Failed to create directory for pid files, check 'pid directory', error code 17

Hmmm, that was fixed in 4.5.1. The fix was announce here, in /etc/samba/smb.conf:

https://bkhome.org/news/202211/easyshar ... e-tlc.html

Somehow "pid directory = /var/run" got reverted. It should be "pid directory = /var/run/samba"
I am going to have to find where the fix got reverted.

BarryK wrote: ↑Tue Nov 29, 2022 9:03 am

Hmmm, that was fixed in 4.5.1. The fix was announce here, in /etc/samba/smb.conf:

https://bkhome.org/news/202211/easyshar ... e-tlc.html

Somehow "pid directory = /var/run" got reverted. It should be "pid directory = /var/run/samba"
I am going to have to find where the fix got reverted.

Looking at /mnt/.easy_ro/easy_sfs/etc/samba/smb.conf, the path is correct:

pid directory = /var/run/samba

...this means, correct in easy.sfs

Ah ha! This looks like the culprit, /usr/local/EasyShare/samba-setup, line 126.

I did check and the line

 find --set-root-uuid () 054a04b8-0f00-11ed-aeb9-287fcfeb4376

in menu.lst file is working properly.

title EasyOS Dunfell (partition sda3 folder easyos)
  find --set-root-uuid () 054a04b8-0f00-11ed-aeb9-287fcfeb4376
  kernel /easyos/vmlinuz rw wkg_uuid=054a04b8-0f00-11ed-aeb9-287fcfeb4376 wkg_dir=easyos
  initrd /easyos/initrd

So I don't need to use
root (hd0,2)
to specify the partition that rooting is done
------------------------------------------------------------------

Bug-fix version 4.5.3 is out:

https://bkhome.org/news/202212/easyos-d ... eased.html

Hey, approaching Xmas!
Summer here in the Southern hemisphere, lots of sunny days ahead, and trips to the beach.

Review EasyOS version 4.5.3

Frugal install on lenovo desktop

1. Checked samba server and it worked fine except I came across strange behaviour...

When I made the mistake of trying to use Easy Share app in Dunfell container I couldn't get it to work.
I have to be in front window to get Easy Share app to work apparently.
.... and another thing I noticed ---> the Alt F6 message disappeared when I tried to use Easy Share app in Dunfell container.
However the Alt-F6 keys did work and I was able to get back to the main window and continue to work.

2. I checked ptm timer SFS and blender 3 SFS and they worked fine in Dunfell container

3. I tried krita 5.1.1 app image and I found that it worked in the short time I tested it,
however there was an unusual bug that I have never seen before. --->
When I drag my mouse over the various brush icons the info windows pop up.
Only one info window is supposed to show at a given time. (see image)

4. There is strange behavior with keyboard layouts that needs attention...

Here is my procedure to duplicate behavior....

I start with frugal install and boot up (pressing ENTER to speed up boot).
When I get to desktop I go thru quick setup and then use keyboard layout to change to azerty keyboard ie 'fr' is chosen
I click yes button to immediately apply and I have a functioning azerty keyboard layout.
When I check /etc/keylayout file I notice that 'us' is still listed as my keyboard option.
I reboot and my keyboard is still azerty ie 'fr'.
I try to get back to qwerty keyboard layboard using keyboard layout app but it
can't make the change.

However I am able to get the change by booting up with '2' key held down.
qwerty keyboard is automatically chosen without my intervention.

____________________________________________________________________

@don570
Regarding your keyboard test, I noticed the same problem when switching from the Canadian-French keyboard layout (cf / qwerty) to the French one (fr / azerty).

I tested latest stable blender 3.4 appimage and it is not usable,
since the subdivision modifier makes the object disappear in window.
https://www.blender.org/download/releas ... 64.tar.xz/
________________________________________________

Wine windows emulator does work in main window...
http://forum.puppylinux.com/viewtopic.p ... 5173f963a4

_______________________________________________________________

Mr. K.
Frugal ease of installation now goes along with distro name.
it's fast , fancy look too .
Could not get right-click menu on this wacom/pen+touch device & easystroke debs or appimage to work ,
so compiled easystroke for easyos<here.
The pet does come with a root/.easystroke folder with my settings
and include 2 libs .Seems ok .EDIT***was not,is now,i think,cleaned 2 symlink,my bad & added a Startup .sh ,.config/autostart easystroke create did not survived restartx,note that it still create one ,some may tell me if it hurt or simply fix it.

Thank you ,
That's a busy productive retirement you got...

Could not get right-click menu on this wacom/pen+touch device & easystroke debs or appimage to work ,

The wacom driver is available but it needs to be un-blacklisted , then reboot.

Paint apps such as krita and gimp should then use the pressure sensitive stylus.

To un-blacklist you must go to the start menu and look for boot manager app that controls drivers and SFS packages that are loaded at boot time.
Find 'wacom' name on list and allow it to load at boot time.

Note that this driver doesn't need to be installed since it is already inside ....
http://distro.ibiblio.org/easyos/amd64/ ... -64.tar.xz
__________________________________________________________________________

I noticed that when EasyOS is installed with a password at boottime,
there appears to be no way to change the password.
It seems to be permanent unless you totally re-install EasyOS.
I suggest a boot option to change the password at boottime and then
reboot your machine.
_________________________

I am testing Momanager.

When I ran Momanager with 'en' locales , I noticed that there was a strange
bug with one of the scripts ---> /mnt/.easy_rw/mainrw/usr/bin/hello_t12s
Perhaps TEXTDOMAIN line in script wasn't correct??
A POT or PO file isn't created for 'hello-t12s'.

Here is the terminal output of Momanager...

create_po_file_from SOURCE_LIST=/tmp/momanager/cache/YESMO_XML
/usr/sbin/momanager #: missing file /usr/share/locales/en/hello_t12s

_______________________________________________________

don570 wrote: ↑Mon Dec 19, 2022 7:08 pm

I noticed that when EasyOS is installed with a password at boottime,
there appears to be no way to change the password.
It seems to be permanent unless you totally re-install EasyOS.
I suggest a boot option to change the password at boottime and then
reboot your machine.
_________________________

Encryption can only be set on empty folders, that's why you can't change the password.
At very first bootup, /mnt/wkg/containers, data, files, releases, .session are created and the password applied to them.
After that, those folders become populated and the password cannot be changed.

You would have to boot up a different distro, then delete all those folders, as well as the 'sfs' folder, leaving just 'vmlinuz', 'initrd' and 'easy.sfs', so it is just like the first-bootup situation, then you can enter a new password.

don570 wrote: ↑Mon Dec 19, 2022 7:16 pm

I am testing Momanager.

When I ran Momanager with 'en' locales , I noticed that there was a strange
bug with one of the scripts ---> /mnt/.easy_rw/mainrw/usr/bin/hello_t12s
Perhaps TEXTDOMAIN line in script wasn't correct??
A POT or PO file isn't created for 'hello-t12s'.

Here is the terminal output of Momanager...

Code: Select all

create_po_file_from SOURCE_LIST=/tmp/momanager/cache/YESMO_XML
/usr/sbin/momanager #: missing file /usr/share/locales/en/hello_t12s

_______________________________________________________

Personally, I use the old momanager, that does not support t12s.
t12s is a translation mechanism different from using gettext. It was developed by old forum member 'technosaurus'.
I do not know what scripts, if any, are still using it.

I see there are scripts /usr/sbin/t12s*

For the upcoming Kirkstone-series, I plan to completely overhaul translation, and might dump t12s completely, and remove the new momanager.
The old momanager was created by me, then L18L (Lutz) kept maintaining it and added t12s support plus a whole lot more.

Having written the old momanager, I understand it better, so might use that only in the Kirkstone-series, and remove the new momanager.
Any good bits in the new momanager can be imported if required.

Found an old post about t12s:

https://bkhome.org/archive/blog2/201112 ... 12s39.html

...it refers to 'HOWTO-internationalization.htm', which is no longer in Easy.
...just checked on woof-CE, it has that file, but no mention of t12s.

Also /usr/sbin/t12s* have been removed. So woof-CE has dumped the t12s method.

Hi,

A Lot of progress in the Os. Congratulations to those who are putting the Effort. Can 2 features be added in future versions:

History Feature: GIMP photo editor shows Last files opened during the Prior sessions. And the list includes pdf files as well. It might be better, if there is a Menu item showing the historical record of the opened files.

The ROX file explorer does not show thumbnails. Some LINUX have this feature, where you can see the pictures displayed on the screen. Nice to have such a file explorer.

Best Regards

Xyz2022 wrote: ↑Tue Dec 20, 2022 7:25 am

Hi,

A Lot of progress in the Os. Congratulations to those who are putting the Effort. Can 2 features be added in future versions:

History Feature: GIMP photo editor shows Last files opened during the Prior sessions. And the list includes pdf files as well. It might be better, if there is a Menu item showing the historical record of the opened files.

The ROX file explorer does not show thumbnails. Some LINUX have this feature, where you can see the pictures displayed on the screen. Nice to have such a file explorer.

GIMP: you would have to contact the GIMP developers.

ROX: does show image thumbnails. Right-click on the "eye" icon.
If you mouse-over the "eye" icon, there is a popup that explains this.

BarryK wrote:

Personally, I use the old momanager, that does not support t12s.
t12s is a translation mechanism different from using gettext. It was developed by old forum member 'technosaurus'.
I do not know what scripts, if any, are still using it.

A feature in the new MoManager that is potentially useful is clicking the create button
will create pot and po files for all the scripts it finds
and stores them altogether in a folder in /tmp
This helps a language pack translator.
LANG has to be set to 'en' for this feature???
___________________________________________

Also I noticed that this folder in /tmp needs to be deleted if momanager is to be used a second time.
_________________________________________________

When I tried to use stable release of krita appimage --> 5.1.4
https://krita.org/en/download/krita-desktop/

I found same bug with hovering my mouse over brush icons.
Fortunately this is not serious.

_________________________________

But when I tried to use appimage in dunfell container ,
it wouldn't launch and I got this popup message....
(see image)

Seen this error before. Not tested on EasyOS, but it could be fixed by, in terminal : modprobe fuse

Fred wrote:

Seen this error before. Not tested on EasyOS, but it could be fixed by, in terminal : modprobe fuse

I just checked and fuse is apparently installed. Two packages listed in ibiblio repository.
https://distro.ibiblio.org/easyos/sourc ... 9.9.tar.gz
https://distro.ibiblio.org/easyos/sourc ... 3.0.tar.gz

I'll check your suggestion at home, but I doubt it will work because the appimage did work fine
in main window. Only Dunfell container showed the problem.
Maybe Barry left fuse out of container for a reason.
______________________________________________________

don570 wrote: ↑Wed Dec 21, 2022 9:41 pm

Fred wrote:

Seen this error before. Not tested on EasyOS, but it could be fixed by, in terminal : modprobe fuse

I just checked and fuse is apparently installed. Two packages listed in ibiblio repository.
https://distro.ibiblio.org/easyos/sourc ... 9.9.tar.gz
https://distro.ibiblio.org/easyos/sourc ... 3.0.tar.gz

I'll check your suggestion at home, but I doubt it will work because the appimage did work fine
in main window. Only Dunfell container showed the problem.
Maybe Barry left fuse out of container for a reason.
______________________________________________________

fuse.ko is builtin to the kernel, not a module.

Containers are intended to be secure, and have a lot of functionality disabled.

Though, security settings can be adjusted, and it is possible to have a container with minimal security.

Have you tried Krita SFS, at easyos/debian/buster?
It is a rather old version, 4.1.7, and will run in a container.

In fact, it has to run in a container, as it is for the EasyOS Buster-series.

Decided to try it... clicked on "sfs" icon, downloaded Krita SFS, it created an icon on the desktop. Yep, works, running in a container.

At startup, reports version is 4.1.7.101

Mouse-over the brush icons, the popups work as expected.