On Wed, Jul 24, 2002 at 09:28:05PM +0200, Alexandr Malusek wrote:
"Robert C. Paulsen Jr."
writes: On Wed, Jul 24, 2002 at 05:48:20AM +0200, Anders Johansson wrote:
On Wednesday 24 July 2002 04.31, Robert C. Paulsen Jr. wrote:
I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode.
I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding).
Any ideas? Is this a common problem?
One idea, if you're using "sux" to run yast. If you're running it some other way it could be other reasons, but I found a problem with sux.
I don't think it's sux since I have the same problem when I log into X as root.
"strace -f yast2" may give some hints (missing files, ...).
Strace shows that it goes to ncurses mode almost immediately: avalon:~ # strace yast2 execve("/sbin/yast2", ["yast2"], [/* 52 vars */]) = 0 uname({sys="Linux", node="avalon", ...}) = 0 brk(0) = 0x80bca6c open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=57251, ...}) = 0 old_mmap(NULL, 57251, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40017000 close(3) = 0 open("/lib/libreadline.so.4", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0\252\0"..., 1024) = 1024 fstat64(3, {st_mode=S_IFREG|0755, st_size=199592, ...}) = 0 old_mmap(NULL, 171856, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40025000 mprotect(0x4004a000, 20304, PROT_NONE) = 0 old_mmap(0x4004a000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x24000) = 0x4004a000 close(3) = 0 open("/lib/libhistory.so.4", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\20\27\0"..., 1024) = 1024 fstat64(3, {st_mode=S_IFREG|0755, st_size=29819, ...}) = 0 old_mmap(NULL, 26908, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4004f000 mprotect(0x40055000, 2332, PROT_NONE) = 0 old_mmap(0x40055000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x5000) = 0x40055000 close(3) = 0 open("/lib/libncurses.so.5", O_RDONLY) = 3
Also, try to view the YaST2 window on a different machine to check it's not an X-server related problem:
good_machine# ssh -X -l root bad_machine yast2
Same results -- goes straight inti ncurses mode. Maybe I don't have some rpm installed. -- Robert C. Paulsen, Jr. robert@paulsenonline.net