Hi, On 08.03.2013 10:21, Adam Nielsen wrote: [...] > I am wondering why Arch upgraded to 3.5 if it is not ready for production use > yet?
Well, it's Arch, the distro for beta testers. :-P [...] > Some of the issues I am experiencing are: > > - Switching focus between monitors with keyboard shortcuts takes 1-2 > seconds. If I press the hotkey and start typing, the first three or so > characters go into the old window, then the rest of them appear in the new > window. So I have to delete the characters, go back to the old window, wait > for a second, delete the other characters, then change back to the new > window, > wait for a second, then retype... https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1071&project=1 https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1075&project=1 > - When new windows appear, such as the Firefox open/save popup when you > download a file, the windows on my other screen resize larger and smaller by > 10 pixels or so about five times before the window appears. This takes 2-3 > seconds to complete. If I choose 'open' and it's a PDF, the other windows > all > resize larger and smaller another five times (with a 2-3 second delay) before > the PDF window appears. If you want me to guess: The other windows are terminals which have size hints and the new size hint handling causes this. The code looks much nicer now, but sadly these bad things happen. https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1117&project=1 (Workaround: Disable size hints handling) > - Switching between terminals uses 100% CPU for a couple of seconds while > they all resize larger and smaller again. I can't type or use the mouse > while > this happens. Same as above. > - Once I have a number of programs open, my mouse cursor freezes for a few > milliseconds every 10 seconds or so. If I'm watching a video it also > glitches > every few seconds. I haven't heard about this one before. The WM shouldn't be able to freeze the cursor since it has nothing to do with it. Rough guess: Awesome uses lots of CPU time (why?!?) and thus the X server doesn't run. However, this sounds unlikely and weird to me. If you want to test, re-nice awesome so that it gets less cpu time than the rest of the system. > I'm not sure what the cause of these issues are, as everything worked fine > before I upgraded to 3.5, so am I missing some sort of compatibility option? Well, my laptop, while certainly not new, has enough CPU power that all of this isn't visible. It just happens too fast. The other aspect is "no one tests stuff before it is released", so I didn't know about any of these issues until two weeks after the release (which is when 3.5 hit Arch). Cheers, Uli -- Sent from my Game Boy. -- To unsubscribe, send mail to [email protected].
