Re: [Cooker] uninstalling msec breaks kdm/kdeinit startup ($PATH problem)
Martin Maèok <[EMAIL PROTECTED]> writes: > I uninstalled msec because I do my security by my own. Then when I > tried to login from KDM, starting KDE stopped in the beginning with an > ERROR (couln't read networking info from /tmp/.dcop make sure > dcopserver is running). When I started KDE with "startx" or from GDM > then KDE started ok. > > So I looked into .xsession-errors and found that kdeinit cannot find > "iceauth" binary. So uninstalling msec make KDM environment missing > /usr/X11R6/bin PATH element and that causes kdeinit/dcopserver failing > to start. Installing msec (particularly /etc/profile.d/msec* files) > again makes to problem go away). > > I think that uninstalling msec should cause problems with starting KDE > :-) > > I've got current Cooker: > msec-0.18-6mdk > kdebase-2.2.2-52mdk corrected in setup-2.2.0-24mdk -- Fred - May the source be with you
[Cooker] uninstalling msec breaks kdm/kdeinit startup ($PATH problem)
I uninstalled msec because I do my security by my own. Then when I tried to login from KDM, starting KDE stopped in the beginning with an ERROR (couln't read networking info from /tmp/.dcop make sure dcopserver is running). When I started KDE with "startx" or from GDM then KDE started ok. So I looked into .xsession-errors and found that kdeinit cannot find "iceauth" binary. So uninstalling msec make KDM environment missing /usr/X11R6/bin PATH element and that causes kdeinit/dcopserver failing to start. Installing msec (particularly /etc/profile.d/msec* files) again makes to problem go away). I think that uninstalling msec should cause problems with starting KDE :-) I've got current Cooker: msec-0.18-6mdk kdebase-2.2.2-52mdk -- Martin Mačok http://underground.cz/ [EMAIL PROTECTED]http://Xtrmntr.org/ORBman/
