EasyOS version 2.3.2, June 22, 2020

[BarryK]

I compiled SeaMonkey 2.53.2, but it is broken:

https://bkhome.org/news/202005/seamonke ... roken.html

But found a fix, posted to that blog post, which is to delete the entire profile.

I just now went back to the SM site, and they have removed 2.53.2, have gone back to showing 2.53.1 as the latest:

http://seamonkey-project.org/

Apparently, the bug has something to do with gtk3 -- I wish they hadn't dropped gtk2 support!!!!

[oui]

Hi Barry

What is the advantage to use a new compiled Seamonkey instead to unpack those offered ready to use by Seamonkey itself?

Using rox, the installation is fast and easy!

Why will we reinvent the wheel?

- download it there https://www.seamonkey-project.org/releases/ into /root

- hit on it in rox

- mark all (option Select all)

- unpack! (option Extract)

and you get it ready to use in your favorite languages (often including the dictionary you need in your language room ...) in /root/Seamonkey. Hitting on /root/Seamonkey/seamonkey, it appears willing on the screen!

using links with the fast function in rox (hold Ctr + Alt and move not as binary but as link at the destination) it is installed fast in Puppy instead of the precedent one (or instead of palemoon & Co. as the Puppy world is now split concerning that...)

see picture (I did process all that to be sure that it's work as I explain! this is in an Pup NON-PAE (*1 ! in better Puppy's it have to work better!)

