Author: branden
Date: 2004-03-19 00:39:37 -0500 (Fri, 19 Mar 2004)
New Revision: 1169
Modified:
trunk/debian/local/FAQ
Log:
Add another paragraph per suggestion from Ingo Saitz.
Modified: trunk/debian/local/FAQ
===
--- trunk/debi
Author: branden
Date: 2004-03-19 00:27:06 -0500 (Fri, 19 Mar 2004)
New Revision: 1168
Modified:
trunk/debian/NEWS
trunk/debian/changelog
trunk/debian/local/FAQ
Log:
Add FAQ entry about the key problem.
Edit news item about the problem to tidy up the wording a little and
direct people t
Your message dated Thu, 18 Mar 2004 23:45:32 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#238815: Acknowledgement ([radeon] X server segfaults in -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 i
I may have been a bit too hasty with the send button: I tried reverting
to -5, and the problem persists. It might still be an X problem, but
today's update was not what caused it. (I'm not sure what DID cause it,
though -- I've reverted all the upgrades that look vaguely likely to
cause a probl
Package: xserver-xfree86
Version: 4.3.0-7
Severity: important
Tags: sid
Since I upgraded the X server today, X refuses to start; exhibit A
(Xfree86.0.log) is its error log. The second attachment, XFree86.1.log,
is from an earlier version of the server that worked (-5, not -6)
The one extreme
Author: branden
Date: 2004-03-18 23:13:39 -0500 (Thu, 18 Mar 2004)
New Revision: 1167
Modified:
NEWS.xhtml
Log:
Correct a couple of broken links.
Fix all URLs to necrotic to omit the host portion (it's not wise to
hard-code the specific hostname).
Modified: NEWS.xhtml
===
Author: branden
Date: 2004-03-18 23:07:59 -0500 (Thu, 18 Mar 2004)
New Revision: 1166
Modified:
NEWS.xhtml
Log:
Redirect package changelog and TODO links to branches/4.3.0/sid checkout,
since that's where the next release to Debian unstable will actually come
from.
Modified: NEWS.xhtml
==
Author: branden
Date: 2004-03-18 23:03:09 -0500 (Thu, 18 Mar 2004)
New Revision: 1165
Modified:
NEWS.xhtml
Log:
Add item announcing 4.3.0-7 release.
Modified: NEWS.xhtml
===
--- NEWS.xhtml 2004-03-18 19:55:46 UTC (rev 1164)
+++
I can also confirm this on my system (Dell GX240, ATI Rage 128 Pro Ultra
TF). It behaves identically to the report in the XFree86 bug DB as
well: the X server locks with 99% of the CPU, no mouse/keyboard; killing
the X server works, but if you restart it it goes right back to 99%.
The only way out
On Thu, Mar 18, 2004 at 12:50:08AM +0100, Mowgli wrote:
> > What version are you running *now*?
>
> Oh, ähm, I do not know why reportbug didn't report the version. It is
> version 4.3.0-5
Okay.
> > Does this bug affect any applications that aren't linked against
> > libgtk1.2? If not, how can y
Package: xfree86-common
Version: 4.3.0-7
Severity: wishlist
Hi,
could you add to the post-install-scripts for the xfree-packages
that an update of the fontconfig cache will be done after upgrading X?
Because if it's not done, something, which stands in relation to
fontconfig, does slowdown the st
Processing commands for [EMAIL PROTECTED]:
> clone 238750 -1
Bug#238750: installation-reports
Bug 238750 cloned as bug 238777.
> retitle -1 defaults to vesa, not savage for S3 Inc. 86C270-294 Savage/MX-MV
Bug#238777: installation-reports
Changed Bug title.
> reassign -1 xserver-xfree86
Bug#23877
Package: xbase-clients
Version: 4.2.1-12.1
Severity: normal
File: /usr/X11R6/bin/xvidtune
Followup-For: Bug #175296
I start xvidtune (from a terminal window).
I expect the xvidtune program window (and the usual warning window) to
pop up.
What happens instead is that I get the following error m
reassign 237970 libxrender1
thanks
> downgrading libxrender1 from 0.8.3-7 to 0.8.3-5, solve the fuss.
> Please reassign the bug, glad it s not fontconfig .
I find it quite surprising; I'm not aware of such grave problems with
libxrender1 0.8.3-7. Can you still reproduce this issue?
Regards,
--
Author: branden
Date: 2004-03-18 14:55:46 -0500 (Thu, 18 Mar 2004)
New Revision: 1164
Modified:
trunk/debian/TODO
Log:
Add four items.
Modified: trunk/debian/TODO
===
--- trunk/debian/TODO 2004-03-18 18:37:46 UTC (rev 1163)
+++
Author: branden
Date: 2004-03-18 13:37:46 -0500 (Thu, 18 Mar 2004)
New Revision: 1163
Modified:
trunk/debian/changelog
Log:
Add historical bug-closer.
Modified: trunk/debian/changelog
===
--- trunk/debian/changelog 2004-03-1
Author: branden
Date: 2004-03-18 10:41:13 -0500 (Thu, 18 Mar 2004)
New Revision: 1162
Added:
tags/4.3.0-7/
Log:
Tag 4.3.0-7 release.
Copied: tags/4.3.0-7 (from rev 1161, branches/4.3.0/sid)
Author: branden
Date: 2004-03-18 10:40:35 -0500 (Thu, 18 Mar 2004)
New Revision: 1161
Modified:
branches/4.3.0/sid/debian/changelog
branches/4.3.0/sid/debian/patches/003_linux.cf_and_xfree86.cf.diff
branches/4.3.0/sid/debian/patches/004_imake_manpage_handling_overhaul.diff
branches/4.
clone 238629 -1
retitle -1 x-dev: hideous namespace pollution in Xosdefs.h
severity -1 normal
thanks
On Wed, Mar 17, 2004 at 06:30:48PM -0800, Daniel Schepler wrote:
> Package: kali
> Severity: serious
> Version: 3.1-4
>
> >From my build log:
>
> ...
> cc -DXFORM -O2 -g -Wall -I/usr/include/X11
On 2004-03-18 Andreas Metzler <[EMAIL PROTECTED]> wrote:
> I *think* neither of the build-errors are xfree86's fault, they rather
> look like subspace anomalies on the buildd.
[...]
At least the alpha-error is simple to diagnose:
---
dh_install --sourcedir=debian/tmp
cp: writing
`debian/x
.0/build-tree/xc'
make[1]: *** [World] Error 2
make[1]: Leaving directory `/build/buildd/xfree86-4.3.0/build-tree/xc'
make: *** [stampdir/stamp-build] Error 2
**
Build finished at 20040318-0759
FAILED [dpkg-buildpackage died]
21 matches
Mail list logo
