GNOME 3 Shell and fglrx fixed in next driver!

So we all complained about fglrx not working with GNOME Shell and it was evil AMD closed source drivers ignoring GNOME users, at least that is what you would think.

The opposite is true here it seems.
As we can read in this bugzilla report. A bugzilla that is not owned by AMD.

We can see AMD respond explaining they noticed the problem 2011-08-10 and it was fixed within 2 days.
They also explain that it takes 4 weeks to go through QA testing before it finally gets released. That obviously makes sense to anyone.

So how can things take this long? Didn’t GNOME developers actually test gnome-shell with fglrx drivers? Didn’t distributions that noticed the bug realize the Bugzilla wasn’t even owned by AMD at all? What would have happened if GNOME developers actually reported this to AMD while GNOME Shell was in a more early development cycle back in 2010?


Thank you AMD! Looking forward for the 11.9 driver that will hopefully come out within 4 weeks.

“Nelson Marques 2011-05-25 23:30:05 UTC
ATI/AMD needs to fix this, not really us… I’ve opened this bug report on
their end, and other distro’s have the same issue…”

  1. #1 by kaddy on August 24, 2011 - 12:09 pm

    AMD You guy’s are Awesome… thanx for paying attention to Linux! I see your Graphics cards getting better and better in Linux due to better drivers and release of source/specs… I will be buying an ATI next time after 10 years of having Nvidia…

  2. #2 by starsilk on August 24, 2011 - 5:14 pm

    and what about the message from ‘John Bridgman’ from AMD on June 7th saying they are aware of the bug? hardly two days…

    • #3 by joostruis on August 24, 2011 - 5:42 pm

      I didn’t realize he was working for AMD. (doh! that I missed that) Yes that indeed makes it a bit weird.

  3. #4 by admiral0 on August 24, 2011 - 9:30 pm

    Why don’t you open an official bugzilla? GNU/Linux users do better quality error reports.

    • #5 by joostruis on August 24, 2011 - 9:58 pm

      Why are you asking me? I’m not working for AMD.

  4. #6 by jackd on August 25, 2011 - 1:02 am

    It’s just silly for anyone at AMD to claim that they were unaware of that bug until this month.

    The bug was first reported in the first version of ubuntu unity (9.10). (The initial version of unity used mutter before it switched to compiz. Gnome3 uses mutter)

    I personally reported this problem directly to AMD back in March with the first Fedora 15 release. This was their “Linux Crew Driver Feedback” page (on the download page:

    • #7 by TGM on August 25, 2011 - 9:47 am

      “It’s just silly for anyone at AMD to claim that they were unaware of that bug until this month”

      I don’t agree. Do you expect a member of AMD to be doing a Google Search once a day for “AMD Bug Linux” or something similar? And how many of them will be packaging errors or even PEBCAK?

      It seems that AMD need to sort themselves out a public bugtracker but if you publish a bug on the wrong website, you’ll deserve the wait you get.

  5. #8 by jackd on August 25, 2011 - 1:14 am

    (Note that I’m still happy with AMD, that they are committing resources to their linux driver. I just think it’s a little disingenuous to claim that they fixed the bug in 2 days. The problem was well known to any user of ubuntu “netbook” last year, and to any user of Fedora 15 which was released in May).

  6. #9 by Ryan Farmer on September 11, 2011 - 9:37 am

    “Didn’t GNOME developers actually test gnome-shell with fglrx drivers?”

    Why is it their responsibility? The driver is proprietary garbage from AMD, AMD took 5 months to fix it, complain to them. I doubt they really care about anything that’s not a proprietary video game on Ubuntu…

    • #10 by detructor on March 2, 2012 - 10:07 pm

      well, according to the programer from AMD @that bugtracker link, Gnome devs failed to follow the OpenGL specification. In that case it would be the fault of the Gnome team.

  7. #11 by Someone on September 16, 2011 - 8:02 pm

    Maybe you guys can update or make a sticky of how to block anything gnome 3 and not just the failed attempt to block gnome 3 by some kde user in your forums that uses limbo what ever that is ?

    This below is useless for Sabayon 6 gnome x86_64 dvd.

    # Masked packages




    # equo install gnome -p
    >> !!! Please update the following critical packages:
    >> # >sys-libs/glibc-2.11.9999
    >> !!! You should install them as soon as possible
    >> @@ These are the chosen packages:
    >> # (1/1) [sabayon-weekly] gnome-base/gnome-3.0.0
    >> Versions: Not installed / NoTag / NoRev ===> 3.0.0 / NoTag / 0
    >> Action: Install
    >> @@ Packages involved: 1
    >> @@ Calculating dependencies …
    >> :: (100.0%) Sorting dependencies ::^C

    Also what is up with the defective equo that always wants to install all updates even though I just need app-misc/mc and then pulls in this gnome 3 garbage that completely destroys my Sabayon.

    equo install app-misc/mc

    PS> sabayon6 x86_64 E17 does not ahve anythign network related so I can not even get on the internet

  8. #12 by ttux on September 29, 2011 - 8:35 am

    They didn’t fix it, install the catalyst 11.9 driver and try, you will see how it’s still completely broken. The only thing they fixed it seems is the rainbow bar.

  9. #15 by ... on October 1, 2011 - 9:22 pm

    TGM: ATI Linux Platform Bug Reporting:

  10. #16 by David Raid on October 14, 2011 - 2:51 pm

    Installed 11.9. The bar is fixed, but Gnome-Shell remains buggy. It seems stable enough until you try to run Skype. Then the notification bar causes major graphical glitches and the activities window becomes unstable.

  11. #17 by Thomas Holbrook II on November 7, 2011 - 4:27 pm


    While your position is understandable, it still would have been a good idea for the GNOME devs to test with FGLRX, especially if they want more people to adopt the environment in question.

  12. #18 by I like pie on February 2, 2012 - 2:33 am

    As far as I’m concerned the blame is 50/50.

    One of the current positions from ATI/AMD that gnome devs didn’t test compatibility nor even attempt to communicate the issue. We’ve seen this pattern of short-sighted/ego-driven behavior before with the transition from Gnome 2.x to 3.x just to keep developers busy and “let’s make this whole thing 3D so we get decent 3d support, but lets not communicate with the video card manufacturers to help make that happen but instead we’ll make them come to us. And when things don’t work as they do on the only configuration that we tested it on, it must be someone else’s fault. And while we’re at it, let’s make it harder to add a printer courtesy of a patch that adds a Fedora-specific requirement that isn’t even available on other distros because it’s not our fault that not everyone else uses Fedora”.

    On the other hand, someone from Ati/AMD made a comment that they don’t have time to test every new distro or every new DE, which is irrelevant since just testing a couple of the major distros would have been enough, considering these issues are not even distro specific but only DE specific. Secondly, Gnome has been a major DE for a long time. You’d think if Ati/AMD devs were serious about supporting Linux they’d at least be aware that support for all of Gnome 2.x was dropped in favor of Gnome 3.x.

    Bottom line, it’s time for both parties to bury their egos and work on the problem together instead of blaming each other.

  1. LXer: Gnome 3 shell and fglrx fixed in next driver! | Coders & Admins
  2. Links 24/8/2011: Fedora 16 Alpha, South Korean Government Wants Own Free/Libre OS | Techrights
  3. Gnome 3 shell and fglrx fixed in next driver! | Linux | Syngu
  4. Problem of ATI and GNOME 3
  5. stamina precision rower 1205
  6. I nuovi driver proprietari ATI fglrx supporteranno GNOME 3 |
  7. zastitne folije

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: