[Desktop-packages] [Bug 1301158] Re: nm-applet icon invisible
This is an very old bug, but maybe it could help someone. In my case, the .dbus directory in home was owned by root:root and that was actually the blocker. sudo chown -R user:user ~/.dbus solved the issue and nm-applet became visible after restart. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1301158 Title: nm-applet icon invisible Status in network-manager-applet package in Ubuntu: Confirmed Bug description: nm-applet's icon is invisible since last session, when it suddenly disappeared. System has been rebooted, but the icon didn't appear again. So i'm currently not able to select a network, turn on/off networks, edit networks and so on. $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.0 Contains all updates as of 2014/04/01. Running 3.14 kernel. $ apt-cache policy network-manager network-manager: Installed: 0.9.8.8-0ubuntu5 Candidate: 0.9.8.8-0ubuntu5 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-gnome 0.9.8.8-0ubuntu3 Uname: Linux 3.14.0-031400-generic i686 ApportVersion: 2.14-0ubuntu1 Architecture: i386 CurrentDesktop: XFCE Date: Wed Apr 2 07:42:58 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-03-21 (11 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140225) IpRoute: default via 192.168.43.1 dev wlan0 proto static 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.14 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Bob Vorgabe 8ba5fa89-4c5d-4f06-a3ff-4bdeb457f99b gsm 1396367611 Di 01 Apr 2014 17:53:31 CEST nono /org/freedesktop/NetworkManager/Settings/2 michigreat-hotspot1ca2fab0-b64c-4eec-b77c-70c7827d7217 802-11-wireless 1396417354 Mi 02 Apr 2014 07:42:34 CEST yes no /org/freedesktop/NetworkManager/Settings/1 greatwlan2d0efc775-adbe-4260-910f-567dc8dd54fc 802-11-wireless 1396382625 Di 01 Apr 2014 22:03:45 CEST yes no /org/freedesktop/NetworkManager/Settings/0 Kabelnetzwerkverbindung 1 c0551746-459f-40bd-be68-8a8ded54f2bc 802-3-ethernet139641 Mi 02 Apr 2014 07:12:35 CEST yes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1301158/+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 1574347] Re: [SRU]network-manager
@leopenausa: have you tried restarting NM instead of rebooting? sudo systemctl restart network-manager.service -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574347 Title: [SRU]network-manager Status in NetworkManager: Fix Released Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Xenial: Fix Committed Bug description: [Impact] NM needs to re-read the DEVTYPE after the device name changed, an example is that WiFi network list disappears from network manager applet Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. [Testcase] After upgrading to the new version, the repeating the above steps should give expected behavior. [Regression Potential] Potential of causing regression is relatively small for a one line change to re-read a value to be known. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1574266] Re: Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning
New finding: installing xserver-xorg-video-intel actually solved the problem for me, LibreOffice is no longer causing Xorg to crash. Previously I think Xorg was working using modesetting driver instead of intel, though I might be wrong. My HW: Integrated Graphics Chipset: Intel(R) HD Graphics 4600 on FUJITSU LIFEBOOK E754. -- 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/1574266 Title: Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning Status in xorg package in Ubuntu: Confirmed Bug description: dmesg output : [ 8815.416923] [drm] stuck on render ring [ 8815.417367] [drm] GPU HANG: ecode 6:0:0x05b2c6c5, in Compositor [21164], reason: Ring hung, action: reset [ 8815.419462] drm/i915: Resetting chip after gpu hang [ 8821.417592] [drm] stuck on render ring [ 8821.418007] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: Ring hung, action: reset [ 8821.420108] drm/i915: Resetting chip after gpu hang [ 8827.430254] [drm] stuck on render ring [ 8827.430672] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], reason: Ring hung, action: reset [ 8827.432786] drm/i915: Resetting chip after gpu hang [ 8833.418862] [drm] stuck on render ring [ 8833.419454] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], reason: Ring hung, action: reset [ 8833.421551] drm/i915: Resetting chip after gpu hang [ 8839.419503] [drm] stuck on render ring [ 8839.419971] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], reason: Ring hung, action: reset [ 8839.422060] drm/i915: Resetting chip after gpu hang [ 8845.432118] [drm] stuck on render ring [ 8845.432647] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: Ring hung, action: reset [ 8845.434799] drm/i915: Resetting chip after gpu hang [ 8851.432751] [drm] stuck on render ring [ 8851.433142] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], reason: Ring hung, action: reset [ 8851.435224] drm/i915: Resetting chip after gpu hang [ 8857.457381] [drm] stuck on render ring [ 8857.457797] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], reason: Ring hung, action: reset [ 8857.459883] drm/i915: Resetting chip after gpu hang [ 8863.458003] [drm] stuck on render ring [ 8863.458555] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: Ring hung, action: reset [ 8863.460640] drm/i915: Resetting chip after gpu hang [ 8869.458654] [drm] stuck on render ring [ 8869.459001] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: Ring hung, action: reset [ 8869.459095] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning! [ 8869.461116] drm/i915: Resetting chip after gpu hang [ 8875.435238] [drm] stuck on render ring [ 8875.435606] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], reason: Ring hung, action: reset [ 8875.437697] drm/i915: Resetting chip after gpu hang [ 8881.447863] [drm] stuck on render ring [ 8881.448251] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], reason: Ring hung, action: reset [ 8881.450331] drm/i915: Resetting chip after gpu hang [ 8887.436497] [drm] stuck on render ring [ 8887.436876] [drm] GPU HANG: ecode 6:0:0xbb88, in compiz [6817], reason: Ring hung, action: reset [ 8887.438961] drm/i915: Resetting chip after gpu hang [ 8893.437078] [drm] stuck on render ring [ 8893.437471] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6817], reason: Ring hung, action: reset [ 8893.439562] drm/i915: Resetting chip after gpu hang ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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: Sun Apr 24 15:57:17 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2002] InstallationDate: Installed on 2016-04-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=45576678-3e92-4769-b6d3-3e3cafa54c2e ro quiet splash
[Desktop-packages] [Bug 1574347] Re: [SRU]network-manager
For me, the version 1.2.0-0ubuntu0.16.04.2 fixes the issue with wifi not visible after fresh boot. Now it works fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574347 Title: [SRU]network-manager Status in NetworkManager: Fix Released Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Xenial: Fix Committed Bug description: [Impact] NM needs to re-read the DEVTYPE after the device name changed, an example is that WiFi network list disappears from network manager applet Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. [Testcase] After upgrading to the new version, the repeating the above steps should give expected behavior. [Regression Potential] Potential of causing regression is relatively small for a one line change to re-read a value to be known. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1574347] Re: WiFi network list disappears from network manager applet
So is there some Ubuntu package containing the fix already, so that we could test it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574347 Title: WiFi network list disappears from network manager applet Status in NetworkManager: Fix Released Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Confirmed Bug description: Issue is in Ubuntu 16.04 LTS amd64 version. Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. Please solve this issue asap. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 23:15:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp18s0 proto static metric 600 169.254.0.0/16 dev wlp18s0 scope link metric 1000 192.168.1.0/24 dev wlp18s0 proto kernel scope link src 192.168.1.99 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Airtel-201 d263b201-9281-427e-94e2-762fa620813c 802-11-wireless 1461519922 Sunday 24 April 2016 11:15:22 PM IST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp18s0 activated /org/freedesktop/NetworkManager/ActiveConnection/8 Wired connection 1 142942d4-d247-4880-9bab-1eeafc29ca86 802-3-ethernet 1461508904 Sunday 24 April 2016 08:11:44 PM IST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp18s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 Airtel-201 d263b201-9281-427e-94e2-762fa620813c /org/freedesktop/NetworkManager/ActiveConnection/8 enp19s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1576163] Re: Libreoffice crashes when opening a dialog
Of course it is related, because both bugs report similar symptoms -- Xorg crashing/freezing with "drm/i915: Resetting chip after gpu hang" error after running Libreoffice. Of course LO is an unlikely cause, rather it is something in Xorg, so the other bug is more appropriate. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1576163 Title: Libreoffice crashes when opening a dialog Status in libreoffice package in Ubuntu: New Bug description: When any type of dialog window opens, libreoffice crashes causing lightdm (unity?) to crash aswell. Since not only libreoffice crashes, but also lightdm/unity, all programs will stop causing work in progress to be lost. Ubuntu: Ubuntu 16.04 LTS libreoffice: 1:5.1.2 Relevant dmesg output: [91484.085656] drm/i915: Resetting chip after gpu hang [91838.035765] [drm] stuck on render ring [91838.036466] [drm] GPU HANG: ecode 7:0:0x85dc, in Xorg [24404], reason: Ring hung, action: reset ... [91848.037375] Hardware name: LENOVO 20EF000SMN/20EF000SMN, BIOS GNET73WW (2.21 ) 03/12/2015 Since the gpu hangs, this is likely a problem with intel gfx drivers. Should be of high importance since all work in progress is lost dues to complete lightdm crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1576163/+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 1576163] Re: Libreoffice crashes when opening a dialog
There is already an appropriate bug 1574266 I think. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1576163 Title: Libreoffice crashes when opening a dialog Status in libreoffice package in Ubuntu: New Bug description: When any type of dialog window opens, libreoffice crashes causing lightdm (unity?) to crash aswell. Since not only libreoffice crashes, but also lightdm/unity, all programs will stop causing work in progress to be lost. Ubuntu: Ubuntu 16.04 LTS libreoffice: 1:5.1.2 Relevant dmesg output: [91484.085656] drm/i915: Resetting chip after gpu hang [91838.035765] [drm] stuck on render ring [91838.036466] [drm] GPU HANG: ecode 7:0:0x85dc, in Xorg [24404], reason: Ring hung, action: reset ... [91848.037375] Hardware name: LENOVO 20EF000SMN/20EF000SMN, BIOS GNET73WW (2.21 ) 03/12/2015 Since the gpu hangs, this is likely a problem with intel gfx drivers. Should be of high importance since all work in progress is lost dues to complete lightdm crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1576163/+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 1574266] Re: Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning
For me it is 100% reproducible with LibreOffice, especially when one quits LO uncleanly and then on the next run it opens a dialog asking about file recovery. Whatever I click in that dialog, LibreOffice will hang for a while and then the whole X session is restarted. -- 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/1574266 Title: Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning Status in xorg package in Ubuntu: Confirmed Bug description: dmesg output : [ 8815.416923] [drm] stuck on render ring [ 8815.417367] [drm] GPU HANG: ecode 6:0:0x05b2c6c5, in Compositor [21164], reason: Ring hung, action: reset [ 8815.419462] drm/i915: Resetting chip after gpu hang [ 8821.417592] [drm] stuck on render ring [ 8821.418007] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: Ring hung, action: reset [ 8821.420108] drm/i915: Resetting chip after gpu hang [ 8827.430254] [drm] stuck on render ring [ 8827.430672] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], reason: Ring hung, action: reset [ 8827.432786] drm/i915: Resetting chip after gpu hang [ 8833.418862] [drm] stuck on render ring [ 8833.419454] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], reason: Ring hung, action: reset [ 8833.421551] drm/i915: Resetting chip after gpu hang [ 8839.419503] [drm] stuck on render ring [ 8839.419971] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], reason: Ring hung, action: reset [ 8839.422060] drm/i915: Resetting chip after gpu hang [ 8845.432118] [drm] stuck on render ring [ 8845.432647] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: Ring hung, action: reset [ 8845.434799] drm/i915: Resetting chip after gpu hang [ 8851.432751] [drm] stuck on render ring [ 8851.433142] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], reason: Ring hung, action: reset [ 8851.435224] drm/i915: Resetting chip after gpu hang [ 8857.457381] [drm] stuck on render ring [ 8857.457797] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], reason: Ring hung, action: reset [ 8857.459883] drm/i915: Resetting chip after gpu hang [ 8863.458003] [drm] stuck on render ring [ 8863.458555] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: Ring hung, action: reset [ 8863.460640] drm/i915: Resetting chip after gpu hang [ 8869.458654] [drm] stuck on render ring [ 8869.459001] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: Ring hung, action: reset [ 8869.459095] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning! [ 8869.461116] drm/i915: Resetting chip after gpu hang [ 8875.435238] [drm] stuck on render ring [ 8875.435606] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], reason: Ring hung, action: reset [ 8875.437697] drm/i915: Resetting chip after gpu hang [ 8881.447863] [drm] stuck on render ring [ 8881.448251] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], reason: Ring hung, action: reset [ 8881.450331] drm/i915: Resetting chip after gpu hang [ 8887.436497] [drm] stuck on render ring [ 8887.436876] [drm] GPU HANG: ecode 6:0:0xbb88, in compiz [6817], reason: Ring hung, action: reset [ 8887.438961] drm/i915: Resetting chip after gpu hang [ 8893.437078] [drm] stuck on render ring [ 8893.437471] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6817], reason: Ring hung, action: reset [ 8893.439562] drm/i915: Resetting chip after gpu hang ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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: Sun Apr 24 15:57:17 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2002] InstallationDate: Installed on 2016-04-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=45576678-3e92-4769-b6d3-3e3cafa54c2e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display
