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 368648 - Spurious 'preferred session type ... is not installed on this computer' message
Spurious 'preferred session type ... is not installed on this computer' message
Status: RESOLVED DUPLICATE of bug 341619
Product: gdm
Classification: Core
Component: general
2.14.x
Other All
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-01 01:36 UTC by Sam Morris
Modified: 2007-05-01 14:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Sam Morris 2006-11-01 01:36:35 UTC
Please describe the problem:
Whenever I log in I am presented with the message, 

 "Do you wish to make GDM_Failsafe.XTERM.desktop the
 default for future sessions?

 Your preferred session type Default System Session is
 not installed on this computer."

If I choose 'Just log in' then I am able to log in normally (using the default
system session).

This happens to my user after I log in once with the 'failsafe xterm'
session.

The captions on the buttons are also incorrect. 'Make default' makes the
allegedly-missing default system session the default setting, and logs
me in as normal.

Steps to reproduce:
1. create a test user
2. log in with 'failsafe xterm'
3. log out
4. log in again... the message appears


Actual results:


Expected results:


Does this happen every time?


Other information:
Forwarded from <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381239>
Comment 1 Brian Cameron 2007-02-09 06:36:10 UTC
This bug has been fixed in the latest GDM2 code.  GDM no longer will save the failsafe session as your default.
Comment 2 Loïc Minier 2007-05-01 14:14:31 UTC
(Reopening to close as dup of bug #341619.)
Comment 3 Loïc Minier 2007-05-01 14:14:51 UTC

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