On Tue, 2014-11-25 at 14:04 +0100, Simone Caronni wrote: > On 25 November 2014 at 13:20, Lukas Zapletal <lzap@xxxxxxxxxx> wrote: > I don't understand why I noticed this today, it looks like the > latest > update was a Critical Path one (???) when Fedora 20 was stable > for six > months. > > https://admin.fedoraproject.org/updates/FEDORA-2014-7331/xorg-x11-server-utils-7.7-6.fc20 > > > from what I've seen xorg packages are always marked as Critical Path. > > 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? > > > There's an intel driver from 18th november, for example: > > https://admin.fedoraproject.org/updates/FEDORA-2014-15384/xorg-x11-drv-intel-2.21.15-9.fc20 > > > > This seems to be much more related to your issues. I don't had any > output renaming recently in the past year (Nouveau here). FWIW my case is Intel too and this change did occur in the most recent update, over possibly a week but certainly not two weeks, and the device naming did change. > > > Regards, > > --Simone > > > > > > -- > You cannot discover new oceans unless you have the courage to lose > sight of the shore (R. W. Emerson). > > http://xkcd.com/229/ > http://negativo17.org/ > -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
