Systemd --user issues
Hi,
upon running
systemctl --user status
I get
Failed to read server status: Input/output error
Here are my dumps of systemctl status user@$UID and journalctl -b _SYSTEMD_UNIT=[email protected] I know pulseaudio is not starting correctly, I probably still have it set up to start the service instead of the socket. Wanted to change that but --user is not working at all. Any tips welcome!
mauritiusdadd wrote:
Is that the only message displayed? Is there anything interesting in the journal? What is the output of the following commands?
systemctl status dbus.service
systemctl status --no-pager
systemctl --state failed --no-pager
Here is dbus, systemctl status --no-pager and failed. Tor fails with this, so it doesn't seem to be related.
karol wrote:https://bbs.archlinux.org/viewtopic.php?id=186232 ?
I read the thing and at the end he says it was a conflicting symlink. How can I find that? I don't know from logs what is causing the issue and browsing through folders I don't see anything specific. Tor is the only failing service and there is just 1 symlink pointing at the correct place. For pulseaudio I don't see a symlink at all.
Similar Messages
-
Pulseaudio and systemd --user: DBus scope issues?
Hi,
I have a multi-seat setup, so I need user-wide pulseaudio and whatnot. I'm trying to setup my boot through systemd --user.
Testing audio working apps are firefox, mpv, and mpd. The problem is:
- If I start pulseaudio and mpd manually everything is fine (no use of systemd)
- If I start pulseaudio through systemd no application has sound.
- If I start pulseaudio and mpd through systemd only mpd has sound.
raimundoyamtech~$ cat .config/systemd/user/pulseaudio.service
[Unit]
Description=PulseAudio Sound System
After=sound.target
[Service]
ExecStart=/usr/bin/pulseaudio
[Install]
WantedBy=multi-user.target
raimundoyamtech~$ cat .config/systemd/user/mpd.service
[Unit]
Description=Music Player Daemon
After=network.target sound.target
[Service]
ExecStart=/usr/bin/mpd %h/.config/mpd/mpd.conf --no-daemon
ExecStop=/usr/bin/mpd %h/.config/mpd/mpd.conf --kill
Restart=always
[Install]
WantedBy=multi-user.target
If I add BusName=org.pulseaudio.Server to the pulseaudio.service nothing changes.
Using pulseaudio's autospawn=yes leads to what seems to be same behaviour: mpd by systemd starts pulseaudio and is the only app with sound.
./config/pulse/client.conf only contains default-sink. Everything else is default.
Using alsa alone is not an option because of firefox.
Any thoughts?
EDIT:
raimundoyamtech~$ systemctl --version
systemd 208
+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
raimundoyamtech~$ pulseaudio --version
pulseaudio 4.0
Last edited by Raimundo (2013-10-23 10:08:13)ewaller wrote:
Please do not bump. I understand the frustration; really, I do. But, these are very active forums with some very good technical people lurking about. I guarantee your post had been read. I read it. I did not have an answer, as I have never seen that behavior afore. I am certain that was true for many other regulars.
In the future, you can bring focus to a thread by providing more information.. Tell us what you have tried, what you have read since the last post, etc. At least it gives the impression that you are working the problem rather than merely waiting for a response.
I don't know almost anything about systemd, especially because it changes so rapidly and documention is so scarce and outdated that either I read the whole documentantion for my version in hopes of finding my problem (something for which I do not have time) or post a topic.
I posted everything I touched regarding systemd since the installation of my system, that's all the relevant information I know I can give, so at this point I had no more info to give.
Actually posting a topic is really my last resort, it usually means that I have already tried everything I knew and I'm hopeless already.
raimundoyamtech~$ loginctl list-sessions
SESSION UID USER SEAT
2 1002 carla seat0
1 1000 raimundo seat0
2 sessions listed.
raimundoyamtech~$ loginctl show-session 1
Id=1
Timestamp=Tue 2013-10-29 12:33:47 WET
TimestampMonotonic=6670234
VTNr=1
TTY=tty1
Remote=no
Service=login
Scope=session-1.scope
Leader=1456
Audit=1
Type=tty
Class=user
Active=no <----- Is this what you are talking about?
State=online
IdleHint=yes
IdleSinceHint=1383050072367636
IdleSinceHintMonotonic=0
Name=raimundo
raimundoyamtech~$ loginctl show-session 2
Id=2
Timestamp=Tue 2013-10-29 12:33:47 WET
TimestampMonotonic=6667439
VTNr=2
TTY=tty2
Remote=no
Service=login
Scope=session-2.scope
Leader=1453
Audit=2
Type=tty
Class=user
Active=no <----- Is this what you are talking about?
State=online
IdleHint=yes
IdleSinceHint=1383050025387636
IdleSinceHintMonotonic=0
Name=carla
raimundoyamtech~$ loginctl show-session 3
Failed to issue method call: No such file or directory
What is an active session? Oo Never heard of it
I could start things. Pulseaudio started, so did mpd. I also have a /usr/lib/systemd/systemd --user process started for each user. I assumed this would be it since this
raimundoyamtech~$ systemctl --user
Failed to issue method call: Process /bin/false exited with status 1
always happens and I've read that systemctl --user is no longer required.
[EDIT]
Fixed it. Don't remember where I read that it wasn't required, just that it was in the same place I found someone else complaining about getting this error.
For anyone else encountering this: sed -i s/system-auth/system-login/g /etc/pam.d/systemd-user
and systemctl --user will work. Insults fly out to the one who wrote it wasn't required!
Still am not able to get an active session though
[/EDIT]
Why would there be a need for anything else? I'm gonna check on that. Thanks!
See, the bump worked ^^ but ok I'll try to refrain from doing that next time. Sorry.
Last edited by Raimundo (2013-10-29 16:27:55) -
Trying to setup systemd user instance
Hi guys!
For the past few days I have been trying to setup systemd to run a user instance (user is 'hans'). Sadly, I have been unable to find a lot of detail in doing this, so much of my work has been trial and error. Just recently I learned about the [email protected] and also about loginctl enable-linger. However to what degree they are related to setting up a user instance, I do not know. I set the user 'hans' to 'linger' using the loginctl enable-linger hans command, however I think I might have misunderstood the significance of the command in relation to what I am trying to do.
What I want to for user 'hans' to have his own service file, i.e. irssi.service, and start/stop/enable/disable/etc that service independently of the system. I realize that I could use sudo and configure it to only allow certain commands, and more than that have individual 'system' services for each user, i.e. hansirssi.service, janeirssi.service, joeirssi.service, etc., but I don't want to have to do that unless there is no other option.
So Question 1:
Is it possible to setup up systemd user instances as I envision it? Or have I misunderstood something?
My system:
[root@ru ~]# uname -a
Linux ru 3.5.4-1-ARCH #1 SMP PREEMPT Sat Sep 15 08:12:04 CEST 2012 x86_64 GNU/Linux
The system is installed in a Proxmox virtual machine with a virtio virtual HDD and standard setup. It is a headless system. I have a complete systemd conversion as per the wiki plus polkit 0.107-2 for use with 'loginctl'.
I tried:
[root@ru ~]$ systemctl enable [email protected]
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@ru ~]$ systemctl start [email protected]
[root@ru ~]# systemctl status [email protected]
[email protected] - User Manager for hans
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
Active: active (running) since Fri, 21 Sep 2012 18:33:07 +0100; 42min ago
Main PID: 23189 (systemd)
Status: "Startup finished in 822us."
CGroup: name=systemd:/user/hans/shared
â 23190 (sd-pam)
â systemd-23189
â 23189 /usr/lib/systemd/systemd --user
And on the user account hans I confirm that the service is running:
[hans@ru ~]$ systemctl status [email protected]
[email protected] - User Manager for hans
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
Active: active (running) since Fri, 21 Sep 2012 18:33:07 +0100; 13s ago
Main PID: 23189 (systemd)
Status: "Startup finished in 822us."
CGroup: name=systemd:/user/hans/shared
â 23190 (sd-pam)
â systemd-23189
â 23189 /usr/lib/systemd/systemd --user
But in regard to actually starting/stopping/enabling a user specific service, I keep getting this error:
[hans@ru ~]$ systemctl start dummyservice.service
Failed to issue method call: Access denied
and when I try by accessing the 'user' instance, I get the following error:
[hans@ru ~]$ systemctl --user
Failed to get D-Bus connection: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
The thing is that dbus is running:
[root@ru ~]# systemctl status dbus
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Thu, 20 Sep 2012 18:19:18 +0100; 24h ago
Main PID: 248 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
â 248 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
Sep 21 18:12:40 ru dbus-daemon[248]: dbus[248]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Sep 21 18:12:40 ru dbus[248]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Sep 21 18:17:50 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.26" (uid.../init ")
Sep 21 18:17:50 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.26" (uid=1000 pid=23167 c...n/init ")
Sep 21 18:32:46 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.31" (uid.../init ")
Sep 21 18:32:46 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.31" (uid=1000 pid=23185 c...n/init ")
Sep 21 18:35:45 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.34" (uid.../init ")
Sep 21 18:35:45 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.34" (uid=1000 pid=23195 c...n/init ")
Sep 21 18:36:06 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.35" (uid.../init ")
Sep 21 18:36:06 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.35" (uid=1000 pid=23197 c...n/init ")
Here is the full output from 'journalctl':
Sep 21 18:17:50 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.26" (uid=1000 pid=23167 comm="systemctl enable [email protected] ") interface="org.freedesktop.systemd1.Manager" member="EnableUnitFiles" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Sep 21 18:17:50 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.26" (uid=1000 pid=23167 comm="systemctl enable [email protected] ") interface="org.freedesktop.systemd1.Manager" member="EnableUnitFiles" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Sep 21 18:32:46 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.31" (uid=1000 pid=23185 comm="systemctl start [email protected] ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Sep 21 18:32:46 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.31" (uid=1000 pid=23185 comm="systemctl start [email protected] ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Sep 21 18:33:07 ru systemd[23189]: Failed to open private bus connection: Failed to connect to socket /run/user/hans/dbus/user_bus_socket: No such file or directory
Sep 21 18:35:45 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.34" (uid=1000 pid=23195 comm="systemctl start userservice ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Sep 21 18:35:45 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.34" (uid=1000 pid=23195 comm="systemctl start userservice ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Sep 21 18:36:06 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.35" (uid=1000 pid=23197 comm="systemctl start userservice.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Sep 21 18:36:06 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.35" (uid=1000 pid=23197 comm="systemctl start userservice.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Question 2:
Why would dbus reject the 'messages', is there something I need to configure (permissions,...?) in order to get this to work?
I suspect that it is my lacking knowledge to blame for this problem, which is why I have sought help here.
EDIT#1:
I forgot to show you what 'loginctl' was doing:
[root@ru ~]# loginctl user-status hans
hans (1000)
Since: Thu, 20 Sep 2012 18:19:18 +0100; 24h ago
State: lingering
CGroup: name=systemd:/user/hans
â shared
â 23190 (sd-pam)
â systemd-23189
â 23189 /usr/lib/systemd/systemd --user
Last edited by sunite (2012-09-21 18:17:35)I just went through the install process, read through the user-session-units doc, I was finally able to get the user instance working, no Dbus errors . However I decided to make sure and run 'dbus-monitor' within the user 'hans' and I got the following error message:
Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
I checked and there is no such file, however I checked the dbus.socket:
[root@ru user]# cat /usr/lib/systemd/user/dbus.socket
[Unit]
Description=D-Bus System Message Bus Socket
[Socket]
ListenStream=%t/dbus/user_bus_socket
And dbus.service:
[root@ru user]# dbus-monitor
Failed to open connection to session bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
[root@ru user]# cat /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
and as far as I can tell everything see alright there.
EDIT#1:
I just restarted the system to see if my symlink worked for the user-session service. It did, sort of, however the following error occured during boot:
Sep 21 22:15:14 ru systemd[307]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
Last edited by sunite (2012-09-21 21:22:11) -
[SOLVED]MPD, PulseAudio & Systemd/User
Since the advent of skype 4.3 I've had to switch to using pulseaudio. Things seems to be working fine except for the interaction between pulseaudio and mpd. My goal is to attain the same functionality as I had before when I was just using alsa. The main problem seems to be that the mpd daemon starts before pulseaudio. This means that when I reboot, for example, my music doesn't automatically keep playing. However if I toggle mpc (or open ncmpcpp and unpause) then it works fine.
What I have done
1) I installed mpd using the script found on the wiki
1a) copied ~/.config/mpd/mpd.conf to /etc/mpd.conf and uncomment #user line so it runs as my user
1b) enabled the mpd service with systemctl so it starts on boot, as directed to from 1)
2) Applied the workaround detailed here to make pulseaudio play nice with mpd
From what I can understand this results in the mpd daemon using the /etc/mpd.conf file which mirrors my local one (but I think the process is still started as root?)
If I don't do 2) then I get a problem where if I try to open pavucontrol I get an error saying I'm unable to connect and the system feels very unresponsive. Two second delays navigating around in thunar for example.
fuser /dev/snd/* outputs
» sudo fuser /dev/snd/*
/dev/snd/controlC0: 440
/dev/snd/controlC1: 440
/dev/snd/pcmC0D0p: 440m
» ps aux | grep 440
quiv 440 1.2 0.1 495964 13248 ? Sl 15:16 0:05 /usr/bin/pulseaudio --start --log-target=syslog
quiv 2259 0.0 0.0 11668 2296 pts/0 S+ 15:23 0:00 grep --color=auto 440
For now I have added in
if grep -q "state: pause" /home/quiv/.config/mpd/state; then
mpc toggle
fi
to my ~/.xinitrc as a work around to get pulse and mpd to work together properly. However it doesn't seem to work all the time. If I leave my music playing then when I reboot the system with reboot it seems that somtimes the state is being saved as paused, and other times as play. I suppose I could just mpc toggle without checking, but I don't want a situation where if I happen to not be playing music that every time I reboot my music starts playing.
Other things I have tried are;
A) not using pulseaudio with mpd.
B) not using systemd to manage mpd. Instead I manually started it in .xinitrc and pointed it to my ~/.config/mpd/mpd.conf file. I believe this means it runs as my own user instead of as root. When I did this I commented the username line and also undid 2) from above in ~/.config/mpd/mpd.conf
The problem with A) is that if I use alsa with mpd, mpd hogs my soundcard. My card becomes unselectable in pavucontrol and I cannot use it with pulseaudio., meanng no skype. The benefit of doing this (this is how I used to do it before I needed pulseaudio) is I have no problems with mpd's state being saved incorrectly.
The problem with B) is the mpdstate is saved incorrectly when for example I issue reboot. I can reproduce this by changing my currently played song then rebooting. When I boot back up mpd resumes playback from the previous session instead of recognizing the last thing I was playing. I had a search around on the forums and I found this issue which seems to describe what is happening. There doesn't seem to be a solution there instead a suggestion to user systemd (which I would like to do!) instead to manage mpd. Rasi's post details a unit file but I'm unsure what to do with this.
Looking at the wiki it seems like maybe I am supposed to provide this file so that it overwrites the default mpd.service unit. So I followed the steps listed there. First I created the directory /etc/systemd/system/mpd.d/ then made the user.conf file inside. I tried just putting the additional arguments in
[Service]
User=YOUR_USER
PAMName=system-local-login
I also remember trying to overwrite the entire [Service] section of the original by using
[Service]
User=YOUR_USER
PAMName=system-local-login
ExecStart=
ExecStart=/usr/bin/mpd --no-daemon
because I think just adding the addtional parameters might not have worked. But I'm not sure on this point, maybe both ways worked. This seemed to work but I had the same problem as above. The state was still being saved incorrectly sometimes when I rebooted. I would get a previous session instead of the most recent change. So I tried the other method for overwriting systemd unit files and made the file /etc/systemd/system/mpd.service in which I pasted Rasi's entire unit file. This also seemed to work, but still the incorrect state problem happened.
At this point I didn't know what to try. It seemed like the only option left was to set up mpd using a local configuration and setting up a systemd/User session and managing it that way. The wiki indiciated that if I did it this way I would not have to use the method 2) above. However I was/still am hesistant about doing this. I'm new to arch and the systemd/User wiki page seems very intimidating. I worry that I will create problems that I won't understand how to solve using this method just for the chance that mpd will function correclty with pulse. However I seemed to have exhausted all my possible options so I thought whatever I'll try it anyway! I'm certain I probably haven't done it right however.
So once again I turned to the wiki to help me with setting this up. However I can't make sense of the article. I don't know if I should follow ONLY the Setup since systemd 206 or if I should follow both setup sections? I decided to follow only the first section. I use no DE so I commented out the
[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx
line in my ~/.zprofile. When I set up my system I followed the Automatic login to virtual console. I left this file alone, but upon second thoughts maybe I should have disabled this too? I don't understand if using xlogin-git to austoart Xorg, as described in the systemd/User page, requires me to get rid of this too. I think xlogin-git just starts Xorg so automatic login via getty should be fine?
Immediately when I boot in using systemd to manage my session I notice that there are problems. I don't think my environment variables are being sourced from .zshenv because my panel fails to load. If I kill the panel and load it again it works. This makes me think there is something wrong with the order of units started with systemd.
» sudo journalctl --this-boot --no-pager | grep -i panel ~
Jul 05 16:25:39 lorelai bash[494]: /home/quiv/.config/bspwm/panel/panel: line 16: : No such file or directory
Jul 05 16:25:39 lorelai bash[494]: /home/quiv/.config/bspwm/panel/panel: line 17: : No such file or directory
Jul 05 16:25:39 lorelai bash[494]: /home/quiv/.config/bspwm/panel/panel: line 18: : No such file or directory
In each instance panel is trying to do things based on $PANEL_FIFO which is exported from ~/.zshenv but it doesn't appear to be set at the time systemd starts things up. Apart from these problems, which are probably undoubtedly due to the fact I failed to set up systemd/User properly, I still have problems with mpd. The state seems to be remembered correctly now, however when I reboot I still have to toggle mpc for it to start playback. It seems to be the same problem as when I use setup detailed intially. I suspect perhaps once again there is something wrong with the order here. MPD starts before pulse so it doesn't find anything to play through, then once I issue the mpc toggle command pulse is started and all is happy.
A final note is that I was getting this error yesterday when using systemd/User
● mpd.service - Music Player Daemon
Loaded: loaded (/usr/lib/systemd/system/mpd.service; enabled)
Active: inactive (dead)
Jul 05 03:11:41 lorelai pulseaudio[450]: [pulseaudio] module-jackdbus-detect.c: Unable to contact D-Bus session bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Jul 05 03:11:41 lorelai pulseaudio[450]: [pulseaudio] module.c: Failed to load module "module-jackdbus-detect" (argument: "channels=2"): initialization failed.
Jul 05 03:11:41 lorelai pulseaudio[450]: [pulseaudio] main.c: Module load failed.
Jul 05 03:13:35 lorelai systemd[1]: Stopping Music Player Daemon...
Jul 05 03:13:35 lorelai systemd[1]: Stopped Music Player Daemon.
but it doesn't seem to happen anymore.
Also I have no idea if I'm even supposed to use it like this but
» sudo systemctl --user enable mpd ~
Failed to get D-Bus connection: Connection refused
I tried this because I was wondering if mpd was even using the correct service when using systemd/User. I thought perhaps it just was using the one in /etc/systemd/system/ instead of /usr/lib/systemd/user/. I'm still not sure about this.
In the end I've exhausted whatever I can think of. I'm sure I've done a lot of things wrong but I tried my best. Hopefully somebody knows what I've done wrong and can help me.
~/.config/mpd/mpd.conf
# An example configuration file for MPD.
# Read the user manual for documentation: http://www.musicpd.org/doc/user/
# Files and directories #######################################################
# This setting controls the top directory which MPD will search to discover the
# available audio files and add them to the daemon's online database. This
# setting defaults to the XDG directory, otherwise the music directory will be
# be disabled and audio files will only be accepted over ipc socket (using
# file:// protocol) or streaming files over an accepted protocol.
music_directory "~/Music"
# This setting sets the MPD internal playlist directory. The purpose of this
# directory is storage for playlists created by MPD. The server will use
# playlist files not created by the server but only if they are in the MPD
# format. This setting defaults to playlist saving being disabled.
playlist_directory "~/.config/mpd/playlists"
# This setting sets the location of the MPD database. This file is used to
# load the database at server start up and store the database while the
# server is not up. This setting defaults to disabled which will allow
# MPD to accept files over ipc socket (using file:// protocol) or streaming
# files over an accepted protocol.
db_file "~/.config/mpd/database"
# These settings are the locations for the daemon log files for the daemon.
# These logs are great for troubleshooting, depending on your log_level
# settings.
# The special value "syslog" makes MPD use the local syslog daemon. This
# setting defaults to logging to syslog, otherwise logging is disabled.
log_file "~/.config/mpd/log"
# This setting sets the location of the file which stores the process ID
# for use of mpd --kill and some init scripts. This setting is disabled by
# default and the pid file will not be stored.
pid_file "~/.config/mpd/pid"
# This setting sets the location of the file which contains information about
# most variables to get MPD back into the same general shape it was in before
# it was brought down. This setting is disabled by default and the server
# state will be reset on server start up.
state_file "~/.config/mpd/state"
# The location of the sticker database. This is a database which
# manages dynamic information attached to songs.
sticker_file "~/.config/mpd/sticker.sql"
# General music daemon options ################################################
# This setting specifies the user that MPD will run as. MPD should never run as
# root and you may use this setting to make MPD change its user ID after
# initialization. This setting is disabled by default and MPD is run as the
# current user.
#user "quiv"
# This setting specifies the group that MPD will run as. If not specified
# primary group of user specified with "user" setting will be used (if set).
# This is useful if MPD needs to be a member of group such as "audio" to
# have permission to use sound card.
#group "nogroup"
# This setting sets the address for the daemon to listen on. Careful attention
# should be paid if this is assigned to anything other then the default, any.
# This setting can deny access to control of the daemon.
# For network
bind_to_address "127.0.0.1"
# And for Unix Socket
bind_to_address "~/.config/mpd/socket"
# This setting is the TCP port that is desired for the daemon to get assigned
# to.
port "6600"
# This setting controls the type of information which is logged. Available
# setting arguments are "default", "secure" or "verbose". The "verbose" setting
# argument is recommended for troubleshooting, though can quickly stretch
# available resources on limited hardware storage.
log_level "default"
# If you have a problem with your MP3s ending abruptly it is recommended that
# you set this argument to "no" to attempt to fix the problem. If this solves
# the problem, it is highly recommended to fix the MP3 files with vbrfix
# (available from <http://www.willwap.co.uk/Programs/vbrfix.php>), at which
# point gapless MP3 playback can be enabled.
gapless_mp3_playback "yes"
# Setting "restore_paused" to "yes" puts MPD into pause mode instead
# of starting playback after startup.
#restore_paused "no"
# This setting enables MPD to create playlists in a format usable by other
# music players.
#save_absolute_paths_in_playlists "no"
# This setting defines a list of tag types that will be extracted during the
# audio file discovery process. The complete list of possible values can be
# found in the mpd.conf man page.
#metadata_to_use "artist,album,title,track,name,genre,date,composer,performer,disc"
# This setting enables automatic update of MPD's database when files in
# music_directory are changed.
auto_update "yes"
# Limit the depth of the directories being watched, 0 means only watch
# the music directory itself. There is no limit by default.
auto_update_depth "3"
# Symbolic link behavior ######################################################
# If this setting is set to "yes", MPD will discover audio files by following
# symbolic links outside of the configured music_directory.
#follow_outside_symlinks "yes"
# If this setting is set to "yes", MPD will discover audio files by following
# symbolic links inside of the configured music_directory.
#follow_inside_symlinks "yes"
# Zeroconf / Avahi Service Discovery ##########################################
# If this setting is set to "yes", service information will be published with
# Zeroconf / Avahi.
#zeroconf_enabled "yes"
# The argument to this setting will be the Zeroconf / Avahi unique name for
# this MPD server on the network.
#zeroconf_name "Music Player"
# Permissions #################################################################
# If this setting is set, MPD will require password authorization. The password
# can setting can be specified multiple times for different password profiles.
#password "password@read,add,control,admin"
# This setting specifies the permissions a user has who has not yet logged in.
#default_permissions "read,add,control,admin"
# Database #######################################################################
#database {
# plugin "proxy"
# host "other.mpd.host"
# port "6600"
# Input #######################################################################
input {
plugin "curl"
proxy "proxy.isp.com:8080"
proxy_user "user"
proxy_password "password"
# Audio Output ################################################################
# MPD supports various audio output types, as well as playing through multiple
# audio outputs at the same time, through multiple audio_output settings
# blocks. Setting this block is optional, though the server will only attempt
# autodetection for one sound card.
# An example of an ALSA output:
#audio_output {
# type "alsa"
# name "My ALSA Device"
## device "hw:0,0" # optional
## mixer_type "hardware" # optional
## mixer_device "default" # optional
## mixer_control "PCM" # optional
## mixer_index "0" # optional
audio_output {
type "pulse"
name "pulse audio"
format "48000:16:2"
## server "127.0.0.1"
## sink "remote_server_sink" # optional
# An example of an OSS output:
#audio_output {
# type "oss"
# name "My OSS Device"
## device "/dev/dsp" # optional
## mixer_type "hardware" # optional
## mixer_device "/dev/mixer" # optional
## mixer_control "PCM" # optional
# An example of a shout output (for streaming to Icecast):
#audio_output {
# type "shout"
# encoding "ogg" # optional
# name "My Shout Stream"
# host "localhost"
# port "8000"
# mount "/mpd.ogg"
# password "hackme"
# quality "5.0"
# bitrate "128"
# format "44100:16:1"
## protocol "icecast2" # optional
## user "source" # optional
## description "My Stream Description" # optional
## url "http://example.com" # optional
## genre "jazz" # optional
## public "no" # optional
## timeout "2" # optional
## mixer_type "software" # optional
# An example of a recorder output:
#audio_output {
# type "recorder"
# name "My recorder"
# encoder "vorbis" # optional, vorbis or lame
# path "/var/lib/mpd/recorder/mpd.ogg"
## quality "5.0" # do not define if bitrate is defined
# bitrate "128" # do not define if quality is defined
# format "44100:16:1"
# An example of a httpd output (built-in HTTP streaming server):
#audio_output {
# type "httpd"
# name "My HTTP Stream"
# encoder "vorbis" # optional, vorbis or lame
# port "8000"
# bind_to_address "0.0.0.0" # optional, IPv4 or IPv6
## quality "5.0" # do not define if bitrate is defined
# bitrate "128" # do not define if quality is defined
# format "44100:16:1"
# max_clients "0" # optional 0=no limit
# An example of a pulseaudio output (streaming to a remote pulseaudio server)
#audio_output {
# type "pulse"
# name "My Pulse Output"
## server "remote_server" # optional
## sink "remote_server_sink" # optional
# An example of a winmm output (Windows multimedia API).
#audio_output {
# type "winmm"
# name "My WinMM output"
## device "Digital Audio (S/PDIF) (High Definition Audio Device)" # optional
# or
## device "0" # optional
## mixer_type "hardware" # optional
# An example of an openal output.
#audio_output {
# type "openal"
# name "My OpenAL output"
## device "Digital Audio (S/PDIF) (High Definition Audio Device)" # optional
## Example "pipe" output:
#audio_output {
# type "pipe"
# name "my pipe"
# command "aplay -f cd 2>/dev/null"
## Or if you're want to use AudioCompress
# command "AudioCompress -m | aplay -f cd 2>/dev/null"
## Or to send raw PCM stream through PCM:
# command "nc example.org 8765"
# format "44100:16:2"
## An example of a null output (for no audio output):
#audio_output {
# type "null"
# name "My Null Output"
# mixer_type "none" # optional
# If MPD has been compiled with libsamplerate support, this setting specifies
# the sample rate converter to use. Possible values can be found in the
# mpd.conf man page or the libsamplerate documentation. By default, this is
# setting is disabled.
#samplerate_converter "Fastest Sinc Interpolator"
# Normalization automatic volume adjustments ##################################
# This setting specifies the type of ReplayGain to use. This setting can have
# the argument "off", "album", "track" or "auto". "auto" is a special mode that
# chooses between "track" and "album" depending on the current state of
# random playback. If random playback is enabled then "track" mode is used.
# See <http://www.replaygain.org> for more details about ReplayGain.
# This setting is off by default.
replaygain "album"
# This setting sets the pre-amp used for files that have ReplayGain tags. By
# default this setting is disabled.
replaygain_preamp "0"
# This setting sets the pre-amp used for files that do NOT have ReplayGain tags.
# By default this setting is disabled.
#replaygain_missing_preamp "0"
# This setting enables or disables ReplayGain limiting.
# MPD calculates actual amplification based on the ReplayGain tags
# and replaygain_preamp / replaygain_missing_preamp setting.
# If replaygain_limit is enabled MPD will never amplify audio signal
# above its original level. If replaygain_limit is disabled such amplification
# might occur. By default this setting is enabled.
#replaygain_limit "yes"
# This setting enables on-the-fly normalization volume adjustment. This will
# result in the volume of all playing audio to be adjusted so the output has
# equal "loudness". This setting is disabled by default.
#volume_normalization "no"
# MPD Internal Buffering ######################################################
# This setting adjusts the size of internal decoded audio buffering. Changing
# this may have undesired effects. Don't change this if you don't know what you
# are doing.
#audio_buffer_size "4096"
# This setting controls the percentage of the buffer which is filled before
# beginning to play. Increasing this reduces the chance of audio file skipping,
# at the cost of increased time prior to audio playback.
#buffer_before_play "10%"
# Resource Limitations ########################################################
# These settings are various limitations to prevent MPD from using too many
# resources. Generally, these settings should be minimized to prevent security
# risks, depending on the operating resources.
#connection_timeout "60"
#max_connections "10"
#max_playlist_length "16384"
#max_command_list_size "2048"
#max_output_buffer_size "8192"
# Character Encoding ##########################################################
# If file or directory names do not display correctly for your locale then you
# may need to modify this setting.
#filesystem_charset "UTF-8"
# This setting controls the encoding that ID3v1 tags should be converted from.
#id3v1_encoding "ISO-8859-1"
# SIDPlay decoder #############################################################
# songlength_database:
# Location of your songlengths file, as distributed with the HVSC.
# The sidplay plugin checks this for matching MD5 fingerprints.
# See http://www.c64.org/HVSC/DOCUMENTS/Songlengths.faq
# default_songlength:
# This is the default playing time in seconds for songs not in the
# songlength database, or in case you're not using a database.
# A value of 0 means play indefinitely.
# filter:
# Turns the SID filter emulation on or off.
#decoder {
# plugin "sidplay"
# songlength_database "/media/C64Music/DOCUMENTS/Songlengths.txt"
# default_songlength "120"
# filter "true"
/etc/mpd.config
# An example configuration file for MPD.
# Read the user manual for documentation: http://www.musicpd.org/doc/user/
# Files and directories #######################################################
# This setting controls the top directory which MPD will search to discover the
# available audio files and add them to the daemon's online database. This
# setting defaults to the XDG directory, otherwise the music directory will be
# be disabled and audio files will only be accepted over ipc socket (using
# file:// protocol) or streaming files over an accepted protocol.
music_directory "~/Music"
# This setting sets the MPD internal playlist directory. The purpose of this
# directory is storage for playlists created by MPD. The server will use
# playlist files not created by the server but only if they are in the MPD
# format. This setting defaults to playlist saving being disabled.
playlist_directory "~/.config/mpd/playlists"
# This setting sets the location of the MPD database. This file is used to
# load the database at server start up and store the database while the
# server is not up. This setting defaults to disabled which will allow
# MPD to accept files over ipc socket (using file:// protocol) or streaming
# files over an accepted protocol.
db_file "~/.config/mpd/database"
# These settings are the locations for the daemon log files for the daemon.
# These logs are great for troubleshooting, depending on your log_level
# settings.
# The special value "syslog" makes MPD use the local syslog daemon. This
# setting defaults to logging to syslog, otherwise logging is disabled.
log_file "~/.config/mpd/log"
# This setting sets the location of the file which stores the process ID
# for use of mpd --kill and some init scripts. This setting is disabled by
# default and the pid file will not be stored.
pid_file "~/.config/mpd/pid"
# This setting sets the location of the file which contains information about
# most variables to get MPD back into the same general shape it was in before
# it was brought down. This setting is disabled by default and the server
# state will be reset on server start up.
state_file "~/.config/mpd/state"
# The location of the sticker database. This is a database which
# manages dynamic information attached to songs.
sticker_file "~/.config/mpd/sticker.sql"
# General music daemon options ################################################
# This setting specifies the user that MPD will run as. MPD should never run as
# root and you may use this setting to make MPD change its user ID after
# initialization. This setting is disabled by default and MPD is run as the
# current user.
user "quiv"
# This setting specifies the group that MPD will run as. If not specified
# primary group of user specified with "user" setting will be used (if set).
# This is useful if MPD needs to be a member of group such as "audio" to
# have permission to use sound card.
#group "nogroup"
# This setting sets the address for the daemon to listen on. Careful attention
# should be paid if this is assigned to anything other then the default, any.
# This setting can deny access to control of the daemon.
# For network
bind_to_address "127.0.0.1"
# And for Unix Socket
bind_to_address "~/.config/mpd/socket"
# This setting is the TCP port that is desired for the daemon to get assigned
# to.
port "6600"
# This setting controls the type of information which is logged. Available
# setting arguments are "default", "secure" or "verbose". The "verbose" setting
# argument is recommended for troubleshooting, though can quickly stretch
# available resources on limited hardware storage.
log_level "default"
# If you have a problem with your MP3s ending abruptly it is recommended that
# you set this argument to "no" to attempt to fix the problem. If this solves
# the problem, it is highly recommended to fix the MP3 files with vbrfix
# (available from <http://www.willwap.co.uk/Programs/vbrfix.php>), at which
# point gapless MP3 playback can be enabled.
gapless_mp3_playback "yes"
# Setting "restore_paused" to "yes" puts MPD into pause mode instead
# of starting playback after startup.
#restore_paused "no"
# This setting enables MPD to create playlists in a format usable by other
# music players.
#save_absolute_paths_in_playlists "no"
# This setting defines a list of tag types that will be extracted during the
# audio file discovery process. The complete list of possible values can be
# found in the mpd.conf man page.
#metadata_to_use "artist,album,title,track,name,genre,date,composer,performer,disc"
# This setting enables automatic update of MPD's database when files in
# music_directory are changed.
auto_update "yes"
# Limit the depth of the directories being watched, 0 means only watch
# the music directory itself. There is no limit by default.
auto_update_depth "3"
# Symbolic link behavior ######################################################
# If this setting is set to "yes", MPD will discover audio files by following
# symbolic links outside of the configured music_directory.
#follow_outside_symlinks "yes"
# If this setting is set to "yes", MPD will discover audio files by following
# symbolic links inside of the configured music_directory.
#follow_inside_symlinks "yes"
# Zeroconf / Avahi Service Discovery ##########################################
# If this setting is set to "yes", service information will be published with
# Zeroconf / Avahi.
#zeroconf_enabled "yes"
# The argument to this setting will be the Zeroconf / Avahi unique name for
# this MPD server on the network.
#zeroconf_name "Music Player"
# Permissions #################################################################
# If this setting is set, MPD will require password authorization. The password
# can setting can be specified multiple times for different password profiles.
#password "password@read,add,control,admin"
# This setting specifies the permissions a user has who has not yet logged in.
#default_permissions "read,add,control,admin"
# Database #######################################################################
#database {
# plugin "proxy"
# host "other.mpd.host"
# port "6600"
# Input #######################################################################
input {
plugin "curl"
proxy "proxy.isp.com:8080"
proxy_user "user"
proxy_password "password"
# Audio Output ################################################################
# MPD supports various audio output types, as well as playing through multiple
# audio outputs at the same time, through multiple audio_output settings
# blocks. Setting this block is optional, though the server will only attempt
# autodetection for one sound card.
# An example of an ALSA output:
#audio_output {
# type "alsa"
# name "My ALSA Device"
## device "hw:0,0" # optional
## mixer_type "hardware" # optional
## mixer_device "default" # optional
## mixer_control "PCM" # optional
## mixer_index "0" # optional
audio_output {
type "pulse"
name "pulse audio"
format "48000:16:2"
server "127.0.0.1"
## sink "remote_server_sink" # optional
# An example of an OSS output:
#audio_output {
# type "oss"
# name "My OSS Device"
## device "/dev/dsp" # optional
## mixer_type "hardware" # optional
## mixer_device "/dev/mixer" # optional
## mixer_control "PCM" # optional
# An example of a shout output (for streaming to Icecast):
#audio_output {
# type "shout"
# encoding "ogg" # optional
# name "My Shout Stream"
# host "localhost"
# port "8000"
# mount "/mpd.ogg"
# password "hackme"
# quality "5.0"
# bitrate "128"
# format "44100:16:1"
## protocol "icecast2" # optional
## user "source" # optional
## description "My Stream Description" # optional
## url "http://example.com" # optional
## genre "jazz" # optional
## public "no" # optional
## timeout "2" # optional
## mixer_type "software" # optional
# An example of a recorder output:
#audio_output {
# type "recorder"
# name "My recorder"
# encoder "vorbis" # optional, vorbis or lame
# path "/var/lib/mpd/recorder/mpd.ogg"
## quality "5.0" # do not define if bitrate is defined
# bitrate "128" # do not define if quality is defined
# format "44100:16:1"
# An example of a httpd output (built-in HTTP streaming server):
#audio_output {
# type "httpd"
# name "My HTTP Stream"
# encoder "vorbis" # optional, vorbis or lame
# port "8000"
# bind_to_address "0.0.0.0" # optional, IPv4 or IPv6
## quality "5.0" # do not define if bitrate is defined
# bitrate "128" # do not define if quality is defined
# format "44100:16:1"
# max_clients "0" # optional 0=no limit
# An example of a pulseaudio output (streaming to a remote pulseaudio server)
#audio_output {
# type "pulse"
# name "My Pulse Output"
## server "remote_server" # optional
## sink "remote_server_sink" # optional
# An example of a winmm output (Windows multimedia API).
#audio_output {
# type "winmm"
# name "My WinMM output"
## device "Digital Audio (S/PDIF) (High Definition Audio Device)" # optional
# or
## device "0" # optional
## mixer_type "hardware" # optional
# An example of an openal output.
#audio_output {
# type "openal"
# name "My OpenAL output"
## device "Digital Audio (S/PDIF) (High Definition Audio Device)" # optional
## Example "pipe" output:
#audio_output {
# type "pipe"
# name "my pipe"
# command "aplay -f cd 2>/dev/null"
## Or if you're want to use AudioCompress
# command "AudioCompress -m | aplay -f cd 2>/dev/null"
## Or to send raw PCM stream through PCM:
# command "nc example.org 8765"
# format "44100:16:2"
## An example of a null output (for no audio output):
#audio_output {
# type "null"
# name "My Null Output"
# mixer_type "none" # optional
# If MPD has been compiled with libsamplerate support, this setting specifies
# the sample rate converter to use. Possible values can be found in the
# mpd.conf man page or the libsamplerate documentation. By default, this is
# setting is disabled.
#samplerate_converter "Fastest Sinc Interpolator"
# Normalization automatic volume adjustments ##################################
# This setting specifies the type of ReplayGain to use. This setting can have
# the argument "off", "album", "track" or "auto". "auto" is a special mode that
# chooses between "track" and "album" depending on the current state of
# random playback. If random playback is enabled then "track" mode is used.
# See <http://www.replaygain.org> for more details about ReplayGain.
# This setting is off by default.
replaygain "album"
# This setting sets the pre-amp used for files that have ReplayGain tags. By
# default this setting is disabled.
replaygain_preamp "0"
# This setting sets the pre-amp used for files that do NOT have ReplayGain tags.
# By default this setting is disabled.
#replaygain_missing_preamp "0"
# This setting enables or disables ReplayGain limiting.
# MPD calculates actual amplification based on the ReplayGain tags
# and replaygain_preamp / replaygain_missing_preamp setting.
# If replaygain_limit is enabled MPD will never amplify audio signal
# above its original level. If replaygain_limit is disabled such amplification
# might occur. By default this setting is enabled.
#replaygain_limit "yes"
# This setting enables on-the-fly normalization volume adjustment. This will
# result in the volume of all playing audio to be adjusted so the output has
# equal "loudness". This setting is disabled by default.
#volume_normalization "no"
# MPD Internal Buffering ######################################################
# This setting adjusts the size of internal decoded audio buffering. Changing
# this may have undesired effects. Don't change this if you don't know what you
# are doing.
#audio_buffer_size "4096"
# This setting controls the percentage of the buffer which is filled before
# beginning to play. Increasing this reduces the chance of audio file skipping,
# at the cost of increased time prior to audio playback.
#buffer_before_play "10%"
# Resource Limitations ########################################################
# These settings are various limitations to prevent MPD from using too many
# resources. Generally, these settings should be minimized to prevent security
# risks, depending on the operating resources.
#connection_timeout "60"
#max_connections "10"
#max_playlist_length "16384"
#max_command_list_size "2048"
#max_output_buffer_size "8192"
# Character Encoding ##########################################################
# If file or directory names do not display correctly for your locale then you
# may need to modify this setting.
#filesystem_charset "UTF-8"
# This setting controls the encoding that ID3v1 tags should be converted from.
#id3v1_encoding "ISO-8859-1"
# SIDPlay decoder #############################################################
# songlength_database:
# Location of your songlengths file, as distributed with the HVSC.
# The sidplay plugin checks this for matching MD5 fingerprints.
# See http://www.c64.org/HVSC/DOCUMENTS/Songlengths.faq
# default_songlength:
# This is the default playing time in seconds for songs not in the
# songlength database, or in case you're not using a database.
# A value of 0 means play indefinitely.
# filter:
# Turns the SID filter emulation on or off.
#decoder {
# plugin "sidplay"
# songlength_database "/media/C64Music/DOCUMENTS/Songlengths.txt"
# default_songlength "120"
# filter "true"
/etc/X11/xinit/xinitrc.d/pulseaudio [not sure if I even need this?]
#!/bin/bash
case "$DESKTOP_SESSION" in
gnome|kde*|xfce*) # PulseAudio is started via XDG Autostart
# Extra checks in case DESKTOP_SESSION is not set correctly
if [[ -z $KDE_FULL_SESSION && -z $GNOME_DESKTOP_SESSION_ID ]]; then
/usr/bin/start-pulseaudio-x11
fi
esac
/etc/pulse/daemon.conf
# This file is part of PulseAudio.
# PulseAudio 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 of the License, or
# (at your option) any later version.
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
# USA.
## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out. Use either ; or # for
## commenting.
; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB
; lock-memory = no
; cpu-limit = no
; high-priority = yes
; nice-level = -11
; realtime-scheduling = yes
; realtime-priority = 5
exit-idle-time=0
; exit-idle-time = 20
; scache-idle-time = 20
; dl-search-path = (depends on architecture)
; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa
; log-target = auto
log-level = error
; log-meta = no
; log-time = no
; log-backtrace = 0
resample-method = speex-float-7
; enable-remixing = yes
; enable-lfe-remixing = no
flat-volumes = no
; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; rlimit-locks = -1
; rlimit-sigpending = -1
; rlimit-msgqueue = -1
; rlimit-nice = 31
; rlimit-rtprio = 9
; rlimit-rttime = 1000000
default-sample-format = s24le
default-sample-rate = 48000
; alternate-sample-rate = 48000
; default-sample-channels = 2
; default-channel-map = front-left,front-right
default-fragments = 2
default-fragment-size-msec = 76
; enable-deferred-volume = yes
; deferred-volume-safety-margin-usec = 8000
; deferred-volume-extra-delay-usec = 0
/etc/pulse/default.pa
#!/usr/bin/pulseaudio -nF
# This file is part of PulseAudio.
# PulseAudio 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 of the License, or
# (at your option) any later version.
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software Foundation,
# Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
# This startup script is used only if PulseAudio is started per-user
# (i.e. not in system mode)
.nofail
### Load something into the sample cache
#load-sample-lazy x11-bell /usr/share/sounds/gtk-events/activate.wav
#load-sample-lazy pulse-hotplug /usr/share/sounds/startup3.wav
#load-sample-lazy pulse-coldplug /usr/share/sounds/startup3.wav
#load-sample-lazy pulse-access /usr/share/sounds/generic.wav
.fail
### Automatically restore the volume of streams and devices
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore
### Automatically augment property information from .desktop files
### stored in /usr/share/application
load-module module-augment-properties
### Should be after module-*-restore but before module-*-detect
load-module module-switch-on-port-available
### Load audio drivers statically
### (it's probably better to not load these drivers manually, but instead
### use module-udev-detect -- see below -- for doing this automatically)
#load-module module-alsa-sink
#load-module module-alsa-source device=hw:1,0
#load-module module-oss device="/dev/dsp" sink_name=output source_name=input
#load-module module-oss-mmap device="/dev/dsp" sink_name=output source_name=input
#load-module module-null-sink
#load-module module-pipe-sink
### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
### Use the static hardware detection module (for systems that lack udev support)
load-module module-detect
.endif
### Automatically connect sink and source if JACK server is present
.ifexists module-jackdbus-detect.so
.nofail
load-module module-jackdbus-detect channels=2
.fail
.endif
### Automatically load driver modules for Bluetooth hardware
#.ifexists module-bluetooth-policy.so
#load-module module-bluetooth-policy
#.endif
#.ifexists module-bluetooth-discover.so
#load-module module-bluetooth-discover
#.endif
### Load several protocols
.ifexists module-esound-protocol-unix.so
load-module module-esound-protocol-unix
.endif
load-module module-native-protocol-unix
### Network access (may be configured with paprefs, so leave this commented
### here if you plan to use paprefs)
#load-module module-esound-protocol-tcp
load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1
#load-module module-zeroconf-publish
### Load the RTP receiver module (also configured via paprefs, see above)
#load-module module-rtp-recv
### Load the RTP sender module (also configured via paprefs, see above)
#load-module module-null-sink sink_name=rtp format=s16be channels=2 rate=44100 sink_properties="device.description='RTP Multicast Sink'"
#load-module module-rtp-send source=rtp.monitor
### Load additional modules from GConf settings. This can be configured with the paprefs tool.
### Please keep in mind that the modules configured by paprefs might conflict with manually
### loaded modules.
.ifexists module-gconf.so
.nofail
load-module module-gconf
.fail
.endif
### Automatically restore the default sink/source when changed by the user
### during runtime
### NOTE: This should be loaded as early as possible so that subsequent modules
### that look up the default sink/source get the right value
load-module module-default-device-restore
### Automatically move streams to the default sink if the sink they are
### connected to dies, similar for sources
load-module module-rescue-streams
### Make sure we always have a sink around, even if it is a null sink.
load-module module-always-sink
### Honour intended role device property
load-module module-intended-roles
### Automatically suspend sinks/sources that become idle for too long
load-module module-suspend-on-idle
### If autoexit on idle is enabled we want to make sure we only quit
### when no local session needs us anymore.
.ifexists module-console-kit.so
load-module module-console-kit
.endif
.ifexists module-systemd-login.so
load-module module-systemd-login
.endif
### Enable positioned event sounds
load-module module-position-event-sounds
### Cork music/video streams when a phone stream is active
load-module module-role-cork
### Modules to allow autoloading of filters (such as echo cancellation)
### on demand. module-filter-heuristics tries to determine what filters
### make sense, and module-filter-apply does the heavy-lifting of
### loading modules and rerouting streams.
load-module module-filter-heuristics
load-module module-filter-apply
# X11 modules should not be started from default.pa so that one daemon
# can be shared by multiple sessions.
### Load X11 bell module
#load-module module-x11-bell sample=bell-windowing-system
### Register ourselves in the X11 session manager
#load-module module-x11-xsmp
### Publish connection data in the X11 root window
#.ifexists module-x11-publish.so
#.nofail
#load-module module-x11-publish
#.fail
#.endif
### Make some devices default
#set-default-sink output
#set-default-source input
~/.xinitrc [currently using daemon mpd]
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
#if grep -q "state: pause" /home/quiv/.config/mpd/state; then
# mpc toggle
#fi
#mpd ~/.config/mpd/mpd.conf
~/.config/bspwm/panel/notify_mpd
xrdb ~/.Xresources
xset +fp ~/.fonts
xset +fp /usr/share/fonts/misc
xset fp rehash
xsetroot -cursor_name left_ptr &
# imlibsetroot -x e -s f /home/quiv/Pictures/bloom_one_desktop.jpg
sh ~/.fehbg &
compton -CGb --backend glx --paint-on-overlay --vsync opengl-swc &
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
sxhkd &
exec bspwm
~/.zprofile [currently trying to use systemd/User]
#[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx
EDIT:A small update; it seems I don't need to have /etc/systemd/system/[email protected]/autologin.conf when using systemd to manag my user session as I removed it and I'm both automatically logged on and in X-session.
Last edited by quiv (2014-07-05 13:40:30)o_caino wrote:
Setting mpd as a systemd user service is very simple. This is what I did.
In ~/.config/systemd/user/mpd.service
[Unit]
Description=Music Player Daemon
After=network.target sound.target
[Service]
ExecStart=/usr/bin/mpd --no-daemon
ExecStop=/usr/bin/mpd --kill
[Install]
WantedBy=default.target
To enable
systemctl --user enable mpd
Done.
Well shit. I guess I didn't need to do all that other stuff. I only wish I'd known about this before wasting most of my day. Thank you very much, everything appears to be working flawlessly now. -
[Solved] Systemd user service and timer dbus error
I have installed arch recently and added a few of my own services, for example the acpi_call commands and such. Now I want to create a systemd service that runs every 5 minutes and execute a script.
I searched a lot and I found that I must use timers. I got the thing with the timers working, but because my script has to do with a specific user, I want it to run only every 5 minutes when i am logged in as that user.
I tried to put the files in /etc/systemd/users, .config/local/users and all the possibilities but everytime i want to enable it, it says dbus connection refused.
Can somebody please provide me a way to execute a systemd service every 5 minutes while I am logged in as a specific user?
I did follow the wiki and created a dbus service and all. Everything works on that side but i can't enable my user service.
thanks!
Last edited by nopemopes (2015-03-25 11:10:06)jasonwryan wrote:
What errors are you getting? https://bbs.archlinux.org/viewtopic.php?id=57855
Not a Sysadmin issue, moving to NC...
sorry, didn't mean to be incomplete.
The error says "Failed to get D-Bus connection: Connection refused".
I did what the wiki said: Create the dbus files, enable them and such.
No i put my service files + timer in the places mentioned by the wiki but everytime i try to enable them, that error shows up.
systemctl status dbus gives me all good
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
Active: active (running) since ma 2015-03-23 19:39:24 CET; 1h 18min ago
Docs: man:dbus-daemon(1)
Main PID: 246 (dbus-daemon)
CGroup: /system.slice/dbus.service
└─246 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='...ervice'
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1....ectory.
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='...ervice'
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1....ectory.
mrt 23 19:39:39 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
mrt 23 19:39:39 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mrt 23 19:47:01 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
mrt 23 19:47:01 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mrt 23 20:51:38 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
mrt 23 20:51:38 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
that's the log for dbus and these are my files:
drive_sync.service
[Unit]
Description=Drive sync
[Service]
Type=simple
ExecStart=drive_script.sh
drive_sync.timer
[Unit]
Description=Drive sync
[Service]
Type=simple
ExecStart=drive_script.sh
these files are located in ~/.config/systemd/user
Last edited by nopemopes (2015-03-23 20:00:55) -
Systemd 206 systemd --user problem
Hi!
I was using xorg-launch-helper and user-session-units previously (systemd 204), and everything worked flawlessly.
Since i upgraded to systemd 206, those units won't work. So i came back to old .xinitrc, autologin to vt and autostart x. Well...it isn't working.
In .xinitrc I have "exec /usr/lib/systemd/systemd" so i guess that is the problem.
In fact, just putting in .xinitrc
#exec /usr/lib/systemd/systemd
xfce4-panel &
xfdesktop &
exec xfwm4
works as expected.
What should i do in order to go on using my systemd --user session? And, if it is possible, how can i go on using xorg-launch-helper and user-session-units too?
Thanks!
EDIT: starting /usr/lib/systemd/systemd gives me:
Failed to create root cgroup hierarchy: Permission denied
Failed to allocate manager object: Permission denied
Last edited by nierro (2013-07-23 15:51:33)falconindy wrote:Not at all related. You should never need to be a part of the audio group -- this is the point of uaccess and ACLs. Doing this can lead to problems, as you're seeing.
Well, this is the first time that I've run into that rather small note in the wiki about systemd supposedly rendering most group membership redundant. So I've removed myself from those listed there, and now I'm really having issues:
Previously mpv would simply complain about insufficient rights for playback, now it won't even find the soundcard (neither does alsamixer anymore). Similar for video playback, which (with opengl as vo) is now refused.
Note that this is a relatively fresh setup (1 month) without any custom configuration for audio nor video.
edit: Found the reason, methinks. I don't use a login manager and thus, without session management, the permissions granted by logind are apparently not transferred to the tty X actually runs on. Previously the group memberships still gave me all the missing permissions, no the don't anymore (for audio). I don't see anything immediately relevant to fix this in the wiki, but I'll update this post if I find a solution.
edit2: After some misadventures with user@/slim, which brought me deeper into the troubles talked about in this thread (plus spontaneous xserver combustion, mpd still missing the same rights, zshenv ignored with user@, etc.), I noticed falconindy's fixes in systemd-git. Installed that, and whereas it would somewhat work now with slim (eg. with a session dependent tmux), it's back to the ever-so-outdated but perfectly working, minimal mingetty+groups again.
Last edited by misc (2013-07-25 13:53:09) -
Systemd --user can't create cpu cgroup
Hi,
recently I've started using 'systemd --user' to manage my sessions. I've followed the wiki and created xorg.service and several others. Then I configured cgroup controllers in /etc/systemd/{system.conf,logind.conf,user.conf} as follows (only relevant changes are shown):
$ logind.conf
[Login]
Controllers=cpu memory blkio
ResetControllers=
$ system.conf
[Manager]
DefaultControllers=cpu memory blkio
#JoinControllers=cpu,cpuacct,cpuset net_cls,net_prio
$ user.conf
[Manager]
DefaultControllers=cpu memory blkio
When I start 'systemd --user', I get the following error (systemd starts fine, but cpu controller for user isn't created):
Failed to create cgroup cpu:/user/lahwaacz/8/systemd-11815/xorg.service: Permission denied
edit: the error shows up for every service started, not just for xorg.service
I guess this is why the default is 'ResetControllers=cpu', but haven't found anything specific to the error. Anyone has experiences with similar issues, or anything helpful?
Thanks
Last edited by lahwaacz (2013-01-09 17:09:00)I found a fix online that removing the SIP information will fix the issue. It did but when I do that they have no control over their phone from Lync.
Hi,
would you please elaborate about the message above you provided? Did "SIP information" mean user profile?
If yes, it maybe the issue of address book sync. you can try to force Lync to immediately download the address book with the following way:
execute the following command from the Windows Command Prompt run as an administrator;
reg add HKLM\Software\Policies\Microsoft\Office\15.0\Lync /v GalDownloadInitialDelay /t REG_DWORD /d 0 /f
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support -
Trouble with some custom SystemD/User unit files
Good evening all,
I'm trying to move programs out of my .xinitrc file and my window manager's startup hooks into systemd user unit files for ease of management, and hopefully more resilient. I have followed the setup on the wiki page for SystemD/User session (https://wiki.archlinux.org/index.php/Sy … asic_setup) and already have some services already running:
╭─vendion@tyre ~
╰─➤ systemctl --user status
● tyre
State: degraded
Jobs: 0 queued
Failed: 4 units
Since: Fri 2014-08-08 20:23:47 EDT; 4 days ago
CGroup: /user.slice/user-1000.slice/[email protected]
├─3200 /usr/lib/systemd/systemd --user
├─3202 (sd-pam)
├─dbus.service
│ ├─ 3623 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation
│ ├─ 3711 /usr/lib/at-spi2-core/at-spi-bus-launcher
│ ├─ 3728 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
│ ├─ 3996 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
│ ├─ 4184 /usr/lib/GConf/gconfd-2
│ └─29638 /usr/bin/dunst
├─udiskie.service
│ └─3389 /usr/bin/python /usr/bin/udiskie
├─spideroak.service
│ ├─3394 /opt/SpiderOak/lib/SpiderOak
│ └─3993 /opt/SpiderOak/lib/SpiderOak --spider
├─skype.service
│ └─3396 /usr/lib32/skype/skype
├─mpd.service
│ ├─3386 /usr/bin/mpd --no-daemon
│ ├─3959 /usr/bin/pulseaudio --start --log-target=syslog
│ └─4178 /usr/lib/pulse/gconf-helper
├─mpdscribble.service
│ └─3544 /usr/bin/mpdscribble
└─google-musicmanager.service
└─3638 /usr/bin/google-musicmanager
Some of them are using unit files provided by the package, others I wrote the unit file for. The services that are failing that are causing the state to be degraded are:
╭─vendion@tyre ~
╰─➤ systemctl --user --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
●clipit.service loaded failed failed Clipboard manager
●pasystray.service loaded failed failed Pulseaudio system tray icon
●pidgin.service loaded failed failed Pidgin IM client
●redshift.service loaded failed failed Redshift display colour temperature adjustment
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
4 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
I had to write the unit files for each of these.
clipit.service unit file: http://sprunge.us/Qjfd
When I check the status for this here is what I get:
● clipit.service - Clipboard manager
Loaded: loaded (/home/vendion/.config/systemd/user/clipit.service; enabled)
Active: failed (Result: start-limit) since Fri 2014-08-08 20:24:04 EDT; 4 days ago
Main PID: 3619 (code=exited, status=1/FAILURE)
Aug 08 20:24:04 tyre systemd[3200]: clipit.service: main process exited, code=exited, status=1/FAILURE
Aug 08 20:24:04 tyre systemd[3200]: Unit clipit.service entered failed state.
Aug 08 20:24:04 tyre systemd[3200]: clipit.service holdoff time over, scheduling restart.
Aug 08 20:24:04 tyre systemd[3200]: Stopping Clipboard manager...
Aug 08 20:24:04 tyre systemd[3200]: Starting Clipboard manager...
Aug 08 20:24:04 tyre systemd[3200]: clipit.service start request repeated too quickly, refusing to start.
Aug 08 20:24:04 tyre systemd[3200]: Failed to start Clipboard manager.
Aug 08 20:24:04 tyre systemd[3200]: Unit clipit.service entered failed state.
pasystray.service unit file: http://sprunge.us/BWWR
Status output
● pasystray.service - Pulseaudio system tray icon
Loaded: loaded (/home/vendion/.config/systemd/user/pasystray.service; enabled)
Active: failed (Result: start-limit) since Fri 2014-08-08 20:24:12 EDT; 4 days ago
Main PID: 3769 (code=killed, signal=TRAP)
Aug 08 20:24:12 tyre systemd[3200]: pasystray.service: main process exited, code=killed, status=5/TRAP
Aug 08 20:24:12 tyre systemd[3200]: Unit pasystray.service entered failed state.
Aug 08 20:24:12 tyre systemd[3200]: pasystray.service holdoff time over, scheduling restart.
Aug 08 20:24:12 tyre systemd[3200]: Stopping Pulseaudio system tray icon...
Aug 08 20:24:12 tyre systemd[3200]: Starting Pulseaudio system tray icon...
Aug 08 20:24:12 tyre systemd[3200]: pasystray.service start request repeated too quickly, refusing to start.
Aug 08 20:24:12 tyre systemd[3200]: Failed to start Pulseaudio system tray icon.
Aug 08 20:24:12 tyre systemd[3200]: Unit pasystray.service entered failed state.
pidgen.service unit file: http://sprunge.us/KgKV
Status output
● pidgin.service - Pidgin IM client
Loaded: loaded (/home/vendion/.config/systemd/user/pidgin.service; enabled)
Active: failed (Result: start-limit) since Fri 2014-08-08 20:24:04 EDT; 4 days ago
Main PID: 3620 (code=exited, status=1/FAILURE)
Redshift.service unit file: http://sprunge.us/IDCC
Status output:
● redshift.service - Redshift display colour temperature adjustment
Loaded: loaded (/home/vendion/.config/systemd/user/redshift.service; enabled)
Active: failed (Result: start-limit) since Fri 2014-08-08 20:23:58 EDT; 4 days ago
Docs: http://jonls.dk/redshift/
Main PID: 3517 (code=exited, status=1/FAILURE)
Aug 08 20:23:57 tyre systemd[3200]: redshift.service: main process exited, code=exited, status=1/FAILURE
Aug 08 20:23:57 tyre systemd[3200]: Unit redshift.service entered failed state.
Aug 08 20:23:58 tyre systemd[3200]: redshift.service holdoff time over, scheduling restart.
Aug 08 20:23:58 tyre systemd[3200]: Stopping Redshift display colour temperature adjustment...
Aug 08 20:23:58 tyre systemd[3200]: Starting Redshift display colour temperature adjustment...
Aug 08 20:23:58 tyre systemd[3200]: redshift.service start request repeated too quickly, refusing to start.
Aug 08 20:23:58 tyre systemd[3200]: Failed to start Redshift display colour temperature adjustment.
Aug 08 20:23:58 tyre systemd[3200]: Unit redshift.service entered failed state.
I know that my unit files for these services work because if I manually start them with "systemctl --user start <service>" then they work just fine, but when systemD is trying to start them when I login they fail. I have dbus setup like the wiki says to, and "DBUS_SESSION_BUS_ADDRESS" is defined. I also have the DISPLAY environment variable set in /etc/systemd/system/[email protected]/display.conf like the wiki suggests as well. I know that SystemD user sessions still may not be ready for prime time but I could use a better way to manage these startup programs than the .xinitrc file.
Thanks in advance for any helpi suppose there is a code whitch resets the default bounds when
the component is beeing added to the JTable.Technically, the Component returned by the getCellRendererComponent() is not added to the JTable, it's just used as a rubber stamp.Mmm, I was wrong: at least with the basic L&F, the Component is (temporarily) added to a CellRendererPane, which is a children of the JTable.
Moreover, I witnessed that both setBounds() and doLayout() are called before the component is actually painted...
I've never used a compound component as a renderer, but I assume the issue is common (did not have time to search nor try it myself). You may investigate whether the JPanel is appropriately laid out, by inserting some breakpoints/logs at appropriate places (setBounds, doLayout,...)Did this on an extra-short example, and it did render correctly...
somehow the textfield's bounds where not set anymore.Note that the Javadoc for Cellrendererpane states that +"After the component is painted it's bounds are reset to -w, -h, 0, 0 so that, if it's the last renderer component painted, it will not start consuming input"+.
That does not explain why the w and h are 0, but at least it's clear that depending on where you put your logging statement makes a big difference about the accuracy of the bounds logged -
Systemd --user not autostarting jobs
I am playing around with the idea of switching all my user jobs to be controlled by Systemd, I followed the wiki on the matter but none of the are auto starting but work fine when I start them manually.
when my .xinitrc only contains the systemd --user line Xorg starts but nothing else starts, after changing it to
#!/bin/sh
systemd --user &
exec /home/vendion/gocode/bin/wingo
My window manager starts but nothing else does, my systemd unit files are as follows:
default.target mystuff.target mystuff.target.wants wingo.service wm.target wm.target.wants [email protected]
I ran "systemctl --user enable" on both wingo.service and [email protected], when I run the xcompmgr unit manually via "systemctl --user start xcompmgr@:0.service" it runs fine and starts up xcompmgr so I know it is not an issue with the unit file itself.
This is what my units look like:
arch-testing% cat wm.target
[Unit]
Description=Window manager target
Wants=xorg.target
Wants=mystuff.target
Requires=dbus.socket
AllowIsolate=true
[Install]
Alias=default.target
arch-testing% cat mystuff.target
[Unit]
Description=Xinitrc Stuff
Wants=wm.target
[Install]
Alias=default.target
arch-testing% cat wingo.service
[Unit]
Description=Wingo window manager service
Before=mystuff.target
After=xorg.target
Requires=xorg.target
[Service]
ExecStart=/home/vendion/gocode/bin/wingo
Restart=always
RestartSec=10
[Install]
WantedBy=wm.target
arch-testing% cat [email protected]
[Unit]
Description=xcompmgr start script
[Service]
ExecStart=/usr/bin/xcompmgr
Environment=DISPLAY=%i
[Install]
WantedBy=mystuff.target
Any clues that would help debug this issue?I am playing around with the idea of switching all my user jobs to be controlled by Systemd, I followed the wiki on the matter but none of the are auto starting but work fine when I start them manually.
when my .xinitrc only contains the systemd --user line Xorg starts but nothing else starts, after changing it to
#!/bin/sh
systemd --user &
exec /home/vendion/gocode/bin/wingo
My window manager starts but nothing else does, my systemd unit files are as follows:
default.target mystuff.target mystuff.target.wants wingo.service wm.target wm.target.wants [email protected]
I ran "systemctl --user enable" on both wingo.service and [email protected], when I run the xcompmgr unit manually via "systemctl --user start xcompmgr@:0.service" it runs fine and starts up xcompmgr so I know it is not an issue with the unit file itself.
This is what my units look like:
arch-testing% cat wm.target
[Unit]
Description=Window manager target
Wants=xorg.target
Wants=mystuff.target
Requires=dbus.socket
AllowIsolate=true
[Install]
Alias=default.target
arch-testing% cat mystuff.target
[Unit]
Description=Xinitrc Stuff
Wants=wm.target
[Install]
Alias=default.target
arch-testing% cat wingo.service
[Unit]
Description=Wingo window manager service
Before=mystuff.target
After=xorg.target
Requires=xorg.target
[Service]
ExecStart=/home/vendion/gocode/bin/wingo
Restart=always
RestartSec=10
[Install]
WantedBy=wm.target
arch-testing% cat [email protected]
[Unit]
Description=xcompmgr start script
[Service]
ExecStart=/usr/bin/xcompmgr
Environment=DISPLAY=%i
[Install]
WantedBy=mystuff.target
Any clues that would help debug this issue? -
[Solved] Starting systemd --user as a systemd --system process?
Hey guys,
I would like to run systemd --user as a system service using this .service file I wrote:
$ cat [email protected]
[Unit]
Description=Systemd --user instance for %I
Documentation=man:systemd
[Service]
User=%I
ExecStart=/usr/lib/systemd/systemd --user --log-level=debug
[Install]
WantedBy=multi-user.target
I enabled it for my user using `systemctl enable systemd-user@evan`, however, when starting it it fails with the following errors:
Jul 21 21:14:42 desktop systemd[12920]: systemd 204 running in user mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
Jul 21 21:14:42 desktop systemd[12920]: Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd/system/[email protected]/[email protected]/systemd-12920.
Jul 21 21:14:42 desktop systemd[12920]: Failed to create root cgroup hierarchy: Permission denied
Jul 21 21:14:42 desktop systemd[12920]: Failed to allocate manager object: Permission denied
Is it possible to run systemd --user like this? Do I need to add something to my [email protected]?
Last edited by EvanPurkhiser (2013-07-22 02:10:10)EDIT: I just realized that the systemd-user-session-units package will only include specific units at build-time weather I have have the programs or not. You're right, I should just use this package!
Well, to be honest, maybe I'm trying to hack around a problem that doesn't even really exist, but I don't think the systemd-user-sessions-units package meets my needs.
The way I would like to have my user sessions setup is something like this:
I would like to have an instance of systemd --user always running under my user so I can keep things like transmission-daemon always running, even when I don't have a user session open. When I do start my user session (via logging into getty) I want to bring my systemd instance up to a certain target. For example, logging in via tty1 should bring up graphical.target, which will start X11 and all that, while logging into any other tty will start console.target (for stuff like ssh-agent etc).
Thinking more about this I suppose there's really no reason I couldn't use the [email protected] from systemd-user-session-units, but since I won't use most of the other user units included, I would rather just not use it.
Here's what my .profile looks like:
if systemctl -q is-active systemd-user@evan
then
# Default systemd to the console target
target="console"
# If we're logging in from VT1 start the graphical target
if [[ $XDG_VTNR == 1 ]] && ! systemctl --user -q is-active graphical.target &> /dev/null
then
export DISPLAY=:0
target="graphical"
fi
# Set all environment variables in the systemd --user instance (still working on this)
env | systemctl --user set-environment -
# Bring up systemd --user to the specified target
systemctl --user start ${target}.target
fi
source "$HOME/.bashrc"
Last edited by EvanPurkhiser (2013-07-22 03:56:13) -
[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/User, starting a Dependent service
I am missing something simple here. I have two services. Once is dependent on the other.
I got the first service to start with:
$ cat ~/.config/systemd/user/[email protected]
[Unit]
Description=Syncthing - Open Source Continuous File Synchronization for %I
Documentation=https://github.com/syncthing/syncthing/wiki
After=network.target
[Service]
#User=%i
Environment=STNORESTART=yes
ExecStart=/usr/bin/syncthing -no-browser -logflags=0
Restart=on-failure
SuccessExitStatus=2 3 4
RestartForceExitStatus=3 4
[Install]
#WantedBy=multi-user.target
WantedBy=default.target
This autostarts upon logging in with i3 and gnome. No problem (now).
The problem I have is with the notifier/watcher:
$ cat ~/.config/systemd/user/[email protected]
[Unit]
Description=Syncthing Inotify File Watcher for %I
Documentation=https://github.com/syncthing/syncthing-inotify/blob/master/README.md
After=network.target [email protected]
[email protected]
[Service]
#User=%i
ExecStart=/usr/bin/syncthing-inotify -logflags=0
SuccessExitStatus=2
Restart=on-failure
ProtectSystem=full
ProtectHome=read-only
[Install]
#WantedBy=multi-user.target
WantedBy=default.target
Installed it into my namespace, like I did with the parent service:
$ systemctl --user enable [email protected]
On system startup/login, the service is "Dead (inactive)."
But, I can start it manually:
$ systemctl --user start [email protected]
And the status of the service shows it logging and working, picking up changes, etc.
I must be missing a configuration parameter in the service file.
Last edited by eduncan911 (2015-05-25 14:39:38)mauritiusdadd wrote:
Just a shot in the dark, but try to change the After= and Requires= lines in [email protected] to
After=network.target syncthing@%i.service
Requires=syncthing@%i.service
You know how you stay up late and everything you do right seems to be wrong?
When I ran:
systemctl status [email protected]
...it showed inactive (dead) and is the reason I made this thread.
Changed it to this:
systemctl --user status [email protected]
Allowed me to see it started. *head smack*
And btw, I tried "syncthing@%i.service" and it worked too! I reverted back to "[email protected]" to verify %i fixed it, but it started as well as before. So "%i" seems agnostic and would work as well. -
[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) -
[SOLVED] systemd user unit for lsyncd
After following the the systemd/User - Basic setup wiki article I have successfully setup user services for systemd. I've also setup a systemd user "unit" to run lsyncd. The user unit appears to start successfully based on the unit status shown below. Only problem is lsyncd isn't running and I'm not seeing any relevant errors or info with journalctl. If I run the script defined in ExecStart on the command line lsyncd starts as expected. Any ideas or pointers?
OUTPUT from "systemctl --user lsyncd.service":
lsyncd.service - lsyncd
Loaded: loaded (/home/maseone/.config/systemd/user/lsyncd.service; enabled)
Active: inactive (dead) since Thu 2014-08-28 18:14:50 PDT; 21min ago
Process: 630 ExecStart=/home/maseone/.lsyncd/start_lsyncd_simple.sh (code=exited, status=0/SUCCESS)
Main PID: 630 (code=exited, status=0/SUCCESS)
Aug 28 18:14:50 archie230x systemd[610]: Starting lsyncd...
Aug 28 18:14:50 archie230x systemd[610]: Started lsyncd.
UNIT for lsyncd:
[Unit]
Description=lsyncd
[Service]
ExecStart=/home/maseone/.lsyncd/start_lsyncd_simple.sh
[Install]
WantedBy=default.target
SCRIPT defined in ExecStart:
#! /bin/sh
/bin/lsyncd -log all /home/maseone/.lsyncd/lsyncd.lua
Last edited by maseone (2014-08-29 04:07:58)firecat53 wrote:
Try changing the service type to forking instead of simple. Or look for an lsycd option that keeps it running in the foreground.
Scott
Thanks for the pointer, it worked! After reading in detail the different types available "forking" does seem the most appropriate type for a daemon written as lsyncd. I believe using an lsyncd option named "detach" would have worked with the "simple" type but forking seemd more appropriate in my case.
Also as an update to my original post I have completely removed the use of the shell script and am now calling lsyncd directly in my defined systemd unit. Also using the %h variable for the home directory now.
REVISED unit file:
[Unit]
Description=lsyncd
[Service]
Type=forking
ExecStart=/bin/lsyncd -log scarce %h/.lsyncd/lsyncd.lua
[Install]
WantedBy=default.target -
[SOLVED] Getting my systemd user service to talk to dbus
I'm currently trying to set up a nice email workflow with mbsync, msmtp and notmuch.
My passwords are saved in the Gnome keyring "login", and I've configured mbsync to use secret-tool to retrieve them. Unfortunately when secret-tool is invoked from this systemd user service there is an error when it in turn tries to call dbus-launch.
Here is the error:
$ systemctl --user status -l mbsync.service
● mbsync.service - Synchronise IMAP folders
Loaded: loaded (/home/leo/.config/systemd/user/mbsync.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2015-05-10 20:10:56 BST; 17min ago
Process: 3691 ExecStart=/usr/bin/mbsync -a (code=exited, status=1/FAILURE)
Main PID: 3691 (code=exited, status=1/FAILURE)
May 10 20:10:55 think3 mbsync[3691]: (secret-tool:3696): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
May 10 20:10:55 think3 mbsync[3691]: secret-tool: Error spawning command line 'dbus-launch --autolaunch=388eb9d3cc5542d5922d60c8f9605b31 --binary-syntax --close-stderr': Child process exited with code 1
May 10 20:10:55 think3 mbsync[3691]: Skipping account ymail, password command exited with status 1
May 10 20:10:56 think3 mbsync[3691]: (secret-tool:3698): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
May 10 20:10:56 think3 mbsync[3691]: secret-tool: Error spawning command line 'dbus-launch --autolaunch=388eb9d3cc5542d5922d60c8f9605b31 --binary-syntax --close-stderr': Child process exited with code 1
May 10 20:10:56 think3 mbsync[3691]: Skipping account gmail, password command exited with status 1
May 10 20:10:56 think3 systemd[716]: mbsync.service: main process exited, code=exited, status=1/FAILURE
May 10 20:10:56 think3 systemd[716]: Failed to start Synchronise IMAP folders.
May 10 20:10:56 think3 systemd[716]: Unit mbsync.service entered failed state.
May 10 20:10:56 think3 systemd[716]: mbsync.service failed.
The file mbsync.service is simply
[Unit]
Description=Synchronise IMAP folders
Wants=network-online.target
After=network-online.target
[Service]
Type=oneshot
ExecStart=/usr/bin/mbsync -a
Any ideas how I can use secret-tool from within a systemd user service? The Wiki includes some information about DBus and systemd here but it looks a little outdated...
Last edited by curiousleo (2015-05-22 22:02:33)barbae wrote:Please could you post the output of 'journalctl -b' just after user login into gnome through gdm?
Sure thing. Here it is (I've cut out some stuff that obviously had nothing to do with the problem at hand):
May 17 17:17:11 think3 systemd[1]: systemd 219 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN)
May 17 17:17:11 think3 systemd[1]: Created slice Root Slice.
May 17 17:17:11 think3 systemd[1]: Starting Root Slice.
May 17 17:17:11 think3 systemd[1]: Created slice System Slice.
May 17 17:17:11 think3 systemd[1]: Starting System Slice.
May 17 17:17:11 think3 systemd[1]: Started Forward Password Requests to Wall Directory Watch.
May 17 17:17:11 think3 systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
May 17 17:17:11 think3 systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
May 17 17:17:11 think3 systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
May 17 17:17:11 think3 systemd[1]: Reached target Login Prompts.
May 17 17:17:11 think3 systemd[1]: Starting Login Prompts.
May 17 17:17:11 think3 systemd[1]: Created slice User and Session Slice.
May 17 17:17:11 think3 systemd[1]: Starting User and Session Slice.
May 17 17:17:11 think3 systemd[1]: Reached target Slices.
May 17 17:17:11 think3 systemd[1]: Starting Slices.
May 17 17:17:11 think3 systemd[1]: Started Create System Users.
May 17 17:17:11 think3 systemd[1]: Created slice system-systemd\x2drfkill.slice.
May 17 17:17:11 think3 systemd[1]: Starting system-systemd\x2drfkill.slice.
May 17 17:17:11 think3 systemd[1]: Started Commit a transient machine-id on disk.
May 17 17:17:11 think3 systemd[1]: Started Daily verification of password and group files.
May 17 17:17:11 think3 systemd[1]: Starting Daily verification of password and group files.
May 17 17:17:11 think3 systemd[1]: Listening on D-Bus System Message Bus Socket.
May 17 17:17:11 think3 systemd[1]: Starting D-Bus System Message Bus Socket.
May 17 17:17:11 think3 systemd[1]: Reached target Sockets.
May 17 17:17:11 think3 systemd[1]: Starting Sockets.
May 17 17:17:11 think3 systemd[1]: Reached target Basic System.
May 17 17:17:11 think3 systemd[1]: Starting Basic System.
May 17 17:17:11 think3 systemd[1]: Starting Login Service...
May 17 17:17:11 think3 systemd[1]: Starting Permit User Sessions...
May 17 17:17:11 think3 systemd[1]: Started D-Bus System Message Bus.
May 17 17:17:11 think3 systemd[1]: Starting D-Bus System Message Bus...
May 17 17:17:11 think3 systemd[1]: Reached target Timers.
May 17 17:17:11 think3 systemd[1]: Starting Timers.
May 17 17:17:11 think3 systemd[1]: Started Permit User Sessions.
May 17 17:17:11 think3 systemd[1]: Starting GNOME Display Manager...
May 17 17:17:11 think3 systemd[1]: Started Login Service.
May 17 17:17:12 think3 systemd[1]: Started GNOME Display Manager.
May 17 17:17:12 think3 systemd[1]: Reached target Multi-User System.
May 17 17:17:12 think3 systemd[1]: Starting Multi-User System.
May 17 17:17:12 think3 systemd[1]: Reached target Graphical Interface.
May 17 17:17:12 think3 systemd[1]: Starting Graphical Interface.
May 17 17:17:12 think3 systemd-logind[293]: New seat seat0.
May 17 17:17:12 think3 dbus[301]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
May 17 17:17:12 think3 systemd[1]: Reached target User and Group Name Lookups.
May 17 17:17:12 think3 systemd[1]: Starting User and Group Name Lookups.
May 17 17:17:12 think3 systemd[1]: Starting Accounts Service...
May 17 17:17:13 think3 dbus[301]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
May 17 17:17:13 think3 systemd[1]: Starting Authorization Manager...
May 17 17:17:13 think3 polkitd[443]: Started polkitd version 0.112
May 17 17:17:13 think3 polkitd[443]: Loading rules from directory /etc/polkit-1/rules.d
May 17 17:17:13 think3 polkitd[443]: Loading rules from directory /usr/share/polkit-1/rules.d
May 17 17:17:13 think3 polkitd[443]: Finished loading, compiling and executing 3 rules
May 17 17:17:13 think3 dbus[301]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
May 17 17:17:13 think3 polkitd[443]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
May 17 17:17:13 think3 systemd[1]: Started Authorization Manager.
May 17 17:17:13 think3 accounts-daemon[436]: started daemon version 0.6.40
May 17 17:17:13 think3 dbus[301]: [system] Successfully activated service 'org.freedesktop.Accounts'
May 17 17:17:13 think3 systemd[1]: Started Accounts Service.
May 17 17:17:13 think3 systemd[1]: Created slice user-120.slice.
May 17 17:17:13 think3 systemd[1]: Starting user-120.slice.
May 17 17:17:13 think3 systemd[1]: Starting User Manager for UID 120...
May 17 17:17:13 think3 systemd-logind[293]: New session c1 of user gdm.
May 17 17:17:13 think3 systemd[1]: Started Session c1 of user gdm.
May 17 17:17:13 think3 systemd[1]: Starting Session c1 of user gdm.
May 17 17:17:13 think3 systemd[454]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
May 17 17:17:13 think3 systemd[454]: Unit type .busname is not supported on this system.
May 17 17:17:13 think3 systemd[454]: Reached target Paths.
May 17 17:17:13 think3 systemd[454]: Starting Paths.
May 17 17:17:13 think3 systemd[454]: Reached target Timers.
May 17 17:17:13 think3 systemd[454]: Starting Timers.
May 17 17:17:13 think3 systemd[454]: Reached target Sockets.
May 17 17:17:13 think3 systemd[454]: Starting Sockets.
May 17 17:17:13 think3 systemd[454]: Reached target Basic System.
May 17 17:17:13 think3 systemd[454]: Starting Basic System.
May 17 17:17:13 think3 systemd[454]: Reached target Default.
May 17 17:17:13 think3 systemd[454]: Startup finished in 3ms.
May 17 17:17:13 think3 systemd[454]: Starting Default.
May 17 17:17:13 think3 systemd[1]: Started User Manager for UID 120.
May 17 17:17:13 think3 gnome-session[460]: glamor: EGL version 1.4 (DRI2):
May 17 17:17:13 think3 org.a11y.Bus[459]: Activating service name='org.a11y.atspi.Registry'
May 17 17:17:13 think3 org.a11y.Bus[459]: Successfully activated service 'org.a11y.atspi.Registry'
May 17 17:17:13 think3 org.a11y.atspi.Registry[518]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
May 17 17:17:14 think3 polkitd[443]: Registered Authentication Agent for unix-session:c1 (system bus name :1.9 [gnome-shell --mode=gdm --wayland --display-server], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.utf8)
May 17 17:17:18 think3 gdm-password][674]: pam_unix(gdm-password:session): session opened for user leo by (uid=0)
May 17 17:17:18 think3 systemd[1]: Created slice user-1000.slice.
May 17 17:17:18 think3 systemd[1]: Starting user-1000.slice.
May 17 17:17:18 think3 systemd[1]: Starting User Manager for UID 1000...
May 17 17:17:18 think3 systemd[1]: Started Session c2 of user leo.
May 17 17:17:18 think3 systemd-logind[293]: New session c2 of user leo.
May 17 17:17:18 think3 systemd[1]: Starting Session c2 of user leo.
May 17 17:17:18 think3 systemd[717]: pam_unix(systemd-user:session): session opened for user leo by (uid=0)
May 17 17:17:18 think3 systemd[717]: Unit type .busname is not supported on this system.
May 17 17:17:18 think3 systemd[717]: Started Synchronise e-mails and create database dump once a day.
May 17 17:17:18 think3 systemd[717]: Starting Synchronise e-mails and create database dump once a day.
May 17 17:17:18 think3 systemd[717]: Reached target default.target.
May 17 17:17:18 think3 systemd[717]: Startup finished in 13ms.
May 17 17:17:18 think3 systemd[717]: Starting default.target.
May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: /etc/gdm/Xsession: Beginning session setup...
May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: localuser:leo being added to access control list
May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: Activating service name='org.a11y.Bus'
May 17 17:17:19 think3 /usr/lib/gdm/gdm-x-session[725]: Successfully activated service 'org.a11y.Bus'
May 17 17:17:19 think3 org.a11y.Bus[732]: Activating service name='org.a11y.atspi.Registry'
May 17 17:17:19 think3 org.a11y.Bus[732]: Successfully activated service 'org.a11y.atspi.Registry'
May 17 17:17:19 think3 org.a11y.atspi.Registry[756]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
May 17 17:17:19 think3 gnome-session[734]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May 17 17:17:19 think3 gnome-session[734]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May 17 17:17:19 think3 gnome-session[734]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
May 17 17:17:20 think3 polkitd[443]: Registered Authentication Agent for unix-session:c2 (system bus name :1.43 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.utf8)
May 17 17:17:20 think3 gnome-session[734]: Entering running state
May 17 17:17:21 think3 gnome-shell[804]: GNOME Shell started at Sun May 17 2015 17:17:20 GMT+0100 (BST)
May 17 17:17:52 think3 /usr/lib/gdm/gdm-x-session[725]: Activating service name='org.gnome.seahorse.Application'
May 17 17:17:52 think3 /usr/lib/gdm/gdm-x-session[725]: Successfully activated service 'org.gnome.seahorse.Application'
May 17 17:20:48 think3 /usr/lib/gdm/gdm-x-session[725]: Activating service name='org.gnome.seahorse.Application'
May 17 17:20:48 think3 /usr/lib/gdm/gdm-x-session[725]: Successfully activated service 'org.gnome.seahorse.Application'
Maybe you are looking for
-
Splitting and InDesign CS2 file.
Going back a little old school here with the CS2. I have a file that is 100 pages and I am looking to split it into 5 different files of 20 pages apiece. I was wondering if anyone knew if that was possible.
-
How to set printer option for information broad casting
Hi I have web template theer i select information broad casting and selected by print , theer its aksing printer name? how can i give setting , if i wnat get prinetr where can i do printer setting ple let em know
-
Too many "duplicate" catalogs - how to clean them up
I have PSE5 operating in Windows XP. For the reasons I will try to explain below, I am awash with numerous copys, versions, etc of catalogs. What I want to do is to safely get rid of those catalogs I don't need/want and end up with only one catalog,
-
ASR 9000 4.2.1 l2tp vpdn config migration
Hi, I had a Cisco 7206VXR G2. I used to use vpn l2tp on the router. 7206 config are below: vpdn-group pppoe_customer description ***** redback ***** accept-dialin protocol l2tp virtual-template 10 terminate-from hostname 192.168.96.149 source-ip
-
Deployed connector has uncertain status
Hi, I am using OMBPLUS 9.2.0.2.8 OMBDEPLOY to deploy a connector using the following script. I decide if I need to deploy the connector by doing an outer join of the repository view all_iv_connectors with the runtime view all_rt_objects (based on uoi