Date: Mon, 29 Jan 2001 04:20:05 -0800 (PST) From: Trevor Johnson <trevor@jpj.net> To: freebsd-ports@FreeBSD.org Subject: Re: ports/24705: Bug concerning Xwrapper/XFree86-4.0.2 Message-ID: <200101291220.f0TCK5k54727@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/24705; it has been noted by GNATS. From: Trevor Johnson <trevor@jpj.net> To: Sebastian Reinert <sepp@saargate.de> Cc: <FreeBSD-gnats-submit@FreeBSD.ORG> Subject: Re: ports/24705: Bug concerning Xwrapper/XFree86-4.0.2 Date: Mon, 29 Jan 2001 07:17:15 -0500 (EST) > The bug occured when I was trying to start my recently installed > XFree86-4.0.2 (installed by the ports) with the little help of > Xwrapper that is delivered with the dists of xfree. > All you need to reproduce this problem is a current version of > Xwrapper with x-right, that you get by ftp for example, an account Hi, Sebastian. Looking at ftp://ftp.xfree86.org/pub/XFree86/4.0.2/source/FILES, I don't see a wrapper.c file listed. Are you using the one from an older version of XFree86? Are you using the one from x11/wrapper in the ports collection (it doesn't sound like you are)? Are you using one from another operating system? Let us know where to find it. > (e.g. telnet) and a > self-written script called .xserverrc, that contains following > phrase: > exec Xwrapper $dspnum &args > It is _very important_ that you use an "&" instead of "$" in front > of "args"! I placed the .xserverrc file in my $HOME, which is where startx usually looks for it. With the startx script I have--unmodified from the way it was installed from the XFree86-4.0.1_3 port--I get: $ startx args: not found Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file "/var/log/XFree86.". I tried making the .xserverrc read: exec startx $dspnum &args and it forked numerous times, after which I got the message: xinit: X server slow to shut down, sending KILL signal. but X kept running. Do you have a command called "args" in your path? Have you set resource limits in /etc/login.conf? By default they are turned off. > After all, you configurate your script with the typical rights (e.g. > "777"), execute "startx" (you will have x-right for it by > default), and the systems shuts down its daemons. > By the way: You do not need root-rights... > > >Fix: > > I have fixed it by reconfigure the rights of some executable files > that you can mostly find in /usr/X11R6/bin like startx, xinit or X > for example. What were the permissions originally, and what have you changed them to? -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101291220.f0TCK5k54727>