I forgot to mention: Am 16.04.2015 um 19:52 schrieb Stefan Seyfried:

Hi,

Today I updated to current TW/Factory: susi:~ # cat /etc/os-release NAME=openSUSE VERSION="20150413 (Tumbleweed)" VERSION_ID="20150413" PRETTY_NAME="openSUSE 20150413 (Tumbleweed) (x86_64)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:20150413" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://opensuse.org/" ID_LIKE="suse"

Certainly a bad idea :-)

* gdm fails to start, after a few minutes I'm at least able to log on the text console It is either "/usr/lib/gdm/gdm-wayland-session[1253]: Unable to register display with display manager" or, if I try to switch back to X, it's "/usr/lib/gdm/gdm-x-session[9556]: Unable to run X server".

Ok, try lightdm. Logs me into XFCE, but nm-applet does no longer know the configured networks. Try kdm4, the same. xdm does not allow to select a DE and tries to start KDE -- instant ctrl-alt-backspace twice :-)

Something is wrong with my permissions: as root: susi:~ # nmcli c NAME UUID TYPE DEVICE linuxtage 4fc5446c-7020-41ea-abbe-21ba03706055 802-11-wireless -- WLAN_GAESTE 8c58232e-3bb7-4c03-9a32-dbcfd3f7833b 802-11-wireless -- Software 18f1ab17-d1af-490a-8d2d-1469c7ac9ace 802-11-wireless -- [...about 50 more networks...] seife's milestone-Netzwerk 6d8fd21a-ac2e-442f-bf7b-0dd2a50a697e bluetooth -- virbr0 02424e1a-e412-428b-811f-0245935f3033 bridge virbr0 defy 834a07de-200f-4a27-8163-64c241ebb623 802-11-wireless -- virbr0-nic be935080-1fcb-45cb-9f02-dbe85833c7fc generic virbr0-nic

as user: seife@susi:~> nmcli c NAME UUID TYPE DEVICE virbr0 02424e1a-e412-428b-811f-0245935f3033 bridge virbr0 virbr0-nic be935080-1fcb-45cb-9f02-dbe85833c7fc generic virbr0-nic Auto cable facf0891-0ac2-4a49-ade1-faa8da8d175e 802-3-ethernet cable

Actually I had to plug in a cable to send this mail. Working around the problem by using nmcli as root does not work, because the credentials are stored in the gnome-keyring...

So what can I do to debug this?

polkitd ist running systemd-logind is running

loginctl does not show anything, neither as root: susi:~ # loginctl SESSION UID USER SEAT

0 sessions listed.

...nor as user: seife@susi:~> loginctl SESSION UID USER SEAT

0 sessions listed.

But I have no idea if this needs to be like this or if there is the error?

additionally, power management functions like "suspend" or "hibernate" via xfce4-power-manager also do not work. I guess it is the same permissions issue? -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 16.04.2015 um 20:37 schrieb Guido Berhoerster:

Yeah, all of the above operations are in openSUSE by default only available to an unprivileged user on the active console without additional authentication. So if you don't have an active session registered with systemd-logind as the above indicates, polkit will not grant permission for these privileged operations or as for authentication via a polkit-agent. Maybe your PAM config is broken?

Yes, "pam-config -a --systemd" did fix it. Which is a pity, because now I need to find out how to get rid of the systemd session started and teared down for every cron job etc. (I had disabled pam_systemd deliberately) :-(

Or there is something wrong with logind.

maybe I just need to find a way to "log in" to logind without pam_systemd :-( -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 17.04.2015 um 01:33 schrieb Cristian Rodríguez:

On Thu, Apr 16, 2015 at 8:04 PM, Stefan Seyfried wrote:

...

maybe I just need to find a way to "log in" to logind without pam_systemd :-(

--> cronie git:(master) <--

I also do not want systemd sessions for ssh logins :-) Looks like I'll have to create and maintain my very own pam config... ...or find a way to use logind without pam... -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 17.04.2015 um 14:56 schrieb Cristian Rodríguez:

On Fri, Apr 17, 2015 at 3:23 AM, Stefan Seyfried wrote:

...

I also do not want systemd sessions for ssh logins :-)

I guess setting UsePam no in sshd_config will do the trick.. (if you use key based authentication, not sure if password login will continue working)

I have now removed pam_systemd from common-session and added it only to lxdm and login pam files. This seems to work fine. But if I now have to start maintaining my own PAM configuration to get a halfway sane system, then it's maybe really time to just start using yocto poky on my x86 boxes, too (it's doing well on all embedded boxes for a long time anyway) :-) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org