Bug 82735

Summary: Desktop Switching Tool breaks account
Product: [Retired] Red Hat Public Beta Reporter: David White <dbwhite>
Component: switchdeskAssignee: Mike A. Harris <mharris>
Status: CLOSED WORKSFORME QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: phoebeCC: srevivo
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: 2003-02-07 11:20:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 79578    
Attachments:
Description Flags
Error text shown in dialog none

Description David White 2003-01-25 15:54:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030115

Description of problem:
Unable to login to account after using Desktop Switching Tool to switch to KDE

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


How reproducible:
Didn't try

Steps to Reproduce:
1. Use Desktop Switching Tool to select KDE, hit OK
2. Reboot machine
3. Try to login to account
    

Actual Results:  Bounced back to login screen with a dialog showing error text.

Expected Results:  Login to a KDE desktop

Additional info:  (Didn't see entry for Desktop Switching Tool; this was as
close as I could get...)

Comment 1 David White 2003-01-25 15:54:57 UTC
Created attachment 89602 [details]
Error text shown in dialog

Comment 2 Mike A. Harris 2003-02-07 11:20:52 UTC
Starting with a fresh install of the latest tree, using "startx" I was able
to start up GNOME, use it for a while to work, then ran switchdesk, set it
to KDE, then logged out of X.  I then ran "startx" and KDE came up, I
worked in it for a while, then ran switchdesk and chose GNOME, then
logged out.  I repeated this procedure 2 more times over the period of
a few hours (while testing out other users reported bugs), and was unable
to reproduce the problem you describe here.

It's possible perhaps that the problem you experienced is fixed now, or
was just some weird beta release transient.

Closing bug as WORKSFORME