| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ConsoleKit has code to try to prevent switching to the same session
that the slave is running on. That code was important when we created
a new throw-away session and slave as part of the user switching process.
These days we connect to the already running slave instead of using a
new one, and that vestigal code gets in the way, breaking user
switching.
This commit removes that harmful code.
https://bugzilla.gnome.org/show_bug.cgi?id=684594
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This is a backport from exherbo changes by Saleem Abdulrasool <compnerd@compnerd.org>
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
GdmSession::session-died and GdmSession::session-exited cause the simple
slave to stop, closing thus also the session, which would then walk all
conversations and free them. But the conversation is already freed at
the end of the worker-exited / worker-died handlers.
https://bugzilla.gnome.org/show_bug.cgi?id=684326
|
|
|
|
|
|
|
|
| |
The conversation is freed at the end of that callback, so the pointer
would be dangling. Among other things, this fixes a duplicate wtmp record,
as session dispose would find that logout was already recorded.
https://bugzilla.gnome.org/show_bug.cgi?id=684326
|
|
|
|
|
|
|
|
| |
Due to the way methods are handled by GDBus, it's possible we get a
method invocation after the worker has already exited and the conversation
freed.
https://bugzilla.gnome.org/show_bug.cgi?id=684326
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
We were a little to excited about memory clean up in
x11_session_is_on_seat
This commit fixes that and the subsequent crashes.
|
|
|
|
|
| |
Don't bother creating a child watch if we're about to fail anyway.
Don't exit from gdm-server.c, we do clean up from gdm-simple-slave.c
|
| |
|
|
|
|
| |
Closes #684081
|
|
|
|
|
|
|
| |
gdm-autologin must reference common-account, not common-auth, otherwise no
module is loaded and the account phase fails.
https://bugzilla.gnome.org/show_bug.cgi?id=684057
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reauthentication sessions depend on having the same environment
as the session they were initiated from. This is important to
make sure login prompts are in the right language, to make sure
the kerberos credentials cache is looked up, and for various
other reasons.
This commit copies the environment from the login session to
any new reauthentication sessions that get started after login.
https://bugzilla.gnome.org/show_bug.cgi?id=684241
|
|
|
|
|
|
|
|
|
| |
The conversation-started message said "stopped" and the
conversation-stopped message said "started"
This commit flips 'em.
https://bugzilla.gnome.org/show_bug.cgi?id=684241
|
|
|
|
| |
<liverig@gmail.com>.
|
| |
|
|
|
|
|
|
|
| |
It's an issue that comes up over and over again.
Give in to the peer pressure and allow root login
by default. We warn in gnome-session now anyway.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
For OSTree, I'm trying to move components to a model where they
automatically create whatever directories/files are needed in /var.
This helps with upgrade/downgrade scenarios.
In GDM's case, this is pretty easy to do because we start with full
root privileges.
https://bugzilla.gnome.org/show_bug.cgi?id=630485
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
First, we can't call a lot of this stuff inside a
GSpawnChildSetupFunc; for example, g_warning() can try to lock a
mutex; if another thread happened to be holding that mutex from before
we forked, we'd deadlock. Thus, it needed to be extracted.
Second, just drop the group-name property; nothing was using it, and
it complicated the code.
Third, the error handling was totally inconsistent and ugly; sometimes
we would g_warning, other times we'd re-throw to the caller, other
times we'd do both. Clean this up by consistently propagating errors
up until the first public API that doesn't take a GError.
https://bugzilla.gnome.org/show_bug.cgi?id=630485
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This will allow clients such as gnome-shell to do runtime detection
of gdm and fallback gracefully if not available.
https://bugzilla.gnome.org/show_bug.cgi?id=683790
|
|
|
|
|
| |
GdmManager is a GdmDBusManagerSkeleton, so it must include that at
the beginning of the instance and class structures.
|
| |
|