These past days I installed a Kubuntu 12.04 on my Lenovo W520, and I was very satisfied. Until some minutes ago.

I copied data to the harddrive, locked the screen and went to get lunch. When I came back I couldnt log in anymore. I rebooted(encrypted hd btw), and instead of my convenience login booting straight into the desktop, I got the KDE auth window. When I use the correct password and username, KDE seems to try to log me in, then I'm back at the auth screen. When I switch to console, log in as the same user, I'm at the shell. Turned out the hdd was full. I deleted 30 gig so theres space now. When I kill KDM and use startx, I can get to my desktop with all my settings(session isnt saved anymore though).


/var/log/kdm.log:
klauncher(1913) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(1905)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"

kdmgreet(1905)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /tmp/0692033858/.config/ibus/bus
ddxSigGiveUp: Closing log
Server terminated successfully (0). Closing log file.


dbus is up and running. I even stopped and restarted it without trouble.


When I try to change the convenience login and switch it off, I get:
Unable to authenticate/execute(Code 4)

Any ideas?? Thanks for your help.

1st step should be to create a new user and see if you can login as it, this will let you know if the problem is your account or something else

this command will walk you through user creation

Code: Select all

sudo adduser <username>

Zwetschge wrote:When I try to change the convenience login and switch it off, I get:
Unable to authenticate/execute(Code 4)

Any ideas??

Edit /etc/kde4/kdm/kdmrc and change AutoLoginEnable=false to AutoLoginEnable=true

@google01103: As I said, logging in works, on the commandline. I ctrl-F1 to the console and log in as that user. The account isn't the issue. I can even start my KDE desktop, if I sudo kill kdm and then startx. My settings and whatnot are there.

@toad: AutoLoginEnable is already 'true' in there

I just started KDE as root, and was able to switch it back and forth then in the sys settings. But it fails to log the user into KDE.

I suspect a leftover lock file thats blocking something. Where do I look?

You got polkit-kde-1 installed? Have you tried changing the settings via systemsettings? No idea what could confuse kdm here. Can't believe that it has something to do with the user...

"polkit-kde-1 is already the newest version." when I try to apt-get install

I just realized sound also doesnt work anymore. Neitehr in flash nor VLC. Both used to work. Kmix shows only 'dummy output'.

I have to leave now for the weekend. I'm pretty ****, honestly. Filling / to the brink shouldn't result in the system trashing itself. Slow load times, a warning, yes. But not breaking stuff that used to work and wasn't changed.

Understandable but a fact of life. I very much doubt there is the perfect OS. But moaning does not solve your problem. Can you let us have the output of df -h which should also give us an insight into your partitioning scheme.

Oh - and keep an eye on your disk space in the future

Not sure if that helps, but try deleting /var/tmp/kdecache-<username>. Maybe it's corrupted.
Also verify that dbus is running, by ps aux |grep dbus.

Greetings

@toad:

df -h

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/Ghostdive-root 143G 94G 42G 70% /
udev 1.9G 4.0K 1.9G 1% /dev
tmpfs 782M 520K 782M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 2.0G 80K 2.0G 1% /run/shm
/dev/sda1 228M 59M 157M 28% /boot


It's what was suggested during boot.
Believe me I'll have an eye on disk space now.

@scummos:
rm -rf on that folder didnt do the trick, sadly. I deleted that cache folder, rebooted, still couldnt log in via kdm, switched to console, logged in, killed kdm, started X, here I am. I still get 'error: code 4' when I try to change the convenience login.

What kinda frustrates me is that I cant find a log that says "Can't write to folder X" or "lock file Y in place" or something similarly helpful.

Hm, sorry then Guess it was worth a try.

Try to check ps aux for dbus. If it's there, try "qdbus" and see if it lists stuff.

If I understand this right, your problem is that you don't get graphical login / autologin any more, right? Did you try using another display server? There's plenty of them. Try slim, lxdm or gdm for example. Maybe those work.

Greetings

scummos' idea about checking dbus is good. For lazy fingers a pgrep qdbus works just as well. But Kubuntu should have that wrapped up, methinks.

What about the comprehensive approach: sudo apt-get remove --purge kdm followed by a sudo rm /etc/kde4/kdm/kdmrc in case that file is still there and finally a sudo apt-get install kdm?

Sorry forgot to mention dbus. It is there, seems to be up and running fine. I did stop and restart it without error.
qdbus lists a ton of things, probably as expected.

me@Ghostdive:~$ ps auxf | grep -i dbus
102 974 0.0 0.0 3964 1520 ? Ss 10:19 0:00 dbus-daemon --system --fork --activation=upstart
me 2289 0.0 0.0 2576 632 tty2 S 10:20 0:00 \_ /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session x-session-manager
me 2323 0.0 0.0 4060 208 ? Ss 10:20 0:00 \_ /usr/bin/ssh-agent /usr/bin/gpg-agent --daemon --sh --write-env-file=/home/me/.gnupg/gpg-agent-info-Ghostdive /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session x-session-manager
me 2324 0.0 0.0 5208 388 ? Ss 10:20 0:00 \_ /usr/bin/gpg-agent --daemon --sh --write-env-file=/home/me/.gnupg/gpg-agent-info-Ghostdive /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session x-session-manager
me 2332 0.0 0.0 3920 492 tty2 S 10:20 0:00 /usr/bin/dbus-launch --exit-with-session x-session-manager
me 2333 0.0 0.0 4340 1412 ? Ss 10:20 0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session


me@Ghostdive:~$ pgrep qdbus
me@Ghostdive:~$ pgrep dbus
974
2332
2333
me@Ghostdive:~$

@scummos:

Convenience login is still enabled, but doesnt work. I DO get the graphical login window instead. When I try wrong credentials, I get the expected error message. When I try the correct ones, it seems to try and start KDE. I see a black screen for a split second, probably telling me that it cant do something or something crashed, then I'm back at the login screen once again.

Removing/Reinstalling KDM sounds like a good idea. What would I lose? What could go wrong?

X.Org X Server 1.11.3
Release Date: 2011-12-16
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.42-26-generic i686 Ubuntu
Current Operating System: Linux Ghostdive 3.2.0-30-generic-pae #48-Ubuntu SMP Fri Aug 24 17:14:09 UTC 2012 i686
Kernel command line: BOOT_IMAGE=/vmlinuz-3.2.0-30-generic-pae root=/dev/mapper/Ghostdive-root ro quiet nosplash
Build Date: 04 August 2012 01:51:24AM
xorg-server 2:1.11.4-0ubuntu10.7 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.24.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Sep 18 10:19:16 2012
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
klauncher(1743) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(1735)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"

kdmgreet(1735)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /tmp/0077350107/.config/ibus/bus
ddxSigGiveUp: Closing log
Server terminated successfully (0). Closing log file.