Page 1 of 1
[SOLVED]KDEInit could not launch '/tmp/.wmanager'.
Posted: 05 Feb 2012, 15:50
by feng
when i click the "Home" icon on the desktop, it shows me the message:
KDEInit could not launch '/tmp/.wmanager'.
what happened?
Re: KDEInit could not launch '/tmp/.wmanager'.
Posted: 05 Feb 2012, 17:17
by fanthom
sounds like a 'DCOP' bug. please try the fix which i posted some time ago:
http://ponce.cc/porteus/i486/current/Porteus-1.1-fixes
as far as i can see from alpha build of Trinity-3.5.13 provided by brokenman this bug will finally be gone in next release
Re: KDEInit could not launch '/tmp/.wmanager'.
Posted: 05 Feb 2012, 20:53
by brokenman
Yes the DCOP error has been dealt with in next release.
Please verify that the /tmp/.wmanager file was created during boot. What is the output of:
file /tmp/.wmanager
Re: KDEInit could not launch '/tmp/.wmanager'.
Posted: 17 Feb 2012, 13:41
by feng
there's no such file "/tmp/.wmanager" ....
Re: KDEInit could not launch '/tmp/.wmanager'.
Posted: 17 Feb 2012, 14:33
by Hamza
If this file is absent, some applications may not works correctly as this symlink is linked to default file manager of your current Desktop.
Please have a look at /opt/porteus-scripts/path
Re: KDEInit could not launch '/tmp/.wmanager'.
Posted: 18 Feb 2012, 06:54
by feng
ok, i know the reason. since i usually boot into text mode (telinit~3) and then run startx. in this case, KDEinit could not launch the file /tmp/.wmanager, it's not exist.
if i boot into kde directly (telinit~4), then the file /tmp/.wmanager will be there.
Re: [SOLVED]KDEInit could not launch '/tmp/.wmanager'.
Posted: 19 Feb 2012, 23:57
by brokenman
In the next version this symlink will not exist. Fanthom has come up with a more elegant solution.