On Sat, Aug 18, 2012 at 6:35 PM, Julien Cristau jcris...@debian.org wrote:
Please package a version = 2.4.34 or backport the patches mentioned in
this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=53222
Why did you file a duplicate then?
I felt a separate bug against libdrm was
Package: libdrm-intel1
Version: 2.4.33-3
Severity: important
If X is started with this libdrm on a machine with Ivy Bridge GT2
Server Intel graphics, it crashes and leaves the machine in an almost
unusable state (network/ssh might remain up). X is certainly completely
unusable, as it won't start.
The problem has fixed itself with today's updates.
It can't have been the kernel or libc after all, neither was in this
round of updates.
Anyway, feel free to close, unless you still want to isolate the cause.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of
Package: xserver-xorg-core
Version: 2:1.10.2-1
Severity: important
Happens reliably on every startup, not on intermittent problem.
This is a very recent development. I suspect either the new kernel or
the new libc.
-- Package-specific info:
X server symlink status:
Julien Pinon wrote:
Le mardi 23 novembre 2010 à 21:40,
Cyril Brulebois k...@debian.org écrivait :
If you feel like getting this fixed, find the actual culprit (on the
gnome side, as suggested by Julien), and reassign it there.
I digged a little bit, and found that maybe the problem
Samuel Thibault wrote:
Maik Zumstrull, le Tue 26 Oct 2010 12:45:19 +0200, a écrit :
XKBMODEL=pc105
XKBLAYOUT=de
XKBVARIANT=nodeadkeys
XKBOPTIONS=compose:rwin
Mmm, I'm getting +compose(rwin) here with your keyboard
configuration... Just to make sure keyboard-configuration does its
6 matches
Mail list logo