Bug#493887: xserver-xorg-video-glint: Crash after start message output INVALID MEM ALLOCATION

To: 493887@bugs.debian.org
Cc: Daniel Smolik <marvin@mydatex.cz>, Dan Smolik <marvin@sitour.cz>
Subject: Bug#493887: xserver-xorg-video-glint: Crash after start message output ****INVALID MEM ALLOCATION****
From: Cyril Brulebois <kibi@debian.org>
Date: Mon, 28 Feb 2011 03:48:16 +0100
Message-id: <[🔎] 20110228024816.GA13146@debian.org>
Reply-to: Cyril Brulebois <kibi@debian.org>, 493887@bugs.debian.org
In-reply-to: <20080805204844.GE5026@patate.is-a-geek.org>
References: <20080805181438.15069.44205.reportbug@shiva.sitour.cz> <20080805184838.GA4928@patate.is-a-geek.org> <4898BA87.3000409@mydatex.cz> <20080805204844.GE5026@patate.is-a-geek.org>

Hi Daniel,

Julien Cristau <jcristau@debian.org> (05/08/2008):
> It's in experimental now, and will be in sid after lenny releases.

it's been a while. Ping?

KiBi.

Attachment: signature.asc
Description: Digital signature

Reply to:

Prev by Date: Bug#590431: xserver-xorg-video-openchrome: cannot start X with VX800 Chipset
Next by Date: Bug#555294: xserver-xorg-video-ivtv: TV output on Hauppauge PVR 350 stops working after upgrade
Previous by thread: Bug#590431: xserver-xorg-video-openchrome: cannot start X with VX800 Chipset
Next by thread: Bug#555294: xserver-xorg-video-ivtv: TV output on Hauppauge PVR 350 stops working after upgrade
Index(es):
- Date
- Thread

Bug#493887: xserver-xorg-video-glint: Crash after start message output ****INVALID MEM ALLOCATION****

Bug#493887: xserver-xorg-video-glint: Crash after start message output INVALID MEM ALLOCATION