[SOLVED] systemd without consolekit: systemd-cgls, no /user/myname

Hi!
While i was facing a problem with network-manager-applet, that needs to be started as root without consolekit, otherwise the applet won't start, i probably understood where is the issue:
systemd-cgls systemd:/user/
systemd:/user/:
└ root
└ c1
├ 282 sudo nm-applet &
├ 283 nm-applet &
├ 336 dbus-launch --autolaunch d3503ec54b9f464baea83af9b8fcf576 --binar...
├ 337 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --ses...
├ 485 /usr/lib/xfce4/xfconf/xfconfd
├ 487 /usr/lib/gvfs/gvfsd
└ 489 /usr/lib/gvfs//gvfs-fuse-daemon -f /root/.gvfs
There is only root user.
What i did: I removed consolekit after rebuilding polkit with systemd support. Usb automount works as expected.
I tried to add "session optional pam_systemd.so" to all files in /etc/pam.d only to give it a try, but nothing changed.
Here instead there is my xfce4.service that starts my xfce4 session:
[Unit]
Description=start xfce4
After=systemd-user-sessions.service
[Service]
User=federico
ExecStart=/usr/bin/startxfce4
[Install]
WantedBy=multi-user.target
Any idea?
Thank you.
EDIT: only to be sure
whoami
federico
EDIT2: sorry, here is another related output:
journalctl -a | grep polkit
Sep 05 12:39:02 arch polkitd[220]: started daemon version 0.105 using authority implementation `local' version `0.105'
Sep 05 12:39:08 arch xinit[217]: (polkit-gnome-authentication-agent-1:285): polkit-gnome-1-WARNING **: Unable to determine the session we are in: No session for pid 285
Last edited by nierro (2012-09-05 12:38:35)

you can't start xfce from a service file, there will be no proper session created for your user. have a look at this: https://bbs.archlinux.org/viewtopic.php?id=147913

Similar Messages

[SOLVED] systemd/cron as user: timer doesn't start after boot

Hello,
I've tried to follow the wiki's systemd/cron functionality article to have a systemd service to run hourly.
Everything seems to be working ok, except that the hourly timer doesn't start automatically : I have to issue a
systemctl --user timer-hourly.timer start
command every time I start the machine to get the timer running.
Can you help me understand what I'm missing to get the (user) timer to start automatically after boot?
Thanks!
My setup consists of the following files:
/home/myuser/.config/systemd/user:
drwxr-xr-x 2 myuser users 4096 Jun 25 17:30 basic.target.wants/
-rw-r--r-- 1 myuser users 217 Jun 25 10:08 db_backup.service
-rw-r--r-- 1 myuser users 232 Jun 25 10:08 test.service
-rw-r--r-- 1 myuser users 61 Jun 19 12:14 timer-hourly.target
drwxr-xr-x 2 myuser users 4096 Jun 25 10:10 timer-hourly.target.wants/
-rw-r--r-- 1 myuser users 134 Jun 19 12:14 timer-hourly.timer
/home/myuser/.config/systemd/user/basic.target.wants/:
lrwxrwxrwx 1 myuser users 50 Jun 25 10:08 timer-hourly.timer -> /home/myuser/.config/systemd/user/timer-hourly.timer
/home/myuser/.config/systemd/user/timer-hourly.target.wants/:
lrwxrwxrwx 1 myuser users 49 Jun 13 15:51 db_backup.service -> /home/myuser/.config/systemd/user/db_backup.service
lrwxrwxrwx 1 myuser users 44 Jun 25 10:10 test.service -> /home/myuser/.config/systemd/user/test.service
timer-hourly.timer:
[Unit]
Description=Hourly Timer
[Timer]
OnBootSec=5min
OnCalendar=hourly
Unit=timer-hourly.target
[Install]
WantedBy=basic.target
timer-hourly.target:
[Unit]
Description=Hourly Timer Target
StopWhenUnneeded=yes
test.service:
[Unit]
Description=Run a test (echo) job every hour
Wants=timer-hourly.timer
[Service]
Nice=19
IOSchedulingClass=2
IOSchedulingPriority=7
ExecStart=/usr/bin/python /home/myuser/test_service.py
[Install]
WantedBy=timer-hourly.target
db_backup.service:
[Unit]
Description=Backups databases
Wants=timer-hourly.timer
[Service]
Nice=19
IOSchedulingClass=2
IOSchedulingPriority=7
ExecStart=/home/myuser/source/db_backups/db_backup.sh
[Install]
WantedBy=timer-hourly.target
test_service.py is a simple python script that appends the current time to a file, to check if the service is being run by the timer. (it is after I start the timer after boot, and runs correctly every hour)
db_backup.sh is a script that dumps a database into a text file in a mercurial repository, commits the change and pushes it to backup locations.
Last edited by fede (2014-06-25 21:06:09)

