Re: [Fwd: Re: Crash on second screen]
The library, as reported by ldd, is /usr/X11R6/lib/libforms.so.0.88 and the version entries in /usr/X11R6/include/forms.h are: #define FL_VERSION 0 #define FL_REVISION 88 #define FL_FIXLEVEL1 This is the latest version reported on the XFreeBSD Ports site, though I see that there is a 0.89 version (last updated 2/00) that has not made it into a FreeBSD distribution package. I've tried downloading the FreeBSD binary distribution of v. 0.89 of the library from the Xforms site and using it with LyX. But the ap won't work with the new library, even though the API is compatible, because it detects the library version change and refuses to coninue (duh; what's the use of using dynamic libraries [no, don't tell me about the reduced sizes of aps] if the ap refuses to take advantage of library upgrades without a rebuild?)! Bradford, The xforms libraries are API compatible but not binary compatible. This means that when going from xforms 0.88 to 0.89 you'll have to recompile LyX. That's why we test to see if the library version has changed; better a controlled exit than a nasty and unpredictable crash. Note that xforms 0.89 has reached fix level 15 or so on linux systems, so it's probably pretty well de-bugged. I'm running here with 0.89 fix level 1 on a Dec Alpha and it's never done anything nasty to me. Angus
Re: [Fwd: Re: Crash on second screen]
> The library, as reported by ldd, is /usr/X11R6/lib/libforms.so.0.88 and > the version entries in /usr/X11R6/include/forms.h are: > > #define FL_VERSION 0 > #define FL_REVISION 88 > #define FL_FIXLEVEL1 > > This is the latest version reported on the XFreeBSD Ports site, though I > see that there is a 0.89 version (last updated 2/00) that has not made it > into a FreeBSD distribution package. I've tried downloading the FreeBSD > binary distribution of v. 0.89 of the library from the Xforms site and > using it with LyX. But the ap won't work with the new library, even though > the API is compatible, because it detects the library version change and > refuses to coninue (duh; what's the use of using dynamic libraries [no, > don't tell me about the reduced sizes of aps] if the ap refuses to take > advantage of library upgrades without a rebuild?)! Bradford, The xforms libraries are API compatible but not binary compatible. This means that when going from xforms 0.88 to 0.89 you'll have to recompile LyX. That's why we test to see if the library version has changed; better a controlled exit than a nasty and unpredictable crash. Note that xforms 0.89 has reached fix level 15 or so on linux systems, so it's probably pretty well de-bugged. I'm running here with 0.89 fix level 1 on a Dec Alpha and it's never done anything nasty to me. Angus
[Fwd: Re: Crash on second screen]
Original Message Subject: Re: Crash on second screen Date: Thu, 24 May 2001 13:14:48 -0700 From: Bradford Castalia [EMAIL PROTECTED] Organization: idaeim To: Allan Rae [EMAIL PROTECTED] References: [EMAIL PROTECTED] Allan Rae wrote: On Wed, 23 May 2001, Bradford Castalia wrote: More details: This system is using a Matrox G-400 AGP video board with dual head support. I am running a single X server (XFree86 4.0.2) configured for two screens (as reported in xdpyinfo) each of the same geometry (1152x864 24 planes, w/ TrueColor visuals). I do not want to use Xinerama; I prefer having two distinct screens. Could you send me privately your XF86Config-4 file? I have a G450 dual-head that I can test on. One other interesting thing might be to check if these crashes occur at other colour depths. There have been a couple of weird situations in the past where xforms hasn't worked at 24bit but has at 16bit colour. My /etc/X11/XF86Config file is being sent separately. I work only with 24-bit color. It wouldn't surprise me if the problem is in the XForms library. I have encountered some other software that only recognizes the first logical screen of an X display. Xinerama hides this by handling multiple physical framebuffers (video hardware) as a single logical screen on an X display. Which version of XForms are you using? Check in forms.h for FL_VERSION, FL_REVISION and FL_FIXLEVEL. They should all be together within the first 50 lines. The library, as reported by ldd, is /usr/X11R6/lib/libforms.so.0.88 and the version entries in /usr/X11R6/include/forms.h are: #define FL_VERSION 0 #define FL_REVISION 88 #define FL_FIXLEVEL1 This is the latest version reported on the XFreeBSD Ports site, though I see that there is a 0.89 version (last updated 2/00) that has not made it into a FreeBSD distribution package. I've tried downloading the FreeBSD binary distribution of v. 0.89 of the library from the Xforms site and using it with LyX. But the ap won't work with the new library, even though the API is compatible, because it detects the library version change and refuses to coninue (duh; what's the use of using dynamic libraries [no, don't tell me about the reduced sizes of aps] if the ap refuses to take advantage of library upgrades without a rebuild?)! Allan. (ARRae) -- Bradford Castalia [EMAIL PROTECTED] Systems Analyst http://azstarnet.com/~castalia idaeim 520-624-6629 Build an image in your mind, fit yourself into it. The Log of Cyradis, Seeress of Kell.
[Fwd: Re: Crash on second screen]
Original Message Subject: Re: Crash on second screen Date: Thu, 24 May 2001 13:14:48 -0700 From: Bradford Castalia <[EMAIL PROTECTED]> Organization: idaeim To: Allan Rae <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Allan Rae wrote: > > On Wed, 23 May 2001, Bradford Castalia wrote: > > > More details: > > > > This system is using a Matrox G-400 AGP video board with dual head > > support. I am running a single X server (XFree86 4.0.2) configured > > for two screens (as reported in xdpyinfo) each of the same geometry > > (1152x864 24 planes, w/ TrueColor visuals). > > > > I do not want to use Xinerama; I prefer having two distinct screens. > > Could you send me privately your XF86Config-4 file? I have a G450 > dual-head that I can test on. One other interesting thing might be to > check if these crashes occur at other colour depths. There have been a > couple of weird situations in the past where xforms hasn't worked at 24bit > but has at 16bit colour. > My /etc/X11/XF86Config file is being sent separately. I work only with 24-bit color. > > It wouldn't surprise me if the problem is in the XForms library. I > > have encountered some other software that only recognizes the first > > logical screen of an X display. Xinerama hides this by handling > > multiple physical framebuffers (video hardware) as a single logical > > screen on an X display. > > Which version of XForms are you using? Check in forms.h for FL_VERSION, > FL_REVISION and FL_FIXLEVEL. They should all be together within the first > 50 lines. > The library, as reported by ldd, is /usr/X11R6/lib/libforms.so.0.88 and the version entries in /usr/X11R6/include/forms.h are: #define FL_VERSION 0 #define FL_REVISION 88 #define FL_FIXLEVEL1 This is the latest version reported on the XFreeBSD Ports site, though I see that there is a 0.89 version (last updated 2/00) that has not made it into a FreeBSD distribution package. I've tried downloading the FreeBSD binary distribution of v. 0.89 of the library from the Xforms site and using it with LyX. But the ap won't work with the new library, even though the API is compatible, because it detects the library version change and refuses to coninue (duh; what's the use of using dynamic libraries [no, don't tell me about the reduced sizes of aps] if the ap refuses to take advantage of library upgrades without a rebuild?)! > Allan. (ARRae) -- Bradford Castalia [EMAIL PROTECTED] Systems Analyst http://azstarnet.com/~castalia idaeim 520-624-6629 "Build an image in your mind, fit yourself into it." The Log of Cyradis, Seeress of Kell.
Re: Crash on second screen
Lars Gullik Bjønnes wrote: Bradford Castalia [EMAIL PROTECTED] writes: | LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) | with the error message BadMatch (invalid parameter attributes). | Startup, with no command line arguments, completes with no apparent | problems. The Help menu is invoked and the Introduction document | selected. Status messages flash quickly in the bottom pane of the | LyX window; I think that an X Server action may happen just before | the crash. Ok... tell us (me) how to setup a second screen so that we can test this. % man xinit :) On a Linux system... * After starting the first X-Server (per run level 3 or so) * type Ctrl-Alt-F1 * login as normal user * xinit -- /usr/X11R6/bin/X :1 Stephan [EMAIL PROTECTED] | beusen Solutions GmbH fon: +49 30 549932-62| Landsberger Allee 366 fax: +49 30 549932-21| 12681 Berlin, Germany
Re: Crash on second screen
On Wed, 23 May 2001, Stephan Witt wrote: Hi Stephan! Lars Gullik Bjønnes wrote: Bradford Castalia [EMAIL PROTECTED] writes: | LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) | with the error message BadMatch (invalid parameter attributes). | Startup, with no command line arguments, completes with no apparent | problems. The Help menu is invoked and the Introduction document | selected. Status messages flash quickly in the bottom pane of the | LyX window; I think that an X Server action may happen just before | the crash. Ok... tell us (me) how to setup a second screen so that we can test this. % man xinit :) On a Linux system... * After starting the first X-Server (per run level 3 or so) * type Ctrl-Alt-F1 * login as normal user * xinit -- /usr/X11R6/bin/X :1 Note that this is _not_ the same as as the original problem. This will setup a second display, :1.0, but Bradford's problem was on the second screen of the first display :0.1. Maybe that is a minor difference for this report, maybe it isn't. Allan. (ARRae)
Re: Crash on second screen
On Tue, May 22, 2001 at 04:39:00PM -0700, Bradford Castalia wrote: LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) with the error message BadMatch (invalid parameter attributes). Startup, with no command line arguments, completes with no apparent problems. The Help menu is invoked and the Introduction document selected. Status messages flash quickly in the bottom pane of the LyX window; I think that an X Server action may happen just before the crash. It does not have this problem on the first screen (localhost:0.0). This version of LyX is from a pre-built FreeBSD port package (so I don't have a traceback for you, sorry) running on FreeBSD 4.2-STABLE with XFree86 Version 4.0.2. The display has two 1152x864 24-bit TrueColor screens (I have attached the xdpyinfo). I have attached the debug logs from running lyx -sync on screen 0 and screen 1. Note that keyboard shortcuts were used to invoke the menu selections. Maybe it is a problem with XForms. Do other XForms programs work correctly ?
Re: Crash on second screen
More details: This system is using a Matrox G-400 AGP video board with dual head support. I am running a single X server (XFree86 4.0.2) configured for two screens (as reported in xdpyinfo) each of the same geometry (1152x864 24 planes, w/ TrueColor visuals). I do not want to use Xinerama; I prefer having two distinct screens. It wouldn't surprise me if the problem is in the XForms library. I have encountered some other software that only recognizes the first logical screen of an X display. Xinerama hides this by handling multiple physical framebuffers (video hardware) as a single logical screen on an X display. -- Bradford Castalia [EMAIL PROTECTED] Systems Analyst http://azstarnet.com/~castalia idaeim 520-624-6629 Build an image in your mind, fit yourself into it. The Log of Cyradis, Seeress of Kell. Allan Rae wrote: On Tue, 22 May 2001, Bradford Castalia wrote: LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) with the error message BadMatch (invalid parameter attributes). Startup, with no command line arguments, completes with no apparent problems. The Help menu is invoked and the Introduction document selected. Status messages flash quickly in the bottom pane of the LyX window; I think that an X Server action may happen just before the crash. I have a dual head setup and can't repeat this. However, it is likely because I'm using the Xinerama module to get one big screen. It seems you are using two separate x-servers (one per screen). You might consider investigating the use of the Xinerama module and thereby letting X pretend it has one big screen. That is, both screens form part of localhost:0.0, there is no :0.1.** You need Option Xinerama in the Modules section. You also just define the two Screen sections as usual but combine them in the one Layout. The best instructions I found for this were at the matrox site (look for linux drivers and then read their howto/install guide). Allan. (ARRae) ** I have considered doing like you to try to get a virtual console and an X session on alternate monitors but decided against it. There's no going back from having 24x10inchs of screen space for X.
Re: Crash on second screen
Dekel Tsur wrote: On Tue, May 22, 2001 at 04:39:00PM -0700, Bradford Castalia wrote: LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) with the error message BadMatch (invalid parameter attributes). Startup, with no command line arguments, completes with no apparent problems. The Help menu is invoked and the Introduction document selected. Status messages flash quickly in the bottom pane of the LyX window; I think that an X Server action may happen just before the crash. It does not have this problem on the first screen (localhost:0.0). This version of LyX is from a pre-built FreeBSD port package (so I don't have a traceback for you, sorry) running on FreeBSD 4.2-STABLE with XFree86 Version 4.0.2. The display has two 1152x864 24-bit TrueColor screens (I have attached the xdpyinfo). I have attached the debug logs from running lyx -sync on screen 0 and screen 1. Note that keyboard shortcuts were used to invoke the menu selections. Maybe it is a problem with XForms. Do other XForms programs work correctly ? I agree: the problem is probably in the XForms library (unless the LyX developers are silly enough to bypass it and twiddle the X server directly ;-). The fdesign ap runs on the second screen, but I have not really used it sufficiently (I just ran it for the test purpose) to exercise whatever bug is stuck in the works. -- Bradford Castalia [EMAIL PROTECTED] Systems Analyst http://azstarnet.com/~castalia idaeim 520-624-6629 Build an image in your mind, fit yourself into it. The Log of Cyradis, Seeress of Kell.
Re: Crash on second screen
On Wed, 23 May 2001, Bradford Castalia wrote: More details: This system is using a Matrox G-400 AGP video board with dual head support. I am running a single X server (XFree86 4.0.2) configured for two screens (as reported in xdpyinfo) each of the same geometry (1152x864 24 planes, w/ TrueColor visuals). I do not want to use Xinerama; I prefer having two distinct screens. Could you send me privately your XF86Config-4 file? I have a G450 dual-head that I can test on. One other interesting thing might be to check if these crashes occur at other colour depths. There have been a couple of weird situations in the past where xforms hasn't worked at 24bit but has at 16bit colour. It wouldn't surprise me if the problem is in the XForms library. I have encountered some other software that only recognizes the first logical screen of an X display. Xinerama hides this by handling multiple physical framebuffers (video hardware) as a single logical screen on an X display. Which version of XForms are you using? Check in forms.h for FL_VERSION, FL_REVISION and FL_FIXLEVEL. They should all be together within the first 50 lines. Allan. (ARRae)
Re: Crash on second screen
Lars Gullik Bjønnes wrote: > > Bradford Castalia <[EMAIL PROTECTED]> writes: > > | LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) > | with the error message "BadMatch (invalid parameter attributes)". > | Startup, with no command line arguments, completes with no apparent > | problems. The Help menu is invoked and the Introduction document > | selected. Status messages flash quickly in the bottom pane of the > | LyX window; I think that an X Server action may happen just before > | the crash. > > Ok... tell us (me) how to setup a second screen so that we can test > this. > % man xinit :) On a Linux system... * After starting the first X-Server (per run level 3 or so) * type Ctrl-Alt-F1 * login as normal user * xinit -- /usr/X11R6/bin/X :1 Stephan <[EMAIL PROTECTED]> | beusen Solutions GmbH fon: +49 30 549932-62| Landsberger Allee 366 fax: +49 30 549932-21| 12681 Berlin, Germany
Re: Crash on second screen
On Wed, 23 May 2001, Stephan Witt wrote: Hi Stephan! > Lars Gullik Bjønnes wrote: > > > > Bradford Castalia <[EMAIL PROTECTED]> writes: > > > > | LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) > > | with the error message "BadMatch (invalid parameter attributes)". > > | Startup, with no command line arguments, completes with no apparent > > | problems. The Help menu is invoked and the Introduction document > > | selected. Status messages flash quickly in the bottom pane of the > > | LyX window; I think that an X Server action may happen just before > > | the crash. > > > > Ok... tell us (me) how to setup a second screen so that we can test > > this. > > > > % man xinit :) > > On a Linux system... > > * After starting the first X-Server (per run level 3 or so) > * type Ctrl-Alt-F1 > * login as normal user > * xinit -- /usr/X11R6/bin/X :1 Note that this is _not_ the same as as the original problem. This will setup a second display, :1.0, but Bradford's problem was on the second screen of the first display :0.1. Maybe that is a minor difference for this report, maybe it isn't. Allan. (ARRae)
Re: Crash on second screen
On Tue, May 22, 2001 at 04:39:00PM -0700, Bradford Castalia wrote: > LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) > with the error message "BadMatch (invalid parameter attributes)". > Startup, with no command line arguments, completes with no apparent > problems. The Help menu is invoked and the Introduction document > selected. Status messages flash quickly in the bottom pane of the > LyX window; I think that an X Server action may happen just before > the crash. > > It does not have this problem on the first screen (localhost:0.0). > > This version of LyX is from a pre-built FreeBSD port package (so I > don't have a traceback for you, sorry) running on FreeBSD 4.2-STABLE > with XFree86 Version 4.0.2. The display has two 1152x864 24-bit > TrueColor screens (I have attached the xdpyinfo). I have attached the > debug logs from running "lyx -sync" on screen 0 and screen 1. Note > that keyboard shortcuts were used to invoke the menu selections. Maybe it is a problem with XForms. Do other XForms programs work correctly ?
Re: Crash on second screen
More details: This system is using a Matrox G-400 AGP video board with dual head support. I am running a single X server (XFree86 4.0.2) configured for two screens (as reported in xdpyinfo) each of the same geometry (1152x864 24 planes, w/ TrueColor visuals). I do not want to use Xinerama; I prefer having two distinct screens. It wouldn't surprise me if the problem is in the XForms library. I have encountered some other software that only recognizes the first logical screen of an X display. Xinerama hides this by handling multiple physical framebuffers (video hardware) as a single logical screen on an X display. -- Bradford Castalia [EMAIL PROTECTED] Systems Analyst http://azstarnet.com/~castalia idaeim 520-624-6629 "Build an image in your mind, fit yourself into it." The Log of Cyradis, Seeress of Kell. Allan Rae wrote: > > On Tue, 22 May 2001, Bradford Castalia wrote: > > > LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) > > with the error message "BadMatch (invalid parameter attributes)". > > Startup, with no command line arguments, completes with no apparent > > problems. The Help menu is invoked and the Introduction document > > selected. Status messages flash quickly in the bottom pane of the > > LyX window; I think that an X Server action may happen just before > > the crash. > > I have a dual head setup and can't repeat this. However, it is likely > because I'm using the Xinerama module to get one big screen. It seems you > are using two separate x-servers (one per screen). You might consider > investigating the use of the Xinerama module and thereby letting X pretend > it has one big screen. That is, both screens form part of localhost:0.0, > there is no :0.1.** > > You need "Option Xinerama" in the Modules section. You also just define > the two Screen sections as usual but combine them in the one Layout. The > best instructions I found for this were at the matrox site (look for linux > drivers and then read their howto/install guide). > > Allan. (ARRae) > > ** I have considered doing like you to try to get a virtual console and an >X session on alternate monitors but decided against it. There's no >going back from having 24x10inchs of screen space for X.
Re: Crash on second screen
Dekel Tsur wrote: > > On Tue, May 22, 2001 at 04:39:00PM -0700, Bradford Castalia wrote: > > LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) > > with the error message "BadMatch (invalid parameter attributes)". > > Startup, with no command line arguments, completes with no apparent > > problems. The Help menu is invoked and the Introduction document > > selected. Status messages flash quickly in the bottom pane of the > > LyX window; I think that an X Server action may happen just before > > the crash. > > > > It does not have this problem on the first screen (localhost:0.0). > > > > This version of LyX is from a pre-built FreeBSD port package (so I > > don't have a traceback for you, sorry) running on FreeBSD 4.2-STABLE > > with XFree86 Version 4.0.2. The display has two 1152x864 24-bit > > TrueColor screens (I have attached the xdpyinfo). I have attached the > > debug logs from running "lyx -sync" on screen 0 and screen 1. Note > > that keyboard shortcuts were used to invoke the menu selections. > > Maybe it is a problem with XForms. > Do other XForms programs work correctly ? I agree: the problem is probably in the XForms library (unless the LyX developers are silly enough to bypass it and twiddle the X server directly ;-). The fdesign ap runs on the second screen, but I have not really used it sufficiently (I just ran it for the test purpose) to exercise whatever bug is stuck in the works. -- Bradford Castalia [EMAIL PROTECTED] Systems Analyst http://azstarnet.com/~castalia idaeim 520-624-6629 "Build an image in your mind, fit yourself into it." The Log of Cyradis, Seeress of Kell.
Re: Crash on second screen
On Wed, 23 May 2001, Bradford Castalia wrote: > More details: > > This system is using a Matrox G-400 AGP video board with dual head > support. I am running a single X server (XFree86 4.0.2) configured > for two screens (as reported in xdpyinfo) each of the same geometry > (1152x864 24 planes, w/ TrueColor visuals). > > I do not want to use Xinerama; I prefer having two distinct screens. Could you send me privately your XF86Config-4 file? I have a G450 dual-head that I can test on. One other interesting thing might be to check if these crashes occur at other colour depths. There have been a couple of weird situations in the past where xforms hasn't worked at 24bit but has at 16bit colour. > It wouldn't surprise me if the problem is in the XForms library. I > have encountered some other software that only recognizes the first > logical screen of an X display. Xinerama hides this by handling > multiple physical framebuffers (video hardware) as a single logical > screen on an X display. Which version of XForms are you using? Check in forms.h for FL_VERSION, FL_REVISION and FL_FIXLEVEL. They should all be together within the first 50 lines. Allan. (ARRae)
Crash on second screen
LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) with the error message BadMatch (invalid parameter attributes). Startup, with no command line arguments, completes with no apparent problems. The Help menu is invoked and the Introduction document selected. Status messages flash quickly in the bottom pane of the LyX window; I think that an X Server action may happen just before the crash. It does not have this problem on the first screen (localhost:0.0). This problem (or something very similar) was previous reported for Lyx version 1.1.5fix1: From: Torbjørn Sund Subject: Lyx crashes on second 8-bit screen Date: Thu, 28 Sep 2000 00:50:30 -0700 This version of LyX is from a pre-built FreeBSD port package (so I don't have a traceback for you, sorry) running on FreeBSD 4.2-STABLE with XFree86 Version 4.0.2. The display has two 1152x864 24-bit TrueColor screens (I have attached the xdpyinfo). I have attached the debug logs from running lyx -sync on screen 0 and screen 1. Note that keyboard shortcuts were used to invoke the menu selections. -- Bradford Castalia [EMAIL PROTECTED] Systems Analyst http://azstarnet.com/~castalia idaeim 520-624-6629 Build an image in your mind, fit yourself into it. The Log of Cyradis, Seeress of Kell. name of display:localhost:0.1 version number:11.0 vendor string:The XFree86 Project, Inc vendor release number:4002 maximum request size: 4194300 bytes motion buffer size: 256 bitmap unit, bit order, padding:32, LSBFirst, 32 image byte order:LSBFirst number of supported pixmap formats:7 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 4, bits_per_pixel 8, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 depth 32, bits_per_pixel 32, scanline_pad 32 keycode range:minimum 8, maximum 255 focus: window 0x1af, revert to PointerRoot number of extensions:28 BIG-REQUESTS DOUBLE-BUFFER DPMS Extended-Visual-Information FontCache GLX LBX MIT-SCREEN-SAVER MIT-SHM MIT-SUNDRY-NONSTANDARD RECORD SECURITY SGI-GLX SHAPE SYNC TOG-CUP X3D-PEX XC-APPGROUP XC-MISC XFree86-Bigfont XFree86-DGA XFree86-Misc XFree86-VidModeExtension XIE XInputExtension XKEYBOARD XTEST XVideo default screen number:1 number of screens:2 screen #0: dimensions:1152x864 pixels (322x241 millimeters) resolution:91x91 dots per inch depths (1):24 root window id:0x30 depth of root window:24 planes number of colormaps:minimum 1, maximum 1 default colormap:0x21 default number of colormap cells:256 preallocated pixels:black 0, white 16777215 options:backing-store NO, save-unders NO largest cursor:64x64 current input event mask:0x58207f KeyPressMask KeyReleaseMask ButtonPressMask ButtonReleaseMaskEnterWindowMask LeaveWindowMask PointerMotionMaskButtonMotionMask SubstructureNotifyMask SubstructureRedirectMask PropertyChangeMask number of visuals:4 default visual id: 0x24 visual: visual id:0x24 class:TrueColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits visual: visual id:0x25 class:TrueColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits visual: visual id:0x26 class:DirectColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits visual: visual id:0x27 class:DirectColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits screen #1: dimensions:1152x864 pixels (322x241 millimeters) resolution:91x91 dots per inch depths (1):24 root window id:0x32 depth of root window:24 planes number of colormaps:minimum 1, maximum 1 default colormap:0x29 default number of colormap cells:256 preallocated pixels:black 0, white 16777215 options:backing-store NO, save-unders NO largest cursor:1152x864 current input event mask:0x58207f KeyPressMask KeyReleaseMask ButtonPressMask
Re: Crash on second screen
Bradford Castalia [EMAIL PROTECTED] writes: | LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) | with the error message BadMatch (invalid parameter attributes). | Startup, with no command line arguments, completes with no apparent | problems. The Help menu is invoked and the Introduction document | selected. Status messages flash quickly in the bottom pane of the | LyX window; I think that an X Server action may happen just before | the crash. Ok... tell us (me) how to setup a second screen so that we can test this. -- Lgb
Re: Crash on second screen
On Tue, 22 May 2001, Bradford Castalia wrote: LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) with the error message BadMatch (invalid parameter attributes). Startup, with no command line arguments, completes with no apparent problems. The Help menu is invoked and the Introduction document selected. Status messages flash quickly in the bottom pane of the LyX window; I think that an X Server action may happen just before the crash. I have a dual head setup and can't repeat this. However, it is likely because I'm using the Xinerama module to get one big screen. It seems you are using two separate x-servers (one per screen). You might consider investigating the use of the Xinerama module and thereby letting X pretend it has one big screen. That is, both screens form part of localhost:0.0, there is no :0.1.** You need Option Xinerama in the Modules section. You also just define the two Screen sections as usual but combine them in the one Layout. The best instructions I found for this were at the matrox site (look for linux drivers and then read their howto/install guide). Allan. (ARRae) ** I have considered doing like you to try to get a virtual console and an X session on alternate monitors but decided against it. There's no going back from having 24x10inchs of screen space for X.
Crash on second screen
LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) with the error message "BadMatch (invalid parameter attributes)". Startup, with no command line arguments, completes with no apparent problems. The Help menu is invoked and the Introduction document selected. Status messages flash quickly in the bottom pane of the LyX window; I think that an X Server action may happen just before the crash. It does not have this problem on the first screen (localhost:0.0). This problem (or something very similar) was previous reported for Lyx version 1.1.5fix1: From: Torbjørn Sund Subject: Lyx crashes on second 8-bit screen Date: Thu, 28 Sep 2000 00:50:30 -0700 This version of LyX is from a pre-built FreeBSD port package (so I don't have a traceback for you, sorry) running on FreeBSD 4.2-STABLE with XFree86 Version 4.0.2. The display has two 1152x864 24-bit TrueColor screens (I have attached the xdpyinfo). I have attached the debug logs from running "lyx -sync" on screen 0 and screen 1. Note that keyboard shortcuts were used to invoke the menu selections. -- Bradford Castalia [EMAIL PROTECTED] Systems Analyst http://azstarnet.com/~castalia idaeim 520-624-6629 "Build an image in your mind, fit yourself into it." The Log of Cyradis, Seeress of Kell. name of display:localhost:0.1 version number:11.0 vendor string:The XFree86 Project, Inc vendor release number:4002 maximum request size: 4194300 bytes motion buffer size: 256 bitmap unit, bit order, padding:32, LSBFirst, 32 image byte order:LSBFirst number of supported pixmap formats:7 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 4, bits_per_pixel 8, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 depth 32, bits_per_pixel 32, scanline_pad 32 keycode range:minimum 8, maximum 255 focus: window 0x1af, revert to PointerRoot number of extensions:28 BIG-REQUESTS DOUBLE-BUFFER DPMS Extended-Visual-Information FontCache GLX LBX MIT-SCREEN-SAVER MIT-SHM MIT-SUNDRY-NONSTANDARD RECORD SECURITY SGI-GLX SHAPE SYNC TOG-CUP X3D-PEX XC-APPGROUP XC-MISC XFree86-Bigfont XFree86-DGA XFree86-Misc XFree86-VidModeExtension XIE XInputExtension XKEYBOARD XTEST XVideo default screen number:1 number of screens:2 screen #0: dimensions:1152x864 pixels (322x241 millimeters) resolution:91x91 dots per inch depths (1):24 root window id:0x30 depth of root window:24 planes number of colormaps:minimum 1, maximum 1 default colormap:0x21 default number of colormap cells:256 preallocated pixels:black 0, white 16777215 options:backing-store NO, save-unders NO largest cursor:64x64 current input event mask:0x58207f KeyPressMask KeyReleaseMask ButtonPressMask ButtonReleaseMaskEnterWindowMask LeaveWindowMask PointerMotionMaskButtonMotionMask SubstructureNotifyMask SubstructureRedirectMask PropertyChangeMask number of visuals:4 default visual id: 0x24 visual: visual id:0x24 class:TrueColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits visual: visual id:0x25 class:TrueColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits visual: visual id:0x26 class:DirectColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits visual: visual id:0x27 class:DirectColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits screen #1: dimensions:1152x864 pixels (322x241 millimeters) resolution:91x91 dots per inch depths (1):24 root window id:0x32 depth of root window:24 planes number of colormaps:minimum 1, maximum 1 default colormap:0x29 default number of colormap cells:256 preallocated pixels:black 0, white 16777215 options:backing-store NO, save-unders NO largest cursor:1152x864 current input event mask:0x58207f KeyPressMask KeyReleaseMask ButtonPressMask
Re: Crash on second screen
Bradford Castalia <[EMAIL PROTECTED]> writes: | LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) | with the error message "BadMatch (invalid parameter attributes)". | Startup, with no command line arguments, completes with no apparent | problems. The Help menu is invoked and the Introduction document | selected. Status messages flash quickly in the bottom pane of the | LyX window; I think that an X Server action may happen just before | the crash. Ok... tell us (me) how to setup a second screen so that we can test this. -- Lgb
Re: Crash on second screen
On Tue, 22 May 2001, Bradford Castalia wrote: > LyX version 1.1.6fix1 crashes on the second screen (localhost:0.1) > with the error message "BadMatch (invalid parameter attributes)". > Startup, with no command line arguments, completes with no apparent > problems. The Help menu is invoked and the Introduction document > selected. Status messages flash quickly in the bottom pane of the > LyX window; I think that an X Server action may happen just before > the crash. I have a dual head setup and can't repeat this. However, it is likely because I'm using the Xinerama module to get one big screen. It seems you are using two separate x-servers (one per screen). You might consider investigating the use of the Xinerama module and thereby letting X pretend it has one big screen. That is, both screens form part of localhost:0.0, there is no :0.1.** You need "Option Xinerama" in the Modules section. You also just define the two Screen sections as usual but combine them in the one Layout. The best instructions I found for this were at the matrox site (look for linux drivers and then read their howto/install guide). Allan. (ARRae) ** I have considered doing like you to try to get a virtual console and an X session on alternate monitors but decided against it. There's no going back from having 24x10inchs of screen space for X.
