I have just upgraded my opensuse x86_64 to 13.2 with KDE4. The process worked fine, but when I log in my kde4 session, the network manager plasmoid is frozen: I can see the surrounding wifi hubs, but refuses to connect to my usual modem, with the following message box:
Failed to add connection
No session found for uid 1000 (unknown)
My connection editor shows up an empty list. Moreover, the uid 1000 is my current user and is not unknown at all.
However, when I log out and relog in, everything works as usual: I’m automatically connected to my modem, and everything is ok.
Ok, found something in /usr/lib/systemd/system/user@.service
but it doesn’t explain why I got root the first time I log as my personal user, and the correct uid when I logout and relogin
The login command normally makes pam calls. The configuration in “/etc/pam.d” indicates which pam modules to call. And “pam_systemd.so” is one of those pam modules, presumably the one that starts the user manager.
I’m not seeing that here (with KDE). However, if I use “su” or if I “ssh root@localhost”, then a root system manager is started. Maybe “kdesu” and “sudo” have a similar effect.
No, nothing to do with su or sudo. I issue a standard graphical login with kdm, then I disconnect (logout) and reconnect with the same usual user ! First I’m root wheras I never been logged as root, then with the correct uid (1000)
Weird no ?
When I get the kdm greeting after a reboot, I open another console, and I login on it as root. Then I killall Xorg, then after xorg restarts, I make a correct login, and all the services depending on systemd work fine.
Found something: when I get the kdm login window, I don’t login at once, but wait a few more seconds. It seems that there is maybe a hidden timeout somewhere, or a task that hasn’t been completed.
Then I login and I get a 100% working session.
The question is: how can I track this possible uncompleted task or pending timeout while the kdm windows is displayed ?
I tried systemd-analyze critical-chain, but it didn’t show up (apparent) abnormal behavior
Sounds like a problem a user in the german forum has after upgrading to 13.2 (on 2 machines, on the 3rd one it works fine… :):
On first login, the user session is not registered with logind, which causes various problems because of missing permissions with networkmanager, sound and mounting.
After logging out and logging in again, the problem is gone.
Hi there! I’m also affected by this bug. 2 PCs with upgrade have this bug, one maschine with clean installation not.
I changes also the display manager but it doesn’t change anything. When I wait a little bit and login then after start, all is working fine.
After some findings in the german thread, I have a suspicion:
do you have ibus installed?
Try to remove it and all ibus-* subpackages, libibus can (and probably must) stay.
I’m not sure yet though whether this really is the problem…