Have you tried this:
systemctl --user enable timer-hourly.timer

[SOLVED] Can Openbox function without ConsoleKit ?

I've very recently converted to a "pure" systemd Arch system & desire to be without ConsoleKit, if it is possible at this stage.
I tried to remove ConsoleKit with pacman but was blocked with the following error:
handy ~ $ pdelete consolekit
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: oblogout: requires consolekit
Which brings two questions:
Can Openbox live without ConsoleKit?
If so, how?
Thanks for your time.
Last edited by handy (2012-08-14 09:20:50)

WonderWoofy wrote:if you have a pure systemd arch, you should be able to user 'systemctl reoot" to reboot without root access as long as no other users are logged into the machine. This should laso work with poweroff, suspend, and hibernate also used with the systemctl command. If you still want a logout dialog, you could create a simple script with something like xmessage using those commands.
We posted at the same time.
I use systemctl reboot & poweroff from buttons configured for the job in Worker. I used to use a couple of simple scripts that first umounted my three NAS NFS shares (to get around the time out problem) & then shutdown or reboot. So I NEVER use oblogout anyway.
The new systemctl commands reboot & poweroff, automatically umount my NFS shares first & then do what they are named. Fantastic, this is how it is supposed to be.

[SOLVED] systemd: Failed to open private dbus connection

Below is a snapshot from journalctl -b:
systemd[1]: Starting user-1000.slice.
systemd[1]: Created slice user-1000.slice.
systemd[1]: Starting User Manager for 1000...
systemd[1]: Starting Session 1 of user me.
systemd[1]: Started Session 1 of user me.
systemd-logind[195]: New session 1 of user me.
systemd[261]: pam_unix(systemd-user:session): session opened for user me by (uid=0)
systemd[261]: Failed to open private dbus connection: Failed to connect to socet /run/usr/1000/dbususer_bus_socket: No such file or directory
systemd[261]: Mounted /sys/kernel/config.
systemd[261]: Stopped target Bluetooth.
systemd[261]: Stopped target Sound Card.
systemd[261] Starting Default.
systemd[261]: Reached target Default.
systemd[261]: Startup finished in 135ms.
systemd[1]: Started User Manager for 1000.
login[199]: LOGIN ON tty1 BY me
It's a fresh Arch Linux install and I didn't even had a time yet to tinker with systemd so it's unlikely that I've messed things up. I suspect that it might be the cause of the following problem:
$ systemctl status --user
Failed to issue method call: Process /bin/false exited with status 1
For reference, systemd version:
$ systemctl --version
systemd 207
+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
Any ideas how can I solve the private dbus connection problem?
Last edited by vox23 (2013-09-25 17:02:22)

65kid wrote:do you actually experience any problems?
I thought that it might be related to:
$ systemctl status --user
Failed to issue method call: Process /bin/false exited with status 1
however when I followed wiki and created:
$cat /etc/systemd/system/[email protected]/environment.conf
[Service]
Environment=DISPLAY=:0
Environment=XDG_RUNTIME_DIR=/run/user/%I
Environment=SHELL=%s
then /bin/false error went away. I still have some problems with systemd managing my user session but unrelated to the above. Marking as solved.

[SOLVED] systemd uses cronie.service in /usr/lib instead of /etc

