Bug#442879: patch

[Greg Best Olszewski]

Here's the patch I used to get it working again.


diff -u -p 
/home/gno/.emacs.backup/\!home\!gno\!xorg-7.3\+10\!debian\!local\!xserver-wrapper.c\~
 /home/gno/xorg-7.3\+10/debian/local/xserver-wrapper.c
--- 
/home/gno/.emacs.backup/!home!gno!xorg-7.3+10!debian!local!xserver-wrapper.c~   
 2007-12-03 20:52:57.0 -0800
+++ /home/gno/xorg-7.3+10/debian/local/xserver-wrapper.c
 2008-03-14 23:23:10.0 -0700
@@ -324,10 +324,14 @@ main(int argc, char **argv)
 
 for (i = 1; i < argc; i++) {
   if (!strcmp(argv[i], "-config") || !strcmp(argv[i], "-xf86config")) {
-if (setuid(getuid())) {
-  perror("X unable to drop setuid privileges for alternate config");
-  exit(1);
-}
+if (i+1 > argc
+|| strstr(argv[i+1],"Xwrapper.config")
+|| strstr(argv[i+1],"..")) {
+  if (setuid(getuid())) {
+perror("X unable to drop setuid privileges for alternate config");
+exit(1);
+  }
+} 
   } else if (strlen(argv[i]) > 256) {
 if (setuid(getuid())) {
   perror("X unable to drop setuid privileges for suspiciously long "





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

Bug#471019: libgl1-mesa-glx: segfaults in glGetString(GL_EXTENSIONS) on amd64 when there is no GL context

[Paul Wise]

Package: libgl1-mesa-glx
Version: 7.0.3~rc2-1
Severity: normal

On amd64, the attached C program segfaults in glGetString()
in /usr/lib/libGL.so.1, but on i386 it simply prints "(nil) 0.00". 

This causes #439973 - boson segfaults before startup on amd64.

--
[EMAIL PROTECTED]:~/tmp$ gcc -o foo foo.c -lGL
[EMAIL PROTECTED]:~/tmp$ gcc -o foo foo.c -lGL
[EMAIL PROTECTED]:~/tmp$ ./foo 
(nil) 0.00
[EMAIL PROTECTED]:~/tmp$ dpkg-architecture 
DEB_BUILD_ARCH=i386
DEB_BUILD_ARCH_OS=linux
DEB_BUILD_ARCH_CPU=i386
DEB_BUILD_GNU_CPU=i486
DEB_BUILD_GNU_SYSTEM=linux-gnu
DEB_BUILD_GNU_TYPE=i486-linux-gnu
DEB_HOST_ARCH=i386
DEB_HOST_ARCH_OS=linux
DEB_HOST_ARCH_CPU=i386
DEB_HOST_GNU_CPU=i486
DEB_HOST_GNU_SYSTEM=linux-gnu
DEB_HOST_GNU_TYPE=i486-linux-gnu
--
(sid_amd64)[EMAIL PROTECTED]:~$ dpkg -s libgl1-mesa-glx | grep Version
Version: 7.0.3~rc2-1
(sid_amd64)[EMAIL PROTECTED]:~$ gcc -o foo foo.c -lGL -g
(sid_amd64)[EMAIL PROTECTED]:~$ ./foo 
Segmentation fault
(sid_amd64)[EMAIL PROTECTED]:~$ gdb foo
GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) r
Starting program: /home/pabs/foo 
[Thread debugging using libthread_db enabled]
[New Thread 0x2ac40d813570 (LWP 447)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x2ac40d813570 (LWP 447)]
0x2ac40c1b79f7 in glGetString () from /usr/lib/libGL.so.1
(gdb) bt full
#0  0x2ac40c1b79f7 in glGetString () from /usr/lib/libGL.so.1
No symbol table info available.
#1  0x00400611 in main (argc=1, argv=0x7fff9eb63408) at foo.c:8
extensions = (const GLubyte *) 0x0
--

-- 
bye,
pabs

http://wiki.debian.org/PaulWise
#include 
#include 

int
main (int argc, char **argv)
{
	const GLubyte* extensions = glGetString(GL_EXTENSIONS);
	printf("%p %f\n",extensions);
	return 0;
}


signature.asc
Description: This is a digitally signed message part

Processed: Re: Bug#439237: xserver-xorg-input-mouse: the mouse disappear when it goes on the 10cm of the left vertical track of the screen

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> forwarded 439237 https://bugs.freedesktop.org/show_bug.cgi?id=15024
Bug#439237: xserver-xorg-input-mouse: the mouse disappear when it goes on the 
10cm of the left vertical track of the screen
Noted your statement that Bug has been forwarded to 
https://bugs.freedesktop.org/show_bug.cgi?id=15024.

> thank you
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#439237: xserver-xorg-input-mouse: the mouse disappear when it goes on the 10cm of the left vertical track of the screen

[Brice Goglin]

forwarded 439237 https://bugs.freedesktop.org/show_bug.cgi?id=15024
thank you



I have forwarded the original sis problem at the URL above, feel free to
add comments there.

Brice




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

Bug#442240: /usr/bin/dexconf: writes incorrect refresh rates into xorg.conf

[Brice Goglin]

Debian Live user wrote:
> Package: x11-common
> Version: 1:7.2-5
> Severity: normal
> File: /usr/bin/dexconf
>
>
> The LCD panel is detected correctly as shown in the log, and the default
> mode is the native resolution @60Hz.
>
> However, modes forg lower resolutions @85Hz are also selected, and they
> are used for fullscreen applications (specifically dosemu). The panel
> works correctly only with 60-75Hz modes. 
>
> Removing the refresh rates from the config file solves the problem.
> (II) NV(0): Probing for EDID on I2C bus A...
> (II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
> (II) NV(0): I2C device "DDC:ddc2" removed.
> (--) NV(0): DDC detected a CRT:
> (II) NV(0): Manufacturer: ENC  Model: 1643  Serial#: 0
> (II) NV(0): Year: 2002  Week: 12
> (II) NV(0): EDID Version: 1.2
> (II) NV(0): Analog Display Input,  Input Voltage Level: 0.700/0.700 V
> (II) NV(0): Sync:  Separate
> (II) NV(0): Max H-Image Size [cm]: horiz.: 32  vert.: 25
> (II) NV(0): Gamma: 2.20
> (II) NV(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
> (II) NV(0): First detailed timing is preferred mode
> (II) NV(0): redX: 0.639 redY: 0.340   greenX: 0.280 greenY: 0.602
> (II) NV(0): blueX: 0.143 blueY: 0.087   whiteX: 0.303 whiteY: 0.319
> (II) NV(0): Supported VESA Video Modes:
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
> (II) NV(0): [EMAIL PROTECTED]
>   

EDID seems to be confirming that no 85Hz modeline is supported.

Can you try a more recent Xorg?
I have a rebuild of the 2.1.7 driver for testing available in
http://people.debian.org/~bgoglin/rebuilds/nv-2.1.7-Xserver1.3/
But it would be better to just upgrade your Xorg to unstable. RandR 1.2
probing may be better there, and the modes could be better chosen.

Brice




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

Bug#428091: Display has wrong colours and is offset

[Brice Goglin]

Andrew Ruthven wrote:
> Hi,
>
> Interestingy enough if my monitor is turned off then X starts up okay.
> I'm guessing because there is no DDC data to fetch, so X doesn't try and
> be clever about the modelines.
>
> I've attached the logfile for a working X session (the one I'm currently
> using).
>
> I'll try and investigate this further, but in the meantime I'll just
> leave my monitor off for a few minutes when I turn my computer on!
>
> There are some oddities with the left button on my mouse, but that is a
> different bug report.
>   

Does this problem still apply with today xserver-xorg-core and
xserver-xorg-video-mga from unstable? If so, can you send the
corresponding config and log? I will forward the bug upstream.

Brice




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

Bug#400632: x11-common: should not ship a SUID root binary

[Steve Langasek]

On Fri, Mar 14, 2008 at 11:42:41AM +0100, Julien Cristau wrote:
> On Mon, Feb  4, 2008 at 21:02:01 -0800, Steve Langasek wrote:

> > The problem is not that /usr/bin/X is suid-root.  The problem is that
> > /usr/bin/X is now shipped in a package which is a dependency of *all* of the
> > X libraries, so you can no longer have a system with X clients only without
> > pulling in an extra suid binary you don't need.

> I can't see the reason why the X libraries (Pre-)Depend on x11-common.
> AFAICT the Pre-Dependency is needed for packages installing stuff in
> /usr/include/X11 and /usr/lib/X11 to ensure that they are proper
> directories and not symlinks to /usr/X11R6.  That doesn't apply to
> libx11-6 and friends.

That's fine with me if it can be resolved that way.  I can't recall now any
reason for the runtime library packages to need this pre-depends, but it
seems reasonable to drop it at this point regardless.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]



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

Bug#471019: libgl1-mesa-glx: segfaults in glGetString(GL_EXTENSIONS) on amd64 when there is no GL context

[Brice Goglin]

Paul Wise wrote:
> Package: libgl1-mesa-glx
> Version: 7.0.3~rc2-1
> Severity: normal
>
> On amd64, the attached C program segfaults in glGetString()
> in /usr/lib/libGL.so.1, but on i386 it simply prints "(nil) 0.00". 
>   

Can you get a better backtrace with libgl1-mesa-glx-dbg installed?

Thanks,
Brice

Bug#463567: xkb changes crash X11

[Michael Olbrich]

Xephyr is affected as well (version 2:1.4.1~git20080131-2).
At least I think it's the same bug.

"setxkbmap -model microsoftpro" will crash Xephyr
"setxkbmap -model pc104" is fine.

unfortunately the backtrace produced by gdb us useless.




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

Bug#471019: libgl1-mesa-glx: segfaults in glGetString(GL_EXTENSIONS) on amd64 when there is no GL context

[Paul Wise]

On Sat, 2008-03-15 at 10:15 +0100, Brice Goglin wrote:

> Can you get a better backtrace with libgl1-mesa-glx-dbg installed?

(gdb) r
Starting program: /home/pabs/foo 
[Thread debugging using libthread_db enabled]
[New Thread 0x2b8f57a9ab80 (LWP 3428)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x2b8f57a9ab80 (LWP 3428)]
glGetString () at ../../../src/mesa/x86-64/glapi_x86-64.S:9876
9876../../../src/mesa/x86-64/glapi_x86-64.S: No such file or
directory.
in ../../../src/mesa/x86-64/glapi_x86-64.S
Current language:  auto; currently asm
(gdb) bt full
#0  glGetString () at ../../../src/mesa/x86-64/glapi_x86-64.S:9876
No locals.
#1  0x00400611 in main (argc=1, argv=0x7fff548dc088) at foo.c:7
extensions = (const GLubyte *) 0x0
(gdb) quit
The program is running.  Exit anyway? (y or n) y

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#463567: xkb changes crash X11

[Michael Olbrich]

When running "setxkbmap -model microsoftpro" Xephyr outputs this line
before crashing:

expected keysym, got XF86Info: line 914 of inet


I rebuilt Xephyr with debuging symbols and got this backtrace. I hope it
helps.

#0  0xb7c70695 in free () from /lib/libc.so.6
#1  0x083758b1 in Xfree (ptr=0xb7d3f124) at ../../os/utils.c:1466
#2  0x08363376 in _XkbFreeGeomLeafElems (freeAll=, 
first=, 
count=17, num_inout=0x8449434, sz_inout=0x8449436, elems=0x844943c, 
elem_sz=8)
at ../../xkb/XKBGAlloc.c:62
#3  0x083633c7 in SrvXkbFreeGeomKeys (row=0x8449430, first=0, count=17, 
freeAll=1)
at ../../xkb/XKBGAlloc.c:327
#4  0x0836340c in _XkbClearRow (row_in=0x1180002 )
at ../../xkb/XKBGAlloc.c:342
#5  0x08362dc1 in _XkbFreeGeomNonLeafElems (freeAll=1, first=0, count=4, 
num_inout=0x84490e0, 
sz_inout=0x84490e6, elems=0x84490ec, elem_sz=24, freeFunc=0x83633d0 
<_XkbClearRow>)
at ../../xkb/XKBGAlloc.c:119
#6  0x08362f4d in SrvXkbFreeGeomRows (section=0x84490d0, first=0, count=4, 
freeAll=1)
at ../../xkb/XKBGAlloc.c:349
#7  0x08362fa1 in _XkbClearSection (section_in=0x84490d0 "Ä") at 
../../xkb/XKBGAlloc.c:363
#8  0x08362dc1 in _XkbFreeGeomNonLeafElems (freeAll=1, first=0, count=7, 
num_inout=0x8448876, 
sz_inout=0x844886a, elems=0x844, elem_sz=48, freeFunc=0x8362f60 
<_XkbClearSection>)
at ../../xkb/XKBGAlloc.c:119
#9  0x08362eed in SrvXkbFreeGeomSections (geom=0x8448850, first=0, count=7, 
freeAll=1)
at ../../xkb/XKBGAlloc.c:374
#10 0x0836365f in SrvXkbFreeGeometry (geom=0x8448850, which=63, freeMap=1) at 
../../xkb/XKBGAlloc.c:443
#11 0x0836169a in SrvXkbFreeKeyboard (xkb=0x844d698, which=127, freeAll=1) at 
../../xkb/XKBAlloc.c:328
#12 0x0834f44f in XkbFreeInfo (xkbi=0x843d760) at ../../xkb/xkbInit.c:820
#13 0x0807008f in CloseDevice (dev=0x843e6c0) at ../../dix/devices.c:530
#14 0x080704f0 in CloseDownDevices () at ../../dix/devices.c:626
#15 0x08080368 in main (argc=2, argv=0xbfd6b624, envp=Cannot access memory at 
address 0x49
) at ../../dix/main.c:472




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

