Re: Programs not accepting input?
On Sun, 2006-Mar-26 17:50:09 +1030, Greg 'groggy' Lehey wrote: >In the last month or two I've seen increasing occurrences of programs >refusing keyboard input after they've been running for a while >(between hours and days). They still respond to the mouse. At first >I thought it was hardware, but it happens on a number of different >machines, and only with certain programs, all of them X clients. >Here's an overview (system names are simply to show that they're >different machines). Is the problem that the clients aren't taking focus or have focus but aren't accepting keyboard input? My work system runs separate X servers on two heads (rather than ximerama) and I have problems with windows occasionally refusing to accept focus after I move the pointer from screen to screen (though I can get an alternative window to accept focus and then switch back to the window I originally wanted). This started after an X.org upgrade but I'm not sure which one. >The fact that new firefox windows accept input suggests that it's >somewhere in X. What X server? -- Peter Jeremy pgp61ENFPAOE4.pgp Description: PGP signature
precompiled header
hi
why fbsd dont use precompiled headers during buildword/buildkernel? I just did
very naive test (which doesnt work for a lot of the headers)
cd /sys; find . -name \*.h -exec gcc -x c-header {} \;
time buildkernel
and delete those compiled headers and time buildkernel again
there is a speedup for the precompiled-headers case (but not very big) and I am
sure if it
was carefully integrated into the build (ie. compiling all headers) the
difference might be quite visible...
thnx
roman
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Programs not accepting input?
On Sun, 26 Mar 2006, Peter Jeremy wrote: On Sun, 2006-Mar-26 17:50:09 +1030, Greg 'groggy' Lehey wrote: In the last month or two I've seen increasing occurrences of programs refusing keyboard input after they've been running for a while (between hours and days). They still respond to the mouse. At first I thought it was hardware, but it happens on a number of different machines, and only with certain programs, all of them X clients. Here's an overview (system names are simply to show that they're different machines). Is the problem that the clients aren't taking focus or have focus but aren't accepting keyboard input? My work system runs separate X servers on two heads (rather than ximerama) and I have problems with windows occasionally refusing to accept focus after I move the pointer from screen to screen (though I can get an alternative window to accept focus and then switch back to the window I originally wanted). This started after an X.org upgrade but I'm not sure which one. I've noticed that KDE's window manager, especially the version currently in ports, seems to occasionally have focus management problems. If I use ctrl-alt-tab to manually switch the focus, keyboard and some mouse input works properly, and after a program exits, things start working right. I think what's going on is that the window manager becomes confused as the mouse passes over the panel or interacts with the panel, as at that point the focus gets "stuck". Probably because mouse input events have been grabbed and not released, which is not an unusual X window manager application bug. Once the grab has happened without a release, the mouse remains grabbed until that application exits or releases it, so that would be consistent with my triggering a release by the window manager through exiting another program and then triggering the bug again by passing over the panel (or whatever). So I'd almost certainly put this down to an X11 application bug, possibly in the window manager. The "grab" behavior is one of the more unfortunate ones in X11, since it allows an application to very trivially interfere with the operation of the window server as a whole, and it's an easy bug to implement (just like leaking memory -- you have an error path and forget to release all resources). Robert N M Watson ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
actual status of 6.1-RELEASE ???
Does anyone know what is real deadline for 6.1-RELEASE (6.1-PR1)? Schedule on website is outdated, to-do list/status isn't updated from weeks. I can't find on mailing lists information about actual status of 6.1-RELEASE. I will be very thankful for information :) -- steve home.pl ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Xen 3.0
All, what's the status of FreeBSD Xen support? The last I heard was that it had DomU support and someone was working on Dom0 support? Has DomU support been integrated in to -current? Thanks, Ray. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Programs not accepting input?
On Sun, Mar 26, 2006 at 11:16:36AM +, Robert Watson wrote: > On Sun, 26 Mar 2006, Peter Jeremy wrote: > >On Sun, 2006-Mar-26 17:50:09 +1030, Greg 'groggy' Lehey wrote: > >>In the last month or two I've seen increasing occurrences of programs > >>refusing keyboard input after they've been running for a while > >>(between hours and days). They still respond to the mouse. At first > >>I thought it was hardware, but it happens on a number of different > >>machines, and only with certain programs, all of them X clients. > >>Here's an overview (system names are simply to show that they're > >>different machines). > > > >Is the problem that the clients aren't taking focus or have focus but > >aren't accepting keyboard input? > > > >My work system runs separate X servers on two heads (rather than ximerama) > >and I have problems with windows occasionally refusing to accept focus > >after I move the pointer from screen to screen (though I can get an > >alternative window to accept focus and then switch back to the window I > >originally wanted). This started after an X.org upgrade but I'm not sure > >which one. > > I've noticed that KDE's window manager, especially the version currently in > ports, seems to occasionally have focus management problems. If I use > ctrl-alt-tab to manually switch the focus, keyboard and some mouse input > works properly, and after a program exits, things start working right. I I'm seeing focus problems every few months running WindowMaker, also in a 2 head configuration. The focus stick with one window - you can close that one using mouse, but you still won't be able get focus on another window. A restart of windowmaker won't help, so far I was forced doing a complete X restart whenever this happened. Not shure when it started, likely with an update from an old XFree to an Xorg release (installed xorg-6.8.2). -- B.Walterhttp://www.bwct.de http://www.fizon.de [EMAIL PROTECTED] [EMAIL PROTECTED][EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Programs not accepting input?
On Sun, Mar 26, 2006 at 07:17:19PM +1100, Peter Jeremy wrote: > > Is the problem that the clients aren't taking focus or have focus > but aren't accepting keyboard input? My problem wasn't about focus. I know the window had input focus (my settings change the border color for focused windows), but the keyboard events weren't accepted by certain clients. > My work system runs separate X servers on two heads (rather than > ximerama) and I have problems with windows occasionally refusing to > accept focus after I move the pointer from screen to screen (though I > can get an alternative window to accept focus and then switch back to > the window I originally wanted). This started after an X.org upgrade > but I'm not sure which one. I've seen that problem also, with and without xinerama enabled (always with dual-head nvidia cards). My keyboard input problem only affected certain clients. Like I said, one rxvt would accept keyboard events and another rxvt right next to it wouldn't. It was an X.org server, I forget the version. I've not noticed the problem recently, but I could try to reproduce the problem if necessary. -- Rick C. Petty ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Programs not accepting input?
On Sunday, 26 March 2006 at 19:17:19 +1100, Peter Jeremy wrote: > On Sun, 2006-Mar-26 17:50:09 +1030, Greg 'groggy' Lehey wrote: >> In the last month or two I've seen increasing occurrences of programs >> refusing keyboard input after they've been running for a while >> (between hours and days). They still respond to the mouse. At first >> I thought it was hardware, but it happens on a number of different >> machines, and only with certain programs, all of them X clients. >> Here's an overview (system names are simply to show that they're >> different machines). > > Is the problem that the clients aren't taking focus or have focus > but aren't accepting keyboard input? The latter. It's not a question of focus. > My work system runs separate X servers on two heads (rather than > ximerama) and I have problems with windows occasionally refusing to > accept focus after I move the pointer from screen to screen (though > I can get an alternative window to accept focus and then switch back > to the window I originally wanted). This started after an X.org > upgrade but I'm not sure which one. Interesting. I've seen this one too: my mail window is at the left of the right-hand monitor on wantadilla (:0.1). Frequently when I move from :0.0 to 0:1, the window manager will highlight the window on :0.1, but focus remains with some window on :0.0. If I move further right and then back again, focus catches up with the correct window. That's mainly irritating; the problem I describe above is annoying. >> The fact that new firefox windows accept input suggests that it's >> somewhere in X. > > What X server? echunga: vendor string:The X.Org Foundation vendor release number:60801000 X.Org version: 6.8.1 wantadilla: vendor string:The X.Org Foundation vendor release number:60802000 X.Org version: 6.8.2 I don't think that the difference in version numbers is the issue. Greg -- See complete headers for address and phone numbers. pgpCdQYWKKAL5.pgp Description: PGP signature
Re: Programs not accepting input?
On Sunday, 26 March 2006 at 1:36:57 -0600, Rick C. Petty wrote: > On Sun, Mar 26, 2006 at 05:50:09PM +1030, Greg 'groggy' Lehey wrote: >> In the last month or two I've seen increasing occurrences of programs >> refusing keyboard input after they've been running for a while >> (between hours and days). They still respond to the mouse. At first >> I thought it was hardware, but it happens on a number of different >> machines, and only with certain programs, all of them X clients. > > > >> One thing that the machines have in common is that they all run x2x > > I noticed very similar problems on both 5.4-stable and 6.0-RELEASE > boxes running xorg. I've never used x2x, but I was running x11vnc, > which I ended up assuming was the culprit. It's a really strange > behavior-- I would have two rxvts side-by-side, one accepting > keyboard input and the other I had to cut/paste text using the > mouse. It was even more frustrating when it would happen in gaim & > mozilla windows! The same gaim process wouldn't accept keyboard > input in the conversation window but the buddy window did responded > to commands (e.g. control-A brought up the accounts window). Yes, this sounds quite close to what I'm experiencing. On Sunday, 26 March 2006 at 15:43:07 -0600, Rick C. Petty wrote: > On Sun, Mar 26, 2006 at 07:17:19PM +1100, Peter Jeremy wrote: >> >> Is the problem that the clients aren't taking focus or have focus >> but aren't accepting keyboard input? > > My problem wasn't about focus. I know the window had input focus (my > settings change the border color for focused windows), but the keyboard > events weren't accepted by certain clients. Same here. As mentioned in the original message, I can use the mouse to open a new window under firefox. The new window will accept keyboard input, the old one won't. It's almost as if it's deadlocking on input. Reminder: my final question was "how do I go about debugging this problem?". Greg -- See complete headers for address and phone numbers. pgpFe3Z0Zr29L.pgp Description: PGP signature
Re: Programs not accepting input?
On Mon, 2006-Mar-27 11:29:15 +1030, Greg 'groggy' Lehey wrote: >>> One thing that the machines have in common is that they all run x2x Can you drop this and just use a single X server? >Reminder: my final question was "how do I go about debugging this >problem?". X11 protocol tracing (eg xmon) and client ktracing might be a start to see where the keyboard events are disappearing. -- Peter Jeremy pgpZaTj3fx9je.pgp Description: PGP signature
