Bug#185584: xserver-xfree86: X server should retry xfs connection
On Tue, Jul 24, 2007 at 02:23:04PM +0200, Julien Cristau wrote:
>
> doesn't "xset fp rehash" do that? (I have no idea, I've never used a
> font server.)
Unfortunately it doesn't seem to help. Now I'll need to restart
my X server.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#248940: Processed: Re: Bug#248940: xlibs: strange caps lock lag
On Fri, May 28, 2004 at 11:52:37PM -0500, Branden Robinson wrote:
>
> I did.
>
> From: Branden Robinson <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> ^^
> Subject: Re: Bug#248940: xlibs: strange caps lock lag
> Date: Fri, 28 May 2004 22:59:58 -0500
> Message-ID: <[EMAIL PROTECTED]>
Sorry, I should've paid more attention to the headers in the BTS.
BTW, that mail was stuck on your machine until today.
Received: from gluck.debian.org [192.25.206.10]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BUUny-0005QF-00; Sun, 30 May 2004 13:13:07 -0500
Received: from dhcp065-026-182-085.indy.rr.com (redwald.deadbeast.net)
[65.26.182.85]
by gluck.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BUUny-0007Jw-00; Sun, 30 May 2004 12:13:06 -0600
Received: by redwald.deadbeast.net (Postfix, from userid 1000)
id 18050649D7; Fri, 28 May 2004 22:59:59 -0500 (EST)
> However, I am supremely disinterested in playing your favorite sport
> (bug tennis), so I guess this bug will languish until a kernel
> person can be troubled to look at it, just like the last Toshiba laptop
> keyboard problem you insisted wasn't the kernel's business to deal
> with[1][2]. As you said, "There is no way that this patch can be
> accepted...Don't bother reassigning it back to me because I will simply
> reassign it again with no warning."[3]
I'm no longer the maintainer of the kernel package, so I suggest that
you appeal to the new maintainers directly at [EMAIL PROTECTED]
If they're happy with the bug report, then I certainly will not stand
in the way of you reassigning it.
Thanks,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
If X refuses to start with Radeon chip...
Then please upgrade your kernel to 2.6.5-4 or above.
The 2.6.5-3 release contained code which attempted to load firmware
for Radeon/R128 from userspace that fails miserably when the firmware
files aren't available.
This has been reverted for now.
I apologise for any inconvenience caused.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Bug#233818: #233818: xlibs: forces xlib6g and dependent packages off the system
So is this bug going to be fixed for sarge?
If not, I'll have to package xv again since the version I have from
potato (or was it slinky) cannot coexist with your package anymore.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: Bug#224909: kernel: atkbd.c: Unknown key released
reassign 224909 xserver-xfree86
quit
On Mon, Mar 01, 2004 at 11:01:01AM +0100, Bruno Muller wrote:
> Le sam 28/02/2004 ? 11:11, Herbert Xu a ?crit :
>
> > > Can you still reproduce this with 2.6.2?
> > >
> > > If so please show me the full kernel boot messages.
> >
> > Please reply.
>
> Sorry.
>
> With 2.6.2 and 2.6.3, the message is:
>
> Feb 29 22:37:20 schmurk kernel: atkbd.c: Unknown key released (translated set
> 2, code 0x7a on isa0060/serio0).
> Feb 29 22:37:20 schmurk kernel: atkbd.c: This is an XFree86 bug. It shouldn't
> access hardware directly.
OK, that really is a bug in X.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: Bug#232267: X-Window-System can't be started with kernel 2.6.2
On Thu, Feb 12, 2004 at 12:49:20PM -0500, Branden Robinson wrote:
> On Thu, Feb 12, 2004 at 07:37:01AM +1100, Herbert Xu wrote:
> > OK Branden, unless you guys can come up with a way to stop these
> > bug reports, I will undo this change tonight.
>
> I have a fix in mind, but I'm not going to be able to implement it and
> do a release on the timeline you appear to expect.
Well when you fix is ready, we can put this change back.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: Bug#232267: X-Window-System can't be started with kernel 2.6.2
On Wed, Feb 11, 2004 at 05:21:39PM +0100, Georg Colle wrote:
> Package: kernel-image-2.6.2-1-686
> Version: 2.6.2-1
>
> debian: unstable (SID)
> libc6 version 2.3.2.ds1-11
> Package: xserver-xfree86
> Version: 4.2.1-16
>
> When booting messages run through as usual until kdm is started. Then
> the monitor screen changes periodically several times between dark gray,
> black and the message "not synchronized" (guess X is looking for the
> right resolution to display). After this, I'm back on the terminal
> console.
> Logging in and starting X (startx): Same as above.
> xserver-xfree86 (Version: 4.2.1-16) does very well with kernel 2.4.24-2,
> so: is the problem due to the configuration of the kernel-image?
>
> Here are some lines extracted from XFree86.0.log dealing with the problem
> discribed above:
>
> //*** schnipp *
>
> (WW) No core pointer registered
> No core pointer
>
> Fatal server error:
> failed to initialize core devices
>
> //*** schnapp *
OK Branden, unless you guys can come up with a way to stop these
bug reports, I will undo this change tonight.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: Bug#187962: kernel oops with i810
On Wed, Apr 16, 2003 at 11:52:15AM +0200, Simon Morlat wrote:
> No more oops but graphic display still disapears.
> Here is what I get in /var/log/messages:
Is the machine still alive though? Can you login via the network
for instance?
If it is, then the bug needs to be reassigned to X so that it
can be dealt properly.
The ring buffer is controlled by the X server. The DRM driver
is just a user. The problem here is that the X server left it
in some bozzo state and the DRM driver just used it without checking
resulting in a lockup.
Since the DRM driver does not have complete possession over the
ring buffer, it is not appropriate for it to completely reset it.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Bug#142569: [lkcl@samba-tng.org: interaction between kernel and xfree86 v 4]
On Tue, Mar 11, 2003 at 02:15:15PM +, Luke Kenneth Casson Leighton wrote:
>
> i can manage recompiling kernels if someone would like
> to send me a patch.
What kind of a keyboard do you have? And what is the exact symptom
of your problem?
> ... what i can't manage [by myself] is recompiling Xfree86
> except possibly under strict supervision and by someone
> prepared to wield a Big Stick.
X is easy, you just need to strace it.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Bug#142569: [lkcl@samba-tng.org: interaction between kernel and xfree86 v 4]
On Tue, Mar 11, 2003 at 02:15:15PM +, Luke Kenneth Casson Leighton wrote:
>
> i can manage recompiling kernels if someone would like
> to send me a patch.
What kind of a keyboard do you have? And what is the exact symptom
of your problem?
> ... what i can't manage [by myself] is recompiling Xfree86
> except possibly under strict supervision and by someone
> prepared to wield a Big Stick.
X is easy, you just need to strace it.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#142569: [lkcl@samba-tng.org: interaction between kernel and xfree86 v 4]
On Tue, Mar 11, 2003 at 12:14:07AM +, Luke Kenneth Casson Leighton wrote:
>
> it was suggested to me after conversations with branden that
> i relate to you a story that may be of assistance to you.
As I have stated before, all we need to resolve #142569/#156563 is for
someone who can readily reproduce the problem to tap into the kernel
driver to produce a list of events, and then do the same for the X server.
Now comparing the two should make the problem obvious.
Unfortunately it seems that no one has been willing to do that as of yet.
Until we have some hard facts, hypothesising is not going to help.
BTW Branden, you should disconnect #121335 from the rest. The issue
of dupliate release events have been worked around in 2.4.21pre. It
is also said that 2.5's new software repeat mechanism also prevents it
from happening.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Bug#142569: [lkcl@samba-tng.org: interaction between kernel and xfree86 v 4]
On Tue, Mar 11, 2003 at 12:14:07AM +, Luke Kenneth Casson Leighton wrote:
>
> it was suggested to me after conversations with branden that
> i relate to you a story that may be of assistance to you.
As I have stated before, all we need to resolve #142569/#156563 is for
someone who can readily reproduce the problem to tap into the kernel
driver to produce a list of events, and then do the same for the X server.
Now comparing the two should make the problem obvious.
Unfortunately it seems that no one has been willing to do that as of yet.
Until we have some hard facts, hypothesising is not going to help.
BTW Branden, you should disconnect #121335 from the rest. The issue
of dupliate release events have been worked around in 2.4.21pre. It
is also said that 2.5's new software repeat mechanism also prevents it
from happening.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xlibmesa naming and relationships
Daniel Stone <[EMAIL PROTECTED]> wrote:
>
> You obviously don't understand how Debian's packaging system works.
> Please come back when you understand the fact that all binary packages
> carry the version assigned to the source package, and that this is
> invariable.
It is actually possible to have two binary packages with different version
numbers in the same source package. Bash used to do it when it was in the
same source package as libreadline.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: xlibmesa naming and relationships
Daniel Stone <[EMAIL PROTECTED]> wrote:
>
> You obviously don't understand how Debian's packaging system works.
> Please come back when you understand the fact that all binary packages
> carry the version assigned to the source package, and that this is
> invariable.
It is actually possible to have two binary packages with different version
numbers in the same source package. Bash used to do it when it was in the
same source package as libreadline.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xlibmesa naming and relationships
Branden Robinson <[EMAIL PROTECTED]> wrote:
>
> On Sat, Feb 08, 2003 at 03:23:25PM +0100, Michel D?nzer wrote:
>> Let me try to put it yet another way: xlibmesa3-gl and xlibmesa4-gl are
>> different versions of the same thing. We have package versions for this
>> purpose, no need to abuse the name.
>
> The package version will be the same as for every other binary package
> that is generated by the XFree86 source package, so it can't be
> communicated there.
So put it in a README file somewhere...
If you're really desparate, create a priority critical debconf note so
everyone sees it :)
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: xlibmesa naming and relationships
Branden Robinson <[EMAIL PROTECTED]> wrote:
>
> On Sat, Feb 08, 2003 at 03:23:25PM +0100, Michel D?nzer wrote:
>> Let me try to put it yet another way: xlibmesa3-gl and xlibmesa4-gl are
>> different versions of the same thing. We have package versions for this
>> purpose, no need to abuse the name.
>
> The package version will be the same as for every other binary package
> that is generated by the XFree86 source package, so it can't be
> communicated there.
So put it in a README file somewhere...
If you're really desparate, create a priority critical debconf note so
everyone sees it :)
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xlibmesa naming and relationships
Branden Robinson <[EMAIL PROTECTED]> wrote:
>
> I do not personally feel that the major version number used by a
> software project is a meaningless detail. At least not in the case of
> Mesa, where they bump the major version number to reflect major new
> developments, like texture and lighting acceleration support.
I appreciate your respect for the upstream authors, but I don't think
the package name is an appropriate forum to express that.
Shared library packages carry part of the soname in their names so that
multiple versions can be installed simultaneously. This does not seem
to be the case here as 3 is not related to the soname. In the event that
the mesa version number is bumped without the ABI changing, you risk
either being inconsistent or changing the package name gratuitously.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: xlibmesa naming and relationships
Branden Robinson <[EMAIL PROTECTED]> wrote:
>
> I do not personally feel that the major version number used by a
> software project is a meaningless detail. At least not in the case of
> Mesa, where they bump the major version number to reflect major new
> developments, like texture and lighting acceleration support.
I appreciate your respect for the upstream authors, but I don't think
the package name is an appropriate forum to express that.
Shared library packages carry part of the soname in their names so that
multiple versions can be installed simultaneously. This does not seem
to be the case here as 3 is not related to the soname. In the event that
the mesa version number is bumped without the ABI changing, you risk
either being inconsistent or changing the package name gratuitously.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#5212: xdm *still* allows login for /bin/true users
H. S. Teoh <[EMAIL PROTECTED]> wrote:
>
> I've just verified that XDM still exhibits this bug, contrary to what
> Steve Durham said about PAM fixing it. I added /bin/true to /etc/shells,
> and changed a user's shell to /bin/true. XDM still logged me in.
IMHO this bug is bogus. Raul's suggestion does not work, there is no
generic way to execute a command given an arbitrary shell.
What Steven Durham may have meant is that after switching to PAM, the
people who want to allow only FTP access can use something other than
/bin/true to do so, e.g., a simple list through pam_listfile.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Bug#5212: xdm *still* allows login for /bin/true users
H. S. Teoh <[EMAIL PROTECTED]> wrote:
>
> I've just verified that XDM still exhibits this bug, contrary to what
> Steve Durham said about PAM fixing it. I added /bin/true to /etc/shells,
> and changed a user's shell to /bin/true. XDM still logged me in.
IMHO this bug is bogus. Raul's suggestion does not work, there is no
generic way to execute a command given an arbitrary shell.
What Steven Durham may have meant is that after switching to PAM, the
people who want to allow only FTP access can use something other than
/bin/true to do so, e.g., a simple list through pam_listfile.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#121335: Please add the Toshiby keybounce fix
On Mon, Oct 28, 2002 at 01:01:43PM +0100, Michel D?nzer wrote:
>
> I doubt that very much as it happens with all kinds of keyboards on Macs
> but doesn't happen in Mac OS.
Well as I said earlier, it's not difficult to convince me.
For ADB keyboards, you just have to enable dump_adb_input in
macintosh/adb.c and recompile your kernel. If the output shows
that you do get the release from the hardware but not the kernel
then the issue is settled and we can find out what's going wrong.
If you suspect that the problem is further down in the system,
then you could also simply add printks to the relevant interrupt
handler (easy to find as they usually call adb_input) to see if
you're getting notified or not. If you don't get an interrupt,
then you won't get any release events.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Bug#121335: Please add the Toshiby keybounce fix
On Mon, Oct 28, 2002 at 01:01:43PM +0100, Michel D?nzer wrote:
>
> I doubt that very much as it happens with all kinds of keyboards on Macs
> but doesn't happen in Mac OS.
Well as I said earlier, it's not difficult to convince me.
For ADB keyboards, you just have to enable dump_adb_input in
macintosh/adb.c and recompile your kernel. If the output shows
that you do get the release from the hardware but not the kernel
then the issue is settled and we can find out what's going wrong.
If you suspect that the problem is further down in the system,
then you could also simply add printks to the relevant interrupt
handler (easy to find as they usually call adb_input) to see if
you're getting notified or not. If you don't get an interrupt,
then you won't get any release events.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#121335: Please add the Toshiby keybounce fix
On Mon, Oct 28, 2002 at 12:42:17PM +0100, Michel D?nzer wrote:
>
> See this thread:
>
> http://lists.debian.org/debian-powerpc/2002/debian-powerpc-200210/msg00260.html
Well I don't see anything in there that shows that this is a kernel
bug. What it does show is that some people are seeing this on the
console. This means that it probably is a hardware problem.
Unfortunately this is not something that can be worked around in
software since it is easy to filter out spurious events, but it
is impossible to manufacture missing events.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Bug#121335: Please add the Toshiby keybounce fix
On Mon, Oct 28, 2002 at 12:42:17PM +0100, Michel D?nzer wrote:
>
> See this thread:
>
> http://lists.debian.org/debian-powerpc/2002/debian-powerpc-200210/msg00260.html
Well I don't see anything in there that shows that this is a kernel
bug. What it does show is that some people are seeing this on the
console. This means that it probably is a hardware problem.
Unfortunately this is not something that can be worked around in
software since it is easy to filter out spurious events, but it
is impossible to manufacture missing events.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
