В Wed, 27 May 2015 15:06:01 -0700 Linda Walsh <suse@tlinx.org> пишет:
tried editing a file as root:
sudo gvim /etc/fstab Error detected while processing /usr/share/vim/vim74/menu.vim: line 354: E327: Part of menu-item path is not sub-menu E233: cannot open display
Default sudo configuration in openSUSE does not preserve DISPLAY environment variable.
E852: The child process failed to start the GUI Press ENTER or type command to continue
Two separate problems -- the menu.vim file is bad. I think I submitted a but on that some time ago, as I seem to remember them asking me if I could test the newer version (couldn't at the time didn't have the new libc installed for the new vim). So it was there in the 13.1 version as well (as tried reinstalling it (the actual file named above is in the vim-data rpm).
---
The 2nd problem, sudo seems to have changed some default to not allow a child process to spawn.
This meant when I used "sudoedit" to try to edit the sudoer's file: sudoedit /etc/sudoers ^C^C^C^Y^Y^C^Y^C^Y^C It just hung -- couldn't even trace it to find out what it was doing until I sigSTOP'd/CONT'd it: sudo strace -f -p 31351 Process 31351 attached -- just sat there w/no output until I ^c then ^CProcess 31351 detached 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
---- Good thing I don't need sudoedit to clean things up.
Sigh. I already wrote a bug about the 1st item and it didn't get fixed. I don't really feel like writing another. (I find problems like this with some regularity (not that the bugs are usually in anything suse has done... though the thing about 'gvim' invoking some child process to start the GUI... now I don't know -- is that a SuSE-ism? The gui used to be a separate program
Computers are so fun these days....
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org