Bug 256454 - x11/gdm: No users shown in login screen, and unable to unlock once locked
Summary: x11/gdm: No users shown in login screen, and unable to unlock once locked
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-gnome (Nobody)
URL:
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2021-06-06 19:56 UTC by Neel Chauhan
Modified: 2021-08-20 21:40 UTC (History)
8 users (show)

See Also:
bugzilla: maintainer-feedback? (gnome)


Attachments
GDM Greeter Log (5.20 KB, text/plain)
2021-06-06 19:56 UTC, Neel Chauhan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Neel Chauhan freebsd_committer 2021-06-06 19:56:51 UTC
Created attachment 225606 [details]
GDM Greeter Log

If I use x11/gdm with gnome3-lite, I cannot:

 * See the users on the login screen

 * If I login manually, and then lock, I am unable to unlock
Comment 1 Neel Chauhan freebsd_committer 2021-06-06 21:02:25 UTC
Also, I get errors like these:

Jun  6 13:56:13 omen polkitd[1576]: Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session6 (system bus name :1.210, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C.UTF-8) (disconnected from bus)
Jun  6 13:56:38 omen polkitd[1576]: Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session8 (system bus name :1.270 [<unknown>], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jun  6 13:56:48 omen gdm-password][5806]: gkr-pam: unable to locate daemon control file
Jun  6 13:56:48 omen gdm-password][5806]: gkr-pam: gnome-keyring-daemon started properly
Jun  6 13:56:50 omen polkitd[1576]: Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session8 (system bus name :1.270, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jun  6 13:56:56 omen polkitd[1576]: Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session9 (system bus name :1.283 [<unknown>], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jun  6 13:57:05 omen polkitd[1576]: Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session9 (system bus name :1.283, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jun  6 13:57:06 omen polkitd[1576]: Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session9 (system bus name :1.333 [<unknown>], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jun  6 13:57:07 omen polkitd[1576]: Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session9 (system bus name :1.333, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jun  6 13:57:18 omen gnome-keyring-daemon[5993]: couldn't access control socket: /var/run/user/1001/keyring/control: No such file or directory
Jun  6 13:57:19 omen polkitd[1576]: Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session11 (system bus name :1.340 [<unknown>], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C.UTF-8)

We should fix this.
Comment 2 Konstantin 2021-06-07 13:34:42 UTC
Today I upgraded my packages and came across a similar issue. In the console I can see:
gdm-password][1126]: gkr-pam: unable to locate daemon control file.
Gnome-shell process also logs numerous "JS Error: Failed to open reauthentification channel: ...."
I disabled GDM and GNOME in /etc/rc.conf and start DE typing startx /usr/local/bin/gnome-session in the console.

PS GDM is broken again.
Comment 3 Charlie Li freebsd_committer 2021-06-07 17:49:56 UTC
Probably caused by 249445.
Comment 4 Charlie Li freebsd_committer 2021-06-07 17:50:27 UTC
Let's properly link it, bug 249445.
Comment 5 Olivier Duchateau 2021-06-08 04:51:28 UTC
Do you try new version of GDM? I have an update [1] for the 3.38.2.1 release.

[1] https://framagit.org/olivierd/freebsd-ports-gnome/-/tree/40/x11/gdm
Comment 6 Neel Chauhan freebsd_committer 2021-06-23 23:44:19 UTC
(In reply to Olivier Duchateau from comment #5)

I haven't tested it. I was busy with drm-kmod hacking for the past two weeks along with an HELL assignment at work (I don't hate my job or team, but god I hate that assignment).

If it works, would it be fine if I commit the update? I will credit you however.
Comment 7 bpurgar 2021-06-24 11:02:45 UTC
(In reply to Olivier Duchateau from comment #5)

I tested it and nothing .. black screen when running gdm service and after some time in logs (/var/log/messages) i got warrning:
gdm-display.c priv->access_file == NULL

starting gdm produce only :X.log log .. :X-greeter.log is missing so i can debug what is going on with gdm (custom.conf debug is enabled) (i see that gdm 3.38.2 use /var/lib for home dir but in passwd home dir is set to /usr/local/etc/gdm/home)

any hint how to debug this to see what is going on ?
Comment 8 Vincent Bentley 2021-07-29 14:04:30 UTC
Can accountsservice-0.6.55 be rolled back to accountsservice-0.6.42 so that it is possible to install a working Gnome3 desktop?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249445
Comment 9 cyclaero 2021-07-29 14:39:30 UTC
(In reply to Vincent Bentley from comment #8)

For a temporary rollback, you can do the following, which resolved the issue for me:

mkdir -p ~/install/ports/sysutils
cd ~/install/ports/sysutils
svn checkout -r r517057 http://svn.freebsd.org/ports/head/sysutils/accountsservice accountsservice
cd accountsservice
make DISABLE_VULNERABILITIES=yes
sudo make reinstall clean

Then restart.
Comment 10 Vincent Bentley 2021-07-29 20:46:19 UTC
Thanks, that works well for me.
For anyone finding this thread needing the same fix, you also need the FreeBSD ports tree on the machine, subversion and automake to build it.
Comment 11 Vincent Bentley 2021-08-06 20:51:43 UTC
I had to do this again today after a package upgrade reinstalled accountsservice-0.6.55

After reinstalling 0.6.42, I locked the package version using:

pkg lock accountsservice-0.6.42