I've got a bunch of problems with my BLFS system with KDE-3.5.5 (Ken, I
acted on your suggestions and compiled KDE-3.5.5 using the instructions in
BLFS Book which worked just perfect ! :-) )

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. These
shortcuts don't work from the login screen ! Infact, I've probs while on KDM
login screen. Typing hyphen produces a strange char while in the login
screen ! I want to have the facility to switch to the VT irrespective of
whether I'm logged into KDE or not. At the moment it doesn't seem to be
possible. Now, how I do I go about this. FYI, Ctrl+Alt+Backspace doesn't
work either (even in KDE) !

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.

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:
----------------------------------------------------
auth       required     pam_unix.so
auth       sufficient   pam_rootok.so
account    required     pam_unix.so
session    optional     pam_mail.so dir=/var/mail standard
session    required     pam_unix.so
session    required     pam_env.so
-----------------------------------------------------
Not sure, if these are the right settings !

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' !! 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...
daemon.log:Nov 14 02:30:48 kevkim powersaved[15074]: ERROR
(hwEvent_callback:113) hw event socket broke away trying to reconnect...
daemon.log:Nov 14 15:05:44 kevkim powersaved[5402]: WARNING
(filter_function:208) Hal service stopped. Battery information no longer
available
daemon.log:Nov 14 15:05:53 kevkim powersaved[5402]: ERROR
(hwEvent_callback:113) hw event socket broke away trying to reconnect...
daemon.log:Nov 14 15:05:57 kevkim powersaved[5402]: ERROR
(filter_function:97) DBus daemon disconnected. Trying to reconnect...
---------------------------------------------------------------

Seem like a problem with DBUS. I'm thinking of recompiling DBUS, not sure if
it would help.

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.

I would really appreciate any help in this regard. Please let me know if
further info is needed and I'd be glad to provide that info.

Thanks.

Kevin
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to