Bug#1076172: pixman: FTBFS on armhf: Error: garbage following instruction -- `bne 01f'

[Mike Hommey]

Source: pixman
Version: 0.42.2-1
Severity: serious

Dear Maintainer,

The package fails to build on armhf on current sid/testing with:

../../pixman/pixman-arm-simd-asm.h:821: Error: garbage following instruction -- 
`bne 01f'
../../pixman/pixman-arm-simd-asm.h:869:  Info: macro invoked from here
../../pixman/pixman-arm-simd-asm.h:326:   Info: macro invoked from here
../../pixman/pixman-arm-simd-asm.h:343:Info: macro invoked from here
../../pixman/pixman-arm-simd-asm.h:354: Info: macro invoked from here
../../pixman/pixman-arm-simd-asm.h:408:  Info: macro invoked from here
../../pixman/pixman-arm-simd-asm.h:793:   Info: macro invoked from here
../../pixman/pixman-arm-simd-asm.S:875:Info: macro invoked from here
../../pixman/pixman-arm-simd-asm.h:822: Error: garbage following instruction -- 
`bcc 03f'
../../pixman/pixman-arm-simd-asm.h:869:  Info: macro invoked from here
../../pixman/pixman-arm-simd-asm.h:326:   Info: macro invoked from here
../../pixman/pixman-arm-simd-asm.h:343:Info: macro invoked from here
../../pixman/pixman-arm-simd-asm.h:354: Info: macro invoked from here
../../pixman/pixman-arm-simd-asm.h:408:  Info: macro invoked from here
../../pixman/pixman-arm-simd-asm.h:793:   Info: macro invoked from here
../../pixman/pixman-arm-simd-asm.S:875:Info: macro invoked from here

See https://gitlab.freedesktop.org/pixman/pixman/-/issues/96 and bug
1073870.

Mike

Bug#901883: xwayland: Firefox causes Xwayland to freeze and eat 100% CPU

[Mike Hommey]

On Wed, Jun 20, 2018 at 05:44:22PM +0900, Mike Hommey wrote:
> Package: xwayland
> Version: 2:1.20.0-2
> Followup-For: Bug #901883
> 
> Dear Maintainer,
> 
> I am able to reproduce this reliably with Firefox from experimental by
> going to 
> http://example.qt.io/qt-webassembly/widgets/richtext/textedit/textedit.html
> 
> Attaching gdb to Xwayland shows the same information as mentioned in
> https://bugs.archlinux.org/task/58705#comment169691, that is, that
> WriteToClient receives a negative count.

Submitted 
https://salsa.debian.org/xorg-team/xserver/xorg-server/merge_requests/2

Mike

Bug#901883: xwayland: Firefox causes Xwayland to freeze and eat 100% CPU

[Mike Hommey]

Package: xwayland
Version: 2:1.20.0-2
Followup-For: Bug #901883

Dear Maintainer,

I am able to reproduce this reliably with Firefox from experimental by
going to 
http://example.qt.io/qt-webassembly/widgets/richtext/textedit/textedit.html

Attaching gdb to Xwayland shows the same information as mentioned in
https://bugs.archlinux.org/task/58705#comment169691, that is, that
WriteToClient receives a negative count.

Mike


-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), 
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xwayland depends on:
ii  libaudit1   1:2.8.3-1
ii  libbsd0 0.9.1-1
ii  libc6   2.27-3
ii  libdrm2 2.4.92-1
ii  libegl1 1.0.0+git20180308-3
ii  libepoxy0   1.4.3-1
ii  libgbm1 18.1.2-1
ii  libgcrypt20 1.8.3-1
ii  libgl1  1.0.0+git20180308-3
ii  libpixman-1-0   0.34.0-2
ii  libselinux1 2.8-1
ii  libsystemd0 238-5
ii  libwayland-client0  1.15.0-2
ii  libxau6 1:1.0.8-1+b2
ii  libxdmcp6   1:1.1.2-3
ii  libxfont2   1:2.0.3-1
ii  libxshmfence1   1.3-1
ii  xserver-common  2:1.20.0-2

xwayland recommends no packages.

xwayland suggests no packages.

-- no debconf information

Re: Backports of pixman and cairo

[Mike Hommey]

On Mon, Aug 15, 2011 at 12:33:17PM +0200, Cyril Brulebois wrote:
> Mike Hommey  (15/08/2011):
> > Do you mind if I upload backports of pixman and cairo to
> > squeeze-backports?
> 
> Not at all. Feel free to push pixman's packaging in a branch
> (debian-squeeze-backports) in our git repository. I can also
> take care of the git part if you like, just reply with a diff,
> and I'll push that, and tag appropriately.

All the required bits are in bug 632943, and don't need to live
in a separate branch. ;)

Mike


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110815110326.ga16...@glandium.org

Backports of pixman and cairo

[Mike Hommey]

Hi,

Do you mind if I upload backports of pixman and cairo to
squeeze-backports?

Cheers,

Mike


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110815070936.gc4...@glandium.org

Bug#632943: pixman: Please allow easier backports

[Mike Hommey]

Package: pixman
Version: 0.22.0-1
Severity: wishlist

Since the switch to multi-arch, the pixman package doesn't build out of the
box in a squeeze-backports environment.

The attached patch allows that.

Mike

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u pixman-0.22.0/debian/rules pixman-0.22.0/debian/rules
--- pixman-0.22.0/debian/rules
+++ pixman-0.22.0/debian/rules
@@ -5,6 +5,16 @@
 
 DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
 
