Processed: tagging 196680, severity of 196680 is important

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tag 196680 + upstream
Bug#196680: xbase-clients: [xwd] locks display
There were no tags set.
Tags added: upstream

> severity 196680 important
Bug#196680: xbase-clients: [xwd] locks display
Severity set to `important'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

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

X Strike Force SVN commit: rev 163 - trunk/debian

[X Strike Force SVN Admin]

Author: branden
Date: 2003-06-08 23:03:18 -0500 (Sun, 08 Jun 2003)
New Revision: 163

Modified:
   trunk/debian/changelog
Log:
set release urgeny to "high" and add angry release notes


Modified: trunk/debian/changelog
==
--- trunk/debian/changelog  2003-06-09 03:52:47 UTC (rev 162)
+++ trunk/debian/changelog  2003-06-09 04:03:18 UTC (rev 163)
@@ -1,5 +1,28 @@
-xfree86 (4.2.1-8) unstable; urgency=low
+xfree86 (4.2.1-8) unstable; urgency=high
 
+  * the "you're damn right I'm bitter" release
+
+  * Release urgency due to 2 factors:
+- the motivation for 4.2.1-7 wasn't actually fulfilled because of an error
+  on my part (see change to debian/xlibs-pic.install* below) (KDE
+  maintainer(s), you want this)
+- GCC 3.3 miscompiles XDM-AUTHORIZATION-1 key generation and/or validation
+  routines at optimization level -O2 on more than just PowerPC; this hits
+  i386 as well.  Also, GCC 3.3 ICEs at -O2 on ARM, but not (reportedly) at
+  -O.  Therefore all of XFree86 is being stepped down to -O for all
+  architectures.  I'm loving the Brave New World of regressions that GCC
+  3.3 is bringing us -- isn't it good all of them were stopped dead in
+  their tracks before release thanks to the rigorous testing gcc-snapshot
+  buys us?
+- Urgency also high because people apparently do not know how to use the
+  Debian Bug Tracking System, and keep reporting the XDM-AUTHORIZATION-1
+  breakage over and over again.  And again.  And again.  And again.  And
+  again.  And again.  And again.  And again.  And again.  And again.  And
+  again.  And again.  And again.  And again.  And again.  And again.  And
+  again.  And again.  And again.  And again.  And again.  And again.  So,
+  just keep doing that, folks -- the more time I spent triaging redundant
+  reports, the less time I have to spend packaging XFree86 4.3.0.
+
   * debian/control:
 - move all "real" -dev and -dbg packages from section devel to section
   libdevel (syncrhonize with Debian archive override file)
@@ -31,7 +54,7 @@
 reported (based on a patch by Petter Reinholdtsen) (Closes: #179904)
   * debian/local/Xsession.5: document Xsession's new behavior
 
- -- Branden Robinson <[EMAIL PROTECTED]>  Sun,  8 Jun 2003 22:49:48 -0500
+ -- Branden Robinson <[EMAIL PROTECTED]>  Sun,  8 Jun 2003 22:55:16 -0500
 
 xfree86 (4.2.1-7) unstable; urgency=medium
 

Bug#196575: Processed: ugh

[Branden Robinson]

On Mon, Jun 09, 2003 at 10:52:47AM +1000, Daniel Stone wrote:
> On Sun, Jun 08, 2003 at 08:48:56PM -0400, Jack Howarth wrote:
> >From http://necrotic.deadbeast.net/xfree86/, I built the
> > branches-4.3.0-sid-debian-2003.06.07.tar.gz. This is against
> > current debian ppc sid plus todays freetype6 2.1.4-4 package.
> > The resulting xfree86 packages, when installed, allow me to
> > telnet back into my machine and open a xcalc in the current
> > xserver. If I should be trying to see this breakage in some
> > other way let me know but everything runs fine here.
> 
> You need to start a ?dm. I've been told that my 4.3.0 packages exhibit
> the same breakage (miscompilation). We already know that startx and
> running apps works, it's the ?dm stuff that breaks.
> 
> Please read bug reports before you dismiss them.

I am tempted to ask the Debian BTS admins to blacklist all of Jack's
known addresses.

-- 
G. Branden Robinson|There is no housing shortage in
Debian GNU/Linux   |Lincoln today -- just a rumor that
[EMAIL PROTECTED] |is put about by people who have
http://people.debian.org/~branden/ |nowhere to live.-- G. L. Murfin


pgpjhsVED9dVt.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Branden Robinson]

On Sun, Jun 08, 2003 at 08:48:56PM -0400, Jack Howarth wrote:
> Daniel,
>From http://necrotic.deadbeast.net/xfree86/, I built the
> branches-4.3.0-sid-debian-2003.06.07.tar.gz.

This is the best reason I've yet seen for imposing access controls on
that directory, or discontinuing this service entirely.

Jack, I don't need your kind of "help", where every problem is used by
an excuse to make disruptive changes and updates to bleeding edge code.

Using bleeding-edge code masquerading as a release (GCC 3.3) is what
got us *into* the current mess with XDM-AUTHORIZATION-1.

-- 
G. Branden Robinson|You should try building some of the
Debian GNU/Linux   |stuff in main that is
[EMAIL PROTECTED] |modern...turning on -Wall is like
http://people.debian.org/~branden/ |turning on the pain. -- James Troup


pgpz9Au3TM4S3.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Branden Robinson]

On Sun, Jun 08, 2003 at 06:38:10PM -0400, Jack Howarth wrote:
> Branden,
>  Well all I can say is that the current xfree86 4.3.0 branch
> debian 0pre1v1 sources that are posted build fine on debian ppc
> sid using gcc 3.3 without any evidence of this bug.

Well, you say they exhibit no "evidence" of this bug, and Daniel Stone
says they do.

You two fight out amongst yourselves.

There is still a lot of work to be done before 4.3.0 is ready for
release to unstable and I am not going to knuckle under to lame,
opportunistic pressure-group tactics like yours as an excuse to pretend
that work isn't necessary.

Jack, please stop mailing these bug reports until you have some actual
data, rather than opinions, to share.

-- 
G. Branden Robinson|The basic test of freedom is
Debian GNU/Linux   |perhaps less in what we are free to
[EMAIL PROTECTED] |do than in what we are free not to
http://people.debian.org/~branden/ |do.  -- Eric Hoffer


pgpbG0lYYiuve.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Branden Robinson]

On Mon, Jun 09, 2003 at 10:28:04AM +1000, Daniel Stone wrote:
> I'm going to see if I can shake this issue down after exams (four days),
> but it basically looks like gcc3.3 is *just* *not* *ready*. It doesn't
> build XFree86 at all on a couple of architectures, it ICEs on KDE on
> mips{,el}, it has numerous regressions, and seems to compile broken code
> at higher optimization levels.
> 
> Yay.

Let's not forget that cpp's -traditional mode is broken, too.

-- 
G. Branden Robinson|Freedom is kind of a hobby with me,
Debian GNU/Linux   |and I have disposable income that
[EMAIL PROTECTED] |I'll spend to find out how to get
http://people.debian.org/~branden/ |people more of it. -- Penn Jillette


pgpJ1gBqmOxtl.pgp
Description: PGP signature

Bug#196621: xserver-xfree86 / xlibs 4.2.1-7 issue - workaround

[Branden Robinson]

On Mon, Jun 09, 2003 at 02:05:11AM +0200, Julien wrote:
> On Sun, Jun 08, 2003 at 05:16:58PM -0500, Branden Robinson wrote:
> > When I experienced this problem during while preparing 4.2.1-7[1], I was
> > able to use xdm 4.2.1-7 and xlibs 4.2.1-7 with xserver-xfree86 4.2.1-6.
> > 
> > Please try that scenario.
> 
> I did upgrade xlibs to 4.2.1-7 but no way, same symptoms appeared again.
> The only working way here is to have both xlibs and xserver-xfree86 in
> their 4.2.1-6 version.

On PowerPC it was only necessary to downgrade xserver-xfree86.  Sigh.

Compiler regressions are hands-down my favorite things in the world.

-- 
G. Branden Robinson| I am only good at complaining.
Debian GNU/Linux   | You don't want me near your code.
[EMAIL PROTECTED] | -- Dan Jacobson
http://people.debian.org/~branden/ |


pgpJg1kjRaHlx.pgp
Description: PGP signature

X Strike Force SVN commit: rev 162 - trunk/debian

[X Strike Force SVN Admin]

Author: branden
Date: 2003-06-08 22:52:47 -0500 (Sun, 08 Jun 2003)
New Revision: 162

Modified:
   trunk/debian/changelog
   trunk/debian/rules
Log:
Step optimization level down to -O from -O2 for all architectures;
XDM-AUTHORIZATION-1 breakage induced by GCC 3.3 is present on i386 as well,
so it probably affects (several|all) architectures.


Modified: trunk/debian/rules
==
--- trunk/debian/rules  2003-06-08 18:25:15 UTC (rev 161)
+++ trunk/debian/rules  2003-06-09 03:52:47 UTC (rev 162)
@@ -101,9 +101,9 @@
 
 # *grumble* GCC 3.3 at -O2 is garbage on several architectures; XXX: this would
 # potentially override $(DEBUGFLAGS) if it were actually meaningful; see above
-ifneq (,$(findstring $(ARCH),arm powerpc))
+#ifneq (,$(findstring $(ARCH),arm powerpc))
 IMAKE_DEFINES+=-DDefaultGcc2OptimizeOpt=-O
-endif
+#endif
 
 # Read in important variables.
 include debian/scripts/vars

Modified: trunk/debian/changelog
==
--- trunk/debian/changelog  2003-06-08 18:25:15 UTC (rev 161)
+++ trunk/debian/changelog  2003-06-09 03:52:47 UTC (rev 162)
@@ -18,8 +18,8 @@
 - slight clarifications to xserver-xfree86, x-window-system-core, and
   x-window-system package descriptions
   * debian/rules: step compile optimization level down to -O from
-Policy-required -O2 for arm architecture as well as powerpc, due to GCC
-3.3 issues (see Debian bug #195424)
+Policy-required -O2 for all architectures, not just powerpc, due to GCC
+3.3 issues (see Debian bugs #195424,#196554,#196575,#196621, etc.)
   * debian/xlibs-pic.install*: sigh; add usr/X11R6/lib/libxkbfile_pic.a so
 that it's actually shipped in the package -- both LaMont and I overlooked
 this subtle detail :-P
@@ -31,7 +31,7 @@
 reported (based on a patch by Petter Reinholdtsen) (Closes: #179904)
   * debian/local/Xsession.5: document Xsession's new behavior
 
- -- Branden Robinson <[EMAIL PROTECTED]>  Thu,  5 Jun 2003 08:15:53 -0500
+ -- Branden Robinson <[EMAIL PROTECTED]>  Sun,  8 Jun 2003 22:49:48 -0500
 
 xfree86 (4.2.1-7) unstable; urgency=medium
 

Bug#179851: acknowledged by developer (Re: Bug#179851: xserver-xfree86)

[Branden Robinson]

On Mon, Jun 09, 2003 at 01:33:52AM +1000, Paul Anthony Judd wrote:
> On Thu, 6 Feb 2003 06:48, you wrote:
> > xserver-xfree86
> 
> I tried :
> apt-get -u -d install xserver-xfree86/testing
> Reading Package Lists... Done
> Building Dependency Tree... Done
> E: Release 'testing' for 'xserver-xfree86' was not found
> 
> apt-get -u -d install xserver-xfree86/unstable
> Reading Package Lists... Done
> Building Dependency Tree... Done
> E: Release 'unstable' for 'xserver-xfree86' was not found
> 
> apt-get -u  install xserver-xfree86
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Sorry, xserver-xfree86 is already the newest version.
> 0 packages upgraded, 0 newly installed, 0 to remove and 1  not upgraded.
> 
> bash [EMAIL PROTECTED]:~/ # apt-cache show xserver-xfree86
> Package: xserver-xfree86
[...]
> Version: 4.1.0-16

Looks like you don't have lines in your /etc/apt/sources.list file
pointing to testing or unstable.

To get them, just copy the ones for "stable", but replace the word
"stable" with "testing" or "unstable".

-- 
G. Branden Robinson| One man's "magic" is another man's
Debian GNU/Linux   | engineering.  "Supernatural" is a
[EMAIL PROTECTED] | null word.
http://people.debian.org/~branden/ | -- Robert Heinlein


pgp0.pgp
Description: PGP signature

00o1.1-beta2-2 startup error + XFree86 warning

[Yang Shouxun]

I have met similar problem to Stephane Chauveau's. See my report at 
http://lists.debian.org/debian-openoffice/2003/debian-openoffice-200306/msg00046.html
 
.

Stephane's message at
http://lists.debian.org/debian-openoffice/2003/debian-openoffice-200306/msg00056.html
 
suggests that the error may be due to FreeType couldn't open certain face.

So I try to search for similar errors, but didn't find one in 
/var/log/XFree86.0.log. Instead a find similar errors /var/log/XFree86.1.log, 
which was produced when I launched a second X session:
8<
: font renderer for ".pcf" already registered at priority 0
Warning: font renderer for ".pcf.Z" already registered at priority 0
Warning: font renderer for ".pcf.gz" already registered at priority 0
Warning: font renderer for ".snf" already registered at priority 0
Warning: font renderer for ".snf.Z" already registered at priority 0
Warning: font renderer for ".snf.gz" already registered at priority 0
Warning: font renderer for ".bdf" already registered at priority 0
Warning: font renderer for ".bdf.Z" already registered at priority 0
Warning: font renderer for ".bdf.gz" already registered at priority 0
Warning: font renderer for ".pmf" already registered at priority 0
FreeType: couldn't open face 
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType/bw=0.5:bsmi00lp.ttf: 1
8<
Interestingly, the last line repeats 8 times last Friday, but four times 
today.

bsmi00lp is a truetype font for Chinese characters (big5 encoding). I 
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType/bsmi00lp.ttf is link to 
/usr/share/fonts/truetype/arphic/bsmi00lp.ttf and the file is there. There 
are other similar entries in the fonts.dir file with prefixes like "bw=0.5" 
but no errors are reported other than the above.

1. Why the first session and the second session of XFree86 differ? I'm using 
XFree86 4.3.0-0ds4 from http://www.penguinppc.org/~daniels/sid/i386 .
2. How to fix the problem in a way similar to what Stephane did?

Any ideas?

shouxun

Processed: tagging 196680, severity of 196680 is important

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tag 196680 + upstream
Bug#196680: xbase-clients: [xwd] locks display
There were no tags set.
Tags added: upstream

> severity 196680 important
Bug#196680: xbase-clients: [xwd] locks display
Severity set to `important'.

>
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]

X Strike Force SVN commit: rev 163 - trunk/debian

[X Strike Force SVN Admin]

Author: branden
Date: 2003-06-08 23:03:18 -0500 (Sun, 08 Jun 2003)
New Revision: 163

Modified:
   trunk/debian/changelog
Log:
set release urgeny to "high" and add angry release notes


Modified: trunk/debian/changelog
==
--- trunk/debian/changelog  2003-06-09 03:52:47 UTC (rev 162)
+++ trunk/debian/changelog  2003-06-09 04:03:18 UTC (rev 163)
@@ -1,5 +1,28 @@
-xfree86 (4.2.1-8) unstable; urgency=low
+xfree86 (4.2.1-8) unstable; urgency=high
 
+  * the "you're damn right I'm bitter" release
+
+  * Release urgency due to 2 factors:
+- the motivation for 4.2.1-7 wasn't actually fulfilled because of an error
+  on my part (see change to debian/xlibs-pic.install* below) (KDE
+  maintainer(s), you want this)
+- GCC 3.3 miscompiles XDM-AUTHORIZATION-1 key generation and/or validation
+  routines at optimization level -O2 on more than just PowerPC; this hits
+  i386 as well.  Also, GCC 3.3 ICEs at -O2 on ARM, but not (reportedly) at
+  -O.  Therefore all of XFree86 is being stepped down to -O for all
+  architectures.  I'm loving the Brave New World of regressions that GCC
+  3.3 is bringing us -- isn't it good all of them were stopped dead in
+  their tracks before release thanks to the rigorous testing gcc-snapshot
+  buys us?
+- Urgency also high because people apparently do not know how to use the
+  Debian Bug Tracking System, and keep reporting the XDM-AUTHORIZATION-1
+  breakage over and over again.  And again.  And again.  And again.  And
+  again.  And again.  And again.  And again.  And again.  And again.  And
+  again.  And again.  And again.  And again.  And again.  And again.  And
+  again.  And again.  And again.  And again.  And again.  And again.  So,
+  just keep doing that, folks -- the more time I spent triaging redundant
+  reports, the less time I have to spend packaging XFree86 4.3.0.
+
   * debian/control:
 - move all "real" -dev and -dbg packages from section devel to section
   libdevel (syncrhonize with Debian archive override file)
@@ -31,7 +54,7 @@
 reported (based on a patch by Petter Reinholdtsen) (Closes: #179904)
   * debian/local/Xsession.5: document Xsession's new behavior
 
- -- Branden Robinson <[EMAIL PROTECTED]>  Sun,  8 Jun 2003 22:49:48 -0500
+ -- Branden Robinson <[EMAIL PROTECTED]>  Sun,  8 Jun 2003 22:55:16 -0500
 
 xfree86 (4.2.1-7) unstable; urgency=medium
 


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

Bug#196575: Processed: ugh

[Branden Robinson]

On Mon, Jun 09, 2003 at 10:52:47AM +1000, Daniel Stone wrote:
> On Sun, Jun 08, 2003 at 08:48:56PM -0400, Jack Howarth wrote:
> >From http://necrotic.deadbeast.net/xfree86/, I built the
> > branches-4.3.0-sid-debian-2003.06.07.tar.gz. This is against
> > current debian ppc sid plus todays freetype6 2.1.4-4 package.
> > The resulting xfree86 packages, when installed, allow me to
> > telnet back into my machine and open a xcalc in the current
> > xserver. If I should be trying to see this breakage in some
> > other way let me know but everything runs fine here.
> 
> You need to start a ?dm. I've been told that my 4.3.0 packages exhibit
> the same breakage (miscompilation). We already know that startx and
> running apps works, it's the ?dm stuff that breaks.
> 
> Please read bug reports before you dismiss them.

I am tempted to ask the Debian BTS admins to blacklist all of Jack's
known addresses.

-- 
G. Branden Robinson|There is no housing shortage in
Debian GNU/Linux   |Lincoln today -- just a rumor that
[EMAIL PROTECTED] |is put about by people who have
http://people.debian.org/~branden/ |nowhere to live.-- G. L. Murfin


pgp0.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Branden Robinson]

