- This topic has 11 replies, 4 voices, and was last updated Dec 30-1:53 am by olsztyn.
-
Posts
-
stevesr0
I am running a “minimalistic” Sid Openbox antiX install with seatd instead of elogind or libelbgind0.
In order to get a program (Pipewire) working, I have to run a script that produces a run_time_dir that works (described on page 6 of the “Pipewire without Systemd” thread).
Looking at my environmental variables with and without running the script before launching X, I see a difference in one line:
Without running the script, this line reads
GPG_AGENT_INFO=/home/stevesr0/.gnupg/S.gpg-agent:0:1When I launch X after running the script, that line reads
GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1When I launch X without running the script first, there is no /run/user/ directory. If this script is run, the directory exists and has a listing for a user 1000.
So apparently, on my system this script is required for the creation of a functional runtime entity that GPG_AGENT can use.
(I haven’t tried to manually create this directory and change the GPG_AGENT_INFO to point to it – I will look into how to do that and report back. Advice welcome.)
I wonder if a “functional” /run/user 1000 is automatically created in other antiX systems running seatd (without elogind or libelogind0). That is – with a full antiX-22 install, does the “printenv” command show a GPG_AGENT_INFO line that points to a /run/user/”x” [1000 or tmp or…]?
Appreciate hearing about this from anyone with such a setup. I would be interested to see what modules in their systems I might install to eliminate the need for this script.
stevesr0
Brian Masinick
Since your home directory is /home/stevesr0, I wonder what would happen if you:
1) Change the file and directory permissions to stevesr0, for instance: sudo chown stevesr0:stevesr0 /run/user/1000
2) Change /run/user/1000 to /run/user/stevesr0First, would it work, and second, would the /run/user/1000 instances continue to reappear?
Worth a try; let us know if this makes any difference or if it’s ignored.--
Brian Masinick
christophe
I wonder if a “functional” /run/user 1000 is automatically created in other antiX systems running seatd (without elogind or libelogind0). That is – with a full antiX-22 install, does the “printenv” command show a GPG_AGENT_INFO line that points to a /run/user/”x” [1000 or tmp or…]?
Running printenv in terminal from antiX 22 full, I don’t have anything with “GPG.”
If it helps, the closest thing I have to that string is:
XDG_RUNTIME_DIR=/tmp/1000/.runconfirmed antiX frugaler, since 2019
olsztyn
I am running antiX 22 SID Full, although I do not have pipewire implemented yet. I have seatd. No *elogind* installed.
Just like @christophe, I do not see anything GPG*, just XDG*. Such as already mentioned by @Christophe:
XDG_RUNTIME_DIR=/tmp/1000/.run
Could GPG* be related to Pipewire?Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersHi “The Mas”, christophe and olsztyn,
Thanks for comments.
To christophe and olsztyn,
On my system, the GPG_AGENT_INFO line only appears when printenv is run in a terminal window after starting X. Did you run the command that way or before launching X?
The /tmp/1000/.run I believe is one of the common XDG_RUN_DIR entries. The script I use causes the /run/user/1000; I think it could be modified to produce /tmp/1000/.run.
To “The Mas”, I will try that and report back.
stevesr0
- This reply was modified 4 months, 1 week ago by stevesr0.
- This reply was modified 4 months, 1 week ago by stevesr0.
On my system, the GPG_AGENT_INFO line only appears when printenv is run in a terminal window after starting X. Did you run the command that way or before launching X?
I am running this from antiX SID Full, so after X started, from terminal window on desktop. Regardless it is run from terminal window on Ice, Flux or JWM, the same.
- This reply was modified 4 months, 1 week ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameterschristophe
gpg-agent:
Installed: 2.2.27-2+deb11u2
Candidate: 2.2.27-2+deb11u2confirmed antiX frugaler, since 2019
Do you have the package gpg-agent installed?
Yes. Version 2.2.40-1.
Installed. Not running.- This reply was modified 4 months, 1 week ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersTo all readers:
Interesting blog post on Run Time Directories: https://utcc.utoronto.ca/~cks/space/blog/linux/UserRuntimeDirectories?showcomments#comments
Hi christophe and olsztyn,
Thanks for responses.
Do you have consolekit packages installed (consolekit, libconsolekit1, libpolkit-gobject-consolekit-1-0)?
stevesr0
Hi The Mas (Shouldn’t this be The_Mas?),
Apologize for delay. I have been focusing on understanding the role of the gpg-agent in enabling Pipewire to run in the absence of systemd elements.
I will try that on a liveUSB no persistence version of this installed system. Hopefully in the next week.
It will be interesting if that works without the activation of gpg-agent and the use of the export line in my .profile file.
stevesr0
Do you have consolekit packages installed (consolekit, libconsolekit1, libpolkit-gobject-consolekit-1-0)?
I have none of this installed.
Just to remind my setup, which I believe does not require the above components:
Full antiX 22 SID, Runit, No elogind, just seatd
My five WMs I am using do not require the consolekit as much as I know:
– JWM -default
– Ice
– Flux
– Herbsluftwm
– Openbox + LXpanel.I do not think I need consolekit stuff for anything, especially that I am trying to not have unnecessary components installed or running.
However I have not implemented pipewire yet, which might be a difference from your setup…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
- You must be logged in to reply to this topic.
