-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 16 Oct 2002 14:09:15 -0500
Source: xfree86
Binary: xserver-common libxaw7-dbg xbase-clients twm xlibmesa3-dbg xfonts-scalable
xfonts-75dpi libdps1-dbg xlib6g-dev xmh libxaw6-dbg xfwp xlibs xlibosmesa3-dbg
libdps-dev
Package: xlibs
Version: 4.2.1-2
Severity: normal
xlibs version 4.1.0-16 (Debian 3.0) contains:
// definition for the extra keys on 104-key Windows95 keyboards
xkb_symbols pc104 {
include us(generic101)
key LALT {[ Alt_L ] };
key RALT {[
Hi,
I've been running a dual-head setup for some time with a 16 MB Matrox
G400, but the last X upgrade (from 4.2.0 to 4.2.1) seems to have bonked
the dual head support. Enclosed is a failure log and a copy of my
XF86Config-4 file.
Note that the line for the second screen in the Server Layout
Package: xutils
Version: 4.2.1-2
Severity: important
Tags: sid upstream
I've already reported the same problem for version 4.1.0-17, now it's
back.
Here's how I've patched the configuration files in /usr/lib/X11/config
to get the macros for linking and installing a shared library and
makedepend
FAI ATTENZIONE PERCHE' CON QUESTO SISTEMA GUADAGNI DAVVERO !
(se il messaggio vi e' arrivato piu volte scusate ma,
leggetelo
..)
Vorresti Davvero Guadagnare con Internet?
Bene, la prima cosa da fare è salvare su disco questa pagina per averla
a portata di mano anche se il tuo PC
Hi,
Well, may it's better said X crashing...?
Trying to open a powerpoint presentation file with
openoffice.org.1.0.1-5+woody crash X-Windows with a last line X-log:
Fatal server error:
Beziers this big not yet supported
I have matrox g400 card, so I tried the line in the mga device option:
False alarm. My problems were completely hardware related. Screen corruption
was present even when not using X and persisted across power cycles. The
problem went away after changing video cards.
Thanks.
Igor
Quoting Branden Robinson [EMAIL PROTECTED]:
On Fri, Oct 11, 2002 at 08:56:41AM
On Thu, Oct 17, 2002 at 02:32:33AM +0900, ChanChan KO wrote:
I found Blackdown-Java 1.4.1beta (not deb'ed) can display KANJI at XF86
4.2.1-2,
but 1.3.1 (deb'ed) can't display KANJI on menubar at XF86 4.2.1-2.
[...]
Maybe, this isssue is not from XF86 , problem of older Blackdown JVM.
I
On Thu, Oct 17, 2002 at 08:54:35AM -0700, Paul Mackinney wrote:
Thanks to Simon Hepburn and Sebastien Picard for their sapient replies.
Simon pointed out that I had mis-matched drivers, the mga_hal driver was
compiled for X4.1, not X4.2. Weird, because the driver either came from:
-The
[Please follow-up to both lists. I do not subscribe to
debian-openoffice.]
On Thu, Oct 17, 2002 at 05:42:04PM +0200, unai wrote:
Well, may it's better said X crashing...?
Trying to open a powerpoint presentation file with
openoffice.org.1.0.1-5+woody crash X-Windows with a last line X-log:
Your message dated Thu, 17 Oct 2002 12:24:32 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#165134: xlibs: [xkb] symbol change in us keyboard disables
Meta and Compose key
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 16 Oct 2002 14:09:15 -0500
Source: xfree86
Binary: xserver-common libxaw7-dbg xbase-clients twm xlibmesa3-dbg
xfonts-scalable xfonts-75dpi libdps1-dbg xlib6g-dev xmh libxaw6-dbg xfwp xlibs
xlibosmesa3-dbg libdps-dev
Your message dated Thu, 17 Oct 2002 16:14:54 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#163927: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164484: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Hi Branden,
I just tried xserver-xfree86 4.2.1-2 and have to tell
the problem has not vanished.
Any thoughts on this?
Thanx,
Stefan
Your message dated Thu, 17 Oct 2002 16:14:54 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#130877: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:54 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#163586: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164708: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164491: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164489: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164486: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164422: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:54 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#158512: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164217: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:54 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#149549: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Heyho,
[EMAIL PROTECTED] writes:
Therefore I'm asking for German users, especially ones with a clue about
XKB, to help make this determination.
What about including a README about that in the package until things
become more clear. I would write one explaining the normal solution for
On Thu, Oct 17, 2002 at 12:27:43PM -0500, [EMAIL PROTECTED] wrote:
On Thu, Oct 17, 2002 at 09:20:27AM +0200, Erwin Burgstaller wrote:
I've already reported the same problem for version 4.1.0-17, now it's
back.
Here's how I've patched the configuration files in /usr/lib/X11/config
to
reopen 165134
thanks
On Thu, Oct 17, 2002 at 02:41:11PM +1000, Anand Kumria wrote:
The Windows keys on upgrade don't send Meta anymore. Personally I prefer
the definition supplied with Debian 3.0 (Left Windows is Meta, Right
Windows is Compose).
=20
This breaks upgrades (and if it isn't
Processing commands for [EMAIL PROTECTED]:
reopen 165134
Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose
key
Bug reopened, originator not changed.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Hi,
Well, may it's better said X crashing...?
Trying to open a powerpoint presentation file with
openoffice.org.1.0.1-5+woody crash X-Windows with a last line X-log:
Fatal server error:
Beziers this big not yet supported
I have matrox g400 card, so I tried the line in the mga device option:
Thanks to Simon Hepburn and Sebastien Picard for their sapient replies.
Simon pointed out that I had mis-matched drivers, the mga_hal driver was
compiled for X4.1, not X4.2. Weird, because the driver either came from:
-The latest xfree86 deb
-The 4.2.0 drivers distributed by Matrox
-Compiled
False alarm. My problems were completely hardware related. Screen corruption
was present even when not using X and persisted across power cycles. The
problem went away after changing video cards.
Thanks.
Igor
Quoting Branden Robinson [EMAIL PROTECTED]:
On Fri, Oct 11, 2002 at 08:56:41AM
On Thu, Oct 17, 2002 at 02:32:33AM +0900, ChanChan KO wrote:
I found Blackdown-Java 1.4.1beta (not deb'ed) can display KANJI at XF86 4.2.1-2,
but 1.3.1 (deb'ed) can't display KANJI on menubar at XF86 4.2.1-2.
[...]
Maybe, this isssue is not from XF86 , problem of older Blackdown JVM.
I am
On Thu, Oct 17, 2002 at 08:54:35AM -0700, Paul Mackinney wrote:
Thanks to Simon Hepburn and Sebastien Picard for their sapient replies.
Simon pointed out that I had mis-matched drivers, the mga_hal driver was
compiled for X4.1, not X4.2. Weird, because the driver either came from:
-The
[Please follow-up to both lists. I do not subscribe to
debian-openoffice.]
On Thu, Oct 17, 2002 at 05:42:04PM +0200, unai wrote:
Well, may it's better said X crashing...?
Trying to open a powerpoint presentation file with
openoffice.org.1.0.1-5+woody crash X-Windows with a last line X-log:
Your message dated Thu, 17 Oct 2002 12:24:32 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta
and Compose key
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been
Well, may it's better said X crashing...?
Trying to open a powerpoint presentation file with
openoffice.org.1.0.1-5+woody crash X-Windows with a last line X-log:
Fatal server error:
Beziers this big not yet supported
[...]
Have anybody had a similar problem ?
Hi Branden,
I just tried xserver-xfree86 4.2.1-2 and have to tell
the problem has not vanished.
Any thoughts on this?
Thanx,
Stefan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Your message dated Thu, 17 Oct 2002 16:14:54 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#130877: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:54 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#163586: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164708: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164491: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164489: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164486: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:54 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#163927: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164484: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164422: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:54 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#158512: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Thu, 17 Oct 2002 16:14:54 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#149549: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Heyho,
[EMAIL PROTECTED] writes:
Therefore I'm asking for German users, especially ones with a clue about
XKB, to help make this determination.
What about including a README about that in the package until things
become more clear. I would write one explaining the normal solution for
Your message dated Thu, 17 Oct 2002 16:14:55 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#164217: fixed in xfree86 4.2.1-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Hey there,
What about including a README about that in the package until things
become more clear. I would write one explaining the normal solution for
US-users (using the altwin:meta_win Option) and the changes I made
to make it working for geman users.
tell me what you think about it,
David
On Thu, Oct 17, 2002 at 12:27:43PM -0500, [EMAIL PROTECTED] wrote:
On Thu, Oct 17, 2002 at 09:20:27AM +0200, Erwin Burgstaller wrote:
I've already reported the same problem for version 4.1.0-17, now it's
back.
Here's how I've patched the configuration files in /usr/lib/X11/config
to
Processing commands for [EMAIL PROTECTED]:
reopen 165134
Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key
Bug reopened, originator not changed.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Processing commands for [EMAIL PROTECTED]:
severity 165134 wishlist
Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key
Severity set to `wishlist'.
retitle 165134 xlibs: [xkb] please break compatibility with upstream in pc104
symbols file
Bug#165134: xlibs:
On Thu, Oct 17, 2002 at 11:49:31PM +0200, David Spreen wrote:
What about including a README about that in the package until things
become more clear. I would write one explaining the normal solution for
US-users (using the altwin:meta_win Option) and the changes I made
to make it working for
On Fri, Oct 18, 2002 at 12:29:33AM +0200, Erwin Burgstaller wrote:
Ok, I see. I've tracked down the problem more carefully now:
The SOSYMLINK problem maybe solved by including Library.tmpl in
Imake.rules:
--- Imake.rules.~1~ 2002-10-08 08:06:23.0 +0200
+++ Imake.rules 2002-10-17
57 matches
Mail list logo
