summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* session: make sure greeter is GNOME session even if gnome isn't installedRay Strode2016-01-211-9/+15
| | | | | | | | | | | | | | | We figure out the XDG_CURRENT_DESKTOP by looking at the session that's use for login. For the greeter, we don't use a session, at all, but instead a directly specified program. Still, we're determining the XDG_CURRENT_DESKTOP for the greeter based on what default session gets picked. On KDE only setups, the greeter will get marked as a KDE session which will prevent gnome-settings-daemon from starting properly. This commit changes the code so that greeter sessions, don't rely on the default session desktop file. https://bugzilla.gnome.org/show_bug.cgi?id=760943
* Updated Russian translationStas Solovey2016-01-191-48/+49
|
* Updated German translationMario Blättermann2016-01-181-92/+35
|
* build: fix help string for --with-groupMichael Catanzaro2016-01-181-2/+2
| | | | | | Another great contribution to free software. ;) https://bugzilla.gnome.org/show_bug.cgi?id=760389
* session-worker: Remove obsolete FIXMEMichael Catanzaro2016-01-181-1/+0
| | | | | | | | | This comment led me on a bit of a wild goose chase, thinking that it is possible for an ActUser to never load. Nowadays it will always load, even if the username does not exist, and no further changes are required in gdm. See fdo#66325. https://bugzilla.gnome.org/show_bug.cgi?id=760401
* Update gsettings descriptions for login screen logo settingsMichael Catanzaro2016-01-181-6/+4
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=760495
* Remove [greeter] section from custom.confMichael Catanzaro2016-01-131-2/+0
| | | | | | There are no greeter options anymore https://bugzilla.gnome.org/show_bug.cgi?id=760589
* launch-environment: Run gnome-session from PATHMichael Catanzaro2016-01-121-1/+1
| | | | | | | | Don't assume that gnome-session and gdm happen to be installed to the same location. This makes it easier to e.g. run gdm from /usr/local without installing gnome-session there as well. https://bugzilla.gnome.org/show_bug.cgi?id=760406
* session: Crash better when no sessions are installedMichael Catanzaro2016-01-121-0/+4
| | | | | | | | If no session desktop file can be found in the search path, we are doomed. Crash nicely with g_error rather than continuing on to call g_sequence_get with an invalid GSequenceIter. https://bugzilla.gnome.org/show_bug.cgi?id=760548
* session: explain rationale between display modes and simplify getterRay Strode2016-01-121-19/+20
| | | | | | | | | | | | | gdm_session_get_display_mode is longer and more confusing than it needs to be. This commit, consolidates code paths together and adds a more descriptive comment explaining why NEW_VT display mode is used for everything but non-seat0 seats. Based on a patch and bug report by Michael Catanzaro <mcatanzaro@gnome.org> https://bugzilla.gnome.org/show_bug.cgi?id=760415
* daemon: don't build wayland support when disabledFrederic Crozat2016-01-121-1/+11
| | | | | | | Ensure all wayland relevant code is disable when wayland is disabled at compile time. https://bugzilla.gnome.org/show_bug.cgi?id=760518
* Updated Lithuanian translationAurimas Černius2016-01-101-53/+32
|
* daemon: fix code style in previous commitMichael Catanzaro2016-01-051-1/+1
| | | | | Ray asked me to change this on Bugzilla, but I didn't look at Bugzilla before I pushed it.
* launch-environment: disable gvfs except in initial setup modeMichael Catanzaro2016-01-051-0/+7
| | | | | | | gnome-initial-setup needs gvfs for remote avatar lookup. The greeter does not. https://bugzilla.gnome.org/show_bug.cgi?id=725584
* session-worker: Don't override prompt from PAM when setting new passwordMichael Catanzaro2016-01-051-1/+0
| | | | | | | | | | | | | | | During the PAM authorize step, if pam_acct_mgmt returns PAM_NEW_AUTHTOK_REQD, gdm displays the message "Your password has expired, please change it now." But pam_unix has already displayed the message "You are required to change your password immediately (root enforced)." This causes the message from PAM to flash very briefly on the screen, then be replaced by the message from gdm. The user will be confused by the disappearing message. There's no value in gdm presenting its own message here, since the message from PAM is fine. https://bugzilla.gnome.org/show_bug.cgi?id=758571
* 3.19.23.19.2Matthias Clasen2015-12-161-0/+11
|
* Updated Swedish translationSebastian Rasmussen2015-11-191-3/+14
|
* Updated Scottish Gaelic translationGNOME Translation Robot2015-11-161-37/+29
|
* session: Cancel worker proxy async ops when freeing conversationsRui Matos2015-11-151-13/+23
| | | | | | | | We need to cancel ongoing async ops for worker proxies when freeing conversations or we'll crash when the completion handler runs and we access free'd memory. https://bugzilla.gnome.org/show_bug.cgi?id=758032
* session: disconnect signals from worker proxy when conversation is freedRay Strode2015-11-151-1/+22
| | | | | | | We don't want an outstanding reference on the worker proxy to lead to signal handlers getting dispatched after the conversation is freed. https://bugzilla.gnome.org/show_bug.cgi?id=758032
* configure: bump to 3.19.2Ray Strode2015-11-101-1/+1
| | | | | Not releasing yet, but I want to do a git snapshot with a reasonable version number.
* Add Arch Linux PAM config filesJan Alexander Steffens (heftig)2015-11-108-2/+88
|
* Use -listen instead of -nolisten for new XorgNathaniel Roach2015-11-103-0/+33
| | | | | | | | | | | | | | | | Newer Xorg versions don't listen to tcp sockets by default, so instead of explicitly passing -nolisten to disable tcp sockets by default, we need to explicitly pass -listen to enable tcp sockets when DisallowTCP=false. Older versions don't support the -listen flag, so we check the version and if it's >= 1.17 then we specify -listen tcp Signed-off-by: Nathaniel Roach <nroach44@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=750026
* Updated POTFILES.inPiotr Drąg2015-11-101-2/+0
|
* manager: don't use wayland for autologin if wayland disabledRay Strode2015-11-091-2/+13
| | | | | | | | | | | | | These days we default to using wayland user sessions if the unless greeter isn't wayland. But in the case of automatic login there is no greeter. This commit makes automatic login ignore wayland sessions if wayland is disabled in the config file. This gives us symetry with the greeter case, and provides a way for users to opt out of wayland. https://bugzilla.gnome.org/show_bug.cgi?id=757715
* session: always update session type when reading saved sessionRay Strode2015-11-091-2/+2
| | | | | | | | We previously only did it if the session name was different, but now it's possible to have sessions of both types with the same name. https://bugzilla.gnome.org/show_bug.cgi?id=757715
* launch-environment: always use "gnome" session nowRay Strode2015-11-091-5/+0
| | | | | | | gnome-wayland isn't a thing anymore, wayland just uses the same session name. https://bugzilla.gnome.org/show_bug.cgi?id=757715
* session: give wayland sessions priorityRay Strode2015-11-091-7/+6
| | | | | | | If two sessions have the same name, give the wayland one priority, unless wayland sessions are being ignored. https://bugzilla.gnome.org/show_bug.cgi?id=757715
* data: drop override xsession filesRay Strode2015-11-093-23/+1
| | | | | | | | We now tell gnome-shell to use GDM mode a different way so we don't need to override the desktop files anymore. https://bugzilla.gnome.org/show_bug.cgi?id=757715
* launch-environment: set shell session mode in environmentRay Strode2015-11-091-0/+32
| | | | | | | | | | Right now we explicitly pass --mode=gdm to gnome-shell via a complicated set of overridden desktop files. This commit instead sets GNOME_SHELL_SESSION_MODE so we can just use the stock files. https://bugzilla.gnome.org/show_bug.cgi?id=757715
* manager: filter out wayland user sessions if X11 login screenRay Strode2015-11-061-1/+15
| | | | | | | | | | We use wayland by default on the login screen, so if we're running in an X11 session, then the presumption is that we're incapable of using wayland. If we're incapable of using wayland sessions then we should ignore wayland sessions read from user configuration and fall back to non-wayland defaults. https://bugzilla.gnome.org/show_bug.cgi?id=757715
* session: add property for ignoring wayland sessionsRay Strode2015-11-062-1/+47
| | | | | | | | | | | We're going to want to be able to exclude wayland sessions from the search path if the manager deems it necessary. This commit adds a property to GdmSession to give the manager that ability. https://bugzilla.gnome.org/show_bug.cgi?id=757715
* session: route GdmSession "self" object into some functionsRay Strode2015-11-061-18/+22
| | | | | | | | We're going to need to look at session state in the future. This commit preps the way forward, for that by, making sure the state object is available. https://bugzilla.gnome.org/show_bug.cgi?id=757715
* libgdm: filter out wayland sessions from X11 login screenRay Strode2015-11-061-0/+4
| | | | | | | | | | | | | We use wayland by default on the login screen, so if we're running in an X11 session, then the presumption is that we're incapable of using wayland. If we're incapable of using wayland sessions then we shouldn't present those sessions to the user in the session list either. This commit makes sure to avoid showing wayland based sessions in the session list if the login screen is running on X11. https://bugzilla.gnome.org/show_bug.cgi?id=757715
* libgdm: refactor session list handling codeRay Strode2015-11-061-4/+14
| | | | | | | | | | This commit splits the code for getting sessions up into two chunks: xorg and wayland. This is necessary because future commits will treat xorg and wayland sessions differently. https://bugzilla.gnome.org/show_bug.cgi?id=757715
* local-display-factory: don't sweat hardcoding seat0 for transient displaysRay Strode2015-11-061-12/+1
| | | | | | seat0 is the only thing that has a chance of supporting multiple sessions at th moment, so drop the FIXME that we won't be making traction on.
* local-display-factory: drop obsolete FIXMERay Strode2015-11-061-2/+0
|
* Xsession: get rid of "custom" sessionRay Strode2015-11-063-24/+0
| | | | | | | | | | | | custom is a magic name we used to allow for having the user decide their session by a ~/.xsession file. We no longer support that construct and haven't for many years. Instead, users who want that functionality can just add a xsession file to accomplish it. This commit just removes some left over cruft that never got cleaned up.
* xdmcp-display: this shouldn't be an abstract typeRay Strode2015-11-061-1/+1
| | | | | | | We instantiate it directly, so make it a normal type. https://bugzilla.gnome.org/show_bug.cgi?id=757714
* get rid of references to slavesRay Strode2015-10-27136-118361/+20839
| | | | | | | | I really don't want $ git grep slave to return hits.
* INTERNALS: dropRay Strode2015-10-271-83/+0
| | | | it's wrong and stuff
* Revert "gdm-session: emit verification-complete even for logins"Ray Strode2015-10-261-7/+8
| | | | This reverts commit 76e2a54a1ef6cb8783844ce11efcf694e220a840.
* gdm-session: emit verification-complete even for loginsRay Strode2015-10-201-8/+7
| | | | | | | | | | Right now we only emit verification-complete when the a user successfully reauthenticates. We should also do it when they successfully initially authenticate. This commit fixes that. https://bugzilla.gnome.org/show_bug.cgi?id=754814
* configure: bump to 3.18.03.18.0Ray Strode2015-09-211-1/+1
|
* NEWS: update for releaseRay Strode2015-09-211-0/+5
|
* Updated French translationAlexandre Franke2015-09-201-6/+6
|
* configure: update to 3.17.923.17.92Ray Strode2015-09-161-1/+1
|
* NEWS: update for releaseRay Strode2015-09-161-0/+6
|
* display: don't complain if we dispose PREPARED displayRay Strode2015-09-141-1/+0
| | | | | | | | It's expected now that we may dispose a display when it's prepared (if it was prepared but then we determined we were going to autologin instead). https://bugzilla.gnome.org/show_bug.cgi?id=749418
* manager: only claen up stub greeter display if it's actually a stubRay Strode2015-09-141-4/+6
| | | | | | | | | | | | | | | | commit 2774c7e43b9fdf5e5e59ef1f53ae7ba29f4aa23c fixed a leak in the case we're doing autologin, but it also unconditionally cleans up the display in the non-autologin case, too. At the moment, we don't want to clean up the greeter in that case, since it causes unnecessary flicker and slows down fast user switching. ( though this behavior may get changed again pending the outcome of bug 747339 ) This commit makes sure we only clean up the leaker greeter display, if there is a leaked greeter display (namely, the autologin case) https://bugzilla.gnome.org/show_bug.cgi?id=749418
View Lorry Controller Status