Processed: [bts-link] source package xserver-xorg-video-intel

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> #
> # bts-link upstream status pull for source package xserver-xorg-video-intel
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # remote status report for #465421
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=13376
> forwarded 465421 https://bugs.freedesktop.org/show_bug.cgi?id=14476, 
> merged-upstream: https://bugs.freedesktop.org/show_bug.cgi?id=13376
Bug#465421: xserver-xorg-video-intel: Segfault when using large (>2048) Virual 
display
Forwarded-to-address changed from 
https://bugs.freedesktop.org/show_bug.cgi?id=14476 to 
https://bugs.freedesktop.org/show_bug.cgi?id=14476, merged-upstream: 
https://bugs.freedesktop.org/show_bug.cgi?id=13376.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#471052: xserver-xorg-input-kbd: AltGr key stops working when three keyboard layouts are configured

[Johannes Rohr]

Package: xserver-xorg-input-kbd
Version: 1:1.2.2-3
Severity: normal

When I configure two keyboard layouts in xorg.conf, like this:

Option "XkbLayout" "de,ru"

everything is fine,

however, when I add a third layout


Option "XkbLayout" "de,ru,dk"

the AltGr key in the German layout stops functioning properly.

I suppose this is easily reproducible. Same effect also when I configure
three layouts in gnome with the keyboard switcher applet.

