>> But the pam message still is there
it's o'k and doesn't matter much.
>> Now the only little problem I've is that when I log in Kde4 or E, Knetworkmanager doesn't work and I can't shutdown directly, I took some screeshots.
let's first discuss E. you should be able to shutdown from menu (directly). if not - just edit the file (as 'root'):
/etc/enlightenment/sysactions.conf
there you can set your custom commands for hibernate, sleep, reboot, shutdown and other system actions. syntax is straight forward and well explained, no issues should occur (post if any
).
also it's recommended to use 'wicd' instead of 'NM' because it can work without systray and allow direct scripting configuration for your network interfaces (works here just fine and available in the same repo of course. after installation service should be started manually or PC should be rebooted).
*********************************************
here goes KDE part. i'm not an expert in KDE so please beg your pardon if something is not as i think.
1) KDE is quite complex and settings are... hmm.. let's say 'awesome'. it has adopted XDG specs (at least kde4) and starts any... '.desktop' file 'Exec=' entry from 'XDG STARTUP' - i.e. - /usr/share/autostart/ (according to the $XDG* variables)- without user notice (you need 'root' privileges to clean that trash). moreover, settings are so awesome that a small 'tick' somewhere inside settings of one software could lead to the autostart of another (those, who lazy to 'click through the forest of options' to guess wtf pulled the trigger this time, just remove boring package).
this time it's clear that replacement of 'kdm' to the 'entrance' resulted in not started 'NM' daemon (guess that something else also could be missed, may be for good). imho - 'NM daemon' is started via 'dbus' and integrated with global system settings via YaST. only can advise to check YaST's network settings, check that 'dbus' service is active (on) and running. if doesn't help - nevermind (yep, exercise is funny so i just vote for 'wicd'). you can login via 'kdm', install 'htop', open console, start 'htop' and see the exact command which starts 'NM daemon'. the rest is easy - add this command to ' /etc/profile.local ' or to your ' ~/.profile ' and allow in YaST user manipulations with network interfaces via 'NM'. (though actually it'd be better to get wtf this daemon is not started via 'dbus' with 'entrance' and why the hell 'KNM' see nothing instead of running daemon). another 'bright' idea is to look inside '/usr/share/autostart/' and check launch of which '.desktop' file will restore 'KNM'.
2) the case with 'shutdown' also a bit tricky. as we see KDE wants 'kdm' (may be it can even operate with 'gdm' - who knows...). only can advise set 'sudo' properly and add/create keyboard shortcuts to turn PC off (restart, etc.). shortcuts could be defined somewhere inside KDE settings and commands could look like this:
a) shutdown
Code:
sudo /sbin/shutdown now
b1) reboot
b2) reboot
Code:
sudo /sbin/shutdown -r now
etc. also you can prepare this commands in a separate files placed inside ' $HOME/bin ' and (hope you can) put them into KDE menu.
sorry, i'm not a KDE expert (and never will...)
Bookmarks