- This topic has 15 replies, 4 voices, and was last updated Jun 13-10:03 am by Freeze.
-
Posts
-
Freeze
Hi,
I am happy to discover antix and sorry for my english. I’m using a VM proxmox.
I am trying to install veyon.
Any one succeed ?After update && upgrade i used :
su
apt install veyon* libqca-qt5-2-pluginsWhen i launch veyon master in start menu, i get a screenplash but no GUI after.
With CLI veyon-master, i get this error messsage :$ veyon-master 2025-06-06T10:15:29.617: [WARN] LinuxSessionFunctions: could not determine dbus object path of current session – please make sure systemd is up to date and/or the environment variable "XDG_SESSION_ID" is set dbus[6327]: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file ../../../dbus/dbus-message.c line 1377. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace AbortedAny help is welcome. Thx
- This topic was modified 1 year, 3 months ago by abc-nix. Reason: code tags
sybok
please make sure systemd is
antiX is by design systemd-free, ‘veyon’ claims it may require ‘systemd’ even though it was not its dependency.
It states that you might be able to solve by handling the ‘dbus’/XDG_SESSION_ID yourself.This means you have to do something to alter the output of the following commands:
ps -ef | grep '\<dbus\>' # List running processes with word 'dbus' in their name echo "$XDG_SESSION_ID" # Print current value of the variableMy output is: dbus is running, the variable is an empty line.
Unfortunately, I have not much of an idea how to proceed apart from:
1) Start ‘dbus-daemon’, if not running
2) Check XDG_SESSION_ID variable after that and if empty, try to set it to 1, i.e. try to run
XDG_SESSION_ID=1; veyon-masterBut this may be an ugly hack that does not work and someone more knowledgeable can provide an elegant solution.
Why 1: https://askubuntu.com/questions/1340098/what-xdg-environment-variables-should-be-set-at-boot
abc-nix
Starts for me. Make sure you have DBUS_SESSION_LAUNCH and CONSOLEKIT_SESSION_LAUNCH variables set to “true” in ~/.desktop-session/desktop-session.conf
This is with antiX full, correct?
EDIT: May require libelogind0 to work. Not sure.
- This reply was modified 1 year, 3 months ago by abc-nix.
Corruption has two hands: the Right and the Left. Don't let them squeeze you.
Thank you 2 a lot !!
First and fastiest @abc-nix,
I installed antiX base not full and DBUS_SESSION_LAUNCH=“true” but no CONSOLEKIT_SESSION_LAUNCH in desktop-session.conf@sybok,
ps found dbus-deamon and dbus-launch ; variable “$XDG_SESSION_ID” is empty too
XDG_SESSION_ID=1; veyon-master offert same message error as precedent.- This reply was modified 1 year, 3 months ago by Freeze.
… Trying with antiX-full …
sybok
@freeze: It might have worked with antiX-base if you set the variables, restart/refresh the session (I’d log out and log in again, just for sure).
antiX full is the recommended way; base is for more experienced users and it misses some of the applications/tools present in full.
I have set up a VM with antiX 23.2 base and I am getting the same error. Will need to investigate.
Corruption has two hands: the Right and the Left. Don't let them squeeze you.
I have fully upgraded the antiX base live VM, installed consokekit, libpam-ck-connector policykit-1 with apt, then installed veyon-master, veyon-configurator and libqca-qt5-2-plugins
I then run the command
DBUS_FATAL_WARNINGS=0 veyon-master
and it starts.On my installed system (too many changes to list, on wayland), it works without the need for the env variable, so it should also be able to work on antiX 23.2. For now see if it can work for you properly with the env variable.
Corruption has two hands: the Right and the Left. Don't let them squeeze you.
Hi,
@syboc, thank you but no solution with your advices. Hope antiX full be friendly.@abc-nix,
I run antiX fullI have fully upgraded the antiX base live VM, installed consolekit, libpam-ck-connector policykit-1 with apt, then installed veyon-master, veyon-configurator and libqca-qt5-2-plugins
I then run the command
DBUS_FATAL_WARNINGS=0 veyon-master
and it starts.Fine !! it works for me too !
After i run :su
apt install veyon-service
DBUS_FATAL_WARNINGS=0 veyon-configuratorI can import fileconf.json and save but with an error about the veyon service.
I discover that veyon service don’t start from GUI. I don’t know how start it.
So, i am able to run veyon-master and control other PCs. My goal is to take control of this antix from my workstation.- This reply was modified 1 year, 3 months ago by Freeze.
- This reply was modified 1 year, 3 months ago by Freeze.
- This reply was modified 1 year, 3 months ago by Freeze.
blur13
CONSOLEKIT_SESSION_LAUNCH variables set to “true”
Could you elaborate on this? What does this do exactly? Why is it set to false by default? Does setting it to true maximize compatibility with software?
Setting DBUS to true did solve a few problems for me before, so wondering if this could have a similar effect.
CONSOLEKIT_SESSION_LAUNCH variables set to “true”
Could you elaborate on this? What does this do exactly? Why is it set to false by default? Does setting it to true maximize compatibility with software?
It fixes some issues with policykit, as described in this thread. As veyon seemed to require polkitd to be installed, I assumed it would help fix the issue, but there is something else missing for veyon to work properly.
I can import fileconf.json and save but with an error about the veyon service.
I discover that veyon service don’t start from GUI. I don’t know how start it.It seems that only the systemd service is packaged. Try first to start it manually to see if it works with
sudo /usr/bin/veyon-service
You may need to install libelogind0 for it to work though.If it works, add the command to /etc/rc.local (as root) before the exit 0 command, so it looks like this:
/usr/bin/veyon-service & exit 0It will start the service automatically on next reboot.
Corruption has two hands: the Right and the Left. Don't let them squeeze you.
This is with antiX full, correct?
Yes
Starts for me. Make sure you have DBUS_SESSION_LAUNCH and CONSOLEKIT_SESSION_LAUNCH variables set to “true” in ~/.desktop-session/desktop-session.conf
Yes
installed consokekit, libpam-ck-connector policykit-1 with apt, then installed veyon* and libqca-qt5-2-plugins
Yes
DBUS_FATAL_WARNINGS=0 or DBUS_FATAL_WARNINGS=0 veyon-configurator
Yes without service run
It seems that only the systemd service is packaged. Try first to start it manually to see if it works with
sudo /usr/bin/veyon-service
You may need to install libelogind0 for it to work though.libelogind0 installed but veyon-service send :
[ERR] LinuxSessionFunctions: Could not query sessions: “The name org.freedesktop.login1 was not provided by any .service file”
This looks like systemd ? I’m offside
please make sure systemd is
antiX is by design systemd-free, ‘veyon’ claims it may require ‘systemd’ even though it was not its dependency.
It states that you might be able to solve by handling the ‘dbus’/XDG_SESSION_ID yourself.Like already said in FAQ and here , no systemd in Antix ! let’s try MX
sybok, abc-nix, thank you for your time, knowledge and kindness
- This reply was modified 1 year, 3 months ago by Freeze.
But if there is any idea to test, i’m ready
You could try with elogind instead of consolekit. It would require first installing elogind and libpam-elogind. I cannot test right now, so I cannot say for sure.
Corruption has two hands: the Right and the Left. Don't let them squeeze you.
sybok
@Freeze: Ahem, the direction it took is already complicated for me as I have little experience with libpolkit and stuff like that (at least thus far).
Once this is solved (or abandoned for lack of a viable solution… because of ‘systemd’?), you could fire a bug to the DEB package maintainer about incomplete dependencies, whatever they may be.
Of course, it is possible that such a bug would be closed by simple adding ‘systemd’.
- You must be logged in to reply to this topic.