Easy Scarthgap-series version 6.5.4 released
Version 6.5.3 was released on December 28, 2024, see announcement:
- EasyOS Scarthgap-series version 6.5.3 — December 28, 2024
Since then, some important fixes, see 6.5.4 highlights:
- Avidemux compiled in Scarthgap — January 07, 2025
- Fix xkbcomp warning messages — January 05, 2025
- Fix run X11 apps in containers — January 05, 2025
- pRun application launcher updated — January 05, 2025
- Orange-ball menu entries install bug — January 02, 2025
Download:
http://distro.ibiblio.org/easyos/amd64/releases/scarthgap/2025/6.5.4/
Feedback welcome at the forum:
https://forum.puppylinux.com/viewtopic.php?p=139572#p139572
Tags: easy
EasyOS Daedalus-series version 6.5.4 released
Version 6.5.3 was released on December 28, 2024, see blog announcement:
- EasyOS Daedalus-series version 6.5.3 released — December 28, 2024
There have been some important fixes since then. Highlights since 6.5.3:
- Fix xkbcomp warning messages — January 05, 2025
- Fix run X11 apps in containers — January 05, 2025
- pRun application launcher updated — January 05, 2025
- Orange-ball menu entries install bug — January 02, 2025
- AnyDesk now an orange-ball menu entry
Download:
http://distro.ibiblio.org/easyos/amd64/releases/daedalus/2025/6.5.4/
Feedback is welcome at the forum:
https://forum.puppylinux.com/viewtopic.php?p=139569#p139569
Tags: easy
Avidemux compiled in Scarthgap
I have compiled Avidemux 2.8.1 video editor in Easy Scarthgap and created a PET package. It will be in the next release of Easy Scarthgap, install via PKGget, but it will also be an "orange-ball" entry in the menu, Multimedia category.
I haven't compiled it in Easy Daedalus, as got put off by all the dependencies required; for Scarthgap, all deps are already builtin. I see that it isn't in the Debian package repository, which is odd.
Avidemux homepage:
https://avidemux.sourceforge.net/
Tags: easy
Fix xkbcomp warning messages
We have had this issue for a very long time. File /tmp/xerrs.log records stdout and stderr when Xorg is started (see /usr/bin/xwin script), and this is part of it:
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Could not resolve keysym XF86CameraAccessEnable
> Warning: Could not resolve keysym XF86CameraAccessDisable
> Warning: Could not resolve keysym XF86CameraAccessToggle
> Warning: Could not resolve keysym XF86NextElement
> Warning: Could not resolve keysym XF86PreviousElement
> Warning: Could not resolve keysym XF86AutopilotEngageToggle
> Warning: Could not resolve keysym XF86MarkWaypoint
> Warning: Could not resolve keysym XF86Sos
> Warning: Could not resolve keysym XF86NavChart
> Warning: Could not resolve keysym XF86FishingChart
> Warning: Could not resolve keysym XF86SingleRangeRadar
> Warning: Could not resolve keysym XF86DualRangeRadar
> Warning: Could not resolve keysym XF86RadarOverlay
> Warning: Could not resolve keysym XF86TraditionalSonar
> Warning: Could not resolve keysym XF86ClearvuSonar
> Warning: Could not resolve keysym XF86SidevuSonar
> Warning: Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Could not resolve keysym XF86CameraAccessEnable
> Warning: Could not resolve keysym XF86CameraAccessDisable
> Warning: Could not resolve keysym XF86CameraAccessToggle
> Warning: Could not resolve keysym XF86NextElement
> Warning: Could not resolve keysym XF86PreviousElement
> Warning: Could not resolve keysym XF86AutopilotEngageToggle
> Warning: Could not resolve keysym XF86MarkWaypoint
> Warning: Could not resolve keysym XF86Sos
> Warning: Could not resolve keysym XF86NavChart
> Warning: Could not resolve keysym XF86FishingChart
> Warning: Could not resolve keysym XF86SingleRangeRadar
> Warning: Could not resolve keysym XF86DualRangeRadar
> Warning: Could not resolve keysym XF86RadarOverlay
> Warning: Could not resolve keysym XF86TraditionalSonar
> Warning: Could not resolve keysym XF86ClearvuSonar
> Warning: Could not resolve keysym XF86SidevuSonar
> Warning: Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Could not resolve keysym XF86CameraAccessEnable
> Warning: Could not resolve keysym XF86CameraAccessDisable
> Warning: Could not resolve keysym XF86CameraAccessToggle
> Warning: Could not resolve keysym XF86NextElement
> Warning: Could not resolve keysym XF86PreviousElement
> Warning: Could not resolve keysym XF86AutopilotEngageToggle
> Warning: Could not resolve keysym XF86MarkWaypoint
> Warning: Could not resolve keysym XF86Sos
> Warning: Could not resolve keysym XF86NavChart
> Warning: Could not resolve keysym XF86FishingChart
> Warning: Could not resolve keysym XF86SingleRangeRadar
> Warning: Could not resolve keysym XF86DualRangeRadar
> Warning: Could not resolve keysym XF86RadarOverlay
> Warning: Could not resolve keysym XF86TraditionalSonar
> Warning: Could not resolve keysym XF86ClearvuSonar
> Warning: Could not resolve keysym XF86SidevuSonar
> Warning: Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
Those warnings have been there "forever", well, a long time. What is new is that 'xkbcomp' runs three times. Recent versions of Easy have been messing around with fixing the keyboard layout; something has caused this.
I don't know what causes 'xkbcomp' to run three times, but have found the cause of those warnings. The problem only occurs in Scarthgap, not Daedalus. In Scarthgap, the package 'xkeyboard-config' has file /etc/X11/xkb/symbols/inet, which causes the warnings. Debian/Devuan has 'xkb-data' DEB package and its 'inet' file does not cause those warnings.
So now using the 'inet' file from Debian, see commit:
https://github.com/bkauler/woofq/commit/1b3178e700ce3ed1042e9fe6656d82f33997a982
I googled several times trying to find why those warnings are
happening. Lots of people report the problem, but noone found the
cause; not that I could find anyway. So did my own detective work
to track it down.
Wish I knew why 'xkbcomp' is running three times, but no cause
jumps out at me.
Tags: easy
Fix run X11 apps in containers
Alfons reported that X11 apps, such as ycalc, rubix, even lite-xl, do not start in containers. Try to run them in a terminal, and see "cannot load font" error message.
I found the cause. These apps need to load .pcf fonts, that are at /usr/share/fonts/misc; however, the Xephyr nested server does not look there. It does see the TrueType fonts in /usr/share/fonts/TTF
The fix is to explicitly add the path with the "-fp" option when launch Xephyr, see commit:
https://github.com/bkauler/woofq/commit/b1e82d7d7b11335b8c88108fc0343ae345626431
...although seems not needed, explicitly added the "TTF" and
"X11" folder paths as well.
Tags: easy
pRun application launcher updated
You will find pRun in the Utility menu category. EasyOS has version 1.3, rather old, and SteveS advised of a later version:
https://forum.puppylinux.com/viewtopic.php?t=13385
pRun is another creation from Roger (radky in the forum). We use a lot of Roger's apps in EasyOS; very grateful for his contributions.
I have updated pRun to 1.7 which will be in the next release of
EasyOS.
Note, there is a thread on the forum for pRun:
https://forum.puppylinux.com/viewtopic.php?t=3555
Tags: easy
Orange-ball menu entries install bug
Alfons reported this. The Network menu category has an "orange-ball" menu entry for AnyDesk. He installed AnyDesk, and the menu entry changed accordingly, with the icon for the app. OK, except after reboot the menu entry had disappeared. This happens to all the orange-ball menu entries.
The AnyDesk menu entry and the concept of orange-ball menu entries is explained here:
- AnyDesk orange-ball menu entry — December 12, 2024
I found the cause of the problem; it is at line 167 in script /usr/local/orange/orange.install:
sed -i -e "s%^Exec=.*%^Exec=${EN}%" ${DT}
...remove the second "^"
What that bug does, is causes this in /usr/share/applications/anydesk.desktop:
^Exec=anydesk
...which is invalid and will cause anydesk.desktop to get deleted
at next bootup.
Tags: easy
EasyOS Scarthgap-series version 6.5.3
The companion Daedalus-series has also reached 6.5.3:
- EasyOS Daedalus-series version 6.5.3 released — December 28, 2024
If you are new to EasyOS, you will find the 6.5 announcement has useful extra information:
- EasyOS Scarthgap-series version 6.5 released — December 03, 2024
Scarthgap 6.5.3 highlights:
Release notes:
http://distro.ibiblio.org/easyos/amd64/releases/scarthgap/2024/6.5.3/release-notes.htm
Download:
http://distro.ibiblio.org/easyos/amd64/releases/scarthgap/2024/6.5.3/
Feedback is welcome at the forum:
https://forum.puppylinux.com/viewtopic.php?p=138915#p138915
Have fun!
Tags: easy