[Solved]I deleted /etc/systemd/logind.conf by mistake

I deleted /etc/systemctl/logind.conf by mistake with
sudo rm /etc/systemd/logind.conf
How can I get that file back?
Last edited by aaa234 (2015-06-07 10:26:56)

it's ok now, I reinstalled it with
sudo pacman -S systemd
The problem is solved, thank u so much everyone.

Similar Messages

[SOLVED] /etc/systemd/system.conf: DumpCore

What's that option for?
I cannot find it by myself, sorry...
Last edited by kokoko3k (2015-01-22 15:27:50)

karol wrote:
/etc/systemd/system.conf has a man page:
man systemd-system.conf wrote: LogLevel=, LogTarget=, LogColor=, LogLocation=, DumpCore=yes, CrashShell=no, ShowStatus=yes,
CrashChVT=1, DefaultStandardOutput=journal, DefaultStandardError=inherit
Configures various parameters of basic manager operation. These options may be overridden by
the respective command line arguments. See systemd(1) for details about these command line
arguments.
but it doesn't say what does this option do.
man systemd wrote: --dump-core
Dump core on crash. This switch has no effect when run as user instance.

[SOLVED]Strange file /etc/ld.so.confe

Dear community,
Starting with filesystem 2010.01-1, after each filesystem update I am finding a file called /etc/ld.co.confe, which is a copy of /etc/ld.co.conf (this is besides the usual /etc/ld.co.conf.pacnew). I took a quick look at PKGBUILD and filesystem.install in /vas/abs/core/filesystem, there was nothing pointing to this file...
Does anyone knows its purpose? The current version is filesystem 2010.02-3.
Thanks.
Last edited by Leonid.I (2010-02-21 20:36:01)

foutrelis wrote:
That file has been created by the qt3 package's qt.install file. Apparently in sed, '-ie' is not the same as '-i -e'.
I filed a bug report here, but for now it's safe to just delete it.
Thanks.
I agree, in 'sed -ie' , 'e' will be considered as a backup suffix. Perhaps it should have been 'sed -ei'
L.
edit: wrong emoticon
Last edited by Leonid.I (2010-02-17 18:03:13)

SOLVED update blanks /etc/X11/xorg.conf.d/10-synaptics.conf

I just ran pacman -Syu and udisks2 was updated with "warning: /etc/X11/xorg.conf.d/10-synaptics.conf saved as /etc/X11/xorg.conf.d/10-synaptics.conf.pacsave". When I looked at the diffs, I noticed that it essentially had removed all contents from that file.
Is there any reason why udisks2 would do this? When I check pacman -Qo /etc/X11/xorg.conf.d/10-synaptics.conf, nothing is reported as "owning" that conf file, which is correct, since I created it myself...?
Last edited by twelveeighty (2013-01-15 16:19:32)

twelveeighty wrote:Wow - I would swear that originally there never was a 50-synaptics.conf, or I would have modified that one instead of creating one from scratch.
There wasn't. The file 10-synaptics.conf was one created by Arch. With version 1.6.2-3, they switched to the upstream config, which is 50-synaptics.conf.

[SOLVED] config in /etc/systemd (ssh, getty) resets after system upgr.

I've made changes in /etc/systemd/system/getty.target.wants/[email protected] (don't clear console at boot as per https://wiki.archlinux.org/index.php/Sy … r_boot.3F) and /etc/systemd/system/sockets.target.wants/sshd.socket (changed ssh port) but they keep getting reset after a system upgrade (not sure by what package, pacman -Qo file says that no package owns them)
I'm starting to wonder if above places are the correct place and even way to do mentioned changes.
What I want to achieve;
1) simple way to not clear console after boot
2) change what port ssh (systemd ssh socket) listens at
3) make them changes permanent and durable even after a system upgrade
My setup is pure systemd.
Last edited by ImbaLocus (2012-10-30 23:41:08)

Thank you, this works.
Have yet to do an upgrade but I'm sure configuring according to your solution will This works perfectly.
Last edited by ImbaLocus (2012-11-01 12:48:33)

[SOLVED] Shall i enable systemd-logind.service?

hi!
I'm using xfce 4.10 with consolekit. So the question is: do i need systemd-logind.service?
And, may be, can i get rid of consolekit and use this systemd feature, even if xfce4-session and slim need it?and finally, is there a good guide to help me doing this?
Thank you very much!
ps: the most important answer i need is the first
EDIT: i found now two lines in the wiki that explains better what i've to do to replace consolekit with logind.service . So all i need is an hint about the first question! Thanks again!
Last edited by nierro (2012-06-08 20:12:19)

