Bug 122299 - switchdesk fails to run at all on x86_64
switchdesk fails to run at all on x86_64
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: switchdesk (Show other bugs)
rawhide
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-05-02 15:51 EDT by Chuck Mead
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-05-03 07:59:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chuck Mead 2004-05-02 15:51:34 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.6)
Gecko/20040312

Description of problem:
switchdesk craps out as soon as you try to run it. I know some people
have been reporting troubles with it on the mailing list but they're
saying they've gotten it to run at least once. I cannot get it to run
at all.

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

How reproducible:
Always

Steps to Reproduce:
1. run switchdesk from the menu or the commandline
2. it fails
3.
    

Actual Results:  switchdesk did not run at all.

Expected Results:  it should have given me my desktop options.

Additional info:

[root@stealth root]# switchdesk
Red Hat Linux switchdesk 4.0
Copyright (C) 1999-2004 Red Hat, Inc
Redistributable under the terms of the GNU General Public License
Traceback (most recent call last):
  File "/usr/share/switchdesk/switchdesk-gui.py", line 36, in ?
    from backend import *
  File "/usr/share/switchdesk/backend.py", line 18
    PROGNAME = @NAME@
               ^
SyntaxError: invalid syntax
Comment 1 Ngo Than 2004-05-03 07:59:21 EDT
it's already fixed in 4.0.3-1, which should be available in rawhide
now. Thanks for your report

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