Bug 129809 - switchdesk not invoking fvwm as startx does -- no .Xclient-default
switchdesk not invoking fvwm as startx does -- no .Xclient-default
Product: Fedora
Classification: Fedora
Component: switchdesk (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Depends On:
  Show dependency treegraph
Reported: 2004-08-12 16:21 EDT by Steve Friedman
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-12 16:30:29 EDT
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 Steve Friedman 2004-08-12 16:21:37 EDT
Description of problem:

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Ngo Than 2004-08-12 16:30:29 EDT
please update new version in rawhide. it should fix this problem.
Comment 2 Steve Friedman 2004-08-12 16:43:01 EDT
Hit the return key, instead of the backspace submitted form prematurely...

Description of problem:
When I switched desktops from Gnome to fvwm, and then attempted to log
in from the graphical greeter, I failed to log in because of: 
"/home/steve/.Xclients:  line 8:  /home/steve/.Xclients-default: no
such file or directory".  When I switched runlevel from 5 to 3, logged
in, and then ran startx, I got a quick message that it was creating
the necessary files, and proceeded to start properly.

Version-Release number of selected component (if applicable):
yum check-update showed up to date as of 12Aug04

How reproducible:
Happened every time.

Steps to Reproduce:
1. install fc1, yum -y update, install fvwm, fvwm-themes
2. Via switchdesk on gnome panel, select fvwm
3. In runlevel 5, always fails to start with indicated error.  In
runlevel 3, via startx, always works.
4. switch runlevel back to 5, and it still fails.
Actual results:
See error message above.

Expected results:
Enter X as appropriate.

Additional info:

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