It's running in any case - systemd starts it on its own whether you explicitly enable it or not. Confirm with "systemctl status systemd-logind.service".
You may want to investigate the "loginctl" tool that comes with systemd - it shows you what logind is doing for you.

[SOLVED] Problem with acpid and systemd-logind

Hi, I have the following problem: I want set an action, when power button is pushed, different from shutdown and I want do this with a rule in acpid. Before set a rule in acpid, I modified the /etc/systemd/logind.conf in the following way:
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
Of course I restart systemd-logind service.
After this, I run #acpi_listen and when I press the power button, the output is the following:
button/power PBTN 00000080 00000000
button/power LNXPWRBN:00 00000080 00000008
So at this point, with reference to arch wiki, I tried to set the acpid rule with a modify the /etc/acpi/handler.sh in this way:
#!/bin/bash
# Default acpi script that takes an entry for all actions
case "$1" in
button/power)
case "$2" in
PBTN)
notify-send "this is a test message"
logger 'Power button pressed'
esac
esac
Because with this setting doesn't happens nothing, I tried the alternative configuration suggested in the arch wiki, So I create a file in /etc/acpi/events/power with this content:
event=button/power
action=/etc/acpi/actions/power.sh "%e"
where power.sh has this content:
#!/bin/bash
notify-send "this is a test message"
but also in the way when I push the power button doesn't happens nothing. Can you help me?
P.S. I try to restart both service systemd-logind and acpid but the result is the same
Last edited by pepib (2015-03-09 12:07:27)

In the handler.sh script I put the getuser function and I modified the handler.sh as following:
case "$1" in
button/power)
case "$2" in
PBTN)
getuser notify-send "this is a test message"
but it continued to doesn't working. So at this point at place of getuser function I tried to put the
export XAUTHORITY="/home/user/.Xauthority"
export DISPLAY=":0.0"
but it doesn't working. Fortunately, at the end I find this possible solution http://goo.gl/Lq4TsY that use uacpid. What was the problem? Where I wrong?

Systemd logind.service reports an error: Failed to start login service

