[Ubuntu-x-swat] [Bug 602809] Re: add Mouse Click Debounce Feature?
This isn't just of value to people who happen to have a mouse that's a bit iffy, who get a bad impression of Ubuntu because the same mouse works fine on Windows (see bug #1). It's possibly also of benefit to those who have difficulty with muscle control, especially the elderly. Maybe this bug can get a raised profile if we play the accessibility card? But most likely what it takes is some capable volunteer to write the code to fix it and get a patch accepted. Few of the bugs I've marked as "me too" ever get fixed by Canonical. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/602809 Title: add Mouse Click Debounce Feature? To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/602809/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 602809] Re: add Mouse Click Debounce Feature?
Affects me with one mouse on Mint 18.3 (also verified on another pc with Ubuntu 16.04). See extensive discussion, including how to investigate with xev, detailed code fix for xserver-xorg-input-evdev, detailed hardware workarounds for mice with contact bounce: https://askubuntu.com/questions/321816/mouse-sometimes-doubleclicks-when-i-click-once I'm amazed the software debouncing still hasn't been incorporated. And debounce time etc ideally should be exposed to the user in the control panel, to allow adjustment? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/602809 Title: add Mouse Click Debounce Feature? To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/602809/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1316035] Re: matrox g200eR2 is unclaimed in 14.04
Presumably Ubuntu devs will not be interested in this. It needs reporting by everyone to the Xorg developers to get their attention. How does one do that? Does anyone know WHY they decided to rip out XAA (whatever that is)? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1316035 Title: matrox g200eR2 is unclaimed in 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1316035/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 842424] Re: Don't remember keyboard layout settings
** Summary changed: - Don't remeber layout settings + Don't remember keyboard layout settings -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/842424 Title: Don't remember keyboard layout settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/842424/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
Hi Tormod, Thanks for your follow-up, I appreciate it very much. I'd be happy to blow the dust off my HP Brio and try either or both 10.10 or Natty, if you feel it's likely to help others. I've abandoned this PC (indeed I would have dismantled and scrapped it, except that I felt I should hang onto it in case it helped). I've become aware that focussing on this problem may be taking resources away from other bug fixing. As you say, support for these very old cards can't be top of the list. The question in my mind is whether there are still people out there for whom support for this card is important. Realistically, I suspect their best option is to add a cheap PCI video card and disable the onboard Matrox. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. https://bugs.launchpad.net/bugs/393129 Title: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
Why is this still marked 'incomplete' despite my report in May (#11)? What, if anything, is still needed, to move this forward? No offence intended, but is 'Bryce Harrington' actually a 'bot? All responses from him seem to me as though they may be automatically generated. Am I being suckered into having a conversation with thin air? I want to help the community, so please tell me if I'm wasting my time. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. https://bugs.launchpad.net/bugs/393129 Title: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 373281] Re: Xorg Cannot Determine Monitor Resolution on Bootup in Jaunty
I still have an HP Brio with Matrox G200 card, and am willing to do further tests on it (see also bug #393129). ** Changed in: xserver-xorg-video-mga (Ubuntu) Status: Expired = Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. https://bugs.launchpad.net/bugs/373281 Title: Xorg Cannot Determine Monitor Resolution on Bootup in Jaunty ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
Why is this still marked 'incomplete' despite my report in May? -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
No response from Bryce, so today I attempted installation of this week's build of Debian 'testing'. Had to abandon that, due to a partitioning problem (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583592), may retry when this is fixed. Instead installed Debian 'stable' (Lenny). No video corruption, but resolution is only 832x624, and this is the highest resolution offered in screen prefs dialog. File /etc/X11/xorg.conf exists but has little in it, i.e. device, monitor, and screen are all of the form Configured [whatever] (attached). I'm disappointed nobody has got back to me with advice on how to provide more info. ** Bug watch added: Debian Bug tracker #583592 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583592 ** Attachment added: xorg.conf from install of Debian Lenny http://launchpadlibrarian.net/50001202/xorg.conf -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
Hi Bryce, thanks for reviewing this. Not sure why you've added 'hardy' tag at this time. Is that a request for further info on 8.04? I still have install media back to 6.06, so if you want additional info on 8.04 on this computer I can supply. I also tried Puppy 5 on this machine this week. Bad news: in contrast with previous versions of Puppy, which performed rather well, 5 has a corrupt screen. Puppy 5 is based on Lucid, so this is not surprising. :( I've not yet tested with Debian. Would you be interested in this? If so, which version(s)? -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
Thank you for your continuing interest. Yesterday I installed from ubuntu-10.04-alternate-i386.iso and the symptoms are still the same. Please let me know if there is any further info I can provide, or if you have recommendations on how fixing this can be progressed. Please review my comments in #3 and #6 and note that, over the years, Ubuntu has regressed from having a less than optimal display on this machine to being totally unusable by a new user, a Very Bad First Impression of Ubuntu... whereas other distros handle this machine quite well and Windows 2000 is excellent (which is something I really loathe saying). I hate whining and I would like to be part of the solution. -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
Thanks for updating this. Just confirming that I still have the PC that exhibited this problem and can provide further reports on more recent versions if that's helpful. -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
Response to yr #7: Post #4 already gives lspci -vvnn. Attaching xorg.0.log here. If you would like me to retest on karmic alpha4 instead (or later if available) I'd be happy to do so. ** Attachment added: xorg.0.log from 9.04 http://launchpadlibrarian.net/31393813/Xorg.0.log -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
** Description changed: Binary package hint: xserver-xorg-video-mga Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) HP Brio, Celeron 300MHz with 256Mb ram - On board Matrox G100 8Mb + On board Matrox G100 2Mb NEC LCD1860NX flat screen (native resolution 1280x1024) + + [update] When I filed this originally I reported 8Mb video (possibly as a result of + reading HP Brio reviews), but I now believe it to be 2Mb. I have also tried a CRT display and had identical symptoms, so I doubt this problem is specific for this screen. The attached photo shows the display on first booting after installing Ubuntu 9.04. It looks similar to a TV that's lost the horizontal hold, and is also displaced a little to the right and down. Although some features can be made out, the content is shown as if 3 copies are overlaid in vertical stripes. The next attached photo shows this more clearly, taken after logging in blind. Note how, in the top panel, the time is visible in 3 places. I found that Puppy and Mepix do not exhibit this problem. The next experiment was to take the xorg.conf generated by the Puppy wizard and reduce it to the following, replacing the empty /etc/X11/xorg.conf with: start Section ServerFlags Option RandR on EndSection Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section InputDevice Identifier Keyboard0 Driver kbd Option XkbRules xorg Option XkbModel pc102 Option XkbLayout us #xkeymap0 EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto #mouse0protocol Option Device /dev/mouse #Option Emulate3Buttons #Option Emulate3Timeout 50 Option ZAxisMapping 4 5 #scrollwheel EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model HorizSync30-72 VertRefresh 50-85 #UseModes Modes0 #monitor0usemodes Option PreferredMode 1024x768 EndSection Section Modes Identifier Modes0 #modes0modeline0 EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option ShadowFB # [bool] #Option DefaultRefresh# [bool] #Option ModeSetClearScreen# [bool] Identifier Card0 Driver vesa #card0driver VendorName Matrox Graphics, Inc. BoardName MGA G100 [Productiva] AGP BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 16 Subsection Display Depth 16 Modes 1024x768 EndSubsection EndSection end of xorg.conf This still did not fix the display. Neither did changing /etc/gdm/gdm.conf GdmXserverTimeout=10 to 25 (following advice in bug #319363). But making both changes gave a good 1024x768 display. I downloaded an iso of Karmic alpha2 and installed this. The symptoms were identical. However, now the change of GdmXserverTimeout=10 isn't needed, though the change of xorg.conf still is. - The G100 8Mb should be able to produce 1280x1024 resolution - with at least 8-bit colour. Since this is the native resolution - of the NEC display, this is what I would prefer. + The G100 2Mb should be able to produce 1280x1024 resolution + with 8-bit colour. Since this is the native resolution of the NEC + display, this is what I would prefer. I'm happy to run any tests, and do complete reinstalls of any distro. I also have various other displays available that I could try. Though due to other commitments it may take several days for me to respond. I have dumps of the /etc and /var/log trees from most of these experiments; they're rather large, so you may prefer to ask for specific files. In case you're wondering, no, the Brio isn't my regular desktop. But it's a nice compact little box to take along to LUG meets. Such machines are often discarded these days, yet are adequate for disadvantaged people wanting very basic facilities. This is likely to be their first exposure to Linux, so it's important that Ubuntu works for them without intervention. -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
Today I've temporarily loaded Windows 2000 on this HP Brio. Initially it came up in 1280x768, which looked rather naff, though readable. No updates needed, just Control Panel, Display, Settings and one of the choices was 1280x1024 8-bit colour. This worked. It worked very well indeed, it's beautiful and exceedingly enviable. Nobody who has seen this on Windows would settle for less on Ubuntu. :( How do I gather info from this Windows installation so as to create good settings to try in Ubuntu? Or, now that I know for certain that there is no hardware problem, what's the best way forward? The workaround I've given above gets it to 1024x768, but it could be so much better at the native resolution. -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
Output from lspci -vvnn attached. I assume this is the same output for all distros? ** Attachment added: lspci.txt http://launchpadlibrarian.net/28528561/lspci.txt -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
I stated previously: I downloaded an iso of Karmic alpha2 and installed this. The symptoms were identical. However, now the change of GdmXserverTimeout=10 isn't needed, though the change of xorg.conf still is. However, without the timeout change it sometimes fails. So it still seems both changes are needed, as with 9.04. -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] [NEW] Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
Public bug reported: Binary package hint: xserver-xorg-video-mga Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) HP Brio, Celeron 300MHz with 256Mb ram On board Matrox G100 8Mb NEC LCD1860NX flat screen (native resolution 1280x1024) I have also tried a CRT display and had identical symptoms, so I doubt this problem is specific for this screen. The attached photo shows the display on first booting after installing Ubuntu 9.04. It looks similar to a TV that's lost the horizontal hold, and is also displaced a little to the right and down. Although some features can be made out, the content is shown as if 3 copies are overlaid in vertical stripes. The next attached photo shows this more clearly, taken after logging in blind. Note how, in the top panel, the time is visible in 3 places. I found that Puppy and Mepix do not exhibit this problem. The next experiment was to take the xorg.conf generated by the Puppy wizard and reduce it to the following, replacing the empty /etc/X11/xorg.conf with: start Section ServerFlags Option RandR on EndSection Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section InputDevice Identifier Keyboard0 Driver kbd Option XkbRules xorg Option XkbModel pc102 Option XkbLayout us #xkeymap0 EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto #mouse0protocol Option Device /dev/mouse #Option Emulate3Buttons #Option Emulate3Timeout 50 Option ZAxisMapping 4 5 #scrollwheel EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model HorizSync30-72 VertRefresh 50-85 #UseModes Modes0 #monitor0usemodes Option PreferredMode 1024x768 EndSection Section Modes Identifier Modes0 #modes0modeline0 EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option ShadowFB # [bool] #Option DefaultRefresh# [bool] #Option ModeSetClearScreen# [bool] Identifier Card0 Driver vesa #card0driver VendorName Matrox Graphics, Inc. BoardName MGA G100 [Productiva] AGP BusID PCI:1:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 16 Subsection Display Depth 16 Modes 1024x768 EndSubsection EndSection end of xorg.conf This still did not fix the display. Neither did changing /etc/gdm/gdm.conf GdmXserverTimeout=10 to 25 (following advice in bug #319363). But making both changes gave a good 1024x768 display. I downloaded an iso of Karmic alpha2 and installed this. The symptoms were identical. However, now the change of GdmXserverTimeout=10 isn't needed, though the change of xorg.conf still is. The G100 8Mb should be able to produce 1280x1024 resolution with at least 8-bit colour. Since this is the native resolution of the NEC display, this is what I would prefer. I'm happy to run any tests, and do complete reinstalls of any distro. I also have various other displays available that I could try. Though due to other commitments it may take several days for me to respond. I have dumps of the /etc and /var/log trees from most of these experiments; they're rather large, so you may prefer to ask for specific files. In case you're wondering, no, the Brio isn't my regular desktop. But it's a nice compact little box to take along to LUG meets. Such machines are often discarded these days, yet are adequate for disadvantaged people wanting very basic facilities. This is likely to be their first exposure to Linux, so it's important that Ubuntu works for them without intervention. ** Affects: xserver-xorg-video-mga (Ubuntu) Importance: Undecided Status: New -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
** Attachment added: Photo of screen waiting for login http://launchpadlibrarian.net/28481368/screen1.jpg -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
Screen after login, to show symptom more clearly ** Attachment added: S http://launchpadlibrarian.net/28481387/screen2.jpg -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 393129] Re: Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others)
Other distros: Crunchbang 8.10 fails the same way as 9.04. Mepis 8.0.06 comes up with 1024x768 absolutely no problem. Ubuntu 7.04 comes up in 832x624, though subsequently using the gui prefs to change to 800x600 made the monitor position the display better. 1024 was not offered. Ubuntu 8.04.1 had an error starting the Gnome settings daemon (sorry, didn't capture full details, could if of interest). Otherwise it was the same as 7.04. Kubuntu 6.06 was same as 7.04 except that it was able to power down (later versions of Ubuntu seem to have lost that capability) (unrelated bug, but of minor importance compared to the display problem, so I don't plan to investigate it at this time). -- Corrupt screen, HP Brio, Matrox G100 (display: NEC LCD1860NX and others) https://bugs.launchpad.net/bugs/393129 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
