Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 106376

Summary: gdm fails to start the default GNOME session
Product: [Retired] Red Hat Raw Hide Reporter: Ralf Ertzinger <redhat-bugzilla>
Component: gdmAssignee: Havoc Pennington <hp>
Status: CLOSED DUPLICATE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:58:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ralf Ertzinger 2003-10-06 16:01:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031003

Description of problem:
(Note: my default session is GNOME)

After selecting the default session (or GNOME session) in gdm, gdm displays a
message stating:

"Could not find or run the base session script, will try the GNOME failsafe
session for you."

It then successfully starts the GNOME failsafe session.
/var/log/messages shows:

gdm[4418]: gdm_slave_session_start: Cannot find or run the base Xsession script,
will try GNOME failsafe

Version-Release number of selected component (if applicable):
gdm-2.4.4.3-1

How reproducible:
Always

Steps to Reproduce:
1. Select GNOME session in gdm
2. Log in
3.
    

Actual Results:  An error message shows, and the GNOME failsafe session is started.

Expected Results:  The user's GNOME session should start

Additional info:

Comment 1 Havoc Pennington 2003-10-06 16:17:39 UTC

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

Comment 2 Red Hat Bugzilla 2006-02-21 18:58:59 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.