[Solved] pam_ck_connector cannot determine display-device

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
MikeS
Level 1
Level 1
Posts: 16
Joined: Sat Aug 12, 2017 10:29 am

[Solved] pam_ck_connector cannot determine display-device

Post by MikeS »

I run Linux Mint 18.2 Cinnamon 64 bit. Something went wrong a few days ago when I updated using the Update Manager. I updated applications and then deleted and added some kernel updates in a single operation. (Not wise!)

At boot the PC stopped with a flashing cursor. <Alt>+<F2> started the terminal. 'startx' did not work. Some searching revealed that slick-greeter and lightdm were not installed, so I installed them.

The PC still stops with a flashing cursor. If I use <Alt>+<F2> the terminal appears, and entering 'startx' now launches the graphical interface. The system then runs.

journalctl -b -p err lists some errors, the most relevant being the one below:
pam_ck_connector(polkit-1:session): cannot determine display-device

Does anyone know how to fix this? I have searched around, but do not have any confidence in the only slightly related information that I found.
Last edited by MikeS on Tue Aug 15, 2017 7:22 am, edited 1 time in total.
MikeS
Level 1
Level 1
Posts: 16
Joined: Sat Aug 12, 2017 10:29 am

Re: pam_ck_connector cannot determine display-device

Post by MikeS »

During my initial attmpts to get things working I loaded an Xorg intel 915 video driver. When I read the associated information carefully, it was suggested that PCs since 2007 should rely on nomodeset in the boot config. I deleted the old driver and the message above disappeared.

I still do not have a correct boot. It does boot to runlevel 5, but the errors below are shown.

mike ~ $ journalctl -b -p err
Aug 14 11:48:17 mike-Inspiron-13-5378 kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40080-0xfed40fff]
Aug 14 11:48:17 mike-Inspiron-13-5378 systemd[1]: Failed to start Show Plymouth Boot Screen.
Aug 14 11:48:17 mike-Inspiron-13-5378 ntpdate[1007]: name server cannot be used: Temporary failure in name resolution (-3)
Aug 14 11:48:18 mike-Inspiron-13-5378 NetworkManager[839]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Aug 14 11:48:18 mike-Inspiron-13-5378 wpa_supplicant[1067]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Aug 14 11:48:18 mike-Inspiron-13-5378 wpa_supplicant[1067]: dbus: Failed to construct signal
Aug 14 11:48:18 mike-Inspiron-13-5378 wpa_supplicant[1067]: Could not read interface p2p-dev-wlp1s0 flags: No such device
Aug 14 11:48:19 mike-Inspiron-13-5378 ntpd[1095]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Aug 14 11:48:20 mike-Inspiron-13-5378 ntpd[1095]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Aug 14 11:48:21 mike-Inspiron-13-5378 ntpd[1095]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Aug 14 11:48:22 mike-Inspiron-13-5378 ntpd[1095]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Aug 14 11:48:23 mike-Inspiron-13-5378 ntpdate[1230]: the NTP socket is in use, exiting
Aug 14 11:48:28 mike-Inspiron-13-5378 ntpdate[1292]: the NTP socket is in use, exiting

Searching the web indicates that the problem appears to be associated with the first line. References to failure to start Plymouth appear throughout the log.
MikeS
Level 1
Level 1
Posts: 16
Joined: Sat Aug 12, 2017 10:29 am

Re: pam_ck_connector cannot determine display-device

Post by MikeS »

Problem is fixed. I tried two things without rebooting in between, so not sure which one worked.

1) From terminal: "sudo dpkg-reconfigure lightdm"
Nothing appeared to happen, so not sure if it did anything.
2) After entering "startx" and entering GUI, ran Administration| LightDM GTK+ Greeter settings
3) Rebooted and Lightdm came up immediately.

[Edit: running "journalctl -b -p err" from the terminal still shows many errors. I assume this is just the multi threaded nature of systemd.]
Post Reply