Bug 75198 - Splash screen wont go away if nautilus isn't set to drawing the desktop
Summary: Splash screen wont go away if nautilus isn't set to drawing the desktop
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-session
Version: 8.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mark McLoughlin
QA Contact: Jay Turner
URL:
Whiteboard:
: 76160 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-05 11:17 UTC by Henrik Brix Andersen
Modified: 2015-01-08 00:00 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-01-08 05:20:33 UTC
Embargoed:


Attachments (Terms of Use)

Description Henrik Brix Andersen 2002-10-05 11:17:57 UTC
Description of Problem:


Version-Release number of selected component (if applicable):
nautilus-2.0.6-6

How Reproducible:
Every time

Steps to Reproduce:
1. Login with gdm
2. Open nautilus by choosing "GNOME Menu/Home Folder"
3. Choose nautilus menu "Edit/Preferences"
4. Click "Desktop and Trash"
5. Uncheck "Use Nautilus to draw the desktop"
6. Close all open windows
7. Logout
8. At next login the splash screen wont go away unless you re-select the 
   previously unchecked checkbox

Actual Results:
Splash screen hangs

Expected Results:
Splash screen should go away and no icons should be shown on desktop

Additional Information:

Comment 1 Brent Fox 2002-10-10 20:51:27 UTC
This works fine for me with at fresh install of 8.0.  I followed your steps exactly.

Comment 2 Henrik Brix Andersen 2002-10-11 14:11:43 UTC
Odd - I can not reproduce it anymore either.

Comment 3 Havoc Pennington 2002-11-05 18:51:38 UTC
There's one other bug report of splash screen getting stuck.

Comment 4 Havoc Pennington 2003-01-08 05:20:33 UTC
I haven't seen any recent reports of this, so let's assume fixed pending further
reports.

Comment 5 Havoc Pennington 2003-01-08 05:22:47 UTC
*** Bug 76160 has been marked as a duplicate of this bug. ***


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