Thanks,

Johannes


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

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

Versions of packages xserver-xorg-input-kbd depends on:
ii  libc6  2.7-9 GNU C Library: Shared libraries
ii  xserver-xorg-core  2:1.4.1~git20080131-2 Xorg X server - core server

xserver-xorg-input-kbd recommends no packages.

-- no debconf information



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

Bug#458916: text becomes unreadable during lenny installation

[oc-spam65]

Hello,

I just want to say that I experienced the same bug when installing a lenny last 
weekend on my laptop (network install). 

Installing an etch the same way is OK. My graphic card is a Intel GM945.

The screen looks the same as the pictures sent by Rémi. The consoles are still 
active, only the screen is unreadable.

The problem also happens near the end of the installation (in the preceding 
sequences of the installation, I had no problem to choose the type of 
installation (graphic things, laptop mode) and give root and user passwords). 
Contrary to Rémi, I was not able to finish the installation because I didn't 
want to press "enter" blindly (I want to preserve another partition...)

Sorry if this e-mail is inappropriate... I don't manage to easily find if this 
bug report is still open and where the information should be sent.

Regards,

O.C.


 Créez votre adresse électronique [EMAIL PROTECTED] 
 1 Go d'espace de stockage, anti-spam et anti-virus intégrés.

Bug#464353: How can we provide more info ?

