Bug 52509 - Cannot configure sawfish.
Summary: Cannot configure sawfish.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sawfish
Version: 9
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-24 15:14 UTC by lars
Modified: 2007-04-18 16:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-11-03 18:36:42 UTC
Embargoed:


Attachments (Terms of Use)
Output of rpm -qa on the system experiencing this bug. (9.66 KB, text/plain)
2001-08-27 16:08 UTC, lars
no flags Details

Description lars 2001-08-24 15:14:06 UTC
Description of Problem:

Attempts to bring up the sawfish configuration tool from the "Start Here"
window result in the error message "Sawfish is not running."  I beg to differ:

$ ps -u lars | grep sawfish
1440 ?        00:00:36 sawfish

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

sawfish-0.38-9
nautilus-1.0.4-34

How Reproducible:

See below.

Steps to Reproduce:
1. Open "start here" by clickingon the mushroom (?) button.
2. Double click on the "Preferences" icon.
3. Double click on the "Sawfish window manager" icon.
4. Double click on any of the settings categories.

The window that comes up says "sawfish isn't running."

Actual Results:


Expected Results:

You know, a configuration dialog or something.

Additional Information:

Comment 1 Glen Foster 2001-08-24 15:52:15 UTC
We (Red Hat) really need to fix this before next release.

Comment 2 Havoc Pennington 2001-08-24 17:57:08 UTC
Works on my test machine. If you log out and log back in, does it work again?

Comment 3 Havoc Pennington 2001-08-27 16:03:08 UTC
I can't reproduce, if logging out solves it most likely it was some random bogon
that won't happen again, if not then please attach the files in ~/.sawfish (or
put them up for http/ftp maybe?) and it might help reproduce...

Comment 4 lars 2001-08-27 16:07:40 UTC
Logging out and back in does not solve the problem.  This is a pretty vanilla
system; I haven't made any GUI-related configuration changes at all.  There is
nothing in ~/.sawfish but files in the "sessions" directory, which all consist
of the following:

  ;; session saved for lars
  ;; sawfish version 0.38; Wed Aug 22 06:19:46 2001

So there's really nothing to attach.

I will, just for kicks, attach the output of 'rpm -qa'.


Comment 5 lars 2001-08-27 16:08:59 UTC
Created attachment 29718 [details]
Output of rpm -qa on the system experiencing this bug.

Comment 6 Havoc Pennington 2001-08-28 18:34:50 UTC
Asked on internal mailing lists if anyone saw this problem, I can't find anyone
who can trigger this bug. There must be something weird going on...

Anything suspicious in ~/.xsession-errors?

Comment 7 Havoc Pennington 2004-11-03 18:36:42 UTC
Closing ancient bugs


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