Re: Was there ever a fix for Sawmill not coming up as a user?

[Rebecca Ore <rebecca ogoense net>]

On Fri, 04 Aug 2000, 1stFlight ! wrote:

> Certainly was... here's the repost. Please read the entire message as your
> installation my vary, but the overall structure and fix action should remain
> the same. For any questions feel free to email me personally.

I read this earlier.  

I uninstalled the helix saw-mill and tried the rpms on the sawmill
site.  I chmod'ed the DOC file.  

The only thing that worked for *me* was rebuilding all relevant
packages - including the two supporting libraries and adding one other
package required by one of the libs - from source rpms.

> 
> 
> Darryl
> 
> My path with the helix update on redhat 6.0 is
> /usr/libexec/sawfish/0.30.2/i686-pc-linux-gnu/DOC, but that did it.
> Thanks so much.
> 
> Gary
> 
> 
> On Sat, 29 Jul 2000, you wrote:
> > While searching the sawfish site I came across this workaround. Tried it
> > and so far its fixed the problem.  One thing in that path where it says
> > "~/0.30.3/i386-redhat-linux/DOC " change that to
> > "~/0.30.2/i386-redhat-linux/DOC" if you're running the latest helix
> > version of sawfish.  Best luck

Neither of these versions from rpms would run for user on my system.
I tried both.  

Where in the path should this have been changed?  Especially when I
had removed the helix-code 0.30.2 version and installed the 0.30.3
from the sawfish site (which did not complain, by the way, of the
earlier versions of rep-gtk and librep as I might have expected if
those were the problems).

Rebuilding the whole set of packages worked.

> >
> > " I don't know what the real solution is, but someone was kind enough to
> >
> > send me the following:
> >
> > >just wanted to let you know how to work around
> > >that annoying little bug (in case you're still
> > >looking for a quick'n dirty workaround)
> > >
> > >just do a chmod 666 on
> > >/usr/libexec/sawfish/0.30.3/i386-redhat-linux/DOC

Doing this didn't help.

Doing this to the 0.30.3 sawmill from rpms didn't help either.



> > I did this and it seems to work.
> >
> > If someone knows what the real problem or solution
> > is (an installation problem?) I would love to hear
> > from you.  Otherwise, this has worked for me and
> > it might help someone else browsing these archives.

Rebuilding from source rpms fixed the problem.


-- 
Rebecca Ore
http://www.ogoense.net