----- Original Message ---- > From: Mathieu Trudel-Lapierre <mathieu...@ubuntu.com> > To: Michael Haney <thezo...@gmail.com> > Cc: ubuntu-qa@lists.ubuntu.com > Sent: Thu, September 9, 2010 2:55:20 PM > Subject: Re: The Final Straw > > Hi Michael, > > On Wed, Sep 8, 2010 at 3:23 AM, Michael Haney <thezo...@gmail.com> wrote: > [...] > > Manually editing the xorg.conf file is the only option at this point, > > but its not something the average user can do on their own, so many > > Right. Even with experience doing this type of thing I constantly find > myself having to search for the syntax rules to write the right parts > of config to do what I want to do, and it's never a pleasant > experience. > > [...] > > submitted a Bug Report about the problem and even posted in the Ubuntu > > QA list about it, I've begged and pleased, and for more than a year > > now there's been nothing done. No progress has been made to fix this > > issue at all. Its considered a "low priority", yet more people than I > > can count have been effected by this problem. > > Could you please respond with the bug report number again? I know > you're posted in on the list before, but I believe this would have > much more benefit than petitions. It's good that you bring it up here, > and it's good that you feel strongly about this, because with some > additional work and by helping and inviting other users with the same > issues to come up and let us know about it is how you can really drive > this forward. Personally I'd be very interested in looking at the bug > report to see if something can be distilled from it -- like a pattern > of specific hardware that has the issue. > > My suggestion for you, without having seen the bug report yet, would > be to ask the people who have signed your petition (if you can contact > them again) to add information to your bug report with the make and > model of monitor they use, as well as the make and model of graphics > card. Opening new bugs and/or pointing to their own bug report is good > too. That way we can know for sure whether you are part of a small > group of unlucky people with Panashiba monitors that don't return > valid EDID information, or a larger group of people with specialized > equipment that we hadn't heard about before. > > Kind regards, > > Mathieu Trudel-Lapierre <mathieu...@ubuntu.com> > Freenode: cyphermox, Jabber: mathieu...@gmail.com > 4096R/EE018C93 1967 8F7D 03A1 8F38 732E FF82 C126 33E1 EE01 8C93
I have been considering for some time filing a bug report about nvidia and my monitor. I will hold off, for the time being, pending a reply to this message. What I would appreciate is knowing exactly what info itwould be most useful to provide. I have been using Kubuntu for many years; if my memory serves me right, I started in late 2005 with Breezy Badger. In early 2006, I upgraded to a Dell 2405 FPW LCD widescreen monitor. I have used this monitors with two different desktops, both with nVidia graphics adapters. The latest is now almost three years old; again, by memory (I am not at home), it is a GS7600. The nVidia card and drivers have always driven the monitor at 1920x1200. This adapter / monitor combination has always worked well with every release of Kubuntu up to and including 10.04 (lucid) --- and until the release of the first development builds of Maverick. In Maverick, I have never once been able to raise the screen resolution beyond 1440 x 1024. I have used both native KDE utilities and nvidia utilities and have re-installed the driver (using the cli utility jockey-text) several times. The Maverick set-up is now entirely foo-barred. A graphical session always fail with the low-res "graphics problem" dialogue; attempts to log into a login virtual console simply leave me staring at a black screen without even so much as a flashing cursor. It has been a while and I cannot recall what happens if I try to boot into a recovery console. Because I know that it is a development release, I do most of my work in Lucid and changes in my personal situation have delayed plans to reinstall Maverick from scratch. I shall try booting into a recovery console to see what can be salvaged. If I cannot manage anything, I will re-install. If that continues to leave me unable to bring up 1920 x 1200, please let me know what information would be most useful to help troubleshoot the problem. Should I do it here? or in a bug report? or both? -- Bruce Miller, Ottawa, Ontario, Canada br...@brmiller.ca; (613) 745-1151 Just when you think your software is idiot proof, somebody comes up with a better idiot Keyboard not found...Press any key to continue. -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
