It doesn't show anything, the list is completely empty; there are two
qtile-processes and I checked both. Their environments might not have been
set at launch, though (as far as I understand checking "environ" might not
contain variables added during runtime).
On Monday, 15 June 2020 16:05:14 UTC+2, Tycho Andersen wrote:
>
> On Sun, Jun 14, 2020 at 10:46:06PM -0700, tcld wrote:
> > There are certain programs I cannot launch via qtile's dmenu or
> lazy.spawn
> > (e.g. flatpak/Teams or standard Steam). Calling something like "steam >
> > ~/test.log" via dmenu works, however. On top of this, when launching the
> > filemanager ranger ("alacritty --command ranger") using lazy.spawn, I
> > noticed that child-processes spawned by that ranger have their
> environment
> > variables set in the wrong order - most noticably $HOME is set very
> late,
> > so that other variables making use of it break.
> > None of these issues occur when launching the processes from a user
> > terminal.
> >
> > As far as I have tracked down the issue, neither of this is caused by
> dmenu
> > itself nor the call to Popen issued by qtile; it appears instead that
> the
> > environments for the processes aren't set up properly (either lacking
> > variables or having them in the wrong order, depending on what I try
> > specifically). Does anybody have any experience with this kind of
> problem
> > and maybe knows a workaround?
> >
> > qtile itself is launched from a login shell on my system, and it is
> > supposedly run by my local user.
>
> What does strings /proc/$(pgrep qtile)/environ show? That should be
> the environment applications are run with.
>
> Tycho
>
--
You received this message because you are subscribed to the Google Groups
"qtile-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qtile-dev/24d49bb8-4c59-4388-a3fc-23eaa96f316co%40googlegroups.com.
