igel-community / igel-custom-partitions Goto Github PK

Hello,

im trying to run Alizams on a custom partition on an IGEL OS11 11.08.440. I created the custom partition and build the alizams.tar.bz2 though Ubuntu 18.04. I imported the profil in the UMS and edited the profil matching to our UMS. So far everything is working, exept, when I try to start the application, it doesnt start. When I launch it thought the terminal, it gives me the information that the libQt5core.so.5: version GT_5.11 was not found.

Can I somehow include the libary in the alizams.tar.bz2 or directly in the partition? I guess this is a simple quastion, but for someone who is new to the Linux world kinda hard. Or should I build it on ubuntu 20.04?

Im happy for any help.

https://github.com/IGEL-Community/IGEL-Custom-Partitions/blob/master/CP_Source/Apps/ConnectWise_Control_ScreenConnect/screenconnect_20.1.29489.7513.inf

file="screenconnect_20.1.29489.7513.tar.bz2"

https://github.com/IGEL-Community/IGEL-Custom-Partitions/blob/master/CP_Source/Apps/ConnectWise_Control_ScreenConnect/screenconnect_20.1.29489.7513_etc_igel1.tar.bz2

screenconnect_20.1.29489.7513_etc_igel1.tar.bz2

Hi Ron,
Just having a little play about with some of the CPs you have here but i cant seem to find the .tar.bz2 files in the actual zip files as per the layout description.
Not sure if they have been lost somewhere but thought i would highlight it to you. Any ideas where the files are now?
Thanks

The desktop icon Activate Tailscale doesn't seem to work, at least with Tailscale 1.36.0. A terminal is started but exits immediately.

Running 'tailscale up' manually in a terminal, as user, gives an error:

Access denied: denied
Use 'sudo tailscale up' or 'tailscale up --operator=$USER' to not require root.

I experimented by first running 'tailscale up --operator=user' and/or 'tailscale set --operator=user' as root, and than run 'tailscale up' as user. This seems to work, however only once. After user runs 'tailscale down', user cannot run 'tailscale up' anymore until root again sets the operator to user.

Tailscale also provides 'tailscale web' which starts a local web server on port 8088 for controlling Tailscale. If I run 'tailscale web' as root, I can connect to Tailscale, as user, through this web server/web interface. This seems a nicer solution than through the terminal.

Perhaps we should consider changing the Tailscale VPN CP to use 'tailscale web' instead of 'tailscale up' in a terminal?

Getting following error while running AppRun from terminal:

error while loading shared libraries: libmediastreamer.so.11: cannot open shared object file: No such file or directory

Built on Ubuntu 22.04 . libmediastreamer-base3 not supported any longer

PicoScope Builder needs to be debugged. See Readme file.

https://github.com/IGEL-Community/IGEL-Custom-Partitions/tree/master/CP_Source/Apps/PicoScope

Tailscale saves the machinekey in the file /var/lib/tailscale/tailscaled.state, but in the current Tailscale Custom Partition, this file is not persistent.

If I reboot the computer, a new machinekey is generated.

When "Device Authorization" is enabled on the tailnet, the device needs to be approved each time after it is restarted, which is very cumbersome.

I was able to fix this by changing the Systemd unit file /custom/tailscale/lib/systemd/system/tailscaled.service:

original line:

ExecStart=/usr/sbin/tailscaled --state=/var/lib/tailscale/tailscaled.state --socket=/run/tailscale/tailscaled.sock --port=${PORT} $FLAGS

modified line:

ExecStart=/usr/sbin/tailscaled --state=/custom/tailscale/var/lib/tailscale/tailscaled.state --socket=/run/tailscale/tailscaled.sock --port=${PORT} $FLAGS

But I'm not sure if this is the right way to do it.

7754871 :

pkexec -u root env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY

The above causes an authentication window/popup, which askes for the root password. (If I enter the root password it works fine.)

This is how I got this working in my test lab (without the need for root password):

UMS profile:
"System" > "Firmware Customization" > "Custom Commands" > "Desktop" > "Final desktop command" :

nohup tailscale web >/root/tailscale-web.log 2>&1 &

e40ab97 :
You ended up removing 'tailscale web' from the tailscale-cp-init-script.sh script, but I think it's needed to start tailscale web the first time/after installing the CP?

Originally posted by @Schwanzskala in #26 (comment)

build the CP from the build script

1. new Icon Name:

/custom/otpclient/usr/share/icons/hicolor/scalable/apps/com.github.paolostivanin.OTPClient.svg

2. client does not start

root@IGELOS:/custom/otpclient/usr/bin# ./otpclient-cli
./otpclient-cli: error while loading shared libraries: libcotp.so.12: cannot open shared object file: No such file or directory

the library is getting made, i guess:

- Installing: /usr/lib/x86_64-linux-gnu/libcotp.so.12

After deploying the Tailscale VPN Custom Partition, 'tailscale web' is not running. A reboot of the device is needed before Tailscale can be used.

I think starting of 'tailscale web' (e.g. nohup tailscale web >/root/tailscale-web.log 2>&1 & ) should be added below the line sudo systemctl start tailscaled in the tailscale-cp-init-script.sh script to resolve this issue.

On the current Tailscale VPN CP, Tailscale subnet routers are not working.

To use Tailscale subnet routers on Linux, you need to add the flag '--accept-routes', for example: 'tailscale up --accept-routes'

See also: https://tailscale.com/kb/1019/subnets/#step-5-use-your-subnet-routes-from-other-machines

As an alternative we could use 'tailscale web', which will by default accept the subnet routes (and also had other advantages, see #26).