Comment 75 for bug 753971

We're getting mixed signals from users. Some users are running custom
code, some aren't, there are many different hardware combinations and
combinations of compiz and unity packages at play here, some people
are saying that they get this issue, some aren't.

What David is trying to say here is that people reporting the same bug
and over and over is confusing internally and messing up our
priorities. DX is accountable to a huge number of groups and we need
to have a straight story here. This is especially the case with this
one, where we're tracking what seems to be a number of larger issues
manifesting with the same symptoms - it becomes very difficult to
track what's helping and what's not on one single bug report where
some people are saying "fixed" and others are saying "not fixed". This
has run on effects, such as fixes that might be helping one of the
core problems that is manifesting as this issue being reverted because
we think that it isn't working because some people are saying that it
isn't fixed because there are still unrelated underlying issues
manifesting in the same symptoms.

On Fri, Jul 22, 2011 at 7:53 AM, andreic <email address hidden> wrote:
> I still have major issues with this myself. They closed the ticket, but
> where are all those tickets tracking the "remaining" issues? Or do they
> hope we'll open new tickets again in a constant battle with them? I
> don't want to appear negative or anything, but I'm just disappointed.
> What should I state in those new tickets when the problem is as simple
> as "plug in monitor" -> "crash & burn"? I suspect they lack resources
> and would want to get rid of the bugs asap just so they can add NEW
> functionality. Perhaps someone should forward this to the people in
> charge and tell them they're not improving usability at all by creating
> ambitious projects like Unity while the rest of the code base is
> deteriorating.
>
> --
> You received this bug notification because you are a member of Canonical
> Desktop Experience Team, which is a bug assignee.
> https://bugs.launchpad.net/bugs/753971
>
> Title:
>  Display garbled when connecting external displays
>
> Status in Unity:
>  Fix Released
> Status in “unity” package in Ubuntu:
>  Fix Released
> Status in “unity” source package in Natty:
>  Fix Released
>
> Bug description:
>  This bug tracks different issues impacting systems on the target
>  certification list when running the Unity shell environment in Ubuntu
>  11.04
>
>  The complete list of problems covers:
>  1. resolution or orientation change in a single monitor setup (Bug #795454)
>  2. plugging or unplugging an external monitor (Bug #795458)
>  3. panel disappearing (Bug #795459)
>
>  The different issues can occur depending on the GPU brand and driver version used, among the list of recommended configurations:
>  * for Intel cards, the default opensource driver shipped in Ubuntu
>  * for Nvidia cards, the default closed-source driver shipped in Ubuntu
>  * for ATI cards supported by the fglrx driver, the fglrx driver shipped in Ubuntu 11.04
>  * for ATI cards not supported by the fglrx driver, the radeon driver shipped in Ubuntu 11.04
>
>  The original issue with resolution changes has been fixed the 27th of
>  April -
>  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/753971/comments/19
>
>  The affected systems include:
>
>  Sony VGN-Z540
>  Dell Inspiron 1545
>  Dell Vostro 3300
>  Dell Vostro 3500
>  Dell Vostro 3700 (2 affected systems)
>  Dell Latitude 2110
>  Dell Latitude 13
>  Dell Vostro 3400
>  Dell Vostro V13 (2 affected systems)
>  Toshiba Tecra R700
>  HP ProBook 6550b
>  Toshiba Tecra R850 (Intel)
>  Toshiba Tecra R850 (ATI)
>  Acer Aspire One
>  Dell Mini 10
>  Lenovo Thinkpad x220
>  Lenovo Thinkpad T420s
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/unity/+bug/753971/+subscriptions
>

--
Sam Spilsbury