Bug#443647: xkb-data missing some characters in gurmukhi (gur) keymap
Package: xkb-data
Version: 1.0~cvs.20070721-1
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
Hello,
xkb-data 'gur' keymap is missing two characters (there may be more, however,
that I may have not come across yet!) from Gurmukhi making it impossible to
correctly type an article.
The two characters are:
1) Unicode character: 0A72 (addak), which is ੱ
2) Unicode character: 0A5C (Rharha), which is ੜ
To get (2) above by typing SHIFT+A30 (I am not sure where it should go
according to the standard based on which others are placed on a keyboard,
but I am guessing it can be put as SHIFT+A30), line no. 50 in
/etc/X11/xkb/symbols/gur may be changed to the following:
key AC07 { [], [ 0x1000A30, 0x1000A5C
] };
The first one is a bit tricky. It appears that it should be mapped to the
key X on the US querty keyboard. Here is one way
to get this, by modifying line 58 of xkb-data package to the following (this
key already has two chars. assigned to it, so
addak will have to typed using the modifier key):
key AB02 { [], [ 0x1000A02, 0x1000A70, 0x1000A71
] };
The above two are just suggestions on how get around the problem. The
maintainer, of course, is free to research if a better method, or a correct
one, exists to solve this problem.
Thanks,
-HS
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
-- no debconf information
Debian-x your lucky day!
man! 7 best xxx sites for free only today 7ForFree dot com Lenore Higgins -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: setting package to xdmx xdmx-tools xnest xorg-server xprint xprint-common xserver-xephyr xserver-xfbdev xserver-xorg-core xserver-xorg-core-dbg xserver-xorg-dev xvfb ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.8 package xdmx xdmx-tools xnest xorg-server xprint xprint-common xserver-xephyr xserver-xfbdev xserver-xorg-core xserver-xorg-core-dbg xserver-xorg-dev xvfb Ignoring bugs not assigned to: xdmx-tools xvfb xserver-xorg-core xnest xserver-xfbdev xserver-xorg-core-dbg xserver-xorg-dev xdmx xprint xorg-server xprint-common xserver-xephyr tags 443611 + pending Bug#443611: xprint-common: [INTL:fi] Finnish translation of the debconf templates Tags were: l10n patch Tags added: pending 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]
xorg-server: Changes to 'debian-unstable'
debian/changelog |5 +++-- debian/po/fi.po | 46 ++ 2 files changed, 49 insertions(+), 2 deletions(-) New commits: commit 7d3d4af0a131b47502f7892e8ba78d959d84dad9 Author: Christian Perrier [EMAIL PROTECTED] Date: Sun Sep 23 08:40:55 2007 +0200 Finnish translation added diff --git a/debian/changelog b/debian/changelog index e48d039..7af3b61 100644 --- a/debian/changelog +++ b/debian/changelog @@ -8,7 +8,7 @@ xorg-server (2:1.4-3) UNRELEASED; urgency=low + Change by hacked ids file name suffix check to use strncmp and check for .ids + Use strncpy instead of strncat unnecessarily - * Add support for a partially configured device section + * Add support for a partially configured device section Implemented in 03_autoload_driver.diff. Now if you have a device section but lack a driver, it'll use the settings. This will allow you to just have a device section and enable EXA but not have to specify the driver or @@ -33,6 +33,7 @@ xorg-server (2:1.4-3) UNRELEASED; urgency=low - Basque. Closes: #443156 - Hebrew. Closes: #443204 - Bulgarian. Closes: #443226 +- Finnish. Closes: #443611 [ Julien Cristau ] * Add patch backported from upstream commit @@ -40,7 +41,7 @@ xorg-server (2:1.4-3) UNRELEASED; urgency=low 05_kill_type1.diff replaces 48_disable_type1.diff, and is now enabled in debian/patches/series. - -- Julien Cristau [EMAIL PROTECTED] Tue, 18 Sep 2007 21:05:33 +0200 + -- Christian Perrier [EMAIL PROTECTED] Sun, 23 Sep 2007 08:39:42 +0200 xorg-server (2:1.4-2) unstable; urgency=low diff --git a/debian/po/fi.po b/debian/po/fi.po new file mode 100644 index 000..393d9bd --- /dev/null +++ b/debian/po/fi.po @@ -0,0 +1,46 @@ +msgid +msgstr +Project-Id-Version: debconf: xorg-server\n +Report-Msgid-Bugs-To: [EMAIL PROTECTED] +POT-Creation-Date: 2007-09-18 20:35+0200\n +PO-Revision-Date: 2007-09-22 22:59+0200\n +Last-Translator: Esko Arajärvi [EMAIL PROTECTED]\n +Language-Team: Finnish [EMAIL PROTECTED]\n +MIME-Version: 1.0\n +Content-Type: text/plain; charset=utf-8\n +Content-Transfer-Encoding: 8bit\n +X-Poedit-Language: Finnish\n +X-Poedit-Country: FINLAND\n +X-Poedit-SourceCharset: utf-8\n + +#. Type: string +#. Description +#: ../xprint-common.templates:2001 +msgid Default printer resolution: +msgstr Tulostimen oletusresoluutio: + +#. Type: string +#. Description +#: ../xprint-common.templates:2001 +msgid +By default, Xprint assumes a printer resolution of 600 dpi. This should be +well suited for the majority of printers. +msgstr +Xprint olettaa tulostimen resoluution olevan 600 dpi. Suurimmalle osalle +tulostimista tämä oletus sopii hyvin. + +#. Type: string +#. Description +#: ../xprint-common.templates:2001 +msgid +On certain 1200 dpi printers, however, the image might appear squashed in +the corner of the page, or it might be blown up too large on 300 dpi +printers. If you are experiencing such printing problems, you may want to +set the default printer resolution to a more appropriate value. See /usr/ +share/doc/xprint-common/README.printing-problems.gz for more details. +msgstr +Joillain 1200 dpi:n tulostimilla kuva saattaa tulostua hyvin pienenä paperin +kulmaan ja joillain 300 dpi:n tulostimilla tulostua liian suurena. +Tällaisten ongelmien ilmetessä saatat haluta asettaa oletusresoluutioksi +jonkin sopivamman arvon. Lisätietoja löytyy dokumentista /usr/share/doc/ +xprint-common/README.printing-problems.gz. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443584: xrandr does not recognise conncted s-video
|xrandr --addmode S-video 800x600| |xrandr --output S-video --mode 800x600| works great :-) and stays this way too. no after effects when i use the mouse or the keyboard. although i watch the output display on the S-Video (tv) i get disconnected message from xrandr. laptop:~# xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2304 x 1024 VGA-0 disconnected (normal left inverted right x axis y axis) LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0*60.0 800x60060.3 640x48059.9 S-video disconnected (normal left inverted right x axis y axis) 800x60060.3 i tried adding other modes: 1024x768 and 640x480 with no success, way ? laptop:~# xrandr --addmode S-video 1024x768 X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 155 (RANDR) Minor opcode of failed request: 18 () Serial number of failed request: 16 Current serial number in output stream: 17 also, when playing video with vlc/xine/mplayer i have to change output driver to X11 otherwise no output on the S-Video (tv) only on the LVDS
Bug#443585: switching to s-video sets LVDS and S-Video brightness to max and inverts colors
xrandr --output LVDS --off --output S-video --auto did not help until i rebooted and tried again. if i plug the s-video during a session and not while it was booting xrandr is not able to use s-video. what was even better is your other suggestion: xrandr --addmode S-video 800x600 xrandr --output S-video --mode 800x600 xrandr --output LVDS --off
Processed: tagging 441902
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.7 tags 441902 + fixed-upstream Bug#441902: xserver-xorg-video-ati: 6.7.192-1~7.2 crashes xserver with xv video playback on compiz There were no tags set. Tags added: fixed-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]
Processed: severity of 443111 is minor ..., found 443111 in 2.1.1-2
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.7 severity 443111 minor Bug#443111: laptop: can't set brightness from within X11 Severity set to `minor' from `normal' retitle 443111 xserver-xorg-video-intel: ACPI keys should control backlight as well as xbacklight do Bug#443111: laptop: can't set brightness from within X11 Changed Bug title to `xserver-xorg-video-intel: ACPI keys should control backlight as well as xbacklight do' from `laptop: can't set brightness from within X11'. found 443111 2.1.1-2 Bug#443111: xserver-xorg-video-intel: ACPI keys should control backlight as well as xbacklight do Bug marked as found in version 2.1.1-2. 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: reassign 443646 to xserver-xorg-core, retitle 443646 to caps lock and scroll lock leds no longer work ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.7 reassign 443646 xserver-xorg-core Bug#443646: xserver-xorg-input-kbd: num lock and caps lock led no longer work Bug reassigned from package `xserver-xorg-input-kbd' to `xserver-xorg-core'. retitle 443646 caps lock and scroll lock leds no longer work Bug#443646: xserver-xorg-input-kbd: num lock and caps lock led no longer work Changed Bug title to `caps lock and scroll lock leds no longer work' from `xserver-xorg-input-kbd: num lock and caps lock led no longer work'. forcemerge 442887 443646 Bug#442887: Xserver 1.4 breaks caps lock and num lock leds Bug#443646: caps lock and scroll lock leds no longer work Bug#440743: xserver-xorg-input-kbd: caps-lock led on thinkpad does not work anymore Bug#443092: xorg: scrolllock led (used for keyboard layout en/ru indication) ain't working after 7.2=7.3 upgrade Bug#443401: xorg: The lights of Caps Lock and Num Lock can not be turned on. Bug#443582: xorg: LED's not working correctly anymore Forcibly Merged 440743 442887 443092 443401 443582 443646. 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#389007: Regression: Radeon 9200 powers off Apple Cinema Display connected via DVI
Hi Roger, Is there anything new about this bug? Did you try 6.7.19x currently in experimental? What kind of machine is this? Your bug report makes me think of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443570 and https://bugs.freedesktop.org/show_bug.cgi?id=12525 This one is fixed upstream with Option MacModel mini, it would be nice to test this with latest upstream git snapshot. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348054: xserver-xorg: [ati/radeon] Desktop window corrupted with ghost images
On Wed, Jun 20, 2007 at 12:42:23AM +0200, Brice Goglin wrote: Mark Brown wrote: On Tue, Jun 19, 2007 at 09:33:16PM +0200, Brice Goglin wrote: About a years ago, you reported a bug to the Debian BTS regarding desktop windows being corrupted with ghost images on a ATI board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. I still see problems with the cursor when it goes to the very edge of the screen with current versions. Which exact versions of xserver-xorg-core and xserver-xorg-video-ati do you have? xserver-xorg-core is 2:1.3.0.0.dfsg-6 in testing and unstable, xserver-xorg-video-ati is 1:6.6.192-1 in experimental, it would be good to test with both. Anything new about this bug with a recent Xserver and ATI driver? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#430058: marked as done (xorg: X server crash using video player in a secondary desktop)
Your message dated Sun, 23 Sep 2007 11:00:34 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#430058: xorg: X server crash using video player in a secondary desktop 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: xorg Version: 1:7.2-3 Severity: important -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-rc5.debian-generic (SMP w/1 CPU core) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xorg depends on: ii gnome-terminal [x-terminal- 2.14.2-2 The GNOME 2 terminal emulator appl ii konsole [x-terminal-emulato 4:3.5.7-1X terminal emulator for KDE ii libgl1-mesa-glx 6.5.2-5 A free implementation of the OpenG ii libglu1-mesa6.5.2-5 The OpenGL utility library (GLU) ii type-handling [not+sparc] 0.2.21 dpkg architecture generation scrip ii xbase-clients 1:7.2.ds2-2 miscellaneous X clients ii xfonts-100dpi 1:1.0.0-3100 dpi fonts for X ii xfonts-75dpi1:1.0.0-375 dpi fonts for X ii xfonts-base 1:1.0.0-4standard fonts for X ii xfonts-scalable 1:1.0.0-6scalable fonts for X ii xkb-data0.9-4X Keyboard Extension (XKB) configu ii xorg-docs 1:1.4-2 Miscellaneous documentation for th ii xserver-xorg1:7.2-3 the X.Org X server ii xterm [x-terminal-emulator] 225-1X terminal emulator ii xutils 1:7.1.ds.3-1 X Window System utility programs Versions of packages xorg recommends: ii libgl1-mesa-dri 6.5.2-5A free implementation of the OpenG -- no debconf information If i have any video player playing a video on a secondary desktop in KDE or gnome and y drop to a shell by Ctrl Atl F1, when i go back to X session by Ctrl Atl F7, X server crash and it is restarted suddenly. I have a Radeon 9250, the problem appears with ati or radeon driver. I paste 'lspci' info: 01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01) 01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (Secondary) (rev 01) ---End Message--- ---BeginMessage--- Closing since I never got any reply to my question 3 months ago. If you can still reproduce with xserver-xorg-core 1.4 (currently in experimental) and xserver-xorg-video-ati 6.7.193 (currently in experimental), feel free to reopen, and please send all required information (as explained in my previous mail). But since secondary desktop probably means MergedFB here, and MergedFB has been dropped in favor of RandR 1.2 in recent drivers, I guess this bug might be irrelevant nowadays anyway. Brice ---End Message---
Bug#436536: xserver-xorg-video-ati: Xorg does not start on a PowerMacintosh 9600/300 with an ATI Mach64 PCI video card
On Sun, Aug 19, 2007 at 11:46:05PM +0200, Damiano Giorgi wrote: After a deadly struggle I somehow managed to get xserver-xorg-video-ati 1:6.6.193-1 installed, but it didn't help: the X server gives the very same errors (log files available, but I'm sure they are more or less the same). It is worth noting that I am not able to get millions of colors in Mac OS 8.6 either (but the other color depths work). One final note. I'm using Ben Herrenschmidt's Mac OS utility BootX to boot Linux on this machine. If I select the No Video Driver option in BootX (which is equivalent to passing video=ofonly, i.e. using Open Firmware video settings) I get 1152x870 on the Linux console. If I don't use that option, I get something like 640x480 on the console. However, this in no way affects the behavior of the X server, it does not work either way. Maybe this issue is unrelated, but I thought that reporting it couldn't hurt. Please let me know if there are any other tests you want me to perform. Testing xserver-xorg-video-ati 6.7.193 currently in experimental would be nice (or 6.7.192 if 193 is not build on powerpc yet). Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439254: xserver-xorg-video-ati: Does not enable default resolution
On Thu, Aug 23, 2007 at 06:30:55PM +0200, Michael Biebl wrote: upgraded to the latest radeon driver from exp which is said to support tv-out (which I haven't tested yet). I built the driver against the xorg-server from unstable myself, as I didn't want to upgrade all the other components. My panel size (laptop) is 1680x1050. xrandr shows: Screen 0: minimum 320 x 200, current 1280 x 768, maximum 1600 x 1200 VGA-0 disconnected (normal left inverted right) LVDS connected 1280x768+0+0 (normal left inverted right) 0mm x 0mm 1680x1050 60.7 + 1280x800 60.0 1280x768 60.0* 1024x768 60.0 800x60060.3 640x48059.9 S-video disconnected (normal left inverted right) So 1280x768 is chosen by the xserver, although 1680x1050 is my default. The Xorg.0.log says something about the width of my virtual size being to wide. I don't exactly know, what that means and how I can fix that. I can switch to my preferred solution via xrandr -s 1680x1050, but that doesn't work e.g. for gdm. Maybe you can help me, and tell me if I misconfigured something. Anything new about this bug with latest 1:6.7.193-1 in experimental or upstream git ? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440918: xserver-xorg-video-ati: supertux lost its textures after hibernation
On Wed, Sep 05, 2007 at 01:39:01PM +0200, Ji??í Pale??ek wrote: Package: xserver-xorg-video-ati Version: 1:6.7.192-1~7.2 Severity: normal Hello, Looks like I never received this mail, it might have been caught by the spam filter on debian-x. Sorry for the delay then... 1:6.7.192-1~7.2 is not a package version from Debian, please test with an official package, especially 1:6.7.193-1 currently in experimental. You'll have to upgrade to xserver-xorg-core 1.4, it might matter for suspend-related problems. when I play supertux (OpenGL mode is on), hibernate and resume the computer, supertux display is completely garbled (it seems like it has loast its textures, so everything looks like a rectangle), see screenshot. Apart from the dirty image, is the game apparently still playable? No lockup or so? If you exit supertux and restart it, do you get dirty textures again? What desktop environment are you running? Nothing compositing such as compiz, kwin, or enlightenment? Same problem if you start X using startx /usr/bin/xterm, launch twm and supertux in there? Please send the whole output of /usr/share/bug/xserver-xorg/script 31 (without gzipping it, please :)) Could you also show the difference between the Xorg log before and after suspend/resume? Brice
Processed: xmodmap run at X startup no longer takes effect
Processing commands for [EMAIL PROTECTED]: forwarded 443473 https://bugs.freedesktop.org/show_bug.cgi?id=12523 Bug#443473: modifying [Caps Lock] via xmodmap is broken Bug#443044: x11-xserver-utils: xmodmap run at X startup no longer takes effect Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=12523. 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#443044: xmodmap run at X startup no longer takes effect
forwarded 443473 https://bugs.freedesktop.org/show_bug.cgi?id=12523 thank you This bug has been reported upstream at the URL above. Feel free to add any comments there if you think it could help. I tried playing with my .xsession to reproduce your problem, but I couldn't. So it'd be better if you could talk there directly. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#430067: xserver-xorg: mplayer causes xserver crash
On Fri, Jun 22, 2007 at 08:47:29AM +0200, Brice Goglin wrote: clayton wrote: Occasionally (not reliably repeatable) mplayer brings down X. This backtrace from the attached log comes from the most recent event. Backtrace: 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c8591] 1: /lib/libc.so.6 [0xb7dbfe28] 2: /usr/lib/xorg/modules/drivers//atimisc_drv.so [0xb7bd406e] 3: /usr/bin/X [0x80dc8bf] 4: /usr/lib/xorg/modules/extensions//libextmod.so(XvdiPutImage+0x174) [0xb7c933$ 5: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7c96398] 6: /usr/bin/X [0x81549be] 7: /usr/bin/X(Dispatch+0x19f) [0x808ed3f] 8: /usr/bin/X(main+0x495) [0x8076e85] 9: /lib/libc.so.6(__libc_start_main+0xdc) [0xb7dabebc] 10: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x80761a1] Could you try xserver-xorg-video-ati 1:6.6.192-1 currently in experimental? The same bug has been reported upstream at the URL above, feel free to add some comments there if you think it may help. Ping? Please try xserver-xorg-video-ati 6.7.193 currently in experimental. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443145: marked as done (Driver doesn't honour specified resolution, and other oddness (might be libxrandr2))
Your message dated Sun, 23 Sep 2007 11:41:23 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#443145: Driver doesn't honour specified resolution, and other oddness (might be libxrandr2) 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: package xserver-xorg-video-ati Version: 1:6.7.192-3 Severity: normal --- Please enter the report below this line. --- This problem is also apparent in the 1:6.7.192-4 driver, is related to the xrandr changes, and might be better filed vs. that. My xorg.conf specifies: Section Monitor Identifier Generic Monitor Option DPMS HorizSync 28-76 VertRefresh 43-85 DisplaySize 328 246 #Default mode 1152x864: 108.0 MHz, 67.5 kHz, 75.0 Hz Modeline 1152x864 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync #Default mode 1024x768: 94.5 MHz, 68.7 kHz, 85.0 Hz Modeline 1024x768 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync #Default mode 800x600: 56.3 MHz, 53.7 kHz, 85.1 Hz Modeline 800x600 56.30 800 832 896 1048 600 601 604 631 +hsync +vsync #Default mode 640x480: 36.0 MHz, 43.3 kHz, 85.0 Hz Modeline 640x480 36.00 640 696 752 832 480 481 484 509 -hsync -vsync EndSection Section Screen Identifier Default Screen Device ATI Radeon x700 AGP Monitor Generic Monitor DefaultDepth24 SubSection Display Depth 16 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1152x864 1024x768 800x600 640x480 EndSubSection EndSection When the xserver starts, I get this in my log: (II) RADEON(0): DDC Type: 3, Detected Monitor Type: 0 (II) RADEON(0): Found color CRT connected to primary DAC in RADEONProbeOutputModes (II) RADEON(0): I2C device VGA_DDC:ddc2 registered at address 0xA0. (II) RADEON(0): I2C device VGA_DDC:ddc2 removed. (II) RADEON(0): I2C device DVI_DDC:ddc2 registered at address 0xA0. (II) RADEON(0): I2C device DVI_DDC:ddc2 removed. (II) RADEON(0): I2C device DVI_DDC:ddc2 registered at address 0xA0. (II) RADEON(0): I2C device DVI_DDC:ddc2 removed. (II) RADEON(0): I2C device DVI_DDC:ddc2 registered at address 0xA0. (II) RADEON(0): I2C device DVI_DDC:ddc2 removed. (II) RADEON(0): DDC Type: 2, Detected Monitor Type: 0 (II) RADEON(0): Detected Monitor Type: 0 (II) RADEON(0): Output VGA-0 connected (II) RADEON(0): Output S-video disconnected (II) RADEON(0): Output DVI-0 disconnected (II) RADEON(0): Output VGA-0 using initial mode 1280x768 after xf86InitialConfiguration and sure enough it sets my resolution to 1280x768, even though it's not a listed mode in my xorg.conf. I figured out how to work around this-- I can either use xrandr, or add the line: Option PreferredMode 1152x864 To the 'monitor' section of the xorg.conf. The preferred mode solution works, however that leaves it's own oddness in my logs: Midway in the xorg.0.log: (II) RADEON(0): ref_freq: 2700, min_pll: 2, max_pll: 5, xclk: 4, sclk: 425.00, mclk: 432.00 (II) RADEON(0): PLL parameters: rf=2700 rd=7 min=2 max=5; xclk=4 (II) RADEON(0): Bios Connector table: (II) RADEON(0): Port0: DDCType-3, DACType-0, TMDSType--1, ConnectorType-1 (II) RADEON(0): Port2: DDCType-3, DACType-1, TMDSType--1, ConnectorType-5 (II) RADEON(0): Port3: DDCType-2, DACType-1, TMDSType-0, ConnectorType-2 (II) RADEON(0): Output VGA-0 using monitor section Generic Monitor (**) RADEON(0): Option PreferredMode 1152x864 (II) RADEON(0): I2C bus VGA_DDC initialized. (II) RADEON(0): Output S-video has no monitor section (II) RADEON(0): Output DVI-0 has no monitor section (II) RADEON(0): I2C bus DVI_DDC initialized. (II) RADEON(0): TMDS PLL from BIOS: 16500 a0112 (II) RADEON(0): Port0: Monitor -- AUTO Connector -- VGA DAC Type -- Primary TMDS Type -- None DDC Type -- VGA_DDC OK, it sees the Preffered Mode and sets it. Late in the xorg.0.log: (II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message. (WW) RADEON(0): Option PreferredMode is not used (--) RandR disabled OK- xrandr ignores it, but no longer sets the 1280 x 768 resolution, which is fine, but makes for a confusing log trail. So basically, setting PreferredMode fixes my problem, but: 1) If I have modes specified, why not honour
Bug#388737: xserver-xorg-video-ati: TV-in black screen on Theatre 200 / radeon 8500
On Thu, Jun 21, 2007 at 10:19:07PM -0700, David Liontooth wrote: Salut Brice, Brice Goglin wrote: Several months ago, you reported a bug to the Debian BTS regarding the TV-input not working on our ATI board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? I'll keep you posted if I get a chance to retest with recent xorg -- thanks for looking at this! Ping? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 443647 is normal
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.8 severity 443647 normal Bug#443647: xkb-data missing some characters in gurmukhi (gur) keymap Severity set to `normal' from `grave' 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#443587: more info
Nadav Kavalerchik wrote: 1024x768 (0x4f) 65.0MHz -HSync -VSync h: width 1024 start 1048 end 1696 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 1024x768 (0x50) 65.0MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz Ok, thanks, the only difference is in h: end unless I am mistaken. The first mode seems to make the server report the following surprising message. It might explain why you get a distorted image when trying it. Maybe the server should just disable such a violating standard mode? (II) RADEON(0): First detailed timing not preferred mode in violation of standard!(II) RADEON(0): redX: 0.565 redY: 0.332 greenX: 0.313 greenY: 0.534 (II) RADEON(0): blueX: 0.157 blueY: 0.140 whiteX: 0.313 whiteY: 0.328 (II) RADEON(0): Manufacturer's mask: 0 (II) RADEON(0): Supported additional Video Mode: (II) RADEON(0): clock: 65.0 MHz Image Size: 304 x 228 mm (II) RADEON(0): h_active: 1024 h_sync: 1048 h_sync_end 1696 h_blank_end 1344 h_border: 0 (II) RADEON(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 806 v_border: 0 (II) RADEON(0): EDID (in hex): (II) RADEON(0): 000030f0546e (II) RADEON(0): 0103801e167828c7749055508828 (II) RADEON(0): 2350540001010101010101010101 (II) RADEON(0): 01010101010164190040410026301888 (II) RADEON(0): 362030e41018 (II) RADEON(0): (II) RADEON(0): (II) RADEON(0): 004f Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443584: xrandr does not recognise conncted s-video
Nadav Kavalerchik wrote: |xrandr --addmode S-video 800x600| |xrandr --output S-video --mode 800x600| works great :-) and stays this way too. no after effects when i use the mouse or the keyboard. Good to know. I'll keep the bug open until I get some clarification from Alex about how we are supposed to enabled TV-out these days. although i watch the output display on the S-Video (tv) i get disconnected message from xrandr. laptop:~# xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2304 x 1024 VGA-0 disconnected (normal left inverted right x axis y axis) LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0*60.0 800x60060.3 640x48059.9 S-video disconnected (normal left inverted right x axis y axis) 800x60060.3 Probably related to the fact that TV-output load detection is disabled for now. i tried adding other modes: 1024x768 and 640x480 with no success, way ? laptop:~# xrandr --addmode S-video 1024x768 X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 155 (RANDR) Minor opcode of failed request: 18 () Serial number of failed request: 16 Current serial number in output stream: 17 I have no idea whether other modes can work on a TV-output... also, when playing video with vlc/xine/mplayer i have to change output driver to X11 otherwise no output on the S-Video (tv) only on the LVDS I guess the XV overlay can only appear on one CRTC. You should either not display the same image on both outputs (disable the LVDS, or move it so that it does not overlap TV-output image) or maybe use xvattr to switch the overlay on the other output, with something like: xvattr -a XV_SWITCHCRT -v 1 Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443585: switching to s-video sets LVDS and S-Video brightness to max and inverts colors
Nadav Kavalerchik wrote: xrandr --output LVDS --off --output S-video --auto did not help until i rebooted and tried again. if i plug the s-video during a session and not while it was booting xrandr is not able to use s-video. what was even better is your other suggestion: xrandr --addmode S-video 800x600 xrandr --output S-video --mode 800x600 xrandr --output LVDS --off So you're saying that once you workaround the S-video enabling problems (reported in other bug reports), switching the S-video using xrandr does avoid your brightness problems? (which means the bug can be closed) Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348054: xserver-xorg: [ati/radeon] Desktop window corrupted with ghost images
notfound 348054 1:6.7.193-1 thanks On Sun, Sep 23, 2007 at 10:55:52AM +0200, Brice Goglin wrote: Anything new about this bug with a recent Xserver and ATI driver? Seems to be fixed. -- You grabbed my hand and we fell into it, like a daydream - or a fever. signature.asc Description: Digital signature
Processed: Re: Bug#348054: xserver-xorg: [ati/radeon] Desktop window corrupted with ghost images
Processing commands for [EMAIL PROTECTED]: notfound 348054 1:6.7.193-1 Bug#348054: xserver-xorg: [ati/radeon] Desktop window corrupted with ghost images Bug no longer marked as found in version 1:6.7.193-1. 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#443377: xserver-xorg-video-ati: xrandr 1.2 gives wierd coloration on VGA display
Ken Bloom wrote: It just occurred to me to mention that the projector in question is a rather complicated setup, because it's part of a multimedia classroom setup at IIT that is used to tape lectures and transmit them to remote viewing sites, and to post the lectures on the internet. I observed the same 1024x768 behavior on one of those setups with xrandr 1.1, X.org 7.2 and the fglrx driver about 2 weeks ago, so you can probably ignore the 1024x768 behavior, at least for now. It also wasn't reproducible on a more normal LCD setup. Ok, thanks for the clarification. The 1280x1024 behavior, which is reproducible on other monitors is still relevant. Could you latest upstream git snapshot in case it helps? If not, we might have to open an upstream bug at bugzilla.freedesktop.org. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296616: Bug#291853: xkbcomp warns about RALT having 2 symbols
On Sun, Sep 23, 2007 at 03:34:40AM +0200, Mohammed Adnène Trojette wrote: do you have something defined in your .xmodmap file? No, I have no .xmodmap file. What is the result of the commands 'xmodmap' and 'xmodmap -pk'? attached. In the meantime, I get even more messages btw.: expected keysym, got XF86KbdLightOnOff: line 70 of pc expected keysym, got XF86KbdBrightnessDown: line 71 of pc expected keysym, got XF86KbdBrightnessUp: line 72 of pc expected keysym, got XF86KbdLightOnOff: line 70 of pc expected keysym, got XF86KbdBrightnessDown: line 71 of pc expected keysym, got XF86KbdBrightnessUp: line 72 of pc The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server Btw... perhaps, in the time of xdm, kdm, gdm and all that stuff I should probably add that these messages do not get logged in the Xorg.*.log file but ony appear on stderr from, for example, startx. Attached this as well. -- There are 10 types of people in the world: Those who understand binary, and those who don't... xmodmap: up to 3 keys per modifier, (keycodes in parentheses): shift Shift_L (0x32), Shift_R (0x3e) lockCaps_Lock (0x42) control Control_L (0x25), Control_R (0x6d) mod1Alt_L (0x40), Meta_L (0x9c) mod2Num_Lock (0x4d) mod3 mod4Super_L (0x7f), Hyper_L (0x80) mod5Mode_switch (0x5d), ISO_Level3_Shift (0x71), ISO_Level3_Shift (0x7c) There are 6 KeySyms per KeyCode; KeyCodes range from 8 to 255. KeyCode Keysym (Keysym) ... Value Value (Name) ... 8 9 0xff1b (Escape) 10 0x0031 (1) 0x0021 (exclam) 0x00b9 (onesuperior)0x00a1 (exclamdown) 0x00b9 (onesuperior)0x00a1 (exclamdown) 11 0x0032 (2) 0x0022 (quotedbl) 0x00b2 (twosuperior) 0x0ac3 (oneeighth) 0x00b2 (twosuperior)0x0ac3 (oneeighth) 12 0x0033 (3) 0x00a7 (section)0x00b3 (threesuperior) 0x00a3 (sterling) 0x00b3 (threesuperior) 0x00a3 (sterling) 13 0x0034 (4) 0x0024 (dollar) 0x00bc (onequarter) 0x00a4 (currency) 0x00bc (onequarter) 0x00a4 (currency) 14 0x0035 (5) 0x0025 (percent)0x00bd (onehalf) 0x0ac4 (threeeighths) 0x00bd (onehalf)0x0ac4 (threeeighths) 15 0x0036 (6) 0x0026 (ampersand) 0x00ac (notsign) 0x0ac5 (fiveeighths)0x00ac (notsign)0x0ac5 (fiveeighths) 16 0x0037 (7) 0x002f (slash) 0x007b (braceleft) 0x0ac6 (seveneighths) 0x007b (braceleft) 0x0ac6 (seveneighths) 17 0x0038 (8) 0x0028 (parenleft) 0x005b (bracketleft) 0x0ac9 (trademark) 0x005b (bracketleft)0x0ac9 (trademark) 18 0x0039 (9) 0x0029 (parenright) 0x005d (bracketright) 0x00b1 (plusminus) 0x005d (bracketright) 0x00b1 (plusminus) 19 0x0030 (0) 0x003d (equal) 0x007d (braceright) 0x00b0 (degree) 0x007d (braceright) 0x00b0 (degree) 20 0x00df (ssharp) 0x003f (question) 0x005c (backslash) 0x00bf (questiondown) 0x005c (backslash) 0x00bf (questiondown) 21 0x0027 (apostrophe) 0x0060 (grave) 0x00b8 (cedilla) 0x00b8 (cedilla)0x00b8 (cedilla)0x00b8 (cedilla) 22 0xff08 (BackSpace) 0xfed5 (Terminate_Server) 23 0xff09 (Tab)0xfe20 (ISO_Left_Tab) 24 0x0071 (q) 0x0051 (Q) 0x0040 (at) 0x07d9 (Greek_OMEGA)0x0040 (at) 0x07d9 (Greek_OMEGA) 25 0x0077 (w) 0x0057 (W) 0x01b3 (lstroke)0x01a3 (Lstroke)0x01b3 (lstroke)0x01a3 (Lstroke) 26 0x0065 (e) 0x0045 (E) 0x20ac (EuroSign) 0x20ac (EuroSign) 0x20ac (EuroSign) 0x20ac (EuroSign) 27 0x0072 (r) 0x0052 (R) 0x00b6 (paragraph) 0x00ae (registered) 0x00b6 (paragraph) 0x00ae (registered) 28 0x0074 (t) 0x0054 (T) 0x03bc (tslash) 0x03ac (Tslash) 0x03bc (tslash) 0x03ac (Tslash) 29 0x007a (z) 0x005a (Z) 0x08fb (leftarrow) 0x00a5 (yen)0x08fb (leftarrow) 0x00a5 (yen) 30 0x0075 (u) 0x0055 (U) 0x08fe (downarrow) 0x08fc (uparrow)0x08fe (downarrow) 0x08fc (uparrow) 31 0x0069 (i) 0x0049 (I) 0x08fd (rightarrow) 0x02b9 (idotless) 0x08fd (rightarrow) 0x02b9 (idotless) 32 0x006f (o) 0x004f (O) 0x00f8 (oslash) 0x00d8 (Oslash) 0x00f8 (oslash) 0x00d8 (Oslash) 33 0x0070 (p) 0x0050 (P) 0x00fe (thorn) 0x00de (THORN) 0x00fe (thorn) 0x00de
Bug#443441: marked as done (Duplicate mouse events with Xserver 1.4)
Your message dated Sun, 23 Sep 2007 13:36:40 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#443441: Duplicate mouse events with Xserver 1.4 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 Version: 1:7.3+2 Severity: important Hi. With Xorg 7.3 there are various input problems. First, the keyboard numlock led doesn't turn on, but numlock can still be toggled. Additionally the toolbar menu in firefox isn't accessible, it just doesn't recognize any clicks. Then, drop down menu from webpages show and immediately dissappear if activated. You can't use them at all. Toolbars of other applications like evince and gftp are clickable, but dissappear with releasing the mouse button. The same applies to grips drop down menus. Downgrading xserver-xorg, xserver-xorg-core, xserver-xorg-input-* and xserver-xorg-video-* to the latest testing packages solved the problems. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xfree86 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-29 11:59 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1669528 2007-09-16 20:56 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600/GeForce 6600 GT] (rev a2) /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 5084 2007-09-19 17:39 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type man XF86Config-4 at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the ### BEGIN DEBCONF SECTION line above, and/or after the # ### END DEBCONF SECTION line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file? in /usr/share/doc/xfree86-common/FAQ.gz. Section Files FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID FontPath/usr/share/fonts/X11/100dpi:unscaled FontPath/usr/share/fonts/X11/75dpi:unscaled FontPath/usr/share/fonts/X11/encodings FontPath/usr/share/fonts/X11/misc FontPath/usr/share/fonts/X11/Type1 FontPath/usr/share/fonts/truetype FontPath/usr/lib/X11/fonts/misc FontPath/usr/lib/X11/fonts/100dpi:unscaled FontPath/usr/lib/X11/fonts/75dpi:unscaled FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/lib/X11/fonts/Speedo EndSection Section Module Loadbitmap Loaddbe Loadddc Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout de Option XkbVariantnodeadkeys EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol ImPS/2 Option Emulate3Buttons true Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Generic Mouse Driver mouse Option SendCoreEventstrue Option Device/dev/input/mice Option Protocol ImPS/2 Option Emulate3Buttons true Option ZAxisMapping 4 5
xorg-server: Changes to 'debian-unstable'
debian/changelog |3 ++-
debian/control |2 +-
debian/rules | 11 +++
3 files changed, 14 insertions(+), 2 deletions(-)
New commits:
commit 50ddaffe30920254835c7bfcc152a3f9860d1c2a
Author: Julien Cristau [EMAIL PROTECTED]
Date: Sun Sep 23 13:56:59 2007 +0200
Don't build Xfbdev on !linux.
Xfbdev is linux-only, so don't build it on other systems.
Additionally, don't build the kdrive-based servers that we don't ship.
diff --git a/debian/changelog b/debian/changelog
index 7af3b61..d76314e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -40,8 +40,9 @@ xorg-server (2:1.4-3) UNRELEASED; urgency=low
13949f997289068354e83bc83e50d97b8232efb1 to remove the type1 module: patch
05_kill_type1.diff replaces 48_disable_type1.diff, and is now enabled in
debian/patches/series.
+ * Don't build kdrive-based servers we're not shipping.
- -- Christian Perrier [EMAIL PROTECTED] Sun, 23 Sep 2007 08:39:42 +0200
+ -- Julien Cristau [EMAIL PROTECTED] Sun, 23 Sep 2007 13:55:28 +0200
xorg-server (2:1.4-2) unstable; urgency=low
diff --git a/debian/control b/debian/control
index 6ef2273..292823b 100644
--- a/debian/control
+++ b/debian/control
@@ -183,7 +183,7 @@ Description: nested X server
This package is built from the X.org xserver module.
Package: xserver-xfbdev
-Architecture: any
+Architecture: alpha amd64 arm armeb armel hppa i386 ia64 lpia m32r m68k mips
mipsel powerpc ppc64 sh3 sh3eb sh4 sh4eb sparc
Depends: ${shlibs:Depends}, ${misc:Depends}
Recommends: xbase-clients
Description: Linux framebuffer device tiny X server
diff --git a/debian/rules b/debian/rules
index 1959722..8395999 100755
--- a/debian/rules
+++ b/debian/rules
@@ -22,12 +22,19 @@ endif
DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
+DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
ifeq ($(DEB_BUILD_GNU_TYPE), $(DEB_HOST_GNU_TYPE))
confflags += --build=$(DEB_HOST_GNU_TYPE)
else
confflags += --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE)
endif
+ifeq ($(DEB_HOST_ARCH_OS), linux)
+ build_xfbdev = --enable-xfbdev
+else
+ build_xfbdev = --disable-xfbdev
+endif
+
BUILD_XPRINT = false
ifeq ($(BUILD_XPRINT), true)
confflags += --enable-xprint
@@ -50,6 +57,10 @@ confflags += --disable-static \
--enable-vfb \
--enable-kdrive \
--enable-xephyr \
+--disable-xsdl \
+--disable-xfake \
+$(build_xfbdev) \
+--disable-kdrive-vesa \
--disable-lbx \
--enable-freetype \
--disable-xorgconfig \
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443584: xrandr does not recognise conncted s-video
using the Fn-F4 keys i can switch the tv output into 1024x768 mode , BUT it's buggy as i reported a bug about it (display gets distorted) so i don't use it. i'm just mentioning it to say that the s-video output can probably support 1024x768. with Xv version 2.2 the XV_SWITCHCRT syntax changed (i think) and correct syntax is probably... xvattr -a XV_CRTC -v 1 (although the min/max values seems like a true/false boolean ?) Name: XV_CRTC Flags: XvGettable XvSettable Min value: -1 Max value: 1 Current value: -1 to play video with overly support on s-video (tv) i used : xvattr -a XV_CRTC -v 1 to play video with overly support on LVDS (laptop) i used : xvattr -a XV_CRTC -v 0 they didn't work on both displays simultaneously :-( but that seems ok :-) On 9/23/07, Brice Goglin [EMAIL PROTECTED] wrote: Nadav Kavalerchik wrote: |xrandr --addmode S-video 800x600| |xrandr --output S-video --mode 800x600| works great :-) and stays this way too. no after effects when i use the mouse or the keyboard. Good to know. I'll keep the bug open until I get some clarification from Alex about how we are supposed to enabled TV-out these days. although i watch the output display on the S-Video (tv) i get disconnected message from xrandr. laptop:~# xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2304 x 1024 VGA-0 disconnected (normal left inverted right x axis y axis) LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0*60.0 800x60060.3 640x48059.9 S-video disconnected (normal left inverted right x axis y axis) 800x60060.3 Probably related to the fact that TV-output load detection is disabled for now. i tried adding other modes: 1024x768 and 640x480 with no success, way ? laptop:~# xrandr --addmode S-video 1024x768 X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 155 (RANDR) Minor opcode of failed request: 18 () Serial number of failed request: 16 Current serial number in output stream: 17 I have no idea whether other modes can work on a TV-output... also, when playing video with vlc/xine/mplayer i have to change output driver to X11 otherwise no output on the S-Video (tv) only on the LVDS I guess the XV overlay can only appear on one CRTC. You should either not display the same image on both outputs (disable the LVDS, or move it so that it does not overlap TV-output image) or maybe use xvattr to switch the overlay on the other output, with something like: xvattr -a XV_SWITCHCRT -v 1 Brice
Bug#443697: xserver-xorg: X crashes when i press the key giving keycode 175
Package: xserver-xorg Version: 1:7.3+2 Severity: normal I just upgraded to xserver-xorg 7.3+2, now X crashes when i press the key giving keycode 175, this happens with kde running as well as with a failsafe session (only xterm). all other keys work fine xev /tmp/x looked like this: KeyPress event, serial 24, synthetic NO, window 0x61, root 0x1a6, subw 0x0, time 1719767, (85,97), root:(87,99), state 0x0, keycode 175 (keysym 0x1008ff1c, XF86AudioRecord), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False -- Package-specific info: 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-10-20 15:03 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1827360 2007-09-16 23:52 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 05:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7600 GS] (rev a1) /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 5790 2007-09-23 15:04 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # /etc/X11/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 /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files RgbPath /usr/lib/X11/rgb FontPath/usr/share/fonts/X11/misc FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/X11R6/lib/X11/fonts/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/100dpi FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi FontPath/usr/X11R6/lib/X11/fonts/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadi2c Loadbitmap Loadddc # Loaddbe Loadextmod Loadfreetype Loadglx Loadint10 Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 #a4techKBS8 Option XkbLayout de Option XkbVariantnodeadkeys EndSection Section InputDevice Identifier A4Tech KBS26 Driver evdev Option CoreKeyboard Option evBits+0-1 -2-16 +17 -18-19 +20 -21-23 Option ledBits +0-4 -5-7 Option keyBits -0 +1-83 -84 +85-100 -101 +102-111 -112 +113-117 -118 +119 -120 +121-138 -139-182 +183-194 -195-239 +240 -241-243 # Option XkbRules xorg # Option XkbModel pc105 #a4techKBS8 Option XkbLayout de Option XkbVariantnodeadkeys EndSection Section InputDevice Identifier A4Tech Office8K Driver evdev Option CorePointer true Option Device/dev/input/event3 # Option Name A4Tech RF USB Receiver # Option Phys usb-:00:1d.0-2/input0 # Option evBits+0 +1 +2 -3 # Option relBits +0 +1 -2-7 +8 +9 # Option keyBits -0-112 +113-116 -117-127 +128 -129-130 +131 -132 +133-138 -139 +140 -141 +142-144 -145-154 +155-156 -157 +158-159 -160-162 +163-166 -167-170 +171-173 -174-180 +181-182 -183-205 +206 -207-209 +210 -211-230 +231-234 -235-271 +272-279 -280-396 +397 -398-420 +421 -422 +423 Option Resolution800 Option SendCoreEvents Option Emulate3Buttons
Bug#443587: both modes are useful, after all :-)
when i use Fn-F4 to switch to s-video (tv) and get the display distorted. i use the first 60.0 Hz mode to fix the display ! , which normally distorts the display. it works only when i use the Fn keys, otherwise i use the second 60.0 Hz mode. in which the laptop loads into normally. LVDS connected 1024x768+0+0 (0x4f) normal (normal left inverted right x axis y axis) 0mm x 0mm Identifier: 0x4d Timestamp: 2349400 Subpixel: horizontal rgb Clones: CRTC: 0 CRTCs: 0 scaler: full backlight: 255 (0x00ff) range: (0,255) 1024x768 (0x4f) 65.0MHz -HSync -VSync h: width 1024 start 1048 end 1696 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 1024x768 (0x50) 65.0MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 800x600 (0x51) 40.0MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew0 clock 37.9KHz v: height 600 start 601 end 605 total 628 clock 60.3Hz 640x480 (0x52) 25.2MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew0 clock 31.5KHz v: height 480 start 490 end 492 total 525 clock 59.9Hz -- 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
On Sun, 2007-09-23 at 06:29 +0100, Ben Hutchings wrote: snip Run this with the argument -*-fixed-*-*-*-*-*-*-*-*-*-*-JISX0208.1983-0 and you should see the bug (or not). I suspect you won't see it. With my normal X server I get: $ ./listfonts -*-fixed-*-*-*-*-13-*-*-*-*-*-JISX0208.1983-0 -jis-fixed-medium-r-normal--13-94-100-100-c-0-jisx0208.1983-0 doesn't exist! -misc-fixed-medium-r-normal--13-94-100-100-c-0-jisx0208.1983-0 doesn't exist! With an Xvfb server in a clean etch chroot I get: $ DISPLAY=:1 ,/listfonts -*-fixed-*-*-*-*-13-*-*-*-*-*-JISX0208.1983-0 -jis-fixed-medium-r-normal--13-94-100-100-c-0-jisx0208.1983-0 exists -misc-fixed-medium-r-normal--13-94-100-100-c-0-jisx0208.1983-0 exists However: $ xlsfonts | grep jisx0208 -jis-fixed-medium-r-normal--0-0-75-75-c-0-jisx0208.1983-0 -jis-fixed-medium-r-normal--16-110-100-100-c-160-jisx0208.1983-0 -jis-fixed-medium-r-normal--16-150-75-75-c-160-jisx0208.1983-0 -jis-fixed-medium-r-normal--24-170-100-100-c-240-jisx0208.1983-0 -jis-fixed-medium-r-normal--24-230-75-75-c-240-jisx0208.1983-0 -misc-fixed-medium-r-normal--0-0-75-75-c-0-jisx0208.1983-0 -misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0 $ diff (xlsfonts | grep jisx0208) (DISPLAY=:1 xlsfonts | grep jisx0208) echo same same And: $ ./listfonts -jis-fixed-medium-r-normal--0-0-75-75-c-0-jisx0208.1983-0 -jis-fixed-medium-r-normal--0-0-75-75-c-0-jisx0208.1983-0 doesn't exist! $ DISPLAY=:1 ./listfonts -jis-fixed-medium-r-normal--0-0-75-75-c-0-jisx0208.1983-0 -jis-fixed-medium-r-normal--0-0-75-75-c-0-jisx0208.1983-0 exists It seems like the servers are offering (in XListFonts) to make 13-pixel fixed for JISX0208 by scaling the 14-pixel or 16-pixel bitmap (ugh!), but my normal X server then disavows that in XListFontsWithInfo. Where do we go from here? Ben. -- Ben Hutchings friends: People who know you well, but like you anyway. signature.asc Description: This is a digitally signed message part
Bug#443585: switching to s-video sets LVDS and S-Video brightness to max and inverts colors
yes, you can close it. a funny think thou... when i use Fn-F4 to switch to s-video (tv) and get the display distorted. i use the first 60.0 Hz mode (which distorts the display, normally) to fix the display ! it works only when i use the Fn keys, otherwise i use the second 60.0 Hz mode. since the S-video is reported disconnected i can't use grandr (gtk gui app) to switch from tv/laptop easily, so still it is a little problems (for my father, that is not familier with the cli xrandr) LVDS connected 1024x768+0+0 (0x4f) normal (normal left inverted right x axis y axis) 0mm x 0mm Identifier: 0x4d Timestamp: 2349400 Subpixel: horizontal rgb Clones: CRTC: 0 CRTCs: 0 scaler: full backlight: 255 (0x00ff) range: (0,255) 1024x768 (0x4f) 65.0MHz -HSync -VSync h: width 1024 start 1048 end 1696 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 1024x768 (0x50) 65.0MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 800x600 (0x51) 40.0MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew0 clock 37.9KHz v: height 600 start 601 end 605 total 628 clock 60.3Hz 640x480 (0x52) 25.2MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew0 clock 31.5KHz v: height 480 start 490 end 492 total 525 clock 59.9Hz On 9/23/07, Brice Goglin [EMAIL PROTECTED] wrote: Nadav Kavalerchik wrote: xrandr --output LVDS --off --output S-video --auto did not help until i rebooted and tried again. if i plug the s-video during a session and not while it was booting xrandr is not able to use s-video. what was even better is your other suggestion: xrandr --addmode S-video 800x600 xrandr --output S-video --mode 800x600 xrandr --output LVDS --off So you're saying that once you workaround the S-video enabling problems (reported in other bug reports), switching the S-video using xrandr does avoid your brightness problems? (which means the bug can be closed) Brice
Bug#443585: marked as done (switching to s-video sets LVDS and S-Video brightness to max and inverts colors)
Your message dated Sun, 23 Sep 2007 17:19:57 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#443585: switching to s-video sets LVDS and S-Video brightness to max and inverts colors 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-video-ati Version: 1:6.7.193-1 Severity: normal --- Please enter the report below this line. --- when i switch to S-Video from LVDS using Fn4 all seems ok at first, BUT when i move the mouse or click it or click the keyboard... both the LVDS and S-Video (TV Screen) gets color inverted and full brightness. and the mouse turns to a huge black box. by pressing Fn4 and cycling through the modes i get clear view again, UNTIL i hit any key or move the mouse, again. and so on... --- System information. --- Architecture: i386 Kernel: Linux 2.6.21-2-686 Debian Release: lenny/sid 500 unstablewww.debian-multimedia.org 500 unstablemirror.isoc.org.il 500 testing mirror.isoc.org.il 500 experimentalwww.debian-multimedia.org 500 etchdebian.beryl-project.org 1 experimentalmirror.isoc.org.il --- Package information. --- Depends (Version) | Installed ==-+-= libc6 (= 2.6.1-1) | 2.6.1-4 xserver-xorg-core (= 2:1.4) | 2:1.4-2 ---End Message--- ---BeginMessage--- Nadav Kavalerchik wrote: yes, you can close it. Ok done. when i use Fn-F4 to switch to s-video (tv) and get the display distorted. i use the first 60.0 Hz mode (which distorts the display, normally) to fix the display ! it works only when i use the Fn keys, otherwise i use the second 60.0 Hz mode. :) Brice ---End Message---
Bug#442907: xserver-xorg-video-mga: Multihead doesn't work on G450
With the update to libpixman, I can now run 1.9.99. It mostly works, except 2d performance is abysmal -- full-screen windows (1152x900 for me) take about a second to redraw. (however, 3d performance is as good, or maybe slightly better, than it ever was) Is this useful for me to report now, or should I wait for whenever it gets pushed into unstable (when upstream will be more nearly finished)? (If so, I've noticed that randr forgets the doublescan flag, and that wmnet's window contents gets placed in the wrong place) In any case, 1.4.7 is sufficiently broken (since dual-heading doesn't work at all) that I'd like to recommend that it not be allowed to propagate. Thank you! - robert jacobs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442907: xserver-xorg-video-mga: Multihead doesn't work on G450
kls wrote: With the update to libpixman, I can now run 1.9.99. It mostly works, except 2d performance is abysmal -- full-screen windows (1152x900 for me) take about a second to redraw. (however, 3d performance is as good, or maybe slightly better, than it ever was) Ok, thanks for the report. Should I mark your bug as fixed in 1.9.99 and let you open a new bug report about 2D being very slow in 1.9.99 (or in 2.0 when it is released)? Is this useful for me to report now, or should I wait for whenever it gets pushed into unstable (when upstream will be more nearly finished)? (If so, I've noticed that randr forgets the doublescan flag, and that wmnet's window contents gets placed in the wrong place) I'll forward your mail to the upstream dev anyway, we'll see what he thinks. In any case, 1.4.7 is sufficiently broken (since dual-heading doesn't work at all) that I'd like to recommend that it not be allowed to propagate. You mean 1.4.7 is more broken than 1.4.6, right? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xorg-server: Changes to 'debian-unstable'
debian/changelog|5
debian/patches/44_XKB_mapping_changes_for_all_core-sending_devices.diff | 149
++
debian/patches/series |1
3 files changed, 154 insertions(+), 1 deletion(-)
New commits:
commit cae73dc9df934f06c4af69a9306d52e5c8257f4e
Author: Brice Goglin [EMAIL PROTECTED]
Date: Sun Sep 23 17:42:19 2007 +0200
Add 44_XKB_mapping_changes_for_all_core-sending_devices.diff
diff --git a/debian/changelog b/debian/changelog
index d76314e..625b5db 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -16,6 +16,9 @@ xorg-server (2:1.4-3) UNRELEASED; urgency=low
[ Brice Goglin ]
* Build the Xfbdev server in new package xserver-xfbdev, closes: #439764.
+ * Add upstream commit 27ad5d74c20f01516a1bff73be283f8982fcf0fe as patch
+44_XKB_mapping_changes_for_all_core-sending_devices.diff to fix broken
+xmodmap invocation in .xsession, closes: #443044.
[ Christian Perrier ]
* Debconf templates and debian/control reviewed by the debian-l10n-
@@ -42,7 +45,7 @@ xorg-server (2:1.4-3) UNRELEASED; urgency=low
debian/patches/series.
* Don't build kdrive-based servers we're not shipping.
- -- Julien Cristau [EMAIL PROTECTED] Sun, 23 Sep 2007 13:55:28 +0200
+ -- Brice Goglin [EMAIL PROTECTED] Sun, 23 Sep 2007 17:32:49 +0200
xorg-server (2:1.4-2) unstable; urgency=low
diff --git
a/debian/patches/44_XKB_mapping_changes_for_all_core-sending_devices.diff
b/debian/patches/44_XKB_mapping_changes_for_all_core-sending_devices.diff
new file mode 100644
index 000..f823591
--- /dev/null
+++ b/debian/patches/44_XKB_mapping_changes_for_all_core-sending_devices.diff
@@ -0,0 +1,149 @@
+From: Daniel Stone [EMAIL PROTECTED]
+Date: Sun, 23 Sep 2007 14:17:03 + (+0300)
+Subject: Input: Generate XKB mapping changes for all core-sending devices (bug
#12523)
+X-Git-Url:
http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commitdiff;h=27ad5d74c20f01516a1bff73be283f8982fcf0fe
+
+Input: Generate XKB mapping changes for all core-sending devices (bug #12523)
+
+When we change the mapping on a core device, make sure we propagate this
+through to XKB for all extended devices as well.
+
+http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443044
+---
+
+--- a/Xi/exevents.c
b/Xi/exevents.c
+@@ -73,6 +73,10 @@ SOFTWARE.
+ #include dixgrabs.h /* CreateGrab() */
+ #include scrnintstr.h
+
++#ifdef XKB
++#include xkbsrv.h
++#endif
++
+ #define WID(w) ((w) ? ((w)-drawable.id) : 0)
+ #define AllModifiersMask ( \
+ ShiftMask | LockMask | ControlMask | Mod1Mask | Mod2Mask | \
+@@ -942,7 +946,7 @@ SetModifierMapping(ClientPtr client, Dev
+ }
+
+ void
+-SendDeviceMappingNotify(CARD8 request,
++SendDeviceMappingNotify(ClientPtr client, CARD8 request,
+ KeyCode firstKeyCode, CARD8 count, DeviceIntPtr dev)
+ {
+ xEvent event;
+@@ -957,6 +961,11 @@ SendDeviceMappingNotify(CARD8 request,
+ ev-count = count;
+ }
+
++#ifdef XKB
++if (request == MappingKeyboard || request == MappingModifier)
++XkbApplyMappingChange(dev, request, firstKeyCode, count, client);
++#endif
++
+ SendEventToAllWindows(dev, DeviceMappingNotifyMask, (xEvent *) ev, 1);
+ }
+
+@@ -992,7 +1001,7 @@ ChangeKeyMapping(ClientPtr client,
+ keysyms.map = map;
+ if (!SetKeySymsMap(k-curKeySyms, keysyms))
+ return BadAlloc;
+-SendDeviceMappingNotify(MappingKeyboard, firstKeyCode, keyCodes, dev);
++SendDeviceMappingNotify(client, MappingKeyboard, firstKeyCode, keyCodes,
dev);
+ return client-noClientException;
+ }
+
+--- a/Xi/setbmap.c
b/Xi/setbmap.c
+@@ -134,7 +134,7 @@ ProcXSetDeviceButtonMapping(ClientPtr cl
+ }
+
+ if (ret != MappingBusy)
+- SendDeviceMappingNotify(MappingPointer, 0, 0, dev);
++ SendDeviceMappingNotify(client, MappingPointer, 0, 0, dev);
+ return Success;
+ }
+
+--- a/Xi/setmmap.c
b/Xi/setmmap.c
+@@ -122,7 +122,7 @@ ProcXSetDeviceModifierMapping(ClientPtr
+ if (ret == MappingSuccess || ret == MappingBusy || ret == MappingFailed) {
+ rep.success = ret;
+ if (ret == MappingSuccess)
+- SendDeviceMappingNotify(MappingModifier, 0, 0, dev);
++ SendDeviceMappingNotify(client, MappingModifier, 0, 0, dev);
+ WriteReplyToClient(client, sizeof(xSetDeviceModifierMappingReply),
+ rep);
+ } else {
+--- a/dix/devices.c
b/dix/devices.c
+@@ -1208,10 +1208,9 @@ SendMappingNotify(unsigned request, unsi
+ }
+ #ifdef XKB
+ if (!noXkbExtension
+- ((request == MappingKeyboard) || (request == MappingModifier))) {
+- XkbApplyMappingChange(inputInfo.keyboard,request,firstKeyCode,count,
+- client);
+-}
++ ((request == MappingKeyboard) || (request == MappingModifier)))
++XkbApplyMappingChange(inputInfo.keyboard, request, firstKeyCode,
Processed: tagging 443044
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.8 tags 443044 + pending Bug#443044: x11-xserver-utils: xmodmap run at X startup no longer takes effect There were no tags set. Bug#443473: modifying [Caps Lock] via xmodmap is broken Tags added: pending 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#443697: xserver-xorg: X crashes when i press the key giving keycode 175
reassign 443697 xserver-xorg-core found 443697 2:1.4-2 forwarded 443697 https://bugs.freedesktop.org/show_bug.cgi?id=12528 tags 443697 +pending thank you Arkadiusz Guzinski wrote: I just upgraded to xserver-xorg 7.3+2, now X crashes when i press the key giving keycode 175, this happens with kde running as well as with a failsafe session (only xterm). all other keys work fine xev /tmp/x looked like this: KeyPress event, serial 24, synthetic NO, window 0x61, root 0x1a6, subw 0x0, time 1719767, (85,97), root:(87,99), state 0x0, keycode 175 (keysym 0x1008ff1c, XF86AudioRecord), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False [...] Backtrace: 0: /usr/bin/X(xf86SigHandler+0x6a) [0x482cca] 1: /lib/libc.so.6 [0x2b66f669c710] 2: /usr/bin/X(GetKeyboardValuatorEvents+0x4c) [0x45d92c] 3: /usr/bin/X(GetKeyboardEvents+0x17) [0x45dc37] 4: /usr/bin/X(xf86PostKeyboardEvent+0x63) [0x49d9e3] 5: /usr/lib/xorg/modules/input//evdev_drv.so [0x2b66f9231d5a] 6: /usr/bin/X [0x482dcf] 7: /usr/bin/X [0x46fbdc] 8: /lib/libc.so.6 [0x2b66f669c710] 9: /lib/libc.so.6(__select+0x13) [0x2b66f6737f63] 10: /usr/bin/X(WaitForSomething+0x6db) [0x55e1fb] 11: /usr/bin/X(Dispatch+0x8b) [0x44df1b] 12: /usr/bin/X(main+0x47c) [0x436a1c] 13: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b66f6688b44] 14: /usr/bin/X(FontFileCompleteXLFD+0x259) [0x435d59] Looks like https://bugs.freedesktop.org/show_bug.cgi?id=12528 It just got fixed upstream, so I'll take the fix and apply it for the next upload. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#443697: xserver-xorg: X crashes when i press the key giving keycode 175
Processing commands for [EMAIL PROTECTED]: reassign 443697 xserver-xorg-core Bug#443697: xserver-xorg: X crashes when i press the key giving keycode 175 Bug reassigned from package `xserver-xorg' to `xserver-xorg-core'. found 443697 2:1.4-2 Bug#443697: xserver-xorg: X crashes when i press the key giving keycode 175 Bug marked as found in version 2:1.4-2. forwarded 443697 https://bugs.freedesktop.org/show_bug.cgi?id=12528 Bug#443697: xserver-xorg: X crashes when i press the key giving keycode 175 Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=12528. tags 443697 +pending Bug#443697: xserver-xorg: X crashes when i press the key giving keycode 175 There were no tags set. Tags added: pending 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]
xorg-server: Changes to 'debian-unstable'
debian/changelog |5 + debian/patches/45_GetKeyboardEvents_reject_out-of-range_keycodes.diff | 33 ++ debian/patches/series |1 3 files changed, 38 insertions(+), 1 deletion(-) New commits: commit 52515167711a69d380ef717f07333400896b57ec Author: Brice Goglin [EMAIL PROTECTED] Date: Sun Sep 23 18:25:55 2007 +0200 Add 45_GetKeyboardEvents_reject_out-of-range_keycodes.diff diff --git a/debian/changelog b/debian/changelog index 625b5db..b4b27f1 100644 --- a/debian/changelog +++ b/debian/changelog @@ -19,6 +19,9 @@ xorg-server (2:1.4-3) UNRELEASED; urgency=low * Add upstream commit 27ad5d74c20f01516a1bff73be283f8982fcf0fe as patch 44_XKB_mapping_changes_for_all_core-sending_devices.diff to fix broken xmodmap invocation in .xsession, closes: #443044. + * Add upstream commit 0e800ca4651a947ccef239e6fe7bf64aab92257c as patch +45_GetKeyboardEvents_reject_out-of-range_keycodes.diff to fix crash +in GetKeyboardValuatorEvents, closes: #443697. [ Christian Perrier ] * Debconf templates and debian/control reviewed by the debian-l10n- @@ -45,7 +48,7 @@ xorg-server (2:1.4-3) UNRELEASED; urgency=low debian/patches/series. * Don't build kdrive-based servers we're not shipping. - -- Brice Goglin [EMAIL PROTECTED] Sun, 23 Sep 2007 17:32:49 +0200 + -- Brice Goglin [EMAIL PROTECTED] Sun, 23 Sep 2007 18:23:39 +0200 xorg-server (2:1.4-2) unstable; urgency=low diff --git a/debian/patches/45_GetKeyboardEvents_reject_out-of-range_keycodes.diff b/debian/patches/45_GetKeyboardEvents_reject_out-of-range_keycodes.diff new file mode 100644 index 000..ac9cd52 --- /dev/null +++ b/debian/patches/45_GetKeyboardEvents_reject_out-of-range_keycodes.diff @@ -0,0 +1,33 @@ +From: Daniel Stone [EMAIL PROTECTED] +Date: Sun, 23 Sep 2007 09:43:31 + (+0300) +Subject: GetKeyboardEvents: Reject out-of-range keycodes (bug #12528) +X-Git-Url: http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commitdiff;h=0e800ca4651a947ccef239e6fe7bf64aab92257c + +GetKeyboardEvents: Reject out-of-range keycodes (bug #12528) + +We can only deal with keycodes between 8 and 255, so make sure that we never +accept anything out of this range. + +http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443697 +--- + +--- a/dix/getevents.c b/dix/getevents.c +@@ -402,6 +402,7 @@ GetKeyboardValuatorEvents(xEvent *events + if (!events) + return 0; + ++/* DO NOT WANT */ + if (type != KeyPress type != KeyRelease) + return 0; + +@@ -409,6 +410,9 @@ GetKeyboardValuatorEvents(xEvent *events + (pDev-coreEvents !inputInfo.keyboard-key)) + return 0; + ++if (key_code 8 || key_code 255) ++return 0; ++ + if (pDev-coreEvents) + numEvents = 2; + else diff --git a/debian/patches/series b/debian/patches/series index 3d6c803..1a9b468 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -11,6 +11,7 @@ 42_fix_RemoveGeneralSocket_crash_from_dbus.diff 43_allow_override_BIOS_EDID_preferred_mode.diff 44_XKB_mapping_changes_for_all_core-sending_devices.diff +45_GetKeyboardEvents_reject_out-of-range_keycodes.diff #47_fbdevhw_magic_numbers.diff #51_xkb-and-loathing.diff 91_ttf2pt1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#429609: root-tail problems with xserver-xorg-core 1.3
On 8/20/07, Brice Goglin [EMAIL PROTECTED] wrote: Leandro Penz wrote: I narrowed it down to the following upgrade: [UPGRADE] xserver-xorg-core 2:1.1.1-21 - 2:1.3.0.0.dfsg-11 After that, root-tail stoped working. That was the only package I upgraded in that session. Then, I downgraded it again: [DOWNGRADE] xserver-xorg-core 2:1.3.0.0.dfsg-11 - 2:1.1.1-21 And root-tail worked again. I tried the free nv driver, both the stable (1.2.0-3) and testing version (1:2.1.2) with xserver-xorg-core 2:1.3.0 and got the same results. Are you sure you removed all the nvidia stuff when trying with the free nv driver? I never tried nvidia-glx myself, but there might be some nvidia specific libs that divert the regular Xorg libs. I don't know if they could cause problems when still installed while using the free nv driver. Anyway, I still can't reproduce it here, on both ati and intel free drivers, so the problem still looks kind of driver-specific to me. The nvidia binary driver had a couple known minor incompatibilities with Xserver 1.3... Brice It is now working for me, with the following packages installed: [UPGRADE] nvidia-glx 100.14.11-1 - 100.14.19-1 [UPGRADE] xserver-xorg 1:7.2-5 - 1:7.3+1 [UPGRADE] xserver-xorg-core 2:1.3.0.0.dfsg-12 - 2:1.4-1 I installed the drivers on 2.6.22-2 from the following package: [UPGRADE] nvidia-kernel-source 100.14.11-1 - 100.14.19-1 Cheers! Leandro Penz
Bug#443697: additional information
I forgot to mention that i use a kbd/mouse set that shares a single receiver usb-port. multimedia-keys (175 is one of them) are handled via the mouse-device, so the corresponding driver is evdev, not kbd. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#429609: marked as done (Not working on latest lenny X)
Your message dated Sun, 23 Sep 2007 18:51:36 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#429609: root-tail problems with xserver-xorg-core 1.3 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: root-tail Version: 1.2-2 Severity: grave --- Please enter the report below this line. --- Background stays black even with process running after the upgrade: [UPGRADE] x11-common 1:7.1.0-18 - 1:7.2-3 [UPGRADE] xfonts-encodings 1:1.0.0-6 - 1:1.0.2-1 [UPGRADE] xorg 1:7.1.0-18 - 1:7.2-3 [UPGRADE] xserver-xorg 1:7.1.0-18 - 1:7.2-3 [UPGRADE] xserver-xorg-core 2:1.1.1-21 - 2:1.3.0.0.dfsg-6 [UPGRADE] xserver-xorg-input-evdev 1:1.1.2-6 - 1:1.1.5-2 (and others) --- System information. --- Architecture: i386 Kernel: Linux 2.6.18-4-686 Debian Release: lenny/sid 900 testing www.debian-multimedia.org 900 testing security.debian.org 900 testing ftp.us.debian.org 900 testing ftp.debian-unofficial.org 600 stable www.debian-multimedia.org 600 stable volatile.debian.org 600 stable security.debian.org 600 stable ftp.us.debian.org 600 stable ftp.debian-unofficial.org 200 unstablewww.debian-multimedia.org 200 unstableuqm.debian.net 200 unstableftp.us.debian.org 200 unstableftp.debian-unofficial.org 100 experimentalwww.debian-multimedia.org 100 experimentalftp.us.debian.org --- Package information. --- Depends (Version) | Installed =-+-= libc6(= 2.3.5-1) | 2.5-9+b1 libx11-6 | 2:1.0.3-7 ---End Message--- ---BeginMessage--- reassign 429609 xserver-xorg-core found 429609 2:1.3.0.0.dfsg-12 fixed 429609 2:1.4-1 thank you Leandro Penz wrote: It is now working for me, with the following packages installed: [UPGRADE] nvidia-glx 100.14.11-1 - 100.14.19-1 [UPGRADE] xserver-xorg 1:7.2-5 - 1:7.3+1 [UPGRADE] xserver-xorg-core 2:1.3.0.0.dfsg-12 - 2:1.4-1 I installed the drivers on 2.6.22-2 from the following package: [UPGRADE] nvidia-kernel-source 100.14.11-1 - 100.14.19-1 Ok closing, thanks for the feedback. Still no idea which package was causing the problem? I would vote for xserver-xorg-core since 2 drivers had the problem. Brice ---End Message---
Processed: Re: Bug#429609: root-tail problems with xserver-xorg-core 1.3
Processing commands for [EMAIL PROTECTED]: reassign 429609 xserver-xorg-core Bug#429609: Not working on latest lenny X Bug reassigned from package `xserver-xorg-video-nv' to `xserver-xorg-core'. found 429609 2:1.3.0.0.dfsg-12 Bug#429609: Not working on latest lenny X Bug marked as found in version 2:1.3.0.0.dfsg-12. fixed 429609 2:1.4-1 Bug#429609: Not working on latest lenny X Bug marked as fixed in version 2:1.4-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#443726: xserver-xorg-input-evtouch: input coordinates not scaled
Package: xserver-xorg-input-evtouch Version: 0.8.7-2 Severity: grave Justification: renders package unusable the driver's conversion_proc is not called in xorg-1.4 xf86PortMotionEvent making the driver fail to scale the input coordinates to the screen size. The net result is the pointer not responding correctly to taps. I'm already working on a fix, but this is to avoid that the package enters lenny if I fail to fix it in a timely fashion. mattia -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (300, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.23-rc1-mm1-1 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_GB, LC_CTYPE=ja_JP (charmap=EUC-JP) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443377: xserver-xorg-video-ati: xrandr 1.2 gives wierd coloration on VGA display
On Sun, 23 Sep 2007 12:55:39 +0200 Brice Goglin [EMAIL PROTECTED] wrote: Ken Bloom wrote: It just occurred to me to mention that the projector in question is a rather complicated setup, because it's part of a multimedia classroom setup at IIT that is used to tape lectures and transmit them to remote viewing sites, and to post the lectures on the internet. I observed the same 1024x768 behavior on one of those setups with xrandr 1.1, X.org 7.2 and the fglrx driver about 2 weeks ago, so you can probably ignore the 1024x768 behavior, at least for now. It also wasn't reproducible on a more normal LCD setup. Ok, thanks for the clarification. The 1280x1024 behavior, which is reproducible on other monitors is still relevant. Could you latest upstream git snapshot in case it helps? If not, we might have to open an upstream bug at bugzilla.freedesktop.org. Brice With a git snapshot checked out just a few minutes ago, constructed by $ git-clone $UPSTREAM_REPOSITORY ati-git-snapshot $ cd ati-git-snapshot $ git-pull $DEBIAN_REPOSITORY debian-experimental (if I did this wrong, let me know -- I've never used git before) I observe on my LCD monitor (on VGA-0) that if I change the VGA-0 resolution directly to 1280x1024, there is no longer a redraw bug, but if I change the resolution to 1680x1050, then 1280x1024 the redraw bug appears in 1280x1024 (but not 1680x1050). So they're getting there. --Ken -- Ken Bloom. PhD candidate. Linguistic Cognition Laboratory. Department of Computer Science. Illinois Institute of Technology. http://www.iit.edu/~kbloom1/ signature.asc Description: PGP signature
Bug#409612: xlibs-data: Modifier mappings broken
(Quoting full post, because Cc:ing to the Ion list.) On 2007-09-23 03:01 +0200, Mohammed Adnène Trojette wrote: tag 409612 moreinfo thanks On Sun, Feb 04, 2007, tuomov wrote: The modifier mappings in stock keyboard layouts are broken. For details, I'll just attach the Ion FAQ entry below from http://iki.fi/tuomov/ion/faq/entries/Modifier_releases.html. (I have not myself experienced that problem, though -- I don't use Xkb crud at all, because customisation of Xkb based layouts is too laboursome, difficult, undocumented etc. -- but users have experienced it on various systems, and this seems the easiest channel to report the problem.) --- _Ion doesn't notice that a modifier has been released (in actions that use like `kpress_wait`, such as META+C, or in “grabmenus”)._ This is most likely to be an X bug/keyboard misconfiguration, when you have changed the “META” key of Ion to Mod4, or something else that supposed has one of the Win-keys bound to it. For some reason, some Xorg comes with some totally broken stock keyboard layouts that define multiple keycodes for the `Super_L` and such “keysyms”, one of them spurious. However, various part of X or Xlib can not handle that, and report the wrong keycode when queried.sup1/sup To check if this is the case, first run `xmodmap` to check what key is bound to the Mod4 (or perhaps Mod3 depending on the configuration) modifier. You may see a line like this: mod4Super_L (0x7f), Hyper_L (0x80) The number 0x7f=127 is the keycode, and this is highly likely the wrong keycode. Check with `xmodmap -pke|grep Super_L` to see what keycodes have `Super_L` bound to them. If you see something like this, your keymap is misconfigured: keycode 115 = Super_L keycode 127 = NoSymbol Super_L The keycode 115 is the keycode for the real left Win key, and 127 is spurious. However, the modifier subsystem only seems to see the latter. Putting the following commands in `~/.Xmodmap` and runnning `xmodmap ~/.Xmodmap` should fix the issue. You may also want/need to repeat for the other Win keys (`Hyper_L` and 0x80=127 in our example case). remove mod4 = Super_L keycode 127 = NoSymbol add mod4 = Super_L (The `remove` command is needed for some reason to not confuse X.) Unless your system configuration is totally weird (and I wouldn't put it past systems built to run Gnome), next time you start X, `~/.Xmodmap` should be loaded automatically. On a working modifier configuration running `xmodmap` should display a line like below (0x73 following `Super_L` being the important part). mod4Super_L (0x73) --- Hello, does this bug apply to Debian's Xorg? Is it still a problem with the recent Xorg versions in Debian? What is the output of the following command? % xprop -root | grep XKB (I don't use ion myself.) -- Mohammed Adnène Trojette Does recent mean something later than etch? In that case I can't help now, and unlikely in the future either (because the present 2.6.14 kernel and etch setup is likely to be my last Linux setup ever unless something marvellous happens, which seems unlikely). In any case, the output from that command is _XKB_RULES_NAMES(STRING) = xfree86, logicdp, fi, nodeadkeys, ctrl:nocaps But, as mentioned above, I don't actually use Xkb crud at all myself (thanks to the use of ISO_Level3_Shift instead of Mode_Switch, only the latter of which can be customised easily with xmodmap, Xkb configuration itself being cryptic and ultra-complex like almost anything recent in *nix). Maybe some people on the Ion list can be of more help; I just reported this bug because nobody else seemed to be arsed to. -- Tuomo
Bug#409612: xlibs-data: Modifier mappings broken
On Sun, Sep 23, 2007, Tuomo Valkonen wrote:
Does recent mean something later than etch? In that case I can't
help now, and unlikely in the future either (because the present
2.6.14 kernel and etch setup is likely to be my last Linux setup
ever unless something marvellous happens, which seems unlikely).
In any case, the output from that command is
_XKB_RULES_NAMES(STRING) = xfree86, logicdp, fi, nodeadkeys,
ctrl:nocaps
But, as mentioned above, I don't actually use Xkb crud at all myself
(thanks to the use of ISO_Level3_Shift instead of Mode_Switch, only
the latter of which can be customised easily with xmodmap, Xkb
configuration itself being cryptic and ultra-complex like almost
anything recent in *nix).
Maybe some people on the Ion list can be of more help; I just reported
this bug because nobody else seemed to be arsed to.
I forwarded your bug upstream. And upstream is asking to try commenting
the lines
key SUPR {[ NoSymbol, Super_L ] };
modifier_map Mod4 { SUPR };
in symbols/pc
(please see http://bugs.freedesktop.org/show_bug.cgi?id=12526)
--
Mohammed Adnène Trojette
Bug#443584: xrandr does not recognise conncted s-video
Brice Goglin wrote: Nadav Kavalerchik wrote: |xrandr --addmode S-video 800x600| |xrandr --output S-video --mode 800x600| works great :-) and stays this way too. no after effects when i use the mouse or the keyboard. Good to know. I'll keep the bug open until I get some clarification from Alex about how we are supposed to enabled TV-out these days. The other way is: xrandr --output S-video --set load_detection 1 which enables load detection back as earlier and then xrandr --auto (or maybe grandr) Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443537: xbase-clients: xrdb: an apostrophe in a comment causes error
Ryo Furue wrote: Package: xbase-clients Version: 1:7.2.ds2-2 Severity: normal If a comment in .Xdefaults contains an apostrophe, xrdb issues an error. For example, $ cat tmp.txt ! This is a comment line. Let's ignore it. $ xrdb tmp.txt stdin:1:31: warning: missing terminating ' character $ (I first recognized this problem with a real .Xdefault file, and I created this stupid example for this bug submission.) Can you provide a patch to fix it? It shouldn't be hard to do, and fixing this problem isn't high priority for us unfortunately :/ Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439254: xserver-xorg-video-ati: Does not enable default resolution
Brice Goglin schrieb: On Thu, Aug 23, 2007 at 06:30:55PM +0200, Michael Biebl wrote: upgraded to the latest radeon driver from exp which is said to support tv-out (which I haven't tested yet). I built the driver against the xorg-server from unstable myself, as I didn't want to upgrade all the other components. My panel size (laptop) is 1680x1050. xrandr shows: Screen 0: minimum 320 x 200, current 1280 x 768, maximum 1600 x 1200 VGA-0 disconnected (normal left inverted right) LVDS connected 1280x768+0+0 (normal left inverted right) 0mm x 0mm 1680x1050 60.7 + 1280x800 60.0 1280x768 60.0* 1024x768 60.0 800x60060.3 640x48059.9 S-video disconnected (normal left inverted right) So 1280x768 is chosen by the xserver, although 1680x1050 is my default. The Xorg.0.log says something about the width of my virtual size being to wide. I don't exactly know, what that means and how I can fix that. I can switch to my preferred solution via xrandr -s 1680x1050, but that doesn't work e.g. for gdm. Maybe you can help me, and tell me if I misconfigured something. Anything new about this bug with latest 1:6.7.193-1 in experimental or upstream git ? Yeah, my main display now uses the correct default resolution. I still need the Virtual Option though, when I use a second monitor. That's a different issue I guess, so imho this bug report can be closed. Rock on, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#443292: Workaround for the bug
On Sat, 22 Sep 2007 the mental interface of
Elimar Riesebieter told:
On Fri, 21 Sep 2007 the mental interface of
Dario Gallucci told:
I had the same problem.
The mouse is working again whit evdev using
Option Device and the specific event identifier given to the mouse by
udev
in /dev/input/by-path/...
I hope this can solve temporary this problem.
Thanks a lot for pointing out.
I created a udev rule:
KERNEL==event*, SYSFS{idVendor}==046d, SYSFS{idProduct}==c50e
NAME=input/event-mx1000, SYMLINK=input/%k
and added:
Option Device /dev/input/event-mx1000
to the InputDevice Section.
This works ;)
Hmm, playing ut or quake3 makes the mouse really nervous and
unusable. So I switched back to 1:1.1.5-3.
Elimar
--
Learned men are the cisterns of knowledge,
not the fountainheads ;-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443761: xserver-xorg-video-intel: debian crash or graphical problems using intel X3000 chipset
Package: xserver-xorg-video-intel Version: 2:2.1.1-4 Severity: critical Justification: breaks the whole system hello! ok, first: my english is very bad. second: i'm a debian/linux newbie i have installed debian unstable + kde on a new system mainboard: asus P5B-VM SE with intel X3000 graphic chipset if I 1. start glxgears 2. move it down to a panel (!with animated tooltips!) 3. and move mouse over a task-caption first glxgears shows funny stuff after this, when i try to resize glxgears, the whole system crash reset is the only way. -- Package-specific info: 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 2007-09-22 04:16 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1669528 2007-09-16 20:56 /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 82G965 Integrated Graphics Controller (rev 02) /etc/X11/xorg.conf unchanged from checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1694 2007-09-23 22:07 /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 command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout de Option XkbVariantnodeadkeys EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol ImPS/2 EndSection Section Device Identifier Intel Corporation 82G965 Integrated Graphics Controller Driver intel BusID PCI:0:2:0 EndSection Section Monitor Identifier COMPAQ S710 Option DPMS HorizSync 30-70 VertRefresh 50-160 EndSection Section Screen Identifier Default Screen Device Intel Corporation 82G965 Integrated Graphics Controller Monitor COMPAQ S710 DefaultDepth24 SubSection Display Modes 1280x1024 1152x864 1024x768 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 34515 2007-09-23 22:13 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4-2) Current Operating System: Linux debian 2.6.22-2-686-bigmem #1 SMP Fri Aug 31 01:40:59 UTC 2007 i686 Build Date: 16 September 2007 02:37:21PM 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 Sep 23 22:13:17 2007 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor COMPAQ S710 (**) | |--Device Intel Corporation 82G965 Integrated Graphics Controller (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/100dpi does not exist. Entry deleted from font path. (WW) The directory
Processed: severity of 443761 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.8 severity 443761 important Bug#443761: xserver-xorg-video-intel: debian crash or graphical problems using intel X3000 chipset Severity set to `important' from `critical' 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#442907: xserver-xorg-video-mga: Multihead doesn't work on G450
kls wrote: With the update to libpixman, I can now run 1.9.99. It mostly works, except 2d performance is abysmal -- full-screen windows (1152x900 for me) take about a second to redraw. (however, 3d performance is as good, or maybe slightly better, than it ever was) Ok, thanks for the report. Should I mark your bug as fixed in 1.9.99 and let you open a new bug report about 2D being very slow in 1.9.99 (or in 2.0 when it is released)? Sounds reasonable. In any case, 1.4.7 is sufficiently broken (since dual-heading doesn't work at all) that I'd like to recommend that it not be allowed to propagate. You mean 1.4.7 is more broken than 1.4.6, right? In my opinion. Of course, looking at the bug report listing, 1.4.7 fixed bug #430112, so you win some, lose some. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443491: xserver-xorg-video-ati: Still present with 1:6.7.193-1
Package: xserver-xorg-video-ati Version: 1:6.7.193-1 Followup-For: Bug #443491 The display corruption at non-native panel resolutions still occurs with 1:6.7.193-1. - Josh Triplett -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2006-04-16 01:03 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1669528 2007-09-16 11:56 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] /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 3621 2007-08-12 22:43 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # /etc/X11/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 /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files FontPath/usr/share/fonts/X11/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/share/fonts/X11/100dpi FontPath/usr/share/fonts/X11/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 EndSection #Section InputDevice # Identifier Synaptics Touchpad # Driver synaptics # Option SendCoreEventstrue # Option Device/dev/psaux # Option Protocol auto-dev # Option HorizScrollDelta 0 #EndSection Section Device Identifier ATI Technologies, Inc. Radeon Mobility M7 LW [Radeon Mobility 7500] Driver radeon Option DynamicClocks on # Option AccelMethod EXA Option AGPMode 4 # Option MergedFB on # Option CRT2Position RightOf # Option MetaModes 1400x1050-1680x1050 1400x1050+1680x1050 1400x1050 1024x768 800x600 640x480 # Option MergedXineramaCRT2IsScreen0 yes EndSection Section Monitor Identifier IBM ThinkPad LCD 1400x1050 Option DPMS DisplaySize 286 215 EndSection Section Screen Identifier Default Screen Device ATI Technologies, Inc. Radeon Mobility M7 LW [Radeon Mobility 7500] DefaultDepth24 # SubSection Display # Depth 24 # Virtual 3080 1050 # Modes 1680x1050 1400x1050 1024x768 800x600 640x480 # EndSubSection Monitor IBM ThinkPad LCD 1400x1050 SubSection Display Depth 1 Modes 1400x1050 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1400x1050 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1400x1050 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1400x1050 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1400x1050 1024x768
Re: binNMUs for X video drivers
On Fri, Sep 21, 2007 at 03:41:29PM +0200, Julien Cristau wrote: it'd be nice if the following binNMUs could be scheduled to pick up the new X video driver ABI (I'll do source uploads otherwise, but.). xserver-xorg-video-sunbw2_1:1.1.0-2, rebuild against xserver 1.4, 1, sparc xserver-xorg-video-suncg14_1:1.1.0-2, rebuild against xserver 1.4, 1, sparc xserver-xorg-video-suncg3_1:1.1.0-2, rebuild against xserver 1.4, 1, sparc xserver-xorg-video-suncg6_1:1.1.0-4, rebuild against xserver 1.4, 1, sparc xserver-xorg-video-sunffb_1:1.1.0-2, rebuild against xserver 1.4, 1, sparc xserver-xorg-video-sunleo_1:1.1.0-2, rebuild against xserver 1.4, 1, sparc xserver-xorg-video-suntcx_1:1.1.0-2, rebuild against xserver 1.4, 1, sparc Scheduled. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
