I just emerged a system from scratch within a vmware environment. When starting gdm, the greeter seems to timeout, the user chooser is not shown (just the blue blackground) before beeing presented with "Oh no! Something has gone wrong". Before opening this issue, I tried the following: - Installation of vmware-tools - Adding "/usr/bin/vmware-user" to /etc/gdm/PreSession/Default - Emerging gdm with USE="-gnome-shell" I emptied the logfiles and set debug to enabled in /etc/gdm/custom.conf. Test was made with gdm built with gnome-shell USE Flag enabled. Don't really see where this could be originating, thx for any help
Created attachment 310709 [details] emerge --info output
Created attachment 310711 [details] sylsog messages /var/log/messages
Created attachment 310713 [details] gdm greeter log
Created attachment 310717 [details] gdm :0-slave.log
I just redid the installation with the same binaries on a bare metal with nvidia graphics card using nvidia-drivers: The issue cannot be confirmed on bare metal, only within vmware environment.
From the logs: gdm-password][7627]: AccountsService-DEBUG(+): ActUserManager: Seat still actively loading, so not setting loaded property gdm-password][7627]: AccountsService-DEBUG(+): Failed to identify the current session: Unable to lookup session information for process '7627' gdm-password][7627]: AccountsService-DEBUG(+): ActUserManager: seat unloaded, so trying to set loaded property gdm-password][7627]: AccountsService-DEBUG(+): ActUserManager: Seat wouldn't load, so giving up on it and setting loaded property gdm-simple-slave[7527]: DEBUG(+): GdmSignalHandler: handling signal 15 gdm-simple-slave[7527]: DEBUG(+): GdmSignalHandler: Found 1 callbacks gdm-simple-slave[7527]: DEBUG(+): GdmSignalHandler: running 15 handler: 0x408d30 gdm-simple-slave[7527]: DEBUG(+): Got callback for signal 15 gdm-simple-slave[7527]: DEBUG(+): Caught signal 15, shutting down normally. gdm-simple-slave[7527]: DEBUG(+): GdmSignalHandler: Caught termination signal - calling fatal func * is dbus started ? * do you have any idea where this signal 15 is coming from ? (maybe check Xorg.0.log) * did you make sure your kernel complies to configuration required by consolekit ? * if so, what ck-list-sessions tells you ?