Small complaint about KDE 4.6.1

[viking60]

Coming from Gnome I am used to click a button and power off or reboot the computer. That is no problem it is right there under system.
In KDE 4.6.1 I ad the red power button to the panel and when finished I hit it.... and what happens?
I get the generous offer to log out
Yes but I can poweroff right there in KDM login manager you say? I could, but I don't use it I use Slim! And yes I know how to reboot in the slim login manager I just enter "reboot" in the userid field. But then I could have done it in the terminal from within KDE to begin with.
My point is that I cannot power off the box from within KDE!
I cannot understand how KDE can claim to be user friendly without it. What about a fresh user coming from Windows (or someone who cannot use CLI)? He will manage just fine until it is time to shut of his computer - and the only thing he is offered is to log out? And finally then he is allowed to shut down his computer.
And if someone installed slim for him, he is fubared.
I just don't get it - what were the KDE guys thinking about?
It works in Mandriva from within KDE in 4.5.5. Am I missing something here?

[dedanna1029]

Code: Select all

systemsettings

"Startup and Shutdown" (towards the bottom middle), then "Session Management" on the left.



...Then click "Apply"

Edit: You *may* need to logout and back in, or reboot for it to take effect.

[viking60]

That has no effect here. (probably because I use slim).

[dedanna1029]

For some reason I'm thinking it still should give you the Logout/Reboot/Shutdown options when you log out of KDE, if you have it set to in systemsettings. Doesn't seem it works though. Hunh. Interesting. It works for me here... but I'll retry to confirm (I use slim too).

[dedanna1029]

For the meantime, see if there is anything here to help. Compare your /etc/slim.conf:

Code: Select all

# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path        /bin:/usr/bin:/usr/local/bin:/usr/sbin
default_xserver     /usr/bin/X
xserver_arguments   -nolisten tcp vt07

# Commands for halt, login, etc.
halt_cmd            /sbin/shutdown -h now
reboot_cmd          /sbin/shutdown -r now
console_cmd         /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd        /usr/sbin/suspend

# Full path to the xauth binary
xauth_path         /usr/bin/xauth

# Xauth file for server
authfile           /var/run/slim.auth

# Activate numlock when slim starts. Valid values: on|off
numlock on

# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
hidecursor          false

# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
#
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd           exec /bin/sh - ~/.xinitrc %session
login_cmd           exec /bin/bash -login ~/.xinitrc %session

# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
#
# sessionstart_cmd   some command
# sessionstop_cmd   some command

# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon   yes

# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions            gnome,kde,xfce4,icewm,wmaker,blackbox

# Executed when pressing F11 (requires imagemagick)
screenshot_cmd      import -window root /slim.png

# welcome message. Available variables: %host, %domain
welcome_msg         Arch Linux or Die!

# Session message. Prepended to the session name when pressing F1
session_msg         Session: Which WM would you like?

# shutdown / reboot messages
shutdown_msg       The system is shutting down...
reboot_msg         The system is rebooting...

# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user        dedanna

# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
focus_password      no

# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login          no


# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme       mindlock

# Lock file
lockfile            /var/lock/slim.lock

# Log file
logfile             /var/log/slim.log

[viking60]

Hm our slim settings are mostly the same so I tend to agree that this is something else. If you have it working then it must be something local here that I have fubared.

[dedanna1029]

Okay, here's the rub, something I'm trying to fix. KDE4.6.1 is now crashing on me as soon as it's fully loaded after login.

HOWEVER... I was able to catch it during load to check to be sure I had the options before it froze.

And, yes, I do have all of the options available to me to get out with. Logout is default, I hit the down arrow, and reboot and shutdown options are both there. That's about when KDE freezes on me is when I get to that point, with that menu dropped down and all, so I can see those options right when it freezes.

I'm trying to fix this at the same time I'm trying to fix the polipo issue with Firefox, so it's taking a bit, after I get my grandson.

Edit: Point of interest. When it freezes, I do still have my mouse and can move it around, but when I try to click on anything at all with it, nothing at all happens. The desktop itself is frozen as Europe's last winter. The only option I can do is to Ctrl+Alt+F2, and reboot from su tty.

As for your issue, I'm beginning to wonder if KDE4 just plain does not want (because of the issue I'm having too) to play nice with Slim, and now requires, as you say, only to work if one is using KDM (and yes, I think that pretty effed up, as you do).

Either way, I hesitate to say much more, as I want to wait until I've done updates, and retry with both KDM and then Slim after, and I can't do updates until I'm done for the night tonight. :\

Edit again: There is only one more single thing that I can think would make KDE do as it is on mine, and that may be that it doesn't want to play nice with Vidalia in startup applications.

[dedanna1029]

https://bugzilla.novell.com/show_bug.cgi?id=681114

https://wiki.archlinux.org/index.php/KDE#Using_xinitrc :

Using xinitrc
The meaning and usage of xinitrc is very well described here.
Edit /home/your-username/.xinitrc. Then uncomment:

Code: Select all

exec ck-launch-session startkde

After a reboot or/and login, each execution of Xorg (startx or xinit) will start KDE automatically.
----> Warning: By doing this you may have restart/shutdown functions disabled in your KDE menu. <-----
Note: If you want to start Xorg at boot, please read Start X at boot article.

I know you said that this started for you with KDE 4.6.1, so you're probably thinking this is not the issue. HOWEVER... Read that again. It said you may, not necessarily you will. My thinking is, that you did not have this issue with previous versions of KDE, and that you do now with 4.6.1, and that's why; the you *may* (as in "you might", not definitely *will*) gotcha. You finally came across a version of KDE where this does get you. It's not happening with me, because I have not yet hit the version of KDE where this will get me, like you did. No worries. I will at some point, I'm sure. You hit the "you will" version this time, I didn't.

Also, keep in mind, that my ~/.xinitrc is set as so:

Code: Select all

DEFAULT_SESSION="ck-launch-session ------->gnome-session"

... Which is probably why I am freezing right after KDE gets through loading.

- Arch Whisky to the rescue, every time.

[viking60]

Ah were to start: .xinitrc is the same here so that is not it. Just forget it. It is relevant for login manager issues but you said yourself that you have the poweroff button working.
This version of KDE 4.6 is the most stable I have ever experienced. So I have absolutely no problem with instability.
Other versions of KDE let me reboot and shut down the computer by the push of a button - yes that is correct (I do not understand what point you are trying to make here though). But that is my small problem.
Plying nice with vidalia: Just uninstall it - you don't need it. In fact it could try to start tor twice and cause trouble.

[dedanna1029]

So, you don't have

Code: Select all

exec ck-launch-session startkde

In your ~/.xinitrc?

Warning: By doing this you may have restart/shutdown functions disabled in your KDE menu.

... Which is what your problem is in your original post.

[viking60]

As I said I have

Code: Select all

DEFAULT_SESSION="ck-launch-session gnome-session"

and I have autologin.
That could have been the reason - but you took care of that by confirming that you have the poweroff button working anyway.

[rolf]

Is there still SystemSettings in 4.6.1? I imagine so. Here, in 4.5.5, toward the bottom of the 'Overview' first page, System Administration > Startup and Shutdown > Session Management >

There is a selection to "Offer shutdown options" that might be related.