Le dimanche 27 janvier 2013 à 19:42 +0000, Neil Williams a écrit : > gdm3 was stopped over an SSH connection using invoke-rc.d. Then I > started gdm3 from the command line (on a directly connected keyboard) > to generate endless lists of: > > gdm3[17041]: WARNING: GdmDisplay: display lasted 1.681562 seconds > gdm3[17041]: WARNING: GdmDisplay: display lasted 1.687131 seconds > gdm3[17041]: WARNING: GdmDisplay: display lasted 1.693576 seconds > > daemon/gdm-display.c : 725 > g_warning ("GdmDisplay: display lasted %lf seconds",elapsed); > > I changed the shell script to avoid the 3 second timeout (which makes > this much more manageable) and gdm3 just keeps respawning using > gdm-simple-slave, incrementing the --display-id each time.
As mentioned on IRC, there is already some code to handle GdmDisplay respawning too fast. See on_display_status_changed() in gdm-local-display-factory.c. I’m interested in logs with debugging enabled, especially stuff like “GdmLocalDisplayFactory: display status changed”. Cheers, -- .''`. Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org