yast2 sw_single not starting

Since a few days all yast2 modules which are in relation with software (install, install-sources,…) are starting no more. Zypper and yast are working fine.

The tail of a strace yast2 sw_single looks so:

— SIGCHLD (Child exited) @ 0 (0) —
wait4(-1, 0x7ffff8bcd264, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigreturn(0xffffffffffffffff) = 0
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
read(255, "
if “$SELECTED_GUI” = “ncurses”…, 8192) = 5705
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
pipe([3, 4]) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], ], 8) = 0
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [INT CHLD], ], 8) = 0
lseek(255, -926, SEEK_CUR) = 11864
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fb8f0b03780) = 9793
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigaction(SIGCHLD, {0x7fb8f0b6f460, ], SA_RESTORER|SA_RESTART, 0x7fb8f019e6e0}, {0x7fb8f0b6f460, ], SA_RESTORER|SA_RESTART, 0x7fb8f019e6e0}, 8) = 0
close(4) = 0
read(3, “/home/fredfist
“, 128) = 15
read(3, “”, 128) = 0
— SIGCHLD (Child exited) @ 0 (0) —
wait4(-1, {WIFEXITED(s) && WEXITSTATUS(s) == 0}], WNOHANG, NULL) = 9793
wait4(-1, 0x7ffff8bcd534, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigreturn(0xffffffffffffffff) = 0
close(3) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], ], 8) = 0
rt_sigaction(SIGINT, {0x7fb8f0b6cc2b, ], SA_RESTORER|SA_RESTART, 0x7fb8f019e6e0}, {SIG_DFL, ], SA_RESTORER|SA_RESTART, 0x7fb8f019e6e0}, 8) = 0
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigaction(SIGINT, {SIG_DFL, ], SA_RESTORER|SA_RESTART, 0x7fb8f019e6e0}, {0x7fb8f0b6cc2b, ], SA_RESTORER|SA_RESTART, 0x7fb8f019e6e0}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
stat(”/home/fredfist/.qt//qtrc”, 0x7ffff8bcdb40) = -1 ENOENT (No such file or directory)
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
read(255, "

do it!

$@ are args for ycp"…, 8192) = 926

rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, ], 8) = 0
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], ], 8) = 0
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [INT CHLD], ], 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [INT CHLD], 8) = 0
rt_sigprocmask(SIG_SETMASK, [INT CHLD], NULL, 8) = 0
lseek(255, -169, SEEK_CUR) = 12621
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fb8f0b03780) = 9796
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], ], 8) = 0
rt_sigprocmask(SIG_SETMASK, ], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], ], 8) = 0
rt_sigaction(SIGINT, {0x7fb8f0b6cc2b, ], SA_RESTORER|SA_RESTART, 0x7fb8f019e6e0}, {SIG_DFL, ], SA_RESTORER|SA_RESTART, 0x7fb8f019e6e0}, 8) = 0
wait4(-1,

Can anybody help?
Thanks

Happens here as well. But not when I start yast2 via the menu…weird

Crazy, you are right. It starts when you call Yast2 by the menu.

This problem appears, when you call Yast2 or one of its sw-modules as root from a pts. A kdesu yast2 as user works for the best. I straced both, but I didn’t came to a clue. Mybe a wrong set environmental variable or so.

Hi
Both ncurses and qt interface work fine here, no errors when starting
from the CLI (Gnome DE)?


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.1 (i586) Kernel 2.6.27.19-3.2-pae
up 18:27, 3 users, load average: 0.31, 0.20, 0.17
ASUS eeePC 1000HE ATOM N280 1.66GHz | GPU Mobile 945GM/GMS/GME

I have the same problem, any solution to this one yet?

Many thanks,
Pierre

Also came across this problem. With a clean install my system started yast2 and all the over components. A re-boot and adding the xen kernel later and I can not start any component from yast2.
The kdesu yast2 approach seems to work though.