KDE 4 Login Manager Broken?

[moktoman]

I might have missed something in the release notes for KDE 4 (4.0.1), but from what I can tell, the login manager located within the Advanced tab in System Settings is unusable.

I was going to make some changes (KDM-KDE4 is currently not themed) and was dismayed to find that every option under all 7 tabs are grayed out and unchangeable.

Is this an incomplete feature? I would think the developers would simply keep it out of the GUI if its wasn't finished yet, and if that's the case, then logic would dictate that there is something wrong (yet again) with my KDM-KDE4 settings...?

Any ideas?
And assuming my settings are screwed up somehow, how would I go about just resetting all the settings for KDM-KDE4 ?

[claydoh]

I think that by default, we are using kde3's kdm, unless you decide to install and enable kdm-kde4, so all the login settings are still administered in kde3's kdm settings

If you want, you can install and try out kdm-kde4 by installing that package, Adept should offer you to select which login manager you want to use. Select KDE4's version and try that to see if that works. If you need to switch back, run the command

sudo dpkg-reconfigure kdm
this is useful too if you want to try out gnome's GDM, or some other login manager, or install ubuntu/xubuntu, etc alongside an existing Kubuntu and you want to use a different login tool

KDM-KDE4 probably isn't tweaked at all by Kubuntu, so it may not have much in the looks department at this time, so be prepared for that :)
or for it to not work at all....

[moktoman]

Yes, I'm aware of that, and I actually already have KDM-KDE4 installed, which is the one I'm trying configure. Within KDE4's System Settings there is a login manager that I'm assuming is for KDM-KDE4 since it is different than the one in KDE3 (as far as options that are available, and general interface differences).

That login manager within KDE4 is what I am trying to get to work.
And oddly enough, I can run KDE3's system settings from within KDE4 and make changes in that version of login manager, but it doesn't seem to be effecting KDM-KDE4 at all (which doesn't surprise me).

I'm thinking it might be that my kdmrc file got messed up. Would it be wise to delete that file? I was hoping it might get recreated when I reboot...

[claydoh]

I don't know, I tried kdm-kde4 last night, and it seemed to not work, it was using kde3's kdm as far as i could see. It did work for me some time back, but was unconfigured. It did work , though it did not seem any different from kde3's kdm

[dibl]

KDE 4 System Settings > Login Manager seems non-functional on my Hardy Heron installation, too. I have the impression that it does not have "Administrator Mode" incorporated yet -- I don't see a way to obtain root privileges. Maybe there's a command to run at as "kdesudo" -- that would probably work.

[Fintan]

Navigate to:
/usr/lib/kde4/bin/sytemsettiings
as root in konqueror or dolphin.

[dibl]

Alt-F2 "kdesudo kcontrol" still works fine, however

[dibl]

Navigate to:
/usr/lib/kde4/bin/sytemsettiings
as root in konqueror or dolphin.



That looks like a good way to get it open in root mode, but it still won't let me change the settings -- can't change the user image source or set a user image, for example.

However, "kdesudo kcontrol" is happy to cooperate.


EDIT: That's odd -- D3lphin, running in root mode, puts up a "See System Administrator" message when I click the "systemsettings" file. So somehow D3lphin loses track of its mode. Hmmmmmmmmmmm. I'll try Konqueror.

EDIT#2: Huh. Same thing in Konqueror -- "See System Administrator", followed by opening the GUI with no "Admin Mode" enabled. Weirdness!

[Fintan]

Let me think about this....hmmm. oh yes we are in alpha of HH. A week ago kcontrol was not even populated, much less working :)

System settings in HH alpha are at the same stage they were in GG beta.
Kde4 system settings are not even close.
I agree they should be, but for the "lords" that be/are these trivial thing are, well just that...trivial.

All we can do is report and do more of that ;D

[dibl]

oh yes we are in alpha of HH. A week ago kcontrol was not even populated, much less working :)



Heh heh heh -- you are so correct, Fintan! Actually, HH is working so well that it's hard to remember that it isn't actually a released OS. I'm using just like I do the "real" OS's -- I shouldn't complain about such stuff as System Settings -- just use KControl and get on with it! ;D

[Fintan]

Well,....... it was martini time over here an hour ago :D ;D

[dibl]

Well,....... it was martini time over here an hour ago :D ;D


Damn -- I hate to hear that I missed ANY martini hour! ;D

[Fintan]

Actually, HH is working so well that it's hard to remember that it isn't actually a released OS.

I know wjat you mean. I have been using HH and kde34 for more than a month now and really only have to bot back into GG for some stuff. Like scanning.


Damn -- I hate to hear that I missed ANY martini hour!

Well when yours starts I'll be happily in dream land ;D :D

[dibl]

only have to bot back into GG for some stuff. Like scanning.



Hmm -- I don't think I've run my scanner since I installed HH. Guess I'd better try it, huh?


EDIT: UH-OH --- Kooka gives me a choice of my Logitech QuickCam Communicate webcam, or my Hauppauge Win-TV PVR-150 card. No Epson scanner shown available. :'(


dibl@cville:~$ lsusb
Bus 004 Device 002: ID 046d:08d7 Logitech, Inc.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 004: ID 04b8:010a Seiko Epson Corp. Perfection 1640SU
Bus 003 Device 002: ID 04b8:0005 Seiko Epson Corp. Stylus Printer
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 005: ID 045e:00dd Microsoft Corp.
Bus 001 Device 004: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 001 Device 001: ID 0000:0000
Bus 005 Device 005: ID 154b:000f
Bus 005 Device 001: ID 0000:0000

[moktoman]

Ok, thanks guys.
I'll try the kcontrol thing.
- Michael

[claydoh]

yeah, scanning is broken in HH due to some as of yet unresolved hal/udev/PolicyKit issues
https://bugs.edge.launchpad.net/ubuntu/+source/sane-backends/+bug/181129

[MoonRise]

Wish they would also find a way to support the Visioneer Stobe Pro. Has always been a great performer for me. Hate to ditch it.

[moktoman]

Ok, so I tried the 'kdesudo kcontrol' command from Alt+F2, and it prompts me for the kdesudo password (which I'm assuming is the same as my root password) which I gave it, then the password prompt disappears and nothing happens.

Also, I somehow switched my user account to the root group, which I thought might be affecting my ability to open applications with root privileges ??

Also, I noticed that KDE4 has the user account settings dialog within the Login Manager area that I am try to access, so I'm in a paradox of needing to change my user permissions to allow myself to access the area where I can change those permissions (as well as KDM settings). Talk about a mind trip...

[moktoman]

Alright, I seem to have gotten things under control.

For the benefit of anybody in a similar situation I will explain in brief detail the steps I took to solve my problem...

- Booted in recovery mode;
- From within recovery console (as root) did 'startx' to get into ubuntu desktop
- Ran 'System Settings' which brought up KDE4 System Settings, in which I was able to finally access the KDE4 Login Manager in all its glory.
- Made desired changes; Applied and quit setting dialog.
- To fix group association for my user account I opened up Dolphin, navigated to '/usr/bin' and ran the KDE3 System Settings, from which I selected User Management, and made the necessary changes.
- Applied settings, quit, and rebooted normally.
- Everything seems to be working fine now.

Whew! What a mouthful...

Anyway, thanks for the suggestions.

- Michael