<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:bensberg@justemail.net" title="Benno Schulenberg <bensberg@justemail.net>"> <span class="fn">Benno Schulenberg</span></a>
</span> changed
<a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91966">bug 91966</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>RESOLVED
</td>
<td>REOPENED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>WONTFIX
</td>
<td>---
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91966#c24">Comment # 24</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91966">bug 91966</a>
from <span class="vcard"><a class="email" href="mailto:bensberg@justemail.net" title="Benno Schulenberg <bensberg@justemail.net>"> <span class="fn">Benno Schulenberg</span></a>
</span></b>
<pre>Hello Christopher,
No, this is not a "wontfix" bug; it is more like a "cantfix because dont know
how" one. It seems that Xavier is the only maintainer at the moment, and as
far as I know he does not have the expertise to really fathom what is going
wrong. Correct me if I'm wrong, Xavier. (Hi there, BTW! :)
But, Christopher, you say you got a visible desktop on an older Puppy version?
Is that reproducible, or was it a fluke? If reproducible, then good, because
you are able to build from git. You could then do:
git checkout release_0_2_904
and then build and install that, and you should have a working openchrome
driver on your newest Puppy distro.
When that works, you could try building 905, 906... and so on (look at the
output of 'git tag'), until it breaks. When you've found the version where it
breaks, you can try to bisect ('git help bisect') to find the commit that broke
things. It's a lot of work, but if you have the time and the willingness, you
can find the problem.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>