summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* settings: print custom.conf at startupRay Strode2015-03-061-0/+8
| | | | This makes it clear what settings gdm is using.
* manager: add more debug spewRay Strode2015-03-061-0/+4
|
* display: add more debug spewRay Strode2015-03-061-0/+8
|
* display: include seat in debug messageRay Strode2015-03-061-4/+6
| | | | | This will help make it more clear why autologin goes one way or the other.
* Updated Slovak translationDušan Kazik2015-03-051-19/+19
|
* Updated Korean translationChangwoo Ryu2015-03-051-153/+110
|
* Updated Slovenian translationMatej Urbančič2015-03-031-162/+160
|
* Updated Serbian translationМирослав Николић2015-03-032-324/+328
|
* configure: bump to 3.15.91.23.15.91.2Ray Strode2015-03-031-1/+1
|
* NEWS: update for releaseRay Strode2015-03-031-0/+6
|
* worker: fix hang on logoutRay Strode2015-03-031-2/+2
| | | | | | | | We need to retake control of VT switch processing on logout, just as we do before login, otherwise we can be left hung waiting for the VT to be released. https://bugzilla.gnome.org/show_bug.cgi?id=745217
* worker: drop mode_fixed variableRay Strode2015-03-031-5/+4
| | | | | | it's unused. https://bugzilla.gnome.org/show_bug.cgi?id=745217
* data: drop caribou autostart fileRay Strode2015-03-032-9/+0
| | | | | | | It's no longer needed and it makes assumptions about install location. https://bugzilla.gnome.org/show_bug.cgi?id=740788
* configure: bump to 3.15.91.13.15.91.1Ray Strode2015-03-021-1/+1
|
* NEWS: update for releaseRay Strode2015-03-021-0/+6
|
* display: drop set_up_greeter_session functionRay Strode2015-03-023-20/+22
| | | | | | | | The function is ill named and ill placed. It really just returns the username of the client that's allowed to connect to the display. This commit moves the function to gdm-manager.c
* Updated Polish translationPiotr Drąg2015-03-021-165/+115
|
* worker: fix hang in VT_WAITACTIVERay Strode2015-03-021-6/+46
| | | | | | | | | | When plymouth deactivates it correctly leaves the display in GRAPHICS mode but incorrectly stops processing VT changes. This combination of VT_AUTO + KD_GRAPHICS makes VT switches hang. Deal with the situation on our side until plymouth is fixed. https://bugzilla.gnome.org/show_bug.cgi?id=745465
* worker: don't use SIGUSR1 for VT switch signalRay Strode2015-03-021-2/+2
| | | | | | | | | | | | That signal is blocked when the worker is forked, because the main daemon uses it to notice when the X server is ready. This commit changes the worker to use real-time signals instead, which are better anyway, since they queue. https://bugzilla.gnome.org/show_bug.cgi?id=745465
* worker: split VT_SETMODE handling to helper functionRay Strode2015-03-021-9/+19
| | | | | | | We're going to call it in more than one place in the code, so it's better to keep it in a separate function. https://bugzilla.gnome.org/show_bug.cgi?id=745465
* worker: drop inaccurate FIXMERay Strode2015-03-021-10/+0
| | | | | | | I think the problem is really just the terminal getting stuck in KD_GRAPHICS/VT_AUTO mode by plymouth. https://bugzilla.gnome.org/show_bug.cgi?id=745465
* configure: bump to 3.15.913.15.91Ray Strode2015-02-271-1/+1
|
* NEWS: update for releaseRay Strode2015-02-271-0/+9
|
* session-worker: add FIXMERay Strode2015-02-271-0/+10
| | | | Document a hang that I need to deal with in the near term.
* manager: fix up spacingRay Strode2015-02-271-2/+2
|
* daemon: make sure autologin display starts on initial vtRay Strode2015-02-271-1/+3
|
* display: improve autologin debug messageRay Strode2015-02-272-6/+13
|
* manager: reset session-type for autologinRay Strode2015-02-271-0/+1
| | | | | If we're doing an autologin we don't want to inadvertently do wayland for X11 sessions, so make sure to reset it.
* systemd: import language into daemon environmentRay Strode2015-02-272-0/+2
| | | | | | | | | By default GDM is started with a pretty blank environment. This commit makes sure that the default locale for the system is used. https://bugzilla.gnome.org/show_bug.cgi?id=745286
* session: more debug spewRay Strode2015-02-271-0/+5
| | | | | This time explain why the display mode that's getting picked, is getting picked.
* worker: setuid after taking control of ttyRay Strode2015-02-271-13/+13
| | | | | This ensures we the session is always given the tty.
* worker: add some debug messagesRay Strode2015-02-271-3/+11
| | | | | This will make it clear what VT we're on, and whether or not the session has control of the tty..
* display: invert g_warn_if_fail conditionalsRay Strode2015-02-271-2/+2
| | | | | | I got them inverted in my head when I did commit 678ac9657d3166dcdeadbccb7ad9427ba0677339
* worker: force KD_GRAPHICS mode before doing VT switchRay Strode2015-02-271-2/+48
| | | | | | | | | | | If we switch VTs when in KD_TEXT mode there's obvious flicker. This commit addresses that problem by going to KD_GRAPHICS mode before switching VTs. Ideally, we wouldn't switch VTs at all, and instead leave it up to the display servers to manage via logind. At the moment, the display servers don't use logind properly, though, so do this as a stop gap. https://bugzilla.gnome.org/show_bug.cgi?id=745031
* session: jump to VT up front for X sessionsRay Strode2015-02-271-3/+4
| | | | | | | | | | | | | | | | It turns out that in order for X to work without being run as root, it needs to have its VT be active at start up. This is because it bails out of some of its logind codepaths if it gets given a "paused" device by logind, and then sometimes fails in its fallback code paths as it races to open /dev/dri/card0 while logind is still giving the user permissions to it. As a workaround, until X is fixed, this commit jumps to the VT up front before starting X. That adds flicker, which we'll address in a follow up commit. https://bugzilla.gnome.org/show_bug.cgi?id=745031
* session: reset session type to default when selecting non-wayland sessionRay Strode2015-02-261-0/+2
| | | | | | | | | | If we select a non-wayland session we need to clear the session type, or it will linger as a wayland session if it was one previously. Prevents users from getting logged into an X session when with XDG_SESSION_TYPE=wayland. https://bugzilla.gnome.org/show_bug.cgi?id=745235
* session: add more debug spew about session typeRay Strode2015-02-261-0/+6
| | | | | | | This should give a clearer picture about what session type is getting picked when. https://bugzilla.gnome.org/show_bug.cgi?id=745235
* session: move some debug spew aroundRay Strode2015-02-261-7/+9
| | | | | | | | We end up printing "looking for session file" a bunch of times in the log with no indication why. This commit drops the message and instead adds messages to the callers. https://bugzilla.gnome.org/show_bug.cgi?id=745235
* manager: quit plymouth laterRay Strode2015-02-261-6/+6
| | | | | | | We don't want to quit plymouth until the display is managed, so there's no chance of flicker. https://bugzilla.gnome.org/show_bug.cgi?id=745234
* display: turn some assertions into warningsRay Strode2015-02-261-4/+4
| | | | | | It's clear there's a bug if they're hit, but we shouldn't tank, since it's not a fatal bug.
* manager: finish displays even if they're unmanagedRay Strode2015-02-251-4/+2
| | | | | | | Some displays may be PREPARED, but not yet MANAGED. Those need to be finished at finalize time too. Fixes an assertion failure crash in some cases.
* configure: bump to 3.15.90.53.15.90.5Ray Strode2015-02-241-1/+1
|
* NEWS: update for releaseRay Strode2015-02-241-0/+8
|
* Revert "defaults: disable InitialSetup for now"Ray Strode2015-02-241-1/+1
| | | | | | | | This reverts commit 2d089ea6f5c123f8ad67fcab964e9ca8bd58b7ad. It's working again. https://bugzilla.gnome.org/show_bug.cgi?id=745139
* manager: fix initial-setup -> user session transitionRay Strode2015-02-241-2/+72
| | | | | | | | | | | | | | | | | | | After the user goes through initial setup, the initial setup program logs the user in. Nowadays, this user session starts on a new X server. The problem is, we also need the initial setup X server to go away, and we need the login screen wayland server to come up, all around the same time. You can't quit one X server on a seat while starting another one up, it doesn't like that, so there's caos, X server segfaults, and unpredictable behavior as to "which session wins". This commit fixes the problem by waiting until the greeter login screen X server is started before starting the user session. This way they don't stomp on each other's toes, and the user session ends up in the foreground. https://bugzilla.gnome.org/show_bug.cgi?id=745139
* manager: move definition of StartUserSessionOperation upRay Strode2015-02-241-8/+11
| | | | | | We're going to call it higher in the code, so move it up a bit https://bugzilla.gnome.org/show_bug.cgi?id=745139
* local-display: don't use wayland with gnome-initial-setupRay Strode2015-02-241-0/+12
| | | | | | | | | | | We haven't yet decided to use gnome-initial-setup on wayland. Before we can, we need to create a wayland based session file for it anyway. This commit makes sure we properly fall back to X11 for gnome-initial-setup. https://bugzilla.gnome.org/show_bug.cgi?id=745139
* Updated French translationAlexandre Franke2015-02-241-166/+163
|
* Updated Ukrainian translationDaniel Korostil2015-02-241-157/+155
|
* Updated Kazakh translationBaurzhan Muftakhidinov2015-02-241-162/+159
|
View Lorry Controller Status