Dnia środa, 25 stycznia 2012 22:28:09 Malte Gell pisze:

Well, killing kdesud did the trick. After killing this process, starting yast2 worked again. So it seems there is an issue with kdesud daemon. After all, is this daemon really needed when starting KDE? Maybe I will create a script that kills kdesud when loggin into KDE session.

I do not have kdesud running. Chris -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org

* Malte Gell [01-25-12 17:13]:

Am 25.01.2012 22:35, schrieb Křištof Želechovski:

...

I do not have kdesud running.

That is strange. When I have some time I will take a look who or what makes kdesud start automatically on my system.

I believe you have *something* else that is not as it should be. I have kdesud running and have no problems starting yast2 from cl or kicker menu or xdg-su openSUSE 12.1 x86_64 kernel: 3.2.1-3-desktop kde: 4.7.2-5.2.2.x86_64 yast2: 2.21.24-2.1.2.x86_64 -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org