Re: ssh -X Error: Can't open display: :0.0
On Tue, Dec 1, 2009 at 6:30 PM, Javier Barroso javibarr...@gmail.com wrote: On Tue, Dec 1, 2009 at 6:03 PM, Mathieu Malaterre mathieu.malate...@gmail.com wrote: On Tue, Dec 1, 2009 at 5:49 PM, Javier Barroso javibarr...@gmail.com wrote: Hi, On Tue, Dec 1, 2009 at 5:35 PM, Mathieu Malaterre mathieu.malate...@gmail.com wrote: Hi there, I am getting confused. I cannot get xclock to run on a remote host from my ssh session: local $ ssh -X mpi0 remote $ xclock Error: Can't open display: :0.0 But I can still do: local $ ssh -Xf mpi0 xclock Could someone please remind me what is the difference, and what am I missing in the first scenario ? Do you set DISPLAY variable in your login ? If you do you have to unset it (don't assign any value in any session config file). Ah ! That was the trick. I can now move on to the next issue, how to get mpirun to do ssh -X ... (since ForwardX11 yes is not honored...) Maybe the response is in mpi faq (search xterm): http://www.open-mpi.de/faq/?category=debugging Excellent FAQ indeed ! I think you will have to disable -nolisten option in X see this bug for reference: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539186 Hum, I did not understand what was going on in this bug report (very cryptic). Instead I used: $ mpirun -np 4 --hostfile ~/mpicluster -x DISPLAY=localhost:10 -x LIBGL_DEBUG=verbose /home/mpiuser/Kitware/VTK-gcc/bin/ParallelBFS Note that for some reason LIBGL_DEBUG=verbose avoids a crash I was getting: ERROR: In /home/mpiuser/Kitware/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 344 vtkXOpenGLRenderWindow (0x186b3b0): bad X server connection. DISPLAY=localhost:10 ERROR: In /home/mpiuser/Kitware/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 344 vtkXOpenGLRenderWindow (0x186b3b0): bad X server connection. DISPLAY=localhost:10 ERROR: In /home/mpiuser/Kitware/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 344 vtkXOpenGLRenderWindow (0x186b3b0): bad X server connection. DISPLAY=localhost:10 [dhcp-67-180:28173] *** Process received signal *** [dhcp-67-180:28173] Signal: Segmentation fault (11) [dhcp-67-180:28173] Signal code: Address not mapped (1) [dhcp-67-180:28173] Failing at address: 0xe0 [dhcp-67-180:28173] [ 0] /lib/libpthread.so.0 [0x7ffe19270a80] [dhcp-67-180:28173] [ 1] /usr/lib/libXt.so.6(_XtAppCreateShell+0x48) [0x7ffe1cc59198] [dhcp-67-180:28173] [ 2] /usr/lib/libXt.so.6(XtVaAppCreateShell+0x156) [0x7ffe1cc87466] [dhcp-67-180:28173] [ 3] /home/mpiuser/Kitware/VTK-gcc/bin/libvtkRendering.so.5.5(_ZN26vtkXRenderWindowInteractor10InitializeEv+0x597) [0x7ffe1e7cd837] [dhcp-67-180:28173] [ 4] /home/mpiuser/Kitware/VTK-gcc/bin/ParallelBFS(main+0x320) [0x409760] [dhcp-67-180:28173] [ 5] /lib/libc.so.6(__libc_start_main+0xe6) [0x7ffe187dc1a6] [dhcp-67-180:28173] [ 6] /home/mpiuser/Kitware/VTK-gcc/bin/ParallelBFS(__gxx_personality_v0+0x369) [0x409349] [dhcp-67-180:28173] *** End of error message *** -- mpirun noticed that process rank 0 with PID 28173 on node mpi0 exited on signal 11 (Segmentation fault). -- Since I am using nvidia driver, I do not think I can report that. -- Mathieu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ssh -X Error: Can't open display: :0.0
Mathieu Malaterre wrote: On Tue, Dec 1, 2009 at 6:30 PM, Javier Barroso javibarr...@gmail.com wrote: On Tue, Dec 1, 2009 at 6:03 PM, Mathieu Malaterre --deleted text-- Excellent FAQ indeed ! I think you will have to disable -nolisten option in X see this bug for reference: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539186 Hum, I did not understand what was going on in this bug report (very I looked at it too, and it seemed to me to be stating the issue was a user error. Message 40 indicates the user included server arguments to startx (-dpi 100), which apparently prevents reading of the X server startup files. In Message 45, the OP states I didn't realise that server arguments would bypass xserverrc. So it would seem to be not relevant to your problem. cryptic). Instead I used: $ mpirun -np 4 --hostfile ~/mpicluster -x DISPLAY=localhost:10 -x LIBGL_DEBUG=verbose /home/mpiuser/Kitware/VTK-gcc/bin/ParallelBFS Note that for some reason LIBGL_DEBUG=verbose avoids a crash I was getting: --deleted error text-- In my experience, this usually means a bad pointer, which in one case accesses memory in a location for which it has no permission or some such, and in the other case is not important. In any case, there's a problem you should report to someone, I think. Perhaps Nvidia? Since I am using nvidia driver, I do not think I can report that. -- Bob McGowan Symantec US Internationalization -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
ssh -X Error: Can't open display: :0.0
Hi there, I am getting confused. I cannot get xclock to run on a remote host from my ssh session: local $ ssh -X mpi0 remote $ xclock Error: Can't open display: :0.0 But I can still do: local $ ssh -Xf mpi0 xclock Could someone please remind me what is the difference, and what am I missing in the first scenario ? Thanks, -- Mathieu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ssh -X Error: Can't open display: :0.0
Hi, On Tue, Dec 1, 2009 at 5:35 PM, Mathieu Malaterre mathieu.malate...@gmail.com wrote: Hi there, I am getting confused. I cannot get xclock to run on a remote host from my ssh session: local $ ssh -X mpi0 remote $ xclock Error: Can't open display: :0.0 But I can still do: local $ ssh -Xf mpi0 xclock Could someone please remind me what is the difference, and what am I missing in the first scenario ? Do you set DISPLAY variable in your login ? If you do you have to unset it (don't assign any value in any session config file). Regards, -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ssh -X Error: Can't open display: :0.0
On Tue, Dec 1, 2009 at 5:49 PM, Javier Barroso javibarr...@gmail.com wrote: Hi, On Tue, Dec 1, 2009 at 5:35 PM, Mathieu Malaterre mathieu.malate...@gmail.com wrote: Hi there, I am getting confused. I cannot get xclock to run on a remote host from my ssh session: local $ ssh -X mpi0 remote $ xclock Error: Can't open display: :0.0 But I can still do: local $ ssh -Xf mpi0 xclock Could someone please remind me what is the difference, and what am I missing in the first scenario ? Do you set DISPLAY variable in your login ? If you do you have to unset it (don't assign any value in any session config file). Ah ! That was the trick. I can now move on to the next issue, how to get mpirun to do ssh -X ... (since ForwardX11 yes is not honored...) Thanks ! -- Mathieu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ssh -X Error: Can't open display: :0.0
Javier Barroso wrote: Error: Can't open display: :0.0 usr/X11R6/bin/xhost + ? -- Sincerely, Nicholas -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ssh -X Error: Can't open display: :0.0
On Tue, Dec 1, 2009 at 6:03 PM, Mathieu Malaterre mathieu.malate...@gmail.com wrote: On Tue, Dec 1, 2009 at 5:49 PM, Javier Barroso javibarr...@gmail.com wrote: Hi, On Tue, Dec 1, 2009 at 5:35 PM, Mathieu Malaterre mathieu.malate...@gmail.com wrote: Hi there, I am getting confused. I cannot get xclock to run on a remote host from my ssh session: local $ ssh -X mpi0 remote $ xclock Error: Can't open display: :0.0 But I can still do: local $ ssh -Xf mpi0 xclock Could someone please remind me what is the difference, and what am I missing in the first scenario ? Do you set DISPLAY variable in your login ? If you do you have to unset it (don't assign any value in any session config file). Ah ! That was the trick. I can now move on to the next issue, how to get mpirun to do ssh -X ... (since ForwardX11 yes is not honored...) Maybe the response is in mpi faq (search xterm): http://www.open-mpi.de/faq/?category=debugging I think you will have to disable -nolisten option in X see this bug for reference: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539186 Regards, Thanks ! -- Mathieu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Cannot get to KDE (X error)
Hello I have a big problem. I have a Debian testing system with a 2.6.18 kernel. It used to work normally, with no problems. But yesterday, when I started the computer, the X server couldn't start. It said something abuot not being able to find some fonts. I installed the xfs and fixed that. So, when I did startx, I entered a GNOME session (where I am now). But when I restart the computer, it starts normally but at the end, when it should start X server and go to KDM, the screen gets all yellow with some irregularities. I have a nvidia graphic card, and I use the nvidia driver. (I have been using it for a lot of time without any problem.) The last thing I did when the computer was running normally was installing gnomad2, libnjb and libmtp in order to use a Creative Zen V player, the only thing that affects that is udev, so I cannot find any relation between that and the X error. I have no more ideas If you need some more information, or anything else, please let me know. -- Intellectus luminis sicci non est recipit infusionem a voluntate et affectibus (Francis Bacon)
Re: Cannot get to KDE (X error)
On Sun, Jan 14, 2007 at 12:31:17 +0100, Jaume Alonso wrote: Hello I have a big problem. I have a Debian testing system with a 2.6.18 kernel. It used to work normally, with no problems. But yesterday, when I started the computer, the X server couldn't start. It said something abuot not being able to find some fonts. I installed the xfs and fixed that. So, when I did startx, I entered a GNOME session (where I am now). But when I restart the computer, it starts normally but at the end, when it should start X server and go to KDM, the screen gets all yellow with some irregularities. I have a nvidia graphic card, and I use the nvidia driver. (I have been using it for a lot of time without any problem.) The last thing I did when the computer was running normally was installing gnomad2, libnjb and libmtp in order to use a Creative Zen V player, the only thing that affects that is udev, so I cannot find any relation between that and the X error. I have no more ideas If you need some more information, or anything else, please let me know. We need to know the error messages and warnings from the Xorg log. Can you switch to a terminal (e.g. CTRL + ALT + F1) after X/kdm hangs? If so, run the following command and post its output here: egrep '^\((EE|WW)\)' /var/log/Xorg.0.log If your system is locked completely you can try to reboot into single user mode and run the same command. You can redirect its output to a file like this: egrep '^\((EE|WW)\)' /var/log/Xorg.0.log somefile.txt Then you can start gnome normally and include somefile.txt in the email message. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Cannot get to KDE (X error)
On Sun, Jan 14, 2007 at 12:31:17 +0100, Jaume Alonso wrote: Hello I have a big problem. I have a Debian testing system with a 2.6.18 kernel. It used to work normally, with no problems. But yesterday, when I started the computer, the X server couldn't start. It said something abuot not being able to find some fonts. I installed the xfs and fixed that. So, when I did startx, I entered a GNOME session (where I am now). But when I restart the computer, it starts normally but at the end, when it should start X server and go to KDM, the screen gets all yellow with some irregularities. I have a nvidia graphic card, and I use the nvidia driver. (I have been using it for a lot of time without any problem.) The last thing I did when the computer was running normally was installing gnomad2, libnjb and libmtp in order to use a Creative Zen V player, the only thing that affects that is udev, so I cannot find any relation between that and the X error. I have no more ideas If you need some more information, or anything else, please let me know. We need to know the error messages and warnings from the Xorg log. Can you switch to a terminal (e.g. CTRL + ALT + F1) after X/kdm hangs? If so, run the following command and post its output here: egrep '^\((EE|WW)\)' /var/log/Xorg.0.log If your system is locked completely you can try to reboot into single user mode and run the same command. You can redirect its output to a file like this: egrep '^\((EE|WW)\)' /var/log/Xorg.0.log somefile.txt Then you can start gnome normally and include somefile.txt in the email message. -- Regards, Florian -- Intellectus luminis sicci non est recipit infusionem a voluntate et affectibus (Francis Bacon) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cannot get to KDE (X error)
On Sun, Jan 14, 2007 at 14:54:18 +0100, Jaume Alonso wrote: I've been trying things: I have some kernels installed, so making this I can run gdm and then enter KDE: 1.- Enter the system with the kernel A 2.- Installing the nvidia driver 3.- running gdm. When I reboot the computer, I enter with kernel A and happens what I explained, It starts normally but when starts the X server, all the screen turns yellow. But then, I restart and enter the system with kernel B, and I get to tho console because it doesn't find the nvidia module. I reinstall it and I can get to gdm. So every time I boot the system, I have to choose a different kernel, and then reinstall the nvidia driver. That is a known issue of using the nvidia installer script with different kernels. The Debian nvidia packages provide a mechanism to fix this. For now I would propose to focus on the real problem without adding complexity. Now I'm at KDE doing this, and my /var/log/Xorg.0.log is this: [ /var/log/Xorg.0.log removed ] That does not help; we need the Xorg log right after a failed attempt. The next successful start of X/KDE will overwrite the information we are looking for. [ You lack of proper quoting and your top-posting make it very hard for other people to join the discussion. This decreases your chances of getting a helpful answer and it is also somewhat impolite. Please set up your email client correctly. ] -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Cannot get to KDE (X error)
I'm sorry for my top-posting and my lack of quotations. I've tryed to make it better, but I'm not actually subscribed to the list (I think I'm going to do it right now) and I'm reading your messages through the debian-mailing-list-archive. I've restarted the computer and I got the error. Then I rebooted the computer (it locks totally) and I run a Knoppix on a DVD and I copied the Xorg.0.log file. As far as I could see, the file is like the other one, but at some point it stops. I copy the ENTIRE file: X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 Build Operating System: UNKNOWN Current Operating System: Linux debian 2.6.18-3-686 #1 SMP Mon Dec 4 16:41:14 UTC 2006 i686 Build Date: 09 January 2007 Before reporting problems, check http://wiki.x.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/Xorg.0.log, Time: Sun Jan 14 16:44:50 2007 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Simple Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Acer Al1711 (**) | |--Device ASUS V9520 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts). (WW) FontPath is completely invalid. Using compiled-in default. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/X11R6/lib/X11/fonts/misc, /usr/share/fonts/X11/cyrillic, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/X11R6/lib/ X11/fonts/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (II) Open ACPI successful (/var/run/acpid.socket) (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.0 X.Org XInput driver : 0.6 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so (II) Module bitmap: vendor=X.Org Foundation compiled for 7.1.1, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules/libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.0 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2570 card 1043,80f2 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2571 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1d:0: chip 8086,24d2 card 1043,80a6 rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24d4 card 1043,80a6 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,24d7 card 1043,80a6 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:3: chip 8086,24de card 1043,80a6 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24dd card 1043,80a6 rev 02 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev c2 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,24d0 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,24db card 1043,80a6 rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:2: chip 8086,24d1 card 1043,80a6 rev 02 class 01,01,8f hdr 00 (II) PCI: 00:1f:5: chip 8086,24d5 card 1043,8152 rev 02 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0322 card 1043,80df rev a1 class 03,00,00 hdr 00 (II) PCI: 02:05:0: chip 11ab,4320 card 1043,811a rev 13 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) Intel Bridge workaround enabled (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 I/O range: [0] -1 0 0xd000 - 0xdfff (0x1000) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xfa00 - 0xfbef (0x1f0) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xf000 - 0xf8ff (0x900) MX[B] (II) Subtractive PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:30:0),
Re: Cannot get to KDE (X error)
On Sun, Jan 14, 2007 at 17:15:35 +0100, Jaume Alonso wrote: I'm sorry for my top-posting and my lack of quotations. I've tryed to make it better, but I'm not actually subscribed to the list (I think I'm going to do it right now) and I'm reading your messages through the debian-mailing-list-archive. You can ask for a CC if you are not subscribed. The problem is that people tend to forget the CC when the thread runs for a longer time. Using gmane (http://dir.gmane.org/gmane.linux.debian.user) might be a more convenient way to participate if you do not want to subscribe. I get the feeling that we have a misunderstanding about top-posting; please see http://people.cornell.edu/pages/kk288/du-guidelines.html for an explanation. I've restarted the computer and I got the error. Then I rebooted the computer (it locks totally) and I run a Knoppix on a DVD and I copied the Xorg.0.log file. As far as I could see, the file is like the other one, but at some point it stops. I copy the ENTIRE file: X Window System Version 7.1.1 [...] (--) PCI:*(1:0:0) nVidia Corporation NV34 [GeForce FX 5200] rev 161, [...] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor=NVIDIA Corporation compiled for 4.0.2, module version = 1.0.9746 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.1 (II) Loading extension GLX (II) LoadModule: nvidia (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so (II) Module nvidia: vendor=NVIDIA Corporation compiled for 4.0.2, module version = 1.0.9746 Module class: X.Org Video Driver [...] (II) Loading extension NV-GLX (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture (==) NVIDIA(0): Backing store disabled (==) NVIDIA(0): Silken mouse enabled (II) Loading extension NV-CONTROL (==) RandR enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (II) Initializing extension GLX [ end of the Xorg log file ] That looks like the driver goes into a hard lock when trying to initialize the GLX extension. I am not sure how to deal with that. Some suggestions: 1) Try an older version of the nvidia module, e.g. 1.0-8776. Maybe the latest driver is buggy. 2) If you have any fancy options in your xorg.conf, such as AllowGLXWithComposite or RenderAccel, turn them off and see if that makes a difference. 3) Maybe the nvidia user forums (http://forums.nvidia.com/) can offer more assistance. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cannot get to KDE (X error)
Hi, Finally I fixed it! If anyone has this problem, what I have done is to run apt-get remove --purge nvidia-glx. As it seems, this was conflicting with the nvidia driver. 2007/1/14, Florian Kulzer [EMAIL PROTECTED]: On Sun, Jan 14, 2007 at 17:15:35 +0100, Jaume Alonso wrote: I'm sorry for my top-posting and my lack of quotations. I've tryed to make it better, but I'm not actually subscribed to the list (I think I'm going to do it right now) and I'm reading your messages through the debian-mailing-list-archive. You can ask for a CC if you are not subscribed. The problem is that people tend to forget the CC when the thread runs for a longer time. Using gmane (http://dir.gmane.org/gmane.linux.debian.user) might be a more convenient way to participate if you do not want to subscribe. I get the feeling that we have a misunderstanding about top-posting; please see http://people.cornell.edu/pages/kk288/du-guidelines.html for an explanation. I've restarted the computer and I got the error. Then I rebooted the computer (it locks totally) and I run a Knoppix on a DVD and I copied the Xorg.0.log file. As far as I could see, the file is like the other one, but at some point it stops. I copy the ENTIRE file: X Window System Version 7.1.1 [...] (--) PCI:*(1:0:0) nVidia Corporation NV34 [GeForce FX 5200] rev 161, [...] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor=NVIDIA Corporation compiled for 4.0.2, module version = 1.0.9746 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.1 (II) Loading extension GLX (II) LoadModule: nvidia (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so (II) Module nvidia: vendor=NVIDIA Corporation compiled for 4.0.2, module version = 1.0.9746 Module class: X.Org Video Driver [...] (II) Loading extension NV-GLX (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture (==) NVIDIA(0): Backing store disabled (==) NVIDIA(0): Silken mouse enabled (II) Loading extension NV-CONTROL (==) RandR enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (II) Initializing extension GLX [ end of the Xorg log file ] That looks like the driver goes into a hard lock when trying to initialize the GLX extension. I am not sure how to deal with that. Some suggestions: 1) Try an older version of the nvidia module, e.g. 1.0-8776. Maybe the latest driver is buggy. 2) If you have any fancy options in your xorg.conf, such as AllowGLXWithComposite or RenderAccel, turn them off and see if that makes a difference. 3) Maybe the nvidia user forums (http://forums.nvidia.com/) can offer more assistance. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Intellectus luminis sicci non est recipit infusionem a voluntate et affectibus (Francis Bacon)
X Error of failed request: XF86DGANoDirectVideoMode
Bonsoir, la liste, Je suis entrain de configurer ma carte TV sous debian, c'est un hauppauge wintv usb, j'ai reussit à la faire fonctionner avec le driver usbvision. J'ai voulu utiliser xawtv pour regarder la télé, mais j'obtiens cette erreur: $xawtv This is xawtv-3.94, running on Linux/i686 (2.6.15.1) X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 137 (XFree86-DGA) Minor opcode of failed request: 1 (XF86DGAGetVideoLL) Serial number of failed request: 67 Current serial number in output stream: 67 J'ai trouvé sur google que l'on pouvais lancer xawtv en lui spécifiant de ne pas utiliser le dga. voilà ce que j'obtiens $xawtv -nodga This is xawtv-3.94, running on Linux/i686 (2.6.15.1) X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 137 (XFree86-DGA) Minor opcode of failed request: 1 (XF86DGAGetVideoLL) Serial number of failed request: 13 Current serial number in output stream: 13 v4l-conf had some trouble, trying to continue anyway WARNING: v4l and x11 disagree about the screen size WARNING: Is v4l-conf installed correctly? WARNING: v4l and x11 disagree about the color depth WARNING: fbuf.depth=0, x11 depth=32 WARNING: Is v4l-conf installed correctly? WARNING: overlay mode disabled Warning: Cannot convert string -*-ledfixed-medium-r-*--39-*-*-*-c-*-*-* to type FontStruct En utilisant le -nodga, xawtv se lance mais je n'ai pas d'image (l'ecran de xawtv reste noir) mais j'ai le son D'apres le message d'erreur il y a une probleme dans v4l-conf, mais si je lance v4l-conf j'ai le meme message d'erreur : $v4l-conf v4l-conf: using X11 display :0.0 dga: version 2.0 X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 137 (XFree86-DGA) Minor opcode of failed request: 1 (XF86DGAGetVideoLL) Serial number of failed request: 13 Current serial number in output stream: 13 Est ce que quelqu'un aurais une idée ?? je suis bloqué et je ne trouve pas de solution sur le net d'avance merci -- Jerome HEYMONET
X error : Major opcode: 151
I just used aptitude to upgrade my debian/unstable box (the previous full update was on 2006-03-19), and then several graphical programs are now having one same error. For some it is fatal, for some it only prints an error report. These errors don't happen _at all_ when I launch windowmaker instead of kde, and I absolutely don't know if this problem is specific to my box, or due to a bug in a package (and then which package..) Just in case it could be hardware-related, my video card is a nvidia GeForce2 with 32MB RAM, and my screen is set to 1680x1050 (16bpp), I'm using latest xorg server, with nv driver. Here are the reports from a few various programs, hoping someone might point me in the right direction : -- firefox and thunderbird : crashes on launch with : The program 'Gecko' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 418 error_code 1 request_code 151 minor_code 23) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) -- gqview : crashes on launch, The program 'gqview' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 143 error_code 1 request_code 151 minor_code 23) etc. -- gimp --verbose starts OK, until I click open then crashes The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 19546 error_code 1 request_code 151 minor_code 23) - knode : reports errors, works normally X Error: BadRequest (invalid request code or no such operation) 1 Major opcode: 151 Minor opcode: 23 Resource id: 0x3e4 it seems all KDE apps work (printing a few of those reports along the way), as overall my kde desktop and usual kde apps appear unaffected. -- opera : reports that same error, works normally
Re: X error : Major opcode: 151
On 12/04/06, Laura Palmer [EMAIL PROTECTED] wrote: I just used aptitude to upgrade my debian/unstable box (the previousfull update was on 2006-03-19), and then several graphical programsare now having one same error. For some it is fatal, for some it onlyprints an error report. These errors don't happen _at all_ when I launch windowmaker insteadof kde, and I absolutely don't know if this problem is specific to mybox, or due to a bug in a package (and then which package..)Just in case it could be hardware-related, my video card is a nvidia GeForce2 with 32MB RAM, and my screen is set to 1680x1050 (16bpp), I'musing latest xorg server, with nv driver.Here are the reports from a few various programs, hoping someone mightpoint me in the right direction : --firefoxand thunderbird : crashes on launch with :The program 'Gecko' received an X Window System error.This probably reflects a bug in the program.The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 418 error_code 1 request_code 151 minor_code 23)(Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)-- gqview : crashes on launch,The program 'gqview' received an X Window System error. This probably reflects a bug in the program.The error was 'BadRequest (invalid request code or no such operation)'.(Details: serial 143 error_code 1 request_code 151 minor_code 23)etc.-- gimp --verbose starts OK, until I click open then crashes The error was 'BadRequest (invalid request code or no such operation)'.(Details: serial 19546 error_code 1 request_code 151 minor_code 23)- knode : reports errors, works normallyX Error: BadRequest (invalid request code or no such operation) 1 Major opcode:151Minor opcode:23Resource id:0x3e4it seems all KDE apps work (printing a few of those reports along theway), as overall my kde desktop and usual kde apps appear unaffected. I had the same trouble. Upgrading to the latest xserver-xorg-core solves this (well, it did for me). I do not know how to link to my thread; You shall have to search the archive if you wish to find it. The thread is Upgrade xorg in Sid breaks link. -- —A watched bread-crumb never boils.—My hover-craft is full of eels.—[...]and that's the he and the she of it.
X error after dist-upgrade
I ran an apt-get dist-upgrade last night (amd64 testing) and now X errors on me saying (EE) Failed to load module nvidia (module does not exist, 0) But when I run lsmod it's still there. I've tried rebooting, unloading reloading the module, and even installing a newer kernel (2.6.15-1-em64t-p4-smp...I was on 2.6.12), but I still can't get X to start properly. Any suggestions? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X error after dist-upgrade
[EMAIL PROTECTED] schrieb: . . . X errors on me saying (EE) Failed to load module nvidia . . .can't get X to start properly. I got the same error some days ago when upgrading xorg. Xorg works normal again (apart from a hardly noticeable fraying of bold letters) after I have changed the line Drivernvidia to Drivernv in section Device of my file /etc/X11/xorg.conf. Yours Hans Vogelsberger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X error after dist-upgrade
[EMAIL PROTECTED] wrote: I ran an apt-get dist-upgrade last night (amd64 testing) and now X errors on me saying (EE) Failed to load module nvidia (module does not exist, 0) But when I run lsmod it's still there. I've tried rebooting, unloading reloading the module, and even installing a newer kernel (2.6.15-1-em64t-p4-smp...I was on 2.6.12), but I still can't get X to start properly. Any suggestions? Did your upgrade include changes to Xorg and its libraries? If so then you could try to rebuild the nvidia module. (You don't mention that in your mail.) I have found that my nvidia module breaks with almost every upgrade of Xorg. (This was not the case with XFree86.) Sometimes X still works, but direct rendering can no longer be enabled, and sometimes X does not start up at all. So far I could always fix these problems by re-running the nvidia-installer script; I assume that the module-wrapper needs to be recompiled against the newer versions of the X libraries. I cannot promise you anything for amd64 (I am on i686), but maybe it is worth a try. Regards, Florian P.S. Only after typing this I realized that you mention trying out a new kernel, therefore you probably did recompile the module-wrapper already. It might nevertheless be worthwhile to try again with the old kernel. (There might be some unrelated issue with 2.6.15 and the nvidia module.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X error after dist-upgrade
I found the solution after a few more hours on google. If X says the nvidia module can't be loaded, when lsmod says it is, then nvidia-glx probably isn't installed. For some reason apt-get dist-upgrade removed nvidia-glx. I suppose that's what I get for running sleep 8h; apt-get -y dist-upgrade. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
X Error: BadWindow (invalid Window parameter) 3
Using Unstable, KDE 3.5.1, gvim 6.4.6. To reproduce the problem do the following in konsole $dcopquit kicker $kicker $gvim exit the gvim window by entering :q After this, on the konsole there are error messages like $X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x383 Is this a known bug? Against which package should the bug be reported (gvim/kicker/konsole)? Can someone reproduce it? Is there a way to get rid of this problem? thanks raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
bastille -x: ERROR: Cannot use X interface because $DISPLAY not set.
Hallo Leute, der Titel enhält mein Problem. Wie kann ich dem abhelfen? Klaus
Re: bastille -x: ERROR: Cannot use X interface because $DISPLAY not set.
Also sprach Klaus Becker [EMAIL PROTECTED] (Sat, 12 Feb 2005 15:41:15 +0100): Hallo Leute, der Titel enhält mein Problem. Wie kann ich dem abhelfen? $ env ..sollte dir dein environment anzeigen. ist dort kein DISPLAY=wo? eintrag: $ export DISPLAY=machine:display damit setzt du die DISPLAY environment varible von der console. das ist, wo die application den Xserver finden kann auf dem das gui dargestellt werden soll. zb. localhost:0 fuer die box an der du arbeitest. willst du auf eine andere machine musst du dort mit xauth (oder mal schnell und unsicher mit xhost + machine) dem klienten die verbindung erlauben. willst du die DISPLAY permanent gesetzt haben, hilft ein eintrag in deiner ~/.bashrc oder generell fuer alle user am system in der /etc/profile* (und einige andere /etc/environment**). das sollte aber eigentlich richtig gesetzt sein. snip* DISPLAY=localhost:0 export DISPLAY snip snip** DISPLAY=localhost:0 ---snip Klaus sl ritch.
Re: bastille -x: ERROR: Cannot use X interface because $DISPLAY not set.
Le Samedi 12 Février 2005 16:24, Richard Mittendorfer a écrit : Also sprach Klaus Becker [EMAIL PROTECTED] (Sat, 12 Feb 2005 15:41:15 +0100): Hallo Leute, der Titel enhält mein Problem. Wie kann ich dem abhelfen? $ env ..sollte dir dein environment anzeigen. ist dort kein DISPLAY=wo? eintrag: $ export DISPLAY=machine:display damit setzt du die DISPLAY environment varible von der console. das ist, wo die application den Xserver finden kann auf dem das gui dargestellt werden soll. zb. localhost:0 fuer die box an der du arbeitest. willst du auf eine andere machine musst du dort mit xauth (oder mal schnell und unsicher mit xhost + machine) dem klienten die verbindung erlauben. willst du die DISPLAY permanent gesetzt haben, hilft ein eintrag in deiner ~/.bashrc oder generell fuer alle user am system in der /etc/profile* (und einige andere /etc/environment**). das sollte aber eigentlich richtig gesetzt sein. snip* DISPLAY=localhost:0 export DISPLAY snip Samit hat's geklappt, danke Klaus snip** DISPLAY=localhost:0 ---snip Klaus sl ritch.
X Error of failed request mit Ansys 71
Hallo, eine Anwendung (Ansys 71) stürzt bei Mausklick mit folgender Meldung ab: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 2 (X_ChangeWindowAttributes) Resource id in failed request: 0x0 Serial number of failed request: 4409 Current serial number in output stream: 4413 Debian Sarge Kernel 2.6.8-1-k7-smp XFree86 4.3.0.1 auf FSC V810 4 GB NVIDIA FX 1100 DH (sind auch zwei Monitore (21' SGI und 17' Nokia) angeschlossen) nvidiatreiber 1.0.6629 OpenGL geht... hat da vielleicht jemand 'ne gute Idee? Besten Dank schon mal. Gruss aus Mannheim Jens -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
How to get X error messages
Hello, when I've seen Linux for the very first time, it was on a friends' machine. IIRC he was running fvwm, and had a console-like window ( I think it was even named Console) where all the error messages of his X apps would scroll by (if any, ofc). From my current understanding, it would catch everything that any X app sends to STDERR. I think this could be useful, but have no clue how to get it. Some hints, or pointers? Keywords I could throw at Google? Please... cu, Schnobs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to get X error messages
On Fri, Mar 05, 2004 at 12:34:24PM +0100, Christian Schnobrich wrote: Hello, when I've seen Linux for the very first time, it was on a friends' machine. IIRC he was running fvwm, and had a console-like window ( I think it was even named Console) where all the error messages of his X apps would scroll by (if any, ofc). From my current understanding, it would catch everything that any X app sends to STDERR. I think this could be useful, but have no clue how to get it. Sounds like xconsole. It's in the xbase-clients package. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to get X error messages
Incoming from Colin Watson: On Fri, Mar 05, 2004 at 12:34:24PM +0100, Christian Schnobrich wrote: when I've seen Linux for the very first time, it was on a friends' machine. IIRC he was running fvwm, and had a console-like window ( I think it was even named Console) where all the error messages of his X apps would scroll by (if any, ofc). From my current understanding, it would catch everything that any X app sends to STDERR. I think this could be useful, but have no clue how to get it. Sounds like xconsole. It's in the xbase-clients package. And it displays what's sent to it, not just X apps. See the appropriate line in syslog.conf I've also found it a PITA to get it running correctly as a user. Modern whiz-bang window environments tend to be really flakey about remembering how to run something as a user that only root would ordinarily be allowed. I often found it popping up and refusing to display anything (permissions), or just exiting immediately. Eventually, after futzing with it for days, sometimes, depending on windowing environment, it finally, magically, works on login with no explanation offered. My only useful suggestion here: you don't have to futz with the default permissions and ownership of /dev/xconsole for it to work. I have it running here in Gnome Sawfish. I've never had any luck with it in KDE. YMMV. Good luck. -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fatal X error: how to diagnose?
I'm running the current Woody release. My graphics card is a Radeon 9200 SE. My problem is that the X server dies and restarts. It dies in 2 situations: (1) when the system is idle for 20 minutes or more. Following is a bunch of consecutive lines from syslog, when nobody was logged in: Feb 24 19:32:12 leo gdm[242]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 24 19:52:14 leo gdm[469]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 24 20:12:16 leo gdm[482]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 24 20:32:18 leo gdm[502]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 24 20:52:20 leo gdm[515]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 24 21:12:22 leo gdm[528]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 24 21:32:24 leo gdm[548]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 24 21:52:26 leo gdm[561]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 24 22:12:28 leo gdm[574]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 24 22:32:30 leo gdm[594]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 24 22:52:32 leo gdm[607]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 24 23:12:58 leo gdm[620]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 24 23:33:00 leo gdm[640]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 (2) When I run mplayer. This reliably kills the X server. Following is my XF86Config-4 file: ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type man XF86Config-4 at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the ### BEGIN DEBCONF SECTION line above, and/or after the # ### END DEBCONF SECTION line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file? in /usr/share/doc/xfree86-common/FAQ.gz. Section Files FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath/usr/lib/X11/fonts/misc FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi/:unscaled FontPath/usr/lib/X11/fonts/75dpi/:unscaled FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/lib/X11/fonts/Speedo FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/lib/X11/fonts/75dpi EndSection Section Module LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord Loadspeedo Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol PS/2 Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Generic Mouse Driver mouse Option SendCoreEventstrue Option Device/dev/input/mice Option Protocol ImPS/2 Option ZAxisMapping 4 5 EndSection Section Device Identifier Radeon 9200 SE Driver vesa EndSection Section Monitor Identifier Compaq V70 HorizSync 60-72 VertRefresh 76-86 Option DPMS EndSection Section Screen Identifier Default Screen Device Radeon 9200 SE Monitor Compaq V70 DefaultDepth24 SubSection Display Depth 1 Modes 1152x864 1024x768 EndSubSection SubSection Display Depth 4 Modes 1152x864 1024x768 EndSubSection SubSection Display Depth 8 Modes 1152x864 1024x768 EndSubSection SubSection Display Depth 15 Modes 1152x864 1024x768 EndSubSection
gdm_slave_xioerror_handler: Fatal X error
I'm using a Radeon SE 9200 card on the latest Debian Woody. Basically it works, using the vesa driver, except that X will sometimes restart, after the following appears in syslog: gdm[403]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 This happens in 2 situations that I have identified: 1. If the system is idle, it happens about once every 20 minutes. The immediate impact is that if you go away from the machine for more than 20 minutes, when you come back you've been logged out because X has restarted. 2. When mplayer is run. Anyone seen this? Suggestions? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
X Error of failed request: XF86DGANoDirectVideoMode
Ma ktos moze pomysl co moze byc przyczyna wykrzaczania sie programow w X? Oto co wypisuje: X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 136 (XFree86-DGA) Minor opcode of failed request: 2 (XF86DGADirectVideo) Serial number of failed request: 261 Current serial number in output stream: 262 Z gory dzieki za help. Pozdr. M.
X Error of failed request: XF86DGANoDirectVideoMode
Ma ktos moze pomysl co moze byc przyczyna wykrzaczania sie programow w X? Oto co wypisuje: X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 136 (XFree86-DGA) Minor opcode of failed request: 2 (XF86DGADirectVideo) Serial number of failed request: 261 Current serial number in output stream: 262 Z gory dzieki za help. Pozdr. M.
Re: X Error of failed request: XF86DGANoDirectVideoMode
On Thu, May 08, 2003 at 02:52:33PM +0200, Mikolaj Wielocha wrote: Ma ktos moze pomysl co moze byc przyczyna wykrzaczania sie programow w X? Oto co wypisuje: Jakich programów? Nie jestem pewien, ale to może wyglądać na nieustawione DGA w pliku konfiguracyjnym XFree86. -- (\ Rafał Bluszcz Zawadzki ::: GSM [+48] 604 856 821 \) http://bluszcz.ats.com.pl/ : bluszczatjabberpl.org /) / LRU #232814 Open Source Solutions :: Debian GNU/Linux (/ You haven't dream about me anymore, you've already have me
Re: X Error of failed request: XF86DGANoDirectVideoMode
On Thu, 08 May 2003 14:55:25 +0200 Mikolaj Wielocha [EMAIL PROTECTED] wrote: Ma ktos moze pomysl co moze byc przyczyna wykrzaczania sie programow w X? Oto co wypisuje: X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 136 (XFree86-DGA) Minor opcode of failed request: 2 (XF86DGADirectVideo) Serial number of failed request: 261 Current serial number in output stream: 262 Z gory dzieki za help. Może karta jest bez akceleratora i DGA nie działa przez to w iksach? -- Pozdrawiam, Michał Byrecki /* Play me online? Well, you know that I'll beat you If I ever meet you I'll control-alt-delete you */
Re: X Error of failed request: XF86DGANoDirectVideoMode
On Thu, May 08, 2003 at 10:52:11PM +0200, Michał Byrecki wrote: Minor opcode of failed request: 2 (XF86DGADirectVideo) Serial number of failed request: 261 Current serial number in output stream: 262 Może karta jest bez akceleratora i DGA nie działa przez to w iksach? W większości XF86Config-4'ów wyłączone jest DGA, stawiałbym na to. Chyba, że ma złe sterowniki do karty (u mnie ten problem pojawiał się przy złych sterownikach do ATI). -- .''`. Rafał Bluszcz Zawadzki ::: GSM [+48] 604 856 821 : :' : http://bluszcz.ats.com.pl/ : bluszczatjabberpl.org `. `' LRU #232814 Powered by Debian GNU/Linux = `-=== Veganism Now!
X error
DCOPServer up and running. Mutex destroy failure: Device or resource busy mcop warning: user defined signal handler found for SIG_PIPE, overriding QFont::setPointSize: Point size = 0 (-3) QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/DigitalClock) Negative sizes (2,-4) are not possible Se repete plusieurs fois! [...] Mutex destroy failure: Device or resource busy Mutex destroy failure: Device or resource busy WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 14 Se repete plusieurs fois! [...] kwin: X_SetInputFocus(0x22000c6): BadMatch (invalid parameter attributes) [...] WARNING: KDE detected X Error: BadAtom (invalid Atom parameter) 5 Major opcode: 17 WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 14 [...] QMenuData::removeItem: Index -1 out of range kdecore (KAccel): WARNING: Sym::initQt( ): failed to convert key. Se repete plusieurs fois! Si vous avez des pistes ! Pour info je suis sous woody avec kde3.0.4 et hier j ai installe gcc3.2 + fichiers dependances + reommnandes + docs Merci pour votre aide Ludo _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail
Re: X error
Rangdalf [EMAIL PROTECTED] wrote: WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 14 [...] QMenuData::removeItem: Index -1 out of range kdecore (KAccel): WARNING: Sym::initQt( ): failed to convert key. Si vous avez des pistes ! Pour info je suis sous woody avec kde3.0.4 et hier j ai installe gcc3.2 + fichiers dependances + reommnandes + docs Pas de piste, mais un conseil à 2 ¢ : une babasse performante est une babasse qui reste mince et consomme les bons paquets. Déjà vu un obèse hypertendu finir un marathon ? En clair : apt-get remove --purge kde* apt-get install [un gestionnaire de fenêtres mince et réputé stable tel que fvwm] et voilà le mammouth un peu dégraissé et plus présentable. _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail C'est quoi, un truc sexuel ? -- Philippe
Re: X error
Le Thu 21/11/2002, Philippe Glaziou disait Pas de piste, mais un conseil à 2 ¢ : une babasse performante est une babasse qui reste mince et consomme les bons paquets. Déjà vu un obèse hypertendu finir un marathon ? Vu l'évolution de debian, va bientôt falloir virer debain si on prend cette optique là... Quand on voit que lprng impose maintenant kerberos... (après xemacs qui impose postgresql et ldap...) -- Erwan
Re: [ze_mil@club-internet.fr: X error]
Branden Robinson wrote: Would someone help this user for me? - Forwarded message from Laurent Dubois [EMAIL PROTECTED] - From: Laurent Dubois [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: X error Message-ID: [EMAIL PROTECTED] Hello, I'm a french Debian user and I've just reinstall my system (kernel 2.4.1). But after installing Xfree86 4.0.2, I got a problem when I tried to launch it : X : cannot stat /etc/X11/X (No such file or directory), abording. I don't know what is the problem so I ask you if you can help me. Thank you, Laurent - End forwarded message - Try ln -s /etc/X11/X /usr/bin/X11/XFree86 -- LINUX~~nobody owns it~~everybody can use it~~anybody can improve it ~~~
RE: [ze_mil@club-internet.fr: X error]
This person probably installed/upgrade X 4.x on top of an existing X remove the entire X11 dir in /usr/bin/X11 reinstall X is the quickest way to make it work COULD take some reconfiguration for window managers etc. Joris -Original Message- From: mike polniak [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 07, 2001 6:57 PM To: debian-user@lists.debian.org Cc: Laurent Dubois Subject: Re: [EMAIL PROTECTED]: X error] Branden Robinson wrote: Would someone help this user for me? - Forwarded message from Laurent Dubois [EMAIL PROTECTED] - From: Laurent Dubois [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: X error Message-ID: [EMAIL PROTECTED] Hello, I'm a french Debian user and I've just reinstall my system (kernel 2.4.1). But after installing Xfree86 4.0.2, I got a problem when I tried to launch it : X : cannot stat /etc/X11/X (No such file or directory), abording. I don't know what is the problem so I ask you if you can help me. Thank you, Laurent - End forwarded message - Try ln -s /etc/X11/X /usr/bin/X11/XFree86 -- LINUX~~nobody owns it~~everybody can use it~~anybody can improve it ~~~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [ze_mil@club-internet.fr: X error]
Branden Robinson wrote: Would someone help this user for me? Dear Laurent, for sure you will found a quicker answer to your questions in the Debian mailing lists (for example debian-user =) instead contacting the packages maintainers... - Forwarded message from Laurent Dubois [EMAIL PROTECTED] - From: Laurent Dubois [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: X error Message-ID: [EMAIL PROTECTED] Hello, I'm a french Debian user and I've just reinstall my system (kernel 2.4.1). But after installing Xfree86 4.0.2, I got a problem when I tried to launch it : X : cannot stat /etc/X11/X (No such file or directory), abording. I don't know what is the problem so I ask you if you can help me. Look if you have the package xserver-xfree86 installed and if the symbolic link in /etc/X11/X point to /usr/X11R6/bin/XFree86... Next time your system is whining about some missing file, try looking on the Debian packages page (http://www.debian.org/distrib/packages), you will find two form, with the second (Search the Contents of the Latest Release) you can find in what package the missing file belongs... Hope this helps Andrea
[ze_mil@club-internet.fr: X error]
Would someone help this user for me? - Forwarded message from Laurent Dubois [EMAIL PROTECTED] - From: Laurent Dubois [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: X error Message-ID: [EMAIL PROTECTED] Hello, I'm a french Debian user and I've just reinstall my system (kernel 2.4.1). But after installing Xfree86 4.0.2, I got a problem when I tried to launch it : X : cannot stat /etc/X11/X (No such file or directory), abording. I don't know what is the problem so I ask you if you can help me. Thank you, Laurent - End forwarded message - -- G. Branden Robinson | If you make people think they're Debian GNU/Linux| thinking, they'll love you; [EMAIL PROTECTED] | but if you really make them think, http://www.debian.org/~branden/ | they'll hate you. pgpZf7damBozO.pgp Description: PGP signature
Re: X error
on Mon, Jan 01, 2001 at 09:28:57PM -0800, Bob Nielsen ([EMAIL PROTECTED]) wrote: I had a problem with woody several days ago where X would die immediately after starting, before the window manager took over. In trying to fix it, I really messed up my X installation, so I decided to downgrade to potato and did a fresh installation of 2.2r2. I did this and everything was working fine (including X). Since I had started with a somewhat minimal installation I just added a lot of new packages and now X dies immediately after starting with no messages, which is the same behaviour I had before with woody. System is a K6/2-350 with 128 MB, Cirrus 5430-based video card with 2048k videoram. Any ideas as to where I should be looking? How are you starting X? Command line or /etc/init.d scripts? Find an appropriate .xsession-errors file lying around anywhere? -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ Evangelist, Zelerate, Inc. http://www.zelerate.org What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/http://www.kuro5hin.org pgpwKXxWbaXQj.pgp Description: PGP signature
Re: X error
To quote Bob Nielsen [EMAIL PROTECTED], # I had a problem with woody several days ago where X would die # immediately after starting, before the window manager took over. In # trying to fix it, I really messed up my X installation, so I decided to # downgrade to potato and did a fresh installation of 2.2r2. I did this # and everything was working fine (including X). # # Since I had started with a somewhat minimal installation I just added a # lot of new packages and now X dies immediately after starting with no # messages, which is the same behaviour I had before with woody. # # System is a K6/2-350 with 128 MB, Cirrus 5430-based video card with # 2048k videoram. # # Any ideas as to where I should be looking? Lemme think. /etc/X11/Xwrapper.config /etc/X11/XF86Config[-4] and, if you're using GDM, /etc/X11/gdm/* (take a good look into the scripts in subdirectories there). Just a few thngs.
Re: X error
On Tue, Jan 02, 2001 at 12:22:39AM -0800, kmself@ix.netcom.com wrote: on Mon, Jan 01, 2001 at 09:28:57PM -0800, Bob Nielsen ([EMAIL PROTECTED]) wrote: I had a problem with woody several days ago where X would die immediately after starting, before the window manager took over. In trying to fix it, I really messed up my X installation, so I decided to downgrade to potato and did a fresh installation of 2.2r2. I did this and everything was working fine (including X). Since I had started with a somewhat minimal installation I just added a lot of new packages and now X dies immediately after starting with no messages, which is the same behaviour I had before with woody. System is a K6/2-350 with 128 MB, Cirrus 5430-based video card with 2048k videoram. Any ideas as to where I should be looking? How are you starting X? Command line or /etc/init.d scripts? Find an appropriate .xsession-errors file lying around anywhere? I use startx on the command line. There is no .xsession-errors (I think that only exists in X 4.x). Funny thing is that I can run win4lin with the fwin command with no problems. I just can't start an X session by itself. I've tried different window managers with no effect. This is what occurred with woody (running xserver-svga, not xserver-xfree86, since that appears to be slightly broken and won't support 1024x768 resolution on my card). There is a slight difference in what happens with potato and what happened with woody--in potato when it dies the line waiting for X server to shut down gets written, while in woody that message did not show up. I tried reinstalling xserver-common, xserver-svga, xfree86-common, xbase-clients and xlib6g, but that made no difference. I think I'll try uninstalling the X apps I added and see if the problem can be traced to the existence of a specific package, but I doubt it will help. Bob -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ Evangelist, Zelerate, Inc. http://www.zelerate.org What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/http://www.kuro5hin.org
Re: X error
On Tue, Jan 02, 2001 at 10:28:51AM -0800, Bob Nielsen wrote: On Tue, Jan 02, 2001 at 12:22:39AM -0800, kmself@ix.netcom.com wrote: on Mon, Jan 01, 2001 at 09:28:57PM -0800, Bob Nielsen ([EMAIL PROTECTED]) wrote: I had a problem with woody several days ago where X would die immediately after starting, before the window manager took over. In trying to fix it, I really messed up my X installation, so I decided to downgrade to potato and did a fresh installation of 2.2r2. I did this and everything was working fine (including X). Since I had started with a somewhat minimal installation I just added a lot of new packages and now X dies immediately after starting with no messages, which is the same behaviour I had before with woody. System is a K6/2-350 with 128 MB, Cirrus 5430-based video card with 2048k videoram. Any ideas as to where I should be looking? How are you starting X? Command line or /etc/init.d scripts? Find an appropriate .xsession-errors file lying around anywhere? I use startx on the command line. There is no .xsession-errors (I think that only exists in X 4.x). Funny thing is that I can run win4lin with the fwin command with no problems. I just can't start an X session by itself. I've tried different window managers with no effect. This is what occurred with woody (running xserver-svga, not xserver-xfree86, since that appears to be slightly broken and won't support 1024x768 resolution on my card). There is a slight difference in what happens with potato and what happened with woody--in potato when it dies the line waiting for X server to shut down gets written, while in woody that message did not show up. I tried reinstalling xserver-common, xserver-svga, xfree86-common, xbase-clients and xlib6g, but that made no difference. I think I'll try uninstalling the X apps I added and see if the problem can be traced to the existence of a specific package, but I doubt it will help. OK, removing most of the added X applications (I kept xterm and netscape) and now X is working again. I guess I need to reinstall them one-by-one to figure out which one is the culprit! Bob
X error
I had a problem with woody several days ago where X would die immediately after starting, before the window manager took over. In trying to fix it, I really messed up my X installation, so I decided to downgrade to potato and did a fresh installation of 2.2r2. I did this and everything was working fine (including X). Since I had started with a somewhat minimal installation I just added a lot of new packages and now X dies immediately after starting with no messages, which is the same behaviour I had before with woody. System is a K6/2-350 with 128 MB, Cirrus 5430-based video card with 2048k videoram. Any ideas as to where I should be looking? Bob
X error message
I recently started getting the following error message when I try to run xinit as a user: X: user not authorized to run the X server, aborting. I've been running XFree86 4 for awhile (about 2 months before it entered woody), and have never received this error message. I can't remember, but it seems the error showed up about 3 days ago, right after I upgraded several of the X packages. I can still run X as root, and can use xdm or gdm for users, but I prefer starting it from the command line, so that I can quickly open up an X session on another virtual terminal whenever I want. Any suggestions about what the problem might be? I would prefer to be using potato, but vmware demands a later libc6 that's not in that distribution. -- Lance Simmons (972)721-5274 - ...man will occasionally stumble over the truth, but usually manages to pick himself up, walk over or around it, and carry on. -- Winston Churchill
Re: X error message
On Monday 11 December 2000 07:46, Lance Simmons wrote: I recently started getting the following error message when I try to run xinit as a user: X: user not authorized to run the X server, aborting. I've been running XFree86 4 for awhile (about 2 months before it entered woody), and have never received this error message. I can't remember, but it seems the error showed up about 3 days ago, right after I upgraded several of the X packages. I can still run X as root, and can use xdm or gdm for users, but I prefer starting it from the command line, so that I can quickly open up an X session on another virtual terminal whenever I want. Any suggestions about what the problem might be? I would prefer to be using potato, but vmware demands a later libc6 that's not in that distribution. Have a look at /etc/X11/Xwrapper.config. Change the allowed_users from root to console (or anybody to use xdm/gdm etc.). HTH, jt
Re: nVidia geForce + X == error?
On Tue, Sep 05, 2000 at 08:38:55AM +0200, J.T. Wenting wrote: Is there an X server for geForce cards (specifically Asus V.6600)? Probing during Debian install did not detect a compatible card, it said... xfree86 3.3.6 - xserver-svga works fine with my geforce 256 I tried the experimental xfree86 4.0.1 deb packages (I think phase1v18 - http://www.debian.org/~branden) with kernel 2.4.0-test7 and the current nvidia drivers (0.9-4), but wasn't able to compile the nvidia kernel module. -ff -- Florian Friesdorf [EMAIL PROTECTED] OpenPGP key available on public key servers -- Save the future of Open Source -- - Online-Petition against Software Patents - -- http://petition.eurolinux.org --- pgpeDHjacijhi.pgp Description: PGP signature
nVidia geForce + X == error?
Is there an X server for geForce cards (specifically Asus V.6600)? Probing during Debian install did not detect a compatible card, it said... Jeroen T. Wenting [EMAIL PROTECTED] Murphy was wrong, things that can't go wrong will anyway
Re: nVidia geForce + X == error?
Is there an X server for geForce cards (specifically Asus V.6600)? Probing during Debian install did not detect a compatible card, it said... You may compile X 4.0.1 from source and nistall driver from nVidia (www.nvidia.com). It will give you the full power of hardware acceleration. -- Alexey Vyskubov (at home) Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
X-Error 'No type converter registered for String to Bitmap'
I reall need help for this: I have standard Debian GNU/Linux (Slink) 2.1. Since I have installed it (I tried to reinstall 3 times to get rid of it), I get following error in couple of X applications: No type converter registered for String to Bitmap conversion. This shows when I run xscreensaver on the screen, when I run gv or ghostscript (that's why it is annoying, for every printing-preview), and when I run couple of other X applications. Basically, every screen saver gives this error to the STERR and other X applications. Now, how to solve this? Or, how to register the type converter? Marko
Repeated X error...
Hi, I recently install x using the xserver-vga16 server, and everytime I run startx I get this: /usr/X11R6/lib/X11/xinit/xinitrc: /etc/X11/Xsession: No such file or directory waiting for X server to shutdown FreeFontPath: FPE /usr/X11R6/lib/X11/fonts/misc/ refcount is 2, should be 1; fixing. I get that output after the server shuts down. Please help, thanks in advance. Rob Hensley
xman: X Error of failed request: BadPixmap ...
Hola: Uso Debian 2.1. He observado que xman explota en cuanto intento acceder a ciertas secciones de las man (4,5,6,7, new) y me muestra un mensaje como éste en el error estándar: X Error of failed request: BadPixmap (invalid Pixmap parameter) Major opcode of failed request: 54 (X_FreePixmap) Resource id in failed request: 0x0 Serial number of failed request: 1385 Current serial number in output stream: 1392 ¿Cómo se arregla? Gracias. Saludos. -- [EMAIL PROTECTED] --- This message was sent by Mutt under Linux ---
Can someone interpret this X error message for me?
Hi folks,
I downloaded the xiraftools deb package from stable. It contains 3
programs: xtapemon, xgterm, and ximtool. The package installed no problem,
and the first two applications worked. However, the third program (which
of course was the one I really wanted to use!) gave me this X error:
~ {208} ximtool
[1] 15911
~ {209} Warning: Cannot convert string center to type Justify
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 72 (X_PutImage)
Serial number of failed request: 3679
Current serial number in output stream: 3684
[1]Exit 1ximtool
Now, I don't know anything about X programming, so can someone enlighten
me to what this means, and, more importantly, can I do anything about it?
Thanks,
David
Re: Can someone interpret this X error message for me?
On Sat, 22 May 1999, David Ballantyne wrote:
~ {208} ximtool
[1] 15911
~ {209} Warning: Cannot convert string center to type Justify
^^^
I'm no expert, but this looks like a font problem. I don't really know
more than that, but for what it's worth...
What does ximtool do, anyway?
Sincerely,
Ray Ingles (248) 377-7735 [EMAIL PROTECTED]
Improvements succeeded each other so rapidly, that machines which had
never been finished were abandoned in the hands of their makers,
because new improvements had superceded their utility.
Charles Babbage 'On the Economy of Manufactures' 1832
Re: Can someone interpret this X error message for me?
~ {208} ximtool
[1] 15911
~ {209} Warning: Cannot convert string center to type Justify
^^^
I'm no expert, but this looks like a font problem. I don't really know
more than that, but for what it's worth...
What does ximtool do, anyway?
ximtool is program to view and analyze astronomical images. Its usually
used along with the IRAF (the main analyis software for optical
astronomy), but it can be used on its own.
Actually, I think I might know what the answer is. According to some
astronomy software people, display tools like ximtool, SAOtng, or the
original SAOimage, can only work in 8bpp mode, as the need to set up the
Pseudocolor maps. I was trying to run ximtool in 24bpp. That might have
caused the problem. I still have to try it out though.
Cheers,
David
X Error
Hi, I have X installed in my new Debian 2.1.3 (Slink). Sometimes X stops and an error occurs. It says: Fatal Server Error: Hung in ApmSync() It seems that when this function is called it hungs my X (it seems that this function is important because it happens often and then I have to reboot linux because it is not possible to restart x. Can anyone be of help? Thanks, Paulo Jorge Matos aka PDestroy Minister of FortuneCity - Marina District http://www.fortunecity.com Personal Page : http://pdestroy.fortunecity.com E-mail : [EMAIL PROTECTED] Page me at : http://wwp.mirabilis.com/361853#pager SBN Level 2 Member HTML Writers Guild Member
weird x error?
this probably isn't a debian specific error, but i think it might have something to do with how i have the system set up. i'm logging in remotely to an SGI IRIX machine and attempting to run an X application. it fails with something like the following error: Error initializing colors for colormap i'm running in 32 bit color depth, and no color intensive processes are being displayed. (don't tell me that sgi has invented 64-bit color...right?) what does this mean? thanks. -alan
Re: weird x error?
this probably isn't a debian specific error, but i think it might have something to do with how i have the system set up. i'm logging in remotely to an SGI IRIX machine and attempting to run an X application. it fails with something like the following error: Error initializing colors for colormap I could probably help more if you were running Accelerated-X, as I know that X Server rather better than XFree86... but I have some wild guesses. Does the application require overlays? Some workstation applications expect to use both 24 bit and 8 bit windows. XFree86 does not support this, and very few PC graphics cards have the hardware to make this work. Some workstations, SGI boxes especially, have multiple color look up tables. This more usually has an effect when running in 8bpp, but it is possible that the unnamed application is trying to access mutually independent color look up tables. Pc Graphics hardware can not support more than a single 8 bit color look up table (which is why SGI boxes and some other workstations have less colormap flashing). There are a few chips that would help, which could be used on a PC graphics board, but they are expensive and used only by specialist board makers for unusual market segments. Are you sure that the application is not attempting to use SGI's DGL or SGI OpenGL's GLX? Depending upon where the error message is being generated, this might be the cause. Are you sure that the application requires 24 bit color? When running the application on the SGI box, displaying to the SGI display, use 'xwininfo' to find the color depth(s) of the applications windows. A message about running out of colors in a colormap suggests that the application is assuming the presence of a programmable colormap. This is normally only true in lower color depths (e.g. you get 8bpp PseudoColor Visuals, but 24bpp Pseudocolor Visuals are unknown as they'd need 48MB of high speed color look up table memory for the DAC; when most graphics board vendors are happy with 16MB of display memory, that would be rather unusual and expensive). i'm running in 32 bit color depth, and no color intensive processes are being displayed. (don't tell me that sgi has invented 64-bit color...right?) what does this mean? You are not actually running in 32 bit color depth. You are running in 24 bit color depth and using 32 bits to do it. 8 bits are being wasted. There are some real 32 bit color depth representations, such as using RGBA formats, but PC's don't do those. The nomenclature problem arises because Intel processors are particularly sensitive to word alignment. If you read a word and it is not aligned with a word boundary then you significantly decrease access. This is also trus to a greater or lesser extent for other processors, too. The color hardware uses 8 bits for each of the red, Green and Blue color guns in the tube. You therefore need 24 bits of color data. This would result in two in three data accesses being misaligned, if data were represented in system memory in contiguous 24 bit chunks. The consequence is an approximate 15% speed penalty. By wasting one byte for each pixel and aligning on a word boundary the speed penalty is removed, at the cost of an approximate 25% memory increase for each dynamically allocated graphical representation. However, it is possible to use 32 bits to store the 24 bit in system memory (accessible directly o the application) but to represent the data in packed form on the system bus and in the graphics board. Accelerated-X does this, which is one reason why our packed pixel representation does not cause application problems, but we still get the full 25% speed up that you'd expect from the better bandwidth utilisation. For some reason, XFree86 appear to have done the right thing in some variants of their Servers, but seem to have lost or forgotten the knowledge in the XFree86_SVGA Server for the Matrox Millennnium type boards. Although the XFree86 Server gains the 25% bus speed up, it then loses about 15% in systm memory access times, for a total speed up of only 10% or so. This is part of the reason that their Servers benchmark at about 50% of our speed. The real problem that using a 24 bit system representation causes is that application developers do not expect this format. Workstation developers use a 32 but system memory representation. All previous X Servers, including earlier XFree86 Server, use 32 bit system representation, instead of the bizarre form introduced last year by XFree86. Since it is a largely untestable format, as well as being rather unwise for maximum speed, I expect that quite a few applications will have unexpected problems. This is *not* a consequence of 24 bit packed pixel operation, but a consequence of presenting 24 bit packed pixels to the application. You could equally easily cause the same problem by using 24 bit packed representation to applications and then unpacking the data for the
X error
Hello I've bin getting an error when I try to start X, xinit: can't resolve symbol '_Xglobal_lock' xinit: can't resolve symbol '_XUnlockMutex_fn' xinit: can't resolve symbol '_XLockMutex_fn' I'm currently using hamm and AccelX 4.1, -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | Frt. Justin Schlottman CSP SP WP | |** | | [EMAIL PROTECTED] | |[EMAIL PROTECTED] | |** | |PGP: 0x035AC4FA 1998-04-09 | | http://spass.home.ml.org | | ICQ: 2232632 | -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- The greatest remedy for anger is delay. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
X error
I successfully compiled XFITSview (a program for viewing and manipulating images in the FITS format) on my machine (running the latest from unstable, including LessTif 0.82). However, when I try to run it, the program starts, I briefly see a couple windows flash on the screen, then they disappear, and the following message appears: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 78 (X_CreateColormap) Serial number of failed request: 915 Current serial number in output stream: 916 The above happens if I have started X as startx -- -bpp 16 However, if I have started X as startx -- -bpp 8 then XFITSview brings a message up saying Colormap full, create new one Is this a problem with XFITSview or is it a problem with my Xserver (xserver-mach64 version 3.3.1-2) or is it a problem with LessTif? Any ideas on what I can do to solve this problem? If further information would be helpful, I'll provide it. Thanks. James -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
X-error in xdvi
Hi, Recently, when I try to use xdvi, I get the following error: X Error of failed request: BadPixmap (invalid Pixmap parameter) Major opcode of failed request: 54 (X_FreePixmap) Resource id in failed request: 0x0 Serial number of failed request: 458 Current serial number in output stream: 472 Can anybody explain it ? l -- Aluisio Neves Fagundes - [EMAIL PROTECTED] Plasma Phys.Group - Phys.Institute - Univ. of Sao Paulo Cx.Postal 66318 -- 05315-970 Sao Paulo SP Brazil Phone: voice (011) 818-6908 --- Fax (011) 818-6749 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
BadPixmap - X Error
Hi, I'm having some error, mainly caused by/with xpaint, concerning BadPixmap, as shown by the bellow lines. Does someone know what I can do to correct this? The error occurs when trying to resize the window using mouse. X Error of failed request: BadPixmap (invalid Pixmap parameter) Major opcode of failed request: 54 (X_FreePixmap) Resource id in failed request: 0x0 Serial number of failed request: 12465 Current serial number in output stream: 12479 -- xpaint info: --- Package: xpaint Status: install ok installed Priority: optional Section: graphics Installed-Size: 411 Maintainer: Mark W. Eichin [EMAIL PROTECTED] Version: 2.4.8-1 Depends: libc5 (= 5.4.0-0), libjpeg6a (= 6a), libpng1 (= 0.88), libtiff3 (= 3.4beta035-1), xlib6 (= 3.2-0), xpm4.7 (= 3.4g-0), zlib1 (= 1.00) --- lib versions info: libc5: Source: libc Version: 5.4.33-3 libjpeg6a: Source: libjpeg Version: 6a-4 libpng: Source: libpng Version: 0.89c-6 libtiff3: Source: libtiff3 Version: 3.4beta035-1 xlib6: Source: xfree86 Version: 3.3-3 Replaces: elf-x11r6lib, xlib Provides: elf-x11r6lib xpm4.7: Source: xpm Version: 3.4g-9 zlib1: Source: zlib Version: 1:1.0.4-7 []s, Mario O.de Menezes mailto:[EMAIL PROTECTED] | Nuclear and Energetic Research Institute - IPEN-CNEN/SP BRAZIL | | http://curiango.ipen.br/~mario | There will be a day when every PC on the world will be a host, not a 'MyComputer'! - mom -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
X Error: xpaint vgen
Hi, I'm getting the following anoying error when executing some functions of xpaint e vgen programs: X Error of failed request: BadPixmap (invalid Pixmap parameter) Major opcode of failed request: 54 (X_FreePixmap) Resource id in failed request: 0x0 Serial number of failed request: 32677 Current serial number in output stream: 32833 Does somebody know what/where is the problem? I'm using Debian 1.3.1 and the following libs, among others: xpm4.7 xpm4.7-dev libtiff3 libjpeg6a libjpeg6a-dev libpng1 zlib1 xlib6-dev xaw3d xcompat xslib xlib6 Thanks, []s, Mario O.de Menezes mailto:[EMAIL PROTECTED] | Nuclear and Energetic Research Institute - IPEN-CNEN/SP BRAZIL | | http://curiango.ipen.br/~mario | There will be a day when every PC on the world will be a host, not a 'MyComputer'! - mom -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Weird X error with pthreads.
I have your basic X program, open a window and draw something on it, and when I link it with the pthreads library and try to run it I get : XIO: fatal IO error 0 (Unknown error) on X server :0.0 after 26 requests (24 known processed) with 0 events remaining. I'm not calling any functions that are in the pthreads library I'm just linking the library in. Does anyone know why I get this? -- Jason Killen Question Stupidity Mama's don't let your babies grow up to be Linux hackers Monolith : the new ANSI standard for humans PGP fingerprint = 64 71 48 14 31 AE C6 70 E4 4F 64 EB 3B AA 00 6B [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
