Bugzilla – Bug 679158
Yast2 sometimes does not start from the menu
Last modified: 2013-01-21 09:04:07 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.9.1.17) Gecko/20110121 SUSE/2.0.12-1.5 SeaMonkey/2.0.12 Yast2 sometimes does not start from the menu. With choosing the menu item (with package-manager --install %F command) nothing happens. After a second attempt Yast starts properly. Reproducible: Always Steps to Reproduce: 1. 2. 3.
I figured out that this happens not only with Yast but with any application started with xdg-su.
Killing process '/usr/lib64/kde4/libexec/kdesud' helps for this on KDE.
I do not have to kill the process, a second attempt usually just works. Also I should note that I have this behavior under KDE3, and Kirill uses KDE4, though the issues can be related.
When I attempt to start YaST from my Computer menu, the computer asks me for Administrator password, and then nothing happens. When I run { su -c yast2; }, YaST starts all right. I can use the desktop action afterwards. However, installing software via KSuSEInstall still fails after the password.
For me it happens differently: when Yast does not start I am NOT asked for password. If I am asked, Yast starts well.
Could this bug be connected with: Bug 681078 - xdg-utils: calling xdg-su inside "su -" fails formerly known as: Bug 681078 yast2-control-center-gnome: After zypper dup to 11.4, most of the (graphical) YaST modules do not start via YaST on GNOME ??? Regards Martin (pistazienfresser)
I have the same issue on 11.3, and now 11.4. I think it might be KDE-related, since the problem is bypassed if I manually kill the process: /usr/lib64/kde4/libexec/kdesud Sometimes this process will remain, even after I log out and switch to runlevel 3. If I try to unmount /home, for example, it will tell me "/home is in use". The reason it says this is because of one process that has not terminated: /usr/lib64/kde4/libexec/kdesud
I've never seen this problem with openSUSE 12.2 therefor I'll close the bug as WORKSFORME. If you still can reporduce it wiht 12.1 or later please reopen.