(*1 poor Pup NON-PAE but with good working pulseaudio ! It is so wonderful...
.

[oui]

excuse the text error on the picture: as I have Seamonkey 2.32 (*1 preinstalled and /root/mozilla/ for that version preinstalled in my ISOs, /root/mozilla did show the old version number. but 2.53.2 is now installed and starts after erasing /root/.mozilla

(*1 I always have Seamonkey preinstalled in my own ISOs!

[OscarTalks]

This machine I am testing on has 3 sound cards,
1 integrated
1 pci
1 usb
Not sure if that is a factor, but I find that Menu>Multimedia>Alsa Mixer just flashes and aborts.
Same happens in EasyPup.
If I edit the alsamixer.desktop file from urxvt to sakura then alsamixer looks OK.
Running urxvt on its own looks OK, but not if I am trying to run alsamixer within it.

EDIT:- Tried booting the EasyOS flash drive on a different machine with just one sound card and alsamixer looks OK in urxvt so I guess it is specific to my hardware and not a universal issue.

[BarryK]

I intend to get back onto tackling some of the issues that you guys have reported for EasyOS. There was a little holiday, and the last couple of days did a resurrection of Quirky:

https://bkhome.org/news/202005/quirky-8 ... lease.html

Seems to work OK, but don't get the bluetooth applet in the system tray.

I wanted to compare bootup time and general responsiveness between Quirky and EasyOS, and for a level playing field they are both built with Debian Buster 10 DEBs.

Though using 5.4.40 kernel with Quirky, Easy is still on 5.4.27.

[TiredPup]

BarryK wrote:

I intend to get back onto tackling some of the issues that you guys have reported for EasyOS. There was a little holiday, and the last couple of days did a resurrection of Quirky:

https://bkhome.org/news/202005/quirky-8 ... lease.html

Seems to work OK, but don't get the bluetooth applet in the system tray.

I wanted to compare bootup time and general responsiveness between Quirky and EasyOS, and for a level playing field they are both built with Debian Buster 10 DEBs.

Though using 5.4.40 kernel with Quirky, Easy is still on 5.4.27.

I know that this is unsupported. I did want to report on a kernel panic issue that occurred during first boot after full install to the 1st partition of the boot drive (in the event someone else has the same problem). I resolved this by editing the menu.1st to read:

title Quirky Buster64 8.8.1 (sda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 ro

I am posting from this Quirky build using the latest iteration of Vivaldi browser.

UPDATE: I have put some mileage on this setup in the last several hours. This is a polished OS that runs smoothly.

[CHLee]

I intend to get back onto tackling some of the issues that you guys have reported for EasyOS. There was a little holiday, and the last couple of days did a resurrection of Quirky:

https://bkhome.org/news/202005/quirky-8 ... lease.html

Seems to work OK, but don't get the bluetooth applet in the system tray.

I wanted to compare bootup time and general responsiveness between Quirky and EasyOS, and for a level playing field they are both built with Debian Buster 10 DEBs.

Though using 5.4.40 kernel with Quirky, Easy is still on 5.4.27.

Thank you very much. This unofficial-release of Quirky help me very much. I could replace the beaver64-8.7.1 now.
I did full installation and will do heavy compiling jobs. Just testing the Quirky buster-8.8.1 and it works well (gcc-8.3.0, binutils-2.31.1). Thanks you again.

[Billtoo]

I installed Quirky to a usb-3.0 SSD:

Computer
Processor 4x Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Memory 8159MB (173MB used)
Machine Type Physical machine
Operating System Quirky Buster64
Date/Time Mon May 18 10:54:04 2020
Kernel Linux 5.4.40 (x86_64)
Version #1 SMP Wed May 13 21:00:45 +08 2020
Display
Resolution 3840x1080 pixels
OpenGL Renderer NVC1
X11 Vendor The X.Org Foundation
Audio Devices
Audio Adapter HDA-Intel - HDA Intel
OpenGL
Vendor nouveau
Renderer NVC1
Version 4.3 (Compatibility Profile) Mesa 18.3.6
Direct Rendering Y_es

Works okay so far,
Thanks.

[tom22251]

Hi Everyone,

To Barry and TiredPup:

I had the Kernel Panic by installig manually
in one folder named "q881"
the 3 files: vmlinuz, initrd.q and q.sfs.

By examening the older Quirky, April-7 realised
it had only 2 files: vmlinuz & initrd.q, the latter
being quite large (180MB). Of course it contains
the base sfs: q.sfs.
So I did the same with Buster64 8.8.1, put q.sfs
inside initrd.q, and it booted up nicely, no Panic.
And it works as a live installation.

Bootloader is extlinux(4.07) and extlinux.conf:

Code: Select all

default q8
display boot.msg
prompt 1
timeout 111

label q8
kernel /q881/vmlinuz
initrd /q881/initrd.q
append rootwait rw

Thanks Barry,
one small thing: MtPaint doesn't recognise
jpg files, so I used one from EasyOs-211,
works well.

Tom

[BarryK]

one small thing: MtPaint doesn't recognise
jpg files, so I used one from EasyOs-211,
works well.

Thanks for reminding me about that. Something went wrong when I compiled the latest mtpaint. Same issue in latest Easy 2.2.16.

I will recompile it tonight.

[BarryK]

This would seem to distress new users: at first boot-up my wired ethernet device is not found, even though it was working before I booted up EasyOS the first time after installation to the USB flash drive. There was no network icon in the tray. (This is not new misbehaviour.)

I had similar issues when I added nm to lighthouse. Added this to rc.local:

Code: Select all

/etc/rc.d/rc.networkmanager restart

df

Richard (rerwin) posted back on page 162, about this problem, and Dry Falls proposed above response, thaf worked for rerwin.

I am wondering if we could put a fix into /usr/sbin/delayedrun. It currently has this code:

#190215 /etc/rc.d/rc.network_eth brings up interfaces, /usr/local/pup_event/netchg
#is called from pup_event_frontend_d whenever network change, however at bootup
#it might need to be triggered here... only doing this for ethernet... 190217...
if grep -E 'connectwizard| sns' /usr/local/bin/defaultconnect >/dev/null; then
sleep 3
FIP="$(getlocalip | grep '^[^l]')" #test if already a lease assigned.
if [ "$FIP" == "" ];then
CARS="$(grep -H -x '1' /sys/class/net/eth[0-9]/carrier 2>/dev/null)"
if [ "$CARS" ];then
#take lo down then up, will trigger network event, end up calling netchg...
ip link set lo down
ip link set lo up
fi
fi
fi

maybe change it to:

#190215 /etc/rc.d/rc.network_eth brings up interfaces, /usr/local/pup_event/netchg
#is called from pup_event_frontend_d whenever network change, however at bootup
#it might need to be triggered here... only doing this for ethernet... 190217...
if grep -E 'connectwizard| sns| nm-setup' /usr/local/bin/defaultconnect >/dev/null; then
sleep 3
FIP="$(getlocalip | grep '^[^l]')" #test if already a lease assigned.
if [ "$FIP" == "" ];then
CARS="$(grep -H -x '1' /sys/class/net/eth[0-9]/carrier 2>/dev/null)"
if [ "$CARS" ];then
#take lo down then up, will trigger network event, end up calling netchg...
#ip link set lo down
#ip link set lo up
/etc/init.d/rc.networkmanager restart
fi
fi
fi

Maybe could first try with just taking lo down then up, if that doesn't do anything, comment those two lines out and insert restarting rc.networkmanager.

I don't have the problem, so you guys will have to try this.

[ETP]

Hi Barry,

Thanks for the Quirky 8.8.1 unofficial release.
I am posting here as the following audio problems are exhibited by both Easy and Quirky.

mpv

This has 2 problems that I have never observed before with any version of mpv in any Pup or Dog.

Short mp3 files that that typically don't contain meta data specifying their exact length are truncated.
This was seen with TTS & Google translate. So, if the phrase to be spoken was "Words must be extracted"
it is heard as "Words must be extract" (Nothing wrong with the text returned by Google)

IIRC you mentioned this truncation problem in connection with Bluetooth. Mpv is not missing any deps and the
output of mpv --version appears in order. The root cause has so far evaded me but I do not know from where the
various components of mpv were sourced.

The second issue with mpv is lip sync (AKA lip flap) seen when receiving network news streams.
A temporary workaround is to create a global mpv.conf file in ~/.config/mpv/ containing at least the following code:

Code: Select all

audio-delay=-0.190
ad=mp3float

mpg123

Thinking to get around the truncation problem by switching over from mpv to mpg123 for TTS I found that the binary had
gone AWOL and that an additional lib was required. Solved by using petget to install the following:

• libout123-0_1.25.10-2|libout123-0|1.25.10-2||BuildingBlock|85K|pool/main/m/mpg123|libout123-0_1.25.10-2_amd64.deb|+libc6&ge2.15|MPEG layer 1/2/3 audio decoder libout123 shared library|debian|buster||
  
  mpg123_1.25.10-2|mpg123|1.25.10-2||Multimedia;sound|453K|pool/main/m/mpg123|mpg123_1.25.10-2_amd64.deb|+libasound2&ge1.0.16,+libaudio2,+libc6&ge2.15,+libjack-jackd2-0&ge1.9.10+20150825,+libmpg123-0&ge1.25.0,+libopenal1&ge1.14,+libout123-0&ge1.23.8,+libportaudio2&ge19+svn20101113,+libpulse0&ge0.99.1|MPEG layer 1/2/3 audio player|debian|buster||

[BarryK]

Hi Barry,

Thanks for the Quirky 8.8.1 unofficial release.
I am posting here as the following audio problems are exhibited by both Easy and Quirky.

mpv

This has 2 problems that I have never observed before with any version of mpv in any Pup or Dog.

Short mp3 files that that typically don't contain meta data specifying their exact length are truncated.
This was seen with TTS & Google translate. So, if the phrase to be spoken was "Words must be extracted"
it is heard as "Words must be extract" (Nothing wrong with the text returned by Google)

IIRC you mentioned this truncation problem in connection with Bluetooth. Mpv is not missing any deps and the
output of mpv --version appears in order. The root cause has so far evaded me but I do not know from where the
various components of mpv were sourced.

Yes, truncation occurs with bluetooth speakers. That is a problem with blue-alsa, the replacement for pulseaudio. Are you using a bluetooth speaker or headphone?

[BarryK]

So far I have only 2 issues.
One is that setting global keybindings with the GUI app don't work as expected. When assigning new keybindings to an action, the old keybindings remain, so I had to comment those in the keybinding file (root/.jwmrc) to deactivate the old keybindings. Strange enough do I see now that this file is renamed to .jwmrc-previous, that the new .jwmrc has the orginal lines uncommented, but it still works correct, cq uses the file /root/jwm/jwmrc-personal. Don't know why it now works as expected but not before, even after reboot/restarting WM & X server.

Edit 20200410:
After some reboots the old default keybindings are suddenly active again, without any change in the configuration. This is really crazy.
Any idea how I can solve this ?

JWMdesk modifies /root/.jwm/jwmrc-personal with the new key bindings.

The last line of /root/.jwmrc has this:

<Include>/root/.jwm/jwmrc-personal</Include>

I tested a change of a key binding and it worked for me. Check that jwmrc-personal file. if somehow it is getting reverted to the original, that would be the cause of your problem.

[BarryK]

The second issue is with SeaMonkey. I saw in the main-menu SeaMonkey IRC chat client, clicked this, but couldn't find the chat client when SeaMonkey opened. Even chatting (with another app) with #seamonkey@freenode didn't help, cq told that I need to install Chatzilla as browser plugin from the Mozilla site. I think that the menu item should be removed, or tell what you should do to get it working.

Chatzilla has disappeared! It used to be part of the suite.

I just now did some quick reading, it was also builtin to Firefox, got removed in 2017.

Right, I will follow this up, see if Chatzilla can be included.

EDIT:
Hmmm, ChatZilla is still part of the SM suite, but somehow it got left out when I compiled it. Ditto for SM 2.53.2.

I have solved the problem by pulling {59c81df5-4b7a-477b-912d-4e0fdf64e5f2}.xpi file out of the official x86_64 SM tarball and put it in my PET.

This is for SM 2.53.2 so the fix will be in the next release of Easy.

[ETP]

Hi Barry,

Thanks for the Quirky 8.8.1 unofficial release.
I am posting here as the following audio problems are exhibited by both Easy and Quirky.

mpv

This has 2 problems that I have never observed before with any version of mpv in any Pup or Dog.

Short mp3 files that that typically don't contain meta data specifying their exact length are truncated.
This was seen with TTS & Google translate. So, if the phrase to be spoken was "Words must be extracted"
it is heard as "Words must be extract" (Nothing wrong with the text returned by Google)

IIRC you mentioned this truncation problem in connection with Bluetooth. Mpv is not missing any deps and the
output of mpv --version appears in order. The root cause has so far evaded me but I do not know from where the
various components of mpv were sourced.

Yes, truncation occurs with bluetooth speakers. That is a problem with blue-alsa, the replacement for pulseaudio. Are you using a bluetooth speaker or headphone?

Hi Barry,
No, I am not using any form of bluetooth. My line output feeds the MiniDisc input on an old Sony mini system with 2 speakers plugged into the output.
Using mpg123 for multilingual TTS once fixed did solve the truncation problem. It may be that the truncation problem in mpv & the mpv lip sync problem
have a common cause.

[BarryK]

I am attempting to fix the problem that rerwin has reported, ethernet not working at first bootup:

https://bkhome.org/news/202005/improvem ... ction.html

[BarryK]

Hi, first I apologize you for this amazing works.
I love your pragmatic approach for all tools/concept.

(http://distro.ibiblio.org/easyos/amd64/ ... d64.img.gz)

booting live USB easyos-fr-2.2.16, and making a install on a SDD with easydd:

Code: Select all

easydd ./downloads/easy-2.2.16-amd64.img.gz
ERREUR: L'utilitaire dd ne prend pas en charge l'option CLI 'status=progress'

Can't launch easydd (GUI or from terminal)

It seems the dd check "progress" is english related:

Code: Select all

#the full dd is required...
DDTEST="$(dd --help | grep 'periodic transfer statistics')"
[ ! "$DDTEST" ] && err_exit "$(gettext "dd utility does not support 'status=progress' cli option")"

so a quick fix for all langages is :

Code: Select all

#the full dd is required...
DDTEST="$(dd --help | grep 'progress')"
[ ! "$DDTEST" ] && err_exit "$(gettext "dd utility does not support 'status=progress' cli option")"

Have you a gitlab/hub for issues/fix ?

Thanks for reporting that. I fixed it this way:

Code: Select all

DDTEST="$(LANG=C dd --help | grep 'periodic transfer statistics')"

No, don't have a github/gitlab.

[BarryK]

To Barry,
Ref my post on 7th April about strange added bootup text,
and hang on bootup, I eventually found the cause.

It turned out that the initial bootup coloured keyboard
selector has a bug.
On default bootup, if say No.5 is selected then entered
no password, all this strange error text scrolls down.

Instead of pressing default, you have to press the second
one, which auto-corrects the file as it proceeds.
I saw the corrector picked out an error in the No.5 keyboard
descriptor. Thereafter install proceeded normally.
I now have a good install to usb.
Regards.

I have been through the exercise, used easydd to write EasyOS .img.gz file to an old usb stick (a very slow, 3MB/sec Emtec stick).

Accepted the normal default bootup, it resized the working-partition to fill the drive, I chose number 5 for keyboard layout, no password, it booted up fine to desktop, no error messages.

[BarryK]

First problem I encountered was finding the img to download. Second problem was getting it onto a USB-Stick. Destroyed one USB-Stick trying to use Etcher.

That's strange, I have only read good things about Etcher. It is highly recommended by the RaspberryPi community.

But, I haven't tried it myself.

Here are my instructions:

https://easyos.org/install/how-to-write ... drive.html

Anyone else had experience with Etcher? Should I remove the recommendation from that page? Something else instead?

Regarding find the image to download, the first post in this thread has a link to blog release announcements, which has download link. I also post release announcements at end of this thread with link to the blog announcement. Don't know how can do any better than that.