Bug#594684: Package

[Panayiotis Karabassis]

In the hope that this bug can be closed, I have prepared a package that 
incorporates the patch.

It is available at:
http://mentors.debian.net/package/xorg-server

-- 
Best regards,
Panayiotis Karabassis



-- 
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/20110919111652.c07198ab3ac15f1e725b1...@gmail.com

Re: xserver-xorg-video-nouveau removes xserver-xorg-input-kbd xserver-xorg-input-mouse and others

[Rainer Dorsch]

Am Sunday, 18. September 2011 schrieb Julien Cristau:
> On Sun, Sep 18, 2011 at 15:23:32 +0200, Rainer Dorsch wrote:
> > Hi Rhonda,
> > 
> > thanks for the quick reply. Worked indeed. The only challenge beyond that
> > was that also needed to upgrade the kernel, otherwise I saw in
> > /var/log/Xorg.log.0
> > 
> > (EE) [drm] failed to open device
> > 
> > and the backported xserver-xorg-video-nouveau did not get up.
> > 
> > Is there a better place to document this (or even enforce by a
> > dependency?) than the mailing list archive here?
> 
> $ dpkg --fsys-tarfile
> ../xserver-xorg-video-nouveau_0.0.16+git20110411+8378443-1_amd64.deb | tar
> xOf - ./usr/share/doc/xserver-xorg-video-nouveau/NEWS.Debian.gz | zcat
> xserver-xorg-video-nouveau (1:0.0.16+git20100518+4b8f1a0-1) experimental;
> urgency=low
> 
>   This version of xserver-xorg-video-nouveau is linked against a newer
>   libdrm-nouveau which breaks the ABI and is not compatible with kernels
>   <= 2.6.33.  You need to upgrade the kernel to 2.6.34-rc1 or newer.
> 
>  -- Sven Joachim   Sat, 22 May 2010 10:22:42 +0200
> 
> That should show up automatically on package installation if you have
> apt-listchanges installed (which you really should).
> 

Thanks, it seems it is all there, I just did not look carefully enough.

Rainer


-- 
Rainer Dorsch
http://bokomoko.de/


-- 
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/201109191413.39111...@bokomoko.de

Bug#594684: Package

[Julien Cristau]

On Mon, Sep 19, 2011 at 11:16:52 +0300, Panayiotis Karabassis wrote:

> In the hope that this bug can be closed, I have prepared a package that 
> incorporates the patch.
> 
> It is available at:
> http://mentors.debian.net/package/xorg-server
> 
What I said in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594684#62 still
applies.  We won't carry this in the debian package until it's upstream.

Cheers,
Julien



-- 
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/20110919124007.ga18...@coloquinte.cristau.org

Bug#642012: x11-common: ssh-agent Xsession script does not check if gpg-agent will enable SSH support

[Julien Cristau]

On Sun, Sep 18, 2011 at 21:51:21 +0200, Luca Capello wrote:

> Hi there!
> 
> On Sun, 18 Sep 2011 17:05:37 +0200, Julien Cristau wrote:
> > On Sun, Sep 18, 2011 at 16:53:13 +0200, Luca Capello wrote:
> >
> >> --8<---cut here---start->8---
> [patch]
> >> --8<---cut here---end--->8---
> >> 
> > NAK, as far as I'm concerned this script has no business looking around
> > in gpg.conf.
> 
> This leaves the bug opened: I would be glad to explore other solutions,
> but AFAIK without checking gpg.conf and gpg-agent.conf there is no way
> to know *beforehand* 1) if gpg-agent will run and 2) if the latter will
> provide SSH support.
> 
> Please note that until now ssh-agent is *never* started if gpg-agent has
> been started at least once with SSH support, for the following reasons
> (and this is another bug, no matter what):
> 
> 1) 90gpg-agent is sourced before 90x11-common_ssh-agent
> 2) gpg-agent does not remove its "PID" file when exiting, see #642021

Sounds like that should be fixed.

> 3) 90gpg-agent sources the "PID" file above, which means that
>SSH_AUTH_SOCK is defined *before* any gpg-agent is started at all

Shouldn't the "if ! $GPGAGENT 2>/dev/null; then" line in 90gpg-agent be
followed by unsetting the variables (and maybe removing the file) it
just read since it found out they don't work?

