Bug 82735 - Desktop Switching Tool breaks account
Desktop Switching Tool breaks account
Product: Red Hat Public Beta
Classification: Retired
Component: switchdesk (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
Jay Turner
Depends On:
Blocks: 79578
  Show dependency treegraph
Reported: 2003-01-25 10:54 EST by David White
Modified: 2015-01-07 19:03 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-07 06:20: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)
Error text shown in dialog (210 bytes, text/plain)
2003-01-25 10:54 EST, David White
no flags Details

  None (edit)
Description David White 2003-01-25 10:54:08 EST
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 10:54:57 EST
Created attachment 89602 [details]
Error text shown in dialog
Comment 2 Mike A. Harris 2003-02-07 06:20:52 EST
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

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