<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div>Sigh. Thanks. I do have a workaround. Your clarification was (regretfully) excellent.<br>art<br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Duncan <1i5t5.duncan@cox.net><br><b><span style="font-weight: bold;">To:</span></b> kde-linux@kde.org<br><b><span style="font-weight: bold;">Sent:</span></b> Fri, June 11, 2010 6:07:05 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [kde-linux] kdeinit: shutting down after setting HOME<br></font><br>
Kevin Krammer posted on Fri, 11 Jun 2010 10:21:05 +0200 as excerpted:<br><br>> On Thursday, 2010-06-10, Schwarz, Arthur I. wrote:<br>>> In Red Hat Linux 5:<br>>> <br>>> <br>>> <br>>> I want to be able to dynamically reset HOME, as in HOME=newHOME; export<br>>> HOME. After I do this, when I execute Kate I get<br>> <br>> Would it be possible to explain which effect you want to achieve, i.e.<br>> why you want to change $HOME?<br>> <br>> Because the way you discribe it here sounds like you run different<br>> programs of the same session with different $HOME values.<br><br>Indeed. KDE isn't designed to have its $HOME changing out from underneath <br>it, and as you (the OP) found out, it doesn't work so well. There's ways <br>around it, but the general case gets pretty complex pretty fast, so if it <br>can be avoided with a fixup for a specific case, it'll make things much <br>simpler for
both you and us.<br><br>A very short explanation of what's going on, however, is that (among other <br>things) kde uses sockets for its inter-process communication (dcop in <br>kde3, dbus in kde4), and these are normally placed in $HOME. So when you <br>try to switch home out from under it, it can't find its sockets anymore, <br>and the various kde components can't communicate with each other <br>properly. What you're seeing is the breakage resulting from that. But <br>that's just one aspect of a rather more complex picture, so if we can <br>simplify the general case to something more specific, it'll be better all <br>around.<br><br>-- <br>Duncan - List replies preferred. No HTML msgs.<br>"Every nonfree program has a lord, a master --<br>and if you use the program, he is your master." Richard Stallman<br><br>___________________________________________________<br>This message is from the kde-linux mailing list.<br>Account
management: <a href="https://mail.kde.org/mailman/listinfo/kde-linux" target="_blank">https://mail.kde.org/mailman/listinfo/kde-linux</a>.<br><span>Archives: <a target="_blank" href="http://lists.kde.org/">http://lists.kde.org/</a>.</span><br><span>More info: <a target="_blank" href="http://www.kde.org/faq.html">http://www.kde.org/faq.html</a>.</span><br></div></div>
</div></body></html>