On Wed, 25 Jul 2007, Julien Cristau wrote:
On Fri, May 4, 2007 at 19:27:03 +0100, Robert de Bath wrote:
Well, looks like I was wrong, the current unstable (1:7.2-3) locks up
with 100% cpu. The process can be kill -9'd and the attached log is what
remains. In addition after resetting the conso
On Fri, May 4, 2007 at 19:27:03 +0100, Robert de Bath wrote:
> Well, looks like I was wrong, the current unstable (1:7.2-3) locks up
> with 100% cpu. The process can be kill -9'd and the attached log is what
> remains. In addition after resetting the console I can see the messages:
>
> " f000:505
Robert de Bath wrote:
> On Sun, 29 Apr 2007, Brice Goglin wrote:
>
>> Hi Robert,
>>
>> A couple months ago, you reported a bug to the Debian BTS regarding the
>> X server being very slow with the vesa driver. Does this problem still
>> happen today? There has not been many changes upstream in the v
On Sun, 29 Apr 2007, Brice Goglin wrote:
Hi Robert,
A couple months ago, you reported a bug to the Debian BTS regarding the
X server being very slow with the vesa driver. Does this problem still
happen today? There has not been many changes upstream in the vesa
For stable and testing ...
xse
Hi Robert,
A couple months ago, you reported a bug to the Debian BTS regarding the
X server being very slow with the vesa driver. Does this problem still
happen today? There has not been many changes upstream in the vesa
driver, but the X server core changed at lot. Could you try with
xserver-xorg
5 matches
Mail list logo