On Sun, Jun 08, 2003 at 08:48:56PM -0400, Jack Howarth wrote:
> Daniel,
>From http://necrotic.deadbeast.net/xfree86/, I built the
> branches-4.3.0-sid-debian-2003.06.07.tar.gz.

This is the best reason I've yet seen for imposing access controls on
that directory, or discontinuing this service entirely.

Jack, I don't need your kind of "help", where every problem is used by
an excuse to make disruptive changes and updates to bleeding edge code.

Using bleeding-edge code masquerading as a release (GCC 3.3) is what
got us *into* the current mess with XDM-AUTHORIZATION-1.

-- 
G. Branden Robinson|You should try building some of the
Debian GNU/Linux   |stuff in main that is
[EMAIL PROTECTED] |modern...turning on -Wall is like
http://people.debian.org/~branden/ |turning on the pain. -- James Troup


pgp0.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Branden Robinson]

On Sun, Jun 08, 2003 at 06:38:10PM -0400, Jack Howarth wrote:
> Branden,
>  Well all I can say is that the current xfree86 4.3.0 branch
> debian 0pre1v1 sources that are posted build fine on debian ppc
> sid using gcc 3.3 without any evidence of this bug.

Well, you say they exhibit no "evidence" of this bug, and Daniel Stone
says they do.

You two fight out amongst yourselves.

There is still a lot of work to be done before 4.3.0 is ready for
release to unstable and I am not going to knuckle under to lame,
opportunistic pressure-group tactics like yours as an excuse to pretend
that work isn't necessary.

Jack, please stop mailing these bug reports until you have some actual
data, rather than opinions, to share.

-- 
G. Branden Robinson|The basic test of freedom is
Debian GNU/Linux   |perhaps less in what we are free to
[EMAIL PROTECTED] |do than in what we are free not to
http://people.debian.org/~branden/ |do.  -- Eric Hoffer


pgp0.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Branden Robinson]

On Mon, Jun 09, 2003 at 10:28:04AM +1000, Daniel Stone wrote:
> I'm going to see if I can shake this issue down after exams (four days),
> but it basically looks like gcc3.3 is *just* *not* *ready*. It doesn't
> build XFree86 at all on a couple of architectures, it ICEs on KDE on
> mips{,el}, it has numerous regressions, and seems to compile broken code
> at higher optimization levels.
> 
> Yay.

Let's not forget that cpp's -traditional mode is broken, too.

-- 
G. Branden Robinson|Freedom is kind of a hobby with me,
Debian GNU/Linux   |and I have disposable income that
[EMAIL PROTECTED] |I'll spend to find out how to get
http://people.debian.org/~branden/ |people more of it. -- Penn Jillette


pgp0.pgp
Description: PGP signature

Bug#196621: xserver-xfree86 / xlibs 4.2.1-7 issue - workaround

[Branden Robinson]

On Mon, Jun 09, 2003 at 02:05:11AM +0200, Julien wrote:
> On Sun, Jun 08, 2003 at 05:16:58PM -0500, Branden Robinson wrote:
> > When I experienced this problem during while preparing 4.2.1-7[1], I was
> > able to use xdm 4.2.1-7 and xlibs 4.2.1-7 with xserver-xfree86 4.2.1-6.
> > 
> > Please try that scenario.
> 
> I did upgrade xlibs to 4.2.1-7 but no way, same symptoms appeared again.
> The only working way here is to have both xlibs and xserver-xfree86 in
> their 4.2.1-6 version.

On PowerPC it was only necessary to downgrade xserver-xfree86.  Sigh.

Compiler regressions are hands-down my favorite things in the world.

-- 
G. Branden Robinson| I am only good at complaining.
Debian GNU/Linux   | You don't want me near your code.
[EMAIL PROTECTED] | -- Dan Jacobson
http://people.debian.org/~branden/ |


pgp0.pgp
Description: PGP signature

X Strike Force SVN commit: rev 162 - trunk/debian

[X Strike Force SVN Admin]

Author: branden
Date: 2003-06-08 22:52:47 -0500 (Sun, 08 Jun 2003)
New Revision: 162

Modified:
   trunk/debian/changelog
   trunk/debian/rules
Log:
Step optimization level down to -O from -O2 for all architectures;
XDM-AUTHORIZATION-1 breakage induced by GCC 3.3 is present on i386 as well,
so it probably affects (several|all) architectures.


Modified: trunk/debian/rules
==
--- trunk/debian/rules  2003-06-08 18:25:15 UTC (rev 161)
+++ trunk/debian/rules  2003-06-09 03:52:47 UTC (rev 162)
@@ -101,9 +101,9 @@
 
 # *grumble* GCC 3.3 at -O2 is garbage on several architectures; XXX: this would
 # potentially override $(DEBUGFLAGS) if it were actually meaningful; see above
-ifneq (,$(findstring $(ARCH),arm powerpc))
+#ifneq (,$(findstring $(ARCH),arm powerpc))
 IMAKE_DEFINES+=-DDefaultGcc2OptimizeOpt=-O
-endif
+#endif
 
 # Read in important variables.
 include debian/scripts/vars

Modified: trunk/debian/changelog
==
--- trunk/debian/changelog  2003-06-08 18:25:15 UTC (rev 161)
+++ trunk/debian/changelog  2003-06-09 03:52:47 UTC (rev 162)
@@ -18,8 +18,8 @@
 - slight clarifications to xserver-xfree86, x-window-system-core, and
   x-window-system package descriptions
   * debian/rules: step compile optimization level down to -O from
-Policy-required -O2 for arm architecture as well as powerpc, due to GCC
-3.3 issues (see Debian bug #195424)
+Policy-required -O2 for all architectures, not just powerpc, due to GCC
+3.3 issues (see Debian bugs #195424,#196554,#196575,#196621, etc.)
   * debian/xlibs-pic.install*: sigh; add usr/X11R6/lib/libxkbfile_pic.a so
 that it's actually shipped in the package -- both LaMont and I overlooked
 this subtle detail :-P
@@ -31,7 +31,7 @@
 reported (based on a patch by Petter Reinholdtsen) (Closes: #179904)
   * debian/local/Xsession.5: document Xsession's new behavior
 
- -- Branden Robinson <[EMAIL PROTECTED]>  Thu,  5 Jun 2003 08:15:53 -0500
+ -- Branden Robinson <[EMAIL PROTECTED]>  Sun,  8 Jun 2003 22:49:48 -0500
 
 xfree86 (4.2.1-7) unstable; urgency=medium
 


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

00o1.1-beta2-2 startup error + XFree86 warning

[Yang Shouxun]

I have met similar problem to Stephane Chauveau's. See my report at 
http://lists.debian.org/debian-openoffice/2003/debian-openoffice-200306/msg00046.html 
.

Stephane's message at
http://lists.debian.org/debian-openoffice/2003/debian-openoffice-200306/msg00056.html 
suggests that the error may be due to FreeType couldn't open certain face.

So I try to search for similar errors, but didn't find one in 
/var/log/XFree86.0.log. Instead a find similar errors /var/log/XFree86.1.log, 
which was produced when I launched a second X session:
8<
: font renderer for ".pcf" already registered at priority 0
Warning: font renderer for ".pcf.Z" already registered at priority 0
Warning: font renderer for ".pcf.gz" already registered at priority 0
Warning: font renderer for ".snf" already registered at priority 0
Warning: font renderer for ".snf.Z" already registered at priority 0
Warning: font renderer for ".snf.gz" already registered at priority 0
Warning: font renderer for ".bdf" already registered at priority 0
Warning: font renderer for ".bdf.Z" already registered at priority 0
Warning: font renderer for ".bdf.gz" already registered at priority 0
Warning: font renderer for ".pmf" already registered at priority 0
FreeType: couldn't open face 
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType/bw=0.5:bsmi00lp.ttf: 1
8<
Interestingly, the last line repeats 8 times last Friday, but four times 
today.

bsmi00lp is a truetype font for Chinese characters (big5 encoding). I 
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType/bsmi00lp.ttf is link to 
/usr/share/fonts/truetype/arphic/bsmi00lp.ttf and the file is there. There 
are other similar entries in the fonts.dir file with prefixes like "bw=0.5" 
but no errors are reported other than the above.

1. Why the first session and the second session of XFree86 differ? I'm using 
XFree86 4.3.0-0ds4 from http://www.penguinppc.org/~daniels/sid/i386 .
2. How to fix the problem in a way similar to what Stephane did?

Any ideas?

shouxun


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

Processed: sigh, duplicates

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 196554 [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196554: [xlib]: gcc3.3 screws up authentication
Changed Bug title.

> retitle 196575 [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196575: [xlib]: gcc3.3 screws up authentication
Changed Bug title.

> retitle 196621 [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196621: After upgrade to 4.2.1-7, no clients can connect to the X server.
Changed Bug title.

> retitle 196622 [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196622: xfree86-common: latest update breaks KDE startup
Changed Bug title.

> retitle 196656 [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196656: xfree86: does not start up with kdm
Changed Bug title.

> reassign 196554 xfree86
Bug#196554: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196575: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196621: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug reassigned from package `xlibs' to `xfree86'.

> reassign 196575 xfree86
Bug#196575: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196554: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196621: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug reassigned from package `xfree86' to `xfree86'.

> reassign 196621 xfree86
Bug#196621: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196554: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196575: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug reassigned from package `xfree86' to `xfree86'.

> reassign 196622 xfree86
Bug#196622: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug reassigned from package `xfree86-common' to `xfree86'.

> reassign 196656 xfree86
Bug#196656: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug reassigned from package `xfree86' to `xfree86'.

> severity 196656 important
Bug#196656: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Severity set to `important'.

> severity 196622 important
Bug#196622: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Severity set to `important'.

> tags 196656 = patch sarge sid
Bug#196656: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Tags were: sid
Tags set to: patch, sarge, sid

> tags 196622 = patch sarge sid
Bug#196622: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
There were no tags set.
Tags set to: patch, sarge, sid

> merge 196554 196656 196622
Bug#196554: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196622: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196656: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196575: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196621: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Merged 196554 196575 196621 196622 196656.

> thanks
Stopping processing here.

Please contact me if you need assistance.

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

Bug#196575: Processed: ugh

[Daniel Stone]

On Sun, Jun 08, 2003 at 08:48:56PM -0400, Jack Howarth wrote:
>From http://necrotic.deadbeast.net/xfree86/, I built the
> branches-4.3.0-sid-debian-2003.06.07.tar.gz. This is against
> current debian ppc sid plus todays freetype6 2.1.4-4 package.
> The resulting xfree86 packages, when installed, allow me to
> telnet back into my machine and open a xcalc in the current
> xserver. If I should be trying to see this breakage in some
> other way let me know but everything runs fine here.

You need to start a ?dm. I've been told that my 4.3.0 packages exhibit
the same breakage (miscompilation). We already know that startx and
running apps works, it's the ?dm stuff that breaks.

Please read bug reports before you dismiss them.

-- 
Daniel Stone <[EMAIL PROTECTED]>
Developer, Trinity College, University of Melbourne


pgpa9wZJyBmot.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Jack Howarth]

Daniel,
   From http://necrotic.deadbeast.net/xfree86/, I built the
branches-4.3.0-sid-debian-2003.06.07.tar.gz. This is against
current debian ppc sid plus todays freetype6 2.1.4-4 package.
The resulting xfree86 packages, when installed, allow me to
telnet back into my machine and open a xcalc in the current
xserver. If I should be trying to see this breakage in some
other way let me know but everything runs fine here.
 Jack
ps The only other difference I can think of is that I am
running the current debian glibc cvs package for 2.3.2-1.

XFree86 in sid/sarge is broken, won't start ?dm

[Daniel Stone]

Hi all,
Yes, XFree86 is broken. If you use ?dm, it won't start. If you've been
bitten by this bug, you have three options:
a) downgrade xserver-xfree86 to 4.2.1-6
b) downgrade xlibs to 4.2.1-6
c) tough it out

If you choose option c, you'll have to stop your ?dm of choice, remove
the .Xauthority file, and run 'startx'. Ensure you have either a valid
.xsession/.xinitrc, or none at all.

There are several bugs reported on this (e.g. #196554), PLEASE do not
report any more! The problem lies with gcc3.3 producing broken code at
high optimization levels (sigh, gcc3.3), and we hope to have it fixed in
the next XFree86 release, whether that be 4.2.1-8, or 4.3.0-1. Please do
not ask us when it will be ready; we don't know.

Cheers!
:) d

-- 
Daniel Stone <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
KDE: Konquering a desktop near you - http://www.kde.org


pgpZhm4l4Hd3A.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Daniel Stone]

On Sun, Jun 08, 2003 at 06:38:10PM -0400, Jack Howarth wrote:
>  Well all I can say is that the current xfree86 4.3.0 branch
> debian 0pre1v1 sources that are posted build fine on debian ppc
> sid using gcc 3.3 without any evidence of this bug.

a) builds != works.
b) Where did you obtain those sources? Only my private repository for
   porters contains 4.3.0-0pre1v1.

-- 
Daniel Stone <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
KDE: Konquering a desktop near you - http://www.kde.org


pgpZaPxgZmXfP.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Daniel Stone]

On Sun, Jun 08, 2003 at 05:10:50PM -0500, Branden Robinson wrote:
> On Sun, Jun 08, 2003 at 02:00:39PM -0400, Jack Howarth wrote:
> > Branden,
> >We have never seen this problem with gcc 3.3 builds of XFree86
> > 4.3.0, right?
> 
> Bzzzt, stop right there.
> 
> What makes you think anyone has any Debian XFree86 packages of 4.3.0
> built with GCC 3.3?  That version of the compiler was made the default
> in unstable *after* Daniel Stone did his last release in the "ds"
> experimental series.
> 
> Please stop being so reckless with your assumptions.

4.3.0-0pre1v1 does, in fact, show the same symptoms when built with
gcc3.3, apparently. 4.3.0-0ds4 don't show the symptoms due to being
built with gcc3.2 (as was default at the time).

I'm going to see if I can shake this issue down after exams (four days),
but it basically looks like gcc3.3 is *just* *not* *ready*. It doesn't
build XFree86 at all on a couple of architectures, it ICEs on KDE on
mips{,el}, it has numerous regressions, and seems to compile broken code
at higher optimization levels.

Yay.

-- 
Daniel Stone <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
KDE: Konquering a desktop near you - http://www.kde.org


pgpz7CygKMsct.pgp
Description: PGP signature

Bug#196621: xserver-xfree86 / xlibs 4.2.1-7 issue - workaround

[Daniel Stone]

On Sun, Jun 08, 2003 at 05:16:58PM -0500, Branden Robinson wrote:
> [1] People who read my changelogs might have noticed the following:
> 
>   + GCC 3.3 appears to produce bad code for PowerPC at the optimization
> level required by Debian Policy (the X server cannot validate
> XDM-AUTHORIZATION-1 keys); when building on PowerPC, set
> DefaultGcc2OptimizeOpt to -O instead of -O2
> 
> I don't own an i386 machine, so I did not know that this bug affected
> that architecture as well.  GCC 3.3 has many regressions, though --
> XFree86 4.2.1-7 will not even build with that compiler on arm, mips,
> mipsel, and possibly m68k (reason for the latter's build failure is not
> nailed down yet, it could be lack of disk space masquerading as
> something more subtle).

I'll do a test build of trunk/ on i386 in about four days (when exams
are over), and see if that fixes it.

-- 
Daniel Stone <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
KDE: Konquering a desktop near you - http://www.kde.org


pgpH3J6rKGeSL.pgp
Description: PGP signature

Bug#196621: xserver-xfree86 / xlibs 4.2.1-7 issue - workaround

[Julien]

On Sun, Jun 08, 2003 at 05:16:58PM -0500, Branden Robinson wrote:
> When I experienced this problem during while preparing 4.2.1-7[1], I was
> able to use xdm 4.2.1-7 and xlibs 4.2.1-7 with xserver-xfree86 4.2.1-6.
> 
> Please try that scenario.

I did upgrade xlibs to 4.2.1-7 but no way, same symptoms appeared again.
The only working way here is to have both xlibs and xserver-xfree86 in
their 4.2.1-6 version.

-- 
Julien.

