[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
[Bug 1096459] [NEW] Unity reports software rendering although it "is fully supported" by hardware
Public bug reported: When running unity --replace it reports that it enables software rendering because it is not supported by my hardware (Unity is not supported by your hardware. Enabling software rendering instead (slow).), but in the next line it displays "Unity is fully supported by your hardware." Running unity_support_test also shows full support, which leaves me quite confused. Graphics Card is an NVidia Quadro FX 360M (G86M) and the driver is nvidia-experimental-310. Unity runs somewhat slow, but I cannot tell whether it actually uses software or hardware rendering (maybe the perceived slowness is caused by something else). Below is the full output of the command: $ unity --replace compiz (core) - Info: Loading plugin: core compiz (core) - Info: Starting plugin: core compiz (core) - Info: Loading plugin: ccp compiz (core) - Info: Starting plugin: ccp compizconfig - Info: Backend : gsettings compizconfig - Info: Integration : true compizconfig - Info: Profile : unity compiz (core) - Info: Loading plugin: composite compiz (core) - Info: Starting plugin: composite compiz (core) - Info: Loading plugin: opengl compiz (core) - Info: Unity is not supported by your hardware. Enabling software rendering instead (slow). compiz (core) - Info: Unity is fully supported by your hardware. compiz (core) - Info: Starting plugin: opengl compiz (core) - Info: Loading plugin: decor compiz (core) - Info: Starting plugin: decor compiz (core) - Info: Loading plugin: resize compiz (core) - Info: Starting plugin: resize compiz (core) - Info: Loading plugin: vpswitch compiz (core) - Info: Starting plugin: vpswitch compiz (core) - Info: Loading plugin: regex compiz (core) - Info: Starting plugin: regex compiz (core) - Info: Loading plugin: snap compiz (core) - Info: Starting plugin: snap compiz (core) - Info: Loading plugin: mousepoll compiz (core) - Info: Starting plugin: mousepoll compiz (core) - Info: Loading plugin: compiztoolbox compiz (core) - Info: Starting plugin: compiztoolbox compiz (core) - Info: Loading plugin: move compiz (core) - Info: Starting plugin: move compiz (core) - Info: Loading plugin: imgpng compiz (core) - Info: Starting plugin: imgpng compiz (core) - Info: Loading plugin: place compiz (core) - Info: Starting plugin: place compiz (core) - Info: Loading plugin: grid compiz (core) - Info: Starting plugin: grid compiz (core) - Info: Loading plugin: unitymtgrabhandles compiz (core) - Info: Starting plugin: unitymtgrabhandles compiz (core) - Info: Loading plugin: animation compiz (core) - Info: Starting plugin: animation compiz (core) - Info: Loading plugin: wall compiz (core) - Info: Starting plugin: wall compiz (core) - Info: Loading plugin: expo compiz (core) - Info: Starting plugin: expo compiz (expo) - Warn: failed to bind image to texture compiz (core) - Info: Loading plugin: fade compiz (core) - Info: Starting plugin: fade compiz (core) - Info: Loading plugin: workarounds compiz (core) - Info: Starting plugin: workarounds compiz (core) - Info: Loading plugin: session compiz (core) - Info: Starting plugin: session compiz (core) - Info: Loading plugin: scale compiz (core) - Info: Starting plugin: scale compiz (core) - Info: Loading plugin: ezoom compiz (core) - Info: Starting plugin: ezoom compiz (core) - Info: Loading plugin: unityshell compiz (core) - Info: Starting plugin: unityshell ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat Jan 5 22:34:35 2013 MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2012-12-15 (21 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096459 Title: Unity reports software rendering although it "is fully supported" by hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1096459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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" [
[Bug 753118] Re: computertemp crashed with GError in save_prefs_thermalzone(): Failed to contact configuration server
*** This bug is a duplicate of bug 635295 *** https://bugs.launchpad.net/bugs/635295 the original bug is marked as private and cannot be viewed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/753118 Title: computertemp crashed with GError in save_prefs_thermalzone(): Failed to contact configuration server -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632376] Re: package nvidia-current 256.53-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build
** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632376 Title: package nvidia-current 256.53-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318791] Re: computertemp crashes when no sensors are configured
computertemp still crashes for me on natty, are there any updates on this bug? i never had this bug before (and even lm_sensors is installed) is there anything i can do to help solve the problem? apport always redirects me to this bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/318791 Title: computertemp crashes when no sensors are configured -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727117] Re: jockey-gtk shows nvidia-current as disabled although it's installed and active
attaching a logfile taken directly after trying to install the driver and closing jockey (logfile was emptied before starting jockey) ** Attachment added: "jockey.log" https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/727117/+attachment/1878728/+files/jockey.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727117 Title: jockey-gtk shows nvidia-current as disabled although it's installed and active -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727117] Re: jockey-gtk shows nvidia-current as disabled although it's installed and active
jockey-text shows similar symptoms: $ jockey-text -l xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Disabled, In use) $ lsmod|grep nv nvidia 9732498 34 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727117 Title: jockey-gtk shows nvidia-current as disabled although it's installed and active -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727117] Re: jockey-gtk shows nvidia-current as disabled although it's installed and active
** Attachment added: "xorg config" https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/727117/+attachment/1878502/+files/xorg.conf ** Description changed: jockey-gtk shows nvidia-current as disabled although it's installed and active. i've attached a screenshot (jockey-gtk and nvidia-settings side by side) to show the problem. this happens on a 32 bit system of ubuntu natty (but happened on maverick too) + + http://paste2.org/p/1275564 shows output of update-alternatives + + --- ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: jockey-gtk 0.9.1-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic-pae 2.6.38-rc6 Uname: Linux 2.6.38-5-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue Mar 1 12:44:47 2011 MachineType: Dell Inc. Precision M4300 PackageArchitecture: all PccardctlIdent: - Socket 0: -no product info available + Socket 0: + no product info available PccardctlStatus: - Socket 0: -no card + Socket 0: + no card ProcEnviron: - LANGUAGE=en_US:en - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US:en + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-5-generic-pae root=UUID=f957135d-b762-45ac-9e0d-6979595882aa ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: Upgraded to natty on 2011-01-13 (46 days ago) dmi.bios.date: 05/23/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0UY141 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/23/2008:svnDellInc.:pnPrecisionM4300:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M4300 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727117 Title: jockey-gtk shows nvidia-current as disabled although it's installed and active -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727117] Re: jockey-gtk shows nvidia-current as disabled although it's installed and active
** Attachment added: "jockey-gtk and nvidia-settings side by side" https://bugs.launchpad.net/bugs/727117/+attachment/1878488/+files/jockey-nvidia-current.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727117 Title: jockey-gtk shows nvidia-current as disabled although it's installed and active -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727117] [NEW] jockey-gtk shows nvidia-current as disabled although it's installed and active
Public bug reported: jockey-gtk shows nvidia-current as disabled although it's installed and active. i've attached a screenshot (jockey-gtk and nvidia-settings side by side) to show the problem. this happens on a 32 bit system of ubuntu natty (but happened on maverick too) http://paste2.org/p/1275564 shows output of update-alternatives --- ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: jockey-gtk 0.9.1-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic-pae 2.6.38-rc6 Uname: Linux 2.6.38-5-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue Mar 1 12:44:47 2011 MachineType: Dell Inc. Precision M4300 PackageArchitecture: all PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-5-generic-pae root=UUID=f957135d-b762-45ac-9e0d-6979595882aa ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: Upgraded to natty on 2011-01-13 (46 days ago) dmi.bios.date: 05/23/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0UY141 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/23/2008:svnDellInc.:pnPrecisionM4300:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M4300 dmi.sys.vendor: Dell Inc. ** Affects: jockey (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727117 Title: jockey-gtk shows nvidia-current as disabled although it's installed and active -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727112] Re: nvdia-current does not detect hardware capabilities
** Attachment added: "output of nvidia-bug-report.sh" https://bugs.launchpad.net/bugs/727112/+attachment/1878462/+files/nvidia-bug-report.log.gz ** Summary changed: - nvdia-current does not detect hardware capabilities + nvidia-current does not detect hardware capabilities correctly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727112] [NEW] nvidia-current does not detect hardware capabilities correctly
Public bug reported: nvidia-current is unable to use two monitors in full resolution (wuxga + full hd), one will always stay blank. looking into xorg.log, i can see something like: [ 89444.991] (WW) NVIDIA(0): Due to hardware capability constraints, disabling display [ 89444.991] (WW) NVIDIA(0): device Seiko/Epson (DFP-0) in MetaMode [ 89444.991] (WW) NVIDIA(0): "CRT-0:nvidia-auto-select@1920x1080+1920+0,DFP-0:1920x1200@1920x1200+0+0". the same configuration works with nvidia-173, so nvidia-current might not be detecting hardware capabalities correctly. nvidia-173 feels a bit slower than nvidia-current, so i'd like to use nvidia-current. my graphics card is `01:00.0 VGA compatible controller: nVidia Corporation G86M [Quadro FX 360M] (rev a1)` i'll be glad to give further information, this has bugged me for quite a while. i'm currently running natty, but i've seen this bug since nvidia- current was introduced ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nvidia-current 270.29-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic-pae 2.6.38-rc6 Uname: Linux 2.6.38-5-generic-pae i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 270.29 Wed Feb 23 16:16:53 PST 2011 GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-3ubuntu3) Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell] CompositorRunning: None Date: Tue Mar 1 12:34:01 2011 DistUpgraded: Yes, recently upgraded Log time: 2010-12-25 19:00:20.784814 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: virtualbox-ose, 4.0.4, 2.6.38-5-generic, i686: installed virtualbox-ose, 4.0.4, 2.6.38-5-generic-pae, i686: installed nvidia-current, 270.29, 2.6.38-5-generic-pae, i686: installed GraphicsCard: nVidia Corporation G86M [Quadro FX 360M] [10de:042d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01ff] MachineType: Dell Inc. Precision M4300 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-5-generic-pae root=UUID=f957135d-b762-45ac-9e0d-6979595882aa ro quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: nvidia-graphics-drivers UpgradeStatus: Upgraded to natty on 2011-01-13 (46 days ago) dmi.bios.date: 05/23/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0UY141 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/23/2008:svnDellInc.:pnPrecisionM4300:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M4300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.4-0ubuntu2 version.libdrm2: libdrm2 2.4.23-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1~git20110215.cc1636b6-0ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu8 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu11 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu5 ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727112 Title: nvidia-current does not detect hardware capabilities correctly -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632376] Re: package nvidia-current 256.53-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build
i think this bug does still affect me on natty, but i cannot test it right now since there are no compatible nvidia drivers since the x-server ABI bump. for the time being i avoided the issue using nvidia-173 installed via apt-get – but i would appreciate it if jockey was able to install nvidia-current. nvidia-current can be installed from the command line, but will only work for the builtin screen. if i attach an external monitor one of the two will always be black when using twinview … -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632376 Title: package nvidia-current 256.53-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492782] Re: Mouse cursor disappears after restarting screen (xrandr / resume)
this has been happening to me for about a week now running fully upgraded natty with nouveau driver. graphic card is 01:00.0 VGA compatible controller [0300]: nVidia Corporation G86M [Quadro FX 360M] [10de:042d] (rev a1) after some time the mouse cursor will randomly disappear on my external monitor, with no errors in Xorg.0.log (but errors in kern.log) other times the cursor is still visible, but if the cursor changes shape (textcursor, loading, links) it will be verry sluggy for a moment (pulseaudio also hangs while this) and trash kern.log with "no space while unhiding cursor" messages. when the symptom is a disappearing cursor only the "EvoCh" line is written to the log file, i.e. Feb 7 10:28:05 kbook kernel: [49943.295050] [drm] nouveau :01:00.0: EvoCh 0 Mthd 0x Data 0x0400 (0x0002 0x01) Feb 7 10:33:01 kbook kernel: [50239.740629] [drm] nouveau :01:00.0: no space while unhiding cursor Feb 7 10:33:01 kbook kernel: [50239.871880] [drm] nouveau :01:00.0: no space while unhiding cursor ... starting the monitor resolution tool will completely freeze X, logging out will not restart X, killing X with ctrl-alt-backspace will hang the screen. the only thing to bring the mouse cursor back to a usable state is to restart the machine (either using shut down from the gnome panel, or after X has hung up using sysrq-reisub) i'll be glad to provide further log files or system information. this bug is really annoying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/492782 Title: Mouse cursor disappears after restarting screen (xrandr / resume) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 716147] Re: cursor disappears on one screen of dual monitor setup
*** This bug is a duplicate of bug 492782 *** https://bugs.launchpad.net/bugs/492782 ** This bug has been marked a duplicate of bug 492782 Mouse cursor disappears after restarting screen (xrandr / resume) * You can subscribe to bug 492782 by following this link: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/492782/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716147 Title: cursor disappears on one screen of dual monitor setup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711286] Re: jockey-gtk crashed with AttributeError in __getattr__(): 'gi.repository.Gtk' object has no attribute 'ICON_LOOKUP_USE_BUILTIN'
*** This bug is a duplicate of bug 706193 *** https://bugs.launchpad.net/bugs/706193 the 'original' bug is not viewable by me (permission problems) is it set to private? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711286 Title: jockey-gtk crashed with AttributeError in __getattr__(): 'gi.repository.Gtk' object has no attribute 'ICON_LOOKUP_USE_BUILTIN' -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711336] Re: package xserver-xorg-core 2:1.9.0.902-1ubuntu4 failed to install/upgrade: installing xserver-xorg-core would break existing software
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711336 Title: package xserver-xorg-core 2:1.9.0.902-1ubuntu4 failed to install/upgrade: installing xserver-xorg-core would break existing software -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 711336] [NEW] package xserver-xorg-core 2:1.9.0.902-1ubuntu4 failed to install/upgrade: installing xserver-xorg-core would break existing software
Public bug reported: trying to purge and reinstall all video drivers for my card (nvidia G86M Quadro FX 360M) because it's simply impossible to tell jockey (or apt- get for that matter) to install the correct driver. when trying to readd drivers (xserver-xorg-video-all) synaptics bailed out ProblemType: Package DistroRelease: Ubuntu 11.04 Package: xserver-xorg-core 2:1.9.0.902-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-1.28-generic-pae 2.6.38-rc2 Uname: Linux 2.6.38-1-generic-pae i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 260.19.29 Wed Dec 8 12:09:09 PST 2010 GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-2ubuntu1) .proc.driver.nvidia.version_: NVRM version: NVIDIA UNIX x86 Kernel Module 260.19.29 Wed Dec 8 12:09:09 PST 2010 GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-2ubuntu1) Architecture: i386 Date: Tue Feb 1 17:32:55 2011 DistUpgraded: Yes, recently upgraded Log time: 2010-12-25 19:00:20.784814 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: virtualbox-ose, 4.0.2, 2.6.38-1-generic-pae, i686: installed ErrorMessage: installing xserver-xorg-core would break existing software GraphicsCard: Subsystem: Dell Device [1028:01ff] MachineType: Dell Inc. Precision M4300 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic-pae root=UUID=f957135d-b762-45ac-9e0d-6979595882aa ro quiet splash vt.handoff=7 ProcKernelCmdLine_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic-pae root=UUID=f957135d-b762-45ac-9e0d-6979595882aa ro quiet splash vt.handoff=7 SourcePackage: xorg-server Title: package xserver-xorg-core 2:1.9.0.902-1ubuntu4 failed to install/upgrade: installing xserver-xorg-core would break existing software dmi.bios.date: 05/23/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0UY141 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/23/2008:svnDellInc.:pnPrecisionM4300:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M4300 dmi.sys.vendor: Dell Inc. version.libdrm2: libdrm2 2.4.23-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.5+6ubuntu8 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.13.2+git20110124.fadee040-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 natty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711336 Title: package xserver-xorg-core 2:1.9.0.902-1ubuntu4 failed to install/upgrade: installing xserver-xorg-core would break existing software -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 671016] Re: EOL needs to be handled more elegantly
** Description changed: Binary package hint: update-manager Users can come into possession of a computer on which is installed a version of Ubuntu that is no longer supported. In cases where the next version of Ubuntu is supported, the user may upgrade to a supported version. However, in the case where the currently installed and the next version is also no longer supported, the user cannot update. In either case, we need to handle these cases more elegantly. - 1. The user should be apprised of the fact that there OS is not supported and will not receive updates. - 2. The user should be told their options in clear language about how to resolve the issue. For instance, attempting an upgrade, reinstalling a fresh Ubuntu, or contacting their manufacturer for instructions. + 1. Users should be apprised of the fact that their OS is not supported anymore and will not receive updates. + 2. Users should be told their options in clear language about how to resolve the issue. For instance, attempting an upgrade, reinstalling a fresh Ubuntu, or contacting their manufacturer for instructions. 3. The update-manage should know about old.* archives so that the user can attempt an upgrade if desired. [fixed] ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: update-manager 1:0.142.20 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Thu Nov 4 09:20:38 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) PackageArchitecture: all ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: update-manager -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/671016 Title: EOL needs to be handled more elegantly -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318791] Re: computertemp crashes when no sensors are configured
** Also affects: computertemp Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/318791 Title: computertemp crashes when no sensors are configured -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 707561] Re: package samba 2:3.5.6~dfsg-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: samba (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/707561 Title: package samba 2:3.5.6~dfsg-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 707581] Re: package samba 2:3.5.6~dfsg-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 707561 *** https://bugs.launchpad.net/bugs/707561 ** This bug has been marked a duplicate of bug 707561 package samba 2:3.5.6~dfsg-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 * You can subscribe to bug 707561 by following this link: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/707561/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/707581 Title: package samba 2:3.5.6~dfsg-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690647] Re: [natty] 'Stop tracking' button no longer works
upstream bug can be found at: https://bugzilla.gnome.org/show_bug.cgi?id=633103 the git commit to fix the issue is: http://git.gnome.org/browse/hamster- applet/commit/?id=f401d649318e0e01ccefeb99a398a6f32fd820a8 ** Bug watch added: GNOME Bug Tracker #633103 https://bugzilla.gnome.org/show_bug.cgi?id=633103 ** Also affects: hamster-applet via https://bugzilla.gnome.org/show_bug.cgi?id=633103 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690647 Title: [natty] 'Stop tracking' button no longer works -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632376] Re: package nvidia-current 256.53-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build
** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553551/+files/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553552/+files/CurrentDmesg.txt ** Attachment added: "DKMSBuildLog.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553553/+files/DKMSBuildLog.txt ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553554/+files/Dependencies.txt ** Attachment added: "DkmsStatus.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553555/+files/DkmsStatus.txt ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553556/+files/Lspci.txt ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553557/+files/Lsusb.txt ** Attachment added: "PciDisplay.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553558/+files/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553559/+files/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553560/+files/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553561/+files/ProcModules.txt ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553562/+files/RelatedPackageVersions.txt ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553563/+files/UdevDb.txt ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553564/+files/UdevLog.txt ** Attachment added: "XorgLog.gz" https://bugs.launchpad.net/bugs/632376/+attachment/1553565/+files/XorgLog.gz ** Attachment added: "XorgLogOld.gz" https://bugs.launchpad.net/bugs/632376/+attachment/1553566/+files/XorgLogOld.gz ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553567/+files/Xrandr.txt ** Attachment added: "glxinfo.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553568/+files/glxinfo.txt ** Attachment added: "make.log.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553569/+files/make.log.txt ** Attachment added: "peripherals.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553570/+files/peripherals.txt ** Attachment added: "setxkbmap.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553571/+files/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553572/+files/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" https://bugs.launchpad.net/bugs/632376/+attachment/1553573/+files/xkbcomp.txt -- package nvidia-current 256.53-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build https://bugs.launchpad.net/bugs/632376 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632376] [NEW] package nvidia-current 256.53-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build
Public bug reported: trying to install the proprietary nvidia driver via jockey fails shortly before finishing ProblemType: Package DistroRelease: Ubuntu 10.10 Package: nvidia-current 256.53-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3 Uname: Linux 2.6.35-19-generic i686 Architecture: i386 DRM.card0.DVI.D.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1920x1200 1920x1200 1920x1080 1600x1200 1680x1050 1400x1050 1280x1024 1280x960 1152x864 1024x768 800x600 640x480 720x400 640x400 640x350 edid-base64: AP///wBMo1UyAAASAQOAIRV4Cof1lFdPjCcnUFQBAQEBAQEBAQEBAQEBAQEBjEGAWHGwI0BkICYAS88QAAAZDwAAAEbSAmQA/gBZMjg0RwAxNTRVMgog/gAXJy8/X5ev/wIBCiAgADk= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Tue Sep 7 14:29:17 2010 ErrorMessage: nvidia-current kernel module failed to build MachineType: Dell Inc. Precision M4300 PackageVersion: 256.53-0ubuntu2 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=f957135d-b762-45ac-9e0d-6979595882aa ro quiet splash SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 256.53-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build dmi.bios.date: 05/23/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0UY141 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/23/2008:svnDellInc.:pnPrecisionM4300:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M4300 dmi.sys.vendor: Dell Inc. system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.35-19-generic ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 maverick -- package nvidia-current 256.53-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build https://bugs.launchpad.net/bugs/632376 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 587534] Re: rhythmbox segfault on launch [maverick]
seems to only occur on 32 bit systems -- rhythmbox segfault on launch [maverick] https://bugs.launchpad.net/bugs/587534 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506357] Re: package python-pyatspi 1.29.5-0ubuntu1 failed to install/upgrade: invalid syntax error for python2.4
should read:
try:
try:
import gconf
gconfClient = gconf.client_get_default()
useDbus = gconfClient.get_bool("/desktop/gnome/interface/at-spi-dbus")
except:
useDbus = False
finally:
del gconfClient
del gconf
this worked for me, although i don't understand how this occured,
default python version on my system is 2.6 -- which already allows try …
except … finally
--
package python-pyatspi 1.29.5-0ubuntu1 failed to install/upgrade: invalid
syntax error for python2.4
https://bugs.launchpad.net/bugs/506357
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 406036] Re: inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL)
i can also reproduce the bug and can confirm the workaround (unsetting GTK_IM_MODULE) as well i need XIM input method so i can use the compose functionality of my keyboard layout (Neo-Layout) -- inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL) https://bugs.launchpad.net/bugs/406036 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 411264] Re: tty corruption on press Ctrl+Alt+F1
there are a lot of duplicates or similar bug reports, so i don’t know which one was the one, i was encountering. also i had problems with my graphics card and installed and uninstalled a lot of packages. nevertheless: my ttys were broken with weird random noisy color, but were still responsive (entering username and password, then emitting sounds, or touching files)—both with proprietary nvidia driveres and open source nv drivers. i don't know why, but sometime in the process i typed grub --version in a terminal, which printed grub 0.97something to the terminal. i was confused, since i thought karmic upgraded to grub2 and i already executed the necessary commands to upgrade my old grub installation to the new one. all files in /boot/grub were there with old grub, so i thought it was grub2. but those files were never be used. after installing grub2 (sudo apt-get install grub-pc) all my ttys work again now. with nv as well as with nvidia. hope this hopes people with similar bugs -- tty corruption on press Ctrl+Alt+F1 https://bugs.launchpad.net/bugs/411264 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
