[Desktop-packages] [Bug 1669344] Re: Received signal 4 ILL_ILLOPN
Confirmed. Updating to 4.8 (from 4.4) fixed the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1669344 Title: Received signal 4 ILL_ILLOPN Status in chromium-browser package in Ubuntu: Confirmed Bug description: This morning chromium-browser upgraded to 56.0.2924.76-0ubuntu0.16.10.1335 and promptly stopped working for me. When trying to load any page, it dumps this traceback: Received signal 4 ILL_ILLOPN 7f78b7a509e7 #0 0x7f78d509500e base::debug::StackTrace::StackTrace() #1 0x7f78d5095403 #2 0x7f78d53aa630 #3 0x7f78b7a509e7 WTF::decommitSystemPages() #4 0x7f78c3f997b0 #5 0x7f78c3f99f17 #6 0x7f78c3f97b0e blink::NormalPageArena::allocatePage() #7 0x7f78c3f98560 blink::NormalPageArena::outOfLineAllocate() #8 0x7f78c3987678 blink::ChromeClientImpl::create() #9 0x7f78c3a2929a blink::WebViewImpl::WebViewImpl() #10 0x7f78c3a2aeb3 blink::WebViewImpl::create() #11 0x7f78cfcd8769 content::RenderViewImpl::Initialize() #12 0x7f78cfcd9443 content::RenderViewImpl::Create() #13 0x7f78cf5d8692 content::mojom::RendererStubDispatch::Accept() #14 0x7f78d4bc2671 mojo::InterfaceEndpointClient::HandleValidatedMessage() #15 0x7f78d0d17bd0 #16 0x7f78d0d18034 #17 0x7f78d5096543 base::debug::TaskAnnotator::RunTask() #18 0x7f78c3f35f4f blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue() #19 0x7f78c3f36ab0 blink::scheduler::TaskQueueManager::DoWork() #20 0x7f78d5096543 base::debug::TaskAnnotator::RunTask() #21 0x7f78d50bc740 base::MessageLoop::RunTask() #22 0x7f78d50be33d base::MessageLoop::DeferOrRunPendingTask() #23 0x7f78d50bf19d base::MessageLoop::DoWork() #24 0x7f78d50bf589 base::MessagePumpDefault::Run() #25 0x7f78d50bbb22 base::MessageLoop::RunHandler() #26 0x7f78d50e44b8 base::RunLoop::Run() #27 0x7f78cfcf5629 #28 0x7f78cfde7048 #29 0x7f78cfde7444 #30 0x7f78cfde68c1 content::ContentMain() #31 0x55b0046e086c #32 0x7f78bfec03f1 __libc_start_main #33 0x55b0046e073a r8: r9: r10: 0022 r11: 0206 r12: 16113987 r13: 0004 r14: 7f78b7c87448 r15: di: 3fb7e8201000 si: 0001e000 bp: 16113981c210 bx: 16113981c218 dx: 0008 ax: cx: ff68 sp: 7fffa09e5f30 ip: 7f78b7a509e7 efl: 00010286 cgf: 0033 erf: trp: 0006 msk: cr2: [end of stack trace] Being chromium, the overall processes don't die or coredump, so apport never sends any reports here. That is why I am filing via ubuntu-bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: chromium-browser 56.0.2924.76-0ubuntu0.16.10.1335 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-DP-2: edid-base64: dpms: Off modes: enabled: enabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-2: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-eDP-1: edid-base64: AP///wAw5DcEAAAXAQSVHBB4Ar8FmllVjiYdUFQBAQEBAQEBAQEBAQEBAQEBFjaAunA4D0AwIDUAFJwQAAAa/gBMRyBEaXNwbGF5CiAg/gBMUDEyNVdGMi1TUEIyAN0= dpms: On modes: 1920x1080 enabled: enabled status: connected Date: Thu Mar 2 10:18:41 2017 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/systemd-session:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2014-05-29 (1007 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InstalledPlugins: /usr/lib/mozilla/plugins: => librhythmbox-itms-detection-plugin.so (size: 6072 bytes, mtime: Sat Sep 10 19:28:55 2016) Load-Avg-1min: 0.95 Load-Processes-Running-Percent: 0.2% MachineType: LENOVO 20ALCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: Upgraded to yakkety on 2016-10-01 (152 days ago) dmi.bios.date: 08/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GIET76WW (2.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.cha
[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
It also works for me. THANK YOU! and good work! -- 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/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Xenial: Fix Committed Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
According to #14 (or #38) in https://bugs.launchpad.net/ubuntu/+bug/1573454 it happens in all Ubuntu flavours, but I did not test myself. I am using xubuntu too. If it is affecting all ubuntu versions with intel graphics that would be a very important bug and not getting this fixed after months, in a LTS, is a good enough reason for users to sadly stop using 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/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Xenial: Confirmed Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
I dont understand how a bug as important as this is not fixed after months in a LTS release of 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/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Xenial: Confirmed Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [SRU for Ubuntu 16.04] Package (yakkety): xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 Current (xenial): xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Debian Changelog (since 2:2.99.917+git20160325-1ubuntu1)] xserver-xorg-video-intel (2:2.99.917+git20160706-1ubuntu1) yakkety; urgency=medium * Merge from Debian. xserver-xorg-video-intel (2:2.99.917+git20160706-1) unstable; urgency=medium * New upstream snapshot. * fix-fd-leak-when-intel-scrn-create-fails.diff, sna-let-modesetting- handle-gen9+.diff: Dropped as the fallback to modesetting will be fully handled in the xserver. * .docs: Include a minimal xorg.conf. xserver-xorg-video-intel (2:2.99.917+git20160522-1ubuntu1) yakkety; urgency=medium * Merge from Debian. * install-dri3info.diff: Install dri3info with the driver, add libxcomposite-dev to build-depends. xserver-xorg-video-intel (2:2.99.917+git20160522-1) unstable; urgency=medium * New upstream snapshot. (Closes: #823116) * fix-fd-leak-when-intel-scrn-create-fails.diff: Fix a failure falling back on another driver when scrn create fails. [Regression Potential] Regression potential here seems minimal. However, as seen in the above Debian changelog, we have a new snapshot which includes several changes since March 25. === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)
Confirmed: libXext 1.3.3 solve the error spamming problem. You can install this version from Ubuntu 15.04 (Vivid) both i386 and amd64 (just in case). NOTE: For steam users, you will also have to replace the steam libXext libraries provided by steam package. These libraries are, in your steam installation directory, here: - ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libXext.so.6.4.0 - ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/libXext.so.6.4.0 As log as you replace the "libXext.so.6.4.0" you wont have to replace the "libXext.so.6", as this one is a symlink to "libXext.so.6.4.0". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1369113 Title: Steam game began crashing 2014-09-12 (cross-post Source bugtracker) Status in “steam” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: Confirmed Bug description: I am cross-posting this issue, which I reported to Valve's Source GIT issue tracker, because it was suggested that the regression may be due to Ubuntu Xorg changes rather than changes on the Steam end. Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822 Symptom -- DoD:Source loads normally. But after a few minutes of playing (not a specific time as far as I can tell), the game freezes in place. A short clip (maybe a quarter of a second) of the last audio that played then repeats over and over on a loop. The process has to be killed manually with a QUIT or HUP signal for good measure. This is a new issue that just arose today. I have included system info, kernel log, and output when game is run from terminal and crashes. X info -- X.Org X Server 1.16.0 Release Date: 2014-07-16 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug Build Date: 10 September 2014 01:10:01PM xorg-server 2:1.16.0-1ubuntu1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.32.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. System -- OS: Ubuntu 14.10 (latest updates) Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64 Model: HP Envy x360 lspci: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4) 00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev e4) 00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4) 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4) 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI mode 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01) 08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b) 09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) Kernel log excerpt (from game start through crash end) -- Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open] Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW context 1 created Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open] Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW context 1 created Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] [CONNECTOR:14:?] Sep 12 19:11:25 kernel: [ 4447.852796] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] [CONNECTOR:14:eDP-1] Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP VDD on Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vd
[Desktop-packages] [Bug 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)
Updating to libXext 1.3.3 should solve the problem. That warning message was removed in this commit: http://cgit.freedesktop.org/xorg/lib/libXext/commit/?id=11aad96bd689d54156064d2e81213dc827a689d1 and that commit released in 1.3.3 (look at the comment from Keith Packard): http://lists.freedesktop.org/pipermail/xorg/2014-July/056771.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1369113 Title: Steam game began crashing 2014-09-12 (cross-post Source bugtracker) Status in “steam” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: Confirmed Bug description: I am cross-posting this issue, which I reported to Valve's Source GIT issue tracker, because it was suggested that the regression may be due to Ubuntu Xorg changes rather than changes on the Steam end. Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822 Symptom -- DoD:Source loads normally. But after a few minutes of playing (not a specific time as far as I can tell), the game freezes in place. A short clip (maybe a quarter of a second) of the last audio that played then repeats over and over on a loop. The process has to be killed manually with a QUIT or HUP signal for good measure. This is a new issue that just arose today. I have included system info, kernel log, and output when game is run from terminal and crashes. X info -- X.Org X Server 1.16.0 Release Date: 2014-07-16 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug Build Date: 10 September 2014 01:10:01PM xorg-server 2:1.16.0-1ubuntu1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.32.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. System -- OS: Ubuntu 14.10 (latest updates) Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64 Model: HP Envy x360 lspci: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4) 00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev e4) 00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4) 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4) 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI mode 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01) 08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b) 09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) Kernel log excerpt (from game start through crash end) -- Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open] Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW context 1 created Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open] Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW context 1 created Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] [CONNECTOR:14:?] Sep 12 19:11:25 kernel: [ 4447.852796] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] [CONNECTOR:14:eDP-1] Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP VDD on Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 0x8008 PP_CONTROL: 0xabcd000f Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 00e04c Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 00e04c Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edi
[Desktop-packages] [Bug 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)
Same problem here. Xubuntu 14.10 64bit Intel HD 4600 I am having the "_xgeWireToEvent: Unknown extension 148, this should never happen." logged due to steam. My ~/.cache/upstart/startxfce4.log and /tmp/dumps/"user"_stdout.txt are showing this message and these files grow several GB due to this message. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1369113 Title: Steam game began crashing 2014-09-12 (cross-post Source bugtracker) Status in “steam” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: Confirmed Bug description: I am cross-posting this issue, which I reported to Valve's Source GIT issue tracker, because it was suggested that the regression may be due to Ubuntu Xorg changes rather than changes on the Steam end. Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822 Symptom -- DoD:Source loads normally. But after a few minutes of playing (not a specific time as far as I can tell), the game freezes in place. A short clip (maybe a quarter of a second) of the last audio that played then repeats over and over on a loop. The process has to be killed manually with a QUIT or HUP signal for good measure. This is a new issue that just arose today. I have included system info, kernel log, and output when game is run from terminal and crashes. X info -- X.Org X Server 1.16.0 Release Date: 2014-07-16 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug Build Date: 10 September 2014 01:10:01PM xorg-server 2:1.16.0-1ubuntu1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.32.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. System -- OS: Ubuntu 14.10 (latest updates) Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64 Model: HP Envy x360 lspci: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4) 00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev e4) 00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4) 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4) 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI mode 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01) 08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b) 09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) Kernel log excerpt (from game start through crash end) -- Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open] Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW context 1 created Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open] Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW context 1 created Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] [CONNECTOR:14:?] Sep 12 19:11:25 kernel: [ 4447.852796] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] [CONNECTOR:14:eDP-1] Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP VDD on Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 0x8008 PP_CONTROL: 0xabcd000f Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 00e04c Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 00e04c Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edid_to_eld] ELD: no CEA Extension fo