Bug#467105: ATI driver: use of Xv causes one monitor to be repeatedly blanked
Darren Salt wrote: Package: xserver-xorg-video-ati Version: 1:6.8.0-1 Severity: important One of my monitors (VGA-0) is repeatedly and regularly blanked and unblanked, each change being approx. 1s apart when Xv is in use, e.g. by gxine. The other monitor (DVI-0) is unaffected, and the position of the overlay does not appear to make any difference, though it does need to be visible (tested by shading and unshading the video window). Reverting to 1:6.7.197-1 cured the problem. I have not checked intermediate snapshot builds. Please try at least these intermediate snapshot. There are 6 of them available at http://snapshot.debian.net Or better, do a git-bisect in the upstream git repository http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-ati.git to locate the exact commit breaking this. If you need help, please let me know. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#389007: marked as done (Regression: Radeon 9200 powers off Apple Cinema Display connected via DVI)
Your message dated Sat, 23 Feb 2008 09:16:45 +0100 with message-id [EMAIL PROTECTED] and subject line Re: Bug#389007: Regression: Radeon 9200 powers off Apple Cinema Display has caused the Debian Bug report #389007, regarding Regression: Radeon 9200 powers off Apple Cinema Display connected via DVI 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 [EMAIL PROTECTED] immediately.) -- 389007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389007 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: xserver-xorg-video-ati Version: 1:6.6.2-2 Severity: important Hi, Back when X.Org was introduced to unstable, there was a bug where when X was started up, the DVI flat panel (Apple Cinema Display 20) went into standby mode, and wouldn't come out. This could be worked around with IIRC a PanelSize option and a few other manual tweaks. This was later fixed, and the special options were no longer necessary. With the latest version, this bug has reappeared, and the monitor again goes into standby when the X server starts. The relevant parts of xorg.conf follow. If I uncomment UseFBDev, the monitor won't come out of standby even if I kill the X server. The other commented out options don't appear to have any effect. I'll be happy to do any further testing. Regards, Roger Section Device Identifier ATI Radeon 9200 Driver ati BusID PCI:0:16:0 # Option UseFBDev true # Option MonitorLayout TMDS Option SWcursor true # Option fbdev /dev/fb0 Option DDCMode true EndSection Section Monitor Identifier Apple Cinema Display #Option DPMS HorizSync 28-90 VertRefresh 43-72 DisplaySize 434 270 Mode 1680x1050 # D: 119.005 MHz, H: 64.677 kHz, V: 59.886 Hz DotClock119.006 HTimings1680 1728 1760 1840 VTimings1050 1053 1059 1080 Flags -HSync +VSync EndMode EndSection Section Screen Identifier Default Screen Device ATI Radeon 9200 Monitor Apple Cinema Display DefaultDepth24 SubSection Display Depth 1 Modes 1680x1050 EndSubSection SubSection Display Depth 4 Modes 1680x1050 EndSubSection SubSection Display Depth 8 Modes 1680x1050 EndSubSection SubSection Display Depth 15 Modes 1680x1050 EndSubSection SubSection Display Depth 16 Modes 1680x1050 EndSubSection SubSection Display Depth 24 Modes 1680x1050 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse EndSection Section DRI Mode0666 EndSection -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-powerpc Locale: LANG=en_GB.UTF8, LC_CTYPE=en_GB.UTF8 (charmap=UTF-8) Versions of packages xserver-xorg-video-ati depends on: ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii xserver-xorg-core2:1.1.1-7 X.Org X server -- core server xserver-xorg-video-ati recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 1:6.8.0-1 Roger Leigh wrote: Installing 1:6.8.0-1 from unstable: X works. It starts up without powering off the monitor and/or locking up the system. However, switching to a VT or stopping X either by shutting down the system from KDE or C-A-Bksp cause the monitor to power off and the system to lock up hard. So it looks like an improvement, but there's still an issue when cleaning up and/or switching VTs. Given how old this bug is and given that the original problem is fixed, I am closing it instead of changing it into a new problem. We need a new (clean) bug report for the above issue. Maybe it's related to
Bug#466384: xkb-data: 0.9+cvs.20070428-1 breaks 0.8-17 Finnish patch
Teemu Likonen kirjoitti: Hi Troy, the following bug was reported to Debian bug tracking system by Martin-Éric Racine: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466384 The Finnish keyboard map change in 0.9+cvs.20070428-1 breaks the dead_macron patch from 0.8-17, among other things. It appears that several other deadkeys are also gone. Coming back to this bug... fi(kotoistus) works well and it must be the default (as it is). The old Finnish keyboard fi(classic) is broken, though, at least in Debian Sid. I'll try to investigate it tomorrow. Ok, now I have done some testing and... did not find any problems at all. The dead_macron patch is there in the current Debian's symbols/fi file and it is in the upstream as well. Debian Etch's fi(basic) is the same as Debian Sid's fi(classic) as the default Finnish keyboard has changed. In Debian Etch I ran the following commands: setxkbmap 'fi(basic)' -option xmodmap -pke xmodmap-pke_etch_fi-default.txt In Debian Sid I did the following: setxkbmap 'fi(classic)' -option xmodmap -pke xmodmap-pke_sid_fi-classic.txt Then compared the files: The only difference is in the keycode 214 which does not affect anything relevant. See the attached diff file. The I compared en_US.UTF-8/Compose files (which is used with fi_FI.UTF-8 locale as well). The Compose files are 100 % identical in Etch and Sid. I also manually tested fi(classic) in Sid and everything seems to be working well. Dead keys do work So, it seems to me that this bug does not exist and the it can be closed. (I'll file a new wishlist bug about updating en_US.UTF-8/Compose file from the upstream. It'll make fi(kotoistus) work a bit better.) --- xmodmap-pke_etch_fi-default.txt 2008-02-23 11:50:16.0 +0200 +++ xmodmap-pke_sid_fi-classic.txt 2008-02-23 11:46:00.0 +0200 @@ -204,7 +204,7 @@ keycode 211 = keycode 212 = keycode 213 = -keycode 214 = +keycode 214 = XF86Display keycode 215 = keycode 216 = keycode 217 =
Processed: your mail
Processing commands for [EMAIL PROTECTED]: reassign 467142 libx11-data Bug#467142: xkb-data: Please update en_US.UTF-8/Compose file from the upstream Bug reassigned from package `xkb-data' to `libx11-data'. retitle 467142 Please update en_US.UTF-8/Compose file from the upstream Bug#467142: xkb-data: Please update en_US.UTF-8/Compose file from the upstream Changed Bug title to `Please update en_US.UTF-8/Compose file from the upstream' from `xkb-data: Please update en_US.UTF-8/Compose file from the upstream'. 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#467142: xkb-data: Please update en_US.UTF-8/Compose file from the upstream
Package: xkb-data Version: 0.9-4 Severity: wishlist Quite recently the default Finnish keyboard layout has changed. The current default is now called fi(kotoistus). It contains some keymappings which don't work with the Compose file shipped with Debian Sid. I'm referring to this file: /usr/share/X11/locale/en_US.UTF-8/Compose (This file is used with fi_FI.UTF-8 locale as well.) For example the Debian Sid's en_US.UTF-8/Compose lacks dead_stroke definitions. Also definitions for U+01EE and U+01EF (latin capital/small letter ezh with caron) are missing. The current upstream version of en_US.UTF-8/Compose.pre has these updates¹. I ask you to update the file before the release of Debian Lenny. - 1. Dead strokes were added in the upstream git commit 4d6c45e60ed13d3b0fea10413873d6a74f9d6a3b U+01EE and U+01EF started working from the commit 438d02ebc08ee171cf1d3936f4c81050d428ab92 See git://anongit.freedesktop.org/git/xorg/lib/libX11
Bug#466384: xkb-data: 0.9+cvs.20070428-1 breaks 0.8-17 Finnish patch
On 2/23/08, Teemu Likonen [EMAIL PROTECTED] wrote: Debian Etch's fi(basic) is the same as Debian Sid's fi(classic) as the default Finnish keyboard has changed. And changing the default is precisely what's wrong. Making it the Kotoisuus map available for those who want it is OK, but changing the default is not. -- Martin-Éric Racine http://q-funk.iki.fi
Processed: The change of default Finnish keyboard
Processing commands for [EMAIL PROTECTED]: severity 466384 wishlist Bug#466384: xkb-data: 0.9+cvs.20070428-1 breaks 0.8-17 Finnish patch Severity set to `wishlist' from `important' retitle 466384 Please don't change the default Finnish keyboard to fi(kotoistus) Bug#466384: xkb-data: 0.9+cvs.20070428-1 breaks 0.8-17 Finnish patch Changed Bug title to `Please don't change the default Finnish keyboard to fi(kotoistus)' from `xkb-data: 0.9+cvs.20070428-1 breaks 0.8-17 Finnish patch'. 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#466384: The change of default Finnish keyboard
severity 466384 wishlist retitle 466384 Please don't change the default Finnish keyboard to fi(kotoistus) thanks Martin-Éric Racine kirjoitti: On 2/23/08, Teemu Likonen [EMAIL PROTECTED] wrote: Debian Etch's fi(basic) is the same as Debian Sid's fi(classic) as the default Finnish keyboard has changed. And changing the default is precisely what's wrong. Making it the Kotoisuus map available for those who want it is OK, but changing the default is not. (It's called Kotoistus.) Ok, this bug does not really break anything. The patch is there and it's in the upstream as well. With the new fi(kotoistus) keyboard we can produce more different characters than with the old. The new keyboard offers easier way to produce certain Finnish and international punctuation marks which have previously been possible only through Compose key sequences. More accented letters can also be produced since there are more dead accent keys in the keyboard. Some rarely needed characters fi(kotoistus) is missing can be produced through Compose key sequences (superscript numbers for example). Therefore this bug report is essentially about objecting the change of default. It is valid opinion of course but there is not any breaking of things anywhere. I retitle this accordingly and change the severity to wishlist. I do not object the change of default. I think the change is really welcome and been long-waited because now correct Finnish and latin-based international text can be written more easily. I also want to remind that this change is not about those who want to use new keyboard and certainly not only about change in Debian. It's about change in standard Finnish keyboard everywhere. So, if there are arguments for or against the change, it's not about Debian community. It's about computer using in general level in Finland. All operating systems included and the big picture must be taken in to consideration. Arguments originating from this view are the only really valid ones.
Bug#466384: The change of default Finnish keyboard
On 2/23/08, Teemu Likonen [EMAIL PROTECTED] wrote: Martin-Éric Racine kirjoitti: On 2/23/08, Teemu Likonen [EMAIL PROTECTED] wrote: Debian Etch's fi(basic) is the same as Debian Sid's fi(classic) as the default Finnish keyboard has changed. And changing the default is precisely what's wrong. Making it the Kotoisuus map available for those who want it is OK, but changing the default is not. Ok, this bug does not really break anything. Yes, it does. Several deadkeys have gone away, because the default is not the same. The patch is there and it's in the upstream as well. With the new fi(kotoistus) keyboard we can produce more different characters than with the old. The new keyboard offers easier way to produce certain Finnish and international punctuation marks which have previously been possible only through Compose key sequences. More accented letters can also be produced since there are more dead accent keys in the keyboard. Some rarely needed characters fi(kotoistus) is missing can be produced through Compose key sequences (superscript numbers for example). Please spare us the Ministry of Education press release. I'm someone who actually *needs* all those new letters and yet the keyboard map is a complete mess, because the only thing it keeps in mind is doing whatever the Swedes and the Norwegians decided to do with the common subset of Scandics. For everything else, it breaks what little compatibility there was was with other neighboring countries' keyboard maps and it makes it *more*difficult* to get some glyphs that fi(Classic) makes a breeze to get. Therefore this bug report is essentially about objecting the change of default. It is valid opinion of course but there is not any breaking of things anywhere. Yes, it is, because it removes previously available combinations. People upgrading from Etch (or from pre-Hardy, on Ubuntu) will be left wondering where those keys went. It *is* a bug. welcome and been long-waited because now correct Finnish and latin-based international text can be written more easily. Do you actually have a use for all this or are you just repeating what the nanny state said in its press release? The selected layout actually makes writing all these languages *more*difficult*. -- Martin-Éric Racine http://q-funk.iki.fi
Bug#466384: The change of default Finnish keyboard
Martin-Éric Racine kirjoitti: I'm someone who actually *needs* all those new letters My point is that this really is not about you and me. This Kotoistus keyboard is about Finnish people in general. For everything else, it breaks what little compatibility there was was with other neighboring countries' keyboard maps and it makes it *more*difficult* to get some glyphs that fi(Classic) makes a breeze to get. The selected layout actually makes writing all these languages *more*difficult*. I do believe you. No doubt you find some letters/characters more difficult to write than before and of course you are right in your opinion. There is fi(classic) available for people like you. But I think it really is not an argument for not making fi(kotoistus) the default because in general fi(kotoistus) makes it easier--and now first time even possible--to write correct Finnish and international text. This means accented characters and punctuation. None of the accented characters are lost; couple of characters (see below) just need dead keys now. Several deadkeys have gone away, because the default is not the same. What keys exactly are gone? Honestly, I'm really confused because all the dead keys of fi(classic) are there and there are even new ones: dead_stroke¹, dead_horn, dead_hook, dead_doubleaqute, dead_belowdot, dead_abovedot and dead_abovering. Do you find writing more difficult because dead_caron and dead_macron are in different place? Or that now łŁħĦšŠžŽñÑ (which were behind AltGr) need dead key? By the way, I'm really interested in this stuff. Thanks for the discussion. :) --- 1. The dead_stroke will work after newer en_US.UTF-8/Compose file is in Debian. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467142 The dead_stroke is AltGr(§) and AltGr(l) in fi(kotoistus).
Bug#466384: The change of default Finnish keyboard
On 2/23/08, Teemu Likonen [EMAIL PROTECTED] wrote: Martin-Éric Racine kirjoitti: My point is that this really is not about you and me. This Kotoistus keyboard is about Finnish people in general. The average Finn won't notice much. However, Finns who need to frequently write in a foreign language (a common case inside EU) definitely will, because writing anything but Scandinavian languages has become harder than before. For everything else, it breaks what little compatibility there was was with other neighboring countries' keyboard maps and it makes it *more*difficult* to get some glyphs that fi(Classic) makes a breeze to get. I do believe you. No doubt you find some letters/characters more difficult to write than before and of course you are right in your opinion. There is fi(classic) available for people like you. But I think it really is not an argument for not making fi(kotoistus) the default because in general fi(kotoistus) makes it easier--and now first time even possible--to write correct Finnish and international text. This means accented characters and punctuation. That was already possible with fi(Classic) and the choices there made a lot more sense, overall. As much as I try, to many of the Kotoistus defaults simply make things more tedious than before. Do you find writing more difficult because dead_caron and dead_macron are in different place? Or that now łŁħĦšŠžŽñÑ (which were behind AltGr) need dead key? Yes, to both items. For someone who often needs to switch between Estonian and Finnish keyboards, having šŠžŽ as AltGr keys on S and Z made a lot of sense. It also kept the typing consistent between both keyboard maps. Likewise, having dead_macron on the - key made a lot of sense, because it too is some sort of dash. Having the cédille as an AltGr deadkey on the comma also made sense, because it looks like a comma and goes under the letter. Kotoistus' choice of moving those away defies logic. In the case of the cédille, it also requires a shift, in addition to a dead key. In other words, it makes writing in French using a Finnish keyboard *much* slower than before. When the Kotoistus keymap was announced, I was initially thrilled but, as soon as I tried it, I learned to *hate* it, because it clearly shows a lack of usability. The committee behind the new standard also blatantly ignored memos by fellow multilinguists on what would be a *usable* new keyboard map. All they were interested in was following whatever standard the other Scandinavian countries would implement. At least one computer manufacturer had the brains to at least try to find a compromise: recent Fujitsu-Semens keyboards have Estonian glyphs in blue, in addition to green for Norwegian and red for Danish (or was it red for Norwegian and green for Danish?) variants to the Finnish-Swedish keyboard map. There, you can clearly what *would* have been a usable compromise by all countries. The differences aren't that big, but they are annoying enough to make the basic keyboard map slightly incompatible between Nordic countries and they ignore the Estonian map completely. -- Martin-Éric Racine http://q-funk.iki.fi
Bug#389007: Regression: Radeon 9200 powers off Apple Cinema Display
Brice Goglin [EMAIL PROTECTED] writes: Roger Leigh wrote: Installing 1:6.8.0-1 from unstable: However, switching to a VT or stopping X either by shutting down the system from KDE or C-A-Bksp cause the monitor to power off and the system to lock up hard. We need a new (clean) bug report for the above issue. Maybe it's related to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463076 ? That sounds like an exact description of the issue, so I won't file a new bug. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. pgpcprA6jadj0.pgp Description: PGP signature
Processed: found 463076 in 1:6.8.0-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.16 found 463076 1:6.8.0-1 Bug#463076: xserver-xorg-video-ati: machine freezes when X is stopped or second X started Bug marked as found in version 1:6.8.0-1. 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]
mesa: Changes to 'debian-unstable'
debian/changelog |5 +- debian/patches/03_optional-progs-and-install.patch | 38 - 2 files changed, 18 insertions(+), 25 deletions(-) New commits: commit 31e9d9d4f85740613a828452a2f2beb801de7878 Author: Julien Cristau [EMAIL PROTECTED] Date: Sat Feb 23 18:18:42 2008 +0100 Prepare changelog for upload. diff --git a/debian/changelog b/debian/changelog index c348a3e..c31d561 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,11 +1,11 @@ -mesa (7.0.3~rc2-1) UNRELEASED; urgency=low +mesa (7.0.3~rc2-1) unstable; urgency=low * New upstream release candidate. + 03_optional-progs-and-install.patch: partly applied upstream, fixed up * Stop building with -O0 on hppa. Bug #451047 should be fixed in recent gcc versions. - -- Julien Cristau [EMAIL PROTECTED] Thu, 24 Jan 2008 22:51:04 +0100 + -- Julien Cristau [EMAIL PROTECTED] Sat, 23 Feb 2008 18:18:29 +0100 mesa (7.0.2-4) unstable; urgency=low commit ea9c6d3d9e9d27c8ba90c98ca671cff6e333c620 Author: Julien Cristau [EMAIL PROTECTED] Date: Sat Feb 23 16:08:53 2008 +0100 03_optional-progs-and-install.patch: partly applied upstream, fixed up diff --git a/debian/changelog b/debian/changelog index 34fbf40..c348a3e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,6 +1,7 @@ mesa (7.0.3~rc2-1) UNRELEASED; urgency=low * New upstream release candidate. ++ 03_optional-progs-and-install.patch: partly applied upstream, fixed up * Stop building with -O0 on hppa. Bug #451047 should be fixed in recent gcc versions. diff --git a/debian/patches/03_optional-progs-and-install.patch b/debian/patches/03_optional-progs-and-install.patch index f802a42..c002803 100644 --- a/debian/patches/03_optional-progs-and-install.patch +++ b/debian/patches/03_optional-progs-and-install.patch @@ -10,39 +10,31 @@ Also remove references to GLU library since it is not required and we don't actually build it at this point. -Index: mesa/progs/xdemos/Makefile -=== mesa.orig/progs/xdemos/Makefile2007-11-11 00:34:12.0 +0100 -+++ mesa/progs/xdemos/Makefile 2007-11-11 02:07:52.0 +0100 -@@ -6,11 +6,11 @@ +--- mesa.orig/progs/xdemos/Makefile mesa/progs/xdemos/Makefile +@@ -10,7 +10,7 @@ - INCDIR = $(TOP)/include + LIBS = -L$(TOP)/$(LIB_DIR) -l$(GL_LIB) $(APP_LIB_DEPS) --LIB_DEP = $(TOP)/$(LIB_DIR)/$(GL_LIB_NAME) $(TOP)/$(LIB_DIR)/$(GLU_LIB_NAME) -+LIB_DEP = $(TOP)/$(LIB_DIR)/$(GL_LIB_NAME) - --LIBS = -L$(TOP)/$(LIB_DIR) -l$(GLU_LIB) -l$(GL_LIB) $(APP_LIB_DEPS) -+LIBS = -L$(TOP)/$(LIB_DIR) -l$(GL_LIB) $(APP_LIB_DEPS) - --PROGS = glthreads \ -+PROGS ?= glthreads \ +-PROGS = \ ++PROGS ?= \ + glthreads \ glxdemo \ glxgears \ - glxgears_fbconfig \ -@@ -46,6 +46,9 @@ +@@ -55,6 +55,11 @@ + extra: $(EXTRA_PROGS) - default: $(PROGS) +install: $(PROGS) + $(INSTALL) -d $(DESTDIR)$(INSTALL_DIR)/bin + $(INSTALL) -m 755 $(PROGS) $(DESTDIR)$(INSTALL_DIR)/bin - ++ ++ clean: - -rm -f $(PROGS) -Index: mesa/progs/Makefile -=== mesa.orig/progs/Makefile 2007-11-11 00:34:12.0 +0100 -+++ mesa/progs/Makefile2007-11-11 02:06:48.0 +0100 + -rm -f $(PROGS) $(EXTRA_PROGS) + -rm -f *.o *~ +--- mesa.orig/progs/Makefile mesa/progs/Makefile @@ -21,8 +21,12 @@ fi \ done -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465154: xserver-xorg-video-intel: same problem here with 82Q963/Q965; is fixed by upstream intel_drv.so
Package: xserver-xorg-video-intel Version: 2:2.2.0.90-3 Followup-For: Bug #465154 I have had the same problem, starting with 2:2.2.0.90-1: Switching to a VT gave me a completely black screen for a moment, then the backlight was turned on but nothing was displayed. If the intel driver was used with XAA then the system at least remained responsive and I could switch back to the X session with ALT-F7 or log in blindly and run commands on the VT. With EXA used, on the other hand, I found that my computer hung completely at this point and could only be rebooted by using ALT-SysRq s-u-b. I now finally had the time to pull the xf86-video-intel source from the upstream git repository and compile the newest driver myself. I am happy to report that this problem was fixed as soon as I replaced intel_drv.so with the git version (last commit Fri Feb 22 11:41:25 2008 -0800) and rebooted. Now things seem to be fine with both XAA and EXA. (I still use XAA because it results in smoother text scrolling in X terminal windows.) -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2007-03-18 12:08 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1831520 2008-02-01 06:08 /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 82Q963/Q965 Integrated Graphics Controller (rev 02) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-rw-r-- 1 root adm 3179 2008-02-23 18:09 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: [...] Section Device Identifier Intel Corporation 82Q963/Q965 Integrated Graphics Controller Driver intel Option AccelMethod XAA # BusID PCI:0:2:0 # Option AllowGLXWithComposite true # Option XaaNoOffscreenPixmaps true # Option VBERestoretrue # Option XvMCSurfaces 7 EndSection [...] Section DRI Mode0666 EndSection #Section Extensions # Option Composite Enable #EndSection [...] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451893: report for 2:2.2.1-1
FYI, 2:2.2.1-1 still has the same problem was before on the following: 00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Unknown device 01da Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at dfe0 (32-bit, non-prefetchable) [size=1M] Memory at c000 (64-bit, prefetchable) [size=256M] I/O ports at ecb8 [size=8] Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Capabilities: [d0] Power Management version 2 00:02.1 Display controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) Subsystem: Dell Unknown device 01da Flags: bus master, fast devsel, latency 0 Memory at dff0 (32-bit, non-prefetchable) [size=1M] Capabilities: [d0] Power Management version 2 Having Option XAANoOffscreenPixmaps true Option AccelMethod XAA in /etc/X11/xorg.conf works, without it text isn't rendered. -- -- arthur - [EMAIL PROTECTED] - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Bug#466384: The change of default Finnish keyboard
Martin-Éric Racine kirjoitti: On 2/23/08, Teemu Likonen [EMAIL PROTECTED] wrote: Martin-Éric Racine kirjoitti: My point is that this really is not about you and me. This Kotoistus keyboard is about Finnish people in general. The average Finn won't notice much. However, Finns who need to frequently write in a foreign language (a common case inside EU) definitely will, because writing anything but Scandinavian languages has become harder than before. I believe that average Finnish people expect to get similar keyboard layout in Microsoft Windows and Unix-type X.org systems. With Kotoistus we'll achieve this. Yes, I do believe in standards. The Kotoistus keyboard is not yet the default in Windows, though, but it is already available for download: http://www.microsoft.fi/nappaimisto/ You made good points about writing (some) foreign languages. I can see now that writing some characters are a bit more difficult with fi(kotoistus). The characters itself are not lost, though. (And there are even more of them.) In these arguments you seem to concentrate on ease of writing (certain) foreign languages. It's fine. I want to emphasize standards and the whole picture of writing any language from Finnish people's point of view. This view includes not only accented letters but certain punctuation marks as well which have first time become available with the Kotoistus keyboard. I'm sure you knew all this already. :)
Bug#467214: xserver-xorg: memory leak
Package: xserver-xorg Version: 1:7.3+10 Severity: normal Hi, X has a memory leak. After running for 52 days (and adding lots of swap), it was taking up 1831m of virtual memory: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 14893 root 5 -10 1831m 16m 1840 S 0.7 3.6 1690:08 Xorg I suspect it is something to do with DBus, as running strings(1) on swap produced lots of references to dbus: $ sudo strings /dev/hda2 /home/sys/swap/* |fgrep org.freedesktop.DBus.Local|wc -l 446272 The strings output contained lots of copies of: unix:path=/var/run/dbus/system_bus_socket org_freedesktop_general org_freedesktop_general org_freedesktop_general /org/freedesktop/DBus/Local org.freedesktop.DBus.Local Disconnected Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ECTED EXTERNAL DBUS_COOKIE_SHA1 ANONYMOUS DBus appears to be working OK (at least running dbus-monitor then starting pidgin produced a flurry of messages). In case it is relevant, I'm running ion3 with mostly xterms. The data above was with a recent but non-current version of X from unstable, I've now been running for 19 days with the version that was in unstable 19 days ago, and X is up to 734Mb of VM usage. Let me know if there is anything I can do to help track this down. Ian. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2006-04-27 15:06 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1673980 2008-02-01 04:06 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:0a.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1) 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 2459 2007-11-08 05:37 /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 InputDevice Identifier ps2keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc104 Option XkbLayout gb EndSection Section InputDevice Identifier ps2mouse Driver mouse Option CorePointer Option Device/dev/gpmdata # Option Protocol IMPS/2 Option Protocol Intellimouse Option Emulate3Buttons false Option Buttons 5 Option ZAxisMapping 4 5 EndSection Section Device Identifier geforce # BusID PCI:0:A:0 Driver nv # Driver nvidia EndSection Section Monitor Identifier Right Monitor (0) Option DPMS HorizSync 31.5-57.0 VertRefresh 50-90 Gamma 1.6 EndSection Section Screen Identifier Right Screen (0) Device geforce Monitor Right Monitor (0) DefaultDepth24 # Option Accel Off SubSection Display Depth 1 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth
Bug#467215: Missing dependency on libpciaccess0
Package: xserver-xorg-video-intel-dbg Version: 2.2.1-1 Severity: normal xserver-xorg-video-intel-dbg 2.2.1-1 now contains intel_reg_dumper which is linked against libpciaccess. However, xserver-xorg-video-intel-dbg does not depend on libpciaccess0, hence intel_reg_dumper is left unusable unless this dependency is installed manually. Regards: David -- /) David Weinehall [EMAIL PROTECTED] /) Rime on my window (\ // ~ // Diamond-white roses of fire // \) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465154: xserver-xorg-video-intel: same problem here with 82Q963/Q965; is fixed by upstream intel_drv.so
Florian Kulzer wrote: Package: xserver-xorg-video-intel Version: 2:2.2.0.90-3 Followup-For: Bug #465154 I have had the same problem, starting with 2:2.2.0.90-1: Switching to a VT gave me a completely black screen for a moment, then the backlight was turned on but nothing was displayed. If the intel driver was used with XAA then the system at least remained responsive and I could switch back to the X session with ALT-F7 or log in blindly and run commands on the VT. With EXA used, on the other hand, I found that my computer hung completely at this point and could only be rebooted by using ALT-SysRq s-u-b. I now finally had the time to pull the xf86-video-intel source from the upstream git repository and compile the newest driver myself. I am happy to report that this problem was fixed as soon as I replaced intel_drv.so with the git version (last commit Fri Feb 22 11:41:25 2008 -0800) and rebooted. Did you use the master branch of the upstream git or xf86-video-intel-2.2-branch? If the latter, then the new 2.1.1 which entered unstable today should work fine? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: found 451893 in 2:2.2.1-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.16 found 451893 2:2.2.1-1 Bug#451893: xserver-xorg-video-intel: shows no fonts Bug#451791: xserver-xorg-video-intel: Fonts and many other items fail to render legibly Bug#452268: all fonts are unreadable Bug#462921: xserver-xorg-video-intel: exa corruption with 965Q Bug marked as found in version 2:2.2.1-1. 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#467214: xserver-xorg: memory leak
reassign 467214 xserver-xorg-core found 467214 2:1.4.1~git20080131-1 thank you Ian Beckwith wrote: Package: xserver-xorg Version: 1:7.3+10 Severity: normal Hi, X has a memory leak. After running for 52 days (and adding lots of swap), it was taking up 1831m of virtual memory: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 14893 root 5 -10 1831m 16m 1840 S 0.7 3.6 1690:08 Xorg I suspect it is something to do with DBus, as running strings(1) on swap produced lots of references to dbus: $ sudo strings /dev/hda2 /home/sys/swap/* |fgrep org.freedesktop.DBus.Local|wc -l 446272 The strings output contained lots of copies of: unix:path=/var/run/dbus/system_bus_socket org_freedesktop_general org_freedesktop_general org_freedesktop_general /org/freedesktop/DBus/Local org.freedesktop.DBus.Local Disconnected Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ECTED EXTERNAL DBUS_COOKIE_SHA1 ANONYMOUS That's interesting. I guess I'll forward this information in the upstream bugzilla, maybe it'll help them fix some memory leaks. DBus appears to be working OK (at least running dbus-monitor then starting pidgin produced a flurry of messages). In case it is relevant, I'm running ion3 with mostly xterms. The data above was with a recent but non-current version of X from unstable, I've now been running for 19 days with the version that was in unstable 19 days ago, and X is up to 734Mb of VM usage. Let me know if there is anything I can do to help track this down. You can look at xrestop in case there's an application allocating too many pixmaps. If dbus is really the bad guy here, you probably won't see anything in xrestop though. It could be related to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447526 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457957 Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#467214: xserver-xorg: memory leak
Processing commands for [EMAIL PROTECTED]: reassign 467214 xserver-xorg-core Bug#467214: xserver-xorg: memory leak Bug reassigned from package `xserver-xorg' to `xserver-xorg-core'. found 467214 2:1.4.1~git20080131-1 Bug#467214: xserver-xorg: memory leak Bug marked as found in version 2:1.4.1~git20080131-1. 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#466747: xserver-xorg-video-ati: Makes X fail to launch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. Brice Goglin schrieb: Mathias Brodala wrote: Hm, what additional info besides the one you already have (CPU, graphics adapter) do you need? More details. Machine model? Monitor model? How is it plugged? The machine is an AMD Athlon X64 Dual core, the graphics adapter is an ATI Radeon 9600 (RV350), the Monitor is an Acer AL1711, plugged into the adapter via VGA. Can you without any xorg.conf at all in case something is bad in yours? Both my current version and the latest version of this package fail to launch X if there is no xorg.conf. The Xorg.0.log for this case is attached. (Summary: the auto configuration fails to set up the busIDs properly; thus unrelated to the actual problem.) Do you have another monitor to test with? Or a DVI cable? No, neither nor. Can you try commenting out HorizSync, VertRefresh, and Modes? The result is the same (no X with the latest package version) plus my usual resolution of 1280×1024 won’t work with the old version. Putting those lines back makes it work again. Regards, Mathias - -- debian/rules -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHwHtaYfUFJ3ewsJgRAsPWAJ9HoMhX1PCF7VHOM/uxVCuOJr4iKgCfQVZ8 LtWQIZeeVj0wNLal/GNId0Y= =g0xf -END PGP SIGNATURE-
Bug#467214: xserver-xorg: memory leak
On Sat, Feb 23, 2008 at 09:18:20PM +0100, Brice Goglin wrote: You can look at xrestop in case there's an application allocating too many pixmaps. If dbus is really the bad guy here, you probably won't see anything in xrestop though. I forgot to mention I'd checked xrestop, there is nothing suspicious there. Looking now: Pixmaps:1544K total, Other: 259K total, All:1803K total It could be related to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447526 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457957 Oops, I hadn't spotted those, I didn't realise xorg-server was a separate source package from xorg. thanks, Ian. -- Ian Beckwith - [EMAIL PROTECTED] - http://erislabs.net/ianb/ GPG fingerprint: AF6C C0F1 1E74 424B BCD5 4814 40EC C154 A8BA C1EA Listening to: Iggy Pop - Nude Rude (Best Of) - Lust For Life -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#156115: Message from eBay Member Regarding Item
Hello! It's Scott! If you can sell HOT items and communicate with buyers,we can do a great deal for you! Please contact me directly to me for details: [EMAIL PROTECTED] Thank you and looking forward to hearing from you! Scott Smith -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#467214: xserver-xorg: memory leak
Processing commands for [EMAIL PROTECTED]: forwarded 467214 https://bugs.freedesktop.org/show_bug.cgi?id=14639 Bug#467214: xserver-xorg: memory leak Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=14639. 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#465154: xserver-xorg-video-intel: same problem here with 82Q963/Q965; is fixed by upstream intel_drv.so
On Sat, Feb 23, 2008 at 21:09:16 +0100, Brice Goglin wrote: Florian Kulzer wrote: Package: xserver-xorg-video-intel Version: 2:2.2.0.90-3 Followup-For: Bug #465154 [...] I now finally had the time to pull the xf86-video-intel source from the upstream git repository and compile the newest driver myself. I am happy to report that this problem was fixed as soon as I replaced intel_drv.so with the git version (last commit Fri Feb 22 11:41:25 2008 -0800) and rebooted. Did you use the master branch of the upstream git or xf86-video-intel-2.2-branch? If the latter, then the new 2.1.1 which entered unstable today should work fine? I used git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel and built the driver following instructions that you had given another user in bugreport 436336, message #27. I will let you know about the 2:2.2.1-1 package as soon as it becomes available on my mirror. (I am on amd64 and so far I see the new package only in my i386 chroot.) BTW, big thanks to you and the rest of the Debian X team for your work. Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467214: xserver-xorg: memory leak
forwarded 467214 https://bugs.freedesktop.org/show_bug.cgi?id=14639 thank you Ian Beckwith wrote: On Sat, Feb 23, 2008 at 09:18:20PM +0100, Brice Goglin wrote: You can look at xrestop in case there's an application allocating too many pixmaps. If dbus is really the bad guy here, you probably won't see anything in xrestop though. I forgot to mention I'd checked xrestop, there is nothing suspicious there. Looking now: Pixmaps:1544K total, Other: 259K total, All:1803K total I have reported this bug upstream at the URL above, feel free to add any comment if you think it could help. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#204307: Message from eBay Member Regarding Item
Hello! It's Scott! If you can sell HOT items and communicate with buyers,we can do a great deal for you! Please contact me directly to me for details: [EMAIL PROTECTED] Thank you and looking forward to hearing from you! Scott Smith -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#204363: Message from eBay Member Regarding Item
Hello! It's Scott! If you can sell HOT items and communicate with buyers,we can do a great deal for you! Please contact me directly to me for details: [EMAIL PROTECTED] Thank you and looking forward to hearing from you! Scott Smith -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#204378: Message from eBay Member Regarding Item
Hello! It's Scott! If you can sell HOT items and communicate with buyers,we can do a great deal for you! Please contact me directly to me for details: [EMAIL PROTECTED] Thank you and looking forward to hearing from you! Scott Smith -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465154: Solved by 2.2.1-1
Package: xserver-xorg-video-intel Version: 2:2.2.1-1 --- Please enter the report below this line. --- Bug disappeared on my box with the new version 2.2.1-1 Thanx to all involved devs. Greetings Tom --- System information. --- Architecture: i386 Kernel: Linux 2.6.24-2.6.24.2.slh.11-sidux-686 Debian Release: lenny/sid 500 unstablesidux.wuertz.org 500 unstablesidux.com 500 unstableftp.de.debian.org 500 unstabledebian.scribus.net 500 unstabledebian.cp69.de 500 unstabledebian-multimedia.informatik.uni-erlangen.de 500 unstabledeb.opera.com 50 experimentalftp.de.debian.org 200 testing ftp.de.debian.org --- Package information. --- Depends(Version) | Installed -+-=== libc6 (= 2.7-1) | 2.7-8 libdrm2 (= 2.3.0) | 2.3.0-4 xserver-xorg-core (= 2:1.4) | 2:1.4.1~git20080131-1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465154: marked as done (Switching to virtual console turns monitor blank)
Your message dated Sun, 24 Feb 2008 00:19:17 +0100 with message-id [EMAIL PROTECTED] and subject line Re: Bug#465154: Solved by 2.2.1-1 has caused the Debian Bug report #465154, regarding Switching to virtual console turns monitor blank 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 [EMAIL PROTECTED] immediately.) -- 465154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465154 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: xserver-xorg-video-intel Version: 2:2.2.0.90-3 Severity: important If I do not start X or kdm at boot I get a normal login prompt. Once I started X, I can not switch back to any virtual console (ctrl-alt-F?) - but get only a blank screen. Also while rebooting (or shutting down) I don't see any messages until the machine POSTs. Greetings Tom -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 8. Apr 2007 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1673980 1. Feb 05:06 /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 82945G/GZ Integrated Graphics Controller (rev 02) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1451 7. Feb 01: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 InputDevice Identifier Generic Keyboard Driver kbd Option XkbRulesxorg Option XkbModelpc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option Emulate3Buttons true EndSection Section Device Identifier Configured Video Device EndSection Section Monitor Identifier Configured Monitor # (via get-edid | parse-edid or # xrandr --verbose) # 1280x1024 @ vfreq 60.020 Hz, hfreq 63.981 kHz; pclk: 108.00 MHz Modeline 1280x1024_60 108.00 1280 1328 1440 1688 1024 1025 1028 1066 -HSync +Vsync Option PreferredMode 1280x1024_60 EndSection Section Screen Identifier Default Screen Monitor Configured Monitor EndSection Section Extensions # Option Composite 0 # Option RENDER 0 EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 43811 8. Apr 2007 /var/log/Xorg.2.log -rw-r--r-- 1 root root 28377 10. Feb 18:45 /var/log/Xorg.1.log -rw-r--r-- 1 root root 38617 10. Feb 20:19 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the xorg product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X.Org X Server 1.4.0.90 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20080131-1) Current Operating System: Linux tuxxy 2.6.24-slh-smp-6 #1 SMP PREEMPT Wed Jan 30 23:51:16 CET 2008 i686 Build Date: 01 February 2008 03:49:13AM 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 Feb 10 12:11:25 2008 (==) Using config file: /etc/X11/xorg.conf (==) No Layout section. Using the first Screen section. (**)
Bug#467235: xserver-xorg-video-ati: [radeon] images not scaled properly when using EXA
Package: xserver-xorg-video-ati Version: 1:6.7.197-1 Severity: normal Symptoms: after upgrading the xserver-xorg-video-ati package, some images are not scaled properly. For example, see http://icons.uhoreg.ca/corrupt-scaling.png, compared to the screenshot http://www.screenlets.org/index.php/Clear_Weather (aside from the fact that they had much better weather than I do). If I downgrade to version 1:6.6.193-3, everything looks fine. If I switch to XAA mode instead of EXA, everything looks fine (but is very slow). I've tried version 1:6.7.198~git20080203.f65e8dfa-1 from experimental, and it still exhibits the same problems. Here is part of my xorg.conf: Section Device Identifier ATI Radeon Mobility M6 LY Driver radeon Option UseFBDev false Option AllowGLXWithComposite true Option EnablePageFlipon Option AGPFastWrite on Option AccelMethod EXA Option DynamicClocks on Option BIOSHotkeys on Option BackingStore true Option ColorTiling on Option AccelDFS on Option CRT2Position Clone Option Monitor-LVDS Internal Panel Option Monitor-VGA External VGA EndSection Background: the ClearWeather screenlet uses cairo to draw some PNG files. I assume that cairo is using the render extension to scale the images to the correct size, but the driver isn't scaling things properly. I also see the problem in other programs, such as skippy-xd. Let me know if you need more information. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.24.2 Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Versions of packages xserver-xorg-video-ati depends on: ii libc6 2.7-4 GNU C Library: Shared libraries ii xserver-xorg-core 2:1.4-3Xorg X server - core server xserver-xorg-video-ati recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467235: xserver-xorg-video-ati: [radeon] images not scaled properly when using EXA
Hubert Chathi wrote: Symptoms: after upgrading the xserver-xorg-video-ati package, some images are not scaled properly. For example, see http://icons.uhoreg.ca/corrupt-scaling.png, compared to the screenshot http://www.screenlets.org/index.php/Clear_Weather (aside from the fact that they had much better weather than I do). If I downgrade to version 1:6.6.193-3, everything looks fine. If I switch to XAA mode instead of EXA, everything looks fine (but is very slow). I've tried version 1:6.7.198~git20080203.f65e8dfa-1 from experimental, and it still exhibits the same problems. Can you try 1:6.8.0-1 which entered unstable very recently ? If it does not help, please send the corresponding Xorg.0.log. By the way, you have some useless/not-recommended options in your xorg.conf, see below. Option UseFBDev false Does not exist anymore. Option AllowGLXWithComposite true Maybe ignored... Option EnablePageFlipon Option AGPFastWrite on May be dangerous, if you experience some lockups, you should try without them... Option BackingStore true Not sure it works nowadays, you might to remove this. Option CRT2Position Clone Probably ignored nowadays, RandR-1.2 is better. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
