[SOLVED] XFCE shutdown and reboot buttons only dump out to prompt

Recently, after an update, the XFCE shutdown and reboot buttons began not working as expected.  Both are present, and I can click them.   They seem to try to do what they should, XFCE does terminate, but I am dumped out to a shell prompt rather than the shutdown or reboot happening.   What might be a possible cause of this behaviour that I can check and correct?
Thanks,
Bill
Last edited by wallenpb (2012-11-20 21:00:19)

Are you running systemd or still a sysv/initscript setup?
If it is the latter take into account that consolekit has been dropped. Therefore, as far as I understand it, you are not 'authenticated' and thus not allowed to either shutdown or reboot.
Consider switching to systemd and a good start would be to comply with the 1st step of the systemd installation featured in the wiki to regain control of shutdown/reboot. Afterwards start investigating for the rest as initscripts support has ended.

Similar Messages

  • XFCE - Shutdown and Reboot buttons greyed-out (SOLVED)

    This issue cropped up for me a couple of weeks ago.  Just sat down to try and find a solution.  Followed several suggestions from several posts to no avail.
    Finally discovered that the syntax for achieving this in "/etc/sudoers" has evidently changed.
    This is what I got from the XFCE site: http://forum.xfce.org/viewtopic.php?pid=21331 and is very similar to what's in the Arch Wiki, https://wiki.archlinux.org/index.php/Al … o_Shutdown. So I had been using the following line in /etc/sudoers and it had been working:
    %users mylaptopname=NOPASSWD: /usr/lib/xfce4/xfsm-shutdown-helper
    At some point in an XFCE upgrade the path to "xfsm-shutdown-helper" changed to "/usr/lib/xfce4/session/xfsm-shutdown-helper"
    I changed the path to "xfsm-shutdown-helper" but that didn't solve the problem.
    Finally I tried this in /etc/sudoers:
    %users  ALL=(ALL)       NOPASSWD: /sbin/shutdown -h now,/sbin/reboot
    And all the usual options in the shutdown menu re-appeared.
    Hope this helps someone.
    (Edited to show the link to the the XFCE forums and the Wiki.)
    Last edited by whatshisname (2011-11-25 16:09:31)

    Replying to my own post because of what I've discovered since I first posted this.
    Most importantly, the fix which I thought had fixed this problem didn't really work.  I was snookered into thinking it had.  But I've found another solution which appears to be working now, thus this post.
    Here's what I've found.
    I had no login/display manager on my laptop.  I was auto-logging into my desktop with this setting in /etc/inittab:
    x:5:once:/bin/su myusername -l -c '/usr/bin/startx >/dev/null 2>&1'
    The snooker alluded to above was this:  If I booted to a command line and issued "startx" to start XFCE, I would have the shutdown and reboot buttons available on the logout dialog.
    But if I booted directly into the desktop, I didn't.  It's taken me a while to figure out that this is what was going on.
    Even though my old setup had worked for the almost 2 years I've been using Arch and XFCE, some upgrade somewhere in  recent months prevented it from working any longer.
    My final fix was to install a login manager, in my case, lxdm.  And set it to auto log me into my desktop.
    I now have the expected reboot and logout menus.
    Hope this helps someone.  This has been a bear to figure out.

  • [SOLVED]Disable Shutdown and Reboot from XFCE

    Hi all
    I would like to disable the shutdown and reboot buttons from XFCE (4.10) or to do disable shutdown/reboot systemwide.
    I searched for specific xfce instructions and all i could find was using xfconf-query[1] and afaik it can only disable hibernate and suspend buttons
    [1]http://forum.xfce.org/viewtopic.php?id=4781
    Last edited by boriscougar (2012-09-11 21:51:22)

    @nadman10
    it had no change to remove my users from the power group
    @2ManyDogs
    Creating that file (/etc/xdg/xfce4/kiosk/kioskrc) and setting which users could shutdown solved the problem
    Thanks for your time

  • Xfce shutdown and reboot disabled with startxfce4

    Hello.
    I try to fix twinview with my nvidia xorg.conf .And run over this kind of issue.
    From the beginning with xfce i only have a logout button no shutdown and reboot.(i can live with that)
    I start with startxfce4.
    In my xinitrc from wiki    exec ck-launch-session startxfce4  and i have dbus in /etc/rc.conf
    But when i start with startx instead all the buttons are there. I can live with that to .
    An explaination why startx working and startxfce4 not ?? Can it be a bug somewhere?
    Last edited by freddie (2011-02-20 10:01:23)

    lockheed  you could always shutdown like this from wiki, thats what i do.
    https://wiki.archlinux.org/index.php/Al … o_Shutdown
    I have all suggestions from from this thread. And i not use any display manager.
    That was more of a surprice that i got shutdown, restart, hibernate, sleep with startx instead of startxfce4. I dont know if more xfce users can do this.
    And for me i dont need to have shutdown, restart, hibernate, sleep in the panel.More curious why startx works and startxfce4 not like i say in my first post.
    Last edited by freddie (2011-02-20 12:36:17)

  • Systemd - kdm - xfce session: shutdown and reboot disappears randomly

    I use systemd and kdm as login manager; my desktop is XFCE.
    Immediately after login, if I click the logout button applet in the xfce panel, I can access all the options (shutdown, reboot, etc).
    But sometimes, after a while during the session, the shutdown and reboot option simply disappear - only logout works. If I log out to KDM and then again log in, they reappear.
    Does anyone have a clue about this?

    Just FYI the wikis were updated:
    Note: slim is ConsoleKit capable since version 1.3.3. Unless you happen to run an old version, you must no longer include ck-launch-session in your .xinitrc or slim.conf login_cmd.
    https://wiki.archlinux.org/index.php/Sl … vironments
    SLiM is also ConsoleKit capable since version 1.3.3. Unless you happen to run an old version, you must not use --with-ck-launch from your .xinitrc or slim.conf login_cmd.
    https://wiki.archlinux.org/index.php/Xfce#Manually

  • [SOLVED] Run script on systemd shutdown and reboot

    Hello!
    I am trying to log uptime on shutdown and reboot with no success.
    I create the file /usr/lib/systemd/system/uptime.service:
    [Unit]
    Description=/etc/rc.local.shutdown Compatibility
    ConditionFileIsExecutable=/etc/rc.local.shutdown
    DefaultDependencies=no
    After=rc-local.service basic.target
    Before=shutdown.target
    [Service]
    Type=oneshot
    ExecStart=/etc/rc.local.shutdown
    StandardInput=tty
    RemainAfterExit=yes
    [Install]
    WantedBy=shutdown.target
    /etc/rc.local.shutdown:
    [jribeiro@arkosta ~]$ ls -l /etc/rc.local.shutdown
    -rwxr-xr-x 1 root root 107 Out 24 12:42 /etc/rc.local.shutdown
    [jribeiro@arkosta ~]$ cat /etc/rc.local.shutdown
    echo "$(date) - $(/usr/bin/uptime | sed 's/.*up \([^,]*\), .*/\1/')" >> /home/jribeiro/registo_de_uptime
    Any ideas?
    Last edited by joseribeiro (2014-10-25 19:57:59)

    I altered the uptime unit file:
    [jribeiro@arkosta ~]$ cat /usr/lib/systemd/system/uptime.service
    [Unit]
    Description=/etc/rc.local.shutdown Compatibility
    Before=shutdown.target
    [Service]
    ExecStart=/bin/true
    ExecStop=/etc/rc.local.shutdown
    RemainAfterExit=yes
    [Install]
    WantedBy=shutdown.target
    Then I started the uptime service manually:
    [jribeiro@arkosta ~]$ sudo systemctl start uptime
    I checked the 'registo_de_uptime' file:
    [jribeiro@arkosta ~]$ cat /home/jribeiro/registo_de_uptime
    Sáb Out 25 19:43:31 WEST 2014 - 2 min
    After that I rebooted my system.
    I checked the 'registo_de_uptime' file, again:
    [jribeiro@arkosta ~]$ cat /home/jribeiro/registo_de_uptime
    Sáb Out 25 19:43:31 WEST 2014 - 2 min
    Sáb Out 25 19:44:27 WEST 2014 - 3 min
    Everything seems to be alright. I wanted to make the ultimate test.
    With that in mind I rebooted the system.
    I checked the 'registo_de_uptime' file, once more:
    [jribeiro@arkosta ~]$ cat /home/jribeiro/registo_de_uptime
    Sáb Out 25 19:43:31 WEST 2014 - 2 min
    Sáb Out 25 19:44:27 WEST 2014 - 3 min
    No success...
    It works when I start the service manually and in the right next reboot, after that it won't work.
    Here is the journal's ouput:
    [jribeiro@arkosta ~]$ sudo journalctl -b -0 -u uptime
    -- Logs begin at Sex 2014-10-24 22:02:03 WEST, end at Sáb 2014-10-25 20:05:29 WEST. --
    By the way:
    [jribeiro@arkosta ~]$ sudo systemctl status uptime
    ● uptime.service - /etc/rc.local.shutdown Compatibility
    Loaded: loaded (/usr/lib/systemd/system/uptime.service; enabled)
    Active: inactive (dead)
    Last edited by joseribeiro (2014-10-25 19:07:32)

  • Nano 7 auto shutdown and reboots after playing videos?

    Hello,my nano 7 is very new, and i just tried to sync videos into it today. when i tried to play them, it would automatically shutdown and reboot.Anyone know how to solve this or have similar problems?

    Okydoky a new fascinating bug has been found!
    I now relabeld all songs with no album with a "no album" tag. I thought I could handle that way the problem with the "no album bug", well I thought. Now all the songs are shown in the display but I can't play all songs through because the player hangs up. When I select just one album to play through it works fine.
    *thumbs up* great mp3 player Apple! *thumbs up*
    Windows XP Pro

  • Shutdown and reboot logging

    Is there any file that keeps shutdowns and reboots track? or
    i should use wtmpx?

    Unia wrote:
    Which one did you install? You have to run it before you can see the icon:
    $ gnome-power-manager
    or
    $ xfce4-power-manager
    Add it to whatever startup script you use to have it launch at boot.
    Note: a power manager won't give you a shutdown dialog AFAIK. At least gnome-power-manager doesn't.
    ...Y'know, I really should've actually tried adding it to my xinitrc! I stupidly assumed that because running it via gmrun or a shell didn't bring up an icon, that adding it to my xinitrc wouldn't make any difference! Thanks a lot Unia
    EDIT: Okay... so I jumped the gun a bit, I tried adding gnome-power-manager and xfce4-power-manager to my xinitrc and both did nothing
    Last edited by Starfall (2011-05-26 18:18:04)

  • HT5390 have a Mac mini server in the data center no physical access. Is it possible to configure a remote "console" that allows shutdown  and reboot remotely ?

    A mini mac used for building sits in the data center normally we access via VNC network connection.
    I want to have "console" access to shutdown and reboot system.
    Reason. Updated to Mountain Lion OS X from 10.7.x and lost VNC connections, now host is down with no physical access.
    Alternate is to call data center and see if someone can cycls the power ?

    As mentioned by Linc there is no 'lights out' management for the Mac mini (or any current Mac). If the Mac is still running you can initiate a reboot via the GUI or commandline. If however it is completely crashed then there is a solution you could consider which is to get a managed power distribution strip. With this the power strip has its own network connection and lets you remotely turn off (and on) individual power sockets. This would then let you 'hard reboot' the Mac mini even if crashed.
    See http://www.apc.com/products/resource/include/techspec_index.cfm?base_sku=ap7921& tab=features

  • The back, forward, reload and stop buttons are greyed out, the address bar stays blank when I go to a website and firefox loads to a blank page, not my home page. There are 3 users on this computer and it only happens on one user.

    Firefox loads to a blank page, not my home page. When I click on the home button it takes me to the home page. The back, forward, refresh and stop buttons are greyed out and not usable. The webpage I am on does not show up in the address bar. If I type something into the address bar, that address stays there no matter what page I go to next.

    Just upgraded to v4. It did NOT fix the problem.

  • Upon starting up my mini mac for the first time I see the welcome screen but the 'go back' and'continue' buttons are greyed out so I cant continue.

    As the title states everytime I boot up my mini mac the 'go back' and 'continue' buttons are greyed out and I cannot continue with the installation. I even went out and bought an external cd drive to try and load the operating system and that did not work either.

    Hi, what OS version is it? And which year Mini?

  • Issue With Shutdown and Reboot

    So I just got home from work and went to watch something on the frontend in the lounge room but the frontend reported it wasn't there. I then noticed that some other shows I know have recorded are shown as not being there either.
    A check shows all shows not there. The another frontend out the back was playing some shows through XBMC so it is talking okay and the one in the lounge room is connecting to the backend okay as it wasn't complaining or looking to be setup.
    I rebooted the lounge room machine and now it doesn't even show any recordings in the list. I have tried to shutdown the backend via the button (which is setup for safe shutdown but it won't) and it also refuses to reboot or shutdown from the terminal.
    I can't access the shared folder for the recorded tv from another machine as it doesn't want to connect but can connect to other shared folders. I can still access tv shows and films in xbmc.
    I have no idea where to start and certainly didn't want to kill the power to the backend in case that might screw it up.
    Hoping someone might be able to help.

    Zancarius wrote:
    If you can access your backend machine via terminal or SSH, have you checked your logs? (Usually /var/log/everything.log or /var/log/messages should have just about all the cruft that might show up.)
    What happens when you issue a reboot or shutdown? Does it just hang at the prompt or does it generate an error? Can you connect to it via SSH? If it's truly hung, there's not much else you can do but kill power, but I suspect that's not the case if you can log in and issue a reboot or shutdown.
    I can get in using putty and I get this from the errors log:
    tail /var/log/errors.log
    Aug 14 16:27:23 localhost smbd[1553]: [2012/08/14 16:27:23.987120, 0] printing/ print_cups.c:487(cups_async_callback)
    Aug 14 16:27:23 localhost smbd[1553]: failed to retrieve printer list: NT_STAT US_UNSUCCESSFUL
    Aug 14 16:40:24 localhost smbd[1163]: [2012/08/14 16:40:24.439254, 0] printing/ print_cups.c:110(cups_connect)
    Aug 14 16:40:24 localhost smbd[1163]: Unable to connect to CUPS server localho st:631 - No such file or directory
    Aug 14 16:40:24 localhost smbd[1553]: [2012/08/14 16:40:24.439438, 0] printing/ print_cups.c:487(cups_async_callback)
    Aug 14 16:40:24 localhost smbd[1553]: failed to retrieve printer list: NT_STAT US_UNSUCCESSFUL
    Aug 14 16:53:24 localhost smbd[1168]: [2012/08/14 16:53:24.742746, 0] printing/ print_cups.c:110(cups_connect)
    Aug 14 16:53:24 localhost smbd[1168]: Unable to connect to CUPS server localho st:631 - No such file or directory
    Aug 14 16:53:24 localhost smbd[1553]: [2012/08/14 16:53:24.742929, 0] printing/ print_cups.c:487(cups_async_callback)
    Aug 14 16:53:24 localhost smbd[1553]: failed to retrieve printer list: NT_STAT US_UNSUCCESSFUL
    Nothing happens when I issue shutdown -h now or even reboot. I can still access things so it doesn't hang at all.

  • [SOLVED]no pos1 and end button functionalities in ZSH-shell

    Hi guys,
    I am wondering how I can configure zsh so that it can support position1 and end button functionalities. What I want is, for example:
    when I type something, or navigate through my folder structures and recognize that there is a typo at the beginning or in the middle, I want to be able to jump to the first character or to the last character once I, for instance, corrected the typo etc...?
    Is this possible?
    Last edited by Archie_Enthusiasm (2010-12-12 14:59:32)

    I have the following in my .zshrc
    # bindkey
    bindkey -e
    bindkey "\e[3~" delete-char
    # Home- und End-Keys.
    bindkey '\e[1~' beginning-of-line
    bindkey '\e[4~' end-of-line
    what are `\e[1~` and `le[4~`? My .zshrc configuration was working pretty fine on my previous linux systems (ubuntu, opensuse, fedora etc..)
    Why should they be coded differently? Can someone please explain this specific syntax?
    Very interestingly - my laptop keyboard has an extra numlock => There is a fn button (for changing the function of a button) => therefore I have
    - Pos 1 on 7 within the numlock
    - End on 1 within the numlock
    But when I turn off the numlock, I can jump to the beginning and end of the line by using 1 and 7 consequently. But I have two more extra buttons only for this pos1 and end purposes. I want to activate those buttons. And I do not know which code they have
    Thanks
    Last edited by Archie_Enthusiasm (2010-12-12 14:44:46)

  • Shutdown and Reboot without going root

    Is there a way I can use the reboot or poweroff commands without using sudo or root?  Or is this a bad idea?
    Last edited by Falcata (2008-09-04 00:19:30)

    mcmillan wrote:
    My question:  What is the difference between 'chmod +s halt' and NOPASSWD for shutdown as you suggested?  I am not familiar with NOPASSWD.
    NOPASSWD is specified when you configure sudo, so some commands will be executed without asking for your users password. This is probably why it wasn't working for your menu, the computer was waiting for a password but there wasn't a way to display that request or enter it in.
    That makes sense, and is in line with what I figured was going on.  With NOPASSWD which commands would be executed w/out asking for a password?  How would this be more "secure" than using chmod +s on halt and reboot?  It seems that both ways accomplish the same thing in the end, I am just trying to understand why one is better than the other.
    moljac024 wrote:
    mcmillan wrote:
    My question:  What is the difference between 'chmod +s halt' and NOPASSWD for shutdown as you suggested?  I am not familiar with NOPASSWD.
    NOPASSWD is specified when you configure sudo, so some commands will be executed without asking for your users password. This is probably why it wasn't working for your menu, the computer was waiting for a password but there wasn't a way to display that request or enter it in.
    Exaclty. So you could specify the NOPASSWD parameter for the shutdown command and sudo will just do it without asking for the password. You should have an example of how to use that in your sudoers file. If not, then
    man sudo
    Please excuse my ignorance, but how is this better than chmod +s, which allows my user to use it w/out sudo?  It seems as though one lets ME use sudo w/out a password, the other lets ME use the command w/out sudo.  What is the benefit to using sudo without a password, other than not having to physically type the password?
    Last edited by monstermudder78 (2008-09-04 23:13:40)

  • HP pavilion DV6 1030us shutdown and reboot spontaneously

    I bought a HP pavilion DV6 1030us in June 2009, and the Bios was updated to the latest version F24A.
    However, during the notebook running, it will sunddenly shutdown and restart again.
    Such unexpected shutdown just looks like loss of power suddenly, and happens randomly, at least I can not find a rule.
    For most cases, such shutdown comes  without blue screen, and it is operating system- independant.  I tried to install windows 7 64bit, windows 7 32bit, vista 64 bit, xp 32bit, all OS has such problem.
    I dont know whether other users with this model has such problem. I tired everything I can do, still can not solve the problem.
    I suspect the Bios has some problem. I hope HP will release a new one quite soon.
    btw, if I update the BIOS, will it erase the old BIOS completely first, then write into the new one?
    Thanks for all your attention!
    This question was solved.
    View Solution.

    Same issue here

Maybe you are looking for