On 11/14/06, Kevin Williams <[EMAIL PROTECTED]> wrote:
Soon after booting into runlevel 5 (KDE) I noticed that, the kbd shortcuts Ctrl+Alt+Fn to switch between the vt's don't work ! Back in the red hat days I knew how to do this, now I just don't remember !! :-( I chose keyboard layout in KControl and that solved the problem of Ctrl+Alt+Fn. Unfortunately, this seems to work as long as I'm logged into KDE.
Somethings wrong with your keyboard setup. Ctrl+Alt+Fn is not a KDE thing. It should works at the console or in X or wherever.
I've tried to look into SuSE (occasionallt I keep booting into SuSE to see how SuSE achieves things which, helps me to troubleshoot whenever I've probs in BLFS) and found that SuSE uses different approach. SuSE seems to be using keymap files stored under /usr/share/kbd. I don't find this folder in BLFS. Maybe, it has to do with the difference between XORG-7 and XORG-6.9. I've XORG-7 installed in BLFS.
If you have a newer LFS, they are in /lib/kbd. X uses an entirely different setup, but I'd try to get things working at the console before complicating things with X.
Secondly, I can't sudo ! Sudo asks for root users password and typing the right password doesn't let me in. Displays a message 'Sorry, try again' ! After three tries it just goes away with a message '3 incorrect password attempts' ! I've installed Kerberos5, heimdal, Linux-PAM with Cracklib support (Uh ! Overkill !). This is what I find in my /etc/pam.d/sudo file:
I don't think the pam configuration is the issue. Two things. What are the permissions of sudo? It needs to be suid as far as I can tell, just like su: [12:08 PM [EMAIL PROTECTED] ls -l /usr/bin/sudo ---s--x--x 2 root root 91232 2006-05-23 15:39 /usr/bin/sudo Second, look in /var/log/auth.log for some clues about what's happening in the authentication process. And, yes, you have a ton of overkill there. Especially with kerberos, which is completely non-trivial. Not that your asking, but it would be a much better plan to build these things gradually. Also, I think it's conflicting to have both Krb5 and heimdal.
Finally, I've problems with kpowersave. I've acpid and powersave (the latest version) installed to support kpowersave. acpid config files are empty to make it forward the events to powersave. Powersaved seems to be running fine. When I boot into KDE, kpowersave displays a messagebox saying 'You are not permitted to connect to the powersave daemon via DBUS. Please check your DBUS configuration and installtion' !!
Are you running a dbus session daemon? You'd probably see something like dbus-launch in ps, but I don't know how KDE sets this up. I don't get any powersave/scheme
option in kpowersave menu save the help menu !! I've compared the settings in SuSE and BLFS including the file permissions and found them to be the same. kpowersave works in SuSE while it displays the before mentioned error message. I guess, it has to with the DBUS policy. These are the messages from powersaved I found in the logs: ----------------------------------------------------------------- daemon.log:Nov 14 02:30:38 kevkim powersaved[15074]: WARNING (filter_function:208) Hal service stopped. Battery information no longer available daemon.log:Nov 14 02:30:39 kevkim powersaved[15074]: ERROR (filter_function:97) DBus daemon disconnected. Trying to reconnect...
Is Hal running? Obviously, kpowersaved isn't going to do squat if it can't get any info from Hal.
I've compared files under /etc/dbus/, /etc/acpid and /etc/powersave and also the files in /etc/sysconfig and found them to be same as those in SuSE. Diff returned nothing ! Yet, I don't understand why it works in SuSE and not in BLFS.
That explains one thing. Unless you have pam_console going, you're going to need to give unprivileged users permission to use the Hal methods. See here: http://lfs.osuosl.org/blfs/view/svn/general/hal.html#hal-config Good luck. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