Processed: sigh, duplicates

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 196554 [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196554: [xlib]: gcc3.3 screws up authentication
Changed Bug title.

> retitle 196575 [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196575: [xlib]: gcc3.3 screws up authentication
Changed Bug title.

> retitle 196621 [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196621: After upgrade to 4.2.1-7, no clients can connect to the X server.
Changed Bug title.

> retitle 196622 [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196622: xfree86-common: latest update breaks KDE startup
Changed Bug title.

> retitle 196656 [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196656: xfree86: does not start up with kdm
Changed Bug title.

> reassign 196554 xfree86
Bug#196554: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196575: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196621: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug reassigned from package `xlibs' to `xfree86'.

> reassign 196575 xfree86
Bug#196575: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196554: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196621: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug reassigned from package `xfree86' to `xfree86'.

> reassign 196621 xfree86
Bug#196621: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196554: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196575: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug reassigned from package `xfree86' to `xfree86'.

> reassign 196622 xfree86
Bug#196622: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug reassigned from package `xfree86-common' to `xfree86'.

> reassign 196656 xfree86
Bug#196656: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug reassigned from package `xfree86' to `xfree86'.

> severity 196656 important
Bug#196656: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Severity set to `important'.

> severity 196622 important
Bug#196622: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Severity set to `important'.

> tags 196656 = patch sarge sid
Bug#196656: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Tags were: sid
Tags set to: patch, sarge, sid

> tags 196622 = patch sarge sid
Bug#196622: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
There were no tags set.
Tags set to: patch, sarge, sid

> merge 196554 196656 196622
Bug#196554: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196622: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196656: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196575: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Bug#196621: [xfree86]: gcc3.3 screws up authentication at -O2, -O needed
Merged 196554 196575 196621 196622 196656.

> 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#196680: xbase-clients: [xwd] locks display

[Alexander Kotelnikov]

Package: xbase-clients
Version: 4.1.0-16
Severity: grave
Justification: causes non-serious data loss

If one run
xwd -display :N 
on :M and kill xwd with, say, ^C, he will get his :N locked. Easily
reproducible.


-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux pale 2.4.18 #1 Sun May 11 20:16:47 MSD 2003 i686
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R

Versions of packages xbase-clients depends on:
ii  cpp  2:2.95.4-14 The GNU C preprocessor.
ii  debconf  1.0.32  Debian configuration management sy
ii  libc62.2.5-11.5  GNU C Library: Shared libraries an
ii  libdps1  4.1.0-16Display PostScript (DPS) client li
ii  libfreetype6 2.0.9-1 FreeType 2 font engine, shared lib
ii  libncurses5  5.2.20020112a-7 Shared libraries for terminal hand
ii  libxaw7  4.1.0-16X Athena widget set library
ii  xlibmesa34.1.0-16XFree86 version of Mesa 3D graphic
ii  xlibmesa3 [libgl1]   4.1.0-16XFree86 version of Mesa 3D graphic
ii  xlibs4.1.0-16X Window System client libraries

Bug#196575: Processed: ugh

[Daniel Stone]

On Sun, Jun 08, 2003 at 08:48:56PM -0400, Jack Howarth wrote:
>From http://necrotic.deadbeast.net/xfree86/, I built the
> branches-4.3.0-sid-debian-2003.06.07.tar.gz. This is against
> current debian ppc sid plus todays freetype6 2.1.4-4 package.
> The resulting xfree86 packages, when installed, allow me to
> telnet back into my machine and open a xcalc in the current
> xserver. If I should be trying to see this breakage in some
> other way let me know but everything runs fine here.

You need to start a ?dm. I've been told that my 4.3.0 packages exhibit
the same breakage (miscompilation). We already know that startx and
running apps works, it's the ?dm stuff that breaks.

Please read bug reports before you dismiss them.

-- 
Daniel Stone <[EMAIL PROTECTED]>
Developer, Trinity College, University of Melbourne


pgp0.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Jack Howarth]

Daniel,
   From http://necrotic.deadbeast.net/xfree86/, I built the
branches-4.3.0-sid-debian-2003.06.07.tar.gz. This is against
current debian ppc sid plus todays freetype6 2.1.4-4 package.
The resulting xfree86 packages, when installed, allow me to
telnet back into my machine and open a xcalc in the current
xserver. If I should be trying to see this breakage in some
other way let me know but everything runs fine here.
 Jack
ps The only other difference I can think of is that I am
running the current debian glibc cvs package for 2.3.2-1.



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

XFree86 in sid/sarge is broken, won't start ?dm

[Daniel Stone]

Hi all,
Yes, XFree86 is broken. If you use ?dm, it won't start. If you've been
bitten by this bug, you have three options:
a) downgrade xserver-xfree86 to 4.2.1-6
b) downgrade xlibs to 4.2.1-6
c) tough it out

If you choose option c, you'll have to stop your ?dm of choice, remove
the .Xauthority file, and run 'startx'. Ensure you have either a valid
.xsession/.xinitrc, or none at all.

There are several bugs reported on this (e.g. #196554), PLEASE do not
report any more! The problem lies with gcc3.3 producing broken code at
high optimization levels (sigh, gcc3.3), and we hope to have it fixed in
the next XFree86 release, whether that be 4.2.1-8, or 4.3.0-1. Please do
not ask us when it will be ready; we don't know.

Cheers!
:) d

-- 
Daniel Stone <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
KDE: Konquering a desktop near you - http://www.kde.org


pgp0.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Jack Howarth]

Branden,
 Well all I can say is that the current xfree86 4.3.0 branch
debian 0pre1v1 sources that are posted build fine on debian ppc
sid using gcc 3.3 without any evidence of this bug.
Jack

Bug#196575: Processed: ugh

[Daniel Stone]

On Sun, Jun 08, 2003 at 06:38:10PM -0400, Jack Howarth wrote:
>  Well all I can say is that the current xfree86 4.3.0 branch
> debian 0pre1v1 sources that are posted build fine on debian ppc
> sid using gcc 3.3 without any evidence of this bug.

a) builds != works.
b) Where did you obtain those sources? Only my private repository for
   porters contains 4.3.0-0pre1v1.

-- 
Daniel Stone <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
KDE: Konquering a desktop near you - http://www.kde.org


pgp0.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Daniel Stone]

On Sun, Jun 08, 2003 at 05:10:50PM -0500, Branden Robinson wrote:
> On Sun, Jun 08, 2003 at 02:00:39PM -0400, Jack Howarth wrote:
> > Branden,
> >We have never seen this problem with gcc 3.3 builds of XFree86
> > 4.3.0, right?
> 
> Bzzzt, stop right there.
> 
> What makes you think anyone has any Debian XFree86 packages of 4.3.0
> built with GCC 3.3?  That version of the compiler was made the default
> in unstable *after* Daniel Stone did his last release in the "ds"
> experimental series.
> 
> Please stop being so reckless with your assumptions.

4.3.0-0pre1v1 does, in fact, show the same symptoms when built with
gcc3.3, apparently. 4.3.0-0ds4 don't show the symptoms due to being
built with gcc3.2 (as was default at the time).

I'm going to see if I can shake this issue down after exams (four days),
but it basically looks like gcc3.3 is *just* *not* *ready*. It doesn't
build XFree86 at all on a couple of architectures, it ICEs on KDE on
mips{,el}, it has numerous regressions, and seems to compile broken code
at higher optimization levels.

Yay.

-- 
Daniel Stone <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
KDE: Konquering a desktop near you - http://www.kde.org


pgp0.pgp
Description: PGP signature

Bug#196621: xserver-xfree86 / xlibs 4.2.1-7 issue - workaround

[Daniel Stone]

On Sun, Jun 08, 2003 at 05:16:58PM -0500, Branden Robinson wrote:
> [1] People who read my changelogs might have noticed the following:
> 
>   + GCC 3.3 appears to produce bad code for PowerPC at the optimization
> level required by Debian Policy (the X server cannot validate
> XDM-AUTHORIZATION-1 keys); when building on PowerPC, set
> DefaultGcc2OptimizeOpt to -O instead of -O2
> 
> I don't own an i386 machine, so I did not know that this bug affected
> that architecture as well.  GCC 3.3 has many regressions, though --
> XFree86 4.2.1-7 will not even build with that compiler on arm, mips,
> mipsel, and possibly m68k (reason for the latter's build failure is not
> nailed down yet, it could be lack of disk space masquerading as
> something more subtle).

I'll do a test build of trunk/ on i386 in about four days (when exams
are over), and see if that fixes it.

-- 
Daniel Stone <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
KDE: Konquering a desktop near you - http://www.kde.org


pgp0.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Branden Robinson]

On Sun, Jun 08, 2003 at 02:00:39PM -0400, Jack Howarth wrote:
> Branden,
>We have never seen this problem with gcc 3.3 builds of XFree86
> 4.3.0, right?

Bzzzt, stop right there.

What makes you think anyone has any Debian XFree86 packages of 4.3.0
built with GCC 3.3?  That version of the compiler was made the default
in unstable *after* Daniel Stone did his last release in the "ds"
experimental series.

Please stop being so reckless with your assumptions.

-- 
G. Branden Robinson| The Rehnquist Court has never
Debian GNU/Linux   | encountered a criminal statute it
[EMAIL PROTECTED] | did not like.
http://people.debian.org/~branden/ | -- John Dean


pgpOuemtkHeGX.pgp
Description: PGP signature

Bug#196621: xserver-xfree86 / xlibs 4.2.1-7 issue - workaround

[Julien]

On Sun, Jun 08, 2003 at 05:16:58PM -0500, Branden Robinson wrote:
> When I experienced this problem during while preparing 4.2.1-7[1], I was
> able to use xdm 4.2.1-7 and xlibs 4.2.1-7 with xserver-xfree86 4.2.1-6.
> 
> Please try that scenario.

I did upgrade xlibs to 4.2.1-7 but no way, same symptoms appeared again.
The only working way here is to have both xlibs and xserver-xfree86 in
their 4.2.1-6 version.

-- 
Julien.



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

Bug#196621: (no subject)

[Branden Robinson]

On Sun, Jun 08, 2003 at 07:31:25PM +0200, Julien wrote:
> Same issue here, before I restart the server to try getting rid of this
> matter. Unfortunately, X did not came up at all... I tried to fallback by
> downgrading xserver-common/xfree86, xfree86-common and all xlibs packages,
> without any result.
> 
> I get the following when trying to start(x):
> 
> 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/XFree86.0.log", Time: Sun Jun  8 19:26:17 2003
> (==) Using config file: "/etc/X11/XF86Config-4"
> Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:debug_xform.o":  No
> symbols found
> (EE) R128(0): No DFP detected
> Could not init font path element /usr/lib/X11/fonts/Speedo, removing from
> list!
> 
> waiting for X server to shut down
> 
> Issuing a 'startx -- -verbose' will not help to display more relevant
> errors than the "No DFP detected".

The above probably has nothing to do with the XDM-AUTHORIZATION-1 problem.

It looks like the kind of log one gets when one hasn't given the X
server any clients to run.

There are multiple reports of the X server working if you stop it,
delete your $HOME/.Xauthority file, and run "startx".  If startx still
fails you are likely experiencing some other problem.  For example, a
$HOME/.xsession file with nothing in it but echo commands will generate
a server log that looks much like the one you pasted.  The X server
starts, makes its usual noise (there were no fatal errors in the above),
finds itself without a client to run, and gracefully exits.

That message "waiting for X server to shut down" is what tells you that
the X server is exiting normally.

-- 
G. Branden Robinson|
Debian GNU/Linux   |   If ignorance is bliss,
[EMAIL PROTECTED] |   is omniscience hell?
http://people.debian.org/~branden/ |


pgpQyIRunMzU9.pgp
Description: PGP signature

Bug#196621: Bug#196554: Jeez, already reported. Merging.

[Branden Robinson]

On Sun, Jun 08, 2003 at 09:06:49PM +0200, Tore Anderson wrote:
> 
> severity 196621 important
> reassign 196621 xlibs
> merge 196554 196621
> quit
> 
>   My apologies for the duplicate bug report, I would never have thought
>  this bug would not be considered release critical, hence I did not
>  notice it when searching for an already submitted bug.
> 
>   Also, contrary to what's suggested earlier in the bug log, I experience
>  this when running startx from a virtual console, and not only from XDM
>  (which is also broken).  Purging the xdm package doesn't help either,
>  I still need to downgrade both the xlibs and xserver-xfree86 packages to
>  get a functional X server.

I have multiple reports, as well as personal experience with, a
workaround involving startx.

1) Stop all running X servers.
2) rm $HOME/.Xauthority
3) startx

You do not have to downgrade any packages for this workaround.

-- 
G. Branden Robinson|
Debian GNU/Linux   |   "Bother," said Pooh, as he was
[EMAIL PROTECTED] |   assimilated by the Borg.
http://people.debian.org/~branden/ |


pgpcBDHxxPY1p.pgp
Description: PGP signature

Bug#196621: xserver-xfree86 / xlibs 4.2.1-7 issue - workaround

[Branden Robinson]

On Sun, Jun 08, 2003 at 10:20:36PM +0200, Julien wrote:
> On Sun, Jun 08, 2003 at 07:31:25PM +0200, Julien wrote:
> > Same issue here, before I restart the server to try getting rid of this
> > matter. Unfortunately, X did not came up at all... I tried to fallback by
> > downgrading xserver-common/xfree86, xfree86-common and all xlibs packages,
> > without any result.
> 
> Correct version hereafter. Upgraded again all packages to 4.2.1-7, then
> downgraded xlibs and xserver-xfree86 to 4.2.1-6 -> X starting again. I
> tested with two drivers (two cards): nv and r128 (not using the generic one
> 'ati', since not 4.2.1-7), both are working after the fallback.

When I experienced this problem during while preparing 4.2.1-7[1], I was
able to use xdm 4.2.1-7 and xlibs 4.2.1-7 with xserver-xfree86 4.2.1-6.

Please try that scenario.

[1] People who read my changelogs might have noticed the following:

  + GCC 3.3 appears to produce bad code for PowerPC at the optimization
level required by Debian Policy (the X server cannot validate
XDM-AUTHORIZATION-1 keys); when building on PowerPC, set
DefaultGcc2OptimizeOpt to -O instead of -O2

I don't own an i386 machine, so I did not know that this bug affected
that architecture as well.  GCC 3.3 has many regressions, though --
XFree86 4.2.1-7 will not even build with that compiler on arm, mips,
mipsel, and possibly m68k (reason for the latter's build failure is not
nailed down yet, it could be lack of disk space masquerading as
something more subtle).

-- 
G. Branden Robinson|The errors of great men are
Debian GNU/Linux   |venerable because they are more
[EMAIL PROTECTED] |fruitful than the truths of little
http://people.debian.org/~branden/ |men. -- Friedrich Nietzsche


pgpk6H5f9nU5V.pgp
Description: PGP signature

Bug#196680: xbase-clients: [xwd] locks display

[Alexander Kotelnikov]

Package: xbase-clients
Version: 4.1.0-16
Severity: grave
Justification: causes non-serious data loss

If one run
xwd -display :N 
on :M and kill xwd with, say, ^C, he will get his :N locked. Easily
reproducible.


-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux pale 2.4.18 #1 Sun May 11 20:16:47 MSD 2003 i686
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R

Versions of packages xbase-clients depends on:
ii  cpp  2:2.95.4-14 The GNU C preprocessor.
ii  debconf  1.0.32  Debian configuration management sy
ii  libc62.2.5-11.5  GNU C Library: Shared libraries an
ii  libdps1  4.1.0-16Display PostScript (DPS) client li
ii  libfreetype6 2.0.9-1 FreeType 2 font engine, shared lib
ii  libncurses5  5.2.20020112a-7 Shared libraries for terminal hand
ii  libxaw7  4.1.0-16X Athena widget set library
ii  xlibmesa34.1.0-16XFree86 version of Mesa 3D graphic
ii  xlibmesa3 [libgl1]   4.1.0-16XFree86 version of Mesa 3D graphic
ii  xlibs4.1.0-16X Window System client libraries




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

Bug#196575: Processed: ugh

[Jack Howarth]

Branden,
 Well all I can say is that the current xfree86 4.3.0 branch
debian 0pre1v1 sources that are posted build fine on debian ppc
sid using gcc 3.3 without any evidence of this bug.
Jack



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

Bug#196621: xserver-xfree86 / xlibs 4.2.1-7 issue - workaround

[Julien]

On Sun, Jun 08, 2003 at 07:31:25PM +0200, Julien wrote:
> Same issue here, before I restart the server to try getting rid of this
> matter. Unfortunately, X did not came up at all... I tried to fallback by
> downgrading xserver-common/xfree86, xfree86-common and all xlibs packages,
> without any result.

Correct version hereafter. Upgraded again all packages to 4.2.1-7, then
downgraded xlibs and xserver-xfree86 to 4.2.1-6 -> X starting again. I
tested with two drivers (two cards): nv and r128 (not using the generic one
'ati', since not 4.2.1-7), both are working after the fallback.

-- 
Julien.

Bug#196575: Processed: ugh

[Branden Robinson]

On Sun, Jun 08, 2003 at 02:00:39PM -0400, Jack Howarth wrote:
> Branden,
>We have never seen this problem with gcc 3.3 builds of XFree86
> 4.3.0, right?

Bzzzt, stop right there.

What makes you think anyone has any Debian XFree86 packages of 4.3.0
built with GCC 3.3?  That version of the compiler was made the default
in unstable *after* Daniel Stone did his last release in the "ds"
experimental series.

Please stop being so reckless with your assumptions.

-- 
G. Branden Robinson| The Rehnquist Court has never
Debian GNU/Linux   | encountered a criminal statute it
[EMAIL PROTECTED] | did not like.
http://people.debian.org/~branden/ | -- John Dean


pgp0.pgp
Description: PGP signature

Bug#196621: (no subject)

[Branden Robinson]

On Sun, Jun 08, 2003 at 07:31:25PM +0200, Julien wrote:
> Same issue here, before I restart the server to try getting rid of this
> matter. Unfortunately, X did not came up at all... I tried to fallback by
> downgrading xserver-common/xfree86, xfree86-common and all xlibs packages,
> without any result.
> 
> I get the following when trying to start(x):
> 
> 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/XFree86.0.log", Time: Sun Jun  8 19:26:17 2003
> (==) Using config file: "/etc/X11/XF86Config-4"
> Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:debug_xform.o":  No
> symbols found
> (EE) R128(0): No DFP detected
> Could not init font path element /usr/lib/X11/fonts/Speedo, removing from
> list!
> 
> waiting for X server to shut down
> 
> Issuing a 'startx -- -verbose' will not help to display more relevant
> errors than the "No DFP detected".

The above probably has nothing to do with the XDM-AUTHORIZATION-1 problem.

It looks like the kind of log one gets when one hasn't given the X
server any clients to run.

There are multiple reports of the X server working if you stop it,
delete your $HOME/.Xauthority file, and run "startx".  If startx still
fails you are likely experiencing some other problem.  For example, a
$HOME/.xsession file with nothing in it but echo commands will generate
a server log that looks much like the one you pasted.  The X server
starts, makes its usual noise (there were no fatal errors in the above),
finds itself without a client to run, and gracefully exits.

That message "waiting for X server to shut down" is what tells you that
the X server is exiting normally.

-- 
G. Branden Robinson|
Debian GNU/Linux   |   If ignorance is bliss,
[EMAIL PROTECTED] |   is omniscience hell?
http://people.debian.org/~branden/ |


pgp0.pgp
Description: PGP signature

Bug#196621: Bug#196554: Jeez, already reported. Merging.

[Branden Robinson]

