Hi Branden,
HACKING.txt currently has outdated information wrt the xf86AutoConfig
code; could you please fix this up?
--
Daniel Stone<[EMAIL PROTECTED]>
Debian: the universal operating system http://www.debian.org
signature.asc
Package: xfree86-common
Version: 4.3.0.dfsg.1-6
Followup-For: Bug #266525
I did a fresh sarge install this weekend and the bug with the not
starting ssh-agent is still there. I changed no files except the
xconfig.
I see no error messages in any X-related logfile. (kdm and xfreelog)
Please fix this
Author: fabbione
Date: 2004-09-06 02:50:53 -0500 (Mon, 06 Sep 2004)
New Revision: 1798
Modified:
trunk/debian/TODO
Log:
Update items due to upcoming -7 release.
Modified: trunk/debian/TODO
===
--- trunk/debian/TODO 2004-09-05 2
Hey Winston
Its been a while since we spoke about the site that I have been ordering all of
my pre_sc_riptions at wholesale from.
Did you ever check it out? If not the new link is below
Talk to you later.
Akecheta Oconnor
check it out
http://plumbago.4098ws.com/_55d958a932f5b91262baa654773c6
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-6
When I connect a flatpanel through a DVI cable with my G5 Mac that
screen is completely garbled. An 'Option "CrtcNumber" "1"' in
XF84Config the picture almost except the last ~1cm on the very right
side are displayed on the very left.
Replacing nv
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-6
Severity: normal
Tags: l10n
Hello.
Seems that keyboard driver is somehow broken.
To get Polish international uppercase character I have to push
ALT | SHIFT | Z/X/C/E/L/O/N/A
Exactly at this order.
Pushing:
SHIFT | ALT | Z/X/C/E/L/O/N/A
doesn't
Just FYI: r1799 is the merge from trunk to branches/4.3.0/sid/debian to
release 4.3.0.dfsg.1-7.
Fabio
--
fajita: step one
Whatever the problem, step one is always to look in the error log.
fajita: step two
When in danger or in doubt, step two is to scream and shout.
On Mon, Sep 06, 2004 at 11:12:14AM +0200, Christoph Hellwig wrote:
> When I connect a flatpanel through a DVI cable with my G5 Mac that
> screen is completely garbled. An 'Option "CrtcNumber" "1"' in
> XF84Config the picture almost except the last ~1cm on the very right
> side are displayed on the
On Mon, Sep 06, 2004 at 03:50:19AM -0700, Daniel Stone wrote:
> On Mon, Sep 06, 2004 at 11:12:14AM +0200, Christoph Hellwig wrote:
> > When I connect a flatpanel through a DVI cable with my G5 Mac that
> > screen is completely garbled. An 'Option "CrtcNumber" "1"' in
> > XF84Config the picture alm
Package: xvfb
Version: 4.3.0.dfsg.1-6
Severity: minor
The xvfb manual page refers to /usr/tmp, but it would be better to
use normal /tmp for examples
Xvfb -pixdepths 3 27 -fbdir /usr/tmp
The server will listen for connections as server number 0, will
have t
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
xfree86_4.3.0.dfsg.1-7.diff.gz
xfree86_4.3.0.dfsg.1-7.dsc
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.
If no .changes file arrives within 23:20:11, the fil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 06 Sep 2004 09:54:18 +0200
Source: xfree86
Binary: libx11-6-dbg libxtst6-dbg xserver-common xlibs-static-dev libxp6-dbg
xbase-clients xlibmesa3-dbg libxtrap6-dbg xfonts-75dpi libxt6 libice6-dbg xmh
libxaw6-dbg x-dev libxv1 libx
xfree86_4.3.0.dfsg.1-7_i386.changes uploaded successfully to localhost
along with the files:
xfree86_4.3.0.dfsg.1-7.dsc
xfree86_4.3.0.dfsg.1-7.diff.gz
pm-dev_4.3.0.dfsg.1-7_all.deb
x-dev_4.3.0.dfsg.1-7_all.deb
xfonts-100dpi_4.3.0.dfsg.1-7_all.deb
xfonts-100dpi-transcoded_4.3.0.dfsg.1-7_
Your message dated Mon, 06 Sep 2004 08:47:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#269507: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#261389: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#261163: fixed in xfree86 4.3.0.dfsg.1-7
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
Accepted:
lbxproxy_4.3.0.dfsg.1-7_i386.deb
to pool/main/x/xfree86/lbxproxy_4.3.0.dfsg.1-7_i386.deb
libdps-dev_4.3.0.dfsg.1-7_i386.deb
to pool/main/x/xfree86/libdps-dev_4.3.0.dfsg.1-7_i386.deb
libdps1-dbg_4.3.0.dfsg.1-7_i386.deb
to pool/main/x/xfree86/libdps1-dbg_4.3.0.dfsg.1-7_i386.deb
libdp
Your message dated Mon, 06 Sep 2004 08:47:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#260868: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#260753: fixed in xfree86 4.3.0.dfsg.1-7
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
There are disparities between your recently accepted upload and the
override file for the following file(s):
x-window-system-dev_4.3.0.dfsg.1-7_i386.deb: package says priority is extra,
override says optional.
Either the package or the override file is incorrect. If you think
the override is co
Your message dated Mon, 06 Sep 2004 08:47:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#260099: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#258986: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#257073: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#257023: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#256706: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#256420: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#256297: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#255701: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#266834: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#257835: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#256706: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#256706: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#255224: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#255197: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#255070: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#254650: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#252274: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#250655: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#200061: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#122039: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#122039: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#122039: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#122039: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#250655: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#259996: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#122039: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#122039: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#255371: fixed in xfree86 4.3.0.dfsg.1-7
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
Author: fabbione
Date: 2004-09-06 08:23:25 -0500 (Mon, 06 Sep 2004)
New Revision: 1800
Added:
4.3.0.dfsg.1-7/
Log:
Tag 4.3.0.dfsg.1-7 release.
Copied: 4.3.0.dfsg.1-7 (from rev 1799, branches/4.3.0/sid)
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#255270: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#236197: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#250655: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#254601: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:44 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#256086: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#258223: fixed in xfree86 4.3.0.dfsg.1-7
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
Your message dated Mon, 06 Sep 2004 08:47:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#261239: fixed in xfree86 4.3.0.dfsg.1-7
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
Author: fabbione
Date: 2004-09-06 08:25:17 -0500 (Mon, 06 Sep 2004)
New Revision: 1801
Removed:
4.3.0.dfsg.1-7/
Log:
Remove "Brownpaper bag" tag.
Author: fabbione
Date: 2004-09-06 08:26:20 -0500 (Mon, 06 Sep 2004)
New Revision: 1802
Added:
tags/4.3.0.dfsg.1-7/
Log:
Tag 4.3.0.dfsg.1-7 release.
Copied: tags/4.3.0.dfsg.1-7 (from rev 1801, branches/4.3.0/sid)
Author: fabbione
Date: 2004-09-06 08:27:32 -0500 (Mon, 06 Sep 2004)
New Revision: 1803
Modified:
NEWS.xhtml
Log:
Announce 4.3.0.dfsg.1-7 release.
Modified: NEWS.xhtml
===
--- NEWS.xhtml 2004-09-06 13:26:20 UTC (rev 1802)
+++ NEW
Author: fabbione
Date: 2004-09-06 08:28:43 -0500 (Mon, 06 Sep 2004)
New Revision: 1804
Modified:
trunk/debian/changelog
Log:
Merge 4.3.0.dfsg.1-7 changelog bits after release.
Modified: trunk/debian/changelog
===
--- trunk/debian
Author: fabbione
Date: 2004-09-06 08:31:43 -0500 (Mon, 06 Sep 2004)
New Revision: 1805
Modified:
trunk/debian/CHANGESETS
trunk/debian/changelog
Log:
Start 4.3.0.dfsg.1-8 development.
Modified: trunk/debian/CHANGESETS
===
--- t
*** eSafe detected hostile content in this email. ***
Time: 06 Sep 2004 07:06:24
Scan result: Mail modified to remove malicious content
Protocol: SMTP in
File Name\Mail Subject: mail_1094577248: Re: Sample
Source: [EMAIL PROTECTED]
Destination: [EMAIL PROTECTED]
Details: sample01.txt
Alphonso,
Got to the site below to order all of the r-xm-e-d-s we spoke about.
Thanks.
Genaro Thomas
It is simple to go heer
http://langley.49dmds.com/_55d958a932f5b91262baa654773c6a8e/
A little more moderation would be good. Of course, my life hasn't exactly been
one of moderation. Donald T
tags 270235 - l10n
thanks
On Mon, Sep 06, 2004 at 11:46:39AM +0200, Bartosz Fenski aka fEnIo wrote:
> Package: xserver-xfree86
> Version: 4.3.0.dfsg.1-6
> Severity: normal
> Tags: l10n
>
> Hello.
>
> Seems that keyboard driver is somehow broken.
> To get Polish international uppercase character
Processing commands for [EMAIL PROTECTED]:
> tags 270235 - l10n
Bug#270235: xserver-xfree86: ALT+SHIFT keys have to be pushed in *exact* order
to get int chars
Tags were: l10n
Tags removed: l10n
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking sy
Package: xfree86-common
Version: 4.3.0.dfsg.1-6
Severity: serious
I'm not sure whether this is xfree86's fault or t1-cyrillic's fault:
Preparing to replace xfree86-common 4.3.0.dfsg.1-6 (using
.../xfree86-common_4.3.0.dfsg.1-7_all.deb) ...
Unpacking replacement xfree86-common ...
dpkg: error pro
Hi Branden,
I just read the changelog of the latest XFree86 packages in unstable.
Shouldn't it work to let xserver-common have a
Conflicts: xserver-xfree86 (= 4.3.0.dfsg.1-5),
xserver-xfree86 (= 4.3.0.dfsg.1-6),
xserver-xfree86-dbg (= 4.3.0.dfsg.1-5),
xser
On Mon, Sep 06, 2004 at 11:16:45PM +0200, Denis Barbier wrote:
> tags 270235 - l10n
Sorry... I wasn't sure if I should mark it as l10n.
So this tag should be used only for translation issues?
> > That's quite weird. Should work with every order.
> > I checked it with both keyboard and kbd driver.
On Tue, Sep 07, 2004 at 12:07:47AM +0200, Bartosz Fenski aka fEnIo wrote:
> On Mon, Sep 06, 2004 at 11:16:45PM +0200, Denis Barbier wrote:
> > tags 270235 - l10n
>
> Sorry... I wasn't sure if I should mark it as l10n.
> So this tag should be used only for translation issues?
Anthony Towns explain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: XFree86
Version: 4.1.0.1
Hi, I would like to report a bug with the XFree86 software. I installed
debian on my laptop, Sony Picturebook, which is a relatively small laptop
and has an odd display ratio, almost widescreen size. When it had windo
Package: xterm
Version: 4.3.0.dfsg.1-6
Severity: important
*?%&?%$ VT bug in 2.6.8.1...
typing this in manually:
xterm: warning, error event recieved:
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 77 (X_ImageText16)
Value
reassign 270346 t1-cyrillic
stop
On Mon, 6 Sep 2004, Joshua Kwan wrote:
> Package: xfree86-common
> Version: 4.3.0.dfsg.1-6
> Severity: serious
>
> I'm not sure whether this is xfree86's fault or t1-cyrillic's fault:
>
> Preparing to replace xfree86-common 4.3.0.dfsg.1-6 (using
> .../xfree86-com
On Tue, Sep 07, 2004 at 06:53:22AM +0200, Fabio Massimo Di Nitto wrote:
> /usr/lib/X11 is a symlink owned by xfree86-common (even in versions
> earlier than -6). t1-cyrillic should respect the symlink, while it ships a
> directory (reason of the conflict).
I was looking at this one, but t1-cyrilli
73 matches
Mail list logo
