Bug 120792

Summary: Greeter Program Crashing
Product: [Fedora] Fedora Reporter: Marcos Miranda <m_c_miranda>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 1CC: m_c_miranda, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-09-19 03:46:04 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 Marcos Miranda 2004-04-13 22:39:40 UTC
Description of problem:
Dialog "The greeter program appears to be crashing. I will attempt to
use a different one."

Version-Release number of selected component (if applicable):
gdm-2.4.4.5-1.2
redhat-artwork-0.88-1

How reproducible:
Just logging out and logging in, again.

Steps to Reproduce:
1. Log out
2. Log in
3.
  
Actual results:
Dialog "The greeter program appears to be crashing. I will attempt to
use a different one."

Expected results:
Graphical login theme (any)

Additional info:
Fresh Install via Format.
Redhat up2date to 2174 Kernel
VIA Samuel2 1GigaPro 800 MHz processor
SiS630E Chipset, 3D Graphics Accelerator

Comment 1 Marcos Miranda 2004-04-14 16:15:57 UTC
At 9:08am Wednesday April 14, 2004, I did a force re-install of the
gdm-2.4.4.5-1.2 packages, including the source.
rpm -i --force --nosignature <packagename>

I logged out, GDM screen went to the circles one.
I changed it to a different one (Glass theme, I downloaded.)
Works!
Did a complete shutdown and reboot.
GDM Glass Theme returned without error.


Comment 2 Warren Togami 2004-09-19 03:46:04 UTC
there may have been a problem with your original install, but in any
case this is not an issue anymore.

Comment 3 Hui Cao 2004-11-12 15:26:16 UTC
I just installed the FC3, however, this is error happens again.

is it solved in this release?

                   Hui.