On Sun, Jun 08, 2003 at 09:06:49PM +0200, Tore Anderson wrote:
> 
> severity 196621 important
> reassign 196621 xlibs
> merge 196554 196621
> quit
> 
>   My apologies for the duplicate bug report, I would never have thought
>  this bug would not be considered release critical, hence I did not
>  notice it when searching for an already submitted bug.
> 
>   Also, contrary to what's suggested earlier in the bug log, I experience
>  this when running startx from a virtual console, and not only from XDM
>  (which is also broken).  Purging the xdm package doesn't help either,
>  I still need to downgrade both the xlibs and xserver-xfree86 packages to
>  get a functional X server.

I have multiple reports, as well as personal experience with, a
workaround involving startx.

1) Stop all running X servers.
2) rm $HOME/.Xauthority
3) startx

You do not have to downgrade any packages for this workaround.

-- 
G. Branden Robinson|
Debian GNU/Linux   |   "Bother," said Pooh, as he was
[EMAIL PROTECTED] |   assimilated by the Borg.
http://people.debian.org/~branden/ |


pgp0.pgp
Description: PGP signature

Bug#196621: xserver-xfree86 / xlibs 4.2.1-7 issue - workaround

[Branden Robinson]

On Sun, Jun 08, 2003 at 10:20:36PM +0200, Julien wrote:
> On Sun, Jun 08, 2003 at 07:31:25PM +0200, Julien wrote:
> > Same issue here, before I restart the server to try getting rid of this
> > matter. Unfortunately, X did not came up at all... I tried to fallback by
> > downgrading xserver-common/xfree86, xfree86-common and all xlibs packages,
> > without any result.
> 
> Correct version hereafter. Upgraded again all packages to 4.2.1-7, then
> downgraded xlibs and xserver-xfree86 to 4.2.1-6 -> X starting again. I
> tested with two drivers (two cards): nv and r128 (not using the generic one
> 'ati', since not 4.2.1-7), both are working after the fallback.

When I experienced this problem during while preparing 4.2.1-7[1], I was
able to use xdm 4.2.1-7 and xlibs 4.2.1-7 with xserver-xfree86 4.2.1-6.

Please try that scenario.

[1] People who read my changelogs might have noticed the following:

  + GCC 3.3 appears to produce bad code for PowerPC at the optimization
level required by Debian Policy (the X server cannot validate
XDM-AUTHORIZATION-1 keys); when building on PowerPC, set
DefaultGcc2OptimizeOpt to -O instead of -O2

I don't own an i386 machine, so I did not know that this bug affected
that architecture as well.  GCC 3.3 has many regressions, though --
XFree86 4.2.1-7 will not even build with that compiler on arm, mips,
mipsel, and possibly m68k (reason for the latter's build failure is not
nailed down yet, it could be lack of disk space masquerading as
something more subtle).

-- 
G. Branden Robinson|The errors of great men are
Debian GNU/Linux   |venerable because they are more
[EMAIL PROTECTED] |fruitful than the truths of little
http://people.debian.org/~branden/ |men. -- Friedrich Nietzsche


pgp0.pgp
Description: PGP signature

Bug#196656: xfree86: does not start up with kdm

[Thomas Koenig]

Package: xfree86
Version: unavailable; reported 2003-06-08
Severity: grave
Tags: sid
Justification: renders package unusable

I just upgraded to the latest version of X (4.2.1-7), and
found that I could not start up with kdm.  The grey screen
was repeatedly respawned, finally leading to it being disabled.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux meiner 2.4.20 #1 Thu Jun 5 20:58:11 CEST 2003 i686
Locale: LANG=C, [EMAIL PROTECTED]

Processed: Jeez, already reported. Merging.

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 196621 important
Bug#196621: After upgrade to 4.2.1-7, no clients can connect to the X server.
Severity set to `important'.

> reassign 196621 xlibs
Bug#196621: After upgrade to 4.2.1-7, no clients can connect to the X server.
Bug reassigned from package `xserver-xfree86' to `xlibs'.

> merge 196554 196621
Bug#196554: [xlib]: gcc3.3 screws up authentication
Bug#196621: After upgrade to 4.2.1-7, no clients can connect to the X server.
Bug#196575: [xlib]: gcc3.3 screws up authentication
Merged 196554 196575 196621.

> quit
Stopping processing here.

Please contact me if you need assistance.

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

Bug#196554: Jeez, already reported. Merging.

[Tore Anderson]

severity 196621 important
reassign 196621 xlibs
merge 196554 196621
quit

  My apologies for the duplicate bug report, I would never have thought
 this bug would not be considered release critical, hence I did not
 notice it when searching for an already submitted bug.

  Also, contrary to what's suggested earlier in the bug log, I experience
 this when running startx from a virtual console, and not only from XDM
 (which is also broken).  Purging the xdm package doesn't help either,
 I still need to downgrade both the xlibs and xserver-xfree86 packages to
 get a functional X server.

-- 
Tore Anderson

X Strike Force SVN commit: rev 161 - people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches

[X Strike Force SVN Admin]

Author: ishikawa
Date: 2003-06-08 13:25:15 -0500 (Sun, 08 Jun 2003)
New Revision: 161

Added:
   
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/057_external_XrenderXftXcursor_X11.tmpl.diff
   
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/058_external_XrenderXftXcursor_programs.diff
   
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/059_external_XrenderXftXcursor_lib.diff
Removed:
   
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/A01_external_XrenderXftXcursor_X11.tmpl.diff
   
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/A02_external_XrenderXftXcursor_programs.diff
   
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/A03_external_XrenderXftXcursor_lib.diff
Log:
renumbering external Xrender,Xft and Xcursor patches



Added: 
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/057_external_XrenderXftXcursor_X11.tmpl.diff
==
--- 
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/057_external_XrenderXftXcursor_X11.tmpl.diff
2003-06-07 20:01:57 UTC (rev 160)
+++ 
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/057_external_XrenderXftXcursor_X11.tmpl.diff
2003-06-08 18:25:15 UTC (rev 161)
@@ -0,0 +1,234 @@
+patch to be able to use external Xrender/Xft/Xcursor libraries
+
+ * add Has{Render,Xft,Xcursor}Library defines
+ * Some defines related {Render,Xft,Xcursor}Library are changed
+   to be able to use external Xrender,Xft,Xcursor libraries
+   (likes freetype2, expat, libz etc...)
+
+ This patch contains  X11.tmpl part only (some xc/lib/*/Imakefile
+and xc/programs/*/Imakefile should adapt this change)
+
+ISHIKAWA Mutsumi <[EMAIL PROTECTED]>
+
+diff -x '*~' -urN xc.orig/config/cf/X11.tmpl xc/config/cf/X11.tmpl
+--- xc.orig/config/cf/X11.tmpl 2003-06-04 05:16:04.0 +0900
 xc/config/cf/X11.tmpl  2003-06-04 05:12:39.0 +0900
+@@ -565,23 +565,29 @@
+ #ifndef BuildRender
+ #define BuildRender   YES
+ #endif
++#ifndef HasRenderLibrary
++#define HasRenderLibrary  NO
++#endif
+ #ifndef BuildRenderLibrary
+-#define BuildRenderLibrary!BuildServersOnly
++#define BuildRenderLibrary(!BuildServersOnly && !HasRenderLibrary)
++#endif
++#ifndef HasXftLibrary
++#define HasXftLibrary NO
+ #endif
+ #ifndef BuildXftLibrary
+-#define BuildXftLibrary   BuildRenderLibrary
++#define BuildXftLibrary   ((BuildRenderLibrary || 
HasRenderLibrary) && !HasXftLibrary)
+ #endif
+ #ifndef BuildXft1Library
+-#define BuildXft1Library  BuildRenderLibrary
++#define BuildXft1Library  (BuildRenderLibrary || HasRenderLibrary)
+ #endif
+ #ifndef UseFontconfig
+-#define UseFontconfig BuildXftLibrary
++#define UseFontconfig (BuildXftLibrary || HasXftLibrary)
+ #endif
+ #ifndef BuildFontconfigLibrary
+ #define BuildFontconfigLibrary(UseFontconfig && !HasFontconfig)
+ #endif
+ #ifndef UseFreetype2
+-#define UseFreetype2  (BuildXftLibrary || BuildXft1Library || 
UseFontconfig)
++#define UseFreetype2  (BuildXftLibrary || HasXftLibrary || 
BuildXft1Library || UseFontconfig)
+ #endif
+ #ifndef HasExpat
+ #define HasExpat  NO
+@@ -603,8 +609,11 @@
+ #define BuildRandRLibrary !BuildServersOnly
+ #endif
+ 
++#ifndef HasXcursorLibrary
++#define HasXcursorLibrary NO
++#endif
+ #ifndef BuildXcursorLibrary
+-#define BuildXcursorLibrary   BuildRenderLibrary
++#define BuildXcursorLibrary   ((BuildRenderLibrary || HasRenderLibrary) && 
!HasXcursorLibrary)
+ #endif
+ 
+ #ifndef BuildXcursorgen
+@@ -2374,6 +2383,7 @@
+ ProjectUnsharedLibReferences(GLW,GLw,$(GLWIDGETSRC),XBuildLibDir)
+ #endif
+ 
++#if BuildRenderLibrary
+ XRENDERLIBSRC = $(LIBSRC)/Xrender
+ #if SharedLibXrender
+ #ifndef SharedXrenderRev
+@@ -2384,6 +2394,42 @@
+ ProjectUnsharedLibReferences(XRENDER,Xrender,$(XRENDERLIBSRC),XBuildLibDir)
+ #endif
+ 
++#ifdef UseInstalled
++XRENDERINCDIR=$(INCDIR)
++#else
++XRENDERINCDIR=$(BUILDINCDIR)
++#endif
++
++XRENDERINCLUDES = -I$(XRENDERINCDIR)
++
++#else /* BuildRenderLibrary */
++
++#if HasRenderLibrary
++
++#ifndef RenderLibraryDir
++#define RenderLibraryDir /usr/X11R6
++#endif
++
++#ifndef RenderLibraryLibDir
++#define RenderLibraryLibDir RenderLibraryDir/LibDirName
++#endif
++
++#ifndef RenderLibraryIncDir
++#define RenderLibraryIncDir RenderLibraryDir/include
++#endif
++
++XRENDERDIR = RenderLibraryDir
++XRENDERLIBDIR = RenderLibraryLibDir
++XRENDERINCDIR = RenderLibraryIncDir
++XRENDERLIB = -L$(XRENDERLIBDIR) -lXrender
++DEPXRENDERLIB =
++
++XRENDERINCLUDES = -I$(XRENDERINCDIR)
++
++#endif /* HasRenderLibrary */
++
++#endif /* else BuildRenderLibrary */
++
+ XRANDRRLIBSRC = $(LIBSRC)/Xrandr
+ #if SharedLibXrandr
+ #ifndef SharedXrandrRev
+@@ -2394,6 +2440,7 @@
+ ProjectUnsharedLibReferences(XRANDR,Xrandr,$(XRANDRLIBSRC),XBuildLibDir)
+ #endif
+ 
++#if BuildXcursorLibrary
+XCURSORRLIBSRC = $(LIBSRC)/Xcursor
+ #if Sh

Bug#196554: xlibs: todays update causes every app to report "Xlib: connection to ":0.0" refused by server"

[Joerg Platte]

Am Sonntag, 8. Juni 2003 00:52 schrieb root:

> This also happens when I try to start kdm from the console.

Workaround: You can fix kdm by writing "Authorize=false" in 
/etc/kde3/kdm/kdmrc (section [X-*-Core]). 

regards,
Jörg

-- 
Hi! I'm a .signature virus! Copy me into your signature to help me spread!.-.
PGP Key: send mail with subject 'SEND PGP-KEY' PGP Key-ID: FD 4E 21 1Doo|
PGP Fingerprint: 388A872AFC5649D3 BCEC65778BE0C605  _ // /`'\
I am Ohm of Borg. Resistance is voltage divided by current. \X/ (\_;/)

Bug#196621: xserver-xfree86 / xlibs 4.2.1-7 issue - workaround

[Julien]

On Sun, Jun 08, 2003 at 07:31:25PM +0200, Julien wrote:
> Same issue here, before I restart the server to try getting rid of this
> matter. Unfortunately, X did not came up at all... I tried to fallback by
> downgrading xserver-common/xfree86, xfree86-common and all xlibs packages,
> without any result.

Correct version hereafter. Upgraded again all packages to 4.2.1-7, then
downgraded xlibs and xserver-xfree86 to 4.2.1-6 -> X starting again. I
tested with two drivers (two cards): nv and r128 (not using the generic one
'ati', since not 4.2.1-7), both are working after the fallback.

-- 
Julien.



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

Bug#196656: xfree86: does not start up with kdm

[Thomas Koenig]

Package: xfree86
Version: unavailable; reported 2003-06-08
Severity: grave
Tags: sid
Justification: renders package unusable

I just upgraded to the latest version of X (4.2.1-7), and
found that I could not start up with kdm.  The grey screen
was repeatedly respawned, finally leading to it being disabled.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux meiner 2.4.20 #1 Thu Jun 5 20:58:11 CEST 2003 i686
Locale: LANG=C, [EMAIL PROTECTED]




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

Bug#196575: Processed: ugh

[Jack Howarth]

Branden,
   We have never seen this problem with gcc 3.3 builds of XFree86
4.3.0, right? It sounds like it might be better to just push
XFree86 4.3.0 into sid and shake out the remaining bugs there.
Now that freetype6 has been regressed back to a binary compatible
state are there really that many bugs keeping 4.3.0 out of sid?
 Jack

Processed: Jeez, already reported. Merging.

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 196621 important
Bug#196621: After upgrade to 4.2.1-7, no clients can connect to the X server.
Severity set to `important'.

> reassign 196621 xlibs
Bug#196621: After upgrade to 4.2.1-7, no clients can connect to the X server.
Bug reassigned from package `xserver-xfree86' to `xlibs'.

> merge 196554 196621
Bug#196554: [xlib]: gcc3.3 screws up authentication
Bug#196621: After upgrade to 4.2.1-7, no clients can connect to the X server.
Bug#196575: [xlib]: gcc3.3 screws up authentication
Merged 196554 196575 196621.

> quit
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#196621: (no subject)

[Julien]

Same issue here, before I restart the server to try getting rid of this
matter. Unfortunately, X did not came up at all... I tried to fallback by
downgrading xserver-common/xfree86, xfree86-common and all xlibs packages,
without any result.

I get the following when trying to start(x):

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/XFree86.0.log", Time: Sun Jun  8 19:26:17 2003
(==) Using config file: "/etc/X11/XF86Config-4"
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:debug_xform.o":  No
symbols found
(EE) R128(0): No DFP detected
Could not init font path element /usr/lib/X11/fonts/Speedo, removing from
list!

waiting for X server to shut down

Issuing a 'startx -- -verbose' will not help to display more relevant
errors than the "No DFP detected".

-- 
Julien.

Bug#196554: Jeez, already reported. Merging.

[Tore Anderson]

severity 196621 important
reassign 196621 xlibs
merge 196554 196621
quit

  My apologies for the duplicate bug report, I would never have thought
 this bug would not be considered release critical, hence I did not
 notice it when searching for an already submitted bug.

  Also, contrary to what's suggested earlier in the bug log, I experience
 this when running startx from a virtual console, and not only from XDM
 (which is also broken).  Purging the xdm package doesn't help either,
 I still need to downgrade both the xlibs and xserver-xfree86 packages to
 get a functional X server.

-- 
Tore Anderson



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

X Strike Force SVN commit: rev 161 - people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches

[X Strike Force SVN Admin]

Author: ishikawa
Date: 2003-06-08 13:25:15 -0500 (Sun, 08 Jun 2003)
New Revision: 161

Added:
   
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/057_external_XrenderXftXcursor_X11.tmpl.diff
   
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/058_external_XrenderXftXcursor_programs.diff
   
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/059_external_XrenderXftXcursor_lib.diff
Removed:
   
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/A01_external_XrenderXftXcursor_X11.tmpl.diff
   
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/A02_external_XrenderXftXcursor_programs.diff
   
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/A03_external_XrenderXftXcursor_lib.diff
Log:
renumbering external Xrender,Xft and Xcursor patches



Added: 
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/057_external_XrenderXftXcursor_X11.tmpl.diff
==
--- 
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/057_external_XrenderXftXcursor_X11.tmpl.diff
2003-06-07 20:01:57 UTC (rev 160)
+++ 
people/ishikawa/4.3.0-0pre1v1-xrender-xcursor-split/patches/057_external_XrenderXftXcursor_X11.tmpl.diff
2003-06-08 18:25:15 UTC (rev 161)
@@ -0,0 +1,234 @@
+patch to be able to use external Xrender/Xft/Xcursor libraries
+
+ * add Has{Render,Xft,Xcursor}Library defines
+ * Some defines related {Render,Xft,Xcursor}Library are changed
+   to be able to use external Xrender,Xft,Xcursor libraries
+   (likes freetype2, expat, libz etc...)
+
+ This patch contains  X11.tmpl part only (some xc/lib/*/Imakefile
+and xc/programs/*/Imakefile should adapt this change)
+
+ISHIKAWA Mutsumi <[EMAIL PROTECTED]>
+
+diff -x '*~' -urN xc.orig/config/cf/X11.tmpl xc/config/cf/X11.tmpl
+--- xc.orig/config/cf/X11.tmpl 2003-06-04 05:16:04.0 +0900
 xc/config/cf/X11.tmpl  2003-06-04 05:12:39.0 +0900
