From: Jochen S. <cyc...@gm...> - 2011-05-05 03:14:50
|
Hi, actually I have been experiencing something like this as well. However, it triggers slightly different and I can recover from it. I don't see anything with the mouse and it appeared only after upgrading E recently, which lets me to believe it is either caused by E or an unrelated issue. The way I can reproduce this is by closing a window, does not matter if by mouse or keybinding, in fact the first time I saw this was when closing using the mouse. This has so far only happened to me when I closed the last window on the specific virtual desktop. I then often try to switch to a different desktop via keybindings but they stop working. Clicks on the desktop to bring up the menu do not work either, however I can click on the pager and switch to a different desktop. This usually also fixes keybindings etc., and everything works back normal. Maybe this helps to track it down. Cheers Jochen On 05/05/11 07:22, Carsten Haitzler (The Rasterman) wrote: > On Thu, 5 May 2011 01:13:53 +0800 P Purkayastha<pp...@gm...> said: > > smells like the bsd thread points to a more general problem that e can't do > anything about :) > >> This should help you get the list of loaded and enabled modules: >> dbus-send --print-reply=literal --dest=org.enlightenment.wm.service >> /org/enlightenment/wm/RemoteObject org.enlightenment.wm.Module.List | grep >> 'int32.*1' >> >> >> By the way, I also have this problem. It is very sporadic and hard to >> reproduce. It sometimes happens when I close a window using a keybinding >> (different from enlightenment keybindings) and there are no more windows >> left on the current desktop. Examples are when I close pidgin using escape, >> or say smplayer using q, etc. I haven't found a way of reliably reproducing >> this behaviour. >> >> I also have a problem where the left mouse click is unresponsive at times. >> It can be made to work again, if by some method you can run xev, or if you >> close some window on which you last used the left mouse click. >> >> The above problems, and the fact that the mouse problem can be cured by >> running xev, makes me suspect that it might be an X problem instead of E >> problem. Searching the net led me to the following thread (on freebsd, but >> my problems are on 64 bit linux): >> http://forums.freebsd.org/showthread.php?t=14780 >> >> Some other people on #e have also experienced similar problems. >> >> >> On Wed, May 4, 2011 at 11:40 PM, Andreas Willich >> <sab...@gm...>wrote: >> >>> 2011/5/4 Cedric BAIL<ced...@fr...> >>> >>>> On Wed, May 4, 2011 at 4:42 AM, Carsten Haitzler<ra...@ra...> >>>> wrote: >>>>> On Tue, 3 May 2011 23:05:44 +0200 Andreas Willich< >>>> sab...@gm...> said: >>>>>> I am currently running rev59088 of E17. >>>>>> Or more I try to run it. After some time, so about 30 - 60 seconds, >>> E17 >>>> does >>>>>> not recognize any input from mouse and keyboard. >>>>>> Does anybody experience something similar? I am not 100% sure that the >>>>>> problem is on E17. >>>>> >>>>> WFM. :) >>>> >>>> Maybe a module that does block E17. What is your module list ? >>>> >>> >>> Can I get this information somehow in a terminal or do I have to transcribe >>> it from the UI? >>> >>> ------------------------------------------------------------------------------ >>> WhatsUp Gold - Download Free Network Management Software >>> The most intuitive, comprehensive, and cost-effective network >>> management toolset available today. Delivers lowest initial >>> acquisition cost and overall TCO of any competing solution. >>> http://p.sf.net/sfu/whatsupgold-sd >>> _______________________________________________ >>> enlightenment-users mailing list >>> enl...@li... >>> https://lists.sourceforge.net/lists/listinfo/enlightenment-users >>> > > |