Bug 109510 - Fedora splash screen won't disappear
Fedora splash screen won't disappear
Status: CLOSED DUPLICATE of bug 108190
Product: Fedora
Classification: Fedora
Component: gnome-session (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Mark McLoughlin
Depends On:
  Show dependency treegraph
Reported: 2003-11-08 16:18 EST by Alexandre Strube
Modified: 2007-11-30 17:10 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:59:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alexandre Strube 2003-11-08 16:18:33 EST
Description of problem: Until a user puts its login and password, the
fedora splash screen (gnome-session) won't disappear if gaim is
opening on session startup. Splash screen will come out only if you
close gaim.

Version-Release number of selected component (if applicable): standard
fedora core 1 and gaim

How reproducible: Close a session with gaim opened, and saving
settings. Open this session again.

Steps to Reproduce:
1. Open gaim.
2. Log out, saving session settings
3. Log in again.
Actual results:
Gnome-session screen does not disappear

Expected results:
this screen to disappear as soon as session is fully started.

Additional info:
Comment 1 Rasmus Back 2003-11-09 07:33:14 EST
I have gaim set to auto-login at session start and I'm also seeing
this bug. I have to click the Fedora Core session splash screen for it
to dissapear.
Comment 2 Marius Andreiana 2004-05-30 09:17:22 EDT
Same as Rasmus here, with FC2
Comment 3 Marius Andreiana 2004-06-01 07:15:47 EDT
duplicate of #108190
Comment 4 Bill Nottingham 2004-06-01 12:12:19 EDT

*** This bug has been marked as a duplicate of 108190 ***
Comment 5 Red Hat Bugzilla 2006-02-21 13:59:52 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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