+PREPROCESS_FILES := $(wildcard debian/*.in)
+
+$(PREPROCESS_FILES:.in=): %: %.in
+	sed 's,@DEB_HOST_MULTIARCH@/,$(DEB_HOST_MULTIARCH:=/),g' $< > $@
+
+ifneq (,$(DEB_HOST_MULTIARCH))
+override_dh_gencontrol:
+	dh_gencontrol -- -Vmisc:Multi-Arch=same
+endif
+
 # Disable Gtk+ autodetection:
 override_dh_auto_configure:
 	dh_auto_configure -- --disable-gtk \
@@ -15,7 +25,7 @@
 	dh_auto_install --destdir=debian/tmp
 
 # Kill *.la files, and forget no-one:
-override_dh_install:
+override_dh_install: $(PREPROCESS_FILES:.in=)
 	find debian/tmp -name '*.la' -delete
 	dh_install --fail-missing
 
diff -u pixman-0.22.0/debian/control pixman-0.22.0/debian/control
--- pixman-0.22.0/debian/control
+++ pixman-0.22.0/debian/control
@@ -19,7 +19,7 @@
  ${shlibs:Depends},
  ${misc:Depends},
 Pre-Depends: ${misc:Pre-Depends}
-Multi-Arch: same
+Multi-Arch: ${misc:Multi-Arch}
 Description: pixel-manipulation library for X and cairo
  A library for manipulating pixel regions -- a set of Y-X banded
  rectangles, image compositing using the Porter/Duff model
@@ -44,7 +44,7 @@
 Depends:
  libpixman-1-0 (= ${binary:Version}),
  ${misc:Depends},
-Multi-Arch: same
+Multi-Arch: ${misc:Multi-Arch}
 Description: pixel-manipulation library for X and cairo (debugging symbols)
  Debugging symbols for the Cairo/X pixel manipulation library.  This is
  needed to debug programs linked against libpixman0.
reverted:
--- pixman-0.22.0/debian/libpixman-1-0-udeb.install
+++ pixman-0.22.0.orig/debian/libpixman-1-0-udeb.install
@@ -1 +0,0 @@
-usr/lib/*/libpixman-1.so.* /usr/lib
reverted:
--- pixman-0.22.0/debian/libpixman-1-dev.install
+++ pixman-0.22.0.orig/debian/libpixman-1-dev.install
@@ -1,4 +0,0 @@
-usr/lib/*/libpixman-1.so
-usr/lib/*/libpixman-1.a
-usr/lib/*/pkgconfig
-usr/include/pixman-1
reverted:
--- pixman-0.22.0/debian/libpixman-1-0.install
+++ pixman-0.22.0.orig/debian/libpixman-1-0.install
@@ -1 +0,0 @@
-usr/lib/*/libpixman-1.so.*
diff -u pixman-0.22.0/debian/changelog pixman-0.22.0/debian/changelog
--- pixman-0.22.0/debian/changelog
+++ pixman-0.22.0/debian/changelog
@@ -1,3 +1,10 @@
+pixman (0.22.0-1.1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * debian/rules, debian/control, debian/*.install: Allow easy backport.
+
+ -- Mike Hommey   Thu, 07 Jul 2011 10:35:46 +0200
+
 pixman (0.22.0-1) unstable; urgency=low
 
   * Team upload.
only in patch2:
unchanged:
--- pixman-0.22.0.orig/debian/libpixman-1-dev.install.in
+++ pixman-0.22.0/debian/libpixman-1-dev.install.in
@@ -0,0 +1,4 @@
+usr/lib/@DEB_HOST_MULTIARCH@/libpixman-1.so
+usr/lib/@DEB_HOST_MULTIARCH@/libpixman-1.a
+usr/lib/@DEB_HOST_MULTIARCH@/pkgconfig
+usr/include/pixman-1
only in patch2:
unchanged:
--- pixman-0.22.0.orig/debian/libpixman-1-0-udeb.install.in
+++ pixman-0.22.0/debian/libpixman-1-0-udeb.install.in
@@ -0,0 +1 @@
+usr/lib/@DEB_HOST_MULTIARCH@/libpixman-1.so.* /usr/lib
only in patch2:
unchanged:
--- pixman-0.22.0.orig/debian/libpixman-1-0.install.in
+++ pixman-0.22.0/debian/libpixman-1-0.install.in
@@ -0,0 +1 @@
+usr/lib/@DEB_HOST_MULTIARCH@/libpixman-1.so.*

Bug#575376: xvfb: Renders garbage in some cases on s390

[Mike Hommey]

On Sun, Jan 30, 2011 at 06:10:36AM +0100, Cyril Brulebois wrote:
> Hi Mike,
> 
> Mike Hommey  (25/03/2010):
> > Package: xvfb
> > Version: 2:1.7.5.902-1
> > Severity: normal
> > 
> > xulrunner reftests ended with 62 failures on s390, which are to be
> > attributed to xvfb rendering garbage in some cases.
> 
> an update with the X stack from squeeze/sid or from experimental would
> be appreciated. I should be able to try and reproduce this, but there
> are plenty of other bug reports to walk through…

It still happens on unstable, according to the iceweasel build log. I'll
try on experimental later.

Mike



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110130084410.ga3...@glandium.org

Bug#591106: Followup on Bug 591106

[Mike Hommey]

On Sun, Aug 01, 2010 at 09:52:46PM -0700, John Aston  wrote:
> I defer to the expert's judgment on where the bug belongs, but I will note 
> that I've only experienced the bug with Iceweasel, and no other programs.  
> I've taken the same image (locally saved) and opened it using various viewers 
> and image editors, and encountered no difficulties when moving the pointer to 
> the other screen.  I've also done plenty of other tasks where one GUI-based 
> program was actively "doing" something on one screen and I've moved the 
> pointer to the other.  No problems there either.
> 
> Also, I just encountered the bug again without a large image.  I went to the 
> main yahoo page (to check for responses to this bug, ironically enough) and 
> once again moved my mouse pointer onto the other screen while the entire page 
> was rendering -- freeze, same as before.
> 
> Without being an expert on the matter, I'd probably place more of the bug on 
> Iceweasel's side, since I can't duplicate it using any other program.

The fact it happens only with iceweasel may simply mean it triggers a bug
with some extension that the other applications you tested don't use.
(Xrender, maybe ?)
Anyways, an application shouldn't be able to freeze X.

Mike



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100802071848.gb21...@glandium.org

Re: Bug#451791: closed by Julien Cristau <[EMAIL PROTECTED]> (Bug#451791: fixed in xserver-xorg-video-intel 2:2.3.2-2+lenny3)

[Mike Hommey]

On Thu, Aug 28, 2008 at 07:25:19PM +0200, Julien Cristau wrote:
> On Thu, Aug 28, 2008 at 19:21:06 +0200, Mike Hommey wrote:
> 
> > On the other hand, switching to XAA made Xv stop working here. I hope
> > I'm alone in that case.
> > 
> > FWIW, xvinfo returns 2 adapters, the first being "Intel(R) Textured
> > Video", and the second "Intel(R) Video Overlay".
> > 
> Argh, right, Xv on XAA is fail.  None of the adapters work?
 

]  * Kill 02_xaa_by_default_on_i965.diff.  Switching to XAA breaks Xvideo,
]which is Not Good™.
]  * New patch 02_965_no_exa_composite.diff: add a "RenderAccel" option, to
]control whether EXA composite acceleration is enabled.  Default to off on
]i965+ to hopefully avoid the font rendering issues reported in #451791 and
]friends.

Now, the problem is that with RenderAccel false, there are strange corruptions
on some image backgrounds in epiphany (and, though not tried, iceweasel, I 
guess)

:-(

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#451791: closed by Julien Cristau <[EMAIL PROTECTED]> (Bug#451791: fixed in xserver-xorg-video-intel 2:2.3.2-2+lenny3)

[Mike Hommey]

On Thu, Aug 28, 2008 at 09:16:15PM +0200, Brice Goglin wrote:
> Mike Hommey wrote:
> >> Argh, right, Xv on XAA is fail.  None of the adapters work?
> >> 
> >
> > I'd try them all if i knew how to...
> >   
> 
> xvinfo gives you the port base and number of ports for each adapter.
> Then you can try something like mplayer -vo xv port=65 to use port #65.

I tried with vlc (which i have installed, contrary to mplayer), and
while I get a BadAlloc with adapter #0, I don't with adapter #1, but i
don't get any image with #1, so all in all, it doesn't work :(

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#451791: closed by Julien Cristau <[EMAIL PROTECTED]> (Bug#451791: fixed in xserver-xorg-video-intel 2:2.3.2-2+lenny3)

[Mike Hommey]

On Thu, Aug 28, 2008 at 07:25:19PM +0200, Julien Cristau wrote:
> On Thu, Aug 28, 2008 at 19:21:06 +0200, Mike Hommey wrote:
> 
> > On the other hand, switching to XAA made Xv stop working here. I hope
> > I'm alone in that case.
> > 
> > FWIW, xvinfo returns 2 adapters, the first being "Intel(R) Textured
> > Video", and the second "Intel(R) Video Overlay".
> > 
> Argh, right, Xv on XAA is fail.  None of the adapters work?

I'd try them all if i knew how to...

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#451791: closed by Julien Cristau <[EMAIL PROTECTED]> (Bug#451791: fixed in xserver-xorg-video-intel 2:2.3.2-2+lenny3)

[Mike Hommey]

On Wed, Aug 27, 2008 at 07:38:38PM +0200, Julien Cristau wrote:
> On Wed, Aug 27, 2008 at 19:25:17 +0200, Mike Hommey wrote:
> 
> > >[ Brice Goglin ]
> > >* Add 02_xaa_by_default_on_i965.diff to switch back to XAA on
> > >  i965 by default to avoid many rendering problems, closes: #451791.
> > 
> > Interestingly, I've never been hit by these rendering problems with EXA,
> > but I don't exactly have a 965G, but a 965GM. But the switch back to XAA
> > seems to apply to any 965...
> > 
> The rendering problems with EXA were reported by people with pretty much
> every 965 variant, and we have no "known good" version.  Upstream was
> never able to reproduce, so at this point this (or forcing
> ExaNoComposite by default) was the only option left.

On the other hand, switching to XAA made Xv stop working here. I hope
I'm alone in that case.

FWIW, xvinfo returns 2 adapters, the first being "Intel(R) Textured
Video", and the second "Intel(R) Video Overlay".

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#451791: closed by Julien Cristau <[EMAIL PROTECTED]> (Bug#451791: fixed in xserver-xorg-video-intel 2:2.3.2-2+lenny3)

[Mike Hommey]

>[ Brice Goglin ]
>* Add 02_xaa_by_default_on_i965.diff to switch back to XAA on
>  i965 by default to avoid many rendering problems, closes: #451791.

Interestingly, I've never been hit by these rendering problems with EXA,
but I don't exactly have a 965G, but a 965GM. But the switch back to XAA
seems to apply to any 965...

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#485939: epiphany-browser: shows corrupted homepage of my bank

[Mike Hommey]

On Thu, Jun 12, 2008 at 02:53:36PM +0200, Josselin Mouette <[EMAIL PROTECTED]> 
wrote:
> reassign 485939 xserver-xorg-core
> thanks
> 
> Le jeudi 12 juin 2008 à 14:08 +0200, Fabian Greffrath a écrit :
> > Package: epiphany-browser
> > Version: 2.22.2-2
> > Severity: normal
> > 
> > Dear Epiphany-maintainers,
> > 
> > both epiphany-webkit and epiphany-gecko display the homepage for my 
> > bank in a corrupted manner. Please check: 
> > .
> > 
> > I don't know if the page uses corrupted java-scripting or similar, 
> > since I am no expert in web design.
> > 
> > However, in the case of epiphany-gecko this is a regression from the
> > good old times [TM] when xulrunner-1.8.x was used. For epiphany-webkit 
> > I cannot tell since I haven't visited this homepage before with this
> > browser.
> 
> This is a known problem with cairo when using the XAA acceleration. You
> can work around it using the EXA acceleration in the X server.

Or disabling XAA offscreen pixmaps.

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482992#30

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#482646: /usr/bin/compiz: Partial upgrades broken ; Should conflict with older version of libcompizconfig0

[Mike Hommey]

On Sat, May 24, 2008 at 10:14:58AM +0200, Mike Hommey wrote:
> Package: compiz-core
> Version: 0.7.4-1
> Severity: important
> File: /usr/bin/compiz
> 
> I unfortunately partially upgraded compiz, and left libcompizconfig0 at
> the previous version:
> ii  libcompizconfig0   0.6.0-3
> 
> This led to this error message (and compiz failure to start):
> /usr/bin/compiz.real (core) - Error: dlsym: /usr/lib/compiz/libccp.so:
> undefined symbol: getCompPluginInfo20070830
> 
> compiz should conflict with incompatible versions of libcompizconfig0 to
> avoid broken partial upgrades.

Same applies with compiz-fusion-plugins-main:
/usr/bin/compiz.real (core) - Error: dlsym:
/usr/lib/compiz/libworkarounds.so: undefined symbol:
getCompPluginInfo20070830

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#482646: /usr/bin/compiz: Partial upgrades broken ; Should conflict with older version of libcompizconfig0

[Mike Hommey]

Package: compiz-core
Version: 0.7.4-1
Severity: important
File: /usr/bin/compiz

I unfortunately partially upgraded compiz, and left libcompizconfig0 at
the previous version:
ii  libcompizconfig0   0.6.0-3

This led to this error message (and compiz failure to start):
/usr/bin/compiz.real (core) - Error: dlsym: /usr/lib/compiz/libccp.so:
undefined symbol: getCompPluginInfo20070830

compiz should conflict with incompatible versions of libcompizconfig0 to
avoid broken partial upgrades.

Cheers

Mike


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages compiz-core depends on:
ii  libc6  2.7-11GNU C Library: Shared libraries
ii  libgl1-mesa-glx [libgl1]   7.0.3-1   A free implementation of the OpenG
ii  libice62:1.0.4-1 X11 Inter-Client Exchange library
ii  libsm6 2:1.0.3-1+b1  X11 Session Management library
ii  libstartup-notification0   0.9-1 library for program launch feedbac
ii  libx11-6   2:1.0.3-7 X11 client-side library
ii  libxcomposite1 1:0.4.0-2 X11 Composite extension library
ii  libxdamage11:1.1.1-4 X11 damaged region extension libra
ii  libxext6   2:1.0.4-1 X11 miscellaneous extension librar
ii  libxfixes3 1:4.0.3-2 X11 miscellaneous 'fixes' extensio
ii  libxinerama1   2:1.0.3-2 X11 Xinerama extension library
ii  libxml22.6.32.dfsg-2 GNOME XML library
ii  libxrandr2 2:1.2.2-2 X11 RandR extension library
ii  libxslt1.1 1.1.23-1  XSLT processing library - runtime 
ii  mesa-utils 7.0.3-1   Miscellaneous Mesa GL utilities

Versions of packages compiz-core recommends:
pn  compiz-plugins (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#474395: iceweasel: some tabs have spurious lines, making display unreadable

[Mike Hommey]

On Mon, Apr 07, 2008 at 10:45:31AM +0200, Evgeni Golov <[EMAIL PROTECTED]> 
wrote:
> On Sat, 05 Apr 2008 17:16:29 +0200 Krzysztof Sobolewski wrote:
> 
> > Mike Hommey pisze:
> > 
> > >> This occurs in xserver-xorg-video-intel from both sid and experimental,  
> > >> but this is the only program that has this problem, and only in 3.0b5.   
> > >> Iceweasel 2 is unaffected by this bug.  Since the only thing that has  
> > >> changed is Iceweasel, I presume that's where the problem is.
> > > 
> > > There is a big difference in rendering between iceweasel 2 and iceweasel
> > > 3, one of which is that it now uses cairo. There are plenty of subtle
> > > ways of triggering video driver bugs, which is why they sometimes only
> > > occur in one application.
> > 
> > If that's helpful in any way, I'd like to mention that I see exactly the
> > same effect with fglrx (non-free cr**, I know).
> 
> And me sees it with xserver-xorg-video-ati (on a Mob Radeon M6 LY). So
> IMHO it's not a driver issue, but firefox^Wiceweasel one.

Then it could also be a cairo issue, or a Xrender issue (or whatever cairo
uses to do rendering). It looks unlikely to be an iceweasel specific issue,
but you can still prove me wrong.

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#473551: libgl1-mesa-dri: Crashes the X server when starting Valve's Portal under Wine on i965

[Mike Hommey]

On Tue, Apr 01, 2008 at 12:18:29AM +0200, Brice Goglin wrote:
> forwarded 473551 https://bugs.freedesktop.org/show_bug.cgi?id=15294
> thank you
> 
> 
> On Mon, Mar 31, 2008 at 11:56:28PM +0200, Mike Hommey wrote:
> > > Here is a stacktrace I was able to get after setting
> > > Option "NoTrapSignals"  "true"
> > > 
> > > (gdb) bt full
> > > #0  0x2ba01ab4b249 in brwProgramStringNotify (ctx=0x10f6590, 
> > > target=, prog=0x130bf80) at brw_program.c:129
> > > No locals.
> > 
> > brw_program.c:129 reads:
> > p->param_state = p->program.Base.Parameters->StateFlags;
> > 
> > where p is 
> > struct brw_vertex_program *p = (struct brw_vertex_program *)prog;
> [...]
> > Which means it's a "standard" null pointer dereference 
> > (program.Base.Parameters is NULL).
> 
> Thanks a lot for debugging this Mike, I have forwarded the bug upstream at 
> the URL
> above. Feel free to add any comments there if you think it could help.

FWIW, I confirm the bug is fixed by upstream commit
7f2c4f96f502e5969fd251ad50a113c3a566686d, which is in 7.0.3 rc3.

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#473551: libgl1-mesa-dri: Crashes the X server when starting Valve's Portal under Wine on i965

[Mike Hommey]

On Mon, Mar 31, 2008 at 11:49:06PM +0200, Mike Hommey wrote:
> On Mon, Mar 31, 2008 at 12:55:52PM +0200, Julien Cristau wrote:
> > On Mon, Mar 31, 2008 at 12:17:20 +0200, Mike Hommey wrote:
> > 
> > > Package: libgl1-mesa-dri
> > > Version: 7.0.3~rc2-1
> > > Severity: important
> > > 
> > > I don't really know if this belongs here, but the stacktrace in the
> > > crashed X server logs seem to indicate that somehow i965_dri.so might be
> > > responsible for this crash.
> > 
> > Does this happen with different versions of the dri driver (it'd be nice
> > to try the different 7.0.x versions at snapshot.debian.net)?
> 
> As said on IRC, it crashes with both 7.0.1~rc2-1 and 7.0.3~rc2-2.
> 
> Here is a stacktrace I was able to get after setting
> Option "NoTrapSignals"  "true"
> 
> (gdb) bt full
> #0  0x2ba01ab4b249 in brwProgramStringNotify (ctx=0x10f6590, 
> target=, prog=0x130bf80) at brw_program.c:129
> No locals.

brw_program.c:129 reads:
p->param_state = p->program.Base.Parameters->StateFlags;

where p is 
struct brw_vertex_program *p = (struct brw_vertex_program *)prog;

FWIW:
(gdb) 
$2 = {program = {Base = {Id = 1, String = 0x0, RefCount = 2, Target = 34336, 
Format = 34933, Resident = 1 '\001', Instructions = 0x0, InputsRead = 0, 
OutputsWritten = 0, 
  TexturesUsed = {0, 0, 0, 0, 0, 0, 0, 0}, Parameters = 0x0, LocalParams = 
{{0, 0, 0, 0} }, Varying = 0x0, Attributes = 0x0, 
NumInstructions = 0, 
  NumTemporaries = 0, NumParameters = 0, NumAttributes = 0, NumAddressRegs 
= 0, NumAluInstructions = 0, NumTexInstructions = 0, NumTexIndirections = 0, 
  NumNativeInstructions = 0, NumNativeTemporaries = 0, NumNativeParameters 
= 0, NumNativeAttributes = 0, NumNativeAddressRegs = 0, 
NumNativeAluInstructions = 0, 
  NumNativeTexInstructions = 0, NumNativeTexIndirections = 0}, IsNVProgram 
= 0 '\0', IsPositionInvariant = 0 '\0', TnlData = 0x0}, id = 5, param_state = 0}

Which means it's a "standard" null pointer dereference (program.Base.Parameters 
is NULL).

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#473551: libgl1-mesa-dri: Crashes the X server when starting Valve's Portal under Wine on i965

[Mike Hommey]

On Mon, Mar 31, 2008 at 12:55:52PM +0200, Julien Cristau wrote:
> On Mon, Mar 31, 2008 at 12:17:20 +0200, Mike Hommey wrote:
> 
> > Package: libgl1-mesa-dri
> > Version: 7.0.3~rc2-1
> > Severity: important
> > 
> > I don't really know if this belongs here, but the stacktrace in the
> > crashed X server logs seem to indicate that somehow i965_dri.so might be
> > responsible for this crash.
> 
> Does this happen with different versions of the dri driver (it'd be nice
> to try the different 7.0.x versions at snapshot.debian.net)?

As said on IRC, it crashes with both 7.0.1~rc2-1 and 7.0.3~rc2-2.

Here is a stacktrace I was able to get after setting
Option "NoTrapSignals"  "true"

(gdb) bt full
#0  0x2ba01ab4b249 in brwProgramStringNotify (ctx=0x10f6590, target=, prog=0x130bf80) at brw_program.c:129
No locals.
#1  0x2ba008e3192c in DoRender (cl=, pc=0xa6c024 "�", 
do_swap=0) at ../../../GL/glx/glxcmds.c:1851
entry = {bytes = 16, varsize = 0x2ba008e4d860 
<__glXProgramStringARBReqSize>}
extra = 0
proc = (__GLXdispatchRenderProcPtr) 0x2ba008e393b0 
<__glXDisp_ProgramStringARB>
err = 0
client = (ClientPtr) 0xb1a910
left = 0
cmdlen = 168
error = 11168
commandsDone = 1
glxc = (__GLXcontext *) 0xc5ba20
sw = 
#2  0x2ba008e3572c in __glXDispatch (client=0xb1a910) at 
../../../GL/glx/glxext.c:561
stuff = (xGLXSingleReq *) 0xa6c010
opcode = 
proc = (__GLXdispatchSingleProcPtr) 0x2ba008e31a40 <__glXDisp_Render>
cl = (__GLXclientState *) 0xc5b690
retval = 1
#3  0x0044e300 in Dispatch () at ../../dix/dispatch.c:502
clientReady = 
result = 
client = (ClientPtr) 0xb1a910
nready = 0
start_tick = 2220
#4  0x00436add in main (argc=9, argv=0x7fffa421bee8, envp=) at ../../dix/main.c:452
i = 1
error = 0
xauthfile = 
alwaysCheckForInput = {0, 1}

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#473551: libgl1-mesa-dri: Crashes the X server when starting Valve's Portal under Wine on i965

[Mike Hommey]

On Mon, Mar 31, 2008 at 12:55:52PM +0200, Julien Cristau wrote:
> On Mon, Mar 31, 2008 at 12:17:20 +0200, Mike Hommey wrote:
> 
> > Package: libgl1-mesa-dri
> > Version: 7.0.3~rc2-1
> > Severity: important
> > 
> > I don't really know if this belongs here, but the stacktrace in the
> > crashed X server logs seem to indicate that somehow i965_dri.so might be
> > responsible for this crash.
> 
> Does this happen with different versions of the dri driver (it'd be nice
> to try the different 7.0.x versions at snapshot.debian.net)?

I'll try that when I have some more time. Do I need to also downgrade
libgl1-mesa-glx and other mesa packages at the same time I downgrade
libgl1-mesa-dri ?

> Please also provide your full X log and config files.

Attached here is the X log and config. (note the log is from another
crash for the same thing, so the addresses are slightly different)

Mike


Xorg.0.log.old
Description: application/trash
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "jp106"
Option  "XkbLayout" "jp"
Option  "XkbVariant""OADG109A"
Option  "XkbOptions"
"grp:alts_toggle,compose:menu,japan:kana_lock"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
EndSection

Section "Device"
Identifier  "Configured Video Device"
EndSection

Section "Monitor"
Identifier  "Configured Monitor"
EndSection

Section "Screen"
Identifier  "Default Screen"
Monitor "Configured Monitor"
EndSection

Bug#473551: libgl1-mesa-dri: Crashes the X server when starting Valve's Portal under Wine on i965

[Mike Hommey]

On Mon, Mar 31, 2008 at 12:17:20PM +0200, Mike Hommey wrote:
>   wine Steam.exe steam://hardwarepromo/609. Click a few times on Next,
>   and *bam*.

Actually, you don't even need to click a few times, it crashes as soon
as you launch the command.

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#473551: libgl1-mesa-dri: Crashes the X server when starting Valve's Portal under Wine on i965

[Mike Hommey]

Package: libgl1-mesa-dri
Version: 7.0.3~rc2-1
Severity: important

I don't really know if this belongs here, but the stacktrace in the
crashed X server logs seem to indicate that somehow i965_dri.so might be
responsible for this crash.

The stacktrace is the following:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6a) [0x4755da]
1: /lib/libc.so.6 [0x2b86ec0f2240]
2: /usr/lib/dri/i965_dri.so [0x2b86feed4239]
3: /usr/lib/xorg/modules/extensions//libglx.so(DoRender+0xcc) [0x2b86ed1ba92c]
4: /usr/lib/xorg/modules/extensions//libglx.so [0x2b86ed1be72c]
5: /usr/bin/X(Dispatch+0x2e0) [0x44e300]
6: /usr/bin/X(main+0x47d) [0x436add]
7: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b86ec0df1c4]
8: /usr/bin/X(FontFileCompleteXLFD+0x281) [0x435e19]

I'm sorry I can't provide a better one, because the X server will just
get stuck at 100% CPU usage whenever I try to attach gdb to it :(

Note this crash appear both when starting Portal or when starting Steam
to try to download the Portal demo. while the game itself is supposed to
work on any chip, the demo is limited for nvidia owners, so I wonder if
there is not some code trying to detect whether the chip is an nvidia
one or not, and that would cause the crash. This is obviously only an
hypothesis.

I also haven't tested if that is amd64 related or not.

Anyways, if you want to reproduce the bug, you can try the following
steps:
- Run wine iexplore http://winehq.org/ and click the install button.
  That will install the Gecko engine that is necessary for Steam. You
  can then close the window (note that if you have libnss-mdns
  installed, you should install lib32nss-mdns ; lacking that, DNS
  resolutions under wine will fail).
- Download the Steam installer from 
http://steampowered.com/download/SteamInstall.msi
- Install Steam: wine msiexec /i SteamInstall.msi. This will install and
  then run steam.
- Login to an existing account that you may own, or create a new one.
- Leave Steam opened (or not, as you wish), go to
  $HOME/.wine/drive_c/Program Files/Steam, then run
  wine Steam.exe steam://hardwarepromo/609. Click a few times on Next,
  and *bam*.

Mike

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libgl1-mesa-dri depends on:
ii  libc62.7-10  GNU C Library: Shared libraries
ii  libdrm2  2.3.0-4 Userspace interface to kernel DRM 
ii  libexpat11.95.8-4XML parsing C library - runtime li
ii  libgl1-mesa-glx  7.0.3~rc2-1 A free implementation of the OpenG

libgl1-mesa-dri recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#460654: xserver-xorg-video-intel: Brightness doesn't work out of the box with i965

[Mike Hommey]

On Wed, Feb 06, 2008 at 07:49:55PM +0100, Brice Goglin wrote:
> Mike Hommey wrote:
> > Package: xserver-xorg-video-intel
> > Version: 2:2.2.0+git20080107-1
> > Severity: normal
> >
> > By default, on my laptop, the "kernel" BACKLIGHT_CONTROL is used, and
> > that doesn't quite help xbacklight to work. I don't know what X uses in
> > such a case, but it appears that tweaking
> > /sys/class/backlight/sony/brightness doesn't work (the laptop is a vaio)
> > either, so it might just be a problem with the kernel driver.
> >
> > Anyways, switching to the "native" BACKLIGHT_CONTROL makes xbacklight
> > work.
> >   
> 
> Mike,
> 
> Can you try 2:2.2.0.90-2 which entered unstable today? If it doesn't
> help, we need to forward this bug upstream at
> http://bugzilla.freedesktop.org (product xorg, component Driver/Intel).
> I'll do it if you can't.

It still happens with 2:2.2.0.90-1 that I took from incoming. I filed
the bug upstream.

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#460654: xserver-xorg-video-intel: Brightness doesn't work out of the box with i965

[Mike Hommey]

Package: xserver-xorg-video-intel
Version: 2:2.2.0+git20080107-1
Severity: normal

By default, on my laptop, the "kernel" BACKLIGHT_CONTROL is used, and
that doesn't quite help xbacklight to work. I don't know what X uses in
such a case, but it appears that tweaking
/sys/class/backlight/sony/brightness doesn't work (the laptop is a vaio)
either, so it might just be a problem with the kernel driver.

Anyways, switching to the "native" BACKLIGHT_CONTROL makes xbacklight
work.

Mike

-- Package-specific info:
Contents of /var/lib/x11/X.roster:
xserver-xorg

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 2008-01-02 02:13 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1831520 2008-01-07 08:34 /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 Mobile Integrated Graphics 
Controller (rev 0c)

/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 1179 2008-01-10 17:41 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "jp106"
Option  "XkbLayout" "jp"
Option  "XkbVariant""OADG109A"
Option  "XkbOptions"
"grp:alts_toggle,compose:menu,japan:kana_lock"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
EndSection

Section "Device"
Identifier  "Configured Video Device"
EndSection

Section "Monitor"
Identifier  "Configured Monitor"
EndSection

Section "Screen"
Identifier  "Default Screen"
Monitor "Configured Monitor"
EndSection


Xorg X server log files on system:
-rw-r--r-- 1 root root 36667 2008-01-03 15:16 /var/log/Xorg.20.log
-rw-r--r-- 1 root root 36490 2008-01-05 22:17 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 39438 2008-01-14 18:30 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20080105-1)
Current Operating System: Linux jigen 2.6.24-rc7-amd64 #1 SMP Sat Jan 12 
01:58:46 UTC 2008 x86_64
Build Date: 06 January 2008  11:20:39PM
 
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: Mon Jan 14 18:29:19 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) No Layout section.  Using the first Screen section.
(**) |-->Screen "Default Screen" (0)
(**) |   |-->Monitor "Configured Monitor"
(==) No device specified for screen "Default Screen".
Using the first device section listed.
(**) |   |-->Device "Configured Video Device"
(==) |-->Input Device "Configured Mouse"
(==) |-->Input Device "Generic Keyboard"
(==) The core pointer device wasn't specified explicitly in the layout.
Using the first mouse device.
(==) The core keyboard device wasn't specified explicitly in the layout.
Using the first keyboard device.
(==) Automatically adding devices
(==) Automatically enabling devices
(==) No FontPath specified.  Using compiled-in default.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
Entry deleted from font path.
(WW) `fonts.dir' not found (or not valid) in 
"/var/

Bug#442892: xserver-xorg: This bug is still around

[Mike Hommey]

Followup-For: Bug #442892
Package: xserver-xorg
Version: 1:7.3+9

FWIW, I got the same thing again when installing a brand new debian system,
first installing the base system, then xserver-xorg with
APT::Install-Recommends set to false.

This sadly results in an empty xorg.conf, which makes the system
unuseable, while having no xorg.conf file at all works in most cases.

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#452734: pixman: Please package new upstream version (0.9.6)

[Mike Hommey]

Package: pixman
Severity: wishlist

Everything is in the subject. This would be required to build
experimental cairo 1.5.2, which, in turn, would be necessary for
xulrunner 1.9b1, aimed at experimental.

Thanks

Mike

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#442892: dpkg-reconfigure xserver-xorg is useless without discover installed

[Mike Hommey]

Package: xserver-xorg
Version: 1:7.3+2
Severity: important

Hi,

I recently upgraded my x.org server in sid, and, after upgrade, the X
server would not work. But this is another issue I will try to
understand at another time.

Anyways, the thing is, since my conf was not working, I wanted to try to
dpkg-reconfigure xserver-xorg, which I would assume to work, but didn't
in my case, because discover was not installed.

Here is the message I get after reconfiguring when discover is not
installed:

xserver-xorg postinst warning: overwriting possibly-customised configuration
   file; backup in /etc/X11/xorg.conf.20070917193443
dexconf: error: cannot generate configuration file; 
xserver-xorg/config/device/driver not set.  Aborting.  Reconfigure the X server 
with "dpkg-reconfigure xserver-xorg" to correct this problem.
xserver-xorg postinst warning: error while preparing new Xorg X server
   configuration file in /etc/X11/xorg.conf.dpkg-new; not attempting to
   update existing configuration

Note that /etc/X11/xorg.conf.dpkg-new doesn't even exist after this, and
that I never get asked what driver to use.

After installing discover, everything works fine.

Mike

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xserver-xorg depends on:
ii  debconf [debconf-2 1.5.14Debian configuration management sy
ii  x11-common 1:7.3+2   X Window System (X.Org) infrastruc
ii  xbase-clients  1:7.3+2   miscellaneous X clients - metapack
ii  xkb-data   1.0~cvs.20070916-1X Keyboard Extension (XKB) configu
ii  xserver-xorg-core  2:1.4-2   X.Org X server -- core server
ii  xserver-xorg-input 1:1.2.0~git20070819-3 X.Org X server -- evdev input driv
ii  xserver-xorg-input 1:1.2.2-3 X.Org X server -- keyboard input d
ii  xserver-xorg-input 1:1.2.2-5 X.Org X server -- mouse input driv
ii  xserver-xorg-video 1:6.6.193-3   X.Org X server -- ATI display driv
ii  xserver-xorg-video 1:1.3.0-4 X.Org X server -- VESA display dri

Versions of packages xserver-xorg recommends:
ii  discover   2.1.2-2   hardware identification system
ii  dmidecode  2.9-1 Dump Desktop Management Interface 
ii  laptop-detect  0.13.2attempt to detect a laptop
ii  libgl1-mesa-dri7.0.1-2   A free implementation of the OpenG
ii  xresprobe  0.4.23debian1-0.1 X Resolution Probe

-- debconf information excluded



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#280579: closed by Mohammed Adnène Trojette <[EMAIL PROTECTED]> (Bug#280579: fixed in xkeyboard-config 1.0~cvs.20070721-1)

[Mike Hommey]

found 280579 1.0~cvs.20070721-1
thanks

On Sat, Jul 21, 2007 at 07:39:03PM +, Debian Bug Tracking System <[EMAIL 
PROTECTED]> wrote:
> This is an automatic notification regarding your Bug report
> #280579: xlibs-data: [xkb] jp106 backslash/yen issue,
> which was filed against the xkb-data package.
> 
> It has been closed by Mohammed Adnène Trojette <[EMAIL PROTECTED]>.

Unfortunately, the yen key still inputs a backslash here...

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#355365: xserver-xorg: Wrong keyboard model for japanese keyboard

[Mike Hommey]

On Sun, Jun 17, 2007 at 08:20:44PM +0200, Brice Goglin <[EMAIL PROTECTED]> 
wrote:
> Hi,
> 
> About a year ago, you reported a bug to the Debian BTS regarding a wrong
> keyboard being chosen for japanese keyboard. Did you reproduce this
> problem recently? With Xorg/Etch? With latest Xorg packages in unstable?

I can confirm that this is okay with xorg in etch (just tested a fresh
install from the official dvds under qemu). Please feel free to close
with the appropriate version information.

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#367158: I have this problem too

[Mike Hommey]

reassign 367158 gdm
thanks

Hi,

First, I believe the bug belongs to gdm, so i'm reassigning.

The problem appears that when running a second X server by mean of gdm
(by asking a new login from the gnome desktop, for example), the gdm
login form in this second X server uses smaller fonts than the same
login form on the first X server.

I guess it is using a dpi of 75 instead of 96.

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#384944: xserver-xorg: Can't enable EXA

[Mike Hommey]

Package: xserver-xorg
Version: 1:7.0.23
Severity: normal

I totally fail to enable EXA. I've tried
Option "AccelMethod" "EXA",
Option "AccelMethod" "exa",
with or without AGP stuff,
with or without the composite extension,

I *always* get the XAA method loaded, as stated by the Xorg.0.log.

Mike


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)

Versions of packages xserver-xorg depends on:
ii  debconf  1.5.3   Debian configuration management sy
ii  x11-common   1:7.0.23X Window System (X.Org) infrastruc
ii  xbase-clients1:7.1.ds-3  miscellaneous X clients
ii  xkb-data 0.8-7   X Keyboard Extension (XKB) configu
ii  xserver-xorg-core2:1.0.2-10  X.Org X server -- core server
ii  xserver-xorg-input-evdev [xs 1:1.1.2-1   X.Org X server -- evdev input driv
ii  xserver-xorg-input-kbd [xser 1:1.0.1.3-2 X.Org X server -- keyboard input d
ii  xserver-xorg-input-mouse [xs 1:1.0.4-3   X.Org X server -- mouse input driv
ii  xserver-xorg-video-ati [xser 1:6.6.0-1   X.Org X server -- ATI display driv
ii  xserver-xorg-video-vesa [xse 1:1.0.1.3-2 X.Org X server -- VESA display dri

Versions of packages xserver-xorg recommends:
pn  discover1 | discover   (no description available)
ii  laptop-detect  0.12.1attempt to detect a laptop
ii  mdetect0.5.2.1   mouse device autodetection tool
ii  xresprobe  0.4.23debian1 X Resolution Probe

-- debconf information:
  xserver-xorg/multiple_possible_x-drivers:
  xserver-xorg/config/monitor/use_sync_ranges:
* xserver-xorg/config/inputdevice/mouse/port: /dev/input/mice
  xserver-xorg/config/monitor/lcd:
  xserver-xorg/config/doublequote_in_string_error:
  xserver-xorg/config/monitor/screen-size: 17 inches (430 mm)
* shared/default-x-server: xserver-xorg
* xserver-xorg/autodetect_monitor: true
* xserver-xorg/config/inputdevice/mouse/protocol: ImPS/2
  shared/no_known_x-server:
* xserver-xorg/config/display/default_depth: 24
  xserver-xorg/config/display/modes: 1280x800
  xserver-xorg/config/device/bus_id_error:
  xserver-xorg/config/inputdevice/keyboard/internal:
  xserver-xorg/config/monitor/vert-refresh: 43-60
* xserver-xorg/config/inputdevice/keyboard/options:
* xserver-xorg/autodetect_keyboard: false
* xserver-xorg/config/device/use_fbdev: false
* xserver-xorg/config/inputdevice/keyboard/variant: jp106
  xserver-xorg/config/nonnumeric_string_error:
  xserver-xorg/config/fontpath/fontserver:
* xserver-xorg/config/inputdevice/keyboard/layout: jp
* xserver-xorg/config/modules: bitmap, dbe, ddc, dri, extmod, freetype, glx, 
int10, type1, vbe
  xserver-xorg/config/monitor/identifier: Generic Monitor
* xserver-xorg/config/inputdevice/mouse/emulate3buttons: true
  xserver-xorg/autodetect_mouse: true
  xserver-xorg/config/monitor/horiz-sync: 28-64
* xserver-xorg/config/device/video_ram:
  xserver-xorg/config/monitor/range_input_error:
  xserver-xorg/config/write_dri_section: true
* xserver-xorg/config/inputdevice/keyboard/model: jp106
* xserver-xorg/config/device/driver: ati
* xserver-xorg/config/device/identifier: Generic Video Card
  xserver-xorg/config/monitor/selection-method: Advanced
  xserver-xorg/config/null_string_error:
  shared/multiple_possible_x-servers:
* xserver-xorg/config/device/bus_id: PCI:1:0:0
* xserver-xorg/config/write_files_section: true
* xserver-xorg/autodetect_video_card: true
  xserver-xorg/config/monitor/mode-list: 1280x800 @ 60Hz
* xserver-xorg/config/inputdevice/keyboard/rules: xorg


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#363965: xserver-xorg: Can't force update of /etc/X11/xorg.conf

[Mike Hommey]

Package: xserver-xorg
Version: 1:7.0.14
Severity: normal

/etc/X11/xorg.conf states:
# 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

So, okay...
namakemono:/home/mh# dpkg-reconfigure -phigh xserver-xorg
xserver-xorg postinst warning: not updating /etc/X11/xorg.conf; file has
   been customized
namakemono:/home/mh#

Either the postinst or the comment has to be fixed according to the
other.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)

Versions of packages xserver-xorg depends on:
ii  debconf   1.4.72 Debian configuration management sy
ii  x11-common1:7.0.14   X Window System (X.Org) infrastruc
ii  xbase-clients 1:7.0.0-4  miscellaneous X clients
ii  xkb-data  0.8-5  X Keyboard Extension (XKB) configu
ii  xserver-xorg-core 1:1.0.2-5  X.Org X server -- core server
ii  xserver-xorg-input-al 1:7.0.14   the X.Org X server -- input driver
ii  xserver-xorg-input-ev 1:1.0.0.5-2X.Org X server -- evdev input driv
ii  xserver-xorg-input-kb 1:1.0.1.3-2X.Org X server -- keyboard input d
ii  xserver-xorg-input-mo 1:1.0.4-2  X.Org X server -- mouse input driv
ii  xserver-xorg-video-al 1:7.0.14   the X.Org X server -- output drive
ii  xserver-xorg-video-ap 1:1.0.1.5-2X.Org X server -- APM display driv
ii  xserver-xorg-video-ar 1:0.5.0.5-2X.Org X server -- ark display driv
ii  xserver-xorg-video-at 1:6.5.7.3-3X.Org X server -- ATI display driv
ii  xserver-xorg-video-ch 1:1.0.1.3-3X.Org X server -- Chips display dr
ii  xserver-xorg-video-ci 1:1.0.0.5-2X.Org X server -- Cirrus display d
ii  xserver-xorg-video-cy 1:1.0.0.5-2X.Org X server -- Cyrix display dr
ii  xserver-xorg-video-du 1:0.1.0.5-2X.Org X server -- dummy display dr
ii  xserver-xorg-video-fb 1:0.1.0.5-2X.Org X server -- fbdev display dr
ii  xserver-xorg-video-gl 1:1.0.1.3-2X.Org X server -- Glint display dr
ii  xserver-xorg-video-i1 1:1.1.0.5-2X.Org X server -- i128 display dri
ii  xserver-xorg-video-i7 1:1.0.0.5-2X.Org X server -- i740 display dri
ii  xserver-xorg-video-i8 1:1.5.1.0-2X.Org X server -- Intel i8xx, i9xx
ii  xserver-xorg-video-im 1:1.0.0.5-2X.Org X server -- IMSTT display dr
ii  xserver-xorg-video-mg 1:1.2.1.3.dfsg.1-2 X.Org X server -- MGA display driv
ii  xserver-xorg-video-ne 1:1.0.0.5-2X.Org X server -- Neomagic display
ii  xserver-xorg-video-ne 1:0.1.4.1-3X.Org X server -- Newport display 
ii  xserver-xorg-video-ns 1:2.7.6.5-2X.Org X server -- NSC display driv
ii  xserver-xorg-video-nv 1:1.0.1.5-2X.Org X server -- NV display drive
ii  xserver-xorg-video-re 1:4.0.1.3.dfsg.1-2 X.Org X server -- Rendition displa
ii  xserver-xorg-video-s3 1:1.8.6.5-2X.Org X server -- S3 ViRGE display
ii  xserver-xorg-video-sa 1:2.0.2.3-4X.Org X server -- Savage display d
ii  xserver-xorg-video-si 1:1.3.1.5-3X.Org X server -- SiliconMotion di
ii  xserver-xorg-video-si 1:0.8.1.3-2X.Org X server -- SiS display driv
ii  xserver-xorg-video-si 1:0.7.1.3-2X.Org X server -- SiS USB display 
ii  xserver-xorg-video-td 1:1.1.1.3-3X.Org X server -- tdfx display dri
ii  xserver-xorg-video-tg 1:1.0.0.5-3X.Org X server -- TGA display driv
ii  xserver-xorg-video-tr 1:1.0.1.2-2X.Org X server -- Trident display 
ii  xserver-xorg-video-ts 1:1.0.0.5-2X.Org X server -- Tseng display dr
ii  xserver-xorg-video-ve 1:1.0.1.3-2X.Org X server -- VESA display dri
ii  xserver-xorg-video-vg 1:4.0.0.5-2X.Org X server -- VGA display driv
ii  xserver-xorg-video-vi 1:0.1.33.2-2   X.Org X server -- VIA display driv
ii  xserver-xorg-video-vm 1:10.11.1.3-2  X.Org X server -- VMware display d
ii  xserver-xorg-video-vo 1:1.0.0.5-2X.Org X server -- Voodoo display d

Versions of packages xserver-xorg recommends:
ii  discover1  1.7.18hardware identification system
ii  laptop-detect  0.12.1attempt to detect a laptop
ii  mdetect0.5.2.1   mouse device autodetection tool
ii  xresprobe  0.4.23debian1 X Resolution Probe

-- debconf information:
  xserver-xorg/multiple_possible_x-drivers:
  xserver-xorg/config/monitor/use_sync_ranges:
* xserver-xorg/config/inputdevice/mouse/port: /dev/input/mice
  xserver-xorg/config/monitor/lcd:
  xserver-xorg/config/doublequote_in_string_

Bug#358578: libxft-dev: FTBFSes firefox,xulrunner,and many others

[Mike Hommey]

Package: libxft-dev
Version: 2.1.8.2-5
Severity: serious
Followup-For: Bug #358578

I'm raising severity because it makes other packages FTBFS.

Due to the lack of the link, a whole lot of packages like firefox,
xulrunner and probably many others just FTBFS.

Please fix that quickly.

Thanks

Mike


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#280579: xlibs-data: [xkb] jp106 backslash/yen issue

[Mike Hommey]

On Wed, Nov 10, 2004 at 10:21:22PM +0100, Denis Barbier <[EMAIL PROTECTED]> 
wrote:
> On Wed, Nov 10, 2004 at 07:49:41PM +0900, Mike Hommey wrote:
> [...]
> > Note that on the same keyboard, The windows key gives keycode 115
> > (keysym 0x0, NoSymbol), which i think is not expected. Shall I file a
> > new bug for that ?
> 
> Yes please, and send the output of the following command:
>   xprop -root | grep XKB

_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "jp106", "jp", "", "jp106"
_XKB_RULES_NAMES(STRING) = "xorg", "jp106", "jp", "", "compose:menu"



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#355365: xserver-xorg: Wrong keyboard model for japanese keyboard

[Mike Hommey]

Package: xserver-xorg
Version: 6.9.0.dfsg.1-4
Severity: normal

When at install time, the user selects the "japanese" keyboard, the
configuration is made as follows:
  xserver-xorg/config/inputdevice/keyboard/options: jp106
  xserver-xorg/config/inputdevice/keyboard/model: pc105

Unless the model is set to jp106, the <},],」,む> key neer Enter doesn't
work as expected (works as a <|,¥,ー> key, which by the way, still
doesn't work as expected either, cf. bug #280579).

Cheers,

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#354245: xserver-xorg-core: Can't load GLcore module: unknown symbol: __glXLastContext

[Mike Hommey]

On Sun, Feb 26, 2006 at 01:38:24PM +0100, Michel D?nzer <[EMAIL PROTECTED]> 
wrote:
> On Fri, 2006-02-24 at 19:11 +0100, Mike Hommey wrote:
> > 
> > I get the following message in my logs:
> > (II) Loading /usr/lib/xorg/modules/extensions/libGLcore.so
> > dlopen: /usr/lib/xorg/modules/extensions/libGLcore.so: undefined symbol: 
> > __glXLastContext
> > (EE) Failed to load /usr/lib/xorg/modules/extensions/libGLcore.so
> > (II) UnloadModule: "GLcore"
> > (EE) Failed to load module "GLcore" (loader failed, 7)
> 
> If you load the "GLcore" module explicitly, don't. This is not a bug in
> the X server but possibly in the configuration logic that lets you load
> this module explicitly (see also
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=346408).

OK, so that is the actual bug: that the X configuration brings GLcore in
its list of modules.
You may choose to close this bug or merge it. It's up to you.

Cheers

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#354363: xserver-xorg: Video modes selection gives me 1200x800 but no 1280x800

[Mike Hommey]

Package: xserver-xorg
Version: 6.9.0.dfsg.1-4
Severity: normal

My screen is 1280x800 and the closer I could find in the video modes
selection was 1200x800, which I'm not exactly sure exists...

It would be greatly appreciated if 1280x800 was added ;)

-- Package-specific info:
Contents of /var/lib/xfree86/X.roster:
xserver-xorg

/etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum.

X server symlink status:
lrwxrwxrwx 1 root root 17 Feb 25 17:58 /etc/X11/X -> /usr/bin/X11/Xorg
-rwxr-xr-x 1 root root 1878044 Jan 15 02:40 /usr/bin/X11/Xorg

Contents of /var/lib/xfree86/xorg.conf.roster:
xserver-xorg

VGA-compatible devices on PCI bus:
:01:00.0 VGA compatible controller: ATI Technologies Inc M9+ 5C61 [Radeon 
Mobility 9200 (AGP)] (rev 01)

/etc/X11/xorg.conf unchanged from checksum in /var/lib/xfree86/xorg.conf.md5sum.

Xorg X server configuration file status:
-rw-r--r-- 1 root root 3081 Feb 25 17:58 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
# xorg.conf (Xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following commands as root:
#
#   cp /etc/X11/xorg.conf /etc/X11/xorg.conf.custom
#   md5sum /etc/X11/xorg.conf >/var/lib/xfree86/xorg.conf.md5sum
#   dpkg-reconfigure xserver-xorg

Section "Files"
FontPath"unix/:7100"# local font server
# if the local font server has problems, we can fall back on these
FontPath"/usr/lib/X11/fonts/misc"
FontPath"/usr/lib/X11/fonts/cyrillic"
FontPath"/usr/lib/X11/fonts/100dpi/:unscaled"
FontPath"/usr/lib/X11/fonts/75dpi/:unscaled"
FontPath"/usr/lib/X11/fonts/Type1"
FontPath"/usr/lib/X11/fonts/CID"
FontPath"/usr/lib/X11/fonts/100dpi"
FontPath"/usr/lib/X11/fonts/75dpi"
EndSection

Section "Module"
Load"bitmap"
Load"dbe"
Load"ddc"
Load"dri"
Load"evdev"
Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"record"
Load"type1"
Load"vbe"
EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "keyboard"
Option  "CoreKeyboard"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "jp"
Option  "XkbOptions""jp106"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "Emulate3Buttons"   "true"
Option  "ZAxisMapping"  "4 5"
EndSection
Section "InputDevice"
Identifier  "Synaptics Touchpad"
Driver  "synaptics"
Option  "SendCoreEvents""true"
Option  "Device""/dev/psaux"
Option  "Protocol"  "auto-dev"
Option  "HorizScrollDelta"  "0"
EndSection

Section "Device"
Identifier  "ATI Technologies, Inc. M9+ 5C61 [Radeon Mobility 9200 
(AGP)]"
Driver  "ati"
BusID   "PCI:1:0:0"
EndSection

Section "Monitor"
Identifier  "Generic Monitor"
Option  "DPMS"
EndSection

Section "Screen"
Identifier  "Default Screen"
Device  "ATI Technologies, Inc. M9+ 5C61 [Radeon Mobility 9200 
(AGP)]"
Monitor "Generic Monitor"
DefaultDepth24
SubSection "Display"
Depth   1
Modes   "1200x800"
EndSubSection
SubSection "Display"
Depth   4
Modes   "1200x800"
EndSubSection
SubSection "Display"
Depth   8
Modes   "1200x800"
EndSubSection
SubSection "Display"
Depth   15
Modes   "1200x800"
EndSubSection
SubSection "Display"
Depth   16
Modes   "1200x800"
EndSubSection
SubSection "Display"
Depth   24
Modes   "1200x800"
EndSubSection
EndSection

Section "ServerLa

Bug#354246: xbase-clients: Doesn't contain (at least) glxgears anymore

[Mike Hommey]

Package: xbase-clients
Version: 1:1.0.1-1
Severity: normal

Contrary to what is said in the package description, (at least) glxgears
is not present in the package.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages xbase-clients depends on:
ii  libc6 2.3.6-1GNU C Library: Shared libraries an
ii  libdmx1   1:1.0.1-1  X11 Distributed Multihead extensio
ii  libfontconfig12.3.2-2generic font configuration library
ii  libfreetype6  2.1.10-1   FreeType 2 font engine, shared lib
ii  libfs62:1.0.0-1  X11 Font Services library
ii  libice6   1:1.0.0-1  X11 Inter-Client Exchange library
ii  libpng12-01.2.8rel-5 PNG library - runtime
ii  libsm66.9.0.dfsg.1-4 X Window System Session Management
ii  libx11-6  2:1.0.0-1  X11 client-side library
ii  libxau6   1:1.0.0-1  X11 authorisation library
ii  libxaw7   6.9.0.dfsg.1-4 X Athena widget set library
ii  libxcursor1   1.1.5.2-1  X cursor management library
ii  libxext6  1:1.0.0-1  X11 miscellaneous extension librar
ii  libxft2   2.1.8.2-3  FreeType-based font drawing librar
ii  libxi61:1.0.0-1  X11 Input extension library
ii  libxinerama1  6.9.0.dfsg.1-4 X Window System multi-head display
ii  libxkbfile1   6.9.0.dfsg.1-4 X Keyboard Extension file parsing 
ii  libxmu6   6.9.0.dfsg.1-4 X Window System miscellaneous util
ii  libxmuu1  6.9.0.dfsg.1-4 lightweight X Window System miscel
ii  libxrandr26.9.0.dfsg.1-4 X Window System Resize, Rotate and
ii  libxrender1   1:0.9.0.2-1X Rendering Extension client libra
ii  libxss1   1:1.0.1-1  X11 Screen Saver extension library
ii  libxt66.9.0.dfsg.1-4 X Toolkit Intrinsics
ii  libxtrap6 1:1.0.0-1  X11 event trapping extension libra
ii  libxtst6  1:1.0.1-1  X11 Testing -- Resource extension 
ii  libxv11:1.0.1-1  X11 Video extension library
ii  libxxf86dga1  1:1.0.1-1  X11 Direct Graphics Access extensi
ii  libxxf86misc1 1:1.0.0-1  X11 XFree86 miscellaneous extensio
ii  libxxf86vm1   1:1.0.0-1  X11 XFree86 video mode extension l
ii  x11-common1:7.0.0X Window System (X.Org) infrastruc
ii  xlibmesa-gl [libgl1]  6.9.0.dfsg.1-4 Mesa 3D graphics library [X.Org]
ii  zlib1g1:1.2.3-9  compression library - runtime

xbase-clients recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#354245: xserver-xorg-core: Can't load GLcore module: unknown symbol: __glXLastContext

[Mike Hommey]

Package: xserver-xorg-core
Version: 1:1.0.1-1
Severity: normal

I get the following message in my logs:
(II) Loading /usr/lib/xorg/modules/extensions/libGLcore.so
dlopen: /usr/lib/xorg/modules/extensions/libGLcore.so: undefined symbol: 
__glXLastContext
(EE) Failed to load /usr/lib/xorg/modules/extensions/libGLcore.so
(II) UnloadModule: "GLcore"
(EE) Failed to load module "GLcore" (loader failed, 7)

There must be a missing dependency or recommends on the package.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages xserver-xorg-core depends on:
ii  libc62.3.6-1 GNU C Library: Shared libraries an
ii  libfontenc1  1:1.0.1-1   X11 font encoding library
ii  libgcc1  1:4.0.2-9   GCC support library
ii  libxau6  1:1.0.0-1   X11 authorisation library
ii  libxdmcp61:1.0.0-1   X11 Display Manager Control Protoc
ii  libxfont11:1.0.0-1   X11 font rasterisation library
ii  x11-common   1:7.0.0 X Window System (X.Org) infrastruc
ii  xserver-xorg-input-all   1:7.0.0 the X.Org X server -- input driver
ii  xserver-xorg-input-evdev [xs 1:1.0.0.5-1 X.Org X server -- evdev input driv
ii  xserver-xorg-input-kbd [xser 1:1.0.1.3-1 X.Org X server -- keyboard input d
ii  xserver-xorg-input-mouse [xs 1:1.0.3.1-1 X.Org X server -- mouse input driv
ii  xserver-xorg-video-ati [xser 1:6.5.7.3-1 X.Org X server -- ATI display driv
ii  zlib1g   1:1.2.3-9   compression library - runtime

Versions of packages xserver-xorg-core recommends:
pn  xkeyboard-config   (no description available)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#349678: acknowledged by developer (Re: RFP: gstreamer-ffmpeg -- 5)

[Mike Hommey]

I don't know which bug you intended to close, but it's not this one...

Mike

On Tue, Jan 24, 2006 at 09:48:16AM -0800, Debian Bug Tracking System <[EMAIL 
PROTECTED]> wrote:
> This is an automatic notification regarding your Bug report
> #349678: libxft-dev: pkg-config file says requires xproto that don't exist,
> which was filed against the libxft-dev package.
> 
> It has been closed by one of the developers, namely
> Loïc Minier <[EMAIL PROTECTED]>.
> 
> Their explanation is attached below.  If this explanation is
> unsatisfactory and you have not received a better one in a separate
> message then please contact the developer, by replying to this email.
> 
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
> 
> Received: (at 349678-done) by bugs.debian.org; 24 Jan 2006 17:44:20 +
> From [EMAIL PROTECTED] Tue Jan 24 09:44:20 2006
> Return-path: <[EMAIL PROTECTED]>
> Received: from mf01.sitadelle.com ([212.94.174.68] helo=smtp.cegetel.net)
>   by spohr.debian.org with esmtp (Exim 4.50)
>   id 1F1SDM-0002hm-Iv
>   for [EMAIL PROTECTED]; Tue, 24 Jan 2006 09:44:20 -0800
> Received: from mx0.bpl-group.org (mx0.bpl-group.org [195.115.71.69])
>   by smtp.cegetel.net (Postfix) with ESMTP id B50626A0B1D;
>   Tue, 24 Jan 2006 18:43:47 +0100 (CET)
> Received: from bee.dooz.org (levallois.dooz.org [81.57.180.178])
>   (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
>   (Client CN "lminier.people.bpl-group.org", Issuer "BPL Group People 
> Certification Authority" (verified OK))
>   by mx0.bpl-group.org (Postfix) with ESMTP id 54EDEC589;
>   Tue, 24 Jan 2006 17:43:47 + (UTC)
> Received: by bee.dooz.org (Postfix, from userid 1000)
>   id CE8F34F008F; Tue, 24 Jan 2006 18:43:45 +0100 (CET)
> Date: Tue, 24 Jan 2006 18:43:45 +0100
> From: =?iso-8859-1?Q?Lo=EFc?= Minier <[EMAIL PROTECTED]>
> To: Jaap Haitsma <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: RFP: gstreamer-ffmpeg -- 5
> Message-ID: <[EMAIL PROTECTED]>
> References: <[EMAIL PROTECTED]>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=iso-8859-1
> Content-Disposition: inline
> In-Reply-To: <[EMAIL PROTECTED]>
> Content-Transfer-Encoding: quoted-printable
> X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
>   (1.212-2003-09-23-exp) on spohr.debian.org
> X-Spam-Level: 
> X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
>   version=2.60-bugs.debian.org_2005_01_02
> 
> Hi,
> 
> On Sat, Mar 26, 2005, Jaap Haitsma wrote:
> > * Package name: gstreamer-ffmpeg
> >   Version : 0.8.4
> >   Upstream Author : gstreamer dev team
> > * URL : http://gstreamer.freedesktop.org/modules/gst-ffmpeg=
> .html
> 
>  This package is in Debian, closing the RFP.
> 
>Bye,
> 
> --=20
> Lo=EFc Minier <[EMAIL PROTECTED]>
> Current Earth status:   NOT DESTROYED


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#349678: libxft-dev: pkg-config file says requires xproto that don't exist

[Mike Hommey]

Package: libxft-dev
Version: 2.1.8.2-1
Severity: critical
Justification: breaks unrelated software

The file /usr/lib/pkgconfig/xft.pc says xft requires xproto, which is
available in no package, as stated by apt-file.

Even if it existed, there should be a dependency to the dev package
holding it.

That breaks all packages that build depend on libxft and rely on
pkg-config to get the compilation and linking flags (such as mozilla,
thunderbird, firefox...).

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#318413: xlibs: Backslash Key is broken on Japanese Keyboards

[Mike Hommey]

On Fri, Jul 15, 2005 at 02:58:32PM +0300, Horms <[EMAIL PROTECTED]> wrote:
> Package: xlibs
> Version: 6.8.2.dfsg.1-2
> Severity: important
> Tags: patch
> 
> Hi,
> 
> After upgrading xlibs the backslash no longer works on 
> my Toshiba Dynabook with a japanese keyboard. This makes
> coding really hard!
> 
> The attached patch resolves this problem as well as making the
> Hirugana/Katakana toggle work.

Interestingly, I had the same problem here, which got resolved as soon
as I switched from xserver-xfree86 to xserver-xorg.

Though the file you patch is the same on my system than your "broken"
one, the backslash key works correctly... it's a bit weird...

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#284561: xserver-xfree86: Mouse buttons events get mixed up when trying to remap buttons

[Mike Hommey]

On Tue, Dec 07, 2004 at 11:24:55AM -0500, Michel Dänzer <[EMAIL PROTECTED]> 
wrote:
> With a 2.6 kernel, /dev/psaux is just an alias of /dev/input/mice. So
> you have two input devices for the same thing (didn't you notice the
> mouse being twice as fast as it should be? ;), but the button remapping
> only applies to the CorePointer.

That's a very interesting explanation, and in fact, after removing
the /dev/psaux input device section, it works correctly.

The thing is that, no, i didn't notice the mouse being twice as fast as
it should be, because it is a newly installed laptop, and i was using
most of the time the touchpad, which now i removed one device is too
slow :-/

So now, there's the problem : I made the installation using the sarge
cd, and using the 2.6 install kernel, which means that even when you
install a 2.6 kernel, XFree does its configuration for both.

May i close the current bug and file a new one about that or may we just
retitle this bug ?

That could be a good thing to add to the XSF FAQ...

Mike

Bug#284561: xserver-xfree86: Mouse buttons events get mixed up when trying to remap buttons

[Mike Hommey]

Package: xserver-xfree86
Version: 4.3.0.dfsg.1-8
Severity: normal
Tags: upstream

When trying to remap the mouse buttons with xmodmap, xinput or the gnome
mouse panel (left-handed setting), the mouse events get mixed up.

I used the following commands, all showing the same behaviour:
$ xmodmap -e "pointer = 3 2 1 4 5"
$ xinput set-button-map "Generic Mouse" 3 2 1 4 5
and going into the gnome mouse configuration panel and choosing
left-handed setting.
All are expected to give the same result.

The mouse in question is a Logitech Cordless Mouse with a scrolling
wheel.

When running xev and looking at events given, this is the result:

Normal setting (no remapping):
Button 1:
 ButtonPress event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 590947, (160,63), root:(164,132),
state 0x0, button 1, same_screen YES

 ButtonRelease event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 591043, (160,63), root:(164,132),
state 0x100, button 1, same_screen YES

Button 2:
 ButtonPress event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 592610, (160,63), root:(164,132),
state 0x0, button 2, same_screen YES

 ButtonRelease event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 592778, (160,63), root:(164,132),
state 0x200, button 2, same_screen YES

Button 3:
 ButtonPress event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 593850, (160,63), root:(164,132),
state 0x0, button 3, same_screen YES

 ButtonRelease event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 594018, (160,63), root:(164,132),
state 0x400, button 3, same_screen YES

Remapped setting:
Button 1:
 ButtonPress event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 611063, (166,85), root:(170,154),
state 0x0, button 1, same_screen YES

 ButtonPress event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 611122, (166,85), root:(170,154),
state 0x100, button 3, same_screen YES

 ButtonRelease event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 611151, (166,85), root:(170,154),
state 0x500, button 1, same_screen YES

 ButtonRelease event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 611151, (166,85), root:(170,154),
state 0x400, button 3, same_screen YES

Button 2:
 ButtonPress event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 612423, (166,85), root:(170,154),
state 0x0, button 2, same_screen YES

 ButtonRelease event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 612607, (166,85), root:(170,154),
state 0x200, button 2, same_screen YES

Button 3:
 ButtonPress event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 613639, (166,85), root:(170,154),
state 0x0, button 3, same_screen YES

 ButtonPress event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 613703, (166,85), root:(170,154),
state 0x400, button 1, same_screen YES

 ButtonRelease event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 613823, (166,85), root:(170,154),
state 0x500, button 3, same_screen YES

 ButtonRelease event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 613823, (166,85), root:(170,154),
state 0x100, button 1, same_screen YES

I also tried something else, being inverting the scroll wheel direction
with:
$ xmodmap -e "pointer = 1 2 3 5 4"
$ xinput set-button-map "Generic Mouse" 1 2 3 5 4

Normal Setting gives:
Scroll up:
 ButtonPress event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 1016660, (161,129), root:(165,198),
state 0x0, button 4, same_screen YES

 ButtonRelease event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 1016660, (161,129), root:(165,198),
state 0x800, button 4, same_screen YES

 ButtonPress event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 1016660, (161,129), root:(165,198),
state 0x0, button 4, same_screen YES

 ButtonRelease event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 1016660, (161,129), root:(165,198),
state 0x800, button 4, same_screen YES

Scroll down:
 ButtonPress event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 1018563, (161,129), root:(165,198),
state 0x0, button 5, same_screen YES

 ButtonRelease event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 1018563, (161,129), root:(165,198),
state 0x1000, button 5, same_screen YES

 ButtonPress event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0, time 1018563, (161,129), root:(165,198),
state 0x0, button 5, same_screen YES

 ButtonRelease event, serial 26, synthetic NO, window 0x201,
root 0x40, subw 0x0,

Re: DPI, font size, and Debian

[Mike Hommey]

On Mon, Dec 06, 2004 at 12:55:20PM -0600, Billy Biggs <[EMAIL PROTECTED]> wrote:
>   - Font hints are not designed for small pixel sizes at arbitrary
> DPIs.  I have shown this via screenshots which I posted.

See Keith's answer

>   - GNOME defaults to a 10 point font for the application font.  My
> experience dictates that users find this too small on their
> autodetected 80-DPI screens, and too large at their autodetected
> 133-DPI screens.

That can be the result of 2 things:
- Actual DPI not being correctly detected by X, but I really doubt it.
- Bad user feedback. Users have been used to badly set DPIs, leading to
  several different things. One of which is the following: 10pt font at
  133dpi, yes, is smaller than 10pt at 100dpi on the same screen at the
  same resolution. And 10pt font at 80dpi, yes, is smaller than 10pt at
  100dpi on the same screen at the same resolution. Coming back to my
  own bad habits case, with having 75dpi on a 15" at a resolution of
  1400x1050 , I got used to *small* fonts. *Everybody*, when looking at
  my screen, told me "isn't it too small" ? And I usually answered "no,
  that's fine".
  Now I'm using a 13.3" screen at 1280x800, with 112dpi and 10pt fonts,
  they are, yes, much much bigger than what I was using before, but
  actually, it's much better now.
  Since then, I reinstalled the 15" laptop (giving a try to Ubuntu at
  the same time ;) ) and set the adequate DPI, set the fonts to 10pt,
  and guess what... it gives me the same size for fonts as the 13.3"
  does, which was what i expected.

>   - Other operating systems do not use the real DPI of the display, and
> there does not seem to be a strong movement towards having this
> changed.

Again, it's not because other OS are stupid that we have to do the same.

Mike

Re: DPI, font size, and Debian

[Mike Hommey]

On Mon, Dec 06, 2004 at 10:30:22AM -0600, Billy Biggs <[EMAIL PROTECTED]> wrote:
>   I think we agree on this.  My opinion was that either every display
> manager set the DPI in their config file (and that be the "one" place)
> or its done elsewhere.  Consensus seems to be to do it elsewhere.

Well, it has to be somewhere else, otherwise, we end up with the DPI
detected by X or set in the conffile being overridden, which is not
really what one would expect.

> > The first one would need more input. As I understand it (but it's only
> > with my limited experience of it), X fallsback to 75dpi when it can't
> > correctly detect display size. Wouldn't changing this fallback value
> > to 96dpi be a much more pleasant solution ?
> 
>   It's a good idea (I would be in support of this for sure).  However,
> my experience supporting users on IRC is that it is rare that X gets
> this far.  Usually DDC provides some values, and X will end up
> calculating anything between 80 and 133 DPI.  If we're talking about
> patches for the X server, I would like to see it default to 96 DPI, and
> not use DDC unless explicitly requested in the config file.

Well, if the user gets something 80 and 133, i would say they probably
got the right value. So what is wrong ? Probably the user not being
accustomed to the fact that the dpi setting actually works.  I've myself
been using a 75dpi setting for a *long* time, going up to editing the
?dm file to use 75 instead of the 100 default value. And now I think
about it, that was due to the fact that in my opinion, the 75dpi xfonts
were much pleasant to my eye than the 100dpi xfonts. So what ? my old
habit of ancient non ttf antialiased fonts made me use for quite some
time some inaccurate setting. Then I got a clue and used the real dpi
value of my monitor.
My point is people are probably still used to old stuff, and can't just
realize that the new setting they have is the actual correct one.
The typical error is using font sizes they're used to, being something
in-between 11 an 13pt, while the one they really want would be 8 or 9pt.

>   I think it would be productive to get this changed there, and we could
> use this as a migration plan.  In the mean time, I still think the Xft
> DPI change is the right thing to do in Debian until we have an X server
> with these modifications.

I think except the default fallback value, there's nothing to change but
people habits.

Mike

Re: DPI, font size, and Debian

[Mike Hommey]

> I would not like to have my screen projected with 1/2 inch (or 1 cm or
> whatever galactic leagues) letters high. In fact, I do not want to know
> the dpi of my projector (which varies according to the distance between
> it and the wall, anyway).
> 
> So I would have to lie about the DPI of my projector, should it ever
> communicate with my X server. I certainly do not want fonts based on a
> resolution of 5-20 dpi (which is approximately what you get with a
> projector).
> 
> So what people want sometimes is measure in pixels (this is the case of
> the font/widget rendering, and the case when the screen is a projector),
> and sometimes points/cm/inches (this is the case of the graphics rendering).

Actually the projector issue is a different one. Nobody wants to use DPI
on a projector, for the simple reason there's no projector available
with a pixel density such that you could have a decent DPI setting on
it. I'm not even sure a projector advertizes its size screen.
I'd say people would want to use a projector as if it was a virtual
screen of , or even simpler, as a
projection of , thus using the already
configured DPI.

Mike

Re: DPI, font size, and Debian

[Mike Hommey]

On Mon, Dec 06, 2004 at 09:38:06AM -0600, Billy Biggs <[EMAIL PROTECTED]> wrote:
> [...]
>   I think that's fair enough, I mean, I think the font design problem is
> somewhat intractable and therefore you'll never get great-looking text
> at small pixel sizes, but we can happily diagree on this point.  I don't
> want to stop you from configuring your system this way.

Thanks for understanding my point of view

>   My priority is solving the practical problem we have today:  many
> Linux users by default are given systems with seemingly random DPI
> values, and they have to go configure all of their fonts.  Can we agree
> that this is a problem worth solving?  Standardizing the default DPI
> value at the Xft level rather than the X server level seems to have
> better consensus, so I think it is a good start.

I can only talk about my experience with X, but the only problems I got
were:
- badly detected screen size making the dpi to be a default 75dpi.
- dpi being forced in ?dm at 100dpi.

The second issue is obvious to solve: just stop to force the dpi this
way.
The first one would need more input. As I understand it (but it's only
with my limited experience of it), X fallsback to 75dpi when it can't
correctly detect display size. Wouldn't changing this fallback value to
96dpi be a much more pleasant solution ?

> [...]
>   My point was simply that there is a lot of practical evidence that
> this method works well, especially on the Mac which seems quite popular
> for desktop publishing.

Actually the Mac problem is that their quite ridiculous dpi setting is
used to justify their pretty bad LCD screens (as per pixel density)

>   The problem is that these display devices reduce the value of using
> the "real" DPI for UI rendering.

Actually, X seeded DPI being calculated from pixel size on display,
using XRandR to resize the display to the external display resolution
will bring a useable and probably expected result.

Mike

Re: DPI, font size, and Debian

[Mike Hommey]

On Mon, Dec 06, 2004 at 11:49:12PM +0900, Mike Hommey <[EMAIL PROTECTED]> wrote:
> >   2. Font hints are designed for specific font sizes at certain common
> >  DPIs.  There is value in using a small set of "standard" DPI values
> >  for UI rendering.   (see http://scanline.ca/dpi/fonts.html)
> 
> Then fix font hinting. While differences of 2 dpi seem to make an ugly
> difference, i'm pretty sure a difference of 10 does not.

Missing some text here.
If hinting was based on nearest good looking dpi, it could consider it
instead of real value.

Mike

Re: DPI, font size, and Debian

[Mike Hommey]

On Mon, Dec 06, 2004 at 08:26:38AM -0600, Billy Biggs <[EMAIL PROTECTED]> wrote:
>   1. Other operating systems do not use the screen's DPI when rendering
>  fonts.  On Windows, there is a different function to determine the
>  real DPI of the display, separate from the DPI used in text
>  rendering.  This seems to work well in practice.

It's not because other systems do stupid things that we must do the
same. With such way of thinking, we would end up with a huge amount of
crap.

>   2. Font hints are designed for specific font sizes at certain common
>  DPIs.  There is value in using a small set of "standard" DPI values
>  for UI rendering.   (see http://scanline.ca/dpi/fonts.html)

Then fix font hinting. While differences of 2 dpi seem to make an ugly
difference, i'm pretty sure a difference of 10 does not.

>   3. DPI becomes more complicated given different display devices such
>  as data projectors.

I don't see why. The only problem that could happen is that when
plugging in the new display, X doesn't know instantly that the dpi
changed.

>   Originally, I argued that both the DPI values from the X server and
> from Xft should be the same thing, and that this should be the
> "canonical DPI" used for UI rendering.  As many people have pointed out
> in this thread, there are other uses for the "real DPI", and furthermore
> there is some prior art in that these are two separate values on
> Windows.  So, by sticking to separately configured DPI values with Xft
> makes sense, as does choosing a default canonical value of 96 DPI.

And all I see is that you want to copy what sucks in windows about dpi
handling.

Mike

Re: DPI, font size, and Debian

[Mike Hommey]

On Mon, Dec 06, 2004 at 12:17:27PM +, Anders Karlsson <[EMAIL PROTECTED]> 
wrote:
> > I still fail to see the advantage of having 2 settings of the same
> > thing, being the number of dots per inch.
> 
> Golden middle way then, if the X DPI is specified manually in the
> XF86Config, the Xft.dpi gets set to what X DPI is set to. If X is
> guessing the DPI, Xft.dpi gets defaulted to 96 dpi?

And what if X is guessing correct (which is likely to happen more and
more) ?

Mike

Re: DPI, font size, and Debian

[Mike Hommey]

On Mon, Dec 06, 2004 at 11:23:48AM +, Anders Karlsson <[EMAIL PROTECTED]> 
wrote:
> Well, yes and no. If you are a normal user, you would not have to tweak
> anything. If you mess with printing/image manipulating a lot, then you
> might have to tweak two sets of values, one to tell X what DPI the
> screen actually is, and one to tell the desktop env what DPI you want
> the fonts displayed in.

I still fail to see the advantage of having 2 settings of the same
thing, being the number of dots per inch.

Mike

Re: DPI, font size, and Debian

[Mike Hommey]

On Mon, Dec 06, 2004 at 12:58:30AM -0800, Keith Packard <[EMAIL PROTECTED]> 
wrote:
> 
> Around 8 o'clock on Dec 6, Anders Karlsson wrote:
> 
> > No, he said he wanted to make Xft applications default to 96 DPI.
> > Nothing stopping you from tweaking the Xft.dpi value to what you want it
> > to be.
> 
> So should Xft just default to 96dpi and let the Xft.dpi value override 
> that?  Right now, Xft defaults to the "real" display resolution, which I 
> think we've come to see as almost always the wrong answer (at least as a 
> default).

The problem lies in the Xserver not having the correct DPI set.
Let's not try to fix that by breaking the cases where the Xserver has
the actual DPI.

Mike

Re: DPI, font size, and Debian

[Mike Hommey]

On Mon, Dec 06, 2004 at 08:52:57AM +, Anders Karlsson <[EMAIL PROTECTED]> 
wrote:
> On Mon, 2004-12-06 at 16:20 +0900, Mike Hommey wrote:
> > On Sun, Dec 05, 2004 at 09:19:25PM -0600, Billy Biggs <[EMAIL PROTECTED]> 
> > wrote:
> > >   The GNOME system has the nice property that it can be changed without
> > > restarting X.  Moving towards systems with this property is a good
> > > thing.  GNOME also advertises it in a vendor neutral way (XSETTINGS) and
> > > sets the Xft X resource so that other applications use its DPI value, so
> > > it seems like it is going in the right direction.
> > > 
> > >   Regardless, my proposal is simply to have Xft always default to 96
> > > DPI, independent of the DPI value you put in X.
> > 
> > Are you telling me you are wanting to force all my Xft applications to
> > use a 96 dpi display while I explicitly configured X to use 112 dpi ?
> > I firmly oppose to that.
> 
> No, he said he wanted to make Xft applications default to 96 DPI.
> Nothing stopping you from tweaking the Xft.dpi value to what you want it
> to be.

Which means I'll have to tweak *2* configurations for *1* DPI. And
fortunately, I don't use several user accounts, otherwise that would be
even more configuration tweaks.

Mike

Re: DPI, font size, and Debian

[Mike Hommey]

On Mon, Dec 06, 2004 at 07:26:24AM +0100, Jean-Christophe Dubacq <[EMAIL 
PROTECTED]> wrote:
> However, Keith's computation is a bit hard: I tested 120 dpi with my
> 1600x1200 and already find those fonts are gigantic. I would not like
> staying with 150.

Probably because you're using 12 or 13 points sized fonts while you
should be using 8 or 9 points.

> By the way, I cannot make sense of the font sizes in firefox. Looks like
> it uses 75 dpi or 72 dpi as a reference.

Yup, roughly. They decided to use a pixel value, and one that is quite
low for dense screens.

Mike

Re: DPI, font size, and Debian

[Mike Hommey]

On Sun, Dec 05, 2004 at 09:19:25PM -0600, Billy Biggs <[EMAIL PROTECTED]> wrote:
>   The GNOME system has the nice property that it can be changed without
> restarting X.  Moving towards systems with this property is a good
> thing.  GNOME also advertises it in a vendor neutral way (XSETTINGS) and
> sets the Xft X resource so that other applications use its DPI value, so
> it seems like it is going in the right direction.
> 
>   Regardless, my proposal is simply to have Xft always default to 96
> DPI, independent of the DPI value you put in X.

Are you telling me you are wanting to force all my Xft applications to
use a 96 dpi display while I explicitly configured X to use 112 dpi ?
I firmly oppose to that.

Mike

Re: DPI, font size, and Debian

[Mike Hommey]

On Sun, Dec 05, 2004 at 08:55:17PM -0600, Billy Biggs <[EMAIL PROTECTED]> wrote:
>   I discussed this issue further and updated my proposal.  Given that
> many people do believe that a measure of the "real" DPI is a useful
> thing to keep around, and that all font rendering systems seem to honour
> the Xft.dpi value, at least if we can get this set everywhere to a
> standard nominal value of 96.0 I think we will be ahead:
> 
> http://scanline.ca/dpi/

I would personnally add something: make gnome NOT use its default 96dpi,
but what the X server gives it. It's annoying to have to put gnome at
the real dpi we already took time to put in X.

Mike

Bug#280696: [xkb] jp106 windows key has no symbol

[Mike Hommey]

On Mon, Nov 22, 2004 at 09:22:57PM +0100, Denis Barbier <[EMAIL PROTECTED]> 
wrote:
>   http://people.debian.org/~barbier/xkb/xkb-4.3.0.dfsg.1-8+SVN.tar.bz2

Sorry about the delay, I confirm it works with the xkb tree from this
tarball, so I guess it will be fixed in 4.3.0.dfsg.1-9...

Thanks

Mike

Bug#280696: [xkb] jp106 windows key has no symbol

[Mike Hommey]

On Sun, Nov 21, 2004 at 04:06:22PM +0100, Denis Barbier wrote:
> On Sat, Nov 13, 2004 at 11:52:30AM +0900, Mike Hommey wrote:
> [...]
> > [EMAIL PROTECTED]:/tmp$ wget 
> > http://ftp.jp.debian.org/debian/pool/main/x/xfree86/xlibs_4.3.0.dfsg.1-8_all.deb
> > [EMAIL PROTECTED]:/tmp$ md5sum xlibs_4.3.0.dfsg.1-8_all.deb
> > 8a5d7cce95cf8db88520849ac18666bf  xlibs_4.3.0.dfsg.1-8_all.deb
> > [EMAIL PROTECTED]:/tmp$ dpkg-deb -x xlibs_4.3.0.dfsg.1-8_all.deb xlibs
> > makemono:/tmp$ diff -ruN /etc/X11/xkb /tmp/xlibs/etc/X11/xkb
> > Binary files /etc/X11/xkb/xkbcomp and /tmp/xlibs/etc/X11/xkb/xkbcomp differ
> > [EMAIL PROTECTED]:/tmp$ LANG=C ls -l /tmp/xlibs/etc/X11/xkb/xkbcomp
> > ls: /tmp/xlibs/etc/X11/xkb/xkbcomp: No such file or directory
> > [EMAIL PROTECTED]:/tmp$ ls -l /etc/X11/xkb/xkbcomp
> > lrwxrwxrwx  1 root root 22 2004-09-29 17:24 /etc/X11/xkb/xkbcomp -> 
> > /usr/X11R6/bin/xkbcomp
> 
> And if you try
>   $ cd /tmp/xlibs/etc/X11/xkb
>   $ setxkbmap -model jp106 -layout jp -option compose:menu -print
> do you have the same output?
> ... xkb_symbols   { include "jp+compose(menu)"  };

yes i do.

Mike

Bug#280696: [xkb] jp106 windows key has no symbol

[Mike Hommey]

On Fri, Nov 12, 2004 at 09:35:50PM +0100, Denis Barbier wrote:
> On Sat, Nov 13, 2004 at 01:54:50AM +0900, Mike Hommey wrote:
> > I haven't tested your fix yet, but what i can tell you is that my
> > /etc/X11/xkb/rules/xfree86 file is the exact same as the one in the
> > xlibs_4.3.0.dfsg.1-8_all.deb archive (extracted with dpkg-deb and
> > diff'ed)
> 
> The command below displays either (a) or (b):
>   $ setxkbmap -model jp106 -layout jp -option -option compose:menu -print
>   xkb_keymap {
> xkb_keycodes  { include "xfree86+aliases(qwerty)"   };
> xkb_types { include "complete"  };
> xkb_compat{ include "complete"  };
>  (a)xkb_symbols   { include 
> "pc/pc(pc102)+pc/jp(latin)+pc/jp:2+compose(menu)" };
>  (b)xkb_symbols   { include "jp+compose(menu)"   };
> xkb_geometry  { include "pc(jp106)" };
>   };
> If (a) is displayed, this means that a program redefines your keyboard
> layout after X has been launched.
> 
> If (b) is displayed, check that 
>   1. setxkbmap is /usr/bin/X11/setxkbmap.
>   2. /usr/X11R6/lib/X11/xkb is a symlink to /etc/X11/xkb
> If both are right, please send me an archive with your whole /etc/X11/xkb
> directory.

[EMAIL PROTECTED]:~$ setxkbmap -model jp106 -layout jp -option compose:menu 
-print
xkb_keymap {
xkb_keycodes  { include "xfree86+aliases(qwerty)"   };
xkb_types { include "complete"  };
xkb_compat{ include "complete"  };
xkb_symbols   { include "jp+compose(menu)"  };
xkb_geometry  { include "pc(jp106)" };
};
[EMAIL PROTECTED]:~$ which setxkbmap
/usr/bin/X11/setxkbmap
[EMAIL PROTECTED]:~$ ls -l /usr/X11R6/lib/X11/xkb
lrwxrwxrwx  1 root root 12 2004-09-29 17:23 /usr/X11R6/lib/X11/xkb -> 
/etc/X11/xkb

As for /etc/X11/xkb:
[EMAIL PROTECTED]:/tmp$ wget 
http://ftp.jp.debian.org/debian/pool/main/x/xfree86/xlibs_4.3.0.dfsg.1-8_all.deb
[EMAIL PROTECTED]:/tmp$ md5sum xlibs_4.3.0.dfsg.1-8_all.deb
8a5d7cce95cf8db88520849ac18666bf  xlibs_4.3.0.dfsg.1-8_all.deb
[EMAIL PROTECTED]:/tmp$ dpkg-deb -x xlibs_4.3.0.dfsg.1-8_all.deb xlibs
makemono:/tmp$ diff -ruN /etc/X11/xkb /tmp/xlibs/etc/X11/xkb
Binary files /etc/X11/xkb/xkbcomp and /tmp/xlibs/etc/X11/xkb/xkbcomp differ
[EMAIL PROTECTED]:/tmp$ LANG=C ls -l /tmp/xlibs/etc/X11/xkb/xkbcomp
ls: /tmp/xlibs/etc/X11/xkb/xkbcomp: No such file or directory
[EMAIL PROTECTED]:/tmp$ ls -l /etc/X11/xkb/xkbcomp
lrwxrwxrwx  1 root root 22 2004-09-29 17:24 /etc/X11/xkb/xkbcomp -> 
/usr/X11R6/bin/xkbcomp

Mike

Bug#280696: [xkb] jp106 windows key has no symbol

[Mike Hommey]

On Fri, Nov 12, 2004 at 11:05:22AM +0100, Denis Barbier wrote:
> On Fri, Nov 12, 2004 at 06:27:17PM +0900, Mike Hommey wrote:
> > > BTW please run
> > >   $ xkbcomp :0
> > > and send the 'server-0.xkb' file generated by this command.
> > 
> > Attached to this mail.
> [...]
> > xkb_symbols "jp+compose(menu)" {
> 
> Here is the culprit, it should be
>   xkb_symbols "pc/pc(pc102)+pc/jp(latin)+pc/jp:2+compose(menu)" {
> 
> My /etc/X11/xkb/rules/xfree86 contains (but I do not remember if I
> modified it):
>   * jp  =   pc/pc(pc102)+pc/jp(latin)+pc/jp:2
> 
> I have no more time to investigate just now, but you can try with
> files from
>  http://people.debian.org/~barbier/xkb/xkb-4.3.0.dfsg.1-8+SVN.tar.bz2

I haven't tested your fix yet, but what i can tell you is that my
/etc/X11/xkb/rules/xfree86 file is the exact same as the one in the
xlibs_4.3.0.dfsg.1-8_all.deb archive (extracted with dpkg-deb and
diff'ed)

Mike

Bug#280696: [xkb] jp106 windows key has no symbol

[Mike Hommey]

On Fri, Nov 12, 2004 at 10:09:48AM +0100, Denis Barbier wrote:
> On Fri, Nov 12, 2004 at 11:08:02AM +0900, Mike Hommey wrote:
> [...]
> > Just in case that would change some things, my keyboard is a laptop one
> > and the non working windows key is the left one (there is no right
> > windows key on laptops).
> 
> As you get the right keycode, it seems to me that the keycode <-> keysym
> mapping is in trouble, but that's strange.  Did you hear of other users
> having the same problem?

I heard someone complaining about the same issue on #debian-devel-fr.
I can't remember who exactly, though.

> BTW please run
>   $ xkbcomp :0
> and send the 'server-0.xkb' file generated by this command.

Attached to this mail.

Mike
xkb_keymap {
xkb_keycodes "xfree86+aliases(qwerty)" {
minimum = 8;
maximum = 255;
  = 9;
 = 10;
 = 11;
 = 12;
 = 13;
 = 14;
 = 15;
 = 16;
 = 17;
 = 18;
 = 19;
 = 20;
 = 21;
 = 22;
  = 23;
 = 24;
 = 25;
 = 26;
 = 27;
 = 28;
 = 29;
 = 30;
 = 31;
 = 32;
 = 33;
 = 34;
 = 35;
 = 36;
 = 37;
 = 38;
 = 39;
 = 40;
 = 41;
 = 42;
 = 43;
 = 44;
 = 45;
 = 46;
 = 47;
 = 48;
 = 49;
 = 50;
 = 51;
 = 52;
 = 53;
 = 54;
 = 55;
 = 56;
 = 57;
 = 58;
 = 59;
 = 60;
 = 61;
 = 62;
 = 63;
 = 64;
 = 65;
 = 66;
 = 67;
 = 68;
 = 69;
 = 70;
 = 71;
 = 72;
 = 73;
 = 74;
 = 75;
 = 76;
 = 77;
 = 78;
  = 79;
  = 80;
  = 81;
 = 82;
  = 83;
  = 84;
  = 85;
 = 86;
  = 87;
  = 88;
  = 89;
  = 90;
 = 91;
 = 92;
 = 93;
 = 94;
 = 95;
 = 96;
 = 97;
   = 98;
 = 99;
 = 100;
 = 102;
  = 103;
 = 104;
 = 105;
  = 106;
 = 107;
 = 108;
 = 109;
 = 110;
 = 111;
 = 112;
 = 113;
  = 114;
 = 115;
 = 116;
 = 117;
 = 118;
 = 119;
 = 120;
 = 121;
 = 122;
 = 123;
 = 124;
  = 125;
 = 126;
 = 127;
 = 128;
 = 129;
  = 130;
 = 131;
  = 132;
 = 133;
  = 134;
  = 135;
  = 136;
  = 137;
  = 138;
  = 139;
  = 140;
  = 141;
  = 142;
  = 143;
  = 144;
  = 145;
  = 146;
  = 147;
  = 148;
  = 149;
  = 150;
  = 151;
  = 152;
  = 153;
  = 154;
  = 155;
 = 156;
  = 158;
  = 159;
  = 160;
  = 161;
  = 162;
  = 163;
  = 164;
  = 165;
  = 166;
  = 167;
  = 168;
  = 169;
  = 171;
  = 172;
  = 173;
  = 174;
  = 175;
  = 176;
  = 177;
  = 178;
  = 179;
  = 180;
  = 185;
  = 186;
  = 187;
  = 188;
  = 194;
  = 195;
  = 196;
  = 197;
  = 202;
  = 212;
  = 213;
  = 214;
  = 215;
  = 216;
  = 217;
  = 218;
  = 222;
  = 223;
  = 224;
  = 225;
  = 226;
  = 227;
  = 228;
  = 229;
  = 230;
  = 231;
  = 232;
  = 233;
  = 234;
  = 235;
  = 236;
  = 237;
  = 238;
  = 239;
  = 240;
  = 241;
  = 242;
  = 243;
  = 244;
  = 245;
  = 246;
  = 247;
  = 248;
  = 249;
  = 250;
  = 251;
  = 252;
  = 253;
  = 254;
  = 255;
indicator 1 = "Caps Lock";
indicator 2 = "Num Lock";
indicator 3 = "Scroll Lock";
virtual indicator 4 = "Shift Lock";
virtual indicator 5 = "Group 2";
virtual indicator 6 = "Mouse Keys";
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias   = ;
alias   = ;
alias   = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
alias  = ;
};

xkb_types "complete" {

virtual_modifiers NumLock,Alt,LevelThree,AltGr,Meta,Super,Hyper,ScrollLock;

type "ONE_LEVEL" {
modifiers= none;
level_name[Level1]= "Any";
};
type "TWO_LEVEL" {
modifiers= Shift;
map[Shift]= Level2;
level_name[Level1]= "Base";
level_name[Level2]= "Shift";
};
type "ALPHABETIC" {
modifiers= Shift+Lock;
map[Shift]= Level2;
map[Lock]= Level1;
preserve[Lock]= Lock;
level_name[Level1]= "Base";
level_name[Level2]= "Caps";
};
  

Bug#280696: [xkb] jp106 windows key has no symbol

[Mike Hommey]

On Fri, Nov 12, 2004 at 12:19:57AM +0100, Denis Barbier wrote:
> tags 280696 + unreproducible
> thanks
> 
> On Thu, Nov 11, 2004 at 11:42:15AM +0900, Mike Hommey wrote:
> > Package: xlibs-data
> > Version: 4.3.0.dfsg.1-8
> > 
> > On Wed, Nov 10, 2004 at 10:21:22PM +0100, Denis Barbier wrote:
> > > On Wed, Nov 10, 2004 at 07:49:41PM +0900, Mike Hommey wrote:
> > > [...]
> > > > Note that on the same keyboard, The windows key gives keycode 115
> > > > (keysym 0x0, NoSymbol), which i think is not expected. Shall I file a
> > > > new bug for that ?
> > > 
> > > Yes please, and send the output of the following command:
> > >   xprop -root | grep XKB
> > 
> > _XKB_RULES_NAMES_BACKUP(STRING) = "xfree86", "jp106", "jp", "", 
> > "compose:menu"
> > _XKB_RULES_NAMES(STRING) = "xfree86", "jp106", "jp", "", "compose:menu"
> 
> I cannot reproduce your problem here with the same settings.
> Please check that you did not modify XKB files (they are configuration
> files and thus not upgraded if you modify them) under /etc/X11/xkb/
> and that you do not run xmodmap commands.

I do not.

Just in case that would change some things, my keyboard is a laptop one
and the non working windows key is the left one (there is no right
windows key on laptops).

Mike

Bug#280696: [xkb] jp106 windows key has no symbol

[Mike Hommey]

Package: xlibs-data
Version: 4.3.0.dfsg.1-8

On Wed, Nov 10, 2004 at 10:21:22PM +0100, Denis Barbier wrote:
> On Wed, Nov 10, 2004 at 07:49:41PM +0900, Mike Hommey wrote:
> [...]
> > Note that on the same keyboard, The windows key gives keycode 115
> > (keysym 0x0, NoSymbol), which i think is not expected. Shall I file a
> > new bug for that ?
> 
> Yes please, and send the output of the following command:
>   xprop -root | grep XKB

_XKB_RULES_NAMES_BACKUP(STRING) = "xfree86", "jp106", "jp", "", "compose:menu"
_XKB_RULES_NAMES(STRING) = "xfree86", "jp106", "jp", "", "compose:menu"

Mike

Bug#280579: xlibs-data: [xkb] jp106 backslash/yen issue

[Mike Hommey]

Package: xlibs-data
Version: 4.3.0.dfsg.1-8
Severity: minor

On a japanese keyboard, there is one key of the Yen sign, and one for
the backslash. While in EUC-JP and SHIFT-JIS encoding, Yen and backslash
are mapped to the same character, it is not the case in UTF-8.
Thus, i'd like the Yen key to return a Yen character, not a backslash.

Keycode for the yen key: keycode 133 (keysym 0x5c, backslash)
Keycode for the backslash key: keycode 123 (keysym 0x5c, backslash)

Mike

Note that on the same keyboard, The windows key gives keycode 115
(keysym 0x0, NoSymbol), which i think is not expected. Shall I file a
new bug for that ?


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-1-686
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)

-- no debconf information

Re: Bug#268120: Adpot Windows conventions for producing International Characters

[Mike Hommey]

On Thu, Aug 26, 2004 at 10:13:10PM +0100, TJ wrote:
(...)
> How to use compose?
> well to get a "ä" (a umlaut) 
> press compose (right win)(and release, not hold) then press "
> (shift+2 on uk keyboards) then press a.
> compose will combine the " and a to give you ä
> also: compose then s then s, gives you ß (German ss)
> or: compose then o then c, gives © (copyright char)
> 
> all composes are compose then two chars, try it.

The problem is that in some locales... compose key has no effect. See
#264557

Mike

Bug#234556: Possible Transmeta CMS bug

[Mike Hommey]

On Thu, Aug 19, 2004 at 10:47:06AM +0200, Emmanuel Fleury wrote:
> Hi,
> 
> I just write here a quick update of the bug to tell you the state of the
> process.
(...)

I'm impressed with the amount of energy you've put into tracking this
bug, but you should have read history of the bugs merged with yours...
Especially
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=216933&msg=63

Mike

Bug#264557: xlibs-data: No composition sequences in japanese locale

[Mike Hommey]

Package: xlibs-data
Version: 4.3.0.dfsg.1-6
Severity: wishlist

Hi,

First, I'm not quite sure if the bug belongs to xlibs-data, so please
reassign if I am wrong.

All "basic" X applications using xlibs (tested with xedit and emacs)
fail to get composition sequences when using the ja_JP.UTF-8 locale.
Interestingly, I get some strange behaviours as well, which might be
related to gnome configurations but I'm not quite sure.

Anyway, what I tried is the following (all with a fresh new account ;
gnome is the default session if i launch startx ; LANG in
/etc/environment is en_US.UTF-8; gnome is configured to have Compose key
on Menu (laptops don't have a right windows key)):
(ok means composition sequences work properly, ko means the contrary)
startx -> emacs -> ok
startx -> LANG=ja_JP.UTF-8 -> ko
LANG=ja_JP.UTF-8 -> emacs -> ko
LANG=ja_JP.UTF-8 -> LANG=en_US.UTF-8 emacs -> ok

The strange behaviour is that with my not fresh account, the one I use
in every day life, the latter has a ko result.

Anyway, I'd like to be able to type french accents in my japanese
environement without having to play with locales ;)

Note that copying /usr/X11R6/lib/X11/locale/en_US.UTF-8/Compose into
/usr/X11R6/lib/X11/locale/ja_JP.UTF-8/ doesn't do the trick (the absence
of the file let me think that would be a solution)

Mike

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.22-mh
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8

-- no debconf information

Bug#228494: 1400x1050

[Mike Hommey]

On Wednesday January 28 2004 02:56, Branden Robinson wrote:
> Do you ever run X at color depth 24?

xdpyinfo says so...

Mike

Bug#228494: 1400x1050

[Mike Hommey]

On Tuesday January 20 2004 15:34, Xavier Bestel wrote:
> Le lun 19/01/2004 à 12:15, Harald Dunkel a écrit :
> > Is there a chance to get it included as an official
> > timing in the ati driver, and in the debconf installation
> > menu?
>
> The ati driver is buggy at 1400x1050: XVideo doesn't work.
> (note that the driver from gatos.sf.net works fine)
>
>   Xav

Never add any problem, with xfree86 4.2.1 ou 4.3 with the ati driver, a Radeon 
Mobility M6 LY on 1400x1050, and Xv display... (except for dual-head related 
stuff and Xv overlay beeing always on top, which are fixed in 4.3)

Mike

Bug#220493: So why is Debian's XFree86 old?....

[Mike Hommey]

On Thursday November 13 2003 17:06, Daniel Stone wrote:
> Yes. Splitting xlibs/xbase-clients, breaking the xlibs build out so you
> can choose to use the freedesktop.org versions ... none of this is
> particularly easy.

Speaking of which there will be a package naming issue at some point, since 
the X11 Server from freedesktop.org is called xserver...

Mike

Re: report error install lindows4 into vmware 3.2

[Mike Hommey]

On Wednesday October 29 2003 05:00, Branden Robinson wrote:
> I'm sorry, but I do not think I can be of much assistance:
>
> 1) You have reached the Debian Project, not Lindows.com.  You will need
> to contact Lindows Customer Support for assistance with their products,
> such as Lindows 4.
>
> 2) Please use a different image format, such as .gif or .png, when
> attaching screenshots that include text.  The JPEG format is very bad
> for displaying text.

3) Ask Lindows to change [EMAIL PROTECTED] address in the xfree packages to 
another address. Jose is not the first and won't be the last to just do what 
he is proposed to do by the server crash message.

Mike

-- 
"I have sampled every language, french is my favorite. Fantastic language,
especially to curse with. Nom de dieu de putain de bordel de merde de
saloperie de connard d'enculé de ta mère. It's like wiping your ass
with silk! I love it." -- The Merovingian, in the Matrix Reloaded


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: libxcursor-dev version 1.0.2-2 problem

[Mike Hommey]

On Monday 15 September 2003 00:37, Daniel Stone wrote:
> You'll either need to use --force-overwrite, or get the pre1v1 packages.

... or dpkg-divert.

Mike
-- 
"I have sampled every language, french is my favorite. Fantastic language,
especially to curse with. Nom de dieu de putain de bordel de merde de
saloperie de connard d'enculé de ta mère. It's like wiping your ass
with silk! I love it." -- The Merovingian, in the Matrix Reloaded

Re: libxcursor-dev version 1.0.2-2 problem

[Mike Hommey]

On Monday 15 September 2003 00:37, Daniel Stone wrote:
> You'll either need to use --force-overwrite, or get the pre1v1 packages.

... or dpkg-divert.

Mike
-- 
"I have sampled every language, french is my favorite. Fantastic language,
especially to curse with. Nom de dieu de putain de bordel de merde de
saloperie de connard d'enculé de ta mère. It's like wiping your ass
with silk! I love it." -- The Merovingian, in the Matrix Reloaded


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#167887: Is there a chance to see 1400x1050 resolution ?

[Mike Hommey]

Is there a chance to see 1400x1050 resolution in debconf templates in upcoming 
4.3.0 packages ?

Regards

Mike

Bug#167887: Is there a chance to see 1400x1050 resolution ?

[Mike Hommey]

Is there a chance to see 1400x1050 resolution in debconf templates in upcoming 
4.3.0 packages ?

Regards

Mike




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]