[Apelete Seketeli]

Hello,

I tried Option "AccelMethod" "XAA" and didn't experience a single crash with
it (even with using an external monitor on my laptop). It seems that EXA is
definitely the source of the current intel driver instability.

Metacity 2.22 just landed in the Debian unstable repos, and I noticed that
when compositing effects are activated, EXA is needed by Totem (and other
movie players I suppose)  in order to watch videos (or even to display the
visual effects when playing music files), otherwise Totem just exit with the
following message:

The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 54 error_code 11 request_code 140 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

I don't know if that helps to narrow the problem, but I hope there will be a
fix soon; Metacity  compositing effects are just so "kicking-ass", what a
shame I can't play any video while using them :-)

Peace.
-- 
Apelete Seketeli <[EMAIL PROTECTED]>

Bug#421772: The above patch for 421772

[James Spencer]

Package: xserver-xorg-core
Version: 2:1.4.1~git20080131-1

--- Please enter the report below this line. ---

The above patch for 421772 when applied has solved a great deal of font 
rendering trouble particularly wrt to KHTML. In my case, my very old CRT 
comes up with some very bad dpi settings. Historically I used 'DisplaySize' 
to get a 'real DPI' for my monitor-- Prior to the new xrandr the fixed DPI 
that was used at least produced correct rendering of fonts. I can work around 
my problems by forcing a dpi, or using any RandR tool to set the size, but 
this patch has been a great boon here.

