[manjaro-dev] help autostarting systemd services
hammera at pickup.hu
Thu Nov 5 17:18:21 CET 2015
Your sintax is real right, but need some working to Brltty start
automatically your profile:
First, your profile.conf file now the start_systemd list is commented
with # character, need remove this line the # character I think.
The proper line is following:
start_systemd=('bluetooth' 'cronie' 'ModemManager' 'NetworkManager'
'org.cups.cupsd' 'tlp' 'tlp-sleep' 'brltty' 'acpid 'firewalld')
Second, your profile in the overlay or the shared/overlay folder need
creating a soft simbolic link in etc/systemd/system/sysinit.target.wants
directory with shows the /usr/lib/systemd/system/brltty.service file.
For example, if you would like creating this simbolic link and the
etc/systemd/system/sysinit.target.wants directory not exists your
profile or your shared folder, enough following commands if your path is
your ISO profiles directory (for example the iso-profiles directory):
mkdir -p shared/overlay/etc/systemd/system/sysinit.target.wants
ln -s /usr/lib/systemd/system/brltty.service
Enjoi, if you rebuild your sonar ISO, hopefully BRLTTY will
automatically starts during live system and the installed system.
My custom profile I doed only this two tasks with BRLTTY related, BRLTTY
wonderful started automatically and Orca communicate right with BRLTTY.
If BRLTTY starting automatically, you will be founding following problem
if installing your new build:
I think after installation default the new created user and other future
created users not part of the brlapi group. BRLTTY starting right
automatically the installed system, but this is not enough.
I think the /etc/brlapi.key default owner is the root user and brlapi group.
My system previous the BRLTTY works too if I modifying the
/etc/brlapi.key file owner the brlapi group to the users group with
chown root:users /etc/brlapi.key
The adwantage this way if you creating another user, not need manual
adding the created user to the brlapi group.
But, this workaround is not full good, because the gdm user is not part
of the users group (this is right I think).
Me help following solution:
I change final with /etc/brlapi.key owner with root user and root group,
and change /etc/brlapi.key permissions with 0644.
So, enough following commands, please test:
chown root:root /etc/brlapi.key
chown 0644 /etc/brlapi.key
I tested this with a kvm virtual machine with an USB Alva Satellite 570
In the Ubuntu BRLTTY package the debian/brltty.postinst file if the
/etc/brlapi.key not exists, happening following commands to creating
this file and set the proper permissions:
if [ ! -e /etc/brlapi.key ]; then
chmod 0644 /etc/brlapi.key
Please test this solution with your new build.
Your new build working BRLTTY and Orca braille support in GDM screen and
More information about the manjaro-dev