I've been having a little problem getting systemd to use my custom service file for cronie. I've tried doing the same thing with ntpd and a few other services, and they all work fine.
[root@garrett garrett]# cp /{usr/lib,etc}/systemd/system/cronie.service
[root@garrett garrett]# systemctl reenable cronie.service
rm '/etc/systemd/system/multi-user.target.wants/cronie.service'
ln -s '/etc/systemd/system/cronie.service' '/etc/systemd/system/multi-user.target.wants/cronie.service'
[root@garrett garrett]# systemctl status cronie.service
cronie.service - Periodic Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/cronie.service; enabled)
Active: inactive (dead)
CGroup: name=systemd:/system/cronie.service
Sep 13 21:32:52 garrett /usr/sbin/crond[622]: (CRON) INFO (running with inotify support)
It appears to have something to do with the crond.service symlink to cronie.service, since when I remove it, systemd will use the service file in /etc.
[root@garrett garrett]# rm /usr/lib/systemd/system/crond.service
[root@garrett garrett]# cp /{usr/lib,etc}/systemd/system/cronie.service
[root@garrett garrett]# systemctl reenable cronie.service
rm '/etc/systemd/system/multi-user.target.wants/cronie.service'
ln -s '/etc/systemd/system/cronie.service' '/etc/systemd/system/multi-user.target.wants/cronie.service'
[root@garrett garrett]# systemctl status cronie.service
cronie.service - Periodic Command Scheduler
Loaded: loaded (/etc/systemd/system/cronie.service; enabled)
Active: inactive (dead)
CGroup: name=systemd:/system/cronie.service
Sep 13 21:32:52 garrett /usr/sbin/crond[622]: (CRON) INFO (running with inotify support)
However, these symlinks don't cause problems in other packages such as with cups.service, which has a symlink cupsd.service. I also tried the same commands above on another arch computer I have that is running systemd and encountered the same results. This just seems really strange, and I'm not exactly sure where to go from here. Any help would be greatly appreciated.
Last edited by Floft (2012-09-14 06:40:23)

I can not replicate on my system.
# find {/usr/lib,/etc}/systemd/system/ -name "*cron*" -ls
803795 4 -rw-r--r-- 1 root root 174 Aug 8 22:24 /usr/lib/systemd/system/cronie.service
803798 0 lrwxrwxrwx 1 root root 14 Aug 8 22:24 /usr/lib/systemd/system/crond.service -> cronie.service
793796 4 -rw-r--r-- 1 root root 174 Sep 14 03:01 /etc/systemd/system/cronie.service
932745 0 lrwxrwxrwx 1 root root 34 Sep 14 03:01 /etc/systemd/system/multi-user.target.wants/cronie.service -> /etc/systemd/system/cronie.service
# systemctl status cronie
cronie.service - Periodic Command Scheduler
Loaded: loaded (/etc/systemd/system/cronie.service; enabled)
Active: active (running) since Fri, 14 Sep 2012 03:06:05 -0300; 1s ago
Main PID: 13956 (crond)
CGroup: name=systemd:/system/cronie.service
└ 13956 /usr/sbin/crond -n

[solved] systemd-journal and shadow.pacnew updates

After a recent install and update I have come across the same issue described here where the user was recommended to ignore and erase some .pacnew files. My update generated the following:
/etc/dhcpcd.conf.pacnew
/etc/group.pacnew
/etc/passwd.pacnew
/etc/shadow.pacnew
/etc/gshadow.pacnew
The first, dhcpcd, seemed sensible enough and I incorporated the changes. The latter four all share the following characteristics:
1. Removed mentions of systemd-journal-remote and systemd-journal-upload. I'm not sure why so I left those records in place.
2. Changed a few permissions here or there, which i incorporated into /etc/group and /etc/password.
3. Changed the default shell for a few users; these changes I incorporated.
I was unable to open /etc/shadow or /etc/gshadow in write mode so I've left these files. Perhaps that's fine because the thread mentioned above says so. However, there's no explanation of why or where this information was obtained (or ordained!)
Is it fine to leave these two files? Why have syssystemd-journal-remote and systemd-journal-upload been omitted?
Last edited by Deau (2014-08-29 06:54:18)

