RE: [XFree86] "AllowMouseOpenFail" does not work?
Some thoughts. (B (BWe use a system which has a touch screen but no mouse which works OK. (B (BI'm not sure if you want to have a mouse on your system sometimes. (B (BIf you don$B!G(Jt need a mouse at any time just comment out both the line in the (BServerLayout section which references the mouse driver. Than make sure your (Btouch screen is set to "CorePointer" by adding "CorePointer" on the end of (Bthe line which references your touch screen in the ServerLayout section. (B (BYou don$B!G(Jt need to do any thing about the Device sections with the mouse (Bdrivers as the system only loads what is specified in the ServerLayout (Bsection. (B (BIf you need to be able to run with a mouse then the best way is to have two (Bdifferent server layouts and select the one you want when you start X using (Bthe -layout switch. (B (B (BKevin (Bemail: [EMAIL PROTECTED] (BTel: +44 (0)118 971 5032 (B (B-Original Message- (BFrom: David Sun [mailto:[EMAIL PROTECTED] (BSent: 22 September 2004 03:37 (BTo: [EMAIL PROTECTED] (BSubject: Re: [XFree86] "AllowMouseOpenFail" does not work? (B (BHi, Vivek (BOne more question: (Bis it ordinary that the whole system hangs when XFree86 waiting for a (Bconfigure mouse to be present? (Bthanks so much (BDavid $B:_(J 2004-09-21 $BFs(J $BE*(J 18:32$B!$(J Vivek Dasmohapatra $B On Tue, Sep 21, 2004 at 06:19:57PM +0800, David Sun wrote: (B> (B> > Could any body tell me what's possibly the reason of the (B> > "AllowMouseOpenFail" failure? (B> (B> What is happening here (I am informed) is that X is waiting to see (B> some mouse input before noticing the keyboard. It's really annoying, (B> but recent X seems to suffer from this. (B> (B> When I last checked (which was admittedly a long time ago) (B> allowmouseopenfail was necessary top allow X to start _at all_ (B> if it couldn't open the configured mouse device. (B> ___ (B> XFree86 mailing list (B> [EMAIL PROTECTED] (B> http://XFree86.Org/mailman/listinfo/xfree86 (B> (B (B___ (BXFree86 mailing list (B[EMAIL PROTECTED] (Bhttp://XFree86.Org/mailman/listinfo/xfree86 (B___ (BXFree86 mailing list (B[EMAIL PROTECTED] (Bhttp://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Want to lose up to 19% weight. Try Adipren!
___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] "AllowMouseOpenFail" does not work?
On Wed, Sep 22, 2004 at 08:40:44AM +0100, Benstead, Kevin wrote: > -Original Message- > From: David Sun [mailto:[EMAIL PROTECTED] > Sent: 22 September 2004 03:37 > To: [EMAIL PROTECTED] > Subject: Re: [XFree86] "AllowMouseOpenFail" does not work? > > Hi, Vivek > One more question: > is it ordinary that the whole system hangs when XFree86 waiting for a > configure mouse to be present? It appears to be the current behaviour, so I guess it is "normal" in that sense, but I would classify it as a bug. And a nasty one, at that. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [Fwd: KDE starts in FailSafe mode only]
--- Begin Message --- Hi. Can anybody out there help me? I have recently upgraded to XFree86 4.4 from 4,3 on RedHat 9.0 i686 system. The KDM manager loads as normal but with strange little grey console screen for some reason. If I select KDE the splash screen does not load and i end up with couple of little windows. terminal, xterm etc. I can type startkde in terminal and kde loads but any windows do not have minimise, max and close buttons in top right of window. The top bar is just grey aswell. If I start KDE from root outside X Get following errors: rm: cannot remove '.' or '. .' xsetroot: unable to open display '' xrdb: cant open display '' xset: unable to open display "" ksplash: cannot connect to x server kdeinit: Aborting $DISPLAY is not set KSM server: cannot connect to x server if i try xstart before this get fatal server error. server already running, if not delete /tmp blah blah only way of starting kde is in fail safe mode. X console always stays open and reports fonts.dir problems missing element 64 plus many other errors. This is not a problem but spent days trying to figure this. Got to be a solution. MArk B --- End Message ---
[XFree86] system crash
The KDE will no longer start on my Mandrake 9.2 system on bootup. Further, running 'startx' at the command line suggests I send the attached log file /var/log/XFree86.0.log to this address. Any ideas what happened? Thanks, StevePost your free ad now! Yahoo! Canada Personals XFree86 Version 4.3.0 Release Date: 9 May 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.18-23mdksmp i686 [ELF] Build Date: 10 September 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Wed Sep 22 07:09:31 2004 (==) Using config file: "/etc/X11/XF86Config-4" (==) ServerLayout "layout1" (**) |-->Screen "screen1" (0) (**) | |-->Monitor "monitor1" (**) | |-->Device "device1" (**) |-->Input Device "Keyboard1" (**) Option "XkbModel" "pc105" (**) XKB: model: "pc105" (**) Option "XkbLayout" "en_US" (**) XKB: layout: "en_US" (WW) Option "XkbOptions" requires an string value (==) Keyboard: CustomKeycode disabled (**) |-->Input Device "Mouse1" (**) FontPath set to "unix/:-1" (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (**) Option "AllowMouseOpenFail" Using vt 7 (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000f940, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2501 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,250f card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:1e:0: chip 8086,2418 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2410 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,2411 card 8086,2411 rev 02 class 01,01,80 hdr 00 (II) PCI: 00:1f:2: chip 8086,2412 card 8086,2412 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1f:3: chip 8086,2413 card 8086,2413 rev 02 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,2415 card 1014,0169 rev 02 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 5333,8a22 card 105d,0018 rev 03 class 03,00,00 hdr 00 (II) PCI: 02:02:0: chip 8086,1229 card 0e11,b0d7 rev 05 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xfeb0 - 0xfebf (0x10) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xf000 - 0xfe9f (0xea0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:30:0), (0,2,2), BCTRL: 0x0002 (VGA_EN is cleared) (II) Bus 2 I/O range: [0] -1 0 0x7000 - 0x7fff (0x1000) IX[B] (II) Bus 2 non-prefetchable memory range: [0] -1 0 0xfea0 - 0xfeaf (0x10) MX[B] (II) Bus 2 prefetchable memory range: [0] -1 0 0xeff0 - 0xefff (0x10) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(1:0:0) S3 Inc. Savage 4 rev 3, Mem @ 0xfeb8/19, 0xf000/27 (II) Addressable bus resource ranges are [0] -1 0 0x - 0x (0x0) MX[B] [1] -1 0 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0 0x000f - 0x000f (0x1) MX[B] [3] -1 0 0x000c
[XFree86] How to remove iconize button in X11 window
Hi, Is there some soft of twm tweak, or something similar that will remove the "round" iconize button on the upper-left corner of X11 windows? I do not wish to implement --geometry or programatically maximize any window. If I must modify some source, can anyone point me with file/code lines to modify? TIA - Vic ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] missing config in inary reslease
I installed ftp://ftp.xfree86.org/pub/XFree86/4.4.0/binaries/Linux-ix86-glibc23 completely. Then I wanted to install KDE-3.3.0 using the konstruct tool. This failed in kdebase. I tracked it down to the fact that imake -DUseInstalled -I/usr/X11R6/lib/X11/config did not find the config data. So I extraced them from the source tarball. It went a little further. Now host.def, version.def, site.def, date.def are missing. Is it possible to generate these? I thought the binary package to the best way to install X11 without too much trouble. Any suggestions Rgds Dieter ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Strange X Lockup problem with Xinerama - take 2
On Mon, 20 Sep 2004, Phil Dibowitz wrote: On Mon, Sep 20, 2004 at 03:13:40PM -0600, Marc Aurele La France wrote: Perhaps we can nail down what firefox/mozilla is repeatedly requesting. What does `xdpyinfo -queryExtensions` say? I'm assuming this wouldn't change when X freezes? Under that assumption, this is from X not frozen: Thanks, this helps muchly. The only reason I can think of that this output would not correspond to that of the looping server would be extensions being initialised in a different order, a situation I see as highly unlikely, if at all possible. On the assumption that this xdpyinfo output is in fact relevent, then your server strace shows, among other things, two client connections repeatedly calling XShmPutImage(), to which the server never replies (with success or failure). At this point, I don't really know whether it's relevent to the problem that there are two such connections, nor whether the lack of server response is normal XShmPutImage() behaviour for this case. For the latter, I'd like you to capture another server strace, this one without Xinerama and as near as possible to the scenario that would cause the Xinerama loop. Please take care to not delete the original strace's you've made available through your web site. If this non-hang strace shows a server response to the client's XShmPutImage() (or some other server behaviour), then there's likely something amiss with xc/programs/Xserver/Xext/shm.c's ProcPanoramiXShmPutImage(), perhaps with its handling of sendEvent, at which point I'd ask Mark, one with more knowledge of Xinerama internals than me, to investigate further. The server strace also shows -- and this might be a red herring -- a number of client connections making XCreateColormap() calls. Some of these are being accepted by the server, but most are being nixed, presumably due to VisualID settings/differences. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] could not open default font 'fixed'
Lemmit Kaplinski wrote: in the first case: most likely the fixed font is in a subdirectory of /usr/X11R6/lib/fonts. Maybe 75dpi or 100dpi. Look at all the subdirs (and if this fails, all other places where you have fonts installed) Can't find it... What package would have installed it? Thanks for any further help... /Mattias ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Is there a man page for the s3 driver in 4.4.0?
On Mon, 20 Sep 2004, Steve Kleiser wrote: http://www.xfree86.org/4.4.0/manindex4.html lists a man page for s3 virge, but not for other chip sets (in my case, Vision 968 on a Stealth64 VRAM PCI). I can load the module "s3" if I specify it explicitly, but have not yet been able to configure it. Is the 3.3.6 documentation still applicable? I've also tried starting Xfree86 w/o any config file to let the server auto-configure, but to no avail. The resulting log file from that particular attempt is attached. The video card seems to appear at multiple bus addresses (and on buses 0, 64, and 65?). The lspci command shows the chip/card at PCI:0:6:0, which is the first of the probe results, but that doesn't appear to get chosen as "primary". And what are all those other probe results anyway? I don't really see how these ghost devices could still be detected. Can you build from source? There're a few things I'd like you to try. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] x server
I assume you are running a display manager and therefore exiting just exits your session rather than shutting down X. In that case, "telinit 3" should do the trick, I believe. Mark. On Tue, 21 Sep 2004, desert whomper wrote: > can u please tell me how to kill or exit x server on mandrake 10 so i > can install my nvidia drivers? i really need help and have tried alot > and have found no help > ___ > XFree86 mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xfree86 > ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] (no subject)
I believe the i845 wasn't supported until XFree86 4.3.0 (you are running 4.2.0). You should probably upgrade to at least 4.3.0. 4.4.0 is the newest XFree86 version. Mark. On Tue, 21 Sep 2004, Ambica P Padhy wrote: > hi , > I am having trouble in the startx for linux i am sending the XFree86.0.log . > Can you check hwat is wrong so that I can correct the same or i need some > patch to install. > thanks, > apadhy > ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Screen Noise
This is a video ram bandwidth issue. If you have a old or very low end card and are trying to run a very high resolution (for that class of card), it's normal. If not then it's a driver bug of some sort. Mark. On Tue, 21 Sep 2004, davidjpenton wrote: > Is it normal for X to generate a lot of visual noise on the screen when, > e.g., you drag a vertical scroll bar? My system shows tons of "sparks" > to the right of a window if you drag a scroll bar, and in some other cases. > > - Dave - > > ___ > XFree86 mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xfree86 > ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Strange X Lockup problem with Xinerama - take 2
On Wed, 22 Sep 2004, Marc Aurele La France wrote: > On Mon, 20 Sep 2004, Phil Dibowitz wrote: > > > On Mon, Sep 20, 2004 at 03:13:40PM -0600, Marc Aurele La France wrote: > > >> Perhaps we can nail down what firefox/mozilla is repeatedly requesting. > >> What does `xdpyinfo -queryExtensions` say? > > > I'm assuming this wouldn't change when X freezes? Under that assumption, this > > is from X not frozen: > > Thanks, this helps muchly. The only reason I can think of that this output > would not correspond to that of the looping server would be extensions being > initialised in a different order, a situation I see as highly unlikely, if at > all possible. > > On the assumption that this xdpyinfo output is in fact relevent, then your > server strace shows, among other things, two client connections repeatedly > calling XShmPutImage(), to which the server never replies (with success or > failure). > > At this point, I don't really know whether it's relevent to the problem that > there are two such connections, nor whether the lack of server response is > normal XShmPutImage() behaviour for this case. For the latter, I'd like you to > capture another server strace, this one without Xinerama and as near as > possible to the scenario that would cause the Xinerama loop. Please take care > to not delete the original strace's you've made available through your web > site. > > If this non-hang strace shows a server response to the client's XShmPutImage() > (or some other server behaviour), then there's likely something amiss with > xc/programs/Xserver/Xext/shm.c's ProcPanoramiXShmPutImage(), perhaps with its > handling of sendEvent, at which point I'd ask Mark, one with more knowledge of > Xinerama internals than me, to investigate further. My Xinerama system stays up for weeks on end and I spend alot of time using Mozilla and Netscape. Perhaps one of these new apps is using RENDER and it's something related to that? If there was a fundamental bug in shm's Xinerama support I would have expected somebody to find it long ago. That code is many years old and I'm not aware of any outstanding bugs. It seems more likely that there is some new extension usage going on, and that extension has some Xinerama issues. Mark. > > The server strace also shows -- and this might be a red herring -- a number of > client connections making XCreateColormap() calls. Some of these are being > accepted by the server, but most are being nixed, presumably due to VisualID > settings/differences. > > Marc. > > +--+---+ > | Marc Aurele La France | work: 1-780-492-9310 | > | Computing and Network Services | fax:1-780-492-1729 | > | 352 General Services Building | email: [EMAIL PROTECTED] | > | University of Alberta +---+ > | Edmonton, Alberta | | > | T6G 2H1 | Standard disclaimers apply| > | CANADA | | > +--+---+ > XFree86 developer and VP. ATI driver and X server internals. > ___ > XFree86 mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xfree86 > ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] could not open default font 'fixed'
Could you look up this error message in Google? This question gets asked a couple times a day and we don't answer it anymore. It's been the number one question for a couple years now and as far as I'm concerned, it's RedHat's bug not XFree86's. Mark. Hint: RedHat and derivatives configure X to *require* a font server yet they don't seem to be able to ensure that the font server stays running. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] could not open default font 'fixed'
Mark Vojkovich wrote: Could you look up this error message in Google? This question gets asked a couple times a day and we don't answer it anymore. Believe me, I really did google quite a bit for the specific error message "could not open default font 'fixed'", without being able to find an answer that could resolve my problem. That's why I asked this question here. It's been the number one question for a couple years now and as far as I'm concerned, it's RedHat's bug not XFree86's. I understand your sentiment. If there's a useful X troubleshooter page (I obviously haven't found one), it would be helpful to steer people with this type of problem to it. Eventually, all the google hits would then link to that same resource. Mark. Hint: RedHat and derivatives configure X to *require* a font server yet they don't seem to be able to ensure that the font server stays running. That seems like an unwise choice no doubt. Thanks for the hint. In my case, xfs seems to be running, however. # service xfs status xfs (pid 2854) is running... /Mattias ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Strange X Lockup problem with Xinerama - take 2
On Wed, 22 Sep 2004, Mark Vojkovich wrote: On Wed, 22 Sep 2004, Marc Aurele La France wrote: On Mon, 20 Sep 2004, Phil Dibowitz wrote: On Mon, Sep 20, 2004 at 03:13:40PM -0600, Marc Aurele La France wrote: Perhaps we can nail down what firefox/mozilla is repeatedly requesting. What does `xdpyinfo -queryExtensions` say? I'm assuming this wouldn't change when X freezes? Under that assumption, this is from X not frozen: Thanks, this helps muchly. The only reason I can think of that this output would not correspond to that of the looping server would be extensions being initialised in a different order, a situation I see as highly unlikely, if at all possible. On the assumption that this xdpyinfo output is in fact relevent, then your server strace shows, among other things, two client connections repeatedly calling XShmPutImage(), to which the server never replies (with success or failure). At this point, I don't really know whether it's relevent to the problem that there are two such connections, nor whether the lack of server response is normal XShmPutImage() behaviour for this case. For the latter, I'd like you to capture another server strace, this one without Xinerama and as near as possible to the scenario that would cause the Xinerama loop. Please take care to not delete the original strace's you've made available through your web site. If this non-hang strace shows a server response to the client's XShmPutImage() (or some other server behaviour), then there's likely something amiss with xc/programs/Xserver/Xext/shm.c's ProcPanoramiXShmPutImage(), perhaps with its handling of sendEvent, at which point I'd ask Mark, one with more knowledge of Xinerama internals than me, to investigate further. My Xinerama system stays up for weeks on end and I spend alot of time using Mozilla and Netscape. Perhaps one of these new apps is using RENDER and it's something related to that? If there was a fundamental bug in shm's Xinerama support I would have expected somebody to find it long ago. That code is many years old and I'm not aware of any outstanding bugs. It seems more likely that there is some new extension usage going on, and that extension has some Xinerama issues. The strace doesn't show any other extension being involved. IOW, there is no call to feel defensive about this. The facts will speak for themselves. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] How did I break run level 5 login during RH9 => 4.4.0 transition?
I downloaded 4.4.0 from xfree86.org and installed per the instructions on a Thinkpad 600E running Red Hat 9. All is well except that booting into run level 5 generates a strange desktop with several xterms and an xsm window, not the usual Red Hat login screen. Changing inittab to default to run level 3, booting, logging in at the console prompts, and running startx with a hand-written .xinitrc ending in "exec gnome-session" works fine. But I'm curious: what got broken during this transition? ___ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Strange X Lockup problem with Xinerama - take 2
On Wed, Sep 22, 2004 at 10:39:49AM -0600, Marc Aurele La France wrote: > On Mon, 20 Sep 2004, Phil Dibowitz wrote: > > >On Mon, Sep 20, 2004 at 03:13:40PM -0600, Marc Aurele La France wrote: > > >>Perhaps we can nail down what firefox/mozilla is repeatedly requesting. > >>What does `xdpyinfo -queryExtensions` say? > > >I'm assuming this wouldn't change when X freezes? Under that assumption, > >this > >is from X not frozen: > > Thanks, this helps muchly. The only reason I can think of that this output > would not correspond to that of the looping server would be extensions > being initialised in a different order, a situation I see as highly > unlikely, if at all possible. Gah, the one site that always reproduced the bug just redesigned their site and won't trigger the bug. I'll be back with that strace as soon as I remember one of the other sites that triggered the bug. Thanks. -- Phil Dibowitz Systems Architect and Administrator Enterprise Infrastructure / ISD / USC UCC 174 - 213-821-5427 pgpjtHQIVuTET.pgp Description: PGP signature
