From mint-bounce@lists.fishpool.fi Sat Jun 12 12:19:44 2010 Message-ID: <4C13B264.1000601@online.no> Date: Sat, 12 Jun 2010 18:14:28 +0200 From: Jo Even Skarstein User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] Keyboard-problem with XaAES helmut-branch References: <4C128FBE.7010402@online.no> <4C12A398.5090308@online.no> <4C12AC8D.3050101@online.no> <4C12B776.5030907@online.no> <4C135D23.2050409@online.no> <4C138688.8080200@online.no> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: On 06/12/2010 03:25 PM, Helmut Karlowski wrote: >>> Have the xaaes-threads the same pgrp as init? >> >> Yes. > > Why? I'm sorry, I misread your question. xaloader has the same pgrp as init. xaaes has the same as the kernel. >>> pid 72 (qed): Dopendir(U:\ram\clipbrd\): error -33 >>> pid 72 (qed): Fxattr(U:\ram\clipbrd\): path2cookie returned -33 >>> >>> Leave away the last \: >>> >>> clipbrd=u:\ram\clipbrd >> >> Tried this, there is no difference. > > Works on aranym. > > Try an old kernel, see if there's a difference with that clipbrd-issue. There is. The problem is not there in a kernel from September. Jo Even