On Tue, Aug 17, 2010 at 10:56:58AM -0400, Ted Unangst wrote: > On Tue, Aug 17, 2010 at 3:30 AM, Tomas Bodzar <[email protected]> wrote: > > did someone saw similar problem in scrotwm(1)? Eg. when I start > > xeyes(1) on empty workspace from menu M-p it simply "shut down" X. If > > I start eg. xcalc(1) then everything is ok. Another problem is with > > xlock(1). When I want to lock my screen and start xlock(1) eg. this > > way 'xlock -mode atlantis' then my computer completely hangs and I > > must to turn it off with button on case. Last problem which I > > discovered is with warzone game. When I start it on empty workspace > > then it says that timing of monitor is not ok for this app and X is > > not working anymore and I must kill X from console. > > For the record, it would be nice to test with a different window > manager. Bugs in scrotwm do not count as bugs in OpenBSD.
M-?xeyes<enter> in cwm (on current, amd64) runs fine. So i bet a scrotwm bug. Then again the mail contains at least 3 bugs being mentioned, this only treats the first. As for the third (warzone) the monitor timing is probably a warzone or X bug, the rest of the failure could be the WM or the application just not quitting and keeping the keyboard grabbed (that would be an application bug). That can be tested using ssh and kill -9. As a note, scotwm really needs it own mailing list, scrotwm bugs are not really topical for misc. -0- -- She missed an invaluable opportunity to give him a look that you could have poured on a waffle.
