You are not logged in.
When I try to make shutdown in KDE it goes to login string like tty1
I found that I don't have shutdown command in my system.
How can I install it - shutdown, reboot, poweroff?
Offline
When I try to make shutdown in KDE it goes to login string like tty1
How are you trying to shutdown - using some KDE menu or the commandline?
https://wiki.archlinux.org/index.php/Sy … r_stays_on
I found that I don't have shutdown command in my system.
How can I install it - shutdown, reboot, poweroff?
https://wiki.archlinux.org/index.php/FA … is_X_in.3F
Last edited by karol (2013-06-04 18:06:56)
Offline
When I try to make shutdown in KDE it goes to login string like tty1
I found that I don't have shutdown command in my system.
How can I install it - shutdown, reboot, poweroff?
Hi, yep, the exact problem I had yesterday after the filesystem changes, except i saved these files (halt and the symlinks poweroff,reboot, etc) from old /sbin and copied them to the new /usr/bin ...
but as karol suggested (thank you by the way, i didn't know this either),
pkgfile halt
core/systemd-sysvcompat
core/sysvinitpkgfile reboot
core/systemd-sysvcompat
core/sysvinitif you are missing these commands, maybe try to reinstall these packages?
Last edited by LyCC (2013-06-04 18:14:16)
Offline
pkgfile halt core/systemd-sysvcompat core/sysvinitpkgfile reboot core/systemd-sysvcompat core/sysvinitif you are missing these commands, maybe try to reinstall these packages?
Please update your pkgfile db, sysvinit is not in the repos anymore.
Offline
Thanks a lot!
Offline
Please remember to mark the thread as solved https://bbs.archlinux.org/viewtopic.php?id=130309
Offline
So the solution to get reboot and poweroff in the KDE menu back is what exactly? Because reinstalling systemd-sysvcompat did not work for me.
The files are all there, so I don't see what KDE's problem is:
$ ll /usr/bin/|grep systemctl
lrwxrwxrwx 1 root root 9 30. Mai 14:55 halt -> systemctl
lrwxrwxrwx 1 root root 9 30. Mai 14:55 poweroff -> systemctl
lrwxrwxrwx 1 root root 9 30. Mai 14:55 reboot -> systemctl
lrwxrwxrwx 1 root root 9 30. Mai 14:55 runlevel -> systemctl
lrwxrwxrwx 1 root root 9 30. Mai 14:55 shutdown -> systemctl
-rwxr-xr-x 1 root root 301240 30. Mai 14:55 systemctl
lrwxrwxrwx 1 root root 9 30. Mai 14:55 telinit -> systemctlOffline
That's why I asked OP what exactly the problem was: KDE menu or commands enteredd in the terminal.
I have no idea how to fix KDE. Maybe you should open a new thread, but search the forums first.
Offline
Maybe my mistake was doing yesterday's updates from the KDE terminal. I should really have dropped to the console for that. Now KDE is probably angry with me for changing the filesystem layout beneath its big, bloated behind. KDE did produce quite a few error messages when I logged out after the update, so maybe that has something to do with this bug.
Oh well, as long as I can still log out and suspend from the KDE menu, I guess it's not an important issue.
Offline
Hi
i have the same problem
i can't shutdown my arch from kde
but i have this error:
kdm[30948]: Failed to execute shutdown command "/sbin/shutdown -r now"what i can do to solve this problem?
edit i turn to full systemd and update grub-legacy to grub2 and everything is ok
Last edited by ElNinijo (2013-06-08 08:34:13)
Offline
Maybe my mistake was doing yesterday's updates from the KDE terminal.
Unlikely
Now KDE is probably angry with me for changing the filesystem layout beneath its big, bloated behind.
Nice anthropomorphism.
KDE did produce quite a few error messages when I logged out after the update,
Specifically?
Also, most importantly, how are you starting KDE?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
@ElNinijo
Have you tried the systemctl way? Do you have systemd-sysvcompat installed?
Offline
Also, most importantly, how are you starting KDE?
With "startx".
Yesterday's update also caused KDE to display a blank background instead of the usual contents of ~/Desktop. It took some fiddling with KDE's settings to get all my desktop icons back. So I think yes, it's quite possible that yesterday's KDE error messages on logout and the subsequent problems might be related somehow.
Offline
Okay, lets take a look at your ~/.xinitrc file and ensure that it does not have any consolekit floobydust left in it.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
$ cat .xinitrc
[[ -f ~/.Xresources ]] && xrdb -merge ~/.Xresources
rm -fr ~/.adobe
redshift -l 53:10 -t 6500:4000 &
xset -dpms; xset s off
conky &
#setxkbmap -layout de; exec wmaker
exec startkde
#exec gnome-sessionOffline
I don't think you are starting dbus.
From my system (Note that this is not my ~.xinitrc, but rather the skeleton in /etc.
ewaller$@$odin /etc/skel [2]1016 %ls /etc/X11/xinit/xinitrc.d
30-dbus 40-libcanberra-gtk-module pulseaudio xdg-user-dirs
ewaller$@$odin /etc/skel 1017 %cat .xinitrc
#!/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
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
ewaller$@$odin /etc/skel 1018 %The loop at the top starts the things in /etc/X11/xinit/xinitrc.d, including dbus.
You might try exec dbus-launch startkde instead of your last command (assuming you have a good reason for not wanting to start the stuff in /etc/X11/xinit/xinitrc.d)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Systemd seems to start dbus:
$ ps aux|grep dbus
dbus 138 0.0 0.0 18172 2312 ? Ss Jun04 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
martin 366 0.0 0.0 15916 620 tty1 S Jun04 0:00 dbus-launch --sh-syntax --exit-with-session
martin 367 0.3 0.0 19176 2224 ? Ss Jun04 0:46 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
$ pstree
systemd-+-akonadi_control-+-3*[akonadi_agent_l---{akonadi_agent_l}]
| |-akonadi_archive
| |-akonadi_maildis
| |-akonadi_mailfil
| |-akonadi_nepomuk
| |-2*[akonadi_pop3_re]
| |-akonadiserver-+-mysqld---38*[{mysqld}]
| | `-21*[{akonadiserver}]
| `-{akonadi_control}
|-at-spi-bus-laun---2*[{at-spi-bus-laun}]
|-colord---{colord}
|-crond
|-cupsd
|-2*[dbus-daemon]
|-dbus-launch
...
I can also see dbus quitting when I exit KDE. But I'll try your suggestion just in case.
Offline
Its a known bug with Kde. You have to start it through KDM or patch it to have shutdown and reboot in the menu.
Offline