OR, fancy new xorg-goodness should submit to cruddy old xorg.conf hammering if 
there's something explicit in there...

--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.24-1-686

Debian Release: lenny/sid
  500 unstablewww.debian-multimedia.org 
  500 unstableftp.de.debian.org 
  500 testing-proposed-updates ftp.de.debian.org 
  500 testing ftp.de.debian.org 
  500 experimentalwww.debian-multimedia.org 
1 experimentalftp.de.debian.org 

--- Package information. ---
Depends (Version) | Installed
=-+-
libc6  (>= 2.7-1) | 2.7-9
libdbus-1-3(>= 1.1.1) | 1.1.20-1
libdrm2(>= 2.3.0) | 2.3.0-4
libfontenc1   | 1:1.0.4-2
libgcc1   (>= 1:4.1.1-21) | 1:4.3.0-1
libhal1  (>= 0.5.8.1) | 0.5.10+git20080301-1
libpixman-1-0(>= 0.9.4-2) | 0.9.6-1
libxau6   | 1:1.0.3-2
libxdmcp6 | 1:1.0.2-2
libxfont1(>= 1:1.2.9) | 1:1.3.2-1
x11-common   (>= 1:7.0.0) | 1:7.3+10
xserver-xorg  | 1:7.3+10


-- 
()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments



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

Bug#464353: How can we provide more info ?

[Apelete Seketeli]

Hello,

I tried Option "AccelMethod" "XAA" and the didn't experience a single crash
with it (even with using an external monitor on my laptop). It seems that
EXA is definitely the source of the current intel driver instability.

Metacity 2.22 just landed in the Debian unstable repos, and I noticed that
when compositing effects are activated, EXA is needed by Totem (and other
movie players I suppose)  in order to watch videos (or even to display the
visual effects when playing music files), otherwise Totem just exit with the
following message:

The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 54 error_code 11 request_code 140 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

I don't know if that helps to narrow the problem, but I hope there will be a
fix soon; Metacity  compositing effects are just so "kicking-ass", what a
shame I can't play any video while using them :-)

Peace.
-- 
Apelete Seketeli <[EMAIL PROTECTED]>

Bug#464353: How can we provide more info ?

[Apelete Seketeli]

I have tried some more options in order to enable video playing with
Metacity's compositing effects (which boils down to re-enable EXA).

I have found that if I use EXA with the option "MigrationHeuristic"
"greedy", xserver does not hang anymore (and using "ExaNoComposite"
"false"does improve compositing if you use "MigrationHeuristic" "greedy",
but that's out of subject). So now I can use the intel driver with EXA, even
though I do not understand why that option is needed now...
-- 
Apelete Seketeli <[EMAIL PROTECTED]>

Bug#422668: absurd andromeda

[Carlos Rios]

Get Presrciptions asap
www.www.anagrambarre.ashamed%2Elitulipog.com



but barcelonaaffidavit




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

Bug#358751: additive although

[Harris Bonds]

Buy rPescriptions while you still can!
www.www.barycentricagrimony.ajar.orginavez.com



on amateurishalbum




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

Bug#394803: marked as done (xserver-xorg-video-nv: Mousepointer vanishes)

[Debian Bug Tracking System]

Your message dated Sun, 16 Mar 2008 01:26:32 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#394803: Bug#396993: xserver-xorg-video-nv: Xserver 
crashes machine completely
has caused the Debian Bug report #394803,
regarding xserver-xorg-video-nv: Mousepointer vanishes
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
394803: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=394803
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: xserver-xorg-video-nv
Version: 1:1.2.0-3
Severity: important

Hi,

I have an Asus Mainboard with that graphics adapter:


00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev 
a2) (prog-if 00 [VGA])
Subsystem: ASUSTeK Computer Inc. Unknown device 81cd
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- --- End Message ---
--- Begin Message ---
Hadmut Danisch wrote:
> Brice Goglin wrote:
>   
>> Any news?
>>
>>   
>> 
>
> Not really. I didn't see that bug for some time, but now
> the mainboard is gone, destroyed by an external USB harddisk
> drawing too much current.
>
> I have replaced the board with a newer one with a different
> graphics adapter.
>
> Maybe I'll get a replacement for the damaged board within the
> next weeks for warranty,  but then I'll use the board in a
> Ubuntu machine.
>   

