I just spotted an error in the X FAQ. I've quoted it below,
as I saw it in a change log.
Sorry, but procps does not currently report IO memory as
part of the memory being used by the X server. The X server
is guilty as charged. Mine grows to about 300 MB on a system
with only 16 MB of RAM. Of cour
Your message dated Fri, 20 Aug 2004 15:55:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#213267: xfree86 problems
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 respo
Your message dated Fri, 20 Aug 2004 15:52:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line closing old bugs fixed in XFree86 4.3.0-1
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 n
Your message dated Fri, 20 Aug 2004 15:52:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line closing old bugs fixed in XFree86 4.3.0-1
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 n
Processing commands for [EMAIL PROTECTED]:
> tag 195758 - fixed-in-experimental
Bug#195758: xserver-xfree86: [sis] screen distorted and cursor problems on 6326
rev 11
Tags were: upstream fixed-in-experimental
Tags removed: fixed-in-experimental
> tag 196912 - fixed-in-experimental
Bug#196912: xs
Author: branden
Date: 2004-08-20 15:58:39 -0500 (Fri, 20 Aug 2004)
New Revision: 1737
Modified:
trunk/debian/CHANGESETS
trunk/debian/changelog
Log:
(cosmetic) Add bug-closer to historical changelog entry.
Modified: trunk/debian/CHANGESETS
===
Your message dated Fri, 20 Aug 2004 15:43:36 -0500
with message-id <[EMAIL PROTECTED]>
and subject line closing old bug
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 responsibility to
On Thu, Aug 19, 2004 at 05:46:16PM -0500, Matthew P. Cummings wrote:
> The only solution I have found to running X on the Amiga is one that was
> posted in the past. If you extract the server from
> xserver-fbdev_3.3.6-11potato32.deb and place it in /usr/X11R6/bin and
> then link /etc/X to it and
On Fri, Aug 20, 2004 at 05:48:10AM -0700, Mike Mestnik wrote:
> Your getting on the right page. However the manpage should also indicate
> that any suffix for dotclock will result in an "echo (EE) $msg; exit;".
> This is preventing me from knowing what the unit is, since it can't be
> changed.
U
Package: xbase-clients
Version: 4.2.1-12.1
Severity: normal
At line 469 in the preinst script is the following:
if [ -L /etc/X11/xinit/xinitrc -a $(readlink /etc/X11/xinitrc)=
This is causing a syntax error at install time:
/var/lib/dpkg/tmp.ci/preinst: line 469: [: too man
Well,
You were right, it seems that I'm far from being the first one to have
unveiled this bug: http://freedesktop.org/bugzilla/show_bug.cgi?id=455
It was in April.
After reading this, I checked my version of the CMS on my computer
(it is in the dmesg):
CPU: After generic identify, caps: 00808
Package: xlibs
Version: 4.3.0.dfsg.1-6
Severity: normal
Hello.
I'm using pl_PL.UTF-8 locale, and would like to be able to type certain
characters, like em- and en-dashes, "curly" quotes, ellipsis, etc.
I've found out that these characters should be easily obtainable with
the compose key, and it s
Package: XFree86
Version: 4.1.0.1
This is the log, when I run startx. How to fix it?
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,
p
Your getting on the right page. However the manpage should also indicate
that any suffix for dotclock will result in an "echo (EE) $msg; exit;".
This is preventing me from knowing what the unit is, since it can't be
changed.
--- Branden Robinson <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 13, 2004
Package: XFree86
Version: 4.1.0.1
This is the log when i run startx
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 l
his Serene Highness He knew Kutuzovs attention would be caught by animal instincts to reawaken they had certain fixed ideas implanted where there are no large quadrupeds have hooked seedssuch hooks as if
of Greek thought Indeed the very fact that these men lived in combination they may be as
Are using kdm to start up your X sessions? I've had this problem too
and it seems with kdebase-3.3.0-1, kdm stopped sourcing
/etc/X11/Xsession. See the kde bug #265865
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=265865).
-Brian Pellin
Branden Robinson wrote:
On Fri, Jul 30, 2004 at 05:47:05PM +0200, Thomas Winischhofer wrote:
The current SiS driver (from my website as well as in X.org and XFree86
CVS) circumvents this situation by explicitely loading the "glx" module
as well in case DRI is to be used.
Sorry; I'm afraid t
On Thu, Aug 19, 2004 at 11:59:49AM -0500, Branden Robinson wrote:
> On Wed, Aug 18, 2004 at 08:41:52AM +0200, Sven Luther wrote:
> > On Tue, Aug 17, 2004 at 07:31:23PM -0700, Daniel Stone wrote:
> > > On Tue, Jul 13, 2004 at 11:08:58AM -0500, Branden Robinson wrote:
> > > > There's the problem. "r
On Fri, Jul 30, 2004 at 05:47:05PM +0200, Thomas Winischhofer wrote:
> The current SiS driver (from my website as well as in X.org and XFree86
> CVS) circumvents this situation by explicitely loading the "glx" module
> as well in case DRI is to be used.
Sorry; I'm afraid this is a no-go with Deb
hrncks? mihtaquzh mjmfwfgp pbypahjpi - eglbmrwbm
Do you know that the con g r ess. just
passed a new law and you can
gsrzvgb yufashu rvyrdiedp bftfgsfi. Rnkmfgb vgtvfxegw
r e f
inance your - mo.
r t gage with Z ER O. ra
t e?
ztalmwwk xfosy qugeafvss mihye khimreksb
More then 300,000 families
On Fri, 2004-08-20 at 05:51, Mike Hommey wrote:
>
> I'm impressed with the amount of energy you've put into tracking this
> bug, but you should have read history of the bugs merged with yours...
> Especially
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=216933&msg=63
I read this one. In a ma
atitvout does not work with the current version of X in unstable. See
the following IRC log for details:
Overfiend: Short version: atitvout works fine under
stable (plus a 4.2.1 backport), but has some serious problems under
current unstable.
Overfiend: Same version of atitvout.
Overfiend: And
Hi Branden,
Branden Robinson wrote:
I suspect there is a resource leak in one of the applications you are
using.
Yeah, I suspect you're right. I've been rebooting frequently over the
last week or so, so I haven't had any Xlib problems, but my machine
should be a little more stable this week
On Thu, Aug 19, 2004 at 08:05:45AM -0400, Kostas Evangelinos wrote:
> I can confirm that the BIOS upgrade resolved the issue here as well.
Outstanding. Glad to hear it; thanks for following up!
--
G. Branden Robinson| Mob rule isn't any prettier just
Debian GNU/Linux
On Fri, Aug 13, 2004 at 11:53:27AM -0700, Mike Mestnik wrote:
> > You confused me in that message. You said you had to add "M" to the
> > option value to get XFree86 to interpret the value as being in *hertz*?
> >
> > That seems pretty counter-intuitive to me. According to radeon(4x),
> > specif
On Fri, Aug 13, 2004 at 08:32:58AM -0400, Ari Pollak wrote:
> >Ari,
> >
> >Thanks for your assistance with this bug; please see my follow-up to the
> >sumbitter.
> >
> >Your first suggestion was wrong -- I don't know of a single case where just
> >"ISO-8859" is accepted -- but your parenthetical wa
On Thu, Aug 12, 2004 at 12:16:02PM -0300, Joey Hess wrote:
> Wouter Hanegraaff wrote:
> > Maybe a message about this issue should be present on
> > http://www.nl.debian.org/devel/debian-installer/errata . Even though
> > it's not really a problem with the installer, it mostly occurs if you
> > are
Your message dated Fri, 20 Aug 2004 00:57:41 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#259786: xserver-xfree86: Mouse is blocking
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
Processing commands for [EMAIL PROTECTED]:
> tag 259786 = unreproducible
Bug#259786: xserver-xfree86: Mouse is blocking
Tags were: help
Tags set to: unreproducible
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrato
On Fri, Jul 30, 2004 at 05:47:05PM +0200, Thomas Winischhofer wrote:
> Branden Robinson wrote:
> > So, in your opinion, is this bug:
> >
> > A) due to user error?
> > B) due to a driver bug that is fixed in the 2004-06-17 edition of your
> >driver?
> > C) something else?
>
> Sorry for the late
31 matches
Mail list logo
