You are not logged in.

#1 2010-10-13 10:35:32

goplexian
Member
From: Vancouver, Canada
Registered: 2010-01-27
Posts: 17
Website

[solved] gdm not showing user list and not recognizing gconf

I installed gdm2setup from aur and ran it as root, and since then gdm will no longer display a user browser to select my user from, I have to manually type in the user name and password to login.

I uninstalled gdm2setup, and then did a force reinstall for gdm (pacman -S --force gdm)

Then I rebooted, and as I mentioned, the user browser does not display.

I edited /etc/gdm/custom.conf so that it shows:

[greeter]
Browser=1

...but still no luck.

I made sure that gconf says that disable_user_list is not true, and it isn't.

gconftool-2 --get /apps/gdm/simple-greeter/disable_user_list
false

So I don't know what else to do, or why this is happening.
If anyone can help it would be greatly appreciated.

EDIT: Here is the most recent :0-greeter.log after a fresh reboot
No idea if any of this is related to my problem.

# cat /var/log/gdm/\:0-greeter.log

** (<unknown>:2058): DEBUG: Client registered with session manager: /org/gnome/SessionManager/Client1
gnome-session[2050]: WARNING: Could not launch application 'gnome-power-manager.desktop': Unable to start application: Failed to execute child process "gnome-power-manager" (No such file or directory)
** (process:2077): DEBUG: Greeter session pid=2077 display=:0.0 xauthority=/var/run/gdm/auth-for-gdm-JngQ5L/database
gdm-simple-greeter[2077]: Gtk-WARNING: gtkwidget.c:5676: widget not within a GtkWindow
gdm-simple-greeter[2077]: WARNING: Unable to read from file /etc/arch-release
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x160002b (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x160002b (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x160002b (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
Window manager warning: Log level 16: Failed to send buffer
gdm-simple-greeter[2077]: WARNING: Failed to send buffer
Window manager warning: Log level 16: Failed to send buffer

(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.

(polkit-gnome-authentication-agent-1:2076): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in

(polkit-gnome-authentication-agent-1:2076): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in

(polkit-gnome-authentication-agent-1:2076): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in

(polkit-gnome-authentication-agent-1:2076): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in

(polkit-gnome-authentication-agent-1:2076): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in

EDIT#2

Solved!

sudo -u gdm gconftool-2 --set --type boolean /apps/gdm/simple-greeter/disable_user_list false

Last edited by goplexian (2010-10-13 10:56:29)


Intel Core2Quad Q9550 @ 3.4 GHz, 4GB DDR2 800MHz
GeForce GTS 250 1024MB + Raid5 Storage
blog

Offline

#2 2010-12-02 17:19:10

SiD
Member
From: Germany
Registered: 2006-09-21
Posts: 729

Re: [solved] gdm not showing user list and not recognizing gconf

I want to set disable_user_list to true, but If I execute this

sudo -u gdm gconftool-2 --set --type boolean /apps/gdm/simple-greeter/disable_user_list true

I'm asked for a password ...

EDIT:

this line was commented in my sudoers file

%wheel    ALL=(ALL) SETENV: ALL

Last edited by SiD (2010-12-02 19:34:46)

Offline

Board footer

Powered by FluxBB