[sudo-users] problem in sudo-1.8.10p3-2.1.6; breakage from sudo-1.8.7-5.1.3

[L. A. Walsh]

When I try to edit a file as root (using sudo), now
I get:
Ishtar:law> sudo gvim /etc/fstab
E233: cannot open displayE852: The child process failed to start the GUI
Press ENTER or type command to continue

However, my sudoers file has:

Defaults !syslog
Defaults !env_reset
Defaults !always_set_home
Defaults !env_delete
Defaults !env_check
Defaults closefrom=65535
Defaults !ignore_dot
Defaults preserve_groups
Defaults fast_glob
Defaults !set_logname
Defaults setenv
Defaults shell_noargs
Defaults !logfile
Defaults exempt_group="lawgroup"
Defaults !log_output
Defaults umask=777
Defaults editor="/usr/bin/gvim -f:/usr/bin/vim"
## User privilege specification

root ALL=(ALL) NOPASSWD: SETENV: ALL
law ALL=(ALL) NOPASSWD: SETENV: ALL
Bliss\\law ALL=(ALL) NOPASSWD: SETENV: ALL
Bliss\\root ALL=(ALL) NOPASSWD: SETENV: ALL
BLISS\\root ALL=(ALL) NOPASSWD: SETENV: ALL
BLISS\\law ALL=(ALL) NOPASSWD: SETENV: ALL

I had the ones w/a domain in there because of past
weirdness where my username got displayed as that,
but was signed in as 'law' in this case.

It appears gvim uses a child for some reason, and
even though my env doesn't get cleared, initially,
it is cleared in the child -- but there's nothing
in the sudoers file

It's a good think I don't need to use sudoedit to edit
the sudoers file:

sudoedit /etc/sudoers
^C^C^C^Y^Y^C^Y^C^Y^C

This is weird:
     PID USER PR NI  VIRT  RES  SHR S %CPU  %MEM TIME+  COMMAND          
ps:31351 law  20  0 73884 1824 1056 R 99.9  0.0  3:15.45 sudoedit 

but can't seem to find out what it is doing:
       
>  sudo strace -f -p 31351
Process 31351 attached
-- just sits there w/no output until I ^c then
^CProcess 31351 detached

Ah...
STOP/CONT gave something:
--- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=34997, si_uid=0} ---
write(5, "\22", 1)                      = -1 EBADF (Bad file descriptor)
rt_sigreturn()                          = 140695816922856

Um... I really don't think sudoedit should do that... nor sudo
be clearing my env by default...seems hazardous.