Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 414515 - gnome-base/gdm-3.2.1: no greeter shown
Summary: gnome-base/gdm-3.2.1: no greeter shown
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-03 20:41 UTC by Frank Harenberg
Modified: 2012-09-16 08:51 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info output (emerge.info,4.60 KB, text/plain)
2012-05-03 20:41 UTC, Frank Harenberg
Details
sylsog messages /var/log/messages (messages,97.44 KB, text/plain)
2012-05-03 20:42 UTC, Frank Harenberg
Details
gdm greeter log (:0-greeter.log,35.04 KB, text/plain)
2012-05-03 20:43 UTC, Frank Harenberg
Details
gdm :0-slave.log (:0-slave.log,35.66 KB, text/plain)
2012-05-03 20:45 UTC, Frank Harenberg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Harenberg 2012-05-03 20:41:16 UTC
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
Comment 1 Frank Harenberg 2012-05-03 20:41:55 UTC
Created attachment 310709 [details]
emerge --info output
Comment 2 Frank Harenberg 2012-05-03 20:42:29 UTC
Created attachment 310711 [details]
sylsog messages /var/log/messages
Comment 3 Frank Harenberg 2012-05-03 20:43:17 UTC
Created attachment 310713 [details]
gdm greeter log
Comment 4 Frank Harenberg 2012-05-03 20:45:56 UTC
Created attachment 310717 [details]
gdm :0-slave.log
Comment 5 Frank Harenberg 2012-05-04 12:16:15 UTC
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.
Comment 6 Gilles Dartiguelongue (RETIRED) gentoo-dev 2012-08-08 13:10:42 UTC
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 ?