Discussion, talk and tips
https://forum.puppylinux.com/
Thanks for reporting that, it has been added to the package-list for the next release of easyVoid.
You can install it now if you want, via PKGget. Type "efibootmgr" into the search box.
In 6.0.1 should not be getting that missing libEGL message. I have done it:
Galculator is one of those must-have apps; I have added it to the package-list to be builtin next release.
EDIT: Have just seen your later post, after installing 6.0.1, no longer getting that libEGL. So all is well.
When I tried to extract the ublock0_1.55.1b13.chromium.zip file. Not able to do so. hence I have rebooted to easyKirckstone and got it done !!!. I have installed Ungoogled chrome in EasyVoid. Lot of in built advertisements in the sites. So thought of adding ublock origin via extension. Not possible while trying to add ublock extension. Hope it may be due to ungoogled chrome setting/limitations. Upon search, it can done through unpacked option in chrome by downloading ublock zip file. ublock zip got from "git" is not able to extract in easyVoid. i dont know what exactly causing issue. However done it through easy 5.6.5 and came back to easyvoid for adding the same.!!
Not able to upload zip due to file size. It can be downloaded from here https://github.com/gorhill/uBlock/relea ... romium.zip
Installed and now doing duty. Why dual entry for krickstone ?. easy 5.6.5 and now void has same issue.
:EasyOS Void64 (partition nvme0n1p6, path easyVoid/releases/easy-6.0.1)
COMMENT=EasyOS bootup
PROTOCOL=linux
KERNEL_CMDLINE=rw wkg_uuid=e77f9da7-35db-4b43-a3ef-c773cca9d5c5 wkg_dir=easyVoid/releases/easy-6.0.1
KERNEL_PATH=guid://7eef90f7-8243-42cb-98ea-f6736db46568/easyVoid/releases/easy-6.0.1/vmlinuz
MODULE_PATH=guid://7eef90f7-8243-42cb-98ea-f6736db46568/easyVoid/releases/easy-6.0.1/initrd
:EasyOS Void64 (partition nvme0n1p6, path easyVoid)
COMMENT=EasyOS bootup
PROTOCOL=linux
KERNEL_CMDLINE=rw wkg_uuid=e77f9da7-35db-4b43-a3ef-c773cca9d5c5 wkg_dir=easyVoid
KERNEL_PATH=guid://7eef90f7-8243-42cb-98ea-f6736db46568/easyVoid/vmlinuz
MODULE_PATH=guid://7eef90f7-8243-42cb-98ea-f6736db46568/easyVoid/initrd
:EasyOS Kirkstone64 (partition nvme0n1p6, path easyos/releases/easy-5.6.5)
COMMENT=EasyOS bootup
PROTOCOL=linux
KERNEL_CMDLINE=rw wkg_uuid=e77f9da7-35db-4b43-a3ef-c773cca9d5c5 wkg_dir=easyos/releases/easy-5.6.5
KERNEL_PATH=guid://7eef90f7-8243-42cb-98ea-f6736db46568/easyos/releases/easy-5.6.5/vmlinuz
MODULE_PATH=guid://7eef90f7-8243-42cb-98ea-f6736db46568/easyos/releases/easy-5.6.5/initrd
:EasyOS Kirkstone64 (partition nvme0n1p6, path easyos)
COMMENT=EasyOS bootup
PROTOCOL=linux
KERNEL_CMDLINE=rw wkg_uuid=e77f9da7-35db-4b43-a3ef-c773cca9d5c5 wkg_dir=easyos
KERNEL_PATH=guid://7eef90f7-8243-42cb-98ea-f6736db46568/easyos/vmlinuz
MODULE_PATH=guid://7eef90f7-8243-42cb-98ea-f6736db46568/easyos/initrd
:Puppy Linux dpup (partition nvme0n1p7, path BWpup64)
PROTOCOL=linux
KERNEL_CMDLINE=psubdir=BWpup64 pmedia=ataflash
KERNEL_PATH=guid://b44c818b-3204-4292-b7e9-b79c5ab6c07f/BWpup64/vmlinuz
MODULE_PATH=guid://b44c818b-3204-4292-b7e9-b79c5ab6c07f/BWpup64/initrd.gz
:Puppy Linux s15pup64 (partition nvme0n1p8, path spup15)
PROTOCOL=linux
KERNEL_CMDLINE=psubdir=spup15 pmedia=ataflash
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/spup15/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/spup15/initrd.gz
:Puppy Linux vanilladpup (partition nvme0n1p8, path vaniladpup)
PROTOCOL=linux
KERNEL_CMDLINE=psubdir=vaniladpup pmedia=ataflash
KERNEL_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/vaniladpup/vmlinuz
MODULE_PATH=guid://f6d0c5d3-ea46-411c-a374-14a7e629e78f/vaniladpup/initrd.gz
:Windows 10
COMMENT=Windows bootup
PROTOCOL=chainload
IMAGE_PATH=guid://21e3bf30-0631-40c4-a470-537756576dcc/EFI/Microsoft/Boot/bootmgfw.efi
limine Boot installer windows
BarryK wrote: ↑Mon Jan 22, 2024 12:00 amI posted above, about voidpup having the PPM. Yes, true; however, I have just booted it and the PPM looks like it is taking a back seat.
In the menu, is "Void Package Manager". This is a CLI app, so not a GUI, you have to do it in a terminal.
"vpm" is a wrapper around the full xbps package manager, to make usage simpler. Hmmm, the github project for vpm does not exist anymore.
I presume that it must be still available in the xbps repository. I found a fork of vpm, named "vbm", here:https://codeberg.org/oSoWoSo/vbm
Playing briefly with voidpup, it looks like the ppm is only useful for installing pet packages. You have to use vpm to install void .xbps packages.
I used vpm to install xfe. The package installed and runs. Using vpm installs already installed dependencies, as it does not recognise packages installed in build. 39 dependencies were installed including glibc, etc.
Edit: Packages installed using PKGget are also not identified by vpm, could also be installed again over the already installed package.
TerryH wrote: ↑Mon Jan 22, 2024 1:35 amBarryK wrote: ↑Mon Jan 22, 2024 12:00 amI posted above, about voidpup having the PPM. Yes, true; however, I have just booted it and the PPM looks like it is taking a back seat.
In the menu, is "Void Package Manager". This is a CLI app, so not a GUI, you have to do it in a terminal.
"vpm" is a wrapper around the full xbps package manager, to make usage simpler. Hmmm, the github project for vpm does not exist anymore.
I presume that it must be still available in the xbps repository. I found a fork of vpm, named "vbm", here:https://codeberg.org/oSoWoSo/vbm
Playing briefly with voidpup, it looks like the ppm is only useful for installing pet packages. You have to use vpm to install void .xbps packages.
I used vpm to install xfe. The package installed and runs. Using vpm installs already installed dependencies, as it does not recognise packages installed in build. 39 dependencies were installed including glibc, etc.
Edit: Packages installed using PKGget are also not identified by vpm, could also be installed again over the already installed package.
that's right. sync of vpm and xbps with pkgget is on the to do list, probably the next release.
nnriyer wrote: ↑Mon Jan 22, 2024 1:07 amWhen I tried to extract the ublock0_1.55.1b13.chromium.zip file. Not able to do so. hence I have rebooted to easyKirckstone and got it done !!!. I have installed Ungoogled chrome in EasyVoid. Lot of in built advertisements in the sites. So thought of adding ublock origin via extension. Not possible while trying to add ublock extension. Hope it may be due to ungoogled chrome setting/limitations. Upon search, it can done through unpacked option in chrome by downloading ublock zip file. ublock zip got "git" from not able to extract in easyVoid. i dont know what exactly causing. However done it through easy 5.6.5 and came back to easyvoid for adding the same.!!
Not able to zip due to file size. It can be downloaded from here https://github.com/gorhill/uBlock/relea ... romium.zip
I ran xarchive from a terminal:
Code: Select all
# xarchive `pwd`/uBlock0_1.55.1b14.chromium.zip
dir: /root/.xarchive/wrappers
no wrappers in /root/.xarchive/wrappers
dir: /usr/lib/xarchive/wrappers
Found 8 wrappers
command 7za not found
extentions 7z ignored
command unace not found
extentions ace ignored
command arj not found
extentions arj ignored
command unrar not found
extentions rar cbr ignored
compress and uncompress not found
extention tar.z ignored
commands unzip and zipinfo not found
extentions zip cbz jar ignored
XArchive 0.2.8-6Installed 'unzip' from PGKget, now xarchive works.
Thanks for reporting that, will add 'unzip' pkg to be builtin for next release.
Didnt find in ibiblio the list of all included programs and versions ...
Also not found in the release notes ...
(sorry for the question).
SeaMonkey 2.53.18.1 released January 16, 2024 [specific changes: It now uses gtk3]
I installed it to /files/downloads/seamonkey with root:root for testing.
Some video platforms still use TLS 1.1 transport. I added TLS 1.1 support via:
Edit -> Preferences -> Privacy & Security -> SSL/TLS SSL/tls Protocol Versions > Enable: TLS 1.1
https://www.seamonkey-project.org/releases/
https://archive.seamonkey-project.org/r ... 64.tar.bz2
502a5692cdddad045bc6d66d75769c00 md5 54311341 linux-x86_64/en-US/seamonkey-2.53.18.1.en-US.linux-x86_64.tar.bz2
https://archive.seamonkey-project.org/r ... D5SUMS.txt
Running well on my Lenovo BIOS-box with:
Code: Select all
Processor 2x Intel(R) Celeron(R) CPU E3400 @ 2.60GHz
Memory 3904MB (355MB used)
Display 1920x1080 pixels
Audio Adapter USB-Audio - USB PnP Sound Device
OpenGL Renderer Mesa Intel(R) G41 (ELK)
Printers Samsung_SCX-3400_Series
SCSI Disks USB SanDisk 3.2Gen1On the 6.0.1, trying to run AnyDesk as flatpak. After installing it from flathub:
Code: Select all
# flatpak run com.anydesk.Anydesk
Code: Select all
# su anydesk
# flatpak run com.anydesk.Anydesk
error: Permission denied
#
it does not matter if the following line on /etc/profile is present or not.
Code: Select all
export $(dbus-launch)
Now also Whatsapp starts immediately, regardless if the line is present or not.
Ungoogled Chromium as flatpak from Flapi works, but strangely enough it cannot be set with the dark theme. If you go to chrome://flags and set Force Dark Mode to enabled it stays white. Totally white, regardless of how many times it is restarted. This does not happen on the one from the app-image installer, if I remember well.
Now it seems that the system handles my laptop's battery correctly, even when discharging.
@Federico
From KLV (Kennel Linux Void) this is the adapted from Puppy Linux run-as-spot script. We have it in /usr/local/bin and have user spot in /home/spot owned by spot:spot
Code: Select all
#!/bin/bash
# generic wrapper to run as ${XUSER} (when currently running as root)
# (C) James Budiono 2012, 2017
# License: GPL version 3 or later
#
#set -x
XUSER=spot
PROG="$1"
# if spot-sandbox is present, run the shell inside a sandbox
SANDBOX=
case "$PROG" in
*.AppImage|flatpak|*/flatpak) ;;
dbus-daemon) ;; # Landlock breaks xdg-desktop-portal, which fails to open /proc/%u/root
*) SANDBOX=`command -v spot-sandbox` ;;
esac
CWD=$PWD
CMD=''
while [ "$1" ]; do
CMD="$CMD \"$1\""
shift
done
[ "$CMD" ] || exit
USER_HOME=$(awk -F: '$1=="'"${XUSER}"'" {print $6}' /etc/passwd)
if ! [ "${USER_HOME}" ] ; then
echo "$0 ERROR: could not HOME dir for user $XUSER"
exit 1
fi
CURDIR=$PWD
if [ $(id -u) -eq 0 ]; then
# [ $XAUTHORITY ] && cp $XAUTHORITY ${USER_HOME}/.Xauthority 2>/dev/null
# touch ${USER_HOME}/.Xauthority
# export XAUTHORITY=${USER_HOME}/.Xauthority
[ -z "$XAUTHORITY" ] && XAUTHORITY=/root/.Xauthority
[ -e "$XAUTHORITY" ] && cp $XAUTHORITY $USER_HOME/.Xauthority &&
chown ${XUSER}:${XUSER} $USER_HOME/.Xauthority &&
export XAUTHORITY=$USER_HOME/.Xauthority
# replace all occurences of /root in XDG_* with /home/spot, because we don't
# run a login shell and source /etc/profile.d/*
OLD_HOME="$HOME"
while IFS='=' read NAME VAL; do
case "$NAME" in
XDG_*) export $NAME="`echo "$VAL" | sed -e s~^$OLD_HOME~$USER_HOME~ -e s~:$OLD_HOME~:$USER_HOME~g`" ;;
esac
done << EOF # hack for old busybox, which doesn't understand <() and <<<
`env`
EOF
export XDG_CONFIG_HOME=${USER_HOME}/.config
export XDG_CACHE_HOME=${USER_HOME}/.cache
export XDG_DATA_HOME=${USER_HOME}/.local/share
export XDG_STATE_HOME=${USER_HOME}/.local/state
for i in ${XDG_CONFIG_HOME} ${XDG_CACHE_HOME} ${XDG_DATA_HOME} ${XDG_STATE_HOME}
do
if ! [ -d $i ] ; then
mkdir -p $i
chown ${XUSER} $i
fi
done
export XDG_RUNTIME_DIR=/tmp/runtime-${XUSER}
if [ ! -d ${XDG_RUNTIME_DIR} ] ; then
mkdir -p ${XDG_RUNTIME_DIR}
chmod 0700 ${XDG_RUNTIME_DIR}
chown ${XUSER} ${XDG_RUNTIME_DIR}
fi
if [ -s /tmp/.${XUSER}-session-bus ]; then
. /tmp/.${XUSER}-session-bus
export DBUS_SESSION_BUS_ADDRESS
export DBUS_SESSION_BUS_PID
fi
# close all file descriptors except std{in,out,err}, in case one of
# them points to a file under /root
if [ "$PROG" != "/usr/bin/Xwayland" ]; then
for FD in /proc/self/fd/*; do
FD="${FD##*/}"
[ $FD -gt 2 ] && eval "exec ${FD}<&-"
done
fi
exec su ${XUSER} --session-command /bin/bash -c '
# try to switch to original directory, unless it is under /root
case "'"$CURDIR"'" in
/root|/root/*)
cd "'"$USER_HOME"'"
;;
*)
cd "'"$CURDIR"'"
;;
esac
exec '"${SANDBOX}"' '"$CMD"'
'
else
exec bash -c "exec $CMD"
fi
### END ###
So you can try:
Code: Select all
run-as-spot flatpak run com.anydesk.AnydeskThis is the method KLV uses to run the xbps package manager GUI OctoXBPS when running it as the root user. Otherwise as another user it can be started normally. This is a small modification made to the octoxbps.desktop which is placed in /root/.local/share/applications which makes it local to the root user.
Thank you so much!!
Of course there are no problems on Kirkstone (just tried).
It doesn't seem to work...
Code: Select all
# run-as-spot flatpak run com.anydesk.Anydesk
chown: /home/spot/.cache/doc: Permission denied
If I create a shell script named anydesk.sh on /opt containing the code:
Code: Select all
#!/bin/sh
flatpak run com.anydesk.Anydesk
I get:
Code: Select all
# cd /opt
# run-as-spot anydesk.sh
chown: /home/spot/.cache/doc: Permission denied
-sh: line 1: anydesk.sh: command not found
#
Probably the script only supports commands and not files as parameter.
@Federico
Interesting report. What does /home/spot look like inside? What are the owner and permissions for it?
In KLV the /home/spot directory looks like this:
/home/spot only exists after executing the script at least once in every X session.
@Federico KLV is a true multi-user system. The user spot is created during the build and is added to wheel, video and audio groups. I am not sure yet how it is set up in easyVoid, and if anydesk requires a --no-sandbox parameter when attempting to start it as the root user.
Code: Select all
usermod -a -G audio spot
usermod -a -G video spot
xhost +Federico wrote: ↑Mon Jan 22, 2024 7:31 pmOn the 6.0.1, trying to run AnyDesk as flatpak. After installing it from flathub:
Code: Select all
# flatpak run com.anydesk.Anydesk
Why didn't you use Flapi to install it?
It then installs to run as non-root.
If you had chosen the name "anydesk" then it would run as "anydesk" user and there will be a menu entry, also can run /usr/bin/anydesk
Tried this out tonight. Booted right up without any problem at all. So far so good, most things seem to be working!
I like the cockatoo wallpaper 
Just had a quick question. What would be the best way to install the wl module for broadcom wireless drivers?
With dunfell and kirkstone I guess I got a bit spoiled and there was always a pet containing this module, albeit it had to be updated for every kernel change.
https://bkhome.org/news/202012/broadcom ... river.html
I don't see that for EasyVoid. Does it need to be compiled from scratch for each kernel change?
Thanks!
Airdale wrote: ↑Tue Jan 23, 2024 4:30 amTried this out tonight. Booted right up without any problem at all. So far so good, most things seem to be working!
I like the cockatoo wallpaper
Just had a quick question. What would be the best way to install the wl module for broadcom wireless drivers?
With dunfell and kirkstone I guess I got a bit spoiled and there was always a pet containing this module, albeit it had to be updated for every kernel change.
https://bkhome.org/news/202012/broadcom ... river.html
I don't see that for EasyVoid. Does it need to be compiled from scratch for each kernel change?
Thanks!
I didn't create a pet for it because compile failed. The source I have doesn't like the 6.6.11 kernel.
The source file I have is broadcom-sta-15-wl64-2020.txz
Don't recall where I got it from, presume there must be a later version?
BarryK wrote: ↑Tue Jan 23, 2024 3:45 amFederico wrote: ↑Mon Jan 22, 2024 7:31 pmOn the 6.0.1, trying to run AnyDesk as flatpak. After installing it from flathub:
Code: Select all
# flatpak run com.anydesk.AnydeskWhy didn't you use Flapi to install it?
It then installs to run as non-root.If you had chosen the name "anydesk" then it would run as "anydesk" user and there will be a menu entry, also can run /usr/bin/anydesk
I tried with Flapi. Hit the "Customize" button, fill in the fields, it installs, also created a desktop icon.
However, it doesn't work. I ran "anydesk" from a terminal, and it just exits, no error message.
BarryK wrote: ↑Tue Jan 23, 2024 3:45 amFederico wrote: ↑Mon Jan 22, 2024 7:31 pmOn the 6.0.1, trying to run AnyDesk as flatpak. After installing it from flathub:
Code: Select all
# flatpak run com.anydesk.AnydeskWhy didn't you use Flapi to install it?
It then installs to run as non-root.If you had chosen the name "anydesk" then it would run as "anydesk" user and there will be a menu entry, also can run /usr/bin/anydesk
Hi Barry, good morning.
I installed it using Flapi, using the Customize button, in exactly the same way I used on Kirkstone, on which it works flawlessly. It is quite an important application, since it makes up the only way of doing remote control on Easy, as far as I know. This must have to do with some peculiarity of AnyDesk, since there are basically no problems with Ungoogled Chromium and Whatsapp.
As you can see, I have the menu entry, which simply does not work, and also the executables on /usr/bin:
This must have to do somehow with a slightly different way in which Void Linux manages users, imo. Anyway, I'm going to remove it and try reinstalling it. If I remember well, as Name I chose AnyDesk, since this is perfectly ok on Kirkstone. I will try naming it just simply anydesk, without upper case letters.
Unfortunately there was no development: it does not run.
Code: Select all
# anydesk
# flatpak run com.anydesk.Anydesk --no-sandbox
# flatpak run com.anydesk.Anydesk
# su anydesk
# flatpak run com.anydesk.Anydesk
error: Permission denied
# run-as-spot flatpak run com.anydesk.Anydesk
error: ' run com.anydesk.Anydesk' is not a flatpak command. Did you mean 'documents'?
See 'flatpak --help'
# exit
exit
# run-as-spot flatpak run com.anydesk.Anydesk
localuser:spot being added to access control list
# run-as-spot flatpak run com.anydesk.Anydesk
chown: /home/spot/.cache/doc: Permission denied
# run-as-spot flatpak run com.anydesk.Anydesk
chown: /home/spot/.cache/doc: Permission denied
# su spot
# run-as-spot flatpak run com.anydesk.Anydesk
error: ' run com.anydesk.Anydesk' is not a flatpak command. Did you mean 'documents'?
See 'flatpak --help'
# run-as-spot anydesk
# exit
exit
#
# su anydesk 'flatpak run com.anydesk.Anydesk'
bash: flatpak run com.anydesk.Anydesk: Permission denied
#
It looks like the custom user created for the flatpak does not have permissions to do something specific or has wrong permissions generally speaking. Hope this can be a hint.
EDIT : modification of the title. The problem is not related to Flatpak
I tested the AnyDesk Flatpak.
EDIT:(modification of the sentence for better understanding ) :
As reported by @Federico, in Easy 5.6.5 it launches, not in easyvoid
This is the result of ps | grep anydesk when Anydesk is launched in 5.6.5
11798 anydesk 0:00 {anydesk.bin} /bin/sh /usr/bin/anydesk.bin
11926 anydesk 0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
11927 anydesk 0:00 /usr/libexec/flatpak-bwrap --args 38 anydesk
11931 anydesk 0:00 /usr/libexec/flatpak-session-helper
11935 anydesk 0:00 {p11-kit-server} server --sh -n /home/anydesk/.cache/.flatpak-helper/pkcs11-flatpak-11931 --provider p11-kit-trust.so pkcs11:model=p11-kit-trust?write-protected=yes
11938 anydesk 0:00 /usr/libexec/xdg-document-portal
11942 anydesk 0:00 /usr/libexec/xdg-permission-store
11948 root 0:00 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=portal -- /home/anydesk/.cache/doc
11954 anydesk 0:00 /usr/libexec/at-spi-bus-launcher
11959 anydesk 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
11961 anydesk 0:00 /usr/libexec/flatpak-bwrap --args 38 /usr/libexec/flatpak-dbus-proxy --args=40
11962 anydesk 0:00 /usr/libexec/flatpak-dbus-proxy --args=40
11964 anydesk 0:00 /usr/libexec/flatpak-bwrap --args 38 anydesk
11965 anydesk 0:01 /app/extra/anydesk
11969 anydesk 0:00 /app/extra/anydesk --local-service
11973 anydesk 0:00 /app/extra/anydesk --tray
The executables flatpak-bwrap and flatpak-dbus-proxy (in /usr/libexec) appear in the list. They are not present in easyvoid (On the other hand there is a flatpak-system-helper in easyvoid but not in 5.6.5)
EDIT2 : I copied those 2 executables from 5.6.5 to easyvoid to test, but anydesk still do not launch
EDIT3 :
When the executables are present:
Code: Select all
# anydesk
localuser:anydesk being added to access control list
Without the executables:
Code: Select all
# anydesk
#
@ Caramel
What? Where did I say that? You probably misunderstood something. Easy 5.6.5 IS Kirkstone. I said exactly the same as you: it runs on EasyOS 5.6.5 and does not on easyVoid.
Sorry for my bad English. The "(as @Federico said)" was for the complete sentence
why not a list of programs for alpha releases too, it is a good habits to take and a good exercice before the big release day...
anyway, that was just a reminder, I did not want to sound rude or anything. 
EDIT : modification of the title. The problem is not related to Flatpak
Last observations.
The Anydesk flatpak launches in Void Linux
The Audacity flatpak launches in easyvoid
After the try of Anydesk in easyvoid, there is a directory .anydesk in /home/anydesk with 2 text files.
The first file is empty, but not the second (anydesk.trace)
The file anydesk.trace consists of several parts like this
info 2024-01-23 18:26:39.083 ad main 2 2 main - * AnyDesk Linux Startup *
info 2024-01-23 18:26:39.083 ad main 2 2 main - * Version 6.3.0 (linux_release_6.3.0 48f2d31752552b3da35079a0d8295c0ffda44a3e)
info 2024-01-23 18:26:39.083 ad main 2 2 main - * Build 20230803142204
info 2024-01-23 18:26:39.083 ad main 2 2 main - * Prefix ad
info 2024-01-23 18:26:39.083 ad main 2 2 main - * Copyright (C) 2023 AnyDesk Software GmbH *
info 2024-01-23 18:26:39.083 ad main 2 2 main -
info 2024-01-23 18:26:39.083 ad main 2 2 main - Distribution Info: Freedesktop SDK 23.08 (Flatpak runtime)
info 2024-01-23 18:26:39.083 ad main 2 2 main - Found GLib Version: 2.76.
info 2024-01-23 18:26:39.122 ad main 2 2 fiber.ipc_namespace - Global: no
explode 2024-01-23 18:26:39.122 ad main 2 2 app.common_path - The logged in user differs from the (non-root) user this process runs as. Process UID: 1005 , logged in UID: 0
info 2024-01-23 18:34:54.097 ad main 2 2 impl_selector - using sse2
Each part corresponds to a launch attempt.
Maybe the problem is relaed to the line :
explode 2024-01-23 18:26:39.122 ad main 2 2 app.common_path - The logged in user differs from the (non-root) user this process runs as. Process UID: 1005 , logged in UID: 0
This line is missing when Andydesk is launched In Easy 5.6.5 :
info 2024-01-23 19:38:34.756 ad main 2 2 main - * AnyDesk Linux Startup *
info 2024-01-23 19:38:34.756 ad main 2 2 main - * Version 6.3.0 (linux_release_6.3.0 48f2d31752552b3da35079a0d8295c0ffda44a3e)
info 2024-01-23 19:38:34.756 ad main 2 2 main - * Build 20230803142204
info 2024-01-23 19:38:34.756 ad main 2 2 main - * Prefix ad
info 2024-01-23 19:38:34.756 ad main 2 2 main - * Copyright (C) 2023 AnyDesk Software GmbH *
info 2024-01-23 19:38:34.756 ad main 2 2 main -
info 2024-01-23 19:38:34.775 ad main 2 2 main - Distribution Info: Freedesktop SDK 23.08 (Flatpak runtime)
info 2024-01-23 19:38:34.776 ad main 2 2 main - Found GLib Version: 2.76.
error 2024-01-23 19:38:34.892 ad main 2 2 unix_base.dbus.logind_manager - Error listing logind session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.login1 was not provided by any .service files
error 2024-01-23 19:38:34.928 ad main 2 2 unix_base.dbus.consolekit - Error getting active consolekit session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
warning 2024-01-23 19:38:34.929 ad main 2 2 session_manager_dummy - Using session manager dummy. Wont be able to use loginscreen.
info 2024-01-23 19:38:34.930 ad main 2 2 fiber.ipc_namespace - Global: no
info 2024-01-23 19:38:34.930 ad main 2 2 app.common_path - user_data_dir = /home/anydesk/.anydesk, logged_in_user_data_dir = /home/anydesk/.anydesk, current_home = /home/anydeskinfo 2024-01-23 19:38:34.955 ad main 2 2 app.common_path - initialized user = /home/anydesk/.anydesk, system = /home/anydesk/.anydesk
info 2024-01-23 19:38:35.009 ad main 6 6 impl_selector - using sse2]
I setup a 8 G USB flash drive with easyOS via the EasyDD utility running on a F96-CE_4. Used that to launch easyVoid-6.0.1 on a DELL INSPIRON laptop which runs different variations of KLV's and Puppy Linux's as well.
Booted smoothly and configuration completed, connected to WiFi easily. easyVoid is running nicely and is very responsive. Have not tried out the AnyDesk issue yet, but will see if it will start with some more coaxing.
Haven't tested much out yet but so far it is blazing fast in a Container desktop.