[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#428148: marked as done (gxine crashes at startup with xserver-xorg-video-intel)

Your message dated Wed, 15 Aug 2007 10:55:41 +0200
with message-id <20070815085541.GA19077@loulous.org>
and subject line Bug#428148: gxine crashes at startup with xserver-xorg-video-intel
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 reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: gxine
Version: 0.5.11-2
Severity: important
System: debian unstable, kernel 2.6.20-1-686, Intel 855 chipset.

When starting gxine using xserver-xorg-video-i810 v. 2.0.0-1, xserver-xorg-video-intel v. 2.0.0-1, it crashes
getting the following error from the X server:
---
The program 'gxine' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 814 error_code 11 request_code 141 minor_code 19)
---

Using xserver-xorg-video-i810 v. 1.7.2-4 (testing) gxine works well.

Regards,
Jos van Wolput

--- End Message ---
--- Begin Message --- 
On Sat, Jun 23, 2007 at 10:52:18PM +0800, Jos van Wolput wrote:
>> From what I read, the problem only occurs when you use XAA with
>> Composite? EXA has been designed towards compositing, so you'd rather
>> not use XAA with Composite anyway.
>
> [...]
> I also tried EXA instead of XAA but it does not work. My fonts, icons and 
> pictures look as if the DPI is to low (not enough pixels).
> Occasionally (when X is restarted) they look good, but usually they look 
> bad.
> This problem with EXA occurs with all the versions 2:2.0.0

According to upstream, this problem is really related to XAA and might not
ever get fixed. You should just use EXA instead and forget about it.
So I am marking this bug as fixed.

If you still experience other problems with EXA as described above, with
latest driver (2:2.1.1-1 entered unstable yesterday), please open a new bug.

thanks,
Brice

--- End Message ---
Reply to: