Tim: >> But it's kind of hard to believe that all the bugs a person might have >> reported can't be fixed within the same release. As the original >> responder suggested, why bother making reports... Tom Horsley: > Because sometimes they become a source of great amusement like > this one: > > https://bugzilla.redhat.com/show_bug.cgi?id=451562 I seem to remember a similar situation, when I installed Fedora 17. It wanted to run at a rate faster than my monitor could handle. I had to modify GRUB, so it was text-only, else the screen shut-off pre-boot. And I had to modify GDM, for the same reason. Since my personal login let me set a screen resolution that worked (after using another monitor, to see what I wanted to do), I worked out that I could set GDM's with the same configuration file. Copying, if I remember the file name and path correctly, my ~/.config/monitors.xml file to GDM's home space (older releases used ~/.gnome2/monitors.xml). Or, as I did on another computer, modifying the file to have useful parameters, from a text-only console. I've never gone in for this bodging the screen dimensions or DPI to something false, though. You get poor resolution, and strange sizing issues. Not to mention an inability to set actual real-world measurements of things on-screen, and system coders aren't motivated to make it easy for users to properly configure their displays, when some hack that *appears* to work is used. I set up the screen details properly, and pick appropriately sized fonts. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