Hello,
I found this error in /var/log/errors.log and /var/log/daemon.log although my system functions normally.
It's been written there every 90 seconds!!!!:
Dec 19 23:52:59 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:54:29 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:55:59 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:57:29 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:58:59 localhost systemd[1]: Failed to start Login Service.
the process: systemd-logind.service seems to be working fine:
[xxx@archbox ~]$ sudo systemctl status systemd-logind.service
[sudo] password for xxx:
systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: activating (start) since Wed, 2012-12-19 23:49:59 CET; 49s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Main PID: 11822 (systemd-logind)
CGroup: name=systemd:/system/systemd-logind.service
└─11822 /usr/lib/systemd/systemd-logind
Dec 19 23:49:59 archbox systemd[1]: Starting Login Service...
Dec 19 23:49:59 archbox systemd-logind[11822]: New seat seat0.
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event6 (P...on)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event7 (V...us)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event4 (L...ch)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event5 (S...on)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event3 (T...ns)
Dec 19 23:49:59 archbox systemd-logind[11822]: New session 1 of user xxx.
Dec 19 23:49:59 archbox systemd-logind[11822]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-...ay.
and journalctl _PID=11822 returns:
Dec 19 23:38:01 archbox sudo[21335]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:38:01 archbox sudo[21335]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:38:01 archbox sudo[21335]: pam_unix(sudo:session): session closed for user root
Dec 19 23:38:44 archbox sudo[22682]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:38:44 archbox sudo[22682]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:38:44 archbox sudo[22682]: pam_unix(sudo:session): session closed for user root
Dec 19 23:39:10 archbox sudo[23516]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:39:10 archbox sudo[23516]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:39:29 archbox systemd[1]: systemd-logind.service operation timed out. Terminating.
Dec 19 23:39:29 archbox systemd[1]: Failed to start Login Service.
Dec 19 23:39:29 archbox systemd[1]: Unit systemd-logind.service entered failed state
Dec 19 23:39:29 archbox systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Dec 19 23:39:29 archbox systemd[1]: Stopping Login Service...
Dec 19 23:39:29 archbox systemd[1]: Starting Login Service...
Dec 19 23:39:29 archbox systemd-logind[24096]: New seat seat0.
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event6 (Power B
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event7 (Video B
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event4 (Lid Swi
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event5 (Sleep B
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event3 (ThinkPa
Dec 19 23:39:29 archbox systemd-logind[24096]: New session 1 of user xxx.
Dec 19 23:39:29 archbox systemd-logind[24096]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-displa
Dec 19 23:39:30 archbox sudo[23516]: pam_unix(sudo:session): session closed for user root
Dec 19 23:40:08 archbox sudo[25314]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:40:08 archbox sudo[25314]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:40:09 archbox sudo[25314]: pam_unix(sudo:session): session closed for user root
Dec 19 23:40:43 archbox slim[641]: error 8: BadMatch (invalid parameter attributes) request 142 mino
Dec 19 23:40:43 archbox slim[641]: error 9: BadDrawable (invalid Pixmap or Window parameter) request
Dec 19 23:40:43 archbox slim[641]: error 4: BadPixmap (invalid Pixmap parameter) request 54 minor 0
Dec 19 23:40:56 archbox sudo[26739]: xxx : TTY=pts/0 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:40:56 archbox sudo[26739]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:40:59 archbox systemd[1]: systemd-logind.service operation timed out. Terminating.
Dec 19 23:40:59 archbox systemd[1]: Failed to start Login Service.
Dec 19 23:40:59 archbox systemd[1]: Unit systemd-logind.service entered failed state
Dec 19 23:40:59 archbox systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Dec 19 23:40:59 archbox systemd[1]: Stopping Login Service...
Dec 19 23:40:59 archbox systemd[1]: Starting Login Service...
Dec 19 23:40:59 archbox systemd-logind[26935]: New seat seat0.
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event6 (Power B
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event7 (Video B
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event4 (Lid Swi
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event5 (Sleep B
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event3 (ThinkPa
Dec 19 23:40:59 archbox systemd-logind[26935]: New session 1 of user xxx.
Dec 19 23:40:59 archbox systemd-logind[26935]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-displa
Updating system with pacman didn't solve it.
Did I miss something out while migrating to systemd, is it a problem with SLiM or user session maybe ? Do you guys have any ideas where to start ? Thanks.
Last edited by nastycino (2012-12-30 17:46:43)

My /etc/systemd/logind.conf:
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# See logind.conf(5) for details
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
HandlePowerKey=poweroff
HandleSuspendKey=suspend
HandleHibernateKey=hibernate
HandleLidSwitch=suspend
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
Is there any way of reinstalling parts of systemd like logind.service?

SOLVED: Created /etc/X11/xorg.conf, now system won't boot.

I was trying to solve an issue with display resolution not sticking and it was suggested to me that I create an /etc/X11/xorg.conf.
I created the file and put in the lines that I had in my .xprofile related to xrandr.
Now... my system will not boot. It appears to get hung up trying to detect my ethernet connection. I tried Ctrl-Alt-F1 to avoid X windowing, no dice.
What's more, my system rescue pen drive appears to have died. I still have my Arch install CD.
All I want to do is delete xorg.conf. My arch root is a logical volume so I have no idea how to mount it after I boot from the Arch install CD, or if I can even do this.
Update: So embarrassing, my mount command was wrong. Once I did something that looked like this:
mount /dev/VolGroup0/root /mnt/
I was able to get into /etc/X11 and delete xorg. conf. Rebooted and all appears well.
Last edited by testingwithfire (2014-06-02 01:36:07)

For mounting LVM, this page should probably help: https://wiki.archlinux.org/index.php/LV … al_volumes
Once in, then it should be easy.

[solved] What makes systemd-logind.service fail?

After last update made yesterday I was unable to reboot. With the help of an installation cd and chrooting I disabled my graphical login manager lxdm which, when started, seems to do nothing and the system is stuck.
Without lxdm service enabled, I can start xfce4 with
startxfce4
from commandline and everything seems to run fine.
But the booting process gives me several messages telling that the service systemd-logind failed. Apart from the virtual console created while booting and the one running X11 there is no other one (no login prompt when pressing strg+alt f3 e.g.)
[root@amd64-archlinux ~]# systemctl status systemd-logind
● systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: failed (Result: start-limit) since Sun 2014-06-08 19:09:24 CEST; 5min ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/logind
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Process: 336 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
Main PID: 336 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.
Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Stopping Login Service...
Jun 08 19:09:24 amd64-archlinux systemd[1]: Starting Login Service...
Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.
Has anyone an idea where to lead me?
Last edited by bernd_b (2014-06-09 11:20:21)

I don't know if I got you point - but here is a try:
I am running X11 started manually with "startxfce4". So firing up a konsole in X11 I do and get
root@amd64-archlinux pkg]# systemctl stop systemd-logind
[root@amd64-archlinux pkg]# systemctl start systemd-logind
Job for systemd-logind.service failed. See 'systemctl status systemd-logind.service' and 'journalctl -xn' for details.
journalctl -xn:
-- Unit systemd-logind.service has begun shutting down.
Jun 08 21:38:18 amd64-archlinux systemd[1]: Starting Login Service...
-- Subject: Unit systemd-logind.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-logind.service has begun starting up.
Jun 08 21:38:18 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
Jun 08 21:38:18 amd64-archlinux systemd[1]: Failed to start Login Service.
-- Subject: Unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-logind.service has failed.
-- The result is failed.
I ran the service directly I get:
[root@amd64-archlinux pkg]# /usr/lib/systemd/systemd-logind
Failed to connect to system bus: No such file or directory
Failed to fully start up daemon: No such file or directory
What I figured out so far is this in addition:
- krusader does not start- there is no response or message in the konsole when firing up this application.
- I can only mount nfs-shares with the option "-o nolock" otherwise I get, e.g.
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
Last edited by bernd_b (2014-06-08 19:48:43)

[SOLVED]xpra + winswitch - best practice due to /etc/X11/xorg.conf.d/*

Running xpra causes some headaches.
The application builds fine and installs just perfectly, the troubles comes from the default Xorg configuration is no longer stored in /etc/X11/xorg.conf, it's now stored and read from numerous files under /etc/X11/xorg.conf.d/ where just so happen to be my 5-nvidia.conf.
Starting xpra via:
xpra start :100
Causes:
X.Org X Server 1.14.3
Release Date: 2013-09-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.11.0-1-ARCH x86_64
Current Operating System: Linux archie 3.11.2-1-ARCH #1 SMP PREEMPT Fri Sep 27 07:35:36 CEST 2013 x86_64
Kernel command line: root=/dev/sda1 rw initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
Build Date: 13 September 2013 01:28:59PM
Current version of pixman: 0.30.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/home/torxed/.xpra/Xorg.:100.log", Time: Thu Oct 3 19:56:30 2013
(++) Using config file: "/etc/xpra/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
setversion 1.4 failed
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
(EE)
Fatal server error:
(EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/home/torxed/.xpra/Xorg.:100.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
2013-10-03 19:56:30,893
2013-10-03 19:56:30,893 Xvfb command has terminated! xpra cannot continue
2013-10-03 19:56:30,894
2013-10-03 19:56:30,895 removing socket /home/torxed/.xpra/archie-100
tl;dr: 5-nvidia.conf is trying to get loaded after xf86-video-dummy is loaded (which is the default for xpra).
Now to the question: What's the best practice because there's no information about this issue, and i can't be the only one who's run in to this since the xorg.conf was removed. At the moment I move all my nvidia configs out of the way, start xpra and move them back in. This works for the better part as long as i execute xpra with my own scripts.
But is there a better way (which doesn't perhaps include recreating xorg.conf since that appears to be something you should walk away from)?
Last edited by Torxed (2013-10-04 10:29:35)

Good thinking! (xpra is basically just screen but for x, or a X11 tunnel via SSH).
After a really quick poking around and remembering that xpra really just uses xorg-server-xvfb and at the very bottom of /etc/xpra/xpra.conf there's a line that says:
xvfb=xpra_Xdummy -dpi 96 -noreset -nolisten tcp +extension GLX +extension RANDR +extension RENDER -logfile ${HOME}/.xpra/Xorg.${DISPLAY}.log -config /etc/xpra/xorg.conf
Appending -configdir appears to be working.
Here are the full steps:
[torxed@archie ~]$ sudo cp -r /etc/X11/xorg.conf.d /etc/xpra/
[torxed@archie ~]$ sudo rm /etc/xpra/xorg.conf.d/*nvidia*
[torxed@archie ~]$ sudo sed -i '$s/$/ -configdir \/etc\/xpra\/xpra.conf.d/' /etc/xpra/xpra.conf
*nvidia* would have to match your graphic-driver-config that would cause xorg-server-xvbf to crash.
I'll update the wiki and put a mention on the package about it because this either has to be standard or well known from the start because it really just breaks the package all together.
Last edited by Torxed (2013-10-04 10:29:09)

[Solved]No active session with systemd-logind

I've read all the posts on the forum about sytemd and active sessions but I can't seem to get it working.
I'm on a up to date Arch, complete systemd. I'm using GDM as DM and latest version of Gnome.
Output of loginctl show-session $XDG_SESSION_ID
1 Id=2
2 Timestamp=Sun 2013-02-03 21:53:16 CET
3 TimestampMonotonic=14881075
4 DefaultControlGroup=name=systemd:/user/peter/2
5 VTNr=0
6 Display=:0
7 Remote=no
8 Service=gdm-password
9 Leader=2712
10 Audit=2
11 Type=x11
12 Class=user
13 Active=no
14 State=online
15 KillProcesses=no
16 IdleHint=no
17 IdleSinceHint=0
18 IdleSinceHintMonotonic=0
19 Name=peter
Output of systemctl list-unit-files |grep enabled
cups.path enabled
acpid.service enabled
chrony.service enabled
cronie.service enabled
cups.service enabled
dbus-org.freedesktop.NetworkManager.service enabled
display-manager.service enabled
dkms.service enabled
gdm.service enabled
[email protected] enabled
httpd.service enabled
lm_sensors.service enabled
mysqld.service enabled
NetworkManager.service enabled
postfix.service enabled
preload.service enabled
rsyslog.service enabled
syslog.service enabled
systemd-readahead-collect.service enabled
systemd-readahead-drop.service enabled
systemd-readahead-replay.service enabled
thinkfan.service enabled
tlp-init.service enabled
tomcat6.service enabled
[email protected] enabled
unload.service enabled
upower.service enabled
acpid.socket enabled
cups.socket enabled
remote-fs.target enabled
Output of ls -lR /etc/systemd/system
/etc/systemd/system:
total 52K
drwxr-xr-x 2 root root 4.0K Nov 1 22:52 cryptsetup.target.wants/
lrwxrwxrwx 1 root root 46 Sep 24 22:02 dbus-org.freedesktop.NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
drwxr-xr-x 2 root root 4.0K Feb 3 21:42 default.target.wants/
lrwxrwxrwx 1 root root 35 Jan 28 23:33 display-manager.service -> /usr/lib/systemd/system/gdm.service
drwxr-xr-x 2 root root 4.0K Nov 8 09:10 getty.target.wants/
drwxr-xr-x 2 root root 4.0K Nov 3 20:36 graphical.target.wants/
drwxr-xr-x 2 root root 4.0K Jan 13 16:58 local-fs.target.wants/
drwxr-xr-x 2 root root 4.0K Feb 3 21:42 multi-user.target.wants/
drwxr-xr-x 2 root root 4.0K Oct 9 09:49 printer.target.wants/
-rw-r--r-- 1 root root 216 Feb 3 21:09 rc-local.service
drwxr-xr-x 2 root root 4.0K Nov 7 23:28 shutdown.target.wants/
drwxr-xr-x 2 root root 4.0K Nov 3 20:43 sockets.target.wants/
drwxr-xr-x 2 root root 4.0K Jan 13 16:58 sysinit.target.wants/
lrwxrwxrwx 1 root root 39 Nov 3 20:39 syslog.service -> /usr/lib/systemd/system/rsyslog.service
drwxr-xr-x 2 root root 4.0K Feb 3 21:42 system-update.target.wants/
-rw-r--r-- 1 root root 166 Nov 7 23:28 unload.service
/etc/systemd/system/cryptsetup.target.wants:
total 0
lrwxrwxrwx 1 root root 42 Nov 1 22:52 [email protected] -> /usr/lib/systemd/system/[email protected]
/etc/systemd/system/default.target.wants:
total 0
lrwxrwxrwx 1 root root 57 Feb 3 21:42 systemd-readahead-collect.service -> /usr/lib/systemd/system/systemd-readahead-collect.service
lrwxrwxrwx 1 root root 56 Feb 3 21:42 systemd-readahead-replay.service -> /usr/lib/systemd/system/systemd-readahead-replay.service
/etc/systemd/system/getty.target.wants:
total 0
lrwxrwxrwx 1 root root 38 Nov 8 09:10 [email protected] -> /usr/lib/systemd/system/[email protected]
/etc/systemd/system/graphical.target.wants:
total 0
lrwxrwxrwx 1 root root 40 Sep 26 22:31 tlp-init.service -> /usr/lib/systemd/system/tlp-init.service
lrwxrwxrwx 1 root root 38 Nov 3 20:36 upower.service -> /usr/lib/systemd/system/upower.service
/etc/systemd/system/local-fs.target.wants:
total 0
/etc/systemd/system/multi-user.target.wants:
total 0
lrwxrwxrwx 1 root root 37 Nov 3 20:43 acpid.service -> /usr/lib/systemd/system/acpid.service
lrwxrwxrwx 1 root root 38 Nov 7 23:10 chrony.service -> /usr/lib/systemd/system/chrony.service
lrwxrwxrwx 1 root root 38 Sep 24 22:04 cronie.service -> /usr/lib/systemd/system/cronie.service
lrwxrwxrwx 1 root root 33 Oct 9 09:49 cups.path -> /usr/lib/systemd/system/cups.path
lrwxrwxrwx 1 root root 36 Oct 11 18:03 dkms.service -> /usr/lib/systemd/system/dkms.service
lrwxrwxrwx 1 root root 37 Sep 26 18:54 httpd.service -> /usr/lib/systemd/system/httpd.service
lrwxrwxrwx 1 root root 42 Jan 14 22:47 lm_sensors.service -> /usr/lib/systemd/system/lm_sensors.service
lrwxrwxrwx 1 root root 38 Nov 8 10:53 mysqld.service -> /usr/lib/systemd/system/mysqld.service
lrwxrwxrwx 1 root root 46 Sep 24 22:02 NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
lrwxrwxrwx 1 root root 39 Oct 3 12:00 postfix.service -> /usr/lib/systemd/system/postfix.service
lrwxrwxrwx 1 root root 39 Oct 1 23:21 preload.service -> /usr/lib/systemd/system/preload.service
lrwxrwxrwx 1 root root 40 Jan 13 16:58 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
lrwxrwxrwx 1 root root 39 Nov 3 20:39 rsyslog.service -> /usr/lib/systemd/system/rsyslog.service
lrwxrwxrwx 1 root root 40 Sep 24 22:21 thinkfan.service -> /usr/lib/systemd/system/thinkfan.service
lrwxrwxrwx 1 root root 39 Oct 5 16:27 tomcat6.service -> /usr/lib/systemd/system/tomcat6.service
/etc/systemd/system/printer.target.wants:
total 0
lrwxrwxrwx 1 root root 36 Oct 9 09:49 cups.service -> /usr/lib/systemd/system/cups.service
/etc/systemd/system/shutdown.target.wants:
total 0
lrwxrwxrwx 1 root root 34 Nov 7 23:28 unload.service -> /etc/systemd/system/unload.service
/etc/systemd/system/sockets.target.wants:
total 0
lrwxrwxrwx 1 root root 36 Nov 3 20:43 acpid.socket -> /usr/lib/systemd/system/acpid.socket
lrwxrwxrwx 1 root root 35 Oct 9 09:49 cups.socket -> /usr/lib/systemd/system/cups.socket
/etc/systemd/system/sysinit.target.wants:
total 0
/etc/systemd/system/system-update.target.wants:
total 0
lrwxrwxrwx 1 root root 54 Feb 3 21:42 systemd-readahead-drop.service -> /usr/lib/systemd/system/systemd-readahead-drop.service
The solution posted here https://bbs.archlinux.org/viewtopic.php … 0#p1186900 with the rc.local compatubility service does work in a way. I created an empty rc.local file and made it executable. Now GDM is not starting until I hit CTRL-C, and after that my session is active!
I use the latest version of Polkit and initscripts is not installed.
Any tip is welcome!
Last edited by pgrond (2013-02-24 17:55:31)

I've read that post but I can't get it fixed. I don't need any rc-local compatibility. I'm on a complete systemd system, so I don't get why I would need this.
If I create a dummy rc-local service GDM won't start. But after a CTRL-C it will start and the session is active. Can it be some sort of race condition?
Or can it be a problem that my home partition is encrypted and mounted on login?

[Solved]Grub ignores commands in /etc/xen/grub.conf

I have the following lines in the file /etc/xen/grub.conf, however it completely ignores the changes I have made
#XEN_HYPERVISOR_CMDLINE="dom0_mem=-4096M dom0_vcpus_pin=true iommu=1 xsave=1"
#XEN_LINUX_CMDLINE="console=tty0"
after running
grub-mkconfig -o /boot/grub/grub.cfg
and then rebooting and runnning
sudo xl list
I get
Domain-0 0 7643 8 r----- 167.9
Last edited by TheLowEndTheory (2014-04-19 08:57:49)

Sometimes it's the simple things, I can't believe I didn't bother to check if that was a comment. I just face palmed so hard, thank you.

Got systemd-logind: failed to get session: when optirun glxgrears

I installed nvidia and bumblebee, primus.
When I tried to test optirun, I ran
optirun glxgrears -info
Then I got this,
[ 2376.692764] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) systemd-logind: failed to get session: PID 1540 does not belong to any known session
[ 2376.692829] [ERROR]Aborting because fallback start is disabled.
Here is my /var/log/Xorg.8.log ,
[ 2376.692764] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) systemd-logind: failed to get session: PID 1540 does not belong to any known session
[ 2376.692829] [ERROR]Aborting because fallback start is disabled.
[hk@hkpc ~]$ cat /var/log/Xorg.8.log
[ 2376.682]
X.Org X Server 1.16.0
Release Date: 2014-07-16
[ 2376.682] X Protocol Version 11, Revision 0
[ 2376.682] Build Operating System: Linux 3.15.5-2-ARCH x86_64
[ 2376.682] Current Operating System: Linux hkpc 3.15.8-1-ARCH #1 SMP PREEMPT Fri Aug 1 08:51:42 CEST 2014 x86_64
[ 2376.682] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=669c53af-9ee3-4bbf-b62f-14c76e81da89 rw quiet
[ 2376.682] Build Date: 31 July 2014 11:53:19AM
[ 2376.682]
[ 2376.682] Current version of pixman: 0.32.6
[ 2376.682] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2376.682] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2376.683] (==) Log file: "/var/log/Xorg.8.log", Time: Mon Aug 4 22:39:09 2014
[ 2376.683] (++) Using config file: "/etc/bumblebee/xorg.conf.nouveau"
[ 2376.683] (++) Using config directory: "/etc/bumblebee/xorg.conf.d"
[ 2376.683] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 2376.683] (==) ServerLayout "Layout0"
[ 2376.683] (==) No screen section available. Using defaults.
[ 2376.683] (**) |-->Screen "Default Screen Section" (0)
[ 2376.683] (**) | |-->Monitor "<default monitor>"
[ 2376.683] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 2376.683] (**) | |-->Device "DiscreteNvidia"
[ 2376.683] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 2376.683] (**) Option "AutoAddDevices" "false"
[ 2376.683] (**) Option "AutoAddGPU" "false"
[ 2376.683] (**) Not automatically adding devices
[ 2376.683] (==) Automatically enabling devices
[ 2376.683] (**) Not automatically adding GPU devices
[ 2376.683] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 2376.683] Entry deleted from font path.
[ 2376.683] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 2376.683] Entry deleted from font path.
[ 2376.683] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 2376.683] Entry deleted from font path.
[ 2376.683] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 2376.683] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 2376.683] Entry deleted from font path.
[ 2376.683] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 2376.683] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 2376.683] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2376.683] (==) |-->Input Device "<default pointer>"
[ 2376.684] (==) |-->Input Device "<default keyboard>"
[ 2376.684] (==) The core pointer device wasn't specified explicitly in the layout.
Using the default mouse configuration.
[ 2376.684] (==) The core keyboard device wasn't specified explicitly in the layout.
Using the default keyboard configuration.
[ 2376.684] (II) Loader magic: 0x818d80
[ 2376.684] (II) Module ABI versions:
[ 2376.684] X.Org ANSI C Emulation: 0.4
[ 2376.684] X.Org Video Driver: 18.0
[ 2376.684] X.Org XInput driver : 21.0
[ 2376.684] X.Org Server Extension : 8.0
[ 2376.685] (EE) systemd-logind: failed to get session: PID 2304 does not belong to any known session
[ 2376.686] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 2376.686] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 2376.686] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
[ 2376.688] (--) PCI:*(0:1:0:0) 10de:0fd4:1558:3700 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 2376.688] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2376.688] (II) LoadModule: "glx"
[ 2376.688] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2376.690] (II) Module glx: vendor="X.Org Foundation"
[ 2376.690] compiled for 1.16.0, module version = 1.0.0
[ 2376.690] ABI class: X.Org Server Extension, version 8.0
[ 2376.690] (==) AIGLX enabled
[ 2376.690] (II) LoadModule: "nouveau"
[ 2376.690] (WW) Warning, couldn't open module nouveau
[ 2376.690] (II) UnloadModule: "nouveau"
[ 2376.690] (II) Unloading nouveau
[ 2376.690] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 2376.690] (II) LoadModule: "mouse"
[ 2376.691] (WW) Warning, couldn't open module mouse
[ 2376.691] (II) UnloadModule: "mouse"
[ 2376.691] (II) Unloading mouse
[ 2376.691] (EE) Failed to load module "mouse" (module does not exist, 0)
[ 2376.691] (II) LoadModule: "kbd"
[ 2376.691] (WW) Warning, couldn't open module kbd
[ 2376.691] (II) UnloadModule: "kbd"
[ 2376.691] (II) Unloading kbd
[ 2376.691] (EE) Failed to load module "kbd" (module does not exist, 0)
[ 2376.691] (EE) No drivers available.
[ 2376.691] (EE)
Fatal server error:
[ 2376.691] (EE) no screens found(EE)
[ 2376.691] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 2376.691] (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional information.
What should I do?

barchiesi wrote:
Oedner wrote:after updating to linux 3.16 i got this error too. using the command without the -info works however.
Are you sure that it only doesn't work with the '-info'? I see no difference.
i just tried it a couple of times and it looks like its completely random o.O
you are right, using it (with or without -info) only works like every third attempt while the others throw the error mentioned by the op. i got that idea because it worked when i tried it. starting nvidia-settings with optirun is the same, error, working, error, working. can't say whats the problem here, i just switched to arch again recently.

[SOLVED] defect dbus service, systemd is unable to create socket

Hi,
I am experiencing serious problems with systemd & dbus.
I want to setup a gateway in a KVM VM, all was working fine till i applied my shorewall config & set to autostart (systemctl enable shorewall).
If I reboot the machine after this step one or two times, then I get a broken dbus service.
What I did than: reinstalled archlinux again (x86_x64) and setup same -> got issue again.
installed arch linux as x86 and setup same -> issue again
installed arch as x86 and configured nothing else shorewall and got this issue again after maximum of two reboots.
i found in log:
Feb 13 15:45:56 pactor systemd[1]: Failed to open private bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
I've checked this directory by hand and found that only /var/run is existing. /var/run/dbus is already not existing.
logs:
journalctl -b: http://nopaste.info/685f4c6192.html
-be aware of systemd-logind, this needs dbus and i experience same problem with other services which require dbus as dnsmasq
root@pactor ~]# systemctl status dbus
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Mi 2013-02-13 15:45:56 CET; 9min ago
Main PID: 169 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
└─169 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
[root@pactor ~]# systemctl status dbus.socket
dbus.socket - D-Bus System Message Bus Socket
Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static)
Active: active (running) since Mi 2013-02-13 15:45:56 CET; 9min ago
Feb 13 15:45:56 pactor systemd[1]: Listening on D-Bus System Message Bus Socket.
systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: activating (start) since Mi 2013-02-13 16:00:56 CET; 48s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Main PID: 338 (systemd-logind)
CGroup: name=systemd:/system/systemd-logind.service
└─338 /usr/lib/systemd/systemd-logind
Feb 13 16:00:56 pactor systemd[1]: Failed to start Login Service.
Feb 13 16:00:56 pactor systemd[1]: Unit systemd-logind.service entered failed state
Feb 13 16:00:56 pactor systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Feb 13 16:00:56 pactor systemd[1]: Stopping Login Service...
Feb 13 16:00:56 pactor systemd[1]: Starting Login Service...
installed packages: http://nopaste.info/1d1be9adad.html
shorewall config: shorewall_conf.tar
Last edited by debijan (2013-02-20 20:13:47)

oh man... found the reason due to help of some guys on systemd irc... big thx to falconindy and alxchk.
shorewall's SUBSYSLOCK option in shorewall.conf is by default set to /var/lock/shorewall.
but the arch wiki point that it should be set to /var/run: https://wiki.archlinux.org/index.php/Router
definitely wrong! that deletes the /var/run symlink and created a directory intstead.
to set the SUBSYSLOCK on default is working like a charm.
look also for this: https://bbs.archlinux.org/viewtopic.php?id=151285
could somebody modify the wiki in the meantime, i will hold this thread on -not-solved in the meantime
edit:/ oh man this wrong info in wiki did cost me a lot of time :-/
Last edited by debijan (2013-02-13 22:09:35)

[Solved]I deleted /etc/systemd/logind.conf by mistake

Similar Messages

Maybe you are looking for