Arch Linux

clayc_989

Member

Registered: 2017-06-13

Posts: 6

Custom service trouble. (Enabled, nothing until started)

I've been searching around and canntot figure out why a custom systemd service I'm trying to run won't do anything even though it is currently enabled and is not failing. However, it does nothing until I start the service. Any insight as to what I'm doing wrong would greatly be appreciated.

The system I curretnly have is on a Macbook 11,x and I'm just trying to get the backlight controls to work on boot.

The script I wrote

#!/bin/bash
setpci -v -H1 -s 00:01.00 BRIDGE_CONTROL=0
exit 0

And the service.

[Unit]
Description= "Enable thingy for backlight control"
ConditionPathExists=/etc/systemd/system/enable-backlight

[Service]
ExecStart=/etc/systemd/system/enable-backlight

[Install]
WantedBy=multi-user.target

Thanks,
-clay

fsckd

Forum Fellow

Registered: 2009-06-15

Posts: 4,173

Re: Custom service trouble. (Enabled, nothing until started)

Just to clarify, it does not run on boot? Share journal output and may be systemctl status for it too.

---

aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies

clayc_989

Member

Registered: 2017-06-13

Posts: 6

Re: Custom service trouble. (Enabled, nothing until started)

Okay, this is really starting to confuse me. I looked at your post and rebooted real quick and it appears to be working now. I've been pulling my hair out for a while now because it wouldn't do anyting everytime I rebooted the system. Now it is working and I would hope its not a one time occurence....I'm not sure what to do for the journal output code (not sure what to target) but the systemctl status is as follows.

[turkey@Arch ~]$ systemctl status enable-backlight
● enable-backlight.service - "Enable thingy for backlight control"
   Loaded: loaded (/etc/systemd/system/enable-backlight.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Mon 2017-06-12 19:17:11 MDT; 4min 45s ago
  Process: 318 ExecStart=/etc/systemd/system/enable-backlight (code=exited, status=0/SUCCESS)
 Main PID: 318 (code=exited, status=0/SUCCESS)

Jun 12 19:17:11 Arch systemd[1]: Started "Enable thingy for backlight control".
Jun 12 19:17:11 Arch enable-backlight[318]: 0000:00:01.0 @3e 0000

I will turn the system off boot into OSX and come back to see if it is stil working.

EDIT: Booted into OSX and back to my Arch install. Cinnamon displayed nothing but the mouse cursor. I rebooted into root (where I'm at currently) disabled the service and logged back in to my account. Cinnamon is now crashing and I am stuck with the root log in.

Last edited by clayc_989 (2017-06-13 01:39:25)

cfr

Member

From: Cymru

Registered: 2011-11-27

Posts: 7,198

Re: Custom service trouble. (Enabled, nothing until started)

Can you log in as yourself if you stop X trying to start? What does the journal say? This sounds like a different problem from the backlight one?

---

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

clayc_989

Member

Registered: 2017-06-13

Posts: 6

Re: Custom service trouble. (Enabled, nothing until started)

I couldn't figure out what to do on my own. I guess my Google-fu isn't very strong.

As of right now, I have a fresh install of Arch running Cinnamon. I can boot between both systems and have no errors. The setpci command allows me to control my backlight when ran in terminal.

Should I create the script again and enable the service or should I post the journalctl output?

Thanks...

clayc_989

Member

Registered: 2017-06-13

Posts: 6

Re: Custom service trouble. (Enabled, nothing until started)

Alright, so I'm back to the issue of not being able to log back into Cinnamon. The only thing that I have done thus far is try and get the lightdm-webkit2 greeter to work. Which unfortunately didn't...so I had to recover from the Live image and change the lightdm.conf file back to how it was originially. Upon reboot I was met with the "CInnamon crashed, in fallback mode" or whatever. Booted into root, reset CInnamon and swithed users. I was greeted with the following:

Failed to update .ICEautority file /home/me/.ICEauthority

I went back to root login and checked the .xsession-errors and this is the output.

** (cinnamon-session:4575): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-EFYWMuqu8C: Connection refused
cinnamon-session[4575]: WARNING: t+0.00451s: IceLockAuthFile failed: Device or resource busy
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

Checking the file with 'ls -al' shows that my username is the owner, I have rw access...I've even tried giving executable access to the file with no gain.

Any ideas?

Also on a brighter note, the service that I was having at the beginning seems to be functioning properly. So that's a plus.

Last edited by clayc_989 (2017-06-15 03:46:48)