+@@ -565,23 +565,29 @@
+ #ifndef BuildRender
+ #define BuildRender   YES
+ #endif
++#ifndef HasRenderLibrary
++#define HasRenderLibrary  NO
++#endif
+ #ifndef BuildRenderLibrary
+-#define BuildRenderLibrary!BuildServersOnly
++#define BuildRenderLibrary(!BuildServersOnly && !HasRenderLibrary)
++#endif
++#ifndef HasXftLibrary
++#define HasXftLibrary NO
+ #endif
+ #ifndef BuildXftLibrary
+-#define BuildXftLibrary   BuildRenderLibrary
++#define BuildXftLibrary   ((BuildRenderLibrary || HasRenderLibrary) && 
!HasXftLibrary)
+ #endif
+ #ifndef BuildXft1Library
+-#define BuildXft1Library  BuildRenderLibrary
++#define BuildXft1Library  (BuildRenderLibrary || HasRenderLibrary)
+ #endif
+ #ifndef UseFontconfig
+-#define UseFontconfig BuildXftLibrary
++#define UseFontconfig (BuildXftLibrary || HasXftLibrary)
+ #endif
+ #ifndef BuildFontconfigLibrary
+ #define BuildFontconfigLibrary(UseFontconfig && !HasFontconfig)
+ #endif
+ #ifndef UseFreetype2
+-#define UseFreetype2  (BuildXftLibrary || BuildXft1Library || UseFontconfig)
++#define UseFreetype2  (BuildXftLibrary || HasXftLibrary || BuildXft1Library 
|| UseFontconfig)
+ #endif
+ #ifndef HasExpat
+ #define HasExpat  NO
+@@ -603,8 +609,11 @@
+ #define BuildRandRLibrary !BuildServersOnly
+ #endif
+ 
++#ifndef HasXcursorLibrary
++#define HasXcursorLibrary NO
++#endif
+ #ifndef BuildXcursorLibrary
+-#define BuildXcursorLibrary   BuildRenderLibrary
++#define BuildXcursorLibrary   ((BuildRenderLibrary || HasRenderLibrary) && 
!HasXcursorLibrary)
+ #endif
+ 
+ #ifndef BuildXcursorgen
+@@ -2374,6 +2383,7 @@
+ ProjectUnsharedLibReferences(GLW,GLw,$(GLWIDGETSRC),XBuildLibDir)
+ #endif
+ 
++#if BuildRenderLibrary
+ XRENDERLIBSRC = $(LIBSRC)/Xrender
+ #if SharedLibXrender
+ #ifndef SharedXrenderRev
+@@ -2384,6 +2394,42 @@
+ ProjectUnsharedLibReferences(XRENDER,Xrender,$(XRENDERLIBSRC),XBuildLibDir)
+ #endif
+ 
++#ifdef UseInstalled
++XRENDERINCDIR=$(INCDIR)
++#else
++XRENDERINCDIR=$(BUILDINCDIR)
++#endif
++
++XRENDERINCLUDES = -I$(XRENDERINCDIR)
++
++#else /* BuildRenderLibrary */
++
++#if HasRenderLibrary
++
++#ifndef RenderLibraryDir
++#define RenderLibraryDir /usr/X11R6
++#endif
++
++#ifndef RenderLibraryLibDir
++#define RenderLibraryLibDir RenderLibraryDir/LibDirName
++#endif
++
++#ifndef RenderLibraryIncDir
++#define RenderLibraryIncDir RenderLibraryDir/include
++#endif
++
++XRENDERDIR = RenderLibraryDir
++XRENDERLIBDIR = RenderLibraryLibDir
++XRENDERINCDIR = RenderLibraryIncDir
++XRENDERLIB = -L$(XRENDERLIBDIR) -lXrender
++DEPXRENDERLIB =
++
++XRENDERINCLUDES = -I$(XRENDERINCDIR)
++
++#endif /* HasRenderLibrary */
++
++#endif /* else BuildRenderLibrary */
++
+ XRANDRRLIBSRC = $(LIBSRC)/Xrandr
+ #if SharedLibXrandr
+ #ifndef SharedXrandrRev
+@@ -2394,6 +2440,7 @@
+ ProjectUnsharedLibReferences(XRANDR,Xrandr,$(XRANDRLIBSRC),XBuildLibDir)
+ #endif
+ 
++#if BuildXcursorLibrary
+XCURSORRLIBSRC = $(LIBSRC)/Xcursor
+ #if Sha

Bug#196554: xlibs: todays update causes every app to report "Xlib: connection to ":0.0" refused by server"

[Joerg Platte]

Am Sonntag, 8. Juni 2003 00:52 schrieb root:

> This also happens when I try to start kdm from the console.

Workaround: You can fix kdm by writing "Authorize=false" in 
/etc/kde3/kdm/kdmrc (section [X-*-Core]). 

regards,
Jörg

-- 
Hi! I'm a .signature virus! Copy me into your signature to help me spread!.-.
PGP Key: send mail with subject 'SEND PGP-KEY' PGP Key-ID: FD 4E 21 1Doo|
PGP Fingerprint: 388A872AFC5649D3 BCEC65778BE0C605  _ // /`'\
I am Ohm of Borg. Resistance is voltage divided by current. \X/ (\_;/)




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

Bug#196575: xserver-xfree86 upgrade breaks X authorization

[Marius Gedminas]

On Sun, Jun 08, 2003 at 09:54:14AM -0500, Branden Robinson wrote:
> >   Xlib: connection to ":0.0" refused by server
> >   Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
> [...]
> > Plain startx used to work before I tried xdm/gdm, but now doesn't.
> 
> This data point is not consistent with any other reports.  Are you
> *sure* startx doesn't work?

Quite sure, I can reproduce it:

1) start xdm
2) log in
3) get the login screen back

At this point ~/.xsession-errors contains just three lines of text with
the same "connection refused by server" error message, coming from xrdb
this time.  (xrdb -merge ~/.Xresources is called early in my ~/.xsession
script, although it is not the first X client started -- xsetroot is the
first one, but strangely it does not complain.)

4) kill xdm
5) startx

I get the default X background pattern with an X-shaped mouse cursor,
and the following messages on the console:

[...]
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/XFree86.0.log", Time: Sun Jun  8 18:09:05 2003
(==) Using config file: "/etc/X11/XF86Config-4"
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:debug_xform.o":  No 
symbols found
Could not init font path element /usr/lib/X11/fonts/Speedo, removing from list!
AUDIT: Sun Jun  8 18:09:07 2003: 1220 X: client 1 rejected from local host
Auth name: XDM-AUTHORIZATION-1 ID: -1
Xlib: connection to ":0.0" refused by server
Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
waiting for X server to begin accepting connections .
AUDIT: Sun Jun  8 18:09:09 2003: 1220 X: client 1 rejected from local host
Auth name: XDM-AUTHORIZATION-1 ID: -1
Xlib: connection to ":0.0" refused by server
Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
..
AUDIT: Sun Jun  8 18:09:11 2003: 1220 X: client 1 rejected from local host
Auth name: XDM-AUTHORIZATION-1 ID: -1
Xlib: connection to ":0.0" refused by server
Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
.
giving up.
xinit:  unable to connect to X server
xinit:  No such process (errno 3):  Server error.

I killed the X server with Ctrl+Alt+Backspace after several seconds, I
guess, that's when xinit said "giving up".


It looks like that startx starts working again once I login successfully
with gdm2.  I guess the contents of my ~/.Xauthority have something to
do with it.

I've performing some tests with ~/.Xauthority removed:
1) startx creates two MIT-MAGIC-COOKIEs and works just fine, when
   .Xauthority is empty before running startx
2) kdm fails to show its login greeter and leaves an empty .Xauthority
   (obviously, since I never had the opportunity to log in)
3) gdm2 creates lots of MIT-MAGIC-COOKIEs and works just fine
4) xdm shows the login dialog but my .Xsession aborts with
  Xlib: connection to ":0.0" refused by server
  Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
  xrdb: Can't open display ':0'
5) xdm leaves ~/.Xauthority full of MIT-MAGIC-COOKIEs and
   XDM-AUTHORIZATION keys.  When these are present in .Xauthority file,
   startx stops working.

So it looks like the presence of XDM-AUTHORIZATION-1 keys breaks the
authorization.

I've saved copies of .Xauthority after each step.  Are you interested in
the output of 'xauth list' on each of those?

HTH,
Marius Gedminas
-- 
Westheimer's Discovery:
A couple of months in the laboratory can
frequently save a couple of hours in the library.

Bug#196575: Plain startx works

[Morgon Kanter]

For me, a plain startx will start X (and KDE) without failure, although 
trying to run kdm will still fail. Other applications that you then 
start will also work. That's a relief.

Morgon
-- 
"Luckily the Evas can run on gasoline... sad to say, they still get 
better mileage than most American cars." -- Gendo Ikari, parody of 
episode 11, Neon Genesis Evangelion.

Bug#196575: Processed: ugh

[Jack Howarth]

Branden,
   We have never seen this problem with gcc 3.3 builds of XFree86
4.3.0, right? It sounds like it might be better to just push
XFree86 4.3.0 into sid and shake out the remaining bugs there.
Now that freetype6 has been regressed back to a binary compatible
state are there really that many bugs keeping 4.3.0 out of sid?
 Jack



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

Bug#179851: acknowledged by developer (Re: Bug#179851: xserver-xfree86)

[Paul Anthony Judd]

On Thu, 6 Feb 2003 06:48, you wrote:
> xserver-xfree86

I tried :
apt-get -u -d install xserver-xfree86/testing
Reading Package Lists... Done
Building Dependency Tree... Done
E: Release 'testing' for 'xserver-xfree86' was not found

apt-get -u -d install xserver-xfree86/unstable
Reading Package Lists... Done
Building Dependency Tree... Done
E: Release 'unstable' for 'xserver-xfree86' was not found

apt-get -u  install xserver-xfree86
Reading Package Lists... Done
Building Dependency Tree... Done
Sorry, xserver-xfree86 is already the newest version.
0 packages upgraded, 0 newly installed, 0 to remove and 1  not upgraded.


bash [EMAIL PROTECTED]:~/ # apt-cache show xserver-xfree86
Package: xserver-xfree86
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 12224
Maintainer: Branden Robinson <[EMAIL PROTECTED]>
Source: xfree86
Version: 4.1.0-16
Replaces: xserver-common (<< 4.0), libxfont-xtt
Provides: xserver
Depends: debconf (>> 0.5), xserver-common (>= 4.1.0-10), libc6 (>= 2.2.4-4), 
zlib1g (>= 1:1.1.4)
Suggests: mdetect, read-edid
Conflicts: libxfont-xtt
Description: the XFree86 X server
 The XFree86 X server is an X server for several architectures and operating
 systems; its architecture was completely redesigned for the 4.0 release, and
 features a loadable module system in which required modules are loaded on
 demand by a single server binary as opposed to the video card-specific X
 servers of the 3.x release.
 .
 The XFree86 server supports most modern graphics hardware from most vendors,
 and supersedes most version 3.x XFree86 X servers.  See
  for information on its support for
 your particular hardware.
 .
 If the mdetect and read-edid packages are present, the debconf scripts in
 this package will use them to attempt automatic configuration of your mouse
 and monitor.
 .
 Note that on the hppa architecture, the server's loadable module support
 is not present, and therefore the XFree86 server is a (very large) single
 binary.

bash [EMAIL PROTECTED]:~/ # apt-cache showpkg xserver-xfree86
Package: xserver-xfree86
Versions:
4.1.0-16(/var/lib/dpkg/status)

Reverse Depends:
  xfree86-common,xserver-xfree86
  xserver-common,xserver-xfree86
  xlibmesa3,xserver-xfree86 4.0.2
  x-window-system-core,xserver-xfree86
Dependencies:
4.1.0-16 - debconf (4 0.5) xserver-common (2 4.1.0-10) libc6 (2 2.2.4-4) 
zlib1g (2 1:1.1.4) mdetect (0 (null)) read-edid (0 (null)) libxfont-xtt (0 
(null)) xserver-common (3 4.0) libxfont-xtt (0 (null))
Provides:
4.1.0-16 - xserver
Reverse Provides:
bash [EMAIL PROTECTED]:~/ #

 what now 
-- 
Regards Paul,
<[EMAIL PROTECTED]> 

Bug#196621: (no subject)

[Julien]

Same issue here, before I restart the server to try getting rid of this
matter. Unfortunately, X did not came up at all... I tried to fallback by
downgrading xserver-common/xfree86, xfree86-common and all xlibs packages,
without any result.

I get the following when trying to start(x):

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/XFree86.0.log", Time: Sun Jun  8 19:26:17 2003
(==) Using config file: "/etc/X11/XF86Config-4"
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:debug_xform.o":  No
symbols found
(EE) R128(0): No DFP detected
Could not init font path element /usr/lib/X11/fonts/Speedo, removing from
list!

waiting for X server to shut down

Issuing a 'startx -- -verbose' will not help to display more relevant
errors than the "No DFP detected".

-- 
Julien.



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

Bug#196554: xlibs: todays update causes every app to report "Xlib: connection to ":0.0" refused by server"

[Dr. David Alan Gilbert]

* Branden Robinson ([EMAIL PROTECTED]) wrote:

> When I experienced this problem on PowerPC while preparing 4.2.1-7, I
> found that downgrading xserver-xfree86 to 4.2.1-6 but leaving everything
> else at -7 worked, too.
> 
> I don't see why downgrading xlibs-{dev,pic} would help anything at all;
> you should be able to re-upgrade those and not change the way your
> system behaves in this regard.
> 
> Can you confirm these two hypotheses for me?

Well I haven't quit X throughout this process; so I doubt its the
server.

If I do:

apt-get install xlibs=4.2.1-7

I'm back to the situation of being unable to run clients and then if I
do:

apt-get install xlibs=4.2.1-6 xlibs-dev=4.2.1-6 xlibs-pic=4.2.1-6

I can run the clients again.

Note the X server has been running since Saturday morning before I ran
the upgrade that got me 4.2.1-7. Its a kdm session I'm in.

> By the way, the reason this broke is because of GCC 3.3 (read the
> package changelog).  I was hoping they wouldn't get it wrong on i386,
> but I guess I was mistaken.

I guess it could be kdm/the server/the libraries disagreeing and that
its just a matter of the two being the same - so perhaps a new library
would work with a authority file created by a new server/kdm/whatever ?

Dave
  Have a happy GNU millennium! --   
/ Dr. David Alan Gilbert| Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#196575: xserver-xfree86 upgrade breaks X authorization

[Branden Robinson]

On Sun, Jun 08, 2003 at 12:46:31PM +0300, Marius Gedminas wrote:
> Package: xserver-xfree86
> Version: 4.2.1-7
> Followup-For: Bug #196575
> 
> After upgrading several X packages (xlibs, xbase-clients,
> xserver-common, xserver-xfree86 and more) I was unable to start any new
> X programs.  For example, xterm would complain
> 
>   Xlib: connection to ":0.0" refused by server
>   Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
[...]
> Plain startx used to work before I tried xdm/gdm, but now doesn't.

This data point is not consistent with any other reports.  Are you
*sure* startx doesn't work?

If it doesn't work, is it because of the error messages above, or
because of some other reason (e.g., a bad $HOME/.xinitrc)?

-- 
G. Branden Robinson|I am sorry, but what you have
Debian GNU/Linux   |mistaken for malicious intent is
[EMAIL PROTECTED] |nothing more than sheer
http://people.debian.org/~branden/ |incompetence! -- J. L. Rizzo II


pgpHUwJkndBjT.pgp
Description: PGP signature

Bug#196554: xlibs: todays update causes every app to report "Xlib: connection to ":0.0" refused by server"

[Branden Robinson]

On Sun, Jun 08, 2003 at 09:55:17AM +0200, Ralf Hildebrandt wrote:
> * Daniel Stone <[EMAIL PROTECTED]>:
> 
> > > This also happens when I try to start kdm from the console.
> > 
> > Yeah, this is a problem with ?dm and authorization. Try 'startx' from
> > the command line.
> 
> Yes, this works.
>  
> > For the BTS, the problem is that gcc3.3 screws up authentication somehow
> > - either cpp3.3's semantics changing, or miscompiled code. This has been
> > seen to happen on both powerpc and i386 now, so it's not a
> > single-architecture problem. Ugh. :(
> 
> Shit happens unlimited.
> So is it kdm's or xlibs's fault?

GCC's.

-- 
G. Branden Robinson|I have a truly elegant proof of the
Debian GNU/Linux   |above, but it is too long to fit
[EMAIL PROTECTED] |into this .signature file.
http://people.debian.org/~branden/ |


pgpoJdXrbJ8A8.pgp
Description: PGP signature

Bug#196554: xlibs: todays update causes every app to report "Xlib: connection to ":0.0" refused by server"

[Branden Robinson]

On Sun, Jun 08, 2003 at 01:13:32AM +0100, Dr. David Alan Gilbert wrote:
> Hi,
>   Yep - this also happens here - (sid on x86, Radeon); note that
> I can confirm it is xlibs since doing:
> 
> apt-get install xlibs=4.2.1-6 xlibs-dev=4.2.1-6 xlibs-pic=4.2.1-6
> 
> gets me a working X again.

When I experienced this problem on PowerPC while preparing 4.2.1-7, I
found that downgrading xserver-xfree86 to 4.2.1-6 but leaving everything
else at -7 worked, too.

I don't see why downgrading xlibs-{dev,pic} would help anything at all;
you should be able to re-upgrade those and not change the way your
system behaves in this regard.

Can you confirm these two hypotheses for me?

By the way, the reason this broke is because of GCC 3.3 (read the
package changelog).  I was hoping they wouldn't get it wrong on i386,
but I guess I was mistaken.

-- 
G. Branden Robinson|I have a truly elegant proof of the
Debian GNU/Linux   |above, but it is too long to fit
[EMAIL PROTECTED] |into this .signature file.
http://people.debian.org/~branden/ |


pgpQoYpq0CGwL.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Branden Robinson]

On Sun, Jun 08, 2003 at 06:18:20AM -0500, Debian Bug Tracking System wrote:
> Processing commands for [EMAIL PROTECTED]:
> 
> > reassign 196575 xlibs
> Bug#196575: [xlib]: gcc3.3 screws up authentication
> Bug reassigned from package `xserver-xfree86' to `xlibs'.
> 
> > merge 196554 196575
> Bug#196554: [xlib]: gcc3.3 screws up authentication
> Bug#196575: [xlib]: gcc3.3 screws up authentication
> Merged 196554 196575.

It is premature to say this is an Xlib problem.  I was able to make the
problem go away on my pre-4.2.1-7 builds by downgrading *only*
xserver-xfree86 to 4.2.1-6.

Now, of course, xdm works fine for me in 4.2.1-7 because of this:

  + GCC 3.3 appears to produce bad code for PowerPC at the optimization
level required by Debian Policy (the X server cannot validate
XDM-AUTHORIZATION-1 keys); when building on PowerPC, set
DefaultGcc2OptimizeOpt to -O instead of -O2

