or to isolate it? Somehow I don't think this is necessarily
an Xorg base or driver issue.
--
Pekka Savola You each name yourselves king, yet the
Netcore Oykingdom bleeds.
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--
fedora-devel-list
or rolling back to radeonhd
helped; maybe something changed between F11 and F12.
I filed a PR: https://bugzilla.redhat.com/show_bug.cgi?id=542398
--
Pekka Savola You each name yourselves king, yet the
Netcore Oykingdom bleeds.
Systems. Networks. Security. -- George
) open
on this.
--
Pekka Savola You each name yourselves king, yet the
Netcore Oykingdom bleeds.
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman
for Fedora 12 in
updates-testing repository. Specific bug reports are definitely going to
help.
Well, here's one graphics regression:
https://bugzilla.redhat.com/show_bug.cgi?id=540476
radeon.modeset=0 worked around the problem.
(I'm not sure if it's filed against the right component.)
--
Pekka
)
--
Pekka Savola You each name yourselves king, yet the
Netcore Oykingdom bleeds.
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel
or gnome weren't updated within the next 3 months or so.
--
Pekka Savola You each name yourselves king, yet the
Netcore Oykingdom bleeds.
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
