/var/log/XFree86.0.log
XFree86 Version 4.2.1 (Debian 4.2.1-3 20021016191246 [EMAIL PROTECTED]) / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 3 September 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look fo
/var/log/XFree86.0.log
XFree86 Version 4.2.1 (Debian 4.2.1-3 20021016191246 [EMAIL PROTECTED]) / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 3 September 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look fo
Hello,
I have also ugly fonts after upgrading Xfree86 from 4.1.0-15 to 4.2.1-6. It's
not really the same issue, but it's near. I know another person how have the
same issue after an upgrade. Before the upgrade, all runs great.
configuration file XF86Config-4 :
Section "Files"
Hello,
I have also ugly fonts after upgrading Xfree86 from 4.1.0-15 to 4.2.1-6. It's not
really the same issue, but it's near. I know another person how have the same issue
after an upgrade. Before the upgrade, all runs great.
configuration file XF86Config-4 :
Section "Files"
I do maintain a backport of the 4.2.1-4 packages for woody [1].
Christopher Huhn <[EMAIL PROTECTED]> asked me to include a fix for a bug he
observes when using these packages together with a backported KDE 3.1.
The discussion of the bug is at [2].
The culprit is the following part of 000_stolen
unsubscribe
Title: Goodbye!
I do maintain a backport of the 4.2.1-4 packages for woody [1].
Christopher Huhn <[EMAIL PROTECTED]> asked me to include a fix for a bug he
observes when using these packages together with a backported KDE 3.1.
The discussion of the bug is at [2].
The culprit is the following part of 000_stolen
unsubscribe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Title: Goodbye!
On Thu, Mar 13, 2003 at 09:44:14AM +0100, Frank Murphy scrawled:
> So these files are created when installing the package, but the package
> system doesn't know about them? And when the package is removed, these files
> won't be removed? I would have thought that every file created with Debian
>
So these files are created when installing the package, but the package
system doesn't know about them? And when the package is removed, these files
won't be removed? I would have thought that every file created with Debian
tools (dpkg, debconf, etc.) would be accounted for.
Is it not true tha
Phil Dibowitz wrote:
XFree86 was working fine when I was using testing, but I recently
upgraded one of my boxes to sid, and since then I've had this issue. So
I'm relatively sure my XFree86Config-4 is fine.
I have solves this issue. It seems that the driver is supposed to be
"s3virge" since s
On Thu, Mar 13, 2003 at 09:44:14AM +0100, Frank Murphy scrawled:
> So these files are created when installing the package, but the package
> system doesn't know about them? And when the package is removed, these files
> won't be removed? I would have thought that every file created with Debian
>
So these files are created when installing the package, but the package
system doesn't know about them? And when the package is removed, these files
won't be removed? I would have thought that every file created with Debian
tools (dpkg, debconf, etc.) would be accounted for.
Is it not true tha
21 matches
Mail list logo
