From mint-bounce@lists.fishpool.fi Sat Jun 12 06:13:21 2010 Message-ID: <4C135D23.2050409@online.no> Date: Sat, 12 Jun 2010 12:10:43 +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> 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 08:34 AM, Helmut Karlowski wrote: > But it did not change a bit since then. It might be related to your > taskbar-problem: The Ctrl-Q-issue mostly appears when the system is busy > (extensive HD-access etc.). It's not related to the load here. And I'm quite sure that you've changed plenty of bits since September ;-) It doesn't have to be directly related to keyboard handling. >> There seems to be a pattern. When Taskbar becomes unresponsive, XaAES' >> Ctrl+Alt-hotkeys stops working. So it seems to be related to the > > Same here when system is too busy. But when I kill Taskbar, the hotkeys still doesn't work. I have to reboot to get them working again. top says that idle has 99% cpu. >> keyboard handling. I don't know if the hotkeys stop working because of a >> problem with Taskbar, or if Taskbar stops working because of a problem >> with XaAES. >> >> According to top Taskbar eats all available CPU when this happens, but >> general performance seems to not be affected. It looks like Taskbar is >> busywaiting for something. I really must dig into this tomorrow night. > > This seems to be the source of all this. Do the keyboard-problems happen > also without taskbar? The missed Ctrl+Q - yes. I've also noticed the same problem with Ctrl+S. About the XaAES-hotkeys not working I've only seen this when Taskbar becomes unresponsive. >> ith Aranym/hostfs or with clipbrd on ramfs? I have been using qed every >> time I've switched on my Milan since I got it, and I have never seen >> this problem until tonight. If I switch back to XaAES from September >> last year, the problem is gone. > > It was u:\ram\clipbrd\. I forgot to mention this. It seems that > everything other than C:\clipbrd\ does not work for qed. It has worked fine for me up until the latest MiNT/XaAES-build. I've had clipbrd pointing to u:/ram/clipbrd since 2007. Jo Even