[Solved] custom systemd service error: Error spawning dbus-launch

Hello!
I wroted a shell script to change gnome background
gsettings set org.gnome.desktop.background picture-uri "/tmp/wallpaper.jpg"
After that i wrote a systemd wall.service file to launch it
[Unit]
Description=Change wallpaper
After=gdm.service
[Service]
Type=oneshot
ExecStart=test.sh
[Install]
WantedBy=graphical.target
When i try systemctl start wall.service, nothing happens and systemctl status wall.service gives me
dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=74d66c08eacb4e12a2219f3fe74c245b --binary-syntax --close-stderr': Child process exited with code 1
Where the problem hides?
Last edited by anptr (2014-06-12 18:08:17)

tomk wrote:Not a gnome user myself, but if I wanted something to change the wallpaper in my Openbox setup I wouldn't involve systemd at all. I would have thought gnome would have some utility for this built-in, but if not use nitrogen, feh, or other such tools.
This.
Really, you are just trying to make things overly complex.  But I was just trying to tell you how to achieve your goal along the path you were taking.  I too wouldn't involve systemd for such a task.  The advantages that systemd provides just aren't necessary for such a process.
Edit: Besides that, I think you would have to specify the $DISPLAY as well somewhere in that setup.  Either in the service file or the script you wrote.
Last edited by WonderWoofy (2014-06-08 15:49:01)

