[Ubuntu-x-swat] [Bug 727112] Re: nvidia-current does not detect hardware capabilities correctly
[Expired for nvidia-graphics-drivers (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/727112/+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 727112] Re: nvidia-current does not detect hardware capabilities correctly
I finally found a solution/workaround (I can't believe it)!!! A thread on the nvnews forums discussed a similar problem. One comment suggested setting the option NoExtendedGpuCapabilitiesCheck in xorg.conf to disable mode validation (http://www.nvnews.net/vbulletin/showpost.php?p=2039336&postcount=11). I can now use both monitors at full/native resolution :) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/727112/+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 727112] Re: nvidia-current does not detect hardware capabilities correctly
I tested my graphics card with another external monitor (a Dell 2408WFP) which runs with a native resolution of 1920x1200. Using that monitor does not exhibit the bug and the driver/graphics card is able to run two monitors simultaneously at 1920x1200 (total resolution: 3840x1200). This shows me, that such a high resolution is definitely supported by my hardware (and by the nvidia-current driver?). But I'm still lost … why does one monitor work and another one with lower resolution does not? My current guess is different frequencies trip up the driver. Is there anybody out there with the slightest clue how to properly troubleshoot this problem? Interestingly, the Dell monitor does not show EDID data when queried with xrandr. Output of xrandr --verbose --query can be found below: Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 8192 x 8192 VGA-0 connected 1920x1200+1920+0 (0x2c8) normal (normal left inverted right x axis y axis) 519mm x 324mm Identifier: 0x278 Timestamp: 217095 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 1 CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: SignalFormat: VGA supported: VGA ConnectorType: VGA ConnectorNumber: 1 (0x0001) _ConnectorLocation: 1 (0x0001) 1920x1200 (0x2c8) 154.0MHz +HSync -VSync *current +preferred h: width 1920 start 1968 end 2000 total 2080 skew0 clock 74.0KHz v: height 1200 start 1203 end 1209 total 1235 clock 60.0Hz 1600x1200 (0x2c9) 162.0MHz +HSync +VSync h: width 1600 start 1664 end 1856 total 2160 skew0 clock 75.0KHz v: height 1200 start 1201 end 1204 total 1250 clock 60.0Hz 1280x1024 (0x2ca) 135.0MHz +HSync +VSync h: width 1280 start 1296 end 1440 total 1688 skew0 clock 80.0KHz v: height 1024 start 1025 end 1028 total 1066 clock 75.0Hz 1280x1024 (0x2cb) 108.0MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew0 clock 64.0KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.0Hz 1152x864 (0x2cc) 108.0MHz +HSync +VSync h: width 1152 start 1216 end 1344 total 1600 skew0 clock 67.5KHz v: height 864 start 865 end 868 total 900 clock 75.0Hz 1024x768 (0x2cd) 78.8MHz +HSync +VSync h: width 1024 start 1040 end 1136 total 1312 skew0 clock 60.0KHz v: height 768 start 769 end 772 total 800 clock 75.0Hz 1024x768 (0x279) 65.0MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 800x600 (0x2ce) 49.5MHz +HSync +VSync h: width 800 start 816 end 896 total 1056 skew0 clock 46.9KHz v: height 600 start 601 end 604 total 625 clock 75.0Hz 800x600 (0x27e) 40.0MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew0 clock 37.9KHz v: height 600 start 601 end 605 total 628 clock 60.3Hz 640x480 (0x2cf) 31.5MHz -HSync -VSync h: width 640 start 656 end 720 total 840 skew0 clock 37.5KHz v: height 480 start 481 end 484 total 500 clock 75.0Hz 640x480 (0x282) 25.2MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew0 clock 31.5KHz v: height 480 start 490 end 492 total 525 clock 59.9Hz TV-0 disconnected (normal left inverted right x axis y axis) Identifier: 0x286 Timestamp: 217095 Subpixel: unknown Clones: CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: SignalFormat: unknown supported: unknown ConnectorType: TV ConnectorNumber: 3 (0x0003) _ConnectorLocation: 3 (0x0003) LVDS-0 connected 1920x1200+0+0 (0x288) normal (normal left inverted right x axis y axis) 331mm x 207mm Identifier: 0x287 Timestamp: 217095 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 00004ca35532 00120103802115780a87f594574f8c27 2750540001010101010101010101 0101010101018c41805871b023406420 2
[Ubuntu-x-swat] [Bug 727112] Re: nvidia-current does not detect hardware capabilities correctly
I just performed further tests with a system booted from an USB drive. The bug happens regardless of architecture, both amd64 and i386 are affected. With the nouveau driver I managed to run both monitors with native resolution, but the external monitor showed graphic errors (see the attached screenshot). Also, the system was feeling very sluggish with two monitors. xrandr --query --verbose when using the nouveau driver outputs: Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192 LVDS-1 connected 1920x1200+0+0 (0x65) normal (normal left inverted right x axis y axis) 331mm x 207mm Identifier: 0x61 Timestamp: 27086 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 00004ca35532 00120103802115780a87f594574f8c27 2750540001010101010101010101 0101010101018c41805871b023406420 26004bcf1019000f 0046d20264fe0059 323834470031353455320a2000fe 0017272f3f5f97afff02010a20200039 dithering depth:auto supported: auto 6 bpc8 bpc dithering mode: auto supported: auto off static 2x2 dynamic 2x2 scaling mode: Full supported: None Full Center Full aspect color vibrance: 150 (0x0096)range: (0,200) vibrant hue: 90 (0x005a)range: (0,180) 1920x1200 (0x65) 167.8MHz -HSync -VSync *current +preferred h: width 1920 start 2020 end 2052 total 2264 skew0 clock 74.1KHz v: height 1200 start 1202 end 1208 total 1235 clock 60.0Hz 1920x1200 (0x66) 193.2MHz -HSync +VSync h: width 1920 start 2056 end 2256 total 2592 skew0 clock 74.6KHz v: height 1200 start 1203 end 1209 total 1245 clock 59.9Hz 1920x1080 (0x67) 173.0MHz -HSync +VSync h: width 1920 start 2048 end 2248 total 2576 skew0 clock 67.2KHz v: height 1080 start 1083 end 1088 total 1120 clock 60.0Hz 1600x1200 (0x68) 161.0MHz -HSync +VSync h: width 1600 start 1712 end 1880 total 2160 skew0 clock 74.5KHz v: height 1200 start 1203 end 1207 total 1245 clock 59.9Hz 1680x1050 (0x69) 146.2MHz -HSync +VSync h: width 1680 start 1784 end 1960 total 2240 skew0 clock 65.3KHz v: height 1050 start 1053 end 1059 total 1089 clock 60.0Hz 1400x1050 (0x6a) 121.8MHz -HSync +VSync h: width 1400 start 1488 end 1632 total 1864 skew0 clock 65.3KHz v: height 1050 start 1053 end 1057 total 1089 clock 60.0Hz 1280x1024 (0x6b) 109.0MHz -HSync +VSync h: width 1280 start 1368 end 1496 total 1712 skew0 clock 63.7KHz v: height 1024 start 1027 end 1034 total 1063 clock 59.9Hz 1280x960 (0x6c) 101.2MHz -HSync +VSync h: width 1280 start 1360 end 1488 total 1696 skew0 clock 59.7KHz v: height 960 start 963 end 967 total 996 clock 59.9Hz 1152x864 (0x6d) 81.8MHz -HSync +VSync h: width 1152 start 1216 end 1336 total 1520 skew0 clock 53.8KHz v: height 864 start 867 end 871 total 897 clock 60.0Hz 1024x768 (0x6e) 63.5MHz -HSync +VSync h: width 1024 start 1072 end 1176 total 1328 skew0 clock 47.8KHz v: height 768 start 771 end 775 total 798 clock 59.9Hz 800x600 (0x6f) 38.2MHz -HSync +VSync h: width 800 start 832 end 912 total 1024 skew0 clock 37.4KHz v: height 600 start 603 end 607 total 624 clock 59.9Hz 640x480 (0x70) 23.8MHz -HSync +VSync h: width 640 start 664 end 720 total 800 skew0 clock 29.7KHz v: height 480 start 483 end 487 total 500 clock 59.4Hz 720x400 (0x71) 22.2MHz -HSync +VSync h: width 720 start 744 end 808 total 896 skew0 clock 24.8KHz v: height 400 start 403 end 413 total 417 clock 59.6Hz 640x400 (0x72) 20.0MHz -HSync +VSync h: width 640 start 664 end 720 total 800 skew0 clock 25.0KHz v: height 400 start 403 end 409 total 417 clock 60.0Hz 640x350 (0x73) 17.5MHz -HSync +VSync h: width 640 start 664 end 720 total 800 skew0 clock 21.9KHz v: height 350 start 353 end 363 total 366 clock 59.8Hz VGA-1 connected (normal left inverted right x axis y axis) Identifier: 0x62 Timestamp: 27086 Subpixel: unknow
[Ubuntu-x-swat] [Bug 727112] Re: nvidia-current does not detect hardware capabilities correctly
I finally took the time to upgrade my Ubuntu install to the recent release 12.10 (Quantal Quetzal). This bug still occurs, and now seems worse then ever. I have skipped (i.e. not tested) the releases 11.10 and 12.04, but I assume those two releases didn't bring any improvement either. In the past, I've set my builtin monitor (laptop) to a smaller resolution (1680x1050). That way I could run the external monitor at full resolution (1920x1080 full HD) even with nvidia-current driver. Remember: both screens worked fine with full resolution with nvidia-173 (slower) as well as with nouveau (even more slow). Under Quantal, nouveau cannot handle both screens at full resolution and neither can any of the provided nvidia proprietary drivers. I tested all available options: -current, -current-updates, -experimental-304, and -experimental-310. I think nouveau managed to run both screens in "mirror"/clone mode, but not sure about the exact resolutions was using. What's worse, I cannot set my laptop monitor to the smaller resolution like I did in the past, since only "Off", "Auto", and "1920x1200" are shown in nvidia-settings as well as in 'Display' system settings (that's using randr, right?). Both monitors run, when I set my external monitor to a smaller resolution (currently 1680x1050), but that's not the native resolution and not the correct aspect ratio (16:10 vs 16:9). And if that was not bad enough, Xorg cannot even start when the external monitor is plugged in. The screen will blink several times and then dump to a black screen with a blinking white cursor. Switching to a VT, unplugging the monitor and starting X (service lightdm start) will finally bring Xorg back up. This is really annoying! (Please imagine a turned on caps lock, to get an idea of my frustration). The external monitor is connected with a VGA cable if that matters. I cannot use DVI, because my laptop only offers VGA out. Relevant details from Xorg.0.log after unsuccessfully trying to start X during boot: [97.253] (II) NVIDIA(0): NVIDIA GPU Quadro FX 360M (G86GL) at PCI:1:0:0 (GPU-0) [97.253] (--) NVIDIA(0): Memory: 524288 kBytes [97.253] (--) NVIDIA(0): VideoBIOS: 60.86.68.00.18 [97.253] (II) NVIDIA(0): Detected PCI Express Link width: 16X [97.253] (--) NVIDIA(0): Interlaced video modes are supported on this GPU [97.359] (--) NVIDIA(0): Valid display device(s) on Quadro FX 360M at PCI:1:0:0 [97.359] (--) NVIDIA(0): QMX Q24 (CRT-0) (connected) [97.359] (--) NVIDIA(0): TV-0 [97.359] (--) NVIDIA(0): Seiko/Epson (DFP-0) (connected) [97.359] (--) NVIDIA(0): DFP-1 [97.359] (--) NVIDIA(0): QMX Q24 (CRT-0): 400.0 MHz maximum pixel clock [97.359] (--) NVIDIA(0): TV-0: 400.0 MHz maximum pixel clock [97.359] (--) NVIDIA(0): TV encoder: (null) [97.359] (--) NVIDIA(0): Seiko/Epson (DFP-0): 330.0 MHz maximum pixel clock [97.359] (--) NVIDIA(0): Seiko/Epson (DFP-0): Internal Dual Link LVDS [97.359] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock [97.359] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS [97.359] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display [97.359] (**) NVIDIA(0): device QMX Q24 (CRT-0) (Using EDID frequencies has been [97.359] (**) NVIDIA(0): enabled on all display devices.) [97.371] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display [97.371] (**) NVIDIA(0): device Seiko/Epson (DFP-0) (Using EDID frequencies has [97.371] (**) NVIDIA(0): been enabled on all display devices.) [97.372] (==) NVIDIA(0): [97.372] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select" [97.372] (==) NVIDIA(0): will be used as the requested mode. [97.372] (==) NVIDIA(0): [97.373] (WW) NVIDIA(0): MetaMode "DFP-0:nvidia-auto-select,CRT-0:nvidia-auto-select" [97.373] (WW) NVIDIA(0): exceeds hardware capabilities; discarding. [97.373] (WW) NVIDIA(0): No valid modes for [97.373] (WW) NVIDIA(0): "DFP-0:nvidia-auto-select,CRT-0:nvidia-auto-select"; [97.373] (WW) NVIDIA(0): removing. [97.373] (WW) NVIDIA(0): [97.373] (WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode [97.373] (WW) NVIDIA(0): "nvidia-auto-select". [97.373] (WW) NVIDIA(0): [97.374] (WW) NVIDIA(0): MetaMode "DFP-0:nvidia-auto-select,CRT-0:nvidia-auto-select" [97.374] (WW) NVIDIA(0): exceeds hardware capabilities; discarding. [97.374] (WW) NVIDIA(0): No valid modes for [97.374] (WW) NVIDIA(0): "DFP-0:nvidia-auto-select,CRT-0:nvidia-auto-select"; [97.374] (WW) NVIDIA(0): removing. [97.374] (EE) NVIDIA(0): Unable to use default mode "nvidia-auto-select". [98.397] (EE) NVIDIA(0): Failing initialization of X screen 0 [99.071] (II) UnloadModule: "nvidia" [99.071] (II) UnloadSubModule: "wfb" [99.071] (II) UnloadSubModule: "fb" [
[Ubuntu-x-swat] [Bug 727112] Re: nvidia-current does not detect hardware capabilities correctly
Tested with Quantal and the bug still occurs. See Comment #8 (https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers/+bug/727112/comments/8) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/727112/+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 727112] Re: nvidia-current does not detect hardware capabilities correctly
We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/727112/+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 727112] Re: nvidia-current does not detect hardware capabilities correctly
Hey knittl, You filed this bug report against natty, but I see it's still open and doesn't appear to have much activity recently. So, now that oneiric is released and stable, this may be a good point for you to upgrade and re-test if this issue is still present there. If it's solved in the new release and you think it's worth backporting the fix, please indicate that. Or if having the fix in the new release is good enough, feel free to close out the bug (or let us know and we'll close it.) If it's not solved, leave the bug report open. I can't promise we'll get to it (we get way more bugs filed than we can usually get to), but your testing and feedback can help out if and when we do. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/727112/+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 727112] Re: nvidia-current does not detect hardware capabilities correctly
new "symptom": last week i had a projector plugged in while booting into ubuntu. when i went home i only put my computer to sleep. when using my monitor at home i was then able to run both monitors in full resolution (nvidia-settings was still thinking the projector was plugged in, it would not recognize my monitor) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly ___ 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 727112] Re: nvidia-current does not detect hardware capabilities correctly
** Changed in: nvidia-graphics-drivers (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly ___ 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 727112] Re: nvidia-current does not detect hardware capabilities correctly
** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly ___ 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 727112] Re: nvidia-current does not detect hardware capabilities correctly
hi bryce, no more luck without an xorg.conf, why would it? there's not much in my config, except the driver. for classic desktop, i am running it already – desktop effects take too much time and resources. i can try if desktop with effects works with nvidia-173 driver, but i'm pretty sure it will (was nvidia-173 updated for the new xserver already?) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly ___ 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 727112] Re: nvidia-current does not detect hardware capabilities correctly
Can you try removing your /etc/X11/xorg.conf and see if the automatic configuration works better? Also, test out running Classic Desktop (No effects). If that works, then I wonder if its just a max texture size limitation of the hardware. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly ___ 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 727112] Re: nvidia-current does not detect hardware capabilities correctly
I'm subscribing Nvidia. @Daniel Dadap: any ideas on the issue? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly ___ 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
