<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 25 November 2014 at 13:20, Lukas Zapletal <span dir="ltr"><<a href="mailto:lzap@redhat.com" target="_blank">lzap@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I don't understand why I noticed this today, it looks like the latest<br>
update was a Critical Path one (???) when Fedora 20 was stable for six<br>
months.<br>
<br>
<a href="https://admin.fedoraproject.org/updates/FEDORA-2014-7331/xorg-x11-server-utils-7.7-6.fc20" target="_blank">https://admin.fedoraproject.org/updates/FEDORA-2014-7331/xorg-x11-server-utils-7.7-6.fc20</a></blockquote></div><br></div><div class="gmail_extra">from what I've seen xorg packages are always marked as Critical Path.<br><br>The update you are referring to is six months old, are you sure the xrandr command is the culprit and not something else? Did you skip updates for six months?<br><br></div><div class="gmail_extra">There's an intel driver from 18th november, for example:<br><br><a href="https://admin.fedoraproject.org/updates/FEDORA-2014-15384/xorg-x11-drv-intel-2.21.15-9.fc20">https://admin.fedoraproject.org/updates/FEDORA-2014-15384/xorg-x11-drv-intel-2.21.15-9.fc20</a><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">This seems to be much more related to your issues. I don't had any output renaming recently in the past year (Nouveau here).<br><br></div><div class="gmail_extra">Regards,<br></div><div class="gmail_extra">--Simone<br><br></div><div class="gmail_extra"><br clear="all"></div><div class="gmail_extra"><br>-- <br><div class="gmail_signature"><div dir="ltr">You cannot discover new oceans unless you have the courage to lose sight of the shore (R. W. Emerson).<br><br><a href="http://xkcd.com/229/" target="_blank">http://xkcd.com/229/</a><br><a href="http://negativo17.org/" target="_blank">http://negativo17.org/</a><br></div></div>
</div></div>