[Desktop-packages] [Bug 2057684] [NEW] Backport a fix from Pulseaudio 17 to fix playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients
Public bug reported: This is a request for a backport of an existing bug fix, present in the recent Pulseaudio version 17 upstream release, to the outdated Pulseaudio 16 releases in jammy - noble. Affects: Ubuntu 22.04.0 LTS and all later versions. The fix fixes an annoying start of playback timing bug that affects my own software package octave-psychtoolbox-3 (part of Ubuntu universe), see https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374 which uses GStreamer for video and audio playback. Psychtoolbox is a very popular toolkit for neuroscience and related medical research, with Ubuntu as the recommended target distribution. It requires high reliability in audio and video presentation timing, so the bug described in the various links below is serious to our users. The bug also in the same way affects other media applications in Ubuntu which play back audio via the default (auto-plugged) pulseaudiosink GStreamer plugin. See GStreamer bug report https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The GStreamer bug turned out to be a pulseaudio client library bug (in libpulse.so.0). Any native pulseaudio client is affected, even if pipewire is used as desktop sound server in recent Ubuntu releases, given that many audio applications still access pipewire via its pulseaudio frontend (package pipewire-pulse). See pipewire bug https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399 The bug in libpulse.so.0, reported against Pulseaudio 16 in https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has been fixed for the Pulseaudio 17 release. See the following merge request for the following trivial one-liner patch that would need to be backported to Ubuntu's current implementation: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs I hoped that Pulseaudio 17 would be included in Debian in time for integration into Ubuntu 24.04-LTS, but apparently not much maintenance of pulseaudio is happening on the Debian side at the moment. Given that this bug affects all Ubuntu versions since Ubuntu 22.04-LTS, I'd ask kindly for a backport, ideally for Pulseaudio 15.99.1 in 22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at least for the upcoming 24.04-LTS. Alternatively it would have been great to get Pulseaudio upgraded to version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but apparently that is too late now, according to https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476 Thanks, -mario ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: gstreamer pipewire pulseaudio sound timing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2057684 Title: Backport a fix from Pulseaudio 17 to fix playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients Status in pulseaudio package in Ubuntu: New Bug description: This is a request for a backport of an existing bug fix, present in the recent Pulseaudio version 17 upstream release, to the outdated Pulseaudio 16 releases in jammy - noble. Affects: Ubuntu 22.04.0 LTS and all later versions. The fix fixes an annoying start of playback timing bug that affects my own software package octave-psychtoolbox-3 (part of Ubuntu universe), see https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374 which uses GStreamer for video and audio playback. Psychtoolbox is a very popular toolkit for neuroscience and related medical research, with Ubuntu as the recommended target distribution. It requires high reliability in audio and video presentation timing, so the bug described in the various links below is serious to our users. The bug also in the same way affects other media applications in Ubuntu which play back audio via the default (auto-plugged) pulseaudiosink GStreamer plugin. See GStreamer bug report https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The GStreamer bug turned out to be a pulseaudio client library bug (in libpulse.so.0). Any native pulseaudio client is affected, even if pipewire is used as desktop sound server in recent Ubuntu releases, given that many audio applications still access pipewire via its pulseaudio frontend (package pipewire-pulse). See pipewire bug https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399 The bug in libpulse.so.0, reported against Pulseaudio 16 in https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has been fixed for the Pulseaudio 17 release. See the following merge request for the following trivial one-liner patch that would need to be backported to Ubuntu's current implementation: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs I hoped that
[Desktop-packages] [Bug 2056079] Re: Serious playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients
Technically this bug belongs to the pulseaudio package in Ubuntu, not pipewire, but the bug tracker does not let me file a bug against pulseaudio. ** Tags added: pipewire pulseaudio -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2056079 Title: Serious playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients Status in gst-plugins-good: New Status in PipeWire: Fix Released Status in pulseaudio package in Ubuntu: New Bug description: This is a request for a backport of an existing bug fix, present in the recent Pulseaudio version 17 release, to the outdated Pulseaudio 16 releases in jammy - noble. Affects: Ubuntu 22.04.0 LTS and all later versions. The fix fixes an annoying start of playback timing bug that affects my own software package octave-psychtoolbox-3 (part of Ubuntu universe), see https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374 which uses GStreamer for video and audio playback. Psychtoolbox is a very popular toolkit for neuroscience and related medical research, with Ubuntu as the recommended target distribution. It requires high reliability in audio and video presentation timing, so the bug described in the various links below is serious to our users. The bug also in the same way affects other media applications in Ubuntu which play back audio via the default (auto-plugged) pulseaudiosink GStreamer plugin. See GStreamer bug report https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The GStreamer bug turned out to be a pulseaudio client library bug (in libpulse.so.0). Any native pulseaudio client is affected, even if pipewire is used as desktop sound server in recent Ubuntu releases, given that many audio applications still access pipewire via its pulseaudio frontend (package pipewire-pulse). See pipewire bug https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399 The bug in libpulse.so.0, reported against Pulseaudio 16 in https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has been fixed for the Pulseaudio 17 release. See the following merge request for the following trivial one-liner patch that would need to be backported to Ubuntu's current implementation: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs I hoped that Pulseaudio 17 would be included in Debian in time for integration into Ubuntu 24.04-LTS, but apparently not much maintenance of pulseaudio is happening on the Debian side at the moment. Given that this bug affects all Ubuntu versions since Ubuntu 22.04-LTS, I'd ask kindly for a backport, ideally for Pulseaudio 15.99.1 in 22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at least for the upcoming 24.04-LTS. Alternatively it would have been great to get Pulseaudio upgraded to version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but apparently that is too late now, according to https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476 Thanks, -mario To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-good/+bug/2056079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056079] [NEW] Serious playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients
Public bug reported: This is a request for a backport of an existing bug fix, present in the recent Pulseaudio version 17 release, to the outdated Pulseaudio 16 releases in jammy - noble. Affects: Ubuntu 22.04.0 LTS and all later versions. The fix fixes an annoying start of playback timing bug that affects my own software package octave-psychtoolbox-3 (part of Ubuntu universe), see https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374 which uses GStreamer for video and audio playback. Psychtoolbox is a very popular toolkit for neuroscience and related medical research, with Ubuntu as the recommended target distribution. It requires high reliability in audio and video presentation timing, so the bug described in the various links below is serious to our users. The bug also in the same way affects other media applications in Ubuntu which play back audio via the default (auto-plugged) pulseaudiosink GStreamer plugin. See GStreamer bug report https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The GStreamer bug turned out to be a pulseaudio client library bug (in libpulse.so.0). Any native pulseaudio client is affected, even if pipewire is used as desktop sound server in recent Ubuntu releases, given that many audio applications still access pipewire via its pulseaudio frontend (package pipewire-pulse). See pipewire bug https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399 The bug in libpulse.so.0, reported against Pulseaudio 16 in https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has been fixed for the Pulseaudio 17 release. See the following merge request for the following trivial one-liner patch that would need to be backported to Ubuntu's current implementation: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs I hoped that Pulseaudio 17 would be included in Debian in time for integration into Ubuntu 24.04-LTS, but apparently not much maintenance of pulseaudio is happening on the Debian side at the moment. Given that this bug affects all Ubuntu versions since Ubuntu 22.04-LTS, I'd ask kindly for a backport, ideally for Pulseaudio 15.99.1 in 22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at least for the upcoming 24.04-LTS. Alternatively it would have been great to get Pulseaudio upgraded to version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but apparently that is too late now, according to https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476 Thanks, -mario ** Affects: gst-plugins-good Importance: Unknown Status: Unknown ** Affects: pipewire Importance: Unknown Status: Unknown ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #1735 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735 ** Also affects: gst-plugins-good via https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #3399 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2056079 Title: Serious playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients Status in gst-plugins-good: Unknown Status in PipeWire: Unknown Status in pulseaudio package in Ubuntu: New Bug description: This is a request for a backport of an existing bug fix, present in the recent Pulseaudio version 17 release, to the outdated Pulseaudio 16 releases in jammy - noble. Affects: Ubuntu 22.04.0 LTS and all later versions. The fix fixes an annoying start of playback timing bug that affects my own software package octave-psychtoolbox-3 (part of Ubuntu universe), see https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374 which uses GStreamer for video and audio playback. Psychtoolbox is a very popular toolkit for neuroscience and related medical research, with Ubuntu as the recommended target distribution. It requires high reliability in audio and video presentation timing, so the bug described in the various links below is serious to our users. The bug also in the same way affects other media applications in Ubuntu which play back audio via the default (auto-plugged) pulseaudiosink GStreamer plugin. See GStreamer bug report https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The GStreamer bug turned out to be a pulseaudio client library bug (in libpulse.so.0). Any native pulseaudio client is affected, even
[Desktop-packages] [Bug 1958673] [NEW] SRU Request for upgrade to X-Server 1.20.14 in focal/20.04-LTS
Public bug reported: I was asked by one of your X-Server maintainers (Timo) to file a bug report here to request an upgrade to the current X-Server 1.20.14 for focal / Ubuntu 20.04-LTS from X-Server 1.20.13. I think this is called a SRU? The 1.20.14 version contains patches to fix some recent CVE's which are already in your 1.20.13 server, and additionally two patches from myself, cfe. the following merge request for the backport: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/778 Therefore an upgrade to 1.20.14 would add my two patches from that merge request. These are trivial backports from master and X-Server 21.1, which did not need any adaptation of the patches. One patch is a bug fix for a bug present in server 1.20 since day one. The other patch can be considered a regression fix for Ubuntu 20.04-LTS on hybrid graphics laptops with Intel iGPU + some other dGPU, although this is not a regression in the X-Server itself, but how the video driver selection by current Ubuntu interacts with the server. See explanation below why i consider it a regression fix. One patch fixes a bug: "Fix RandR leasing for more than 1 simultaneously active lease." The bug is a trivial code bug, which was there since RandR leasing was introduced into the 1.20 server by Keith Packard. Keith has reviewed my bug description and fix and agreed that it is indeed a bug and that my fix is correct. See the following merge request for the master branch with Keith's R-b in the discussion: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/767 The bug triggers whenever more than one RandR output gets leased out simultaneously during a session. It doesn't matter if multiple outputs get leased to a single client application, or if multiple separate client applications each lease out one output, or any mix of these. Only the very last output leased in a session can be released back to the server by the corresponding client (voluntarily or due to client exit, crash etc.). All other previously leased out outputs by the same or other clients will be completely dead and unusable until the X-Session is terminated and the X-Server restarted. So this can be seen as a denial of service bug. Typically affected applications would be Vulkan applications using the direct display extension, e.g., the octave-psychtoolbox-3 package in Ubuntu for scientific/medical research, or high end video games which may use this functionality, and probably most prominently VR applications built with SteamVR or the OpenXR Monado runtime and VR compositor. It has been tested extensively by myself on single X-Screen and dual X-Screen setups with 1, 2 and three displays, leasing out 1, 2 or 3 outputs. The second patch is "modesetting: Allow Present flips with mismatched stride on atomic drivers." It applies to the xorg-video-modesetting ddx. It does not fix a bug in the strict sense, but it does improve the quality and performance of unredirected fullscreen applications like video games or scientific software like octave-psychtoolbox-3 under PRIME render offload in a way that turns them from "technically correct behavior, but unusable in practice" to "good". The patch is based on a tip by Michel Daenzer from AMD. See the following original merge request for X-Server master for details: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/740 On modern kernels and atomic modesetting drivers, the patch allows the modesetting-ddx to use page flipping for fullscreen applications even if the Pixmap stride between the display gpu (iGPU, e.g., Intel, AMD) and the render offload gpu (e.g., AMD, NVidia) is mismatched, as atomic modesetting drivers can easily handle that. Without the patch, on such mismatched stride configurations, rejecting the pageflip, normally the X-Server and modesetting-ddx would fall back to a fullscreen copy swap, executed via glamor and therefore Mesa as a framebuffer copy from application backbuffer to system/X-Server frontbuffer. This increases required memory bandwidth and thereby reduces cpu and gpu performance, increases latency and the potential for skipped frames, e.g., for OpenGL and Vulkan applications, and makes presentation timestamps unreliable, which is especially bad for scientific applications like the octave-psychtoolbox-3 package. More importantly for the general case, it causes massive visual tearing and display artifacts. The current implementation of the X-Servers DRI3/Present backend and glamor + Mesa's does not use hardware synchronization to vertical blank (vsync) for such "copy swaps", only software sync, which is prone to random X-Server scheduling and processing latency between start of vblank and submission of the copy command to Mesa. Additionally Mesa submits the hardware copy commands to the regular 3D engine command stream, so further random delays are added by any other running GUI application, stalling the "copy command hw packet" behind other unrelated 2D or 3D
[Desktop-packages] [Bug 1674304] Re: PRIME synchronization not working with xserver-1.19.x
I can't see anything obviously wrong with your kernel output. It seems as if the nvidia_modeset driver has loaded. I assume xrandr --verbose output also reports PRIME sync: 0? However, the NVidia forum has some reports by people with similar problems, hinting at a potential incompatibility of the 375.39 NVidia driver with at Linux 4.10 from the Ubuntu 17.04 beta. Maybe try with a 4.8 kernel? See https://devtalk.nvidia.com/default/topic/957814/linux/prime-and-prime- synchronization/10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1674304 Title: PRIME synchronization not working with xserver-1.19.x Status in nvidia-prime package in Ubuntu: Confirmed Bug description: xserver-1.19.x is being proposed for 17.04, currently available in test ppa https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799 On 2 separate Optimus laptops there is no sign of it actually working, tearing while using nvidia drivers (375.x) is rampart. Testing with both current 4.10.0-13 & previous 4.9.0-11 kernels. Shows this in kern.log so support is enabled Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver supports precise vblank timestamp ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nvidia-prime 0.8.4 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Mar 20 07:53:12 2017 InstallationDate: Installed on 2017-03-15 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1674304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1674304] Re: PRIME synchronization not working with xserver-1.19.x
Is the nvidia-drm module loaded and its drm modesetting enabled? E.g., via kernel cmdline option nvidia_drm.modeset=1 cat /sys/module/nvidia_drm/parameters/modeset should be 1 or "Y" I think that isn't needed for PRIME outputs, but it is needed for the new PRIME sync to work, so maybe not yet part of the nvidia-prime package/setup. Downside is that multi-gpu SLI wouldn't work anymore, but then i assume there aren't any Optimus laptops with two discrete NVidia gpu's, so that's a non-issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1674304 Title: PRIME synchronization not working with xserver-1.19.x Status in nvidia-prime package in Ubuntu: Confirmed Bug description: xserver-1.19.x is being proposed for 17.04, currently available in test ppa https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799 On 2 separate Optimus laptops there is no sign of it actually working, tearing while using nvidia drivers (375.x) is rampart. Testing with both current 4.10.0-13 & previous 4.9.0-11 kernels. Shows this in kern.log so support is enabled Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver supports precise vblank timestamp ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nvidia-prime 0.8.4 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Mar 20 07:53:12 2017 InstallationDate: Installed on 2017-03-15 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1674304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1237718] [NEW] [arrandale] GPU lockup IPEHR: 0xacfbf37f
Public bug reported: This came up as System problem detected after a cold reboot. However, this is a hybrid graphics mbp which only uses the discrete nvidia gpu with nouveau. The intel card is inaccessible. I played around with trying to get the intel working via vgaswitcheroo, to no success - it ended with a black screen (maybe also gpu hang?) Strangely that was multiple reboots ago, not sure why it is reported now. However, nouveau is also unreliable since the upgrade to 13.10, reporting frequent random gpu lockups after working perfectly fine for hours. Maybe the bug reporter gets confused. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.99.903-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3 Uname: Linux 3.11.0-11-lowlatency x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Chipset: arrandale CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 7 20:05:55 2013 DistUpgraded: 2013-10-06 06:04:30,466 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: backfire, 0.84-2, 3.11.0-11-generic, x86_64: installed backfire, 0.84-2, 3.8.0-32-generic, x86_64: installed DuplicateSignature: [arrandale] GPU lockup IPEHR: 0xacfbf37f Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00c7] InstallationDate: Installed on 2012-04-23 (534 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64+mac (20120421) InterpreterPath: /usr/bin/python3.3 MachineType: Apple Inc. MacBookPro6,2 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=74bd9b8e-bd79-4987-b628-9e5156b7bc46 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu5 libdrm2 2.4.46-1 xserver-xorg-video-intel 2:2.99.903-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [arrandale] GPU lockup IPEHR: 0xacfbf37f UpgradeStatus: Upgraded to saucy on 2013-10-06 (3 days ago) UserGroups: dmi.bios.date: 12/09/11 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP61.88Z.0057.B0F.1112091028 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP61.88Z.0057.B0F.1112091028:bd12/09/11:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.name: MacBookPro6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.10+13.10.20131004-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.903-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 10 01:11:49 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu1 xserver.video_driver: nouveau ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 freeze saucy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1237718 Title: [arrandale] GPU lockup IPEHR: 0xacfbf37f Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: This came up as System problem detected after a cold reboot. However, this is a hybrid graphics mbp which only uses the discrete nvidia gpu with nouveau. The intel card is inaccessible. I played around with trying to get the intel working via vgaswitcheroo, to no success - it ended with a black screen (maybe