Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Aug 2005 08:24:26 -0700 (PDT)
From:      modelt20@canada.com
To:        modelt20@canada.com
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Users unable to select their own window manager in X.
Message-ID:  <20050829152427.27884.fh041.wm@smtp.sc0.cp.net>

next in thread | raw e-mail | index | archive | help
Anyone have an idea on which dependent files to look at?
Thanks

On Mon, 29 Aug 2005 07:17:38 -0700 (PDT),
modelt20@canada.com wrote:

> 
> Hello Kevin:
> 
> Thank you for your input. 
> 
> The permissions on fvwm2 are:
>  -r-xr-xr-x  1 root  wheel  355452 Aug 26 10:13
> /usr/X11R6/bin/fvwm2*
> 
> It appears the fvwm2 has been upgraded; and its one
(or
> more) of the dependent files that is causing the
issue.
> 
> Thanks.
> 
> >
> On Mon, 29 Aug 2005 08:45:18 -0500, Kevin Kinsey
wrote:
> 
> > 
> > modelt20@canada.com wrote:
> > 
> > >Hello All:
> > >
> > >Last week, I did a CVSup on all ports, and then
did a
> > >portupgrade over the weekend. The portupgrade
> completed
> > >successfully, without significant errors.
> > >
> > >Now, normal users are no longer able to set their
own
> > >window manager (e.g. fvwm2) in X, but logging in as
> > >root, I can. The user's .xinitrc file has not
changed
> > >recently, but when the user launches X, all they
get
> is
> > >the grey hatched background with a black X for the
> > >mouse pointer. No windows (clock, mail, task panel,
> > >etc) appear. If I rename the user's .xinitrc file
and
> > >then start X, the standard 'xterm' window manager
> > >loads. As root, the fvwm2 window manager loads
fine.
> It
> > >appears the portupgrade changed a permissions
setting
> > >somewhere, but beings this ran over the weekend, I
> > >don't know what setting got changed.
> > >  
> > >
> > 
> > What do the logs say?
> > 
> > In one line of thought, it sure sounds as if
whatever
> > wm they are calling isn't there any longer, or, more
> > likely,
> > encounters an error and hangs.  Obviously the X
> > server is starting, and the wm isn't.  Again, logs
or
> > stderr (switch to ttyv0 and read console) might
give a
> > clue.
> > 
> > The "standard 'xterm' window manager" is twm, and
> > is started in the abscence of the user's .xinitrc by
> > (most likely) /usr/X11R6/lib/X11/xinit/xinitrc.
> > 
> > And, it might be a permissions issue, but I can't
tell
> > by your description.  FWIW, here's the permissions
> > on my fvwm2:
> > 
> > [587] Mon 29.Aug.2005 8:37:46
> > [kadmin@archangel][/usr/X11R6/lib/X11/xinit]
> > # ll /usr/X11R*/bin/fvwm2
> > -r-xr-xr-x  1 root  wheel  355452 Jun 23 21:29
> > /usr/X11R6/bin/fvwm2*
> > 
> > More likely, it's not permissions on this file
itself,
> > though,
> > but some dependant object instead.....
> > 
> > HTH,
> > 
> > Kevin Kinsey
> > _______________________________________________
> > freebsd-questions@freebsd.org mailing list
> >
>
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to
> > "freebsd-questions-unsubscribe@freebsd.org"
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
>
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050829152427.27884.fh041.wm>