The steps you took look quite sane to me.
These groups are not in the defaults provided by filesystem (e.g. I don't have them). see the edit
Apparently systemd creates system groups and users on it's own, see 'man systemd-sysusers'. Do you know / can figure out why these groups are created in the first place ? not important in this case, see the edit as well
FYI e.g.: https://bugs.archlinux.org/task/41717
The filesystem package provides those files as defaults (group, passwd, shadow, gshadow amongst otheres). However there are some packages that actually add additional groups they need (like ntp e.g.). The filesystem package cannot know about these. Therefor it's likely to have more groups in your local installation than in the .pacnew files you get.
The same applies for manually created users and groups of course.
If needed see the man pages for explanations of the respective files (e.g. 'man group').
Edit: Ok, I see that after an update I have them as well, so these are apparently new systemd groups and users. I think the rest I said above is still valid, so leaving those in place was the right thing to do.
Last edited by rebootl (2014-08-28 20:46:43)

[SOLVED] systemd: laptop-mode-tools fails to start (No such file ...)

Hi,
I recently moved to systemd. I noticed that 'laptop-mode-tools' does not start:
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
Also laptop-mode itself does not run (but exits successfully), maybe this has something to do with it:
laptop-mode.service - Laptop Mode Tools
Loaded: loaded (/usr/lib/systemd/system/laptop-mode.service; enabled)
Active: active (exited) since Sat, 2012-11-10 10:44:13 CET; 2min 17s ago
Process: 1020 ExecStart=/usr/sbin/laptop_mode init auto (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/laptop-mode.service
I cannot find anything in journal that would help resolve this issue. Has someone else come across this problem? Where should I look to fix this issue?
Sidenote: When I boot up, there show up some errors about 'eth0' and 'wlan0' "No such file or directory", but I cannot find them in the journal so I don't know them exactly.
Last edited by javex (2012-11-10 12:41:07)

When I upgraded, pacman said the following
[2012-11-04 09:41] The systemd service name has changed from \laptop-mode-tools" to "laptop-mode"
[2012-11-04 09:41] The change requires the old symlink to be manually removed:
[2012-11-04 09:41] rm /etc/systemd/system/multi-user.target.wants/laptop-mode-tools.service
[2012-11-04 09:41] The laptop-mode.service can be enabled using:
[2012-11-04 09:41] systemctl enable laptop-mode
[2012-11-04 09:41] upgraded laptop-mode-tools (1.61-2 -> 1.62-2)

[solved] systemd 219: automount doesn't work anymore

To mount a directory with sshfs on another Arch system in my local net I added this to fstab:
[email protected]:/var/cache/pacman/pkg /var/cache/pacman/pkg fuse.sshfs x-systemd.automount,_netdev,user,noatime,idmap=user,transform_symlinks,identityfile=/root/.ssh/id_rsa,allow_other,default_permissions,reconnect 0 0
I need it to use a local pacman directory globally so new packages will be downloaded only once for all my Arch pc's.
This has worked for a long time but since systemd 219-1 nothing happens. Mounting it manually using fstab works. I switched back to systemd 218-2 and it works fine again.
Thanks, lw.
Last edited by LessWire (2015-03-16 14:41:09)

Same here for cifs and ntfs4 mounts in fstab. Downgrade from 219-2 to 218-2 fixes this.
Example fstab entry:
//sambaserver/myshare /home/me/server/myshare cifs x-systemd.automount,sec=ntlmv2,nobrl,user=me,password=mypw,workgroup=My.LAN 0 0
works with 218-2 but not with 219-2. Timing issue?
Manually mounting the directories on console after boot works:
mount //sambaserver/myshare
Harvey

[SOLVED] systemd-modules-load fglrx error

Hello,
recently I have updated my catalyst drivers (catalyst-test from the AUR) and did a full system upgrade (-Syu).
Since then I'm unable to do almost anything.
I'm guessing the catalyst-test upgrade went bad because systemd says it's unable to locate fglrx.
archlinux systemd-modules-load[188]: Failed to find module 'fglrx'
I want to reinstall catalyst-test, but I'm unable to do so since I can't even see the tty's.
They work, but every time I issue a command I have to write the output to a file since I can't see the output or what I'm writing.
ex.
to see the output of "systemctl --state=failed" I have to do "systemctl --state=failed > file.txt" and then boot into another OS to read it, it's really painful.
I have tried adding "systemd.unit=multi-user.target" to the kernel cmdline as suggested on the IRC, but it didn't work. Nor did "systemd.unit=rescue.target"
Is there any other way to fix this except chroot?
Thanks in advance.
Last edited by lakiluki (2015-01-13 16:45:52)

clfarron4 wrote:Did you re-generate the fglrx module or have the catalyst-hook enabled when you upgraded catalyst-test?
I did not re-generate it, but I'm pretty sure I had the catalyst-hook enabled. Not 100% sure, tho.

NetworkManager without ConsoleKit (possible?)

Hello there,
I am struggling to get NetworkManager working without consolekit since I have switched to systemd.
So far, after setting up systemd and recompiling polkit from ABS with the -systemd flag set, I "added session optional pam_systemd.so" to all relevant files in /etc/pam.d/ thus enabling systemd to divide user sessions into groups.
Once this was done, my nm-applet that didn't work at all before, now work to the extend that it is showing me all available wifi-network nearby. However, I am unable to connect to any. Once I click on a network, it tells me "Failed to activate connection" "(32) No session found for uid 1000 (Error statting file /var/run/ConsoleKit/database: No such file or directory)"
At that point I have been stuck for a while spending the past couple of days searching the internet for a (working) solution - with no luck. Does anyone of you happen to know how to solve this? I rly don't wonna install the depreciated ConsoleKit just to be able to manage wifi connections.
I'd switch to wicd but I need to be able to manage mobile broadband connections aswell and the only other option besides network manager to achieve that seems to be connman which doesn't have a working applet yet and can only be controlled by some test scripts...

I'm having the same your problem @str@ng3r.
Did you managed to solve it? How?
I already rebuilt networkmanager from abs with no luck. The applet tells me "no network devices available"...
EDIT:
** (nm-applet:388): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Rejected send message, 2 matched rules; type="method_call", sender=":1.29" (uid=1000 pid=388 comm="nm-applet ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=378 comm="NetworkManager ")
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area
** (nm-applet:388): WARNING **: Failed to register as an agent: (32) Session not found
** Message: applet now removed from the notification area
That's the relevant part of the error when launching nm-applet .
EDIT2: i recompiled network-manager-applet too enabling systemd support (as i did with networkmanager), but it does not work, the error is the same as above.
I'm using both from testing (0.9.6).
EDIT3: nm-applet works perfectly if started from root.
This is my
cat /etc/polkit-1/localauthority/50-local.d/org.freedesktop.NetworkManager.pkla
[nm-applet]
Identity=unix-group:network
Action=org.freedesktop.NetworkManager.*
ResultAny=yes
ResultInactive=yes
ResultActive=yes
(yes i added ResultInactive=yes too, but that doesn't solved the issue...). My user is in network group...
Last edited by nierro (2012-09-05 10:07:37)

How to you create a 2nd itunes account without losing content for either user

How do you create a new 2nd itunes account without losing content for either user?

Make a new user account.
System Preferences > Users & Groups

[SOLVED] systemd --user: "Failed to open private bus connection:"

EDIT: The solution was to set DBUS_SESSION_BUS_ADDRESS, as suggested by gtmanfred in irc. By putting the following before executing systemd --user, the error vanished:
export DBUS_SESSION_BUS_ADDRESS=/run/user/$(id -u)/dbus/user_bus_socket
===================
Original problem:
Everything on my box appears to be working ok, but I'm getting this error consistently in tty1 and at the top of journalctl (as user) whenever I start systemd --user:
systemd[3975]: Failed to open private bus connection: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
I roughly have my system setup per this wiki section https://wiki.archlinux.org/index.php/Sy … ur_Session. I start systemd --user via a small script in my .bash_profile. Here are my relevant dbus{.service,socket} files, from the package user-session-units mentioned in the wiki: (Edit: xorg is started through xorg-launch-helper, also from that wiki page) Edit2: I'm not using autologin. I noticed that under the autologin section of that page, DBUS_SESSION_BUS_ADDRESS is set to some path. In my setup that isn't set anywhere, so I may try to copy that later but I don't have time to play with it right now. Will post back later.
=====/usr/lib/systemd/user/dbus.service=====
[Unit]
Description=D-Bus System Message Bus
Requires=dbus.socket
[Service]
ExecStart=/usr/bin/dbus-daemon --session --address=systemd: --nofork --systemd-activation
ExecReload=/usr/bin/dbus-send --print-reply --session --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig
=====/usr/lib/systemd/user/dbus.socket=====
[Unit]
Description=D-Bus System Message Bus Socket
[Socket]
ListenStream=%t/dbus/user_bus_socket
And the output of sudo systemctl status dbus:
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Tue 2013-02-05 14:50:30 EST; 22min ago
Main PID: 369 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
└─369 /usr/bin/dbus-daemon --system --address=systemd: --no...
Feb 05 14:50:30 sellers-laptop systemd[1]: Starting D-Bus System Message Bus...
Feb 05 14:50:30 sellers-laptop systemd[1]: Started D-Bus System Message Bus.
Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 05 14:51:18 sellers-laptop dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 05 14:51:18 sellers-laptop dbus[369]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
I'm not sure what the error even means or how to go about debugging it. Any suggestions would be appreciated.
Last edited by Feynman (2013-02-05 22:07:23)

NVM...didn't notice it was already solved.
Last edited by the sad clown (2013-02-05 22:33:10)

[Not solved]systemd-tmpfiles stat(/run/user/myuser/gvfs) failed: Perm

I get this error message since a couple of days and systemd-tmpfiles service is slow to start compared to before. I have no arch-units/initscripts anymore. I update everyday but I can see no updates that sticks out in pacman-log, on the day before this failure appeared. (systemd-tools was updated 3 days before this error)
Permissions;
/run/user
drwxr-xr-x 3 root root 60 7 jun 10.51 .
drwxr-xr-x 11 root root 340 7 jun 10.51 ..
drwx------ 3 myuser myuser 80 7 jun 10.51 myuser
/run/user/myuser
drwx------ 3 myuser myuser 80 7 jun 10.51 .
drwxr-xr-x 3 root root 60 7 jun 10.51 ..
dr-x------ 2 myuser myuser 0 7 jun 10.51 gvfs
lrwxrwxrwx 1 root root 17 7 jun 10.51 X11-display -> /tmp/.X11-unix/X0
/run/user/myuser/gvfs
dr-x------ 2 myuser myuser 0 7 jun 10.51 .
drwx------ 3 myuser myuser 80 7 jun 10.51 ..
EDIT: Now I've look at the files;
/usr/lib/tmpfiles.d
totalt 160K
drwxr-xr-x 2 root root 4,0K 2 jun 15.54 .
drwxr-xr-x 167 root root 128K 7 jun 07.34 ..
-rw-r--r-- 1 root root 30 1 jun 02.28 console.conf
-rw-r--r-- 1 root root 29 27 maj 06.29 consolekit.conf
-rw-r--r-- 1 root root 719 1 jun 02.28 legacy.conf
-rw-r--r-- 1 root root 729 1 jun 02.28 systemd.conf
-rw-r--r-- 1 root root 449 1 jun 02.28 tmp.conf
-rw-r--r-- 1 root root 622 1 jun 02.28 x11.conf
And the only thing possibly close is; d /run/user 0755 root root 10d
from systemd.conf.
Last edited by swanson (2012-06-08 07:20:28)

Nope, error still there and no clue what's happening. It occurs without me trying to mount anything, no usb's, no phones and no disks.

[Solved] systemd-user-session: Best way to pass global ENV vars?

Hey guys,
So when using the [email protected] from the user-session-units what's the best / cleanest way to set global environment variables for that systemd --user instance (and thus, all programs spawned from it)?
What I'm talking about is /etc/profile and $HOME/.profile.
For example, I usally configure my XDG_CONFIG_HOME and XDG_CACHE_HOME in my ~/.profile. But since systemd --user is being started by systemd --session none of these environment variables are loaded.
The solution I've come up is to change the ExecStart in the [email protected] file to something like this:
ExecStart=/usr/bin/sh -c "source /etc/profile; source $HOME/.config/bash/environment; exec /usr/lib/systemd/systemd --user"
I know I could use the `EnvironmentFile` option to load the environment variables from a file, but it's not as flexable as a bash script.
Am I thinking about this problem wrong? Is there a more "systemd --user"-y way of solving the problem?
Last edited by EvanPurkhiser (2013-08-12 03:02:48)

I've more or less solved this using my own user-session units. I still don't know if my method would really be considered the proper way or not though.
Last edited by EvanPurkhiser (2013-08-12 03:02:19)

[SOLVED] systemd reboot and poweroff as user

I decided to try systemd and all my services are working but I cannot reboot or poweroff as user.
$ systemctl poweroff
Failed to issue method call: Access denied
Failed to issue method call: Access denied
I also get that duplicate message for systemctl reboot.
According to the systemd wiki article, I should be able to reboot and poweroff as user and even if not, I should be given the opportunity to provide the root password, but I was not. Both commands work as expected if I su to root. Any suggestions? Thanks.
Last edited by kekules_dream (2012-08-13 10:14:50)

@Smasher816 - the op is right that he/she should be able to reboot, shutdown without superuser access with systemd. I just began using systemd and mine seems to work fine. You aren't logged in as root or another user in another terminal or tty are you? I know that you should STILL be given the option to enter the root password and shutdown, but that is the best I can think of at the moment

[SOLVED] systemd without consolekit: systemd-cgls, no /user/myname

Similar Messages

Maybe you are looking for