Bug#430545: Display goes off at the mid of installation
reassign 430545 xresprobe retitle 430545 xresprobe breaks display at the middle of installation thank you nirupama rout wrote: Hi I have attached the text file for the output that i got for /usr/share/bug/xserver-xorg/script 31 This is not problem with one kind of PC and I have tried installing in acer pcs all show the same. As explained by Matthew earlier, this problem is probably caused by xresprobe probing available video modes. There is no easy way to fix it for now apart from not probing at all but that might generate buggy xorg.conf. However, we expect xresprobe to be dropped in the long term thanks to the server autoconfiguration features. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#430545: Display goes off at the mid of installation
Processing commands for [EMAIL PROTECTED]: reassign 430545 xresprobe Bug#430545: Display goes off at the mid of installation Bug reassigned from package `xserver-xorg-core' to `xresprobe'. retitle 430545 xresprobe breaks display at the middle of installation Bug#430545: Display goes off at the mid of installation Changed Bug title to `xresprobe breaks display at the middle of installation' from `Display goes off at the mid of installation'. thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437009: No window borders in latest Compiz
Tim Hull wrote: Package: compiz Version: 0.5.0.dfsg-2 Priority: important On Debian sid with the latest Compiz and X installed, running compiz --replace with an active Gnome/Metacity session results in there being no window borders. Compiz effects (cube, window effects, alt+tab, etc) all work, but none of my windows have window borders. I even tried unregistering the /apps/compiz settings in gconf, but it still doesn't work - hence Compiz is basically unusable. I'm using a MacBook with Intel GMA 950 graphics and the X.org http://X.org intel driver. No such problems were experienced with Compiz with the same system in Etch. Any warning? Is gtk-window-decorator running after starting compiz? if so, kill it and compiz --replace again and again? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437023: marked as done (xserver-xorg-input-kbd: X does not start if I upgrade the package)
Your message dated Fri, 10 Aug 2007 09:24:55 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#437023: xserver-xorg-input-kbd: X does not start if I upgrade the package has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: xserver-xorg-input-kbd Version: 1:1.1.0-4 Severity: critical Justification: breaks the whole system If I upgrade this package to the testing/unstable version, X refuses to start. Downgrading back to 1:1.1.0-4 helps. Excerpts from /var/log/Xorg.0.log: (**) |--Input Device Generic Keyboard (==) Keyboard: CustomKeycode disabled (II) LoadModule: keyboard (WW) Warning, couldn't open module keyboard (II) UnloadModule: keyboard (EE) Failed to load module keyboard (module does not exist, 0) (EE) No Input driver matching `keyboard' No core keyboard Fatal server error: failed to initialize core devices My /etc/X11/xorg.conf has: Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout fi EndSection -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.17-1-486 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-input-kbd depends on: ii libc6 2.5-11 GNU C Library: Shared libraries ii xserver-xorg-core 2:1.3.0.0.dfsg-6 X.Org X server -- core server xserver-xorg-input-kbd recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- reassign 437023 xserver-xorg-core fixed 437023 2:1.3.0.0.dfsg-8 thank you Mikko Heimola wrote: Package: xserver-xorg-input-kbd Version: 1:1.1.0-4 Severity: critical Justification: breaks the whole system If I upgrade this package to the testing/unstable version, X refuses to start. Downgrading back to 1:1.1.0-4 helps. You need to upgrade xserver-xorg-core to be uptodate in testing too. The disappearing to the keyboard driver in xserver-xorg-input-kbd 1.2 has been fixed by adding an alias in xserver-xorg-core 2:1.3.0.0.dfsg-8 (you only have -6). I guess we should have made sure people couldn't upgrade the former without the latter, but it may be to late now... Brice ---End Message---
Bug#420840: Regression: Device-specific resolution no longer supported on i915GM
Brice Goglin wrote: xrandr tells that max screen size is 1024x1024, which is false. Is there a way to tell the correct panel dimensions manually (versus DDC auto detection)? Add Virtual 2048 2048 to the Subsection Display in xorg.conf. But I don't think it will help here. With the new driver it didn't help, just as you expected. The screen was still 1024x768. But the 1.7 version began to believe that the screen is really 204x2048. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437023: xserver-xorg-input-kbd: X does not start if I upgrade the package
On Thu, 09 Aug 2007 08:51:01 +0300 Mikko Heimola wrote: If I upgrade this package to the testing/unstable version, X refuses to start. Downgrading back to 1:1.1.0-4 helps. You're running testing/unstable? So you did read /usr/share/doc/xserver-xorg-input-kbd/NEWS.Debian.gz? ;) keyboard is obsolete, one should use kbd instead. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#420840: Regression: Device-specific resolution no longer supported on i915GM
Brice Goglin wrote: Sergey Yanovich wrote: video-intel seems to reject this mode (exceeds panel dimensions). I can't find the corresponding code in the intel driver. Could you send the Xorg.0.log of this test? xrandr tells that max screen size is 1024x1024, which is false. Is there a way to tell the correct panel dimensions manually (versus DDC auto detection)? Add Virtual 2048 2048 to the Subsection Display in xorg.conf. But I don't think it will help here. Thanks for your time, Brice. Please find enclosed Xorg.0.log and xorg.conf with 'Virtual' set. Sergey X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Linux Debian Current Operating System: Linux host3 2.6.22-1-sony-tx770p #1 Wed Jul 25 22:12:34 EEST 2007 i686 Build Date: 14 July 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: Fri Aug 10 09:23:13 2007 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (**) |--Input Device Synaptics Touchpad (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) Including the default font path /usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType. (**) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/cyrillic, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (==) RgbPath set to /etc/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x81e50c0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.2 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2590 card 104d,81e2 rev 03 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,2592 card 104d,81e2 rev 03 class 03,00,00 hdr 80 (II) PCI: 00:02:1: chip 8086,2792 card 104d,81e2 rev 03 class 03,80,00 hdr 80 (II) PCI: 00:1b:0: chip 8086,2668 card 104d,81e2 rev 03 class 04,03,00 hdr 00 (II) PCI: 00:1d:0: chip 8086,2658 card 104d,81e2 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2659 card 104d,81e2 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,265a card 104d,81e2 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:3: chip 8086,265b card 104d,81e2 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,265c card 104d,81e2 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card , rev d3 class 06,04,01 hdr 01 (II) PCI: 00:1f:0: chip 8086,2641 card 104d,81e2 rev 03 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,266f card 104d,81e2 rev 03 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,266a card 104d,81e2 rev 03 class 0c,05,00 hdr 00 (II) PCI: 06:05:0: chip 104c,8031 card 2400, rev 00 class 06,07,00 hdr 82 (II) PCI: 06:05:2: chip 104c,8032 card 104d,81e2 rev 00 class 0c,00,10 hdr 80 (II) PCI: 06:05:3: chip 104c,8033 card 104d,81e2 rev 00 class 01,80,00 hdr 80 (II) PCI: 06:08:0: chip 8086,1069 card 104d,81e2 rev 03 class 02,00,00 hdr 00 (II) PCI: 06:0b:0: chip 8086,4220 card 8086,2751 rev 05 class 02,80,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,7), 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) Subtractive PCI-to-PCI bridge: (II) Bus 6:
Bug#389007: [Xorg-driver-ati] Bug#389007: Regression: Radeon 9200 powers off Apple Cinema Display connected via DVI
NoDDC set to true or false has no effect. The monitor is powered off with all combination of this option with either or both of the PanelSize and MonitorLayout commented out. NoDDC set to true or false with both PanelSize and MonitorLayout enabled result in a working monitor. Hi Roger, This bug should be forwarded in the upstream bugzilla to get good care, especially if it still does not work with latest 1:6.6.193-1 in experimental. Before I do so, you could test the randr-1.2 branch of the upstream git repository in case it helps. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#420840: Regression: Device-specific resolution no longer supported on i915GM
Sergey Yanovich wrote:
Please find enclosed Xorg.0.log and xorg.conf with 'Virtual' set.
Thanks. I don't think the Virtual size matters here. The driver seems to
be probing the panel dimensions wrong. But I don't see any option to
supersede it in this driver. It would be nice to test the latest
upstream git snapshot with the attached patch to see the panel
dimensions. To build it, you need to:
Get some development headers/libs:
$ apt-get build-dep xserver-xorg-video-intel
Then grab the git tree with:
$ git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel
Then enter it and apply the patch with
$ patch -p1 brice's patch file
Build with
$ ./autogen.sh
$ make
If it complains about some macros being undef, you might need to install
xutils-dev or so. Let me know.
Once it is built, copy src/.libs/intel_drv.so in
/usr/lib/xorg/modules/drivers/ and restart X (logout/login is usually
not enough, ctrl-alt-backspace or xdm/gdm restart is ok).
Once this is done, we'll know how bad the panel size dimension is
detected and we'll have enough information to forward this bug upstream.
Brice
diff --git a/src/i830_dvo.c b/src/i830_dvo.c
index cb461d7..22942a8 100644
--- a/src/i830_dvo.c
+++ b/src/i830_dvo.c
@@ -172,6 +172,9 @@ i830_dvo_mode_valid(xf86OutputPtr output, DisplayModePtr pMode)
/* XXX: Validate clock range */
if (drv-panel_fixed_mode) {
+ xf86Msg(X_WARNING,
+ i830_dvo_mode_valid: using panel dimensions %dx%d\n,
+ drv-panel_fixed_mode-HDisplay, drv-panel_fixed_mode-VDisplay);
if (pMode-HDisplay drv-panel_fixed_mode-HDisplay)
return MODE_PANEL;
if (pMode-VDisplay drv-panel_fixed_mode-VDisplay)
diff --git a/src/i830_lvds.c b/src/i830_lvds.c
index 18e5c2b..e8a9dcd 100644
--- a/src/i830_lvds.c
+++ b/src/i830_lvds.c
@@ -213,6 +213,9 @@ i830_lvds_mode_valid(xf86OutputPtr output, DisplayModePtr pMode)
if (pFixedMode)
{
+ xf86Msg(X_WARNING,
+ i830_lvds_mode_valid: Using panel dimensions %dx%d\n,
+ pFixedMode-HDisplay, pFixedMode-VDisplay);
if (pMode-HDisplay pFixedMode-HDisplay)
return MODE_PANEL;
if (pMode-VDisplay pFixedMode-VDisplay)
Bug#437023: xserver-xorg-input-kbd: X does not start if I upgrade the package
Package: xserver-xorg-input-kbd Version: 1:1.1.0-4 Severity: critical Justification: breaks the whole system If I upgrade this package to the testing/unstable version, X refuses to start. Downgrading back to 1:1.1.0-4 helps. Excerpts from /var/log/Xorg.0.log: (**) |--Input Device Generic Keyboard (==) Keyboard: CustomKeycode disabled (II) LoadModule: keyboard (WW) Warning, couldn't open module keyboard (II) UnloadModule: keyboard (EE) Failed to load module keyboard (module does not exist, 0) (EE) No Input driver matching `keyboard' No core keyboard Fatal server error: failed to initialize core devices My /etc/X11/xorg.conf has: Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout fi EndSection -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.17-1-486 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-input-kbd depends on: ii libc6 2.5-11 GNU C Library: Shared libraries ii xserver-xorg-core 2:1.3.0.0.dfsg-6 X.Org X server -- core server xserver-xorg-input-kbd recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421025: XCreateFontSet fails with fixed 13 as first font pattern in UTF-8 environment
Ben Hutchings wrote: If list-charset_list != NULL and list-charset_count == 0, the Xmalloc call in copy_string_list might return NULL (I don't know whether it supports a size of 0), causing copy_string_list and XCreateFontSet() to return NULL. This seems unlikely to be triggered only by the exact font pattern lists I identified though. By the way, did you try with libx11-6 2:1.1.3-1 currently in experimental? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421854: libx11-6: opera: xcb_xlib.c:52 xcb_xlib_unlock: Assertion 'c-xlib.lock' failed.Aborted
Is there anything new about this bug? Thanks, Brice Branden Robinson wrote: As I understand it, the XCB-linked Xlib has not yet propagated into unstable, so you must be running experimental libx11-6 packages. [Note to XSF: If I don't get to it first, please change the submitter on this report to Charlie Kroeger [EMAIL PROTECTED] as soon as it is convenient.] On Tue, May 01, 2007 at 11:43:09PM -0500, Charlie Kroeger wrote: Dear Mr. Robinson, This message I get when trying to start Opera from the command line: opera: xcb_xlib.c:52 xcb_xlib_unlock: Assertion 'c-xlib.lock' failed.Aborted I wrote the Opera Linux newsgroup and their man: Eirik Byrkjeflot Anonsen said: Ouch! This is a bug in xlib. Some people have been adding a new interface to X with some improvements over the old xlib stuff. The error message above says that the sequence of calls into xcb (the new interface) is wrong. Opera doesn't use xcb directly, so this is almost certainly a bug in xlib. I didn't know exactly where to file this report so I send it to you, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415588: modelines are ignored
Frederik Eaton wrote: Package: Xorg Version: 1:7.1.0-11 Severity: normal Hello, I have an Xorg configuration file which specifies a single modeline (1680x1050), a single display, and a single screen; however, when I run Xorg, this modeline is ignored, according to xrandr. To me, this seems inconsistent with the documentation: $ sudo X -config /home/frederik/xorg.conf.new -allowMouseOpenFail _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/taisa:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 X Window System Version 7.1.1 Unfortunately, all this code changed a lot since Xorg 7.1. What happens if you upgrade xserver-xorg-core to testing (2:1.3.0.0.dfsg-11)? I don't know whether there are some restriction regarding modelines with the vesa driver, but at least modelines seem to work fine with recent intel driver and Xserver core. (--) PCI:*(0:2:0) Intel Corporation unknown chipset (0x29a2) rev 2, Mem @ 0x9020/20, 0x8000/28, I/O @ 0x2140/3 This board is supported by the intel driver in testing. Try installing xserver-xorg-video-intel 2:2.1.0-2 and using intel instead of vesa in xorg.conf. It is supposed to detect supported modes automatically (as well as VertRefresh and HorizSync). ModeLine are only required if detected modes are not ok/enough. So the bug might irrelevant then. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#436923: psili/dasia problem
Processing commands for [EMAIL PROTECTED]: forwarded 436923 https://bugs.freedesktop.org/show_bug.cgi?id=11930 Bug#436923: Compose file problem with some Greek accents Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=11930. thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437066: xserver-xorg-video-intel: refuses 1366x768 because detects 1024x768 panel size
forwarded 437066 https://bugs.freedesktop.org/show_bug.cgi?id=11932 thank you Sergey Yanovich wrote: Brice Goglin wrote: The upstream developer thinks the panel size detection needs to be fixed. But, in order to look at it, he needs your Xorg.0.log after adding Option ModeDebug yes to the device section. Could you send this log when using the git snapshot that you built this morning? No problem. And xorg.conf for reference. Bug forwarded at the URL above, feel free to add any comment there if you think it could help. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#437066: xserver-xorg-video-intel: refuses 1366x768 because detects 1024x768 panel size
Processing commands for [EMAIL PROTECTED]: forwarded 437066 https://bugs.freedesktop.org/show_bug.cgi?id=11932 Bug#437066: xserver-xorg-video-intel: refuses 1366x768 because detects 1024x768 panel size Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=11932. thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423739: libgl1-mesa-dri: banding in rendering when using blending for transparency
Hi Dan, Thanks for all the testing you did for this bug report. I have forwarded it in the upstream bugzilla at https://bugs.freedesktop.org/show_bug.cgi?id=11931 Feel free to add any comment there if you think it could help (or if I missed something in my summary). There might be very few people competent and interested enough to fix this, your help might be important. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: bug 423739 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=11931
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 forwarded 423739 https://bugs.freedesktop.org/show_bug.cgi?id=11931 Bug#423739: libgl1-mesa-dri: banding in rendering when using blending for transparency Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=11931. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Bug#400189: xserver-xorg-video-nv: garbage output (6800 GS); renders vt1-6 unusable
Processing commands for [EMAIL PROTECTED]: forwarded 400189 https://bugs.freedesktop.org/show_bug.cgi?id=6212 Bug#400189: xserver-xorg-video-nv: garbage output (6800 GS); renders vt1-6 unusable Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=6212. thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#370709: xserver-xorg-video-nv: system hang in NVSync() when scrolling programs or terminal windows
On Wed, May 16, 2007 at 12:59:42AM +0200, Bernard Jungen wrote: On Sun, May 13, 2007 at 09:16:09PM +0200, Brice Goglin wrote: For now, the best would be to try with xserver-xorg-video-nv 2.0.2 (the one in unstable). If you can't upgrade to it because it brings lots of dependencies (such a libc6 2.5), you might want to rebuild it. It should be easy. I choose the rebuild route, but it'll be low precedence on my todo list, especially since my workaround is reliable enough for now. Did you have a chance to test a newer driver? Either 2.0.2 or the latest 2.1.2? So, no problem for me if you close this Debian bug, as upstream is aware of it. I'd rather keep it open, anybody else using Debian and having the same bug would open a new one or so. I will add a comment on upstream bug #6161 when I'll have some feedback from you. thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400189: xserver-xorg-video-nv: garbage output (6800 GS); renders vt1-6 unusable
forwarded 400189 https://bugs.freedesktop.org/show_bug.cgi?id=6212 thank you On Sun, May 13, 2007 at 07:19:15AM +1000, Andrew Vaughan wrote: Ok. I rebuilt the 2.0.2-1 source package on Etch and installed/tested on Etch. (Let me know if you expect this to be fixed in conjunction with other packages from unstable). The bug is still present. (I also checked 1.2.0-3 which shipped with Etch). Ok thanks. I found an old upstream bug at the above URL with the same issues. I am marking your bugreport as forwarded there, and I posted a comment there saying it still occured with 2.0.2. Feel free to add any comment there if you think it could help. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436923: psili/dasia problem
forwarded 436923 https://bugs.freedesktop.org/show_bug.cgi?id=11930 thank you Jan Willem Stumpel wrote: I suppose it can _also_ be cured by making the reverse substitution (U0313 -- U1313 etc.) in /usr/share/X11/xkb/symbols/gr, which is part of the xkb-data package; so it is unclear where the blame for this bug lies. I supposed wrongly. Making this reverse substitution in the xkb file does _not_ cure the problem. Don't know why. I have forwarded this bug on the upstream bugzilla at the URL above. Feel free to add any comments there if you think it could help. I know nothing about Greek accents and I don't have a Greek polytonic keyboard, so I won't be able to help much :) Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 437023
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 tags 437023 sid lenny Bug#437023: xserver-xorg-input-kbd: X does not start if I upgrade the package There were no tags set. Tags added: sid, lenny End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Processed (with 1 errors): cloning 420840, submitter -1, found -1 in 2:2.1.0-2 ..., bug -1 is not forwarded
Processing commands for [EMAIL PROTECTED]: unmerge 420840 Bug#420840: xserver-xorg-video-intel: custom resolution set with 915resolution doesn't work anymore, Xorg falls back to 1280x1024 Bug#435621: xserver-xorg-video-i810: won't run at 1366x768 after upgrade to lenny Disconnected #420840 from all other report(s). clone 420840 -1 Bug#420840: xserver-xorg-video-intel: custom resolution set with 915resolution doesn't work anymore, Xorg falls back to 1280x1024 Bug 420840 cloned as bug 437066. merge 420840 435621 Bug#420840: xserver-xorg-video-intel: custom resolution set with 915resolution doesn't work anymore, Xorg falls back to 1280x1024 Bug#435621: xserver-xorg-video-i810: won't run at 1366x768 after upgrade to lenny Merged 420840 435621. submitter -1 Sergey Yanovich [EMAIL PROTECTED] Bug#437066: xserver-xorg-video-intel: custom resolution set with 915resolution doesn't work anymore, Xorg falls back to 1280x1024 Changed Bug submitter from Tino Keitel [EMAIL PROTECTED] to Sergey Yanovich [EMAIL PROTECTED]. found -1 2:2.1.0-2 Bug#437066: xserver-xorg-video-intel: custom resolution set with 915resolution doesn't work anymore, Xorg falls back to 1280x1024 Bug marked as found in version 2:2.1.0-2. retitle -1 xserver-xorg-video-intel: refuses 1366x768 because detects 1024x768 panel size Bug#437066: xserver-xorg-video-intel: custom resolution set with 915resolution doesn't work anymore, Xorg falls back to 1280x1024 Changed Bug title to `xserver-xorg-video-intel: refuses 1366x768 because detects 1024x768 panel size' from `xserver-xorg-video-intel: custom resolution set with 915resolution doesn't work anymore, Xorg falls back to 1280x1024'. notforwarded -1 Bug#437066: xserver-xorg-video-intel: refuses 1366x768 because detects 1024x768 panel size Removed annotation that Bug had been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=10784. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432847: /usr/bin/xload: xload needs a way to limit range of values it can display
Unfortunately, most tiny X programs like this one usually don't get much maintenance. So you should probably try to come with a patch if you really want this to be implemented :/ Fair enough. If I find the time ... Eddy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432847: /usr/bin/xload: xload needs a way to limit range of values it can display
Edward Welbourne wrote: This could readilly enough be remedied by providing a command-line option, --clip-at=n, to tell xload to not try to display any load level above n. More fancy solutions are possible. closer inspection of the man page suggests this could be implemented as an optional second value for -scale: Unfortunately, most tiny X programs like this one usually don't get much maintenance. So you should probably try to come with a patch if you really want this to be implemented :/ Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#437023: xserver-xorg-input-kbd: X does not start if I upgrade the package
Processing commands for [EMAIL PROTECTED]: reassign 437023 xserver-xorg-core Bug#437023: xserver-xorg-input-kbd: X does not start if I upgrade the package Bug reassigned from package `xserver-xorg-input-kbd' to `xserver-xorg-core'. fixed 437023 2:1.3.0.0.dfsg-8 Bug#437023: xserver-xorg-input-kbd: X does not start if I upgrade the package Bug marked as fixed in version 2:1.3.0.0.dfsg-8. thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion
Clayton wrote: On Thu, 09 Aug 2007 10:05:21 +0200 Brice Goglin [EMAIL PROTECTED] wrote: Clayton wrote: Brice, I just added the testing version of only xserver-xorg-core to the snapshot.debian.net/archive/2007/03/08/debian/ version of xorg. And then booted into a blank screen. After downgrading xserver-xorg-core back down to snapshot.debian.net/archive/2007/03/08/debian/ everything Hum, these URL are the same :) One of them is version 1.1.1-20. The other is probably 1.3 something. And I guess xserver-xorg-video-siliconmotion is still 1.4.1, right? Everything works under snapshot.debian.net/archive/2007/03/08/debian/ -- xserver-xorg-core=2:1.1.1-19 -- xserver-xorg-video-siliconmotion=1:1.4.1-4 Replace above xserver-xorg-core (and nothing else changes) with xserver-xorg-core=2:1.3.0.0.dfsg-11 from testing and it breaks. Thanks a lot for the clarification, I'll notify the upstream developer. He's supposed to look at the problem soon. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436336:
Antoine Cailliau wrote: Installing the git version of the driver seems to solve the problem I had. I had a very similar problem but my display was not unrestorable only when I switched to VT but also on suspend-to-disk, -to-ram, logout, shutdown, reboot... Systematically my computer hard freeze. Good to know, thanks for the followup. Joshua, did you have a chance to test it? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436336:
Installing the git version of the driver seems to solve the problem I had. I had a very similar problem but my display was not unrestorable only when I switched to VT but also on suspend-to-disk, -to-ram, logout, shutdown, reboot... Systematically my computer hard freeze. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437023: xserver-xorg-input-kbd: X does not start if I upgrade the package
On Fri, 10 Aug 2007, Evgeni Golov wrote: You're running testing/unstable? So you did read /usr/share/doc/xserver-xorg-input-kbd/NEWS.Debian.gz? ;) No, as I was not aware of the existence of such files (nor of apt-listchanges) until now. keyboard is obsolete, one should use kbd instead. This fixed the problem, thank you. -- Mikko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion
On Thu, 09 Aug 2007 10:05:21 +0200 Brice Goglin [EMAIL PROTECTED] wrote: Clayton wrote: Brice, I just added the testing version of only xserver-xorg-core to the snapshot.debian.net/archive/2007/03/08/debian/ version of xorg. And then booted into a blank screen. After downgrading xserver-xorg-core back down to snapshot.debian.net/archive/2007/03/08/debian/ everything Hum, these URL are the same :) One of them is version 1.1.1-20. The other is probably 1.3 something. And I guess xserver-xorg-video-siliconmotion is still 1.4.1, right? Everything works under snapshot.debian.net/archive/2007/03/08/debian/ -- xserver-xorg-core=2:1.1.1-19 -- xserver-xorg-video-siliconmotion=1:1.4.1-4 Replace above xserver-xorg-core (and nothing else changes) with xserver-xorg-core=2:1.3.0.0.dfsg-11 from testing and it breaks. Clayton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319388: [libglu1-xorg] should hide C++ interfaces
On Sat, Feb 17, 2007 at 01:23:26PM -0800, Zack Weinberg wrote: On 2/17/07, Brice Goglin [EMAIL PROTECTED] wrote: If you are still interested in fixing this problem, I would appreciate if you could send an updated patch. But please do not prepare it against Mesa 6.5.1 in Etch (such a change won't be accepted in Etch anyway). You should prepare it against Mesa 6.5.2-3 in experimental (where the Mesa packaging has been getting a large rework). I will see if I can find time to do this, but it may be several weeks. Is there any deadline approaching? Hi Zack, Any news about this? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315589: xlibmesa-gl: opengl programs freeze system
On Thu, Mar 01, 2007 at 04:24:19PM -0500, Ashif Harji wrote: Are you still running XFree86/Sarge? If so, could you try Xorg/Etch? Yes, I am still running XFree86/Sarge. Unfortunately, I can't update that machine at the moment. ashif. Hi Ashif, Did you have a chance to try reproducing on Etch? Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366830: marked as done (libgl1-mesa-dri: segfault in r300_dri in _tnl_RenderClippedLine)
Your message dated Fri, 10 Aug 2007 09:49:06 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#366830: libgl1-mesa-dri: segfault in r300_dri in _tnl_RenderClippedLine has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libgl1-mesa-dri Version: 6.4.1-0.4 Severity: normal Hello, When running flightgear and simulation time is at night, it crashes in r300_dri.so with fillowing backtrace: (gdb) bt #0 0x2b0c31004849 in _tnl_RenderClippedLine () from /usr/lib/dri/r300_dri.so #1 0x2b0c3100ca9d in _tnl_RenderClippedLine () from /usr/lib/dri/r300_dri.so #2 0x2b0c30ff168d in _tnl_run_pipeline () from /usr/lib/dri/r300_dri.so #3 0x2b0c30ff74ec in _tnl_playback_vertex_list () from /usr/lib/dri/r300_dri.so #4 0x2b0c30f91d4b in _mesa_save_EvalMesh1 () from /usr/lib/dri/r300_dri.so #5 0x2b0c30f92266 in _mesa_CallList () from /usr/lib/dri/r300_dri.so #6 0x2b0c274acb09 in ssgVtxTable::draw () from /usr/lib/libplibssg.so.1.8.4 #7 0x2b0c2748f96d in _ssgDrawDList () from /usr/lib/libplibssg.so.1.8.4 #8 0x2b0c2748a1a7 in ssgCullAndDraw () from /usr/lib/libplibssg.so.1.8.4 #9 0x0041fedd in std::operator+char, std::char_traitschar, std::allocatorchar () #10 0x004485e2 in std::vectorSGSharedPtrSGPropertyNode, std::allocatorSGSharedPtrSGPropertyNode ::operator= () #11 0x2b0c27d56e6a in glutJoystickGetCenter () from /usr/lib/libglut.so.3 #12 0x2b0c27d5a6a9 in fgEnumWindows () from /usr/lib/libglut.so.3 #13 0x2b0c27d573e5 in glutMainLoopEvent () from /usr/lib/libglut.so.3 #14 0x2b0c27d57d40 in glutMainLoop () from /usr/lib/libglut.so.3 #15 0x0041e63f in ?? () #16 0x0041ae33 in ?? () #17 0x2b0c293454ca in __libc_start_main () from /lib/libc.so.6 #18 0x0041ac8a in ?? () #19 0x7fe83e88 in ?? () #20 0x2b0c2550a9c0 in ?? () from /lib64/ld-linux-x86-64.so.2 #21 0x0001 in ?? () #22 0x7fe84a77 in ?? () #23 0x in ?? () Feel free to ask additional information. If you tell me how to build debugging version, I can provide full backtrace or even a core dump. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.16-1-amd64-k8 Locale: LANG=C, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Versions of packages libgl1-mesa-dri depends on: ii libgl1-mesa-glx 6.4.1-0.4 A free implementation of the OpenG libgl1-mesa-dri recommends no packages. -- no debconf information -- Jan 'Bulb' Hudec [EMAIL PROTECTED] signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Version: 7.0.1-1 This bug is very probably fixed in latest mesa release, maybe even earlier. If not, please let me know. Brice ---End Message---
Bug#437066: xserver-xorg-video-intel: refuses 1366x768 because detects 1024x768 panel size
Sergey Yanovich wrote: Brice Goglin wrote: Once this is done, we'll know how bad the panel size dimension is detected and we'll have enough information to forward this bug upstream. Please find enclosed Xorg.0.log with video-intel at git20070810+your patch. (WW) i830_lvds_mode_valid: Using panel dimensions 1024x768 Thanks a lot for testing this so fast. The driver does not detect the right panel size (or the hardware does not expose it correctly). I will forward this problem upstream, either to fix the driver detection or to request an Option PanelSize to override the detection. Since this is a different bug than the original submitter of #420840, I have cloned it into a new bug report (#437066). I am keeping #420840 for its original submitter. Please only use the new #437066 when replying about the panel size being wrongly detected. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#428556: Pressing Fn-CRT/LCD garbles display
Processing commands for [EMAIL PROTECTED]: forwarded 428556 https://bugs.freedesktop.org/show_bug.cgi?id=10785 Bug#428556: Pressing Fn-CRT/LCD garbles display Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=10785. tags 428556 +wontfix Bug#428556: Pressing Fn-CRT/LCD garbles display There were no tags set. Tags added: wontfix thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428556: Pressing Fn-CRT/LCD garbles display
forwarded 428556 https://bugs.freedesktop.org/show_bug.cgi?id=10785 tags 428556 +wontfix thank you On Tue, Jun 12, 2007 at 05:20:30PM +0200, Simon Josefsson wrote: Hi! I have had this problem with all releases of the driver that I've tried since installing debian on this machine, but never gotten around to report it. I now installed the package in experimental to see if it had been solved, but it wasn't. Is there any point in testing the version in unstable too? I have a Dell Precision M65 laptop (see http://josefsson.org/etch-dell-m65.html) with a nVidia Quadro FX 350M. When I press Fn-CRT/LCD it cycles through some modes. The modes seems to be somewhat influenced on the state when I started the machine, e.g., with lid closed or open, connected to port repliactor or not. In any case, it is typically is some variation of: 1. Internal TFT 2. Black 3. External TFT via DVI The video changing works but with a flaw: after changing between video modes, the screen is sort of shifted to the right so that only half of the screen image is visible in the middle of the screen. The left and right sides of the screen is blank. Two photos: http://josefsson.org/bug/ As you can see, it happens both on the internal screen and on the external DVI screen. The work around is simple: just press ctrl-alt-f1 and then go back to the virtual console with X. The image looks fine and everything works. Debug X log attached. Any ideas how I can avoid the ctrl-alt-f1 step and have it work correctly immediately? Your problem looks like the upstream bug at the URL above. Unfortunately, the nVidia maintainer tagged it as wontfix because the nv driver can't support VBIOS-controlled hotkey switching. So I am marking this as wontfix too, sorry :( Fortunately, ctrl-alt-f1 is not too bad as a workaround :/ Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436923: psili/dasia problem
I wrote: I suppose it can _also_ be cured by making the reverse substitution (U0313 -- U1313 etc.) in /usr/share/X11/xkb/symbols/gr, which is part of the xkb-data package; so it is unclear where the blame for this bug lies. I supposed wrongly. Making this reverse substitution in the xkb file does _not_ cure the problem. Don't know why. And of course I also made a mistake by reporting this as a bug in xlibs-data. It is libx11-data nowadays. JWS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 436923 to libx11-data
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 reassign 436923 libx11-data Bug#436923: Compose file problem with some Greek accents Bug reassigned from package `xkb-data' to `libx11-data'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: bug 383953 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=11936
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 forwarded 383953 https://bugs.freedesktop.org/show_bug.cgi?id=11936 Bug#383953: xkb-data: Keyboard layout Asus 6000 series laptop not supported Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=11936. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437207: xserver-xorg-video-i810: OpenGL crashes, only after a suspend
Package: xserver-xorg-video-i810 Version: 2:2.1.0-2 Severity: important I've consistently found that after a suspend to RAM, many GL applications fail to render correctly, or sometimes completely lock up the system. GL behaves fine up until after the first suspend. A workaround is to restart the X server after each suspend, though this is obviously not ideal. In more detail, symptoms occur with programs such as bzflag or xmoto, but oddly enough, never glxgears. Either the rendering will be exceedingly dark, such that I can't tell if the rendering is otherwise correct or not, or the screen will fill entirely with multicoloured fuzz and the machine will crash entirely (can't switch to a virtual terminal, can't ping on the network). The graphics hardware is reported by the X logs as Intel Corporation 82852/855GM Integrated Graphics Device rev 2. Richard -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.20.3-ubuntu1rt (PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-video-i810 depends on: ii xserver-xorg-video-intel 2:2.1.0-2 X.Org X server -- Intel i8xx, i9xx xserver-xorg-video-i810 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437207: xserver-xorg-video-i810: OpenGL crashes, only after a suspend
On Sat, Aug 11, 2007 at 01:24:40 +0100, Richard Thrippleton wrote: I've consistently found that after a suspend to RAM, many GL applications fail to render correctly, or sometimes completely lock up the system. GL behaves fine up until after the first suspend. A workaround is to restart the X server after each suspend, though this is obviously not ideal. In more detail, symptoms occur with programs such as bzflag or xmoto, but oddly enough, never glxgears. Either the rendering will be exceedingly dark, such that I can't tell if the rendering is otherwise correct or not, or the screen will fill entirely with multicoloured fuzz and the machine will crash entirely (can't switch to a virtual terminal, can't ping on the network). The graphics hardware is reported by the X logs as Intel Corporation 82852/855GM Integrated Graphics Device rev 2. Please run '/usr/share/bug/xserver-xorg-core/script 31' and send the output to this bug. Cheers, Julien signature.asc Description: Digital signature
Bug#437207: xserver-xorg-video-i810: OpenGL crashes, only after a suspend
On Sat Aug 11 02:38, Julien Cristau wrote: Please run '/usr/share/bug/xserver-xorg-core/script 31' and send the output to this bug. Attached. This was run on a fresh X server before a suspend. Do you want a second output from after a suspend? Richard Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2006-05-01 15:34 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1742256 2007-07-14 19:30 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rwxr-xr-x 1 root root 3940 2006-07-15 10:35 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (Xorg 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 commands as root: # # cp /etc/X11/xorg.conf /etc/X11/xorg.conf.custom # md5sum /etc/X11/xorg.conf /var/lib/xfree86/xorg.conf.md5sum # dpkg-reconfigure xserver-xorg Section Files # if the local font server has problems, we can fall back on these FontPath/usr/share/fonts/X11/misc FontPath/usr/share/fonts/X11/misc FontPath/usr/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi/:unscaled FontPath/usr/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/share/fonts/X11/Type1 FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/CID FontPath/usr/share/fonts/X11/CID FontPath/usr/lib/X11/fonts/CID FontPath/usr/share/fonts/X11/100dpi FontPath/usr/share/fonts/X11/100dpi FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi FontPath/usr/share/fonts/X11/75dpi FontPath/usr/lib/X11/fonts/75dpi EndSection Section ServerFlags Option DontZap true EndSection Section Module Loadbitmap Loaddbe Loadddc Loaddri Loadevdev Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout gb EndSection #Section InputDevice # Identifier Configured Mouse # Driver mouse # Option CorePointer # Option Device/root/serio0 # Option Protocol ImPS/2 # Option Emulate3Buttons true # Option ZAxisMapping 4 5 # Option HorizScrollDelta 0 #EndSection Section InputDevice Identifier Synaptics Touchpad Driver synaptics Option CorePointer Option SendCoreEventstrue Option Device/dev/input/mice # Option Protocol auto-dev Option HorizScrollDelta 0 EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option SendCoreEventstrue Option Device/dev/input/mouse1 # Option Protocol auto-dev Option HorizScrollDelta 0 EndSection Section Device Identifier Intel Corporation 82852/855GM Integrated Graphics Device Driver i810 EndSection Section Monitor Identifier Generic Monitor Option DPMS EndSection Section Screen Identifier Default Screen Device Intel Corporation 82852/855GM Integrated Graphics Device Monitor Generic Monitor DefaultDepth24 SubSection Display Depth
Bug#156115: This is what Microsoft Windows95 does, though this may change in the future.
{H}{u}(g)[e] (N)ew[s] To I_mpact {C}[Y](T)V
Chi^na Y_ouTV (C){o}r[p].
S+ymbol: {C}(Y)[T]{V}
We [h](a)(v)e a.lready {s}[e]{e}{n} CYTV*'s mar^ket imp`act befo,re cl*imbi.ng to {o}(v)e{r} $_2.00 (w)i{t}(h) (n)[e](w){s}[.]
Pres,s Release`:
C_hina You^TV's CnB*oo [W]eb (S){i}[t](e) R,anks {N}{o}{.}1 on M#icrosof.t [L]iv{e} Se#arch Engi_ne
C^nBoo Tr`affic Inc_r-eases (4){9}(%) {O}[v](e)r T(w)o Mon*ths
{R}{e}[a](d) {t}[h][e] n.ews, thin.k abo`ut th{e} im^pact, and
[j][u][m](p) on [t]hi(s) fi`rst th.ing Tomor+-row morni-n^g! $0-.42 is a [g](i)[f]{t} at [t]hi{s} pr.^ice.
Do (y)(o){u}{r} homewo-r^k (a){n}{d} wa-tch [t]h{i}[s] t*rade M-onday mornin+g.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#199675: When used in this manner, the expected behavior is to switch seamlessly between full-screen mode and then back into normal window playback when the user presses ESC or other escape sequenc
H(u)[g][e] (N)e{w}(s) To I*mpact (C)[Y]{T}V
Chi+na Y+ouTV {C}o(r){p}(.)
Symbo-l: (C)[Y]T[V]
We h(a)[v][e] alrea`dy [s][e][e]{n} CYT_V's mark_et im-pact be,fore cli^m_bing to o{v}[e][r] $2.0-0 w(i)(t)[h] (n)(e){w}s[.]
P_ress Releas,e:
Chin,a Y,ouTV's CnB_oo {W}[e](b) [S]{i}(t)e Ra^nks N(o)[.]1 on Mic*-rosoft [L]{i}(v)(e) Searc#h Engin_e
Cn.Boo Traf_fic Incre`ase,s 4(9)(%) Ov(e)r [T][w]o Mon_ths
(R){e}{a}(d) (t)[h]e ne`ws, th^ink abou+t [t][h]e i`mpact, and
jum{p} on t[h][i]{s} fi^rst th_ing T.om#orrow mo.rning^! $0-.42 is a g[i][f]t at [t](h)[i]s pr`ice.`
Do [y][o]ur h*ome+work (a)n{d} w.atch th[i]{s} tr^ade M,onday mo*rning.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#167370: Rawether for Windows and Rawether for Windows CE are trademarks of Printing Communications Assoc.
H[u][g]e N(e)(w)(s) To Impac,t C(Y)[T](V)
C*hina YouT+V [C](o){r}{p}.
Symbo+l: {C}{Y}[T](V)
We {h}a(v)[e] alr+eady (s)(e)e[n] CYTV'*s mar-ket impac#t be^fore climb`,ing to [o](v){e}[r] $2.#00 w(i)[t](h) {n}e{w}s(.)
P.ress Relea.se:
Ch_ina YouT.V's C.nBoo W[e]b (S)[i]t{e} Ran_ks (N)o(.)(1) on Mi+c.rosoft (L)(i){v}{e} Searc.h En.gine
CnB.oo Tra#ffic I,n.creases 4[9]{%} [O]{v}{e}{r} (T)[w]{o} Mon.ths
{R}[e]ad {t}he new*s, thi-nk ab,out {t}{h}{e} impac`t, and
[j]u{m}(p) on (t)h{i}{s} fi,rst t+hing To#+morrow mornin#g.! $0_.42 is a [g]i(f){t} at (t)h[i][s] pri*c+e.
Do (y)o(u)(r) hom_e-work (a){n}[d] wat`ch t{h}(i){s} tra#de Monda_y mornin*g.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#202923: Then, just run, e.
[H](u)[g](e) [N](e)(w){s} To Im,pact CYT(V)
Chi#na You#TV [C]o[r]{p}{.}
Symbol-: {C}[Y](T){V}
We (h)av[e] alread+y [s]e(e)(n) CY`TV's mark_et impa`ct b,efore cli`#mbing to [o](v)e{r} $.2.00 {w}i{t}{h} n(e)w[s].
Pre#ss Release-:
Chi-na You,TV's CnB#oo (W)(e)b {S}{i}{t}[e] R+anks [N](o).1 on Micr^o^soft [L]i{v}{e} Sear,ch En+gine
Cn,Boo Tra_ffic In##creases (4)(9)% [O]ve(r) T[w][o] Mont,hs
[R]{e}{a}[d] t{h}e news-, th_ink abou+t [t]he impa#ct, and
[j]u{m}{p} on [t]{h}{i}[s] firs^t th.ing T__omorrow mor_nin+g! $0.4+2 is a {g}[i](f)t at {t}[h]{i}s price.._._..
Do [y]{o}{u}r home-_work [a](n)(d) wat*ch {t}h(i)[s] trad#e Mond`ay m.orning.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423739: libgl1-mesa-dri: banding in rendering when using blending for transparency
Hi, Brice, Thanks very much for writing up the bug report... It looks right on to me... FWIW, the bug's still present for me in the 7.0.1~rc2-1 version of libgl1-mesa-dri... Dan On 8/10/07, Brice Goglin [EMAIL PROTECTED] wrote: Hi Dan, Thanks for all the testing you did for this bug report. I have forwarded it in the upstream bugzilla at https://bugs.freedesktop.org/show_bug.cgi?id=11931 Feel free to add any comment there if you think it could help (or if I missed something in my summary). There might be very few people competent and interested enough to fix this, your help might be important. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
