Bug#622308: xserver-xorg-video-intel: sporadic graphics corruption after upgrade to 2.6.38
On Tue, 2011-04-19 at 09:32 +0200, Cyril Brulebois wrote: > Nathan Stine (18/04/2011): > > On Mon, Apr 11, 2011 at 9:21 PM, Cyril Brulebois wrote: > > > We're AFAICT only lacking a package for latest libdrm; not sure > > > it's worth waiting until (say..) tomorrow for an updated libdrm > > > package to be available, I think opening a bug upstream is the > > > right thing to do. > > FWIW, we now have libdrm 2.4.25 in experimental, and x-x-v-intel > 2.15.0 is unstable; you may want to give them a shot before talking to > upstream. > > KiBi. Well, I've upgraded to 2.4.25 and the newest kernel in unstable. The problem isn't completely gone, but it's certainly a lot less noticeable. When I have the time, I'll still send the bug report upstream and keep you in the loop. Thanks, Nathan A. Stine -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1303950075.3152.6.camel@stine-1
Bug#622660: marked as done (xserver-xorg-video-vesa: The vesa video driver does not allow users on the console to execute "X")
Your message dated Wed, 27 Apr 2011 20:05:32 +0200 with message-id <20110427180532.gb2...@radis.liafa.jussieu.fr> and subject line Re: Bug#622660: xserver-xorg-video-vesa: The vesa video driver does not allow users on the console to execute "X" has caused the Debian Bug report #622660, regarding xserver-xorg-video-vesa: The vesa video driver does not allow users on the console to execute "X" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 622660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-vesa Version: 1:2.3.0-5 Severity: normal Executing "X" on a console (/dev/tty?) (a laptop computer) with the "vesa" video driver results in an error message: X: user not authorized to run the X server, aborting. The file "/etc/X11/Xwrapper.config" contains: allowed_users=console This parameter must then be changed to "anybody" to bypass the error. That should not be necessary. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jun 30 2009 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1783236 Mar 26 07:55 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Trident Microsystems TGUI 9660/938x/968x [1023:9660] (rev d3) Xorg X server configuration file status: -rw-r--r-- 1 root root 2712 Apr 13 00:24 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" FontPath "/usr/share/fonts/X11/misc,/usr/share/fonts/X11/75dpi/:unscaled" FontPath "/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/75dpi" FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" # FontPath "built-ins" EndSection Section "ServerFlags" Option "DefaultServerLayout""laptop" # Option "AIGLX" "no" # Option "GLX""no" Option "UseDefaultFontPath" "no" EndSection Section "InputClass" Identifier "evdev pointer catchall" MatchIsPointer "on" MatchDevicePath "/dev/input/event*" Driver "evdev" EndSection Section "Module" # Disable "dri" # Disable "dri2" # Disable "glx" # Load "glx" Load "evdev" EndSection Section "Device" Identifier "Configured Video Device" # Identifier "Trident Microsystems TGUI 9660/938x/968x" # Driver "trident" Driver "vesa" BusID "PCI:0:2:0" EndSection Section "Monitor" Identifier "Configured Monitor" HorizSync 38-40 VertRefresh 57-63 EndSection Section "Screen" Identifier "Default Screen" Device "Configured Video Device" # Device "Trident Microsystems TGUI 9660/938x/968x" Monitor "Configured Monitor" DefaultDepth16 SubSection "Display" Depth 1 Modes "800x600" EndSubSection SubSection "Display" Depth 4 Modes "800x600" EndSubSection SubSection "Display" Depth 8 Modes "800x600" EndSubSection SubSection "Display" Depth 15 Modes "800x600" EndSubSection SubSection "Display" Depth 16 Modes "800x600" EndSubSection SubSection "Display" Depth 24 Modes "800x600" EndSubSection EndSection Section "ServerLayout" Identifier "laptop" Screen "Default Screen" # InputDevice "Generic Keyboard" "CoreKeyboard" # InputDevice "Configured Mouse" "CorePointer" #
Bug#622553: xserver-xorg: Calling XFlush causes a crasch from XNextEvent under 64 bit squeeze
Please always keep the bug report in cc. On Wed, Apr 27, 2011 at 12:58:36 +0200, Leif Asbrink wrote: > Hello Julien, > > With some hesitation I changed my /etc/apt/sources.list > to use sid instead of squeeze for my 64 bit installation. > That way I got libx11-6=2:1.4.3-1 installed. > > That has eliminated the bug:-) > > The application that has the problem under squeeze is Linrad: > http://www.sm5bsz.com/linuxdsp/linrad.htm > > I have a 32 bit sid installation on that same laptop. I made it > as an upgrade from squeeze exactly as I now did with the 54 > bit installation, but 32 bit sid does not work. When I try > startx I just get a black screen with a mouse cursor on it. > I can move the mouse cursor and CtrlAltF1 brings me back to > the terminal. This problem with sid was the reason I hesitated > to upgrade the 64 bit squeeze to sid. > [...] > Can you tellme if/when the new libx11 will be introduced in > squeeze? > It won't. A targetted fix might, if it can be tracked down and is obvious enough to not cause regressions. Cheers, Julien -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110427110512.gq2...@radis.liafa.jussieu.fr
