[Ubuntu-x-swat] [Bug 1396011] [NEW] (i915) Black screen resuming from suspend
Public bug reported: Similar to Bug #1336227 and Bug #966744, intermittedly when resuming from suspend I get a black screen with only a visible mouse pointer. Sometimes I can move the mouse pointer. I have the feeling it occurs more often when disconnecting an external monitor while in suspend. I can always switch to a VT, and sometimes I'm able to get everything going again by killing compiz and restarting unity: killall -9 compiz unity --replace But most oft, only way is to restart the lightdm service... All the best, Niklas ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDesktop: Unity Date: Tue Nov 25 08:55:29 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.20, 3.16.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c0ef] InstallationDate: Installed on 2014-10-29 (26 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 940X3G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=1eda5db0-0197-4609-a37f-4c5361a1d619 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02ACJ.101.130926.dg dmi.board.asset.tag: No Asset Tag dmi.board.name: NP940X3G-K03SE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02ACJ.101.130926.dg:bd09/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn940X3G:pvrP02ACJ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP940X3G-K03SE:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 940X3G dmi.product.version: P02ACJ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Nov 25 08:46:34 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41082 vendor DEL xserver.version: 2:1.16.0-1ubuntu1 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic -- 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/1396011 Title: (i915) Black screen resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1396011/+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 1379180] Re: AMD Radeon HD 8670A/8670M/8690M [1002:6660] No HDMI audio with open-source / proprietary driver
*** This bug is a duplicate of bug 1383997 *** https://bugs.launchpad.net/bugs/1383997 ** This bug has been marked a duplicate of bug 1383997 [Dell Vostro 5470] No HDMI audio with 14.04 -- 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/1379180 Title: AMD Radeon HD 8670A/8670M/8690M [1002:6660] No HDMI audio with open- source / proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1379180/+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 1396094] [NEW] -
Public bug reported: - ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-lowlatency 3.16.7 Uname: Linux 3.16.0-25-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Nov 25 12:25:05 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: i915-3.16-3.13, 1, 3.13.0-40-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-40-generic, x86_64: installed virtualbox, 4.3.10, 3.16.0-25-lowlatency, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:17df] InstallationDate: Installed on 2014-09-09 (77 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook 2570p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-lowlatency root=UUID=2db0b3c4-555a-4f39-8ebc-5de4822fe97f ro acpi_backlight=vendor acpi_osi=Linux SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ISB Ver. F.50 dmi.board.name: 17DF dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 61.25 dmi.chassis.asset.tag: CNU3089NVX dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ISBVer.F.50:bd08/07/2014:svnHewlett-Packard:pnHPEliteBook2570p:pvrA1029D1102:rvnHewlett-Packard:rn17DF:rvrKBCVersion61.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2570p dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.2 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.911-0intel1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Nov 23 17:45:33 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8300 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages 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/1396094 Title: - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396094/+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 927168] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpText
Launchpad has imported 2 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=55343. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-09-26T05:29:41+00:00 Timo Aaltonen wrote: downstream bug from ubuntu: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/927168 started happening for more people when the default fallback session started using llvmpipe. Applies to 8.0.x and 9.0. It's worked around for now (Check that pixmaps which aren't managed by us actually exist before binding) but a proper fix should be added to mesa. some stacktraces: https://launchpadlibrarian.net/115551011/Stacktrace.txt https://launchpadlibrarian.net/115545323/Stacktrace.txt https://launchpadlibrarian.net/115549285/Stacktrace.txt https://launchpadlibrarian.net/115587684/Stacktrace.txt https://launchpadlibrarian.net/115563588/Stacktrace.txt https://launchpadlibrarian.net/115553644/Stacktrace.txt Reply at: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/927168/comments/29 On 2014-11-24T20:56:50+00:00 Jfonseca-e wrote: IIUC the compiz-core patch https://i116412274.restricted.launchpadlibrarian.net/116412274/2c4b2354 -00dc-11e2-a4a9-002481e91f22.txt?token=60HdnFNMGFc5zJXJwfwH9pN2wg6pmXxn the fix consisted of not calling glXBindTexImageEXT when XGetGeometry (dpy, pixmap, ...) returns false. https://www.opengl.org/registry/specs/EXT/texture_from_pixmap.txt does say that Currently, only pixmaps can be bound to textures. If draw is not a valid GLXPixmap, then a GLXBadPixmap error is generated. so indeed this should be handled better. This technically is a bug in st/dri though. Reply at: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/927168/comments/34 ** Changed in: mesa Status: Unknown = Confirmed ** Changed in: mesa Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/927168 Title: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/927168/+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 1328026] Re: Screen corruption on rotate (Unity, radeon)
That sounds like good news. Once you are sure the problem is fixed in 14.10, you can set the status of this bug to Fix Released. -- 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/1328026 Title: Screen corruption on rotate (Unity, radeon) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1328026/+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 1396232] [NEW] Xorg freeze
Public bug reported: gnome-do and Xorg/unity/desktop seem to be incompatible on a fresh install of either utopic or vivid. This is either tied to 1080p (1920x1080) or a fresh install of either version. Details as I know them are provided here. I have a brand new machine which is running 1080p to an HDMI monitor. I installed Ubuntu 15.04 fresh from a usb install (usb-creator run from an existing, working vivid machine). As with all new machines, I go through my new install check list: https://wiki.ubuntu.com/BarryWarsaw These are slightly out of order, and this problem crops up after doing all the apt-get installs, apt-get update, and apt-get dist-upgrade. After all that, a reboot, and a re-login, the desktop is corrupt and unusable. I see the top menu bar extend from the right but only about 1/8th of the way to the left (the rest is desktop background), the dash only displayes on the lower left about 1/3 of the way up (again, desktop background the rest of the way), and neither the mouse nor the keyboard work at all. I must ssh in to reboot (or hard reboot of course). The system is still operational as the ssh shell works perfectly. The desktop is simply corrupt visually and unresponsive. The login screen after boot seems completely functional though. Mouse works fine as does the keyboard (or I wouldn't be able to log in!). Some additional data points make this even more interesting. On a different disk on this very same machine, I installed OS X 10.10.1, and VMware Fusion 7.0.1. Inside Fusion, I installed Vivid from daily live build iso of yesterday (11/24/14), and went through the same steps. I get exactly the same corruption and desktop freeze. I took a snapshot of the disk and then installed Utopic fresh from an iso downloaded via the normal www.ubuntu.com download site. In Utopic, I took a disk snapshot, and then I again went through the same apt-get steps and the desktop is again corrupt and frozen. This leads me to believe that one of the packages in my new machine buildout are to blame. I should also mention that in Vivid, I installed vmware-tools but in Utopic I did not. No difference (except that with vmware-tools I can set the display to 1920x1080, i.e. the full physical screen, while without vmware-tools, I cannot get full screen resolution from System Settings - Displays). Oh, I tried booting each of the previous kernels, with no effect. So now, I went back to the Utopic snapshot I took right after installing from iso and confirmed that everything works perfectly fine. Desktop is not corrupt and keyboard/mouse are responsive. Through the process of elimination, I would take a disk snapshot, install a few packages, test login, rinse and repeat. I was able to narrow it down to gnome-do and its dependencies. Specifically, after installing gnome-do and its dependencies, the desktop was broken as described above. Reverting to the disk snapshot pre-install of gnome-do, confirms that everything works fine. So now, I installed gnome-do and its dependencies, witnessed the corruption and freeze, and then ssh'd in and then did `apt-get purge gnome-do apt- get autoremove`. gnome-do and its dependencies were removed, I rebooted, logged in and everything was fine again. I went back to the Vivid disk snapshot, purged gnome-do and autoremoved, and *its* desktop was fixed. Clearly the problem is related to gnome-do in both Utopic and Vivid and/or one of its dependencies. After submitting this bug I will reboot back into Vivid running natively on the hardware, ssh in, purge gnome-do and its dependencies and see what happens. I suspect the desktop will be fixed again. As if this is not interesting enough, I have two other desktops currently running Vivid, and both have gnome-do installed, *and* both work perfectly well! The big difference here is that both of them have been dist-upgraded to Vivid through existing Utopic releases, and before that, even Trusty. IOW, both machines were running at least Trusty, upgraded to Utopic, upgraded to Vivid, and work perfectly fine. No desktop corruption, no freezes. (One machine has been upgraded successively since at least Precise; both machines are now on the 'devel' channel.) I'm happy to continue helping with this in any way necessary. Let me know if you need any other information or have anything you want me to test. I will let you bugtask this to unity and/or gnome-do or some other dependency, as you see fit. Thanks! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu10 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 CurrentDesktop: Unity Date: Tue Nov 25 10:59:11 2014
[Ubuntu-x-swat] [Bug 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver
Any update here? -- 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/1104230 Title: DisplayPort 1.2 MST support is missing in the Intel driver To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1104230/+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 1328026] Re: Screen corruption on rotate (Unity, radeon)
Corruption is gone, but rotation seems to disable vsync even when switching back to normal. Is this a separate bug? If so, I'll close this one as fixed. -- 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/1328026 Title: Screen corruption on rotate (Unity, radeon) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1328026/+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 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.
The error occurs because nv10 (the driver used for this card) declares VBO support (extension GL_ARB_vertex_buffer_object) but only supports VBOs of int8, int16 and float (not double) types, and the application is trying to draw data of type double. Given that the double type is part of the OpenGL spec, that would appear to be a bug in mesa, not the application. The easy fix would be don't declare VBO support on those cards, but that would slow down many other applications, and break any that require this feature. An alternative would be a software fallback that reads back the VBO data and draws it as either a client-side array or individual primitives (which would probably be even slower, but only applications that actually use doubles would take the penalty), but that might be more work than is reasonable to do for little benefit: stellarium and other QtOpenGL applications will lose OpenGL 1 support in the upcoming Qt 5 transition anyway, and flightgear would probably be unusably slow on such old hardware even if it didn't crash. As an immediate workaround, you can use software rendering with LIBGL_ALWAYS_SOFTWARE=1 stellarium (perhaps the error message should suggest that?), but expect that to be slow. I will report this upstream. ** Changed in: stellarium (Ubuntu) Status: Confirmed = Invalid ** Changed in: flightgear (Ubuntu) Status: New = Incomplete ** Changed in: mesa (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1079011 Title: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1079011/+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 1396232] Re: Xorg freeze
** Also affects: gnome-do (Ubuntu) Importance: Undecided Status: New -- 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/1396232 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-do/+bug/1396232/+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 1388887] Re: two cursors instead of one
This bug definitely occurs when I have not just rotated or un-rotated a screen. That is, the cursor can be fine, and then it suddenly changes to two cursors when some new window pops up or something (not sure what). However, I am using an external monitor which is rotated, at the time. -- 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/137 Title: two cursors instead of one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/137/+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 1240957] Re: Scrolling behaviour and window focus has changed and is inconsistent
This is still happening on Kubuntu 14.10. GTK3 applications like Synaptic won't scroll unless they are focused. -- 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/1240957 Title: Scrolling behaviour and window focus has changed and is inconsistent To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1240957/+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 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.
Sorry, upstream explicitly don't want bug reports for cards older than nv30 (yours is nv18, current is ~nv120): http://nouveau.freedesktop.org/wiki/MesaDrivers/ Changing the error message (at http://sources.debian.net/src/mesa/10.3.2-1/src/mesa/drivers/dri/nouveau/nv10_render.c/#L104 ) to something more useful, e.g. - assert(0); + assert(0 This application requires GLdouble vertex buffers, which your graphics card does not support. Try software rendering (LIBGL_ALWAYS_SOFTWARE=1 application).); is probably about all that is reasonable to do as a Debian/Ubuntu patch. ** Tags removed: quantal third-party-packages ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1079011 Title: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1079011/+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 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.
Thanks for looking into this for me. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1079011 Title: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1079011/+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 1314800] Re: i915 page table error on boot
Isn't it the same: https://bugs.freedesktop.org/show_bug.cgi?id=86583 ? ** Bug watch added: freedesktop.org Bugzilla #86583 https://bugs.freedesktop.org/show_bug.cgi?id=86583 -- 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/1314800 Title: i915 page table error on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1314800/+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 1389300] Re: Display frozen during sleep
** Also affects: systemd-shim (Ubuntu) Importance: Undecided Status: New -- 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/1389300 Title: Display frozen during sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1389300/+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 1174495] Re: Window Managers instability with r600 radeon and high monitor resolutions
Closing 0.9.9 task (0.9.9 series is obsolete) ** Changed in: compiz/0.9.9 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1174495 Title: Window Managers instability with r600 radeon and high monitor resolutions To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1174495/+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 1364630] Re: init: Error while reading from descriptor: Broken pipe
I have no nVidia, only AMD and broken pipe massage during booting Linux 3.18RC6 also still is. What does this have to Nvidia? о_О -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1364630/+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 1396019] Re: ubuntu 14.04
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1396019 Title: ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396019/+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 1394977] Re: Slow unity panel loading during first login
Found the issue, i had four NTFS partitions auto mounted with ntfs-3g in /etc/fstab. Setting three of them to noauto reduced the delay to 2 seconds. I'm quite sure if I remove the last one it's fixed completely, but I need it. So should I file the bug against fuse / ntfs-3g / another display package or is this inteded? -- 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/1394977 Title: Slow unity panel loading during first login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1394977/+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 1394977] Re: Slow unity panel loading during first login
I subscribed Elliot Murphy and filed it against fuse as ntfs-3g has no maintainer. Please mark the bug as conformed or invalid. Hope this is the right procedure. ** Also affects: fuse (Ubuntu) Importance: Undecided Status: New -- 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/1394977 Title: Slow unity panel loading during first login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1394977/+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 1396361] [NEW] Double Mouse Cursor
Public bug reported: When dragging with the mouse cursor often it creates a double cursor side by side about 10 cm apart on the screen. Only one cursor works. Using print screen does not show the cursor in the resulting image. Rebooting corrects the problem. This is similar to the double mouse cursor reported as a result of flash in a browser, however the current problem will occur without the browser open. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: LXDE Date: Tue Nov 25 15:58:51 2014 InstallationDate: Installed on 2014-10-24 (32 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xinput (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 utopic -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1396361 Title: Double Mouse Cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1396361/+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 1392887] Re: serial wacom devices gone after upgrade to utopic/14.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xf86-input-wacom (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1392887 Title: serial wacom devices gone after upgrade to utopic/14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1392887/+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 1381638] Re: [Utopic] Wacom stylus button does not work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xf86-input-wacom (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1381638 Title: [Utopic] Wacom stylus button does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1381638/+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 1392887] Re: serial wacom devices gone after upgrade to utopic/14.10
Thanks littlelion for the workaround, it was broken here too (Thinkpad X61 Tablet) and the .rules file fixed it. After upgrading from Trusty to Utopic, there was no /lib/udev/rules.d/69-xserver-xorg-input-wacom.rules and no /lib/udev/rules.d/69-wacom.rules/wacom.rules at all here. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1392887 Title: serial wacom devices gone after upgrade to utopic/14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1392887/+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 1376760] Re: after a screen rotation we get a double mouse pointer
There is a workaround: When I move an all day event in Thunderbird's month view to another day, it brings up another shadow symbol of the courser during moving that disappears when the date is dropped and then also the double courser icon is gone! -- 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/1376760 Title: after a screen rotation we get a double mouse pointer To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1376760/+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 1396232] Re: Xorg freeze
Urgh. You've run into https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=767280 which *should* be fixed in Vivid but isn't because 0.95.3-2 hasn't migrated out of proposed for some reason. Adding utopic task. ** Changed in: gnome-do (Ubuntu) Status: New = In Progress ** Changed in: gnome-do (Ubuntu) Importance: Undecided = Critical ** Changed in: gnome-do (Ubuntu) Assignee: (unassigned) = Chris Halse Rogers (raof) ** No longer affects: xorg (Ubuntu) ** Also affects: gnome-do (Ubuntu Vivid) Importance: Critical Assignee: Chris Halse Rogers (raof) Status: In Progress ** Also affects: gnome-do (Ubuntu Utopic) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #767280 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767280 ** Changed in: gnome-do (Ubuntu Utopic) Status: New = In Progress ** Changed in: gnome-do (Ubuntu Utopic) Assignee: (unassigned) = Chris Halse Rogers (raof) ** Changed in: gnome-do (Ubuntu Utopic) Importance: Undecided = High ** Changed in: gnome-do (Ubuntu Vivid) Importance: Critical = High -- 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/1396232 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-do/+bug/1396232/+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 1391975] Re: USC - mouse cursor on AMD graphics is drawing incorrectly
Well X talks to radeon code directly, which will do the cursor whatever way is correct for radeon... Mir is different because we're going through GBM (Mesa) and asking radeon to conform to GBM rules. I think that's probably where the bug lies. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1391975 Title: USC - mouse cursor on AMD graphics is drawing incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1391975/+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 1396412] [NEW] Severe Graphics lag after upgrade to 14.10
Public bug reported: After running a fresh Ubuntu 14.04 OS for several months without any problems, my pc now has several video lag issues after upgrading to 14.10. Everything is noticeably slower :streaming video, moving windows around in the desktop, playing steam games is impossible now and any other kind of game. Searched everywhere for a solution. Will probably revert back to fresh 14.04 install since there seems to be no immediate remedy. keep getting msg: Your system is providing 3D via software rendering rather than hardware rendering. This is a compatibility mode which should display 3D graphics properly but the performance may be very poor. If the problem you're reporting is related to graphics performance, your real question may be why X didn't use hardware acceleration for your system tried several things but could not fix thus far. There didn't appear to be a standard answer for this anywhere. I'm using an older AMD gpu but that shouldn't break everything when it worked well before. I wasn't using proprietary but rather the open source drivers that are supposed to be default. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: acceleration amd hardware lag -- 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/1396412 Title: Severe Graphics lag after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396412/+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
