Hi All,

While I was installing some packages, the power in my street went out (uncleanly killing my system) ... unfortunately Kpackage was open at the time of the power outage.

Now when I try to use KPackage, I get "Login Problem, Please Login Manually" ... which does not allow me to login using either the root or user's password.

I have rebooted my computer many times and have even run a 'reiserfsck /dev/*** --fix-fixable' on my system, which did not repair the problem.

I have researched this error, but have only found responses that people suggest changing the KPackage behaviour from 'su' to 'sudo' ... ; while this does work, it feels like a 'putting-a-band-aid-over-a-warning-light-so-I-can't-see-the-warning-light-anymore' kind of 'fix?' which isn't good as it would enable anyone using the system to add or remove packages without thought or consequence.

What I would prefer to do is actually fix the problem so that proper root password entering is again required to add or remove packages, so my question is:

1. Does anyone know if KPackage 'locks' out a file(s) on the system which may be preventing me from logging into the program correctly, and if so what and where the file(s) may be?

2. Can I delete any kpackage (profile?) file to gain normal login behaviour again?

3. Is this a permissions error?, has something in users/groups? been broken that I can look into?

4. Can anyone offer any other suggestions or files I can look at on how I may be able to properly repair this KPackage login problem on my system?


Thanks very much, I'll look forward to hearing from you.

Cheers

p.s. I'm on Slackware 12.2

I vaguely remember kpackage. With Slackware, you can run this command on any package you like

upgradepkg --reinstall somepkg which simply installs over, and throws the config file in as .new. Try it.

Hi business_kid,

Thanks, Yes I know about upgradepkg, but I'm not sure I understand what it is you are trying to tell me about fixing KPackage?

What Package would you suggest I re-install?

I don't know offhand but if there is a lock (or some other) file throwing it off it's probably an idea to quit kde, clean out /tmp and also have a look in /var/run perhaps.

I'd also look for kpackage directories in your ~/.kde directory to see what's in there.

AFAIK kpackage doesnt work with Slackware packages (at least the version included in KDE4, dont know about KDE3).
Also kpackage has been removed from recent KDE versions completely due to the fact that it was unmaintained.

Whilst I wouldn't recomend using Kpackage in Slackware - it did work in KDE3 as the OP is running with Slackware 12.2.