After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 318696 - picking previous session doesn't work after using a failsafe option
picking previous session doesn't work after using a failsafe option
Status: RESOLVED DUPLICATE of bug 341619
Product: gdm
Classification: Core
Component: general
2.8.x
Other All
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2005-10-12 17:06 UTC by Sebastien Bacher
Modified: 2006-05-15 20:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Sebastien Bacher 2005-10-12 17:06:51 UTC 
The bug has been described here: http://bugzilla.ubuntu.com/show_bug.cgi?id=17617

"If a login is made with the Failsafe Gnome session, at the next login the
following message appears, if 'Last' is selected as session:

"Your prefered session type GDM_Failsafe.GNOME.desktop is not installed in this
computer. Do you wish to make Default System session the default for future
sessions?"

And "Just Log In", "Make Default" and "Cancel" are listed as sessions, none of
which logs in to the last session (Failsafe Gnome).

The same occurs after a successful login with Failsafe terminal session (the
only difference is the reference file: GDM_Failsafe.XTERM.desktop

I'm currently running an up-to-date breezy (as of 12/10/05) updated from a Hoary
setup.
...
> Thanks for your bug. That is specific to the failsafe sessions, right? Your bug
title is confusing ....
...
Sorry, I didn't knew how to summarize the problem correctly. It happens with the
failsafe sessions only. For the problem to arise, I need to log in twice. First,
selecting one of the failsafe sessions, and second, selecting 'Last' as the
session. "
Comment 1 Brian Cameron 2006-03-11 01:35:05 UTC 
Yes, this is an annoying problem that should be fixed.  I'd accept a patch to fix it.
Comment 2 Brian Cameron 2006-05-15 20:14:11 UTC 

*** This bug has been marked as a duplicate of 341619 ***