Similar Messages

  • [SOLVED] A custom systemd service doesn't execute a specific command

    I have made a custom service which should set screen brightness.
    file: /etc/systemd/system/backlight100.service
    [Unit]
    Description=Set screen brightness
    [Service]
    Type=oneshot
    ExecStart=/bin/echo 100 > /sys/class/backlight/intel_backlight/brightness
    ExecStart=/usr/bin/beep
    [Install]
    WantedBy=multi-user.target
    (beep is there so I can know for sure that the script runs)
    The problem is, when I run "# systemctl start backlight100.service" I can hear the beep but it doesn't change the brightness. When I run "/bin/echo 100 > /sys/class/backlight/intel_backlight/brightness" in terminal it does change the brightness... but not when I start or restart the service.
    Here's the output of systemctl status backlight100.service after starting it
    backlight100.service - Set screen brightness
    Loaded: loaded (/etc/systemd/system/backlight100.service; enabled)
    Active: inactive (dead) since Fri 2013-04-05 20:17:32 AMT; 3min 19s ago
    Process: 27698 ExecStart=/usr/bin/beep (code=exited, status=0/SUCCESS)
    Process: 27696 ExecStart=/bin/echo 100 > /sys/class/backlight/intel_backlight/brightness (code=exited, status=0/SUCCESS)
    Apr 05 20:17:32 work systemd[1]: Starting Set screen brightness...
    Apr 05 20:17:32 work echo[27696]: 100 > /sys/class/backlight/intel_back...ss
    Apr 05 20:17:32 work systemd[1]: Started Set screen brightness.
    What am I doing wrong here? Any help appreciated.
    Last edited by axper (2013-04-05 18:35:24)

    msthev wrote:$ man systemd.service
    ExecStart=
    Note that this setting does not directly support shell command
    lines. If shell command lines are to be used they need to be passed
    explicitly to a shell implementation of some kind. Example:
    ExecStart=/bin/sh -c 'dmesg | tac'
    Thanks, changing ExecStart line to
    ExecStart=/bin/bash -c '/bin/echo 100 > /sys/class/backlight/intel_backlight/brightness'
    solved the issue. Though I can recall seeing ExecStart lines with direct shell commands.
    Raynman wrote:
    You should look at tmpfiles.d.
    https://wiki.archlinux.org/index.php/Sy … rary_files
    I'll do that, thanks!

  • Run custom systemd service before NetworkManager

    Hi, I am trying to write a systemd service that runs and completes before NetworkManager.service starts.
    I tried this:
    [Unit]
    Description=Custom service test
    Before=NetworkManager.service
    [Service]
    Type=oneshot
    ExecStart=/usr/bin/echo Custom service test 1
    ExecStart=/usr/bin/sleep 5
    ExecStart=/usr/bin/echo Custom service test 2
    [Install]
    WantedBy=network.target
    While the custom service does start, I got this rather strange output:
    Jan 22 00:12:46 localhost echo[1166]: Custom service test 1
    Jan 22 00:12:48 localhost kernel: NVRM: GPU at 0000:02:00: GPU-(snip)
    ... some unrelated messages (acpid, kdm, etc) ...
    Jan 22 00:12:49 localhost systemd-logind[1170]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
    Jan 22 00:13:13 localhost echo[1254]: Custom service test 2
    Jan 22 00:12:50 localhost systemd[1]: Started Custom service test.
    Jan 22 00:12:50 localhost systemd[1]: Starting Network Manager...
    As you can see, while everything appears in the expected order in the log, the timestamps look very wrong. The "Custom service test 2" says "00:13:13", yet it is in the middle of "00:12:49" and "00:12:50". What gives?
    Also, notice that the first echo was at 00:12:46, but NetworkManager started at 00:12:50, which is only 4 seconds later. The "sleep" in the custom services should have made it start at 00:12:51 at the earliest. I don't understand why things are not being respected.
    The output I'd expect to see is something like this:
    Jan 22 00:12:46 localhost echo[1166]: Custom service test 1
    Jan 22 00:12:51 localhost echo[1254]: Custom service test 2
    Jan 22 00:12:51 localhost systemd[1]: Started Custom service test.
    Jan 22 00:12:51 localhost systemd[1]: Starting Network Manager...
    I have also made sure that it shows up in NetworkManager.service's After list:
    $ systemctl show -p After NetworkManager.service
    After=mycustomservice.service syslog.target systemd-journald.socket dbus.socket basic.target

    falconindy wrote:Sooooo this begs the question: what are you really trying to do?
    I'm trying to write a script that changes the interface's MAC address before NetworkManager gets a chance to take over the network interface. I'm aware that there's a page about exactly that on the wiki. I started with the systemd service from the bottom of the page, which says "Before=dhcpcd@%i.service". I changed that line to use "NetworkManager.service", and I changed the ExecStart line to "/usr/bin/macchanger -A myinterface" in order to get a random MAC address, instead of setting a fixed one like the example shows. Then I saw that macchanger's output was being mixed with NetworkManager's output in the journal, so I decided to try and write a custom service just for testing, making it start before NetworkManager, in order to see if it really was systemd's fault or if it was something macchanger-specific. Then I noticed the strange behavior described in the OP, didn't really know what to do about it, so I posted this topic. That's the story so far...
    Last edited by WindPower (2013-01-23 00:13:22)

  • [SOLVED] Running Systemd service on login (encrypted home partition)

    Hi,
    I have a dm-crypt/LUKS encrypted home partition that's mounted via PAM on login. I'm trying to use a systemd service (profile-sync-daemon), but the service tries to start and access the home partition before the partition is mounted. The service does seem to start successfully, but it doesn't gain access to necessary files on the home partition and malfunctions later on. Is there a sane hack to somehow delay the start of the service until the relevant partition gets mounted (basically after login)? Manually starting the service after login works just as intended in this case - I'm just looking for a way to automate this process.
    I have an idea of starting the service via Openbox autostart, but I've currently failed in my attempts.
    Last edited by ggg377 (2015-05-28 18:31:10)

    Things got quite complicated and hacky as I researched this so I went out of the box a bit (or took the easy way out, whichever you prefer) and reinstalled Arch with a full disk encryption. All is fine now and I also expect to see less problems overall in the future. If anyone wants to continue researching this it would probably be a good idea to start a new thread.

  • Custom ESS Service Error

    I have created one custom apppppciation for ESS Service...and getting the following error..Any help is appreciated?
    java.lang.NullPointerException
            at com.sap.xss.config.FPMRepository$RepositoryKey.hashCode(FPMRepository.java:46)
            at java.util.HashMap.hash(HashMap.java:261)
            at java.util.HashMap.get(HashMap.java:317)
            at com.sap.xss.config.FPMRepository.retrieveObjectInternal(FPMRepository.java:79)
            at com.sap.xss.config.FPMRepository.retrieveObject(FPMRepository.java:66)
            at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.initializeConfiguration(FcXssPcd.java:816)
            at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.loadConfiguration(FcXssPcd.java:250)
            at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcd.loadConfiguration(InternalFcXssPcd.java:178)
            at com.sap.pcuigp.xssutils.ccpcd.FcXssPcdInterface.loadConfiguration(FcXssPcdInterface.java:138)
            at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface.loadConfiguration(InternalFcXssPcdInterface.java:148)
            at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface$External.loadConfiguration(InternalFcXssPcdInterface.java:240)
            at com.sap.pcuigp.xssutils.ccpcd.CcXssPcd.loadConfiguration(CcXssPcd.java:282)
            at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcd.loadConfiguration(InternalCcXssPcd.java:184)
            at com.sap.pcuigp.xssutils.ccpcd.CcXssPcdInterface.loadConfiguration(CcXssPcdInterface.java:115)
            at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface.loadConfiguration(InternalCcXssPcdInterface.java:124)
            at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface$External.loadConfiguration(InternalCcXssPcdInterface.java:184)
            at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:209)
            at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)
            at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)
            at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)
            at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)
            at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:187)
            at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
            at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
            at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
            at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
            at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
            at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
            at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
            at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
            at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
            at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
            at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
            at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
            at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
            at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
            at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Thanks,
    Damodhar.

    I Think I have to add a parameter sap.xss.BaseConfigurationID (PCD FPM View) to application properties. Is it mandatory to add FPM View which is created in PCD to Application Properties. Is there any other way to avoid this procedure?
    Thanks,
    Damodhar.

  • Please help...I can't solve this web services error (ConfigException)

    Hi
    I've got the following error when I try to build document-oriented web services
    [clientgen] Generating client jar for WLWSSEApp.ear(SimpleService) ...
    [clientgen] weblogic.webservice.server.ConfigException: Could not add parameter
    to operation. You must specify either its Java or XML type.
    [clientgen] at weblogic.webservice.server.WebServiceFactory.addPart(WebServi
    ceFactory.java:1258)
    [clientgen] at weblogic.webservice.server.WebServiceFactory.addParamsToMetho
    d(WebServiceFactory.java:1211)
    [clientgen] at weblogic.webservice.server.WebServiceFactory.registerOperatio
    n(WebServiceFactory.java:798)
    [clientgen] at weblogic.webservice.server.WebServiceFactory.initOperations(W
    ebServiceFactory.java:633)
    [clientgen] at weblogic.webservice.server.WebServiceFactory.createFromMBean(
    WebServiceFactory.java:220)
    [clientgen] at weblogic.webservice.tools.build.internal.WSDLGenImpl.getWebSe
    rviceRuntime(WSDLGenImpl.java:240)
    [clientgen] at weblogic.webservice.tools.build.internal.WSDLGenImpl.run(WSDL
    GenImpl.java:135)
    [clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.doClie
    ntGenFromEAR(ClientGenImpl.java:438)
    [clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.run(Cl
    ientGenImpl.java:345)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.doC
    lientGen(ClientGenTask.java:351)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.exe
    cute(ClientGenTask.java:208)
    [clientgen] at org.apache.tools.ant.Task.perform(Task.java:341)
    [clientgen] at org.apache.tools.ant.Target.execute(Target.java:309)
    [clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    [clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:1255
    [clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:609)
    [clientgen] at org.apache.tools.ant.Main.start(Main.java:196)
    [clientgen] at org.apache.tools.ant.Main.main(Main.java:235)
    BUILD FAILED
    file:C:/bea/user_projects/domains/examples/build_ws/build.xml:54: weblogic.webservice.tools.build.WSBuildException: Could not add parameter to operation. You mu
    st specify either its Java or XML type. - with nested exception:
    [weblogic.webservice.server.ConfigException: Could not add parameter to operatio
    n. You must specify either its Java or XML type.]
    My environment:
    - JBuilder X
    - Weblogic Platform 8.1
    - Windows XP SP2
    Here are my steps of implementing web services:
    1. Write the Java code for the back-end components that make up the Web Service. Here's the method that handle the operation
    public String testName(InputParam test) {
    String inputName = test.getName();
    System.out.println("Input name:"+inputName);
    return "Hello "+inputName;
    Here's InputParam:
    public class InputParam {
    private String name;
    public InputParam() {
    public String getName() {
    return name;
    public void setName(String name) {
    this.name = name;
    2. Since I use JBuilder X I configure everything including handlers chain through web services designers
    3. Build project
    If nothing goes wrong, I will get generated client jars and a war file with web-services.xml inside.
    I have no problem when I implement RPC-style web services.
    I got the above error when I implement Document-oriented web services, but
    I have no problem when I use String as a parameter instead of InputParam class.
    I tried to change some attributes that might be relevant but got no luck.
    I've tried using clientgen command line as well but the result was the same.
    Below are the guidelines for creating document-oriented web services from the BEA's document that I think I already followed
    - The methods that implement each operation of the Web Service can have only one parameter. This single parameter can be of any supported data type. (The Weblogic web services toolkit support simple JavaBean, doesn't it?)
    - The methods that implement each operation cannot use out and in-out parameters. (I'm not sure about this one since I got Holder classes after using clientgen. However, there's no <param> tag in web-services.xml.)
    I found the old solution from support.bea.com (ID = S-25689), but I don't think my situation is the same. I got the error while building web services...not deploying a web service.
    Any answers to this question will be very much appreciated.
    George

    Quote from: danknuggets11 on 22-December-06, 11:23:06
    Reply, Should have mentioned this before, I can't even turn agp on.  I go into SMARTGART it shows AGP off, Fastwrites off.  If I move the AGP settings to 4x, 8x, it says I need to restart to apply. After the restart it just resets it back to off.
    get Driver Cleaner and remove curently ATI Drivers.
    reboot,
    get and install chipset Drivers: http://download.msi.com.tw/support/dvr_exe/mbd_dvr/VIA4in1_MB.zip
    reboot,
    then get and install ATI Drivers: https://forum-en.msi.com/index.php?topic=102839.msg761297#msg761297

  • [solved] writing systemd service file to run script

    i have completely migrated to systemd. now, i am trying to write a service file to run a startup script (~/.startup.sh). one of the functions of the script is to set the brightness of the screen:
    echo "95" > /sys/class/backlight/intel_backlight/brightness
    i created /etc/systemd/system/startup.service:
    [Unit]
    Description=Run startup script
    [Service]
    Type=oneshot
    ExecStart=~/.startup.sh
    [Install]
    WantedBy=multi-user.target
    but i get the following error:
    Failed to issue method call: Unit startup.service failed to load: Invalid argument. See system logs and 'systemctl status startup.service' for details.
    i have two questions:
    1. what am i missing?
    2. how can i avoid permission issues associated with modifying the brightness file (e.g., permission denied errors, the need to put in the password, etc.)?
    thanks.
    Last edited by anti-destin (2012-08-01 22:26:04)

    thanks for the replies.
    just a note: using an absolute path didn't fix the issue.
    but i went ahead and created the file /etc/tmpfiles.d/backlight.conf:
    w /sys/class/backlight/intel_backlight/brightness - - - - 95
    and that worked.
    is there a reason for recommending using a tmpfile rather than a service?
    in any case, i'm marking this as solved.

  • [solved] Writing systemd service file - forking no pidfile

    Hey all,
    I am trying to write .service files for TORQUE, but am having some difficulty and quite can't understand the docs.  Here's what I have so far for the server
    [Unit]
    Description=TORQUE server
    Wants=basic.target
    After=basic.target network.target
    [Service]
    Type=forking
    PIDFile=/run/torque-server.pid
    ExecStart=/usr/sbin/pbs_server
    [Install]
    WantedBy=multi-user.target
    The problem I'm having is with the PIDFile - pbs_server doesn't provide an option (as far as I can see) to specify a pid file... is this something that systemd can generate on its own, or what's the normal solution here?
    Without the PIDFile specified systemctl start returns immediately and no process exists, with the PIDFile systemctl start stalls for a while and then has an error saying it couldn't find the pid file (surprise), but pbs_server is left running.
    Thanks for any help
    Last edited by dandaman0061 (2012-12-13 19:58:36)

    Nevermind - it appears that pbs_server creates a pid file at $TORQUE_HOME/server_priv/server.lock where using torque from the AUR is /var/spool/torque
    Chaging the pidfile setting in the service file to this now works.

  • [SOLVED] Dovecot Systemd Service Fails

    Hello all, I can't find the reason for why my dovecot fails. My journalctl doesn't provide output for the PID I give it.
    $ systemctl status dovecot.service
    * dovecot.service - Dovecot IMAP/POP3 email server
    Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled)
    Active: failed (Result: exit-code) since Mon 2014-08-04 17:53:27 UTC; 1min 4s ago
    Process: 4580 ExecStart=/usr/bin/dovecot -F (code=exited, status=89)
    Main PID: 4580 (code=exited, status=89)
    $ journalctl -b _PID=4580
    -- Logs begin at Fri 2013-03-29 01:07:20 UTC, end at Mon 2014-08-04 02:50:51 UTC. --
    Thank you for the help.
    ========================
    EDIT:
    ran the process described above: dovecot -F which gave me the dovecot error message. I had a misconfigured file (spelling mistake).
    Thanks for the help!
    Last edited by lexan (2014-08-04 18:11:28)

    Padfoot wrote:
    Try the following:
    [Unit]
    Description=K Display Manager
    Conflicts=[email protected]
    After=systemd-user-sessions.service [email protected]
    [Service]
    ExecStart=/usr/bin/kdm -nodaemon
    Restart=always
    IgnoreSIGPIPE=no
    StandardOutput=syslog
    [Install]
    Alias=display-manager.service
    Thank you for your suggestion. Unfortunately it does not work. Out of 4 boots, 3 time I ended up with blank screen. Interestingly, in the last boot I was able to switch to tty1 just after screen went blank and managed to log in to tty. I've restarted the kdm.service then manually in hope the image will be restored, but it wasn't. The restart of kdm then made the screen totally blank and I was unable to switch to tty anymore.
    Is it possible that radeon module in kernel has some slow initialization procedure and if X requires its services before it is properly initialized it ends up with blank screen?

  • [SOLVED] X-Autostart, Auto-log-in and DBus : a non-pulseaudio issue

    Hello,
    besides the not-so-clear title, I've been investigating for what first looked like a pulseaudio problem for a while, and I'm now sharing what I found with you :
    Pre-existing conditions
    An Arch system with systemd, auto-loggin on a TTY and auto-start of X
    Symptoms
    Pulseaudio wouldn't start anymore at boot, but everything worked fine if it was started a while after, provided one would have sudo killall -9 pulseaudio before, and there was no major upgrade that could be related to this change.
    Journalctl showed dbus related messages, saying that pulse wasn't able to find it, and a general failure in main.c start.
    Solution
    Actually, a part of the boot process was the following :
                |-----> lots of things, and at a point dbus
    Init --> |
                |-----> auto-logging service (getty stuff) -----> .xinitrc ------> pulseaudio
    and there was no guarantee that dbus was already started when pulse audio was.
    To add this guarantee, edit your autologging service and add the following
    [Unit]
    ... your stuff ...
    #lines to add :
    Requires=dbus.Service #I'm not sure this one is needed, if anyone here can confirm it
    After=dbus.Service
    ..rest of the file..
    reboot, and enjoy
    Last edited by NougatRillettes (2012-12-30 16:05:02)

    I know this is an older post, but I'm hoping by bumping it someone will be able to help me with this issue even though the thread is marked as [SOLVED], so that I won't have to create a new post.
    I'm trying to set up a host to autologin a user, then automatically startx to enter a desktop environment.  I am using these guides:
    https://wiki.archlinux.org/index.php/au … al_console
    https://wiki.archlinux.org/index.php/Start_X_at_Login
    I haven't yet set up the startx at login, but I've done that before, so I don't expect any issues or problems.
    I successfully set up autologin using the first link and everything seemed fine.  However, on the startx at login wiki, it states:
    Tips
    This method can be combined with automatic login to virtual console. When doing this you have to set correct dependencies for the autologin systemd service to ensure that dbus is started before ~/.xinitrc is read and hence pulseaudio started (see: BBS#155416)
    I don't have pulseaudio issues to worry about, but I do have an exec line to start lxde.  So, I followed that link to this thread and created the lines NougatRillettes suggested.  Here's the complete file:
    /etc/systemd/system/[email protected]/autologin.conf
    [Unit]
    Requires=dbus.Service
    After=dbus.Service
    [Service]
    ExecStart=
    ExecStart=-/usr/bin/agetty --autologin <username> --noclear %I 38400 linux
    Then, when I reboot the kernel spits this out:
    Nov 06 14:39:23 [Host] systemd[1]: Set hostname to <[Host]>.
    Nov 06 14:39:23 [Host] systemd[1]: [/etc/systemd/system/[email protected]/autologin.conf:2] Failed to add dependency on dbus.Service, ignoring: Invalid argument
    Nov 06 14:39:23 [Host] systemd[1]: [/etc/systemd/system/[email protected]/autologin.conf:3] Failed to add dependency on dbus.Service, ignoring: Invalid argument
    Nov 06 14:39:23 [Host] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
    I rechecked the wikis and noticed:
    Tips & Tricks
    Avoiding unnecessary dmesg errors
    To avoid errors related to display-manager.service in dmesg, you should set the default target to multi-user instead of graphical:
    # systemctl enable multi-user.target
    So I went ahead and enabled multi-user.target and rebooted, thinking that would solve the problem, but it didn't...the error messages were the same.
    I'm hoping someone can help...and maybe update those two wikis if there's any information missing.  I'm also wondering if I should reverse the last step I described by disabling multi-user.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'

  • Tip regarding the "systemd[1]: Failed to start Journal Service" error

    Just a tip regarding the well-known
    systemd[1]: Failed to start Journal Service
    error (which I ran into last weekend) to maybe save one or two among you a couple of hours of your time:
    The error is described here https://bbs.archlinux.org/viewtopic.php?id=151012 as well as in several other threads in other language boards / in other forums etc. It is usually (as in the linked thread) 'solved' by reinstalling the system - good old Windows magic, also useful when dealing with systemd.
    The Problem with this error is that you do not get into your system. Instead, systemd will print you the mentioned "Failed to start Journal Service" error message a couple of million times. There are also no logs that you could retrieve (when booting from a livesystem) and that would give you any helpful hints, since journal is systemd's logging service, old-style system logs are not kept, and the dmesg log doesn't survive the reboot with default settings.
    As pointed out in the above mentioned thread, you will see a few more instructive error messages when adding 'emergency' to the kernel line in the bootloader config.
    Now there may be plenty of reasons why the systemd journal service might not work. The most common and most annoying, however, appears to be this one:
    In this case you will see that the problem actually lies in
    systemd[1]: Cannot open /etc/machine-id: No such file or directory
    Now, 'man machine-id' reveals that "the /etc/machine-id file contains the unique machine id of the local system that is set during installation. (...) The machine ID is usually generated from a random source (...)". It is obviously perfectly justified to refuse to boot the system because an absolutely insignificant random number is missing. As far as systemd is concerned anyway.
    Usually, it seems, the /etc/machine-id is set by /usr/bin/systemd-machine-id-setup during installation or system upgrade. It is not documented anywhere that this is a rather important step and that you should better check if this was or was not actually done before rebooting. Obviously (but for no apparent reasons) systemd fails to run this (or to run this successfully) sometimes.
    Also to be recommended: Always retain (back up) your old kernel and initramfs and edit your bootloader config appropriately to be able to boot with your old kernel again ... just to have one or two options left to get back into the system in case of running into an unpleasant surprise from the side of systemd or other packages.
    The solution is, obviously, to create this file /etc/machine-id ... You probably want to do that from a livesystem (if you want to try it from the emergency shell, you would need to remount / (i.e. root) as rw and hope that systemd will not punish you for that) by just running the program that was designed for creating this file manually:  /usr/bin/systemd-machine-id-setup
    http://permalink.gmane.org/gmane.comp.s … devel/7528 states that it might also work with merely creating the file 'touch /etc/machine-id'. Though I didn't try that since I had enough fun with systemd for one week and didn't want to break my system again just to see if that works.

    Jristz wrote:
    ackalker wrote:Sorry for necrobumping this.
    Generating the machine-id in a consistent way is very important when working with KVM and containers, where the machine-id can be set for the VM or container. See `man systemd-machine-id-setup`.
    Again, _don't_ just put some random UUID in there, especially not in the systemd package install script, this makes provisioning Arch Linux containers a PITA.
    If you thing that the way that arch is handlynbg the machine-id is wrong or can be improved, then file a bug.
    He already did.
    Jristz wrote:Anyway, I thing if reinstalling systemd package or if systemd have a command to reinitialize the machine-id file.
    Like so many of your posts, I had to read this a half dozen times before it made any sense. I think you're hinting at the utility that ackalker already pointed out in the post you're replying to. And, if you read the install scriptlet, you wouldn't need to think about whether or not reinstalling would be an option. You would know that it isn't.

  • Getting error while connecting Utility Customer E-Services

    I am getting the following error while connecting to Utility Customer E-Services through the browser.
    Error:       Your user master has not been created correctly. Contact your system administrator.
    Please advise some fix for this problem.
    Thanks in advance.
    Regards,
    Nitin

    Hi Mattia,
    yes, I had resolved this problem. It requires some configuration in ume database of the WebAS, where UCES application is hosted.
    1) Create a user in ume.
    2) Assign group "Everyone" and "Authenticated Users" to the user
    3) Within Customized Information tab, create the mapping between your web user, reference user and business partner.
    fscm_refuser: Use reference user id. ( user id to login to ISU system )
    objtype_0: BUS1006
    objkey_0: User business partner details ( business partner number in ISU)
    If there is no customized Information tab, then open visual administrator and do the following.
    1) Navigate to Services->Configuration Adapter
    2) Click on Runtime tab -> Display configuration
    3) Navigate to cluster_data -> server -> cfg -> services -> Propertysheet com.sap.security.core.ume.service
    4) Add the following in ume.admin.addattrs.
    com.sap.security.core.user.refuser:fscm_refuser;com.sap.security.core.user.references:objtype_0;com.sap.security.core.user.references:objkey_0;com.sap.security.core.user.references:objtype_1;com.sap.security.core.user.references:objkey_1;com.sap.security.core.user.references:objtype_2;com.sap.security.core.user.references:objkey_2;com.sap.security.core.user.references:objtype_3;com.sap.security.core.user.references:objkey_3;com.sap.security.core.user.references:objtype_4;com.sap.security.core.user.references:objkey_4;com.sap.security.core.user.references:objtype_5;com.sap.security.core.user.references:objkey_5;com.sap.security.core.user.references:objtype_6;com.sap.security.core.user.references:objkey_6;com.sap.security.core.user.references:objtype_7;com.sap.security.core.user.references:objkey_7;com.sap.security.core.user.references:objtype_8;com.sap.security.core.user.references:objkey_8;com.sap.security.core.user.references:objtype_9;com.sap.security.core.user.references:objkey_9;com.sap.security.core.useces:objtype_10;com.sap.security.core.user.references:objkey_10;com.sap.security.core.user.references:objtype_11;com.sap.security.core.user.references:objkey_11;com.sap.security.core.user.references:objtype_12;com.sap.security.core.user.references:objkey_12;com.sap.security.core.user.references:objtype_13;com.sap.security.core.user.references:objkey_13;com.sap.security.core.user.references:objtype_14;com.sap.security.core.user.references:objkey_14;com.sap.security.core.user.references:objtype_15;com.sap.security.core.user.references:objkey_15;com.sap.security.core.user.references:objtype_16;com.sap.security.core.user.references:objkey_16;com.sap.security.core.user.references:objtype_17;com.sap.security.core.user.references:objkey_17;com.sap.security.core.user.references:objtype_18;com.sap.security.core.user.references:objkey_18;com.sap.security.core.user.references:objtype_19;com.sap.security.core.user.references:objkey_19;
    5) Save the changes, exit visual administrator and restart the server.
    Now. your application will work perfectly fine.

  • Customer self service form gives the error of  "Page cannot be displayed"

    Hi All,
    Customer self service form from Navigation: Recievables -> Customers --> Standard gives the error of "Page cannot be displayed" but the same form gets opened when i navigate that from Order Management responsibility
    Thanks&Regards,
    APPS DBA

    Hi All,
    I have been trying to install the EBS 11i in configured system core 2 duo with 1 gb ram and 250 gb HDD,
    have been following the below steps to install the EBS 11i,
    1.installed Win20003 server edition
    2.VC++ and copyind the link file into windows\system32,
    3.GNU make done the path set everything,
    4.MKS tool kit,
    5IP config and installing MS loopback,
    started the installtion direct from the DVDs,
    Pre-Installtion everything was OK,
    but after done everything I got struck last min, where the popup window appeared as login page responding but i did wait for 30 min and nothing has happened.
    So closed and I restarted the System and I have restarted process putting 1st DVD and given the command rapidwiz -restart.from command prompt.
    and Again its started as a new installtion, and preinstatltion wizard has came.
    where I haeve commited the mistake i did not understand...?
    Please guide me
    regards
    Satya

  • [solved] systemd services not starting at boot (or at all)

    On my router, some systemd services fail to start at boot.
    The services are :
    adsl (pppoe connetction on the wan interface)
    shorewall (funny again for a router)
    logind (brings up only tty1, and not the others with a 'timeout' error)
    adsl starts fine manually after booting up
    the others don't work, I have to launch shorewall with the old sysvinit rc script (and it works)
    I really don't know, what happened to logind...
    Last edited by scar (2012-11-30 10:20:44)

    cups: avahi client failed
    adsl: timeout (ppp0 running on eth0, the service did not found eth0)
    shorewall: did not work by the systemctl command, only with the old rc script
    I'm not sure if there was an error with logind, but I've had only tty1, not all the others (I have not touched /etc/inittab)
    since this was a very old install (but up to date), I've decided to reinstall the whole thing,
    Everything works
    (But reinstalling does not solve any problem, it erases the problems...)
    Last edited by scar (2012-11-30 10:21:20)

Maybe you are looking for

  • Sound over HDMI works halfway.[SOLVED]

    //After looking around, HDMI only sends the signals to turn down the HDMI connected device. I guess it's as good as it gets...// Using nVidia GT218 [ION] on Zotac Hd-id11. NVIDIA Driver Version: 260.19.44 2.6.37-ARCH //pianobar uses libao. My config,

  • Attaching Word and PDF files in Mail without preview in the middle of a message

    I am using Mail but often attaching Word docs and PDFs. Word attachments appear as small icons, but PDFs as preview and usually in the middle of the message. Can I attach PDFs as small icons and not in the middle  of a message? Having just moved to M

  • LDAP Error Code in authentication?

    Hi, I'm working with Weblogic app server 7.0. I have configured LDAP authentication provider with iplanet. And I'm using FORM authentication. How can I know which code error is returned if authentication fails? I want to discriminate between wrong pa

  • My download won't go through

    im trying to downlaod the trail of Dreamweaver, and when it gets to the big screen where it asks for the serial # and other stuff, it says that it can't go through because the Adobe installer is open. so i thought that it was the akami downloader tha

  • Unable to Release my Webdynpro DC in NWDS DC Perspective

    Hi All,         I Configured the NWDI Successfully, i created one webdynpro DC application and after that deployment was done successfull, after that i went to DC perspective,i did checkin the activity, it was activated successfully then i went to ac