I guess it produces bad code for *all* architectures at -O2.  Wonderful.

-- 
G. Branden Robinson|   The last Christian died on the
Debian GNU/Linux   |   cross.
[EMAIL PROTECTED] |   -- Friedrich Nietzsche
http://people.debian.org/~branden/ |


pgpyws2ODq4o8.pgp
Description: PGP signature

Bug#196621: After upgrade to 4.2.1-7, no clients can connect to the X server.

[Tore Anderson]

Package: xserver-xfree86
Severity: grave

  No clients can connect to the X server after the upgrade to 4.2.1-7,
 making X unusable.  The error message, which is repeated to the console
 ad infinitum, reads:

AUDIT: Sun Jun  8 15:47:34 2003: 19251 X: client 1 rejected from local host
Auth name: XDM-AUTHORIZATION-1 ID: -1

  19251 is the pid of the X server.  The problem perishes after downgrading
 both the xlibs and xserver-xfree86 packages to the 4.2.1-6 version (so the
 bug could easily be in the xlibs package instead of xserver-xfree86).

  I've attached the logfile from 4.2.1-6 and -7, the Dexconf-generated
 configuration file, and output from 'debconf-show xserver-xfree86'.  Let
 me know of you need more debug information.

-- 
Tore Anderson

This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to XFree86@XFree86.Org and patches submitted
to [EMAIL PROTECTED]  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs)

XFree86 Version 4.2.1.1 (Debian 4.2.1-6 20030225230350 [EMAIL PROTECTED]) / X 
Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 18 October 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.20-586tsc i686 [ELF] 
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/XFree86.0.log", Time: Sun Jun  8 15:50:16 2003
(==) Using config file: "/etc/X11/XF86Config-4"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) |   |-->Monitor "Generic Monitor"
(**) |   |-->Device "Generic Video Card"
(**) |-->Input Device "Generic Keyboard"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "no"
(**) XKB: layout: "no"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Configured Mouse"
(WW) The directory "/usr/lib/X11/fonts/CID" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist.
Entry deleted from font path.
(**) FontPath set to 
"unix/:7100,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi"
(==) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(--) using VT number 7

(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.1
XFree86 Video Driver: 0.5
XFree86 XInput driver : 0.3
XFree86 Server Extension : 0.1
XFree86 Font Renderer : 0.3
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="The XFree86 Project"
compiled for 4.2.1.1, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.3
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
compiled for 4.2.1.1, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,7190 card , rev 03 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,7191 card , rev 03 class 06,04,00 hdr 01
(II) PCI: 00:04:0: chip 104c,ac1c card 1800, rev 01 class 06,07,00 hdr 82
(II) PCI: 00:04:1: chip 104c,ac1c card 3000, rev 01 class 06,07,00 hdr 82
(II) PCI: 00:07:0: chip 8086,7110 card , rev 02 class 06,80,00 hdr 80
(II) PCI: 00:07:1: chip 8086,7111 card , rev 01 class 01,01,80 hdr 00
(II) PCI: 00:07:2: chip 8086,7112 card , rev 01 class 0c,03,00 hdr 00
(II) PCI: 00:07:3: chip 8086,7113 card , rev 03 class 06,80,00 hdr 00
(II) PCI: 00:08:0: chip 125d,1978 card 1028,00cc rev 10 class 04,01,00 hdr 00
(II) PCI: 01:00:0: chip 1002,4c46 card 1028,00cc rev 02 class 03,00,00 hdr 00
(II) PCI: 02:00:0: chip 115d,0003 card 115d,1181 rev 03 class 02,00,00 hdr 80
(II) PCI: 02:00:1: chip 115d,0103 card 115d,1181 rev 03 class 07,00,02 hdr 80
(II) PCI: End of PCI scan
(II) LoadModule: "scanpci"
(II) Loading /usr/X11R6/lib/modules/libscanpci.a
(II) Module scanpci: vendor="The XFree86 Project"
compiled for 4.2.1.1, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(II) UnloadModule

Bug#196622: xfree86-common: latest update breaks KDE startup

[Neil Darlow]

Package: xfree86-common
Version: 4.2.1-7
Severity: normal


This update causes KDE startup, via KDM, to fail. Approximately 3
attempts at server startup occur before a fallback to console login
results.

A number of numerically named directories, owned by root and mode 700,
are placed in /tmp/ but I can't see any other useful evidence of what
has gone wrong.

Regards,
Neil Darlow M.Sc.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux ideal 2.4.20-epia #1 Fri May 30 15:19:54 BST 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages xfree86-common depends on:
ii  debconf   1.2.39 Debian configuration management sy
ii  debianutils   2.5.2  Miscellaneous utilities specific t

-- debconf information:
  xfree86-common/experimental_packages: 

Bug#196575: xserver-xfree86 upgrade breaks X authorization

[Marius Gedminas]

On Sun, Jun 08, 2003 at 09:54:14AM -0500, Branden Robinson wrote:
> >   Xlib: connection to ":0.0" refused by server
> >   Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
> [...]
> > Plain startx used to work before I tried xdm/gdm, but now doesn't.
> 
> This data point is not consistent with any other reports.  Are you
> *sure* startx doesn't work?

Quite sure, I can reproduce it:

1) start xdm
2) log in
3) get the login screen back

At this point ~/.xsession-errors contains just three lines of text with
the same "connection refused by server" error message, coming from xrdb
this time.  (xrdb -merge ~/.Xresources is called early in my ~/.xsession
script, although it is not the first X client started -- xsetroot is the
first one, but strangely it does not complain.)

4) kill xdm
5) startx

I get the default X background pattern with an X-shaped mouse cursor,
and the following messages on the console:

[...]
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/XFree86.0.log", Time: Sun Jun  8 18:09:05 2003
(==) Using config file: "/etc/X11/XF86Config-4"
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:debug_xform.o":  No symbols 
found
Could not init font path element /usr/lib/X11/fonts/Speedo, removing from list!
AUDIT: Sun Jun  8 18:09:07 2003: 1220 X: client 1 rejected from local host
Auth name: XDM-AUTHORIZATION-1 ID: -1
Xlib: connection to ":0.0" refused by server
Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
waiting for X server to begin accepting connections .
AUDIT: Sun Jun  8 18:09:09 2003: 1220 X: client 1 rejected from local host
Auth name: XDM-AUTHORIZATION-1 ID: -1
Xlib: connection to ":0.0" refused by server
Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
..
AUDIT: Sun Jun  8 18:09:11 2003: 1220 X: client 1 rejected from local host
Auth name: XDM-AUTHORIZATION-1 ID: -1
Xlib: connection to ":0.0" refused by server
Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
.
giving up.
xinit:  unable to connect to X server
xinit:  No such process (errno 3):  Server error.

I killed the X server with Ctrl+Alt+Backspace after several seconds, I
guess, that's when xinit said "giving up".


It looks like that startx starts working again once I login successfully
with gdm2.  I guess the contents of my ~/.Xauthority have something to
do with it.

I've performing some tests with ~/.Xauthority removed:
1) startx creates two MIT-MAGIC-COOKIEs and works just fine, when
   .Xauthority is empty before running startx
2) kdm fails to show its login greeter and leaves an empty .Xauthority
   (obviously, since I never had the opportunity to log in)
3) gdm2 creates lots of MIT-MAGIC-COOKIEs and works just fine
4) xdm shows the login dialog but my .Xsession aborts with
  Xlib: connection to ":0.0" refused by server
  Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
  xrdb: Can't open display ':0'
5) xdm leaves ~/.Xauthority full of MIT-MAGIC-COOKIEs and
   XDM-AUTHORIZATION keys.  When these are present in .Xauthority file,
   startx stops working.

So it looks like the presence of XDM-AUTHORIZATION-1 keys breaks the
authorization.

I've saved copies of .Xauthority after each step.  Are you interested in
the output of 'xauth list' on each of those?

HTH,
Marius Gedminas
-- 
Westheimer's Discovery:
A couple of months in the laboratory can
frequently save a couple of hours in the library.



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

Bug#196575: Plain startx works

[Morgon Kanter]

For me, a plain startx will start X (and KDE) without failure, although 
trying to run kdm will still fail. Other applications that you then 
start will also work. That's a relief.

Morgon
-- 
"Luckily the Evas can run on gasoline... sad to say, they still get 
better mileage than most American cars." -- Gendo Ikari, parody of 
episode 11, Neon Genesis Evangelion.



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

Bug#179851: acknowledged by developer (Re: Bug#179851: xserver-xfree86)

[Paul Anthony Judd]

On Thu, 6 Feb 2003 06:48, you wrote:
> xserver-xfree86

I tried :
apt-get -u -d install xserver-xfree86/testing
Reading Package Lists... Done
Building Dependency Tree... Done
E: Release 'testing' for 'xserver-xfree86' was not found

apt-get -u -d install xserver-xfree86/unstable
Reading Package Lists... Done
Building Dependency Tree... Done
E: Release 'unstable' for 'xserver-xfree86' was not found

apt-get -u  install xserver-xfree86
Reading Package Lists... Done
Building Dependency Tree... Done
Sorry, xserver-xfree86 is already the newest version.
0 packages upgraded, 0 newly installed, 0 to remove and 1  not upgraded.


bash [EMAIL PROTECTED]:~/ # apt-cache show xserver-xfree86
Package: xserver-xfree86
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 12224
Maintainer: Branden Robinson <[EMAIL PROTECTED]>
Source: xfree86
Version: 4.1.0-16
Replaces: xserver-common (<< 4.0), libxfont-xtt
Provides: xserver
Depends: debconf (>> 0.5), xserver-common (>= 4.1.0-10), libc6 (>= 2.2.4-4), 
zlib1g (>= 1:1.1.4)
Suggests: mdetect, read-edid
Conflicts: libxfont-xtt
Description: the XFree86 X server
 The XFree86 X server is an X server for several architectures and operating
 systems; its architecture was completely redesigned for the 4.0 release, and
 features a loadable module system in which required modules are loaded on
 demand by a single server binary as opposed to the video card-specific X
 servers of the 3.x release.
 .
 The XFree86 server supports most modern graphics hardware from most vendors,
 and supersedes most version 3.x XFree86 X servers.  See
  for information on its support for
 your particular hardware.
 .
 If the mdetect and read-edid packages are present, the debconf scripts in
 this package will use them to attempt automatic configuration of your mouse
 and monitor.
 .
 Note that on the hppa architecture, the server's loadable module support
 is not present, and therefore the XFree86 server is a (very large) single
 binary.

bash [EMAIL PROTECTED]:~/ # apt-cache showpkg xserver-xfree86
Package: xserver-xfree86
Versions:
4.1.0-16(/var/lib/dpkg/status)

Reverse Depends:
  xfree86-common,xserver-xfree86
  xserver-common,xserver-xfree86
  xlibmesa3,xserver-xfree86 4.0.2
  x-window-system-core,xserver-xfree86
Dependencies:
4.1.0-16 - debconf (4 0.5) xserver-common (2 4.1.0-10) libc6 (2 2.2.4-4) 
zlib1g (2 1:1.1.4) mdetect (0 (null)) read-edid (0 (null)) libxfont-xtt (0 
(null)) xserver-common (3 4.0) libxfont-xtt (0 (null))
Provides:
4.1.0-16 - xserver
Reverse Provides:
bash [EMAIL PROTECTED]:~/ #

 what now 
-- 
Regards Paul,
<[EMAIL PROTECTED]> 



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

Bug#196554: xlibs: todays update causes every app to report "Xlib: connection to ":0.0" refused by server"

[Dr. David Alan Gilbert]

* Branden Robinson ([EMAIL PROTECTED]) wrote:

> When I experienced this problem on PowerPC while preparing 4.2.1-7, I
> found that downgrading xserver-xfree86 to 4.2.1-6 but leaving everything
> else at -7 worked, too.
> 
> I don't see why downgrading xlibs-{dev,pic} would help anything at all;
> you should be able to re-upgrade those and not change the way your
> system behaves in this regard.
> 
> Can you confirm these two hypotheses for me?

Well I haven't quit X throughout this process; so I doubt its the
server.

If I do:

apt-get install xlibs=4.2.1-7

I'm back to the situation of being unable to run clients and then if I
do:

apt-get install xlibs=4.2.1-6 xlibs-dev=4.2.1-6 xlibs-pic=4.2.1-6

I can run the clients again.

Note the X server has been running since Saturday morning before I ran
the upgrade that got me 4.2.1-7. Its a kdm session I'm in.

> By the way, the reason this broke is because of GCC 3.3 (read the
> package changelog).  I was hoping they wouldn't get it wrong on i386,
> but I guess I was mistaken.

I guess it could be kdm/the server/the libraries disagreeing and that
its just a matter of the two being the same - so perhaps a new library
would work with a authority file created by a new server/kdm/whatever ?

Dave
  Have a happy GNU millennium! --   
/ Dr. David Alan Gilbert| Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
 \ _|_ http://www.treblig.org   |___/



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

Bug#196575: xserver-xfree86 upgrade breaks X authorization

[Branden Robinson]

On Sun, Jun 08, 2003 at 12:46:31PM +0300, Marius Gedminas wrote:
> Package: xserver-xfree86
> Version: 4.2.1-7
> Followup-For: Bug #196575
> 
> After upgrading several X packages (xlibs, xbase-clients,
> xserver-common, xserver-xfree86 and more) I was unable to start any new
> X programs.  For example, xterm would complain
> 
>   Xlib: connection to ":0.0" refused by server
>   Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
[...]
> Plain startx used to work before I tried xdm/gdm, but now doesn't.

This data point is not consistent with any other reports.  Are you
*sure* startx doesn't work?

If it doesn't work, is it because of the error messages above, or
because of some other reason (e.g., a bad $HOME/.xinitrc)?

-- 
G. Branden Robinson|I am sorry, but what you have
Debian GNU/Linux   |mistaken for malicious intent is
[EMAIL PROTECTED] |nothing more than sheer
http://people.debian.org/~branden/ |incompetence! -- J. L. Rizzo II


pgp0.pgp
Description: PGP signature

Bug#196554: xlibs: todays update causes every app to report "Xlib: connection to ":0.0" refused by server"

[Branden Robinson]

On Sun, Jun 08, 2003 at 09:55:17AM +0200, Ralf Hildebrandt wrote:
> * Daniel Stone <[EMAIL PROTECTED]>:
> 
> > > This also happens when I try to start kdm from the console.
> > 
> > Yeah, this is a problem with ?dm and authorization. Try 'startx' from
> > the command line.
> 
> Yes, this works.
>  
> > For the BTS, the problem is that gcc3.3 screws up authentication somehow
> > - either cpp3.3's semantics changing, or miscompiled code. This has been
> > seen to happen on both powerpc and i386 now, so it's not a
> > single-architecture problem. Ugh. :(
> 
> Shit happens unlimited.
> So is it kdm's or xlibs's fault?

GCC's.

-- 
G. Branden Robinson|I have a truly elegant proof of the
Debian GNU/Linux   |above, but it is too long to fit
[EMAIL PROTECTED] |into this .signature file.
http://people.debian.org/~branden/ |


pgp0.pgp
Description: PGP signature

Bug#196554: xlibs: todays update causes every app to report "Xlib: connection to ":0.0" refused by server"

[Branden Robinson]

On Sun, Jun 08, 2003 at 01:13:32AM +0100, Dr. David Alan Gilbert wrote:
> Hi,
>   Yep - this also happens here - (sid on x86, Radeon); note that
> I can confirm it is xlibs since doing:
> 
> apt-get install xlibs=4.2.1-6 xlibs-dev=4.2.1-6 xlibs-pic=4.2.1-6
> 
> gets me a working X again.

When I experienced this problem on PowerPC while preparing 4.2.1-7, I
found that downgrading xserver-xfree86 to 4.2.1-6 but leaving everything
else at -7 worked, too.

I don't see why downgrading xlibs-{dev,pic} would help anything at all;
you should be able to re-upgrade those and not change the way your
system behaves in this regard.

Can you confirm these two hypotheses for me?

By the way, the reason this broke is because of GCC 3.3 (read the
package changelog).  I was hoping they wouldn't get it wrong on i386,
but I guess I was mistaken.

-- 
G. Branden Robinson|I have a truly elegant proof of the
Debian GNU/Linux   |above, but it is too long to fit
[EMAIL PROTECTED] |into this .signature file.
http://people.debian.org/~branden/ |


pgp0.pgp
Description: PGP signature

Bug#196575: Processed: ugh

[Branden Robinson]

On Sun, Jun 08, 2003 at 06:18:20AM -0500, Debian Bug Tracking System wrote:
> Processing commands for [EMAIL PROTECTED]:
> 
> > reassign 196575 xlibs
> Bug#196575: [xlib]: gcc3.3 screws up authentication
> Bug reassigned from package `xserver-xfree86' to `xlibs'.
> 
> > merge 196554 196575
> Bug#196554: [xlib]: gcc3.3 screws up authentication
> Bug#196575: [xlib]: gcc3.3 screws up authentication
> Merged 196554 196575.

It is premature to say this is an Xlib problem.  I was able to make the
problem go away on my pre-4.2.1-7 builds by downgrading *only*
xserver-xfree86 to 4.2.1-6.

Now, of course, xdm works fine for me in 4.2.1-7 because of this:

  + GCC 3.3 appears to produce bad code for PowerPC at the optimization
level required by Debian Policy (the X server cannot validate
XDM-AUTHORIZATION-1 keys); when building on PowerPC, set
DefaultGcc2OptimizeOpt to -O instead of -O2

I guess it produces bad code for *all* architectures at -O2.  Wonderful.

-- 
G. Branden Robinson|   The last Christian died on the
Debian GNU/Linux   |   cross.
[EMAIL PROTECTED] |   -- Friedrich Nietzsche
http://people.debian.org/~branden/ |


pgp0.pgp
Description: PGP signature

Bug#196621: After upgrade to 4.2.1-7, no clients can connect to the X server.

[Tore Anderson]

Package: xserver-xfree86
Severity: grave

  No clients can connect to the X server after the upgrade to 4.2.1-7,
 making X unusable.  The error message, which is repeated to the console
 ad infinitum, reads:

AUDIT: Sun Jun  8 15:47:34 2003: 19251 X: client 1 rejected from local host
Auth name: XDM-AUTHORIZATION-1 ID: -1

  19251 is the pid of the X server.  The problem perishes after downgrading
 both the xlibs and xserver-xfree86 packages to the 4.2.1-6 version (so the
 bug could easily be in the xlibs package instead of xserver-xfree86).

  I've attached the logfile from 4.2.1-6 and -7, the Dexconf-generated
 configuration file, and output from 'debconf-show xserver-xfree86'.  Let
 me know of you need more debug information.

-- 
Tore Anderson

This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to [EMAIL PROTECTED] and patches submitted
to [EMAIL PROTECTED]  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs)