Let's close this bug now since it does not seem like you will be able to
debug this further soon. Feel free to reopen if you ever reproduce with
a recent debian X.org anyway.

Brice


--- End Message ---

Processed: retitle 456997 to /usr/bin/xon missing, severity of 456997 is wishlist

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.18.1
> retitle 456997 /usr/bin/xon missing
Bug#456997: xutils: where has /usr/bin/xon gone ?
Changed Bug title to `/usr/bin/xon missing' from `xutils: where has 
/usr/bin/xon gone ?'.

> severity 456997 wishlist
Bug#456997: /usr/bin/xon missing
Severity set to `wishlist' from `normal'

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#457900: xfs: upgrade from xterm freezes X server

[Brice Goglin]

Paul Evans wrote:
> Package: xfs
> Version: 1:1.0.5-2
> Severity: normal
>
> During a normal 'dist-upgrade' of my system, the xfs package was
> upgraded. Early on in 'dist-upgrade', the old XFS was stopped. This
> caused the xterm that dist-upgrade was running from to stop responding,
> as well as other X programs stopping.
>
> To fix this, I ssh'ed in from another machine and ran:
>
>   /etc/init.d/xfs start
>
> This woke up the xterm and allowed me to finish the upgrade
>   

Are you sure that these programs were actually stuck? Or were they just
unable to display and receive events from you?

Last time I saw "problems" while upgrading xfs, my xterm/dist-upgrade
was unable to display anything, but it was still upgrading things in
background. So xfs finally got restarted at the end of the upgrade and I
got everything working as before. Not nice meanwhile, but seems to be
working fine iirc.

Brice




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

Processed: reassign 458692 to xserver-xorg-core ..., severity of 458692 is wishlist

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.18.1
> reassign 458692 xserver-xorg-core
Bug#458692: Starts X regardless of whether keyboard is correctly setup
Bug reassigned from package `xinit' to `xserver-xorg-core'.

> retitle 458692 please do not ignore xkbcomp-like errors when starting X
Bug#458692: Starts X regardless of whether keyboard is correctly setup
Changed Bug title to `please do not ignore xkbcomp-like errors when starting X' 
from `Starts X regardless of whether keyboard is correctly setup'.

> severity 458692 wishlist
Bug#458692: please do not ignore xkbcomp-like errors when starting X
Severity set to `wishlist' from `normal'

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Re: [Xcb] [RFC PATCH] New XCB socket handoff mechanism for Xlib/XCB and other libraries

[Jamey Sharp]

On Sun, Mar 16, 2008 at 06:55:23AM +0100, Vincent Torri wrote:
> it's too complicated for me, so i just have a small (and maybe stupid) 
> question: will it break abi ?

The short answer is "no, this does not break API or ABI", but the
details are a bit tricky.

These patches do not break the API or ABI of libxcb; they do introduce
new interfaces, so new programs built against the libxcb will require
the new libxcb at runtime, but old applications built against libxcb
will continue to work.

However, the patches remove libxcb-xlib and xcbxlib.h entirely, since
they existed solely to provide access to the old Xlib-specific
interface.  Anything depending on libxcb-xlib will have to switch to the
new handoff interface.  To the best of our knowledge, only Xlib links to
libxcb-xlib, and the patches convert Xlib to the new interface;
certainly nothing else *should* have used libxcb-xlib.

Unfortunately, Xlib and XCB must be upgraded at the same time. Though we
tried, we believe the libxcb-xlib interface cannot be implemented on top
of the new handoff system, at least not without reintroducing into
libxcb something like the xcb-xlib lock that we worked so hard to
remove.

However, shared library versioning should prevent any silent failures if
you don't upgrade simultaneously.  New Xlib/XCB will neither build nor
run without new XCB.  If you install new libxcb and remove the old
libxcb-xlib, Xlib will fail to load.  If you install new libxcb and
leave the old libxcb-xlib around, libxcb-xlib should fail to load due to
missing symbols.  In all cases, if you get this wrong, you'll know it,
because you'll get a dynamic linker error.

Distribution packages can address this problem through the use of
dependencies and conflicts, to ensure that the two libraries upgrade
simultaneously.  Make the new libxcb package conflict with the old
libxcb-xlib package.

As for the sentiment of "complicated", please do let us know if you have
any concerns or if you believe it needs a more detailed explanation.  We
found that the new interface simplified implementation in both Xlib and
XCB.

- Jamey Sharp and Josh Triplett


signature.asc
Description: Digital signature