On 01/10/03 11:20 PM, Dan Espen sat at the `puter and typed:
> Louis LeBlanc <fvwm_at_keyslapper.org> writes:
> > On 01/10/03 12:56 PM, Dan Espen sat at the `puter and typed:
> > > Louis LeBlanc <fvwm_at_keyslapper.org> writes:
> > > > Hey all. I've been away for some time (got my fvwm config tweaked
> > > > just where I wanted it) and now something has happened.
> > > >
> > > > I recently upgraded to fvwm2.4.14 on FreeBSD, but hadn't gotten around
> > > > to restarting the system yet. Then last night, we lost power for
> > > > awhile, and when it came back, the system came up great - except for X
> > > > and Fvwm.
> > > >
> > > > I narrowed down and solved most of the problems, but now I have Fvwm
> > > > starting with my usual desktop and menus, but the menus and any exec
> > > > hotkeys don't seem to work. Any time I try to exec something from the
> > > > menus, I simply get a message in the log that says:
> > > > Abort trap
> > > >
> > > > and that's it. Nothing else.
> > >
> > > Something is calling the abort() function.
> > >
> > > Since Fvwm is still running, it doesn't sound like fvwm.
> > >
> > > When you "exec" something, Fvwm looks for the config command
> > > "ExecUseShell" and then $SHELL, otherwise it uses /bin/sh.
> >
> > Hmm. Not sure if this sheds any light . . .
> >
> > -bash-2.05b$ echo $SHELL
> > /usr/local/bin/bash
> > -bash-2.05b$ /usr/local/bin/bash xterm
> > xterm: /usr/X11R6/bin/xterm: Permission denied
> > -bash-2.05b$ /bin/sh /usr/X11R6/bin/xterm
> > /usr/X11R6/bin/xterm: Can't open /usr/X11R6/bin/xterm: Permission denied
> > -bash-2.05b$
> >
> > Permission denied? I must be doing something wrong there. I usually
> > just type in the command from the prompt. Typing in xterm from the
> > bash shell pops up a terminal immediately. Ditto if I switch to
> > /bin/sh.
>
> The permission denied message is an indication of a problem,
> it shouldn't be happening. I don't know exactly what it is.
>
> I guess I'd first look at the permissions on the files.
> All of them. Then run "file" on each. Then run the whole
> thing under strace:
>
> strace -f /bin/sh /usr/X11R6/bin/xterm 2>/tmp/strace.out
>
> Then look in /tmp/strace.out for whats causing the permission
> denied.
-bash-2.05b$ strace -f /bin/sh /usr/X11R6/bin/xterm 2>/tmp/strace.out
-bash-2.05b$ cat /tmp/strace.out
execve("/bin/sh", ["/bin/sh", "/usr/X11R6/bin/xterm"], [/* 19 vars */]) = 0
getpid() = 56490 (ppid 56489)
geteuid(0x2) = 500
readlink("/etc/malloc.conf", 0xbfbff574, 63) = -1 ENOENT (No such file or directory)
mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0x280b1000
break(0x80c1000) = 0
break(0x80c2000) = 0
stat("/var/mail/leblanc", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
getuid() = 500 (euid 500)
geteuid(0x2) = 500
getgid() = 100 (egid 100)
getegid(0x2) = 100
open("/usr/X11R6/bin/xterm", O_RDONLY) = -1 EACCES (Permission denied)
break(0x80c3000) = 0
write(2, "/usr/X11R6/bin/xterm: Can\'t open"..., 73/usr/X11R6/bin/xterm: Can't open /usr/X11R6/bin/xterm: Permission denied) = 73
exit(2) = ?
-bash-2.05b$
I'm afraid I don't really understand this. It seems to say it can't
open /usr/X11R6/bin/xterm in the write call, but that should be the
case anyway. I shouldn't be able to write to the file itself. One
thing that could be a problem is that the xterm executable is not
readable, only executable:
bash-2.05b$ ls -l /usr/X11R6/bin/xterm
-rws--x--x 1 root wheel 226568 Jan 10 09:19 /usr/X11R6/bin/xterm*
And the file command gives this:
# file /usr/X11R6/bin/xterm
/usr/X11R6/bin/xterm: setuid ELF 32-bit LSB executable, Intel 80386,
version 1 (FreeBSD), dynamically linked (uses shared libs), stripped
So I don't think there's anything particularly wrong with the
executable itself, but something's screwy with the shell execution
method that is used by Fvwm. This isn't necessarily a problem in the
Fvwm code however. It could be in the Xterm. Unfortunately, I did
just upgrade both of them, so your guess is as good as mine.
> Its a little odd that you have bash installed in /usr/local,
> I guess thats normal for FreeBSD?
Yes. It doesn't install by default, but it's my shell of choice.
Since the ports system is by far the easiest software management
system I've ever seen, I installed it from there. Almost all ports go
to /usr/local/.
Thanks.
Lou
--
Louis LeBlanc leblanc_at_keyslapper.org
Fully Funded Hobbyist, KeySlapper Extrordinaire :)
http://www.keyslapper.org ԿԬ
QOTD:
"I haven't come far enough, and don't call me baby."
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Fri Jan 10 2003 - 22:54:24 GMT