Arch Linux

boojum

Member

From: /dev/null

Registered: 2013-09-23

Posts: 44

Website

fbterm systemd user service problem

Howdy! I'm having a wee problem with fbterm. What I want to achieve is to have systemd start fbterm as user service right after (automatic) login. Here's fbterm.service

[Unit]
Description=FbTerm
Documentation=man:fbterm(1)
Before=multiplexer.target
ConditionPathExists=/dev/fb0

[Service]
Type=oneshot
TTYPath=/dev/tty1
Environment=FRAMEBUFFER=/dev/fb0
Environment=TERM=fbterm
ExecStart=/usr/bin/fbterm

[Install]
WantedBy=default.target

After enabling and restarting systemd reports that it successfully started fbterm yet I'm still staring at plain tty. Fbterm, on the other hand, is complaining about stdin not being tty -  exactly the same sort of a complain I was getting when starting fbterm from my shellrc. It won't moan about stdin (or anything else) when started manually after logging in.

Either way, here's relevant systemd snippet:

● fbterm.service - FbTerm
   Loaded: loaded (/home/boojum/.config/systemd/user/fbterm.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Sun 2016-02-28 23:56:28 GMT; 7h ago
     Docs: man:fbterm(1)
  Process: 27288 ExecStart=/usr/bin/fbterm (code=exited, status=0/SUCCESS)
 Main PID: 27288 (code=exited, status=0/SUCCESS)

Feb 28 23:56:28 ElmerFudd systemd[342]: Starting FbTerm...
Feb 28 23:56:28 ElmerFudd fbterm[27288]: stdin isn't a tty!
Feb 28 23:56:28 ElmerFudd systemd[342]: Started FbTerm

Why does fbterm complain about stdin?

Addendum: I should mention that it is X-less system. Adding

 RemainAfterExit=yes 

makes no difference.

Last edited by boojum (2016-02-29 16:41:28)