XFree86 Version 4.2.1.1 (Debian 4.2.1-6 20030225230350 [EMAIL PROTECTED]) / X Window 
System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 18 October 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.20-586tsc i686 [ELF] 
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/XFree86.0.log", Time: Sun Jun  8 15:50:16 2003
(==) Using config file: "/etc/X11/XF86Config-4"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) |   |-->Monitor "Generic Monitor"
(**) |   |-->Device "Generic Video Card"
(**) |-->Input Device "Generic Keyboard"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "no"
(**) XKB: layout: "no"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Configured Mouse"
(WW) The directory "/usr/lib/X11/fonts/CID" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist.
Entry deleted from font path.
(**) FontPath set to 
"unix/:7100,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi"
(==) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(--) using VT number 7

(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.1
XFree86 Video Driver: 0.5
XFree86 XInput driver : 0.3
XFree86 Server Extension : 0.1
XFree86 Font Renderer : 0.3
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="The XFree86 Project"
compiled for 4.2.1.1, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.3
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
compiled for 4.2.1.1, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,7190 card , rev 03 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,7191 card , rev 03 class 06,04,00 hdr 01
(II) PCI: 00:04:0: chip 104c,ac1c card 1800, rev 01 class 06,07,00 hdr 82
(II) PCI: 00:04:1: chip 104c,ac1c card 3000, rev 01 class 06,07,00 hdr 82
(II) PCI: 00:07:0: chip 8086,7110 card , rev 02 class 06,80,00 hdr 80
(II) PCI: 00:07:1: chip 8086,7111 card , rev 01 class 01,01,80 hdr 00
(II) PCI: 00:07:2: chip 8086,7112 card , rev 01 class 0c,03,00 hdr 00
(II) PCI: 00:07:3: chip 8086,7113 card , rev 03 class 06,80,00 hdr 00
(II) PCI: 00:08:0: chip 125d,1978 card 1028,00cc rev 10 class 04,01,00 hdr 00
(II) PCI: 01:00:0: chip 1002,4c46 card 1028,00cc rev 02 class 03,00,00 hdr 00
(II) PCI: 02:00:0: chip 115d,0003 card 115d,1181 rev 03 class 02,00,00 hdr 80
(II) PCI: 02:00:1: chip 115d,0103 card 115d,1181 rev 03 class 07,00,02 hdr 80
(II) PCI: End of PCI scan
(II) LoadModule: "scanpci"
(II) Loading /usr/X11R6/lib/modules/libscanpci.a
(II) Module scanpci: vendor="The XFree86 Project"
compiled for 4.2.1.1, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(II) UnloadModule: 

Bug#196622: xfree86-common: latest update breaks KDE startup

[Neil Darlow]

Package: xfree86-common
Version: 4.2.1-7
Severity: normal


This update causes KDE startup, via KDM, to fail. Approximately 3
attempts at server startup occur before a fallback to console login
results.

A number of numerically named directories, owned by root and mode 700,
are placed in /tmp/ but I can't see any other useful evidence of what
has gone wrong.

Regards,
Neil Darlow M.Sc.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux ideal 2.4.20-epia #1 Fri May 30 15:19:54 BST 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages xfree86-common depends on:
ii  debconf   1.2.39 Debian configuration management sy
ii  debianutils   2.5.2  Miscellaneous utilities specific t

-- debconf information:
  xfree86-common/experimental_packages: 




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

Re: RFC: define FontLibSharedFreeType=NO

[ISHIKAWA Mutsumi]

> In <[EMAIL PROTECTED]> 
>   Anthony Fok <[EMAIL PROTECTED]> wrote:
>> Hello,

>> Does the same crash exists between libfreetype6_2.1.3-2 and 2.1.3-3? In
>> 2.1.3-4 (which I uploaded this morning), I tried to revert the change with
>> respect to PS_FontInfoRec (while going to CVS 2003-06-07), and I had been
>> wondering whether I did it correctly or not.
>>
>> My apologies for the troubles caused.

 Ah..Oops, soory.

 I miswrote 2.1.4-2 as 2.1.4-3 and 2.1.4-3 as 2.1.4-4...
 I'm talking about changes between libfreetype6_2.1.4-2 and -3.

 I am sorry to make it get confused.

 I've not checked libfreetype6_2.1.4-4 yet.


>> On Sun, Jun 08, 2003 at 07:36:13PM +0900, ISHIKAWA Mutsumi wrote:
>> > > In <[EMAIL PROTECTED]> 
>> > >  Branden Robinson <[EMAIL PROTECTED]> wrote:
>> > 
>> > >> On Sat, Jun 07, 2003 at 11:20:01PM +0900, ISHIKAWA Mutsumi wrote:
>> > >> > >> I got a report in private mail (grrr) from a person who ran into 
>> > >> > >> the
>> > >> > >> very problem you describe, so I appreciate you tracking this down 
>> > >> > >> and
>> > >> > >> fixing it.  Your analysis looks reasonable and I agree with your
>> > >> > >> solution.
>> > >> > 
>> > >> >  Sorry, I found my mistakes by my self.
>> > >> > 
>> > >> >  1) PS_FontInfoRec was not changed between FreeeType 2.1.3 and
>> > >> > 2.1.4. It makes after FreeType 2.1.4 release (please see
>> > >> > 
>> > >> > freetype-2.1.4/debian/patches/001-freetype-2.1.4+cvs20030601.diff).
>> > >>
>> > >> If this is true, then, FreeType maintainer: *please stop doing this*.
>> > >>
>> > >> Debian needs to have FreeType packages that are compatible with the rest
>> > >> of the world's FreeType packages.
>> > >>
>> > >> Perhaps what we really need is a freetype-snapshot package, which ships
>> > >> a libfreetype6-snapshot package which Conflicts/Replaces/Provides:
>> > >> libfreetype6.  For reasons that should be obvious, there should be no
>> > >> snapshot -dev package at all.
>> > >>
>> > >> Please, please, please, I beg of you, do not break binary compatibility
>> > >> in library packages.
>> > 
>> >  Humm, I found a message from Werner LEMBERG posted to
>> > [EMAIL PROTECTED] I believe libfreetype6 incompatible between
>> > 2.1.4-3 and 2.1.4-4.
>> > 
>> >   Application build with libfreetype6_2.1.4-4 (use PS_FontInfoRec)
>> > will crash with libfreetype6_2.1.4-3.
>> > 
>> >   Application build with libfreetype6_2.1.4-3 (use PS_FontInfoRec)
>> > will crash with libfreetype6_2.1.4-4.
>> > 
>> >  But SONAME is not changed yet (on upstream).
>> > 
>> > 
>> > > In <[EMAIL PROTECTED]> 
>> > >  Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>> > >> >
>> > >> >You might want to reconsider the change...
>> > >> > 
>> > >> > * src/type1/t1tokens.h: Change italic_angle, is_fixed_pitch,
>> > >> > underline_position, and underline_thickness to pointers.  
>> > >> > Change
>> > >> > the type of the latter two to `fixed'.
>> > >> > 
>> > >> > in current freetype6 without a change in version numbering of the 
>> > >> > shared
>> > >> > libraries.
>> > >>
>> > >> Our normal strategy is to increase the shared library version number
>> > >> right before a new release (as suggested by libtool).  We will do
>> > >> that, of course, but not now.
>> > >>
>> > >> Is there a better strategy?
>> > >>
>> > >>
>> > >> Werner

-- 
ISHIKAWA Mutsumi
 <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>

Processed: duplicate bugs go whoooo whooooooo

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 196575 important
Bug#196575: xserver-xfree86 (and related packages from source) upgrade breaks 
kdm, sylpheed-claws
Severity set to `important'.

> retitle 196575 [xlib]: gcc3.3 screws up authentication
Bug#196575: xserver-xfree86 (and related packages from source) upgrade breaks 
kdm, sylpheed-claws
Changed Bug title.

> tags 196575 = patch sid sarge
Bug#196575: [xlib]: gcc3.3 screws up authentication
There were no tags set.
Tags set to: patch, sid, sarge

> merge 196554 196575
Bug#196554: [xlib]: gcc3.3 screws up authentication
Bug#196575: [xlib]: gcc3.3 screws up authentication
Mismatch - only Bugs in same state can be merged:
Values for `package' don't match:
 #196554 has `xlibs';
 #196575 has `xserver-xfree86'

> thanks
Stopping processing here.

Please contact me if you need assistance.

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

Processed: ugh

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 196575 xlibs
Bug#196575: [xlib]: gcc3.3 screws up authentication
Bug reassigned from package `xserver-xfree86' to `xlibs'.

> merge 196554 196575
Bug#196554: [xlib]: gcc3.3 screws up authentication
Bug#196575: [xlib]: gcc3.3 screws up authentication
Merged 196554 196575.

> --
Stopping processing here.

Please contact me if you need assistance.

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

Re: RFC: define FontLibSharedFreeType=NO

[Anthony Fok]

Hello,

Does the same crash exists between libfreetype6_2.1.3-2 and 2.1.3-3? In
2.1.3-4 (which I uploaded this morning), I tried to revert the change with
respect to PS_FontInfoRec (while going to CVS 2003-06-07), and I had been
wondering whether I did it correctly or not.

My apologies for the troubles caused.

Anthony

On Sun, Jun 08, 2003 at 07:36:13PM +0900, ISHIKAWA Mutsumi wrote:
> > In <[EMAIL PROTECTED]> 
> > Branden Robinson <[EMAIL PROTECTED]> wrote:
> 
> >> On Sat, Jun 07, 2003 at 11:20:01PM +0900, ISHIKAWA Mutsumi wrote:
> >> > >> I got a report in private mail (grrr) from a person who ran into the
> >> > >> very problem you describe, so I appreciate you tracking this down and
> >> > >> fixing it.  Your analysis looks reasonable and I agree with your
> >> > >> solution.
> >> > 
> >> >  Sorry, I found my mistakes by my self.
> >> > 
> >> >  1) PS_FontInfoRec was not changed between FreeeType 2.1.3 and
> >> > 2.1.4. It makes after FreeType 2.1.4 release (please see
> >> > freetype-2.1.4/debian/patches/001-freetype-2.1.4+cvs20030601.diff).
> >>
> >> If this is true, then, FreeType maintainer: *please stop doing this*.
> >>
> >> Debian needs to have FreeType packages that are compatible with the rest
> >> of the world's FreeType packages.
> >>
> >> Perhaps what we really need is a freetype-snapshot package, which ships
> >> a libfreetype6-snapshot package which Conflicts/Replaces/Provides:
> >> libfreetype6.  For reasons that should be obvious, there should be no
> >> snapshot -dev package at all.
> >>
> >> Please, please, please, I beg of you, do not break binary compatibility
> >> in library packages.
> 
>  Humm, I found a message from Werner LEMBERG posted to
> [EMAIL PROTECTED] I believe libfreetype6 incompatible between
> 2.1.4-3 and 2.1.4-4.
> 
>   Application build with libfreetype6_2.1.4-4 (use PS_FontInfoRec)
> will crash with libfreetype6_2.1.4-3.
> 
>   Application build with libfreetype6_2.1.4-3 (use PS_FontInfoRec)
> will crash with libfreetype6_2.1.4-4.
> 
>  But SONAME is not changed yet (on upstream).
> 
> 
> > In <[EMAIL PROTECTED]> 
> > Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> >> >
> >> >You might want to reconsider the change...
> >> > 
> >> > * src/type1/t1tokens.h: Change italic_angle, is_fixed_pitch,
> >> > underline_position, and underline_thickness to pointers.  Change
> >> > the type of the latter two to `fixed'.
> >> > 
> >> > in current freetype6 without a change in version numbering of the shared
> >> > libraries.
> >>
> >> Our normal strategy is to increase the shared library version number
> >> right before a new release (as suggested by libtool).  We will do
> >> that, of course, but not now.
> >>
> >> Is there a better strategy?
> >>
> >>
> >> Werner
> 
> -- 
> ISHIKAWA Mutsumi
>  <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>

-- 
Anthony Fok Tung-Ling
ThizLinux Laboratory   <[EMAIL PROTECTED]> http://www.thizlinux.com/
Debian Chinese Project <[EMAIL PROTECTED]>   http://www.debian.org/intl/zh/
Come visit Our Lady of Victory Camp!   http://www.olvc.ab.ca/

Re: RFC: define FontLibSharedFreeType=NO

[ISHIKAWA Mutsumi]

> In <[EMAIL PROTECTED]> 
>   Branden Robinson <[EMAIL PROTECTED]> wrote:

>> On Sat, Jun 07, 2003 at 11:20:01PM +0900, ISHIKAWA Mutsumi wrote:
>> > >> I got a report in private mail (grrr) from a person who ran into the
>> > >> very problem you describe, so I appreciate you tracking this down and
>> > >> fixing it.  Your analysis looks reasonable and I agree with your
>> > >> solution.
>> > 
>> >  Sorry, I found my mistakes by my self.
>> > 
>> >  1) PS_FontInfoRec was not changed between FreeeType 2.1.3 and
>> > 2.1.4. It makes after FreeType 2.1.4 release (please see
>> > freetype-2.1.4/debian/patches/001-freetype-2.1.4+cvs20030601.diff).
>>
>> If this is true, then, FreeType maintainer: *please stop doing this*.
>>
>> Debian needs to have FreeType packages that are compatible with the rest
>> of the world's FreeType packages.
>>
>> Perhaps what we really need is a freetype-snapshot package, which ships
>> a libfreetype6-snapshot package which Conflicts/Replaces/Provides:
>> libfreetype6.  For reasons that should be obvious, there should be no
>> snapshot -dev package at all.
>>
>> Please, please, please, I beg of you, do not break binary compatibility
>> in library packages.

 Humm, I found a message from Werner LEMBERG posted to
[EMAIL PROTECTED] I believe libfreetype6 incompatible between
2.1.4-3 and 2.1.4-4.

  Application build with libfreetype6_2.1.4-4 (use PS_FontInfoRec)
will crash with libfreetype6_2.1.4-3.

  Application build with libfreetype6_2.1.4-3 (use PS_FontInfoRec)
will crash with libfreetype6_2.1.4-4.

 But SONAME is not changed yet (on upstream).


> In <[EMAIL PROTECTED]> 
>   Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>> >
>> >You might want to reconsider the change...
>> > 
>> > * src/type1/t1tokens.h: Change italic_angle, is_fixed_pitch,
>> > underline_position, and underline_thickness to pointers.  Change
>> > the type of the latter two to `fixed'.
>> > 
>> > in current freetype6 without a change in version numbering of the shared
>> > libraries.
>>
>> Our normal strategy is to increase the shared library version number
>> right before a new release (as suggested by libtool).  We will do
>> that, of course, but not now.
>>
>> Is there a better strategy?
>>
>>
>> Werner

-- 
ISHIKAWA Mutsumi
 <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>

Bug#196575: xserver-xfree86: I agree it's a general problem

[Guido Trotter]

Package: xserver-xfree86
Version: 4.2.1-7
Followup-For: Bug #196575

I also agree it's a general problem: after the upgrade I weren't able
to start an X program anymore. I tried to restart xdm, but then X didn't
work at all, it closed suddenly after logging in. (Also xdm was
graphically changed, after restarting...)

If I try to manually start the server it works, showing me the
"classical" grey background with the mouse as an X, but no client is able 
to connect to it. Here is what the console reports:

waiting for X server to begin accepting connections .
AUDIT: Sun Jun  8 12:09:19 2003: 716 X: client 1 rejected from local
host
Auth name: XDM-AUTHORIZATION-1 ID: -1
Xlib: connection to ":0.0" refused by server
Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
..
  

Thanks for any help!

Guido

PS I'm going back to 4.2.1-6 from testing, hoping it works again... 

Bug#196575: xserver-xfree86 upgrade breaks X authorization

[Marius Gedminas]

Package: xserver-xfree86
Version: 4.2.1-7
Followup-For: Bug #196575

After upgrading several X packages (xlibs, xbase-clients,
xserver-common, xserver-xfree86 and more) I was unable to start any new
X programs.  For example, xterm would complain

  Xlib: connection to ":0.0" refused by server
  Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
  xterm Xt error: Can't open display: :0

I logged out hoping that KDM would generate a new key and fix things,
but it didn't work -- KDM greeter is unable to connect to the X server
either and KDM just aborts.

I have nearly the same problem with XDM -- the login dialog works, but
my .xsession aborts with the same Invalid XDM-AUTHORIZATION-1 key
message.

