You are not logged in.

#1 2015-02-18 11:27:24

Llama
Banned
From: St.-Petersburg, Russia
Registered: 2008-03-03
Posts: 1,379

[SOLVED] xscreensaver daemon fails on startup

Hi,

I've created the xscreensaver daemon like this.

It fails on startup, but later can be successfully started manually:

$ systemctl --user status xscreensaver
● xscreensaver.service - XScreensaver
   Loaded: loaded (/home/alexey/.config/systemd/user/xscreensaver.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2015-02-18 14:28:53 MSK; 39s ago
  Process: 307 ExecStart=/usr/bin/xscreensaver -no-splash (code=exited, status=1/FAILURE)
 Main PID: 307 (code=exited, status=1/FAILURE)

Feb 18 14:28:52 rimfirebox systemd[304]: Starting XScreensaver...
Feb 18 14:28:52 rimfirebox systemd[304]: Started XScreensaver.
Feb 18 14:28:53 rimfirebox systemd[304]: xscreensaver.service: main process exited, code=exited, status=1/FAILURE
Feb 18 14:28:53 rimfirebox systemd[304]: Unit xscreensaver.service entered failed state.
Feb 18 14:28:53 rimfirebox systemd[304]: xscreensaver.service failed.
$ systemctl --user start xscreensaver
$ systemctl --user status xscreensaver
● xscreensaver.service - XScreensaver
   Loaded: loaded (/home/alexey/.config/systemd/user/xscreensaver.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2015-02-18 14:29:57 MSK; 13s ago
 Main PID: 417 (xscreensaver)
   CGroup: /user.slice/user-1000.slice/user@1000.service/xscreensaver.service
           └─417 /usr/bin/xscreensaver -no-splash

Feb 18 14:29:57 rimfirebox systemd[304]: Started XScreensaver.
Feb 18 14:29:57 rimfirebox xscreensaver[417]: xscreensaver: 14:29:57: warning: $DISPLAY is not set: defaulting to ":0.0".
$ 

Is there a way to investigate this condition?

Last edited by Llama (2015-02-18 17:20:49)

Offline

#2 2015-02-18 11:38:38

parazyd
Member
From: Amsterdam
Registered: 2012-10-14
Posts: 259
Website

Re: [SOLVED] xscreensaver daemon fails on startup

I wouldn't start it at startup if you're logging in from TTY. Start it with your .xinitrc

Offline

#3 2015-02-18 11:58:48

Llama
Banned
From: St.-Petersburg, Russia
Registered: 2008-03-03
Posts: 1,379

Re: [SOLVED] xscreensaver daemon fails on startup

What's exactly 'logging in from TTY'?

I put it in my ~/.fluxbox/startup:

...
exec /opt/dropbox/dropboxd &
exec nm-applet &
exec xscreensaver -no-splash &
...

Is it correct (it looks like working)?

Offline

#4 2015-02-18 12:08:00

Alad
Wiki Admin/IRC Op
From: Bagelstan
Registered: 2014-05-04
Posts: 2,422
Website

Re: [SOLVED] xscreensaver daemon fails on startup

systemd user instances have issues with DISPLAY variables. This is supposed to get better with v219, where it can import those variables from your environment.

An X11 session scriptlet is now shipped that uploads
          $DISPLAY and $XAUTHORITY into the environment of the systemd
          --user daemon if a session begins. This should improve
          compatibility with X11 enabled applications run as systemd
          user services.


Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby

Offline

#5 2015-02-18 12:19:23

parazyd
Member
From: Amsterdam
Registered: 2012-10-14
Posts: 259
Website

Re: [SOLVED] xscreensaver daemon fails on startup

Llama wrote:

What's exactly 'logging in from TTY'?

I put it in my ~/.fluxbox/startup:

...
exec /opt/dropbox/dropboxd &
exec nm-applet &
exec xscreensaver -no-splash &
...

Is it correct (it looks like working)?

As in "not using a DM". Nevermind.

Yes, that is okay (I guess fluxbox needs 'exec' on every exec).

Offline

#6 2015-02-18 17:20:24

Llama
Banned
From: St.-Petersburg, Russia
Registered: 2008-03-03
Posts: 1,379

Re: [SOLVED] xscreensaver daemon fails on startup

Thanks!

Offline

Board footer

Powered by FluxBB