Bug 169658 - The greeter application appears to be crashing.
The greeter application appears to be crashing.
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: gdm (Show other bugs)
rawhide
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-09-30 14:14 EDT by David Bentley
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: updates 4/10/05
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-10-05 17:20:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David Bentley 2005-09-30 14:14:04 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.8b4) Gecko/20050915 Fedora/1.5-0.5.0.beta1 Firefox/1.4

Description of problem:
When typing in the user name and pressing <CR> the scrteen goes blank and asks 
for username again which when supplied has the same effect except that when the
video returns the login screen is replaced by a dialogue box saying "The greeter application appears to be crashing. Attempting to try another one" this one does
work as expected.

When loging out you get a similar message.



Version-Release number of selected component (if applicable):
gdm-2.8.0.4-3 and a few previous incarnations

How reproducible:
Always

Steps to Reproduce:
1. See above
  

Actual Results:  See description.

Expected Results:  gdm should work as it does on my other system also running RAWHIDE

Additional info:

The system that fails is a twin XEON with 1024 meg of ram on an Intel SE7505VB2
mother board usimg a RADEON 9800 PRO video card (fails with both normal and SMP
kernels)

The one that works is K6 III on an Asus P5a with 384 meg of ram and a MATROX
G400 video card.
Comment 1 David Bentley 2005-10-05 17:20:18 EDT
The reported problem has gone away after the 4th of October updates one of which
has fixed things.

Note You need to log in before you can comment on or make changes to this bug.