Comment 4 for bug 1554004
Revision history for this message
|
|
#4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hi Dariusz,
Okay, I just noticed that you have a Canonical e-mail address.
I am the project maintainer for OpenChrome at this point (I obtained commit privilege about 2 weeks ago.) since no one other than myself has done commits for the past 8 months or so.
https:/
I am getting OpenChrome Version 0.3.4 ready for release within a week, and I will like to know how I can get Canonical to adopt it.
https:/
This is what I will like to see happen.
- For those Ubuntu with OpenChrome Version 0.3.3, please replace it with OpenChrome Version 0.3.4.
This includes Ubuntu 14.04 LTS and later releases.
Version 0.3.3 has the very bug you are dealing with, and this bug has been fixed between the current master branch and when Version 0.3.3 was released.
- For those Ubuntu with OpenChrome Version 0.2.x, please hold off from updating it with OpenChrome Version 0.3.4 at this point
I am talking about Ubuntu 12.04 LTS specifically.
This is due to the fact that there is a bug in the code that affects computers with a DVI-I output (i.e., a DVI connector that has both DVI and VGA signals come out of it), and more specifically, if DVI to VGA adapter is used.
This feature was working in OpenChrome Version 0.2.904 that shipped with Ubuntu 12.04 LTS.
Unfortunately, OpenChrome Version 0.3.x appear to have broken it.
https:/
It is taking a long time in fixing this bug due to the fact that the person who reported it uses a thin client (i.e., no hard drive), and he needs to update his SD card to boot PuppyLinux (Ubuntu based).
I do not really have a functioning computer with VIA Technologies IGP that comes with DVI-I at this point, so I am not really able to fix it in a timely manner.
Version 0.3.4 will likely ship without fixing this bug.
I will try to fix this bug in the future release.