<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>
<style type="text/css">
@page {
margin: 2cm
}
p {
margin-bottom: 0.25cm;
line-height: 120%
}
</style> </p>
Op 28-05-17 om 14:18 schreef Luca Boccassi:<br>
<blockquote class=" cite"
id="mid_1495973939_14971_7_camel_gmail_com"
cite="mid:1495973939.14971.7.camel@gmail.com" type="cite">
<pre wrap="">On Fri, 2017-05-26 at 13:37 +0200, Hugo Sepulveda wrote:
</pre>
<blockquote class=" cite" id="Cite_7716779" type="cite">
<pre wrap="">I've isolated the problem, it seems the DisplayPort does not get
initialized. Have no other OS to test this behaviour, not a
replacement
GPU card. However i really doubt the displayport just "died" on me,
neither is the error caused by hardware failure of the screen itself.
Admitted, it's a luxury problem (i cna still work with 2 display's
connected to the DVI ports), but it used to work fine with 3, now
it's
all fubar, and X is tripping.
Maybe that helps. If you need any additional info, i'm happy to
provide it.
</pre>
</blockquote>
<pre wrap="">If 375.66 fixes the problem, it might be just your lucky day!
CVEs have been revealed and they are fixed by that version, so I have
now uploaded it to unstable. Due to the security implications I've
requested the release team to allow it to migrate to testing as well,
and after that happens we will upload to jessie-backports too.
It will take a few days to a couple of weeks to happen.
Kind regards,
Luca Boccassi</pre>
</blockquote>
That would be really wonderful! Great way to start of a monday. <br>
Thank you again for your efforts, I'll get back on this issue after
the new version has been released on backports to give a status
update.<br>
<br>
<br>
With kind regards,<br>
<br>
Hugo<br>
<br>
</body>
</html>