[Ubuntu-x-swat] [Bug 589485] Re: Ignores physical display size and calculates based on 96DPI
There is some progress upstream: https://bugs.freedesktop.org/show_bug.cgi?id=41115 -- 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/589485 Title: Ignores physical display size and calculates based on 96DPI To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+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 589485]
@Michal: I have also 1.17.2 and reported DPI is still 96x96, even though the actual resolution is 174x171 (see https://bugs.launchpad.net/bugs/1512606 for details). -- 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/589485 Title: Ignores physical display size and calculates based on 96DPI To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+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 1512606] Re: Display size incorreectly detected (assuming 96x96 DPI)
*** This bug is a duplicate of bug 589485 *** https://bugs.launchpad.net/bugs/589485 The dupe is Confirmed and High priority. When you assigned it to unity before, I can have justified doubts you generally read what you reply to. Never mind, this one is not relevant anymore, being a duplicate. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1512606 Title: Display size incorreectly detected (assuming 96x96 DPI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1512606/+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 589485] Re: Ignores physical display size and calculates based on 96DPI
There is 62 people who think this bug *is* important. It is a problem mainly with displays of which DPI is far from 96x96, such as more and more common HiDPI. Let's not turn it into discussion forum on Linux vs. Windows, or ideal state of Linux. We simply want Xorg to respect the DPI reported by EDID. -- 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/589485 Title: Ignores physical display size and calculates based on 96DPI To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+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 589485] Re: Ignores physical display size and calculates based on 96DPI
@Sergio, sorry but your comments are OT. Different resolutions for different screens are not supported on the toolkit level; a window can be on both screens at once and such, and it is beyond the scope of this bug. Viewing distance again has nothing to do with this bug; DPI does not depend on the viewing distance, it simply expresses physical dimensions (lengths) of one pixel; length does not depend on distance (I am a physicist, I know that one for sure). Of course for guessing comfortable font size for reading, viewing distance is important, but that is an entirely different problem, although it actually required a valid value of DPI. -- 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/589485 Title: Ignores physical display size and calculates based on 96DPI To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+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 1512606] Re: Display size incorreectly detected (assuming 96x96 DPI)
*** This bug is a duplicate of bug 589485 *** https://bugs.launchpad.net/bugs/589485 @Timo seriously, don't set "won't fix" when you manifestly have no clue what this bug is about. It would be more helpful to find the LP duplicate and set it, which I just did. ** This bug has been marked a duplicate of bug 589485 Ignores physical display size and calculates based on 96DPI -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1512606 Title: Display size incorreectly detected (assuming 96x96 DPI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1512606/+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 1512606] Re: Display size incorreectly detected (assuming 96x96 DPI)
(Putting back to intel driver; please actually read the bug report before changing to unity) ** Package changed: unity (Ubuntu) => xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1512606 Title: Display size incorreectly detected (assuming 96x96 DPI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1512606/+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 1512606] [NEW] Display size incorreectly detected (assuming 96x96 DPI)
Public bug reported: I am running 14.10 on Lenovo Yoga 12 with 280x160mm panel with 1920x1080 resolution, which translates to 174x171 DPI by trivial calculation. The panel size is correctly reported by edid: $ get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 0 No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 1 potential busses found: 4 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "" ModelName "" VendorName "LGD" # Monitor Manufactured week 0 of 2013 # EDID version 1.4 # Digital Display DisplaySize 280 160 Gamma 2.20 Option "DPMS" "false" Modeline"Mode 0" 138.46 1920 1968 2000 2106 1080 1083 1088 1095 +hsync -vsync EndSection The XServer thinks something different: $ xdpyinfo | grep -B2 resolution screen #0: dimensions:1920x1080 pixels (508x285 millimeters) resolution:96x96 dots per inch where the physical size is garbage. The driver sets DPI to 96 despite having correct data, and there seems to be no straightforward way to force a different DPI (see e.g. [1]). The internet is full of various workarounds for HiDPI displays, which include setting text-scaling- factor in dconf (gnome-only) , layout.css.devPixelsPerPt (mozilla products), scaling-factor (integer values only?), all of the toolkit- or program-specific. They have all of them some gotchas (such as terribly- looking interface, different scaling of some text, ugly icons etc). I am willing to help debugging the driver, since Ubuntu should have a way to behave well out-of-box on HiDPI configurations. If the driver reports the right DPI, I assume many of those issue would disappear. [1] https://ask.fedoraproject.org/en/question/39272/how-to-configure- screen-dpi-ppi-properly/ ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 BootLog: [[32m OK [0m] Started Modem Manager. [[32m OK [0m] Started Detect the available GPUs and deal with any system changes. Starting Light Display Manager... CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 3 08:54:40 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:503e] InstallationDate: Installed on 2015-08-31 (63 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20DLCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=f5cdca16-e2f9-4b9e-b12c-65011c787ea7 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JEET66WW (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DLCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K11826 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJEET66WW(1.15):bd06/05/2015:svnLENOVO:pn20DLCTO1WW:pvrThinkPadS1Yoga12:rvnLENOVO:rn20DLCTO1WW:rvrSDK0K11826WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DLCTO1WW dmi.product.version: ThinkPad S1 Yoga 12 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Nov 2 08:12:10 2015 xserver.configfile: default xserver.errors: Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'pad
[Ubuntu-x-swat] [Bug 1362326] [NEW] LCD panel sometimes says "No signal" and is blank, the driver thinks it is active
Public bug reported: I have 3 LCD panels attached via straight DisplayPort cables (no daisy chaining, no DVI-DP converters and so on) to the FirePro V7900, which has 4 DisplayPort sockets. One of the panels will often not come up when screens are DPMS-suspended (xset dpms force off, or by the screensaver). The panel will then say "No signal", but the card still thinks it is enabled and working (as verified in AMDCCCLE). It is sometimes possible make it work again by cycling a few times "xset dpms force off" and then pressing a key to turn screens on. It is always the same panel which has troubles, but it is port-bound (I tried exchaning the screens physically; it is the port numbered "3" in amdcccle, the other two being 1 and 2), not screen- bound. Sometimes the screen also just flickers, showing what it should only intermittently. Restarting X fixes the issue (but terminates the session) most the time. The open-source driver does not suffer from this issue at all. The fglrx driver has had this issue since as long as I remember (2 or 3 years). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fglrx-updates 2:13.350.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,resize,move,place,snap,gnomecompat,mousepoll,session,regex,wall,imgpng,grid,vpswitch,animation,expo,ezoom,workarounds,unitymtgrabhandles,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: LXDE Date: Wed Aug 27 22:42:24 2014 DistUpgraded: 2012-03-12 13:59:22,955 DEBUG icon theme changed, re-reading DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO GL [FirePro V7900] [1002:6704] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2b0c] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=3cc5f6b9-69d1-4bb6-a9d0-93d506786ed9 ro nosplash radeon.dpm=1 nosplash radeon.dpm=1 SourcePackage: fglrx-installer-updates UpgradeStatus: Upgraded to trusty on 2012-03-12 (898 days ago) dmi.bios.date: 10/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0604:bd10/03/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Aug 27 22:39:56 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: fglrx ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install trusty ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1362326 Title: LCD panel sometimes says "No signal" and is blank, the driver thinks it is active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1362326/+subscriptions __
[Ubuntu-x-swat] [Bug 1349866] Re: display blank after resume (consistent)
Confirmed as per duplicate report #1350910; as suggested there, I flashed new BIOS to F.28 without any improvement; the changelog [1] does not mention anything display-related either. (The flash BIOS utility can be run in Windows (on any computer) to create USB flash, which can be used in the Linux machine to update the BIOS, without depending on the OS.) I confirm that installing fglrx or fglrx-updates (which was previously, when trusty first came, freezing the system at boot-time IIRC) works around the issue. [1] http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=5359417&spf_p.tpst=swdMain&spf_p.prp_swdMain =wsrp- navigationalState%3Didx%253D5%257CswItem%253Dob_129812_1%257CswEnvOID%253D4059%257CitemLocale%253D%257CswLang%253D%257Cmode%253D4%257Caction%253DdriverDocument&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken -- 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/1349866 Title: display blank after resume (consistent) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1349866/+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 1350910] Re: blank screen after suspend resume
*** This bug is a duplicate of bug 1349866 *** https://bugs.launchpad.net/bugs/1349866 ** This bug has been marked a duplicate of bug 1349866 display blank after resume (consistent) -- 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/1350910 Title: blank screen after suspend resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1350910/+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 1349866] [NEW] display blank after resume (consistent)
Public bug reported: With the hardware as shown in automatically attached files (HP ProBook 455), display never recovers from resume, although the computer works fine otherwise (it can be connected to over ssh, in particular). I disabled the discrete GPU BIOS (that is the current stand) but the problem remains. Contrary to #1010683, where some people were helped by using "pm-suspend --quirk-test --quirk-s3-mode", this problem is exhibited without discrete graphics (thus ruling out problems with vgaswitcheroo). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jul 29 16:32:42 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7420G] [1002:9992] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:194e] InstallationDate: Installed on 2014-06-27 (31 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 455 G1 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=8f659b6c-ad5b-49ef-8f46-052d943c2cb5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 194E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.26:bd10/29/2013:svnHewlett-Packard:pnHPProBook455G1:pvrA2018CD200:rvnHewlett-Packard:rn194E:rvrKBCVersion91.0C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 455 G1 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jul 29 16:24:26 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze trusty ubuntu -- 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/1349866 Title: display blank after resume (consistent) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1349866/+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 1349866] Re: display blank after resume (consistent)
FWIW, this is the output of radeontool ("sudo radeontool light on" had
no effect at all):
$ sudo radeontool regs
RADEON_DAC_CNTL
RADEON_DAC_EXT_CNTL
RADEON_DAC_MACRO_CNTL
RADEON_DAC_CNTL2
RADEON_TV_DAC_CNTL c100a080
RADEON_DISP_OUTPUT_CNTL
RADEON_CONFIG_MEMSIZE
RADEON_AUX_SC_CNTL
RADEON_CRTC_EXT_CNTL
RADEON_CRTC_GEN_CNTL
RADEON_CRTC2_GEN_CNTL
RADEON_DEVICE_ID
RADEON_DISP_MISC_CNTL 0010
RADEON_GPIO_MONID
RADEON_GPIO_MONIDB
RADEON_GPIO_CRT2_DDC
RADEON_GPIO_DVI_DDC
RADEON_GPIO_VGA_DDC
RADEON_LVDS_GEN_CNTL
RADEON_LVDS_PLL_CNTL
RADEON_FP_GEN_CNTL
RADEON_FP2_GEN_CNTL
RADEON_PPLL_CNTL
RADEON_PPLL_REF_DIV
RADEON_PPLL_DIV_3
RADEON_PIXCLKS_CNTL
RADEON_P2PLL_CNTL
RADEON_P2PLL_REF_DIV
RADEON_P2PLL_DIV_0
RADEON_VCLK_ECP_CNTL
RADEON_MEM_TIMING_CNTL
RADEON_TMDS_PLL_CNTL
RADEON_TMDS_TRANSMITTER_CNTL
RADEON_CRTC_MORE_CNTL
RADEON_FP_H_SYNC_STRT_WID
RADEON_FP_V_SYNC_STRT_WID
RADEON_FP_CRTC_H_TOTAL_DISP
RADEON_FP_CRTC_V_TOTAL_DISP
RADEON_FP_HORZ_STRETCH
RADEON_FP_VERT_STRETCH
RADEON_FP_HORZ_VERT_ACTIVE
RADEON_CRTC_H_TOTAL_DISP0001f478
RADEON_CRTC_H_SYNC_STRT_WID 040f0001
RADEON_CRTC_V_TOTAL_DISP
RADEON_CRTC_V_SYNC_STRT_WID
RADEON_CRTC2_H_TOTAL_DISP 000f
RADEON_CRTC2_H_SYNC_STRT_WID3f3f
RADEON_CRTC2_V_TOTAL_DISP
RADEON_CRTC2_V_SYNC_STRT_WID0002
--
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/1349866
Title:
display blank after resume (consistent)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1349866/+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 1300260] [NEW] Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1033533 *** https://bugs.launchpad.net/bugs/1033533 Public bug reported: Bug reported automatically. The X seems to have crashed after resume, with mouse moving but keyboard not No other idea about what was happening, hopefully the automatically attached logs will help. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Mon Mar 31 16:29:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF104GLM [Quadro 3000M] [10de:0e3a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04a4] InstallationDate: Installed on 2014-03-31 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140331) MachineType: Dell Inc. Precision M6600 ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=4e9ddd97-9f89-44b3-89eb-1b6006e3c9a4 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so Title: Xorg crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 04YY4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd05/24/2011:svnDellInc.:pnPrecisionM6600:pvr01:rvnDellInc.:rn04YY4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M6600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 third-party-packages trusty ubuntu ** Information type changed from Private to Public -- 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/1300260 Title: Xorg crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1300260/+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 1043328] Re: corrupt screen both in terminal (KMS) and in X
I am not able to reproduce it with normal installation anymore (13.10), so I assume this is a "works for me" now (though the upstream bug is confirmed). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1043328 Title: corrupt screen both in terminal (KMS) and in X To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1043328/+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 959275] Re: libs unique to nvidia should be linked to /usr/lib
This bug is still relevant. "Easily switch" for sure does not mean that CUDA programs fail to start when the card is not primary. -- 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/959275 Title: libs unique to nvidia should be linked to /usr/lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/959275/+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 1071389] [NEW] nvidia-current conflicts with fglrx (both cards present)
Public bug reported: I have primary AMD FirePro GPU for graphics and a secondary headless nVidia GTX 560Ti for OpenCL. In Ubuntu 12.04, it was possible to install both nvidia-current and fglrx alongside, and after adjusting alternatves for libGL.so, Xorg would happily use the first card, and nVidia was available for OpenCL computations. Since quantal, nvidia-current is conflicting with fglrx. While I can imagine this is intentional (most users won't ever need to install both), it is nevertheless a packaging bug. Please provide at least a workaround on how to install both drivers simultaneously. Version informations attached automatically (I hope). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nvidia-current (not installed) ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,resize,move,place,snap,gnomecompat,mousepoll,session,regex,wall,imgpng,grid,vpswitch,animation,expo,ezoom,workarounds,unitymtgrabhandles,fade,scale,unityshell] CompositorRunning: None Date: Thu Oct 25 18:09:17 2012 DistUpgraded: 2012-03-12 13:59:22,955 DEBUG icon theme changed, re-reading DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI Cayman PRO GL [FirePro V7900] [1002:6704] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2b0c] NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology Device [10b0:0401] JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use) kmod:nvidia_current - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:fglrx_updates - ATI Fire GL (Proprietary, Enabled, Not in use) MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=3cc5f6b9-69d1-4bb6-a9d0-93d506786ed9 ro nosplash nosplash SourcePackage: nvidia-graphics-drivers UpgradeStatus: Upgraded to quantal on 2012-03-12 (227 days ago) dmi.bios.date: 10/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0604:bd10/03/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.modprobe.d.nvidia.current.hybrid.conf: [deleted] version.compiz: compiz 1:0.9.8.4-0ubuntu3 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal ubuntu -- 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/1071389 Title: nvidia-current conflicts with fglrx (both cards present) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1071389/+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 1043328] Re: corrupt screen both in terminal (KMS) and in X
** Summary changed: - corrupt screen in terminal (KMS) and in gnome + corrupt screen both in terminal (KMS) and in X -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1043328 Title: corrupt screen both in terminal (KMS) and in X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1043328/+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 1043328] Re: corrupt screen in terminal (KMS) and in gnome
** Attachment added: "xserver corrupt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1043328/+attachment/3282129/+files/IMG_0097.JPG -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1043328 Title: corrupt screen in terminal (KMS) and in gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1043328/+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 1043328] Re: corrupt screen in terminal (KMS) and in gnome
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1043328 Title: corrupt screen in terminal (KMS) and in gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1043328/+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 1043328] [NEW] corrupt screen in terminal (KMS) and in gnome
Public bug reported: Using fresh dev quantal installation, I am seeing corruption of the screen making the computer unusable. The terminal gets first set to correct mode, but later, vertical stripes appear (screenshot will be attached). When launching lightdm, there are inclined horizontal lines superimposed over whatever is on the desktop (screenshot attached). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu3 Architecture: amd64 Date: Wed Aug 29 09:32:41 2012 DistUpgraded: 2012-03-12 13:59:22,955 DEBUG icon theme changed, re-reading DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.18, 3.5.0-13-generic, x86_64: installed GraphicsCard: Advanced Micro Devices [AMD] nee ATI Cayman XT [Radeon HD 6970] [1002:6718] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:03bc] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=3cc5f6b9-69d1-4bb6-a9d0-93d506786ed9 ro nosplash SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to quantal on 2012-03-12 (170 days ago) dmi.bios.date: 10/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0604:bd10/03/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1043328 Title: corrupt screen in terminal (KMS) and in gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1043328/+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 1043328] Re: corrupt screen in terminal (KMS) and in gnome
** Attachment added: "console corrupt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1043328/+attachment/3282128/+files/IMG_0098.JPG -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1043328 Title: corrupt screen in terminal (KMS) and in gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1043328/+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 1043318] Re: Xorg crashed with SIGABRT in OsAbort()
** Visibility changed to: Public -- 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/1043318 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1043318/+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 993427] Re: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build [error: ‘cpu_possible_map’ undeclared (first use in this function)]
@Holm: patches much appreciated. Last hunk ("for_each_possible_cpu")
from the firegl patch was meanwhile integrated upstream (version 12-8
downloaded today from ati site) and will not apply.
Perhaps the xorg-edgers guys might be interested in putting those
patches to the fglrx-installer packages?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/993427
Title:
fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build [error:
‘cpu_possible_map’ undeclared (first use in this function)]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/993427/+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 953477] Re: "Czech (qwerty)" layout has " instead of ß in the 4th level
I installed the version from precise-proposed and confirm that this bug is fixed and can be closed. #1013881 and #221112 anre related to french layout and cannot be affected by this fix. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/953477 Title: "Czech (qwerty)" layout has " instead of ß in the 4th level To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/953477/+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 953477]
My apologies, I meant 4th level; I changed the bug title accordingly. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/953477 Title: "Czech (qwerty)" layout has " instead of ß in the 4th level To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/953477/+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 953477] Re: "Czech (qwerty)" layout has " instead of ß in the 4th level
** Summary changed: - "Czech (qwerty)" layout has " instead of ß in the 3rd level + "Czech (qwerty)" layout has " instead of ß in the 4th level -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/953477 Title: "Czech (qwerty)" layout has " instead of ß in the 4th level To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/953477/+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 953477] Re: "Czech (qwerty)" layout has " instead of ß in the 3rd level
** Bug watch added: freedesktop.org Bugzilla #48252 https://bugs.freedesktop.org/show_bug.cgi?id=48252 ** Also affects: xkeyboard-config via https://bugs.freedesktop.org/show_bug.cgi?id=48252 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/953477 Title: "Czech (qwerty)" layout has " instead of ß in the 3rd level To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/953477/+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 959275] Re: libs unique to nvidia should be linked to /usr/lib
-- 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/959275 Title: libs unique to nvidia should be linked to /usr/lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/959275/+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 959275] [NEW] libs unique to nvidia should be linked to /usr/lib
Public bug reported: nvidia-current contains libGL.so which is found (if a nvidia card is used for accelerated graphics) by setting /etc/alternatives/x86_64 -linux-gnu_gl_conf. nvidia-current however contains other libraries, which are useful also if an nvidia card is not used for OpenGL, such as libnvidia-compiler.so for OpenCL or libcuda.so for CUDA. In such a case, the whole /usr/lib /nvidia-current directory must NOT be added to ld.so.conf.d or LD_LIBRARY_PATH, since it also contains nvidia's libGL.so, which could override (come first before) libGL.so's installed by other drivers. A workaround is to link manually individual libs from /usr/lib/nvidia- current into /usr/(local/)lib so that they are found, while not exposing the libGL.so. A proper solution would be to create symlinks for libs not carrying a generic name (e.g. libcuda.so, libnvidia-compiler.so, but NOT libOpenCL.so, libGL.so, which are also provided by other packages) in directories searched by ld.so by default, e.g. /usr/lib. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-current 295.20-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: fglrx nvidia .tmp.unity.support.test.0: ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Mar 19 14:04:24 2012 DistUpgraded: Log time: 2012-03-12 11:26:17.508009 DistroCodename: precise DistroVariant: ubuntu DkmsStatus: blcr, 0.8.2: added fglrx-updates, 8.911, 3.2.0-18-generic, x86_64: installed nvidia-current, 295.20, 3.2.0-18-generic, x86_64: installed GraphicsCard: Advanced Micro Devices [AMD] nee ATI Cayman XT [Radeon HD 6970] [1002:6718] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:03bc] NVIDIA Corporation GF110 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology Device [10b0:0401] JockeyStatus: xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Disabled, Not in use) xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=3cc5f6b9-69d1-4bb6-a9d0-93d506786ed9 ro SourcePackage: nvidia-graphics-drivers UpgradeStatus: Upgraded to precise on 2012-03-12 (7 days ago) dmi.bios.date: 10/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0604:bd10/03/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.7.0+bzr3035-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug has-workaround precise single-occurrence ubuntu -- 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/959275 Title: libs unique to nvidia should be linked to /usr/lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/959275/+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 953477] [NEW] "Czech (qwerty)" layout has " instead of ß in the 3rd level
Public bug reported:
In precise, a new version of /usr/share/X11/xkb/symbols/cz appears. The
alternative "Czech (qwerty)" layout redefines key, overriding the
definition of "Czech" (the base layout). Thus, there is no ß in that
lazout, making it unusable for writing german texts. Workaround is to
change that key back to include "ssharp":
--- cz.orig 2012-03-12 23:07:40.292135311 +0100
+++ cz 2012-03-12 23:08:15.700137025 +0100
@@ -90,7 +90,7 @@
key { [ z, Z, degree, NoSymbol ] };
key { [ uring, quotedbl,semicolon,colon ] };
-key { [ section, exclam, apostrophe, quotedbl ] };
+key { [ section, exclam, apostrophe, ssharp ] };
key { [ y, Y, NoSymbol, NoSymbol ] };
key { [uacute, slash, bracketleft,braceleft ] };
key { [parenright, parenleft, bracketright, braceright ] };
Not sure if this is a good place to discuss it, but the 3rd level of the
czech layout contains all characters needed to write German texts;
omission of ß in favor of " (which is in the 2nd level of AC10 already
by standard) defeats that purpose.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xkb-data 2.5-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Mon Mar 12 23:01:55 2012
Dependencies:
DistUpgraded: Log time: 2012-03-11 11:17:23.082591
DistroCodename: precise
DistroVariant: ubuntu
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: LENOVO 3680D79
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic
root=UUID=2fb6c33e-a177-47ef-b0f4-7ed9711f2114 ro quiet splash vt.handoff=7
SourcePackage: xkeyboard-config
UpgradeStatus: Upgraded to precise on 2012-03-11 (1 days ago)
dmi.bios.date: 04/26/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET45WW (1.15 )
dmi.board.name: 3680D79
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: 6900025198
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr6QET45WW(1.15):bd04/26/2010:svnLENOVO:pn3680D79:pvrThinkPadX201:rvnLENOVO:rn3680D79:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3680D79
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5
version.ia32-libs: ia32-libs 20090808ubuntu33
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
1:2.6.99.901+git20120126-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati
1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:0.0.16+git20111201+b5534a1-1build2
** Affects: xkeyboard-config (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug has-fix has-workaround precise regression
reproducible single-occurrence ubuntu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/953477
Title:
"Czech (qwerty)" layout has " instead of ß in the 3rd level
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/953477/+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 953477] Re: "Czech (qwerty)" layout has " instead of ß in the 3rd level
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/953477 Title: "Czech (qwerty)" layout has " instead of ß in the 3rd level To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/953477/+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 474455] Re: [g33] dpkg-reconfigure xserver-xorg (with sudo) ends abruptly. Does not show the configuration screens.
What log files do you need exactly? I am at lucid and have this problem, though using xorg-edgers packages. -- [g33] dpkg-reconfigure xserver-xorg (with sudo) ends abruptly. Does not show the configuration screens. https://bugs.launchpad.net/bugs/474455 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel 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