> 4) 90x11-common_ssh-agent starts ssh-agent only if SSH_AUTH_SOCK is
>empty, which is not the case as per point 3
> 
> Here is the patch to test the behavior above:
> 
> --8<---cut here---start->8---
> --- 90x11-common_ssh-agent.ORG
> +++ 90x11-common_ssh-agent
> @@ -14,6 +14,11 @@
># use ssh-agent2's ssh-agent1 compatibility mode
>SSHAGENTARGS=-1
>  fi
> +  else
> +cat <>"$HOME"/.xsession-errors
> +/etc/X11/Xsession.d/90x11-common_ssh-agent: SSH_AUTH_SOCK='$SSH_AUTH_SOCK'
> +/etc/X11/Xsession.d/90x11-common_ssh-agent: not starting ssh-agent
> +EOF
>fi
>  fi
>  
> --8<---cut here---end--->8---
> 
> IMHO the real bug is to try to start ssh-agent in a system-wide fashion
> via /etc/X11/Xsession.options, while this is (clearly) a user option.
> This is also why I fear the new Xsession "use-gpg-agent" option at
> .  The fact
> that ssh_config does not have any way to define that we want the agent
> is probably the original cause of this bug.
> 
Can we switch the order so that 1) doesn't apply?  And turn ssh-agent
into a no-op when it's started by gpg-agent with ssh support (assuming
it's not already)?

> Finally, may I ask why this file is not provided by openssh-client?  I
> could not find any reference in the x11-common changelog.Debian nor
> x11-common Recommends:/Suggests:/Enhances: openssh-client.
> 
The changelog suggests this was already in xfree86-common with the
initial xfree86 4.0 upload 11 years ago.  I could go look for earlier
changelogs, but I guess "hysterical raisins" pretty much covers it?

Cheers,
Julien



-- 
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/20110919125714.gb18...@coloquinte.cristau.org

Bug#594684: Package

[Panayiotis Karabassis]

Is this dictated by Debian Policy? Just curious.

On 09/19/2011 03:40 PM, Julien Cristau wrote:
> On Mon, Sep 19, 2011 at 11:16:52 +0300, Panayiotis Karabassis wrote:
> 
>> In the hope that this bug can be closed, I have prepared a package that 
>> incorporates the patch.
>>
>> It is available at:
>> http://mentors.debian.net/package/xorg-server
>>
> What I said in
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594684#62 still
> applies.  We won't carry this in the debian package until it's upstream.
> 
> Cheers,
> Julien

-- 
Best regards,
Panayiotis Karabassis



-- 
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/4e774529.1080...@gmail.com

Q about modules and driver

[David Roguin]

Hi,

I don't really know if this is the correct list to ask this kind of
question, if not, could you please point me the right one?

I've recenty installed debian wheezy (with kernel 3.0) on a macbook pro
(8,1) . I got it up and running, but I'm struggling with the multitouch
trackpad that came with the mac.
The thing is, I'm trying to use the X module 'mtrack', but it's not even
loading. I've asked to several people and everything is where it should be
(but still is not working) so i'm wondering how is the flow between the
kernel and X, who should identify the trackpad? How does the kernel tell the
X which device to listen for input?
I was reading the example of how make a simple X module that reads from
random, but looking in this mtrack module i could't find anything that point
to the right input device; I'm asumming the kernel or X should do some
discovery of their own.

Tthanks for reading :)

-- 
David

Bug#594684: Package

[Julien Cristau]

On Mon, Sep 19, 2011 at 16:35:37 +0300, Panayiotis Karabassis wrote:

> Is this dictated by Debian Policy? Just curious.
> 
It's dictated by wanting to remain sane, as much as possible.  Which
implies not forking X with random feature patches.

Cheers,
Julien



-- 
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/20110919215501.gv3...@radis.liafa.jussieu.fr

Bug#594684: Package

[Panayiotis Karabassis]

Hi Julien,

On 09/20/2011 12:55 AM, Julien Cristau wrote:
> On Mon, Sep 19, 2011 at 16:35:37 +0300, Panayiotis Karabassis wrote:
> 
>> Is this dictated by Debian Policy? Just curious.
>>
> It's dictated by wanting to remain sane, as much as possible.  Which
> implies not forking X with random feature patches.
> 
> Cheers,
> Julien

It's not a random feature patch. X is unusable on Yeelong without this
patch.( So I am told, I have not tried ). Recompiling X takes about 3
hours on Yeelong. And nothing prevents you to drop the patch when it's
included upstream. Quilt will just tell about it.

What do others think?

-- 
Best regards,
Panayiotis Karabassis



-- 
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/4e77e37e.10...@gmail.com