Your message dated Wed, 27 Feb 2008 19:11:56 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#458099: xserver-xorg-video-intel: Please consider
packaging old i810 driver again
has caused the Debian Bug report #458099,
regarding xserver-xorg-video-intel: Please consider packaging old i810 driver
again
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 reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
458099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=458099
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: xserver-xorg-video-intel
Version: 2:2.2.0-1
Severity: wishlist
The new xserver-xorg-video-intel driver has never worked properly for
me; there are several showstoppers (which I've been dutifully filing
into xorg's bugzilla), and so I've been using a kind of backport of
version 1.7.2-4 of the i810 driver. It looks from the BTS like I'm not
the only one having problems with the new driver, and so it seems to me
that it would be nice to provide a package for the old driver until the
new one gets more stable.
Thanks.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages xserver-xorg-video-intel depends on:
ii libc6 2.7-5 GNU C Library: Shared libraries
ii libdrm2 2.3.0-4 Userspace interface to kernel DRM
ii xserver-xorg-core 2:1.4.1~git20071212-2 Xorg X server - core server
xserver-xorg-video-intel recommends no packages.
--- End Message ---
--- Begin Message ---
Andrew Moise wrote:
> This is less of an issue for me now, since upstream has started
> fixing my bugs instead of just claiming my hardware is broken or
> assigning them all to Keith Packard :-). I'm now using the new intel
> driver (locally compiled from a git snapshot with some recent fixes)
> and it's working acceptably for me, so AFAIC this bug can be closed.
>
Ok, done, thanks.
Brice
--- End Message ---