GDM2 (Unofficial package from http://non-us.debian.org woody/gnome2)
works fine.

Plain startx used to work before I tried xdm/gdm, but now doesn't.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux mg 2.4.20-mg #1 Fri Jan 31 22:32:32 EET 2003 i686
Locale: LANG=C, LC_CTYPE=lt_LT.UTF-8

Versions of packages xserver-xfree86 depends on:
ii  debconf   1.2.39 Debian configuration management sy
ii  libc6 2.3.1-17   GNU C Library: Shared libraries an
ii  xserver-common4.2.1-7files and utilities common to all 
ii  zlib1g1:1.1.4-12 compression library - runtime

Marius Gedminas
-- 
Of course everyone knows that vim is the best text editor in the world. Anyone
who tells you differently is either wrong, lying, or criminally insane. (Or an
emacs user, in which case they are wrong, lying and criminally insane).

Re: RFC: define FontLibSharedFreeType=NO

[ISHIKAWA Mutsumi]

> In <[EMAIL PROTECTED]> 
>   Anthony Fok <[EMAIL PROTECTED]> wrote:
>> Hello,

>> Does the same crash exists between libfreetype6_2.1.3-2 and 2.1.3-3? In
>> 2.1.3-4 (which I uploaded this morning), I tried to revert the change with
>> respect to PS_FontInfoRec (while going to CVS 2003-06-07), and I had been
>> wondering whether I did it correctly or not.
>>
>> My apologies for the troubles caused.

 Ah..Oops, soory.

 I miswrote 2.1.4-2 as 2.1.4-3 and 2.1.4-3 as 2.1.4-4...
 I'm talking about changes between libfreetype6_2.1.4-2 and -3.

 I am sorry to make it get confused.

 I've not checked libfreetype6_2.1.4-4 yet.


>> On Sun, Jun 08, 2003 at 07:36:13PM +0900, ISHIKAWA Mutsumi wrote:
>> > > In <[EMAIL PROTECTED]> 
>> > >  Branden Robinson <[EMAIL PROTECTED]> wrote:
>> > 
>> > >> On Sat, Jun 07, 2003 at 11:20:01PM +0900, ISHIKAWA Mutsumi wrote:
>> > >> > >> I got a report in private mail (grrr) from a person who ran into the
>> > >> > >> very problem you describe, so I appreciate you tracking this down and
>> > >> > >> fixing it.  Your analysis looks reasonable and I agree with your
>> > >> > >> solution.
>> > >> > 
>> > >> >  Sorry, I found my mistakes by my self.
>> > >> > 
>> > >> >  1) PS_FontInfoRec was not changed between FreeeType 2.1.3 and
>> > >> > 2.1.4. It makes after FreeType 2.1.4 release (please see
>> > >> > freetype-2.1.4/debian/patches/001-freetype-2.1.4+cvs20030601.diff).
>> > >>
>> > >> If this is true, then, FreeType maintainer: *please stop doing this*.
>> > >>
>> > >> Debian needs to have FreeType packages that are compatible with the rest
>> > >> of the world's FreeType packages.
>> > >>
>> > >> Perhaps what we really need is a freetype-snapshot package, which ships
>> > >> a libfreetype6-snapshot package which Conflicts/Replaces/Provides:
>> > >> libfreetype6.  For reasons that should be obvious, there should be no
>> > >> snapshot -dev package at all.
>> > >>
>> > >> Please, please, please, I beg of you, do not break binary compatibility
>> > >> in library packages.
>> > 
>> >  Humm, I found a message from Werner LEMBERG posted to
>> > [EMAIL PROTECTED] I believe libfreetype6 incompatible between
>> > 2.1.4-3 and 2.1.4-4.
>> > 
>> >   Application build with libfreetype6_2.1.4-4 (use PS_FontInfoRec)
>> > will crash with libfreetype6_2.1.4-3.
>> > 
>> >   Application build with libfreetype6_2.1.4-3 (use PS_FontInfoRec)
>> > will crash with libfreetype6_2.1.4-4.
>> > 
>> >  But SONAME is not changed yet (on upstream).
>> > 
>> > 
>> > > In <[EMAIL PROTECTED]> 
>> > >  Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>> > >> >
>> > >> >You might want to reconsider the change...
>> > >> > 
>> > >> > * src/type1/t1tokens.h: Change italic_angle, is_fixed_pitch,
>> > >> > underline_position, and underline_thickness to pointers.  Change
>> > >> > the type of the latter two to `fixed'.
>> > >> > 
>> > >> > in current freetype6 without a change in version numbering of the shared
>> > >> > libraries.
>> > >>
>> > >> Our normal strategy is to increase the shared library version number
>> > >> right before a new release (as suggested by libtool).  We will do
>> > >> that, of course, but not now.
>> > >>
>> > >> Is there a better strategy?
>> > >>
>> > >>
>> > >> Werner

-- 
ISHIKAWA Mutsumi
 <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>


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

Processed: duplicate bugs go whoooo whooooooo

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 196575 important
Bug#196575: xserver-xfree86 (and related packages from source) upgrade breaks kdm, 
sylpheed-claws
Severity set to `important'.

> retitle 196575 [xlib]: gcc3.3 screws up authentication
Bug#196575: xserver-xfree86 (and related packages from source) upgrade breaks kdm, 
sylpheed-claws
Changed Bug title.

> tags 196575 = patch sid sarge
Bug#196575: [xlib]: gcc3.3 screws up authentication
There were no tags set.
Tags set to: patch, sid, sarge

> merge 196554 196575
Bug#196554: [xlib]: gcc3.3 screws up authentication
Bug#196575: [xlib]: gcc3.3 screws up authentication
Mismatch - only Bugs in same state can be merged:
Values for `package' don't match:
 #196554 has `xlibs';
 #196575 has `xserver-xfree86'

> 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]

Processed: ugh

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 196575 xlibs
Bug#196575: [xlib]: gcc3.3 screws up authentication
Bug reassigned from package `xserver-xfree86' to `xlibs'.

> merge 196554 196575
Bug#196554: [xlib]: gcc3.3 screws up authentication
Bug#196575: [xlib]: gcc3.3 screws up authentication
Merged 196554 196575.

> --
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: RFC: define FontLibSharedFreeType=NO

[Anthony Fok]

Hello,

Does the same crash exists between libfreetype6_2.1.3-2 and 2.1.3-3? In
2.1.3-4 (which I uploaded this morning), I tried to revert the change with
respect to PS_FontInfoRec (while going to CVS 2003-06-07), and I had been
wondering whether I did it correctly or not.

My apologies for the troubles caused.

Anthony

On Sun, Jun 08, 2003 at 07:36:13PM +0900, ISHIKAWA Mutsumi wrote:
> > In <[EMAIL PROTECTED]> 
> > Branden Robinson <[EMAIL PROTECTED]> wrote:
> 
> >> On Sat, Jun 07, 2003 at 11:20:01PM +0900, ISHIKAWA Mutsumi wrote:
> >> > >> I got a report in private mail (grrr) from a person who ran into the
> >> > >> very problem you describe, so I appreciate you tracking this down and
> >> > >> fixing it.  Your analysis looks reasonable and I agree with your
> >> > >> solution.
> >> > 
> >> >  Sorry, I found my mistakes by my self.
> >> > 
> >> >  1) PS_FontInfoRec was not changed between FreeeType 2.1.3 and
> >> > 2.1.4. It makes after FreeType 2.1.4 release (please see
> >> > freetype-2.1.4/debian/patches/001-freetype-2.1.4+cvs20030601.diff).
> >>
> >> If this is true, then, FreeType maintainer: *please stop doing this*.
> >>
> >> Debian needs to have FreeType packages that are compatible with the rest
> >> of the world's FreeType packages.
> >>
> >> Perhaps what we really need is a freetype-snapshot package, which ships
> >> a libfreetype6-snapshot package which Conflicts/Replaces/Provides:
> >> libfreetype6.  For reasons that should be obvious, there should be no
> >> snapshot -dev package at all.
> >>
> >> Please, please, please, I beg of you, do not break binary compatibility
> >> in library packages.
> 
>  Humm, I found a message from Werner LEMBERG posted to
> [EMAIL PROTECTED] I believe libfreetype6 incompatible between
> 2.1.4-3 and 2.1.4-4.
> 
>   Application build with libfreetype6_2.1.4-4 (use PS_FontInfoRec)
> will crash with libfreetype6_2.1.4-3.
> 
>   Application build with libfreetype6_2.1.4-3 (use PS_FontInfoRec)
> will crash with libfreetype6_2.1.4-4.
> 
>  But SONAME is not changed yet (on upstream).
> 
> 
> > In <[EMAIL PROTECTED]> 
> > Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> >> >
> >> >You might want to reconsider the change...
> >> > 
> >> > * src/type1/t1tokens.h: Change italic_angle, is_fixed_pitch,
> >> > underline_position, and underline_thickness to pointers.  Change
> >> > the type of the latter two to `fixed'.
> >> > 
> >> > in current freetype6 without a change in version numbering of the shared
> >> > libraries.
> >>
> >> Our normal strategy is to increase the shared library version number
> >> right before a new release (as suggested by libtool).  We will do
> >> that, of course, but not now.
> >>
> >> Is there a better strategy?
> >>
> >>
> >> Werner
> 
> -- 
> ISHIKAWA Mutsumi
>  <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>

-- 
Anthony Fok Tung-Ling
ThizLinux Laboratory   <[EMAIL PROTECTED]> http://www.thizlinux.com/
Debian Chinese Project <[EMAIL PROTECTED]>   http://www.debian.org/intl/zh/
Come visit Our Lady of Victory Camp!   http://www.olvc.ab.ca/


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

Re: RFC: define FontLibSharedFreeType=NO

[ISHIKAWA Mutsumi]

> In <[EMAIL PROTECTED]> 
>   Branden Robinson <[EMAIL PROTECTED]> wrote:

>> On Sat, Jun 07, 2003 at 11:20:01PM +0900, ISHIKAWA Mutsumi wrote:
>> > >> I got a report in private mail (grrr) from a person who ran into the
>> > >> very problem you describe, so I appreciate you tracking this down and
>> > >> fixing it.  Your analysis looks reasonable and I agree with your
>> > >> solution.
>> > 
>> >  Sorry, I found my mistakes by my self.
>> > 
>> >  1) PS_FontInfoRec was not changed between FreeeType 2.1.3 and
>> > 2.1.4. It makes after FreeType 2.1.4 release (please see
>> > freetype-2.1.4/debian/patches/001-freetype-2.1.4+cvs20030601.diff).
>>
>> If this is true, then, FreeType maintainer: *please stop doing this*.
>>
>> Debian needs to have FreeType packages that are compatible with the rest
>> of the world's FreeType packages.
>>
>> Perhaps what we really need is a freetype-snapshot package, which ships
>> a libfreetype6-snapshot package which Conflicts/Replaces/Provides:
>> libfreetype6.  For reasons that should be obvious, there should be no
>> snapshot -dev package at all.
>>
>> Please, please, please, I beg of you, do not break binary compatibility
>> in library packages.

 Humm, I found a message from Werner LEMBERG posted to
[EMAIL PROTECTED] I believe libfreetype6 incompatible between
2.1.4-3 and 2.1.4-4.

  Application build with libfreetype6_2.1.4-4 (use PS_FontInfoRec)
will crash with libfreetype6_2.1.4-3.

  Application build with libfreetype6_2.1.4-3 (use PS_FontInfoRec)
will crash with libfreetype6_2.1.4-4.

 But SONAME is not changed yet (on upstream).


> In <[EMAIL PROTECTED]> 
>   Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>> >
>> >You might want to reconsider the change...
>> > 
>> > * src/type1/t1tokens.h: Change italic_angle, is_fixed_pitch,
>> > underline_position, and underline_thickness to pointers.  Change
>> > the type of the latter two to `fixed'.
>> > 
>> > in current freetype6 without a change in version numbering of the shared
>> > libraries.
>>
>> Our normal strategy is to increase the shared library version number
>> right before a new release (as suggested by libtool).  We will do
>> that, of course, but not now.
>>
>> Is there a better strategy?
>>
>>
>> Werner

-- 
ISHIKAWA Mutsumi
 <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>


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

Bug#196575: xserver-xfree86: I agree it's a general problem

[Guido Trotter]

Package: xserver-xfree86
Version: 4.2.1-7
Followup-For: Bug #196575

I also agree it's a general problem: after the upgrade I weren't able
to start an X program anymore. I tried to restart xdm, but then X didn't
work at all, it closed suddenly after logging in. (Also xdm was
graphically changed, after restarting...)

If I try to manually start the server it works, showing me the
"classical" grey background with the mouse as an X, but no client is able 
to connect to it. Here is what the console reports:

waiting for X server to begin accepting connections .
AUDIT: Sun Jun  8 12:09:19 2003: 716 X: client 1 rejected from local
host
Auth name: XDM-AUTHORIZATION-1 ID: -1
Xlib: connection to ":0.0" refused by server
Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
..
  

Thanks for any help!

Guido

PS I'm going back to 4.2.1-6 from testing, hoping it works again... 




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

Bug#196554: xlibs: todays update causes every app to report "Xlib: connection to ":0.0" refused by server"

[Ralf Hildebrandt]

* Daniel Stone <[EMAIL PROTECTED]>:

> > This also happens when I try to start kdm from the console.
> 
> Yeah, this is a problem with ?dm and authorization. Try 'startx' from
> the command line.

Yes, this works.
 
> For the BTS, the problem is that gcc3.3 screws up authentication somehow
> - either cpp3.3's semantics changing, or miscompiled code. This has been
> seen to happen on both powerpc and i386 now, so it's not a
> single-architecture problem. Ugh. :(

Shit happens unlimited.
So is it kdm's or xlibs's fault?

-- 
Ralf Hildebrandt (Im Auftrag des Referat V a)   [EMAIL PROTECTED]
Charite Campus MitteTel.  +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze - Fax.  +49 (0)30-450 570-916
AIM: ralfpostfix

Bug#196575: xserver-xfree86 upgrade breaks X authorization

[Marius Gedminas]

Package: xserver-xfree86
Version: 4.2.1-7
Followup-For: Bug #196575

After upgrading several X packages (xlibs, xbase-clients,
xserver-common, xserver-xfree86 and more) I was unable to start any new
X programs.  For example, xterm would complain

  Xlib: connection to ":0.0" refused by server
  Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
  xterm Xt error: Can't open display: :0

I logged out hoping that KDM would generate a new key and fix things,
but it didn't work -- KDM greeter is unable to connect to the X server
either and KDM just aborts.

I have nearly the same problem with XDM -- the login dialog works, but
my .xsession aborts with the same Invalid XDM-AUTHORIZATION-1 key
message.

GDM2 (Unofficial package from http://non-us.debian.org woody/gnome2)
works fine.

Plain startx used to work before I tried xdm/gdm, but now doesn't.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux mg 2.4.20-mg #1 Fri Jan 31 22:32:32 EET 2003 i686
Locale: LANG=C, LC_CTYPE=lt_LT.UTF-8

Versions of packages xserver-xfree86 depends on:
ii  debconf   1.2.39 Debian configuration management sy
ii  libc6 2.3.1-17   GNU C Library: Shared libraries an
ii  xserver-common4.2.1-7files and utilities common to all 
ii  zlib1g1:1.1.4-12 compression library - runtime

Marius Gedminas
-- 
Of course everyone knows that vim is the best text editor in the world. Anyone
who tells you differently is either wrong, lying, or criminally insane. (Or an
emacs user, in which case they are wrong, lying and criminally insane).



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

Bug#196575: xserver-xfree86 (and related packages from source) upgrade breaks kdm, sylpheed-claws

[Morgon Kanter]

Package: xserver-xfree86
Version: 4.2.1-7
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

After upgrading from 4.2.1-6 to 4.2.1-7, first sylpheed-claws could not
start (something about a key mismatch and not being able to connect to
the display, I didn't manage to get the full error message down).

After logging out of KDE (3.1), kdm took back over and immediately
started failing. I restarted kdm, but the screen flickered a few times,
and the following showed up in syslog. surgo is merely my machine name:

Jun  8 02:32:10 surgo kdm[15884]: Greeter exited unexpectedly
Jun  8 02:32:10 surgo kdm[15884]: Abnormal helper termination, code 1,
signal 0
Jun  8 02:32:18 surgo kdm[15889]: Greeter exited unexpectedly
Jun  8 02:32:18 surgo kdm[15889]: Abnormal helper termination, code 1,
signal 0
Jun  8 02:32:26 surgo kdm[15894]: Greeter exited unexpectedly
Jun  8 02:32:26 surgo kdm[15894]: Abnormal helper termination, code 1,
signal 0
Jun  8 02:32:34 surgo kdm[15899]: Greeter exited unexpectedly
Jun  8 02:32:34 surgo kdm[15899]: Abnormal helper termination, code 1,
signal 0
Jun  8 02:32:34 surgo kdm[15882]: Display :0 is being disabled
(restarting too fast)

The problems I found were with sylpheed-claws and kdm, but I believe
this is a general X11 problem because they were both broken upon X11's
upgrade to 2.4.1-7

- -- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux surgo 2.4.20 #1 Fri May 23 17:43:27 EDT 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages xserver-xfree86 depends on:
ii  debconf   1.2.39 Debian configuration management sy
ii  libc6 2.3.1-17   GNU C Library: Shared libraries an
ii  xserver-common4.2.1-7files and utilities common to all 
ii  zlib1g1:1.1.4-12 compression library - runtime

- -- debconf information excluded

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)

iQEVAwUBPuLc0g+aqp0pfOpbAQLJGAgAqcYUn/1dKjGt0CTdeElrlPgmIXU1FJoK
zTYx0FMihX2q/dt6b2krtPVzeODdWKoHFW7JpcMFBBfhgRxUw9QCrp08Tfy80pTF
1LyPISDNfo9qTqboodXfvYPWFRlhvGNEH2rrOUko96gyMxBZUWq6h4YQSTkLrauJ
U5YEqYSqCm/v59YSJ4AZmdVMzPFxKtz9jRTB2woDgYRu4HfGNTqA6ssuQvg12HxM
UkzVuocHSmvxlhT8ZFRcgFzHiEsDsjQWb30j/ee+JZT2aH5WheGCE+9Jx8TJO9Pc
wTf7CsJ4zMa8MfGFnWBdiaAeNuZhsDGsJt2ikM8fUUih3fu8zYs5/Q==
=uFG3
-END PGP SIGNATURE-

Bug#196554: xlibs: todays update causes every app to report "Xlib: connection to ":0.0" refused by server"

[Ralf Hildebrandt]

* Daniel Stone <[EMAIL PROTECTED]>:

> > This also happens when I try to start kdm from the console.
> 
> Yeah, this is a problem with ?dm and authorization. Try 'startx' from
> the command line.

Yes, this works.
 
> For the BTS, the problem is that gcc3.3 screws up authentication somehow
> - either cpp3.3's semantics changing, or miscompiled code. This has been
> seen to happen on both powerpc and i386 now, so it's not a
> single-architecture problem. Ugh. :(

Shit happens unlimited.
So is it kdm's or xlibs's fault?

-- 
Ralf Hildebrandt (Im Auftrag des Referat V a)   [EMAIL PROTECTED]
Charite Campus MitteTel.  +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze - Fax.  +49 (0)30-450 570-916
AIM: ralfpostfix



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