On 19/09/2021 13.11, Ed Greshko wrote:
OK..
I think I see the problem now. I don't need Environment=. But the
issue is that, I assumed, "plasma-core.target" would be
reached only after a user logged in to plasma.
I was wrong and the user's service is run earlier when the login
screen
> What would be the proper way to get the DISPLAY environment varible use it as
> opposed
Having someone else (your desktop) call
"dbus-update-activation-environment --systemd" on startup or an
equivalent
and ensure your service is started after that, such as being after
graphical-session.target
On 9/21/21 9:13 AM, Michael Biebl wrote:
Just curious:
Can someone familiar with KDE/Plasma tell us, if they nowadays (can)
use "systemd --user" to manage a login session.
Seems to be the case on openSUSE Leap 15.3
So, I'll say yes.
Am Di., 21. Sept. 2021 um 12:52 Uhr schrieb Ed Greshko
Just curious:
Can someone familiar with KDE/Plasma tell us, if they nowadays (can)
use "systemd --user" to manage a login session.
Am Di., 21. Sept. 2021 um 12:52 Uhr schrieb Ed Greshko :
>
> On 21/09/2021 18:20, Colin Guthrie wrote:
> > Ed Greshko wrote on 19/09/2021 12:11:
> >> OK..
> >>
On 21/09/2021 18:20, Colin Guthrie wrote:
Ed Greshko wrote on 19/09/2021 12:11:
OK..
I think I see the problem now. I don't need Environment=. But the issue is that, I
assumed, "plasma-core.target" would be
reached only after a user logged in to plasma.
I was wrong and the user's
Ed Greshko wrote on 19/09/2021 12:11:
OK..
I think I see the problem now. I don't need Environment=. But the
issue is that, I assumed, "plasma-core.target" would be
reached only after a user logged in to plasma.
I was wrong and the user's service is run earlier when the login screen
On Sun, Sep 19, 2021 at 4:48 PM Ed Greshko wrote:
> On 19/09/2021 21:39, Michael Biebl wrote:
>
> A useful command in this context is
>
> systemctl --user show-environment
>
>
> OK, that was helpful. But leads to another question.
>
> How to run the service only if KDE_FULL_SESSION=true?
>
To
> On 19 Sep 2021, at 14:48, Ed Greshko wrote:
>
>
> On 19/09/2021 21:39, Michael Biebl wrote:
>> A useful command in this context is
>>
>> systemctl --user show-environment
>
> OK, that was helpful. But leads to another question.
>
> How to run the service only if KDE_FULL_SESSION=true?
> On 19 Sep 2021, at 14:48, Ed Greshko wrote:
>
>
> On 19/09/2021 21:39, Michael Biebl wrote:
>> A useful command in this context is
>>
>> systemctl --user show-environment
>
> OK, that was helpful. But leads to another question.
>
> How to run the service only if KDE_FULL_SESSION=true?
Am So., 19. Sept. 2021 um 15:48 Uhr schrieb Ed Greshko :
>
> On 19/09/2021 21:39, Michael Biebl wrote:
>
> A useful command in this context is
>
> systemctl --user show-environment
>
>
> OK, that was helpful. But leads to another question.
>
> How to run the service only if KDE_FULL_SESSION=true?
On 19/09/2021 21:39, Michael Biebl wrote:
A useful command in this context is
systemctl --user show-environment
OK, that was helpful. But leads to another question.
How to run the service only if KDE_FULL_SESSION=true?
Am So., 19. Sept. 2021 um 11:53 Uhr schrieb Mantas Mikulėnas
:
On
A useful command in this context is
systemctl --user show-environment
Am So., 19. Sept. 2021 um 11:53 Uhr schrieb Mantas Mikulėnas
:
>
> On Sun, Sep 19, 2021 at 4:05 AM Ed Greshko wrote:
>>
>> Not a everyday systemd service writer
>>
>> I've written a user service file to start an app on
On 19/09/2021 17:53, Mantas Mikulėnas wrote:
On Sun, Sep 19, 2021 at 4:05 AM Ed Greshko wrote:
Not a everyday systemd service writer
I've written a user service file to start an app on login. It works well
for Xorg with Environment=DISPLAY=:0.
But I've found that under
On Sun, Sep 19, 2021 at 4:05 AM Ed Greshko wrote:
> Not a everyday systemd service writer
>
> I've written a user service file to start an app on login. It works well
> for Xorg with Environment=DISPLAY=:0.
>
> But I've found that under Wayland the DISPLAY=:1 after a logout of Xorg
> and
On 19/09/2021 14:52, Michael Biebl wrote:
You don't hard-code it, you just use it?
OK, yes, it is just used.
In your case, since you have a user service which appears bound to the
lifetime of a graphical (X/Wayland) session, I guess
graphical-session.target is what you want.
See man
You don't hard-code it, you just use it?
In your case, since you have a user service which appears bound to the
lifetime of a graphical (X/Wayland) session, I guess
graphical-session.target is what you want.
See man systemd.special.
So far, I think only GNOME implements graphical-session.target
Not a everyday systemd service writer
I've written a user service file to start an app on login. It works well for
Xorg with Environment=DISPLAY=:0.
But I've found that under Wayland the DISPLAY=:1 after a logout of Xorg and
login to a
Wayland session.
What would be the proper way to
17 matches
Mail list logo
