[Touch-packages] [Bug 1871282] Re: libpam fails to install during upgrade from 19.10 to 20.20 beta
** Description changed: Hello, I runned an upgrade from 19.10 to 20.20 beta and it gave me a bunch of errors related to pam: 6.3965:installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Segmentation fault), core dumped installed libpam-runtime package post-installation script subprocess was killed by signal (Segmentation fault), core dumped And some other errors probably because of the previous failures: Não foi possível instalar '/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb' (Could not install '/var...') Não foi possível instalar 'libpam-modules' Não foi possível instalar 'passwd' + + I had some extra repos added: + google-chrome + flacon-ubuntu-ppa-eoan + kubuntu-ppa-ubuntu-backports-disco + otto-kesselgulasch-ubuntu-gimp-bionic + virtualbox.list + skype-stable.list -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1871282 Title: libpam fails to install during upgrade from 19.10 to 20.20 beta Status in pam package in Ubuntu: New Bug description: Hello, I runned an upgrade from 19.10 to 20.20 beta and it gave me a bunch of errors related to pam: 6.3965:installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Segmentation fault), core dumped installed libpam-runtime package post-installation script subprocess was killed by signal (Segmentation fault), core dumped And some other errors probably because of the previous failures: Não foi possível instalar '/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb' (Could not install '/var...') Não foi possível instalar 'libpam-modules' Não foi possível instalar 'passwd' I had some extra repos added: google-chrome flacon-ubuntu-ppa-eoan kubuntu-ppa-ubuntu-backports-disco otto-kesselgulasch-ubuntu-gimp-bionic virtualbox.list skype-stable.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1871282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871282] [NEW] libpam fails to install during upgrade from 19.10 to 20.20 beta
Public bug reported: Hello, I runned an upgrade from 19.10 to 20.20 beta and it gave me a bunch of errors related to pam: 6.3965:installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Segmentation fault), core dumped installed libpam-runtime package post-installation script subprocess was killed by signal (Segmentation fault), core dumped And some other errors probably because of the previous failures: Não foi possível instalar '/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb' (Could not install '/var...') Não foi possível instalar 'libpam-modules' Não foi possível instalar 'passwd' ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1871282 Title: libpam fails to install during upgrade from 19.10 to 20.20 beta Status in pam package in Ubuntu: New Bug description: Hello, I runned an upgrade from 19.10 to 20.20 beta and it gave me a bunch of errors related to pam: 6.3965:installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Segmentation fault), core dumped installed libpam-runtime package post-installation script subprocess was killed by signal (Segmentation fault), core dumped And some other errors probably because of the previous failures: Não foi possível instalar '/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb' (Could not install '/var...') Não foi possível instalar 'libpam-modules' Não foi possível instalar 'passwd' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1871282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1857099] [NEW] strerror_r used as non-portable format
Public bug reported: I got a elfutils-0.178 glibc provides two different signatures for strerror_r. One is GNU-specific and it is not portable. The other is int strerror_r(int errnum, char *buf, size_t buflen); /* XSI-compliant */ char *strerror_r(int errnum, char *buf, size_t buflen); /* GNU-specific */ man strerror(3) says: The XSI-compliant strerror_r() is preferred for portable applications. It returns the error string in the user-supplied buffer buf of length buflen. musl implements strerror_r as XSI-compliant version while elfutils uses GNU-specific variant. The solution should not simply ignore strerror_r return value as it would break build when -Werror=unused-result is set. An alternative is to do something like: https://github.com/luizluca/openwrt/blob/a79698fefdd9dacb84865c870bf75aee978c005d/package/libs/elfutils/patches/100 -musl-compat.patch#L51 ** Affects: elfutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to elfutils in Ubuntu. https://bugs.launchpad.net/bugs/1857099 Title: strerror_r used as non-portable format Status in elfutils package in Ubuntu: New Bug description: I got a elfutils-0.178 glibc provides two different signatures for strerror_r. One is GNU-specific and it is not portable. The other is int strerror_r(int errnum, char *buf, size_t buflen); /* XSI-compliant */ char *strerror_r(int errnum, char *buf, size_t buflen); /* GNU-specific */ man strerror(3) says: The XSI-compliant strerror_r() is preferred for portable applications. It returns the error string in the user-supplied buffer buf of length buflen. musl implements strerror_r as XSI-compliant version while elfutils uses GNU-specific variant. The solution should not simply ignore strerror_r return value as it would break build when -Werror=unused-result is set. An alternative is to do something like: https://github.com/luizluca/openwrt/blob/a79698fefdd9dacb84865c870bf75aee978c005d/package/libs/elfutils/patches/100 -musl-compat.patch#L51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1857099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.
Since yesterday's update, it is working now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1770176 Title: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange. Status in network-manager package in Ubuntu: Confirmed Bug description: In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour on my Dell XPS 15. This laptop doesn't have an integrated Ethernet port, so I've to use external USB 3.0 Ethernet adapters. When I boot Ubuntu with the adapter plugged in, the wired connection section in the top right menu doesn't show the "Via cavo collegato" section (in Italian, sorry... maybe in English it is "Through connected cable") in the correct way, often but not every time... The menu section title is sometimes " collegato" and expanding the section it doesn't list all the defined Ethernet connection profiles I've on my machine. To access all profiles and to change it I've to select the "Wired network settings" item in the section and so the system settings window appears and all defined profiles are there (so I can change connection by clicking here). Another strange behaviour occours with the "VPN" section in the same topright menu. I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN type). If I select one of this two profiles, VPN connection is established but the switch button in the menu doesn't reflect the state of the connection. To see the correct state of the VPN connection I've to open the "system settings" window, again. It seems there is some trouble in the topright menu communication with the NetworkManager subsystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1770176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.
Some follow-up. My wifi is disabled by default. Even being able to connect to an OpenVPN, the menu is not able to disconnect an OpenVPN connection (as it does not know it was up). As the reporter, I can only see the correct status using gnome setting. There I can enable/disable wifi, list wifi hotspots, connect to them, enable/disable OpenVPN, etc. And there, it also shows the correct visual feedback. The problem is only with the menu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1770176 Title: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange. Status in network-manager package in Ubuntu: Confirmed Bug description: In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour on my Dell XPS 15. This laptop doesn't have an integrated Ethernet port, so I've to use external USB 3.0 Ethernet adapters. When I boot Ubuntu with the adapter plugged in, the wired connection section in the top right menu doesn't show the "Via cavo collegato" section (in Italian, sorry... maybe in English it is "Through connected cable") in the correct way, often but not every time... The menu section title is sometimes " collegato" and expanding the section it doesn't list all the defined Ethernet connection profiles I've on my machine. To access all profiles and to change it I've to select the "Wired network settings" item in the section and so the system settings window appears and all defined profiles are there (so I can change connection by clicking here). Another strange behaviour occours with the "VPN" section in the same topright menu. I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN type). If I select one of this two profiles, VPN connection is established but the switch button in the menu doesn't reflect the state of the connection. To see the correct state of the VPN connection I've to open the "system settings" window, again. It seems there is some trouble in the topright menu communication with the NetworkManager subsystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1770176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.
Same here. I'm using lang pt_BR. I upgraded from 17.10. There is no text in the gnome top menu item which open the wired connections. Translation issues? The menu does not list any wireless settings/connection as if I had no wireless adapter. I do and it list and works when I use nmcli. OpenVPN items list correctly. When I click on any connection, it does connect correctly. However, the switch button in gnome menu is never on and there is no visual clue that something happened. Again, nmcli is simply correct. Maybe it is related to OpenVPN presence? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1770176 Title: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange. Status in network-manager package in Ubuntu: Confirmed Bug description: In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour on my Dell XPS 15. This laptop doesn't have an integrated Ethernet port, so I've to use external USB 3.0 Ethernet adapters. When I boot Ubuntu with the adapter plugged in, the wired connection section in the top right menu doesn't show the "Via cavo collegato" section (in Italian, sorry... maybe in English it is "Through connected cable") in the correct way, often but not every time... The menu section title is sometimes " collegato" and expanding the section it doesn't list all the defined Ethernet connection profiles I've on my machine. To access all profiles and to change it I've to select the "Wired network settings" item in the section and so the system settings window appears and all defined profiles are there (so I can change connection by clicking here). Another strange behaviour occours with the "VPN" section in the same topright menu. I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN type). If I select one of this two profiles, VPN connection is established but the switch button in the menu doesn't reflect the state of the connection. To see the correct state of the VPN connection I've to open the "system settings" window, again. It seems there is some trouble in the topright menu communication with the NetworkManager subsystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1770176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599360] Re: wireless device is detected as wired on boot
** Changed in: network-manager (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1599360 Title: wireless device is detected as wired on boot Status in network-manager package in Ubuntu: Fix Released Bug description: Hello, On every boot since install, my wireless card is listed on network manager as a wired one. If I switch it on and off, it is correctly detected. It is a vintage asus eeepc 701 with a atheros wireless. This is an example of rfkill after switch wireless off and on using keyboard shortcut: luizluca@brinquedinho:~$ rfkill list 0: eeepc-wlan: Wireless LAN Soft blocked: no Hard blocked: no luizluca@brinquedinho:~$ rfkill list 0: eeepc-wlan: Wireless LAN Soft blocked: no Hard blocked: no 4: phy3: Wireless LAN Soft blocked: yes Hard blocked: no ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: Unity Date: Wed Jul 6 01:08:59 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.3.1 dev wlp1s0 proto static metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.3.0/24 dev wlp1s0 proto kernel scope link src 192.168.3.11 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected/org/freedesktop/NetworkManager/Devices/5 PB1202 2267e91b4-d9c8-4670-92ce-c966b289cb52 /org/freedesktop/NetworkManager/ActiveConnection/1 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- 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/ubuntu/+source/network-manager/+bug/1599360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599360] [NEW] wireless device is detected as wired on boot
Public bug reported: Hello, On every boot since install, my wireless card is listed on network manager as a wired one. If I switch it on and off, it is correctly detected. It is a vintage asus eeepc 701 with a atheros wireless. This is an example of rfkill after switch wireless off and on using keyboard shortcut: luizluca@brinquedinho:~$ rfkill list 0: eeepc-wlan: Wireless LAN Soft blocked: no Hard blocked: no luizluca@brinquedinho:~$ rfkill list 0: eeepc-wlan: Wireless LAN Soft blocked: no Hard blocked: no 4: phy3: Wireless LAN Soft blocked: yes Hard blocked: no ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: Unity Date: Wed Jul 6 01:08:59 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.3.1 dev wlp1s0 proto static metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.3.0/24 dev wlp1s0 proto kernel scope link src 192.168.3.11 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected/org/freedesktop/NetworkManager/Devices/5 PB1202 2267e91b4-d9c8-4670-92ce-c966b289cb52 /org/freedesktop/NetworkManager/ActiveConnection/1 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- 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'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1599360 Title: wireless device is detected as wired on boot Status in network-manager package in Ubuntu: New Bug description: Hello, On every boot since install, my wireless card is listed on network manager as a wired one. If I switch it on and off, it is correctly detected. It is a vintage asus eeepc 701 with a atheros wireless. This is an example of rfkill after switch wireless off and on using keyboard shortcut: luizluca@brinquedinho:~$ rfkill list 0: eeepc-wlan: Wireless LAN Soft blocked: no Hard blocked: no luizluca@brinquedinho:~$ rfkill list 0: eeepc-wlan: Wireless LAN Soft blocked: no Hard blocked: no 4: phy3: Wireless LAN Soft blocked: yes Hard blocked: no ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: Unity Date: Wed Jul 6 01:08:59 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.3.1 dev wlp1s0 proto static metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.3.0/24 dev wlp1s0 proto kernel scope link src 192.168.3.11 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected/org/freedesktop/NetworkManager/Devices/5 PB1202 2267e91b4-d9c8-4670-92ce-c966b289cb52 /org/freedesktop/NetworkManager/ActiveConnection/1 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- 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:
[Touch-packages] [Bug 1599357] [NEW] WARN_ON(!encoder->crtc), more warnings and unstable X on 16.04
Public bug reported: Hello, I installed ubuntu 16.04 on the vintage asus eeepc 701. However, i915 is giving me warnings on dmesg and it is unstable, specially on vt-switch (I cannot go back to X). I'll attach what dmesg shows me. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 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: Wed Jul 6 00:52:20 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 915GM/GMS/910GML Express Graphics Controller [1043:82d9] Subsystem: ASUSTeK Computer Inc. Mobile 915GM/GMS/910GML Express Graphics Controller [1043:82d9] MachineType: ASUSTeK Computer INC. 701 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-28-generic root=UUID=88e47f5f-2717-42af-a83c-05a041cf9895 ro rootflags=subvol=@ quiet splash forcepae vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0910 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 701 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0910:bd03/03/2008:svnASUSTeKComputerINC.:pn701:pvrx.x:rvnASUSTeKComputerINC.:rn701:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 701 dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jul 6 00:20:43 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial ** Attachment added: "dmesg "cut here" messages" https://bugs.launchpad.net/bugs/1599357/+attachment/4696130/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1599357 Title: WARN_ON(!encoder->crtc), more warnings and unstable X on 16.04 Status in xorg package in Ubuntu: New Bug description: Hello, I installed ubuntu 16.04 on the vintage asus eeepc 701. However, i915 is giving me warnings on dmesg and it is unstable, specially on vt-switch (I cannot go back to X). I'll attach what dmesg shows me. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 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: Wed Jul 6 00:52:20 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 915GM/GMS/910GML Express Graphics Controller [1043:82d9] Subsystem: ASUSTeK Computer Inc. Mobile 915GM/GMS/910GML Express Graphics Controller [1043:82d9] MachineType: ASUSTeK Computer INC. 701 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-28-generic root=UUID=88e47f5f-2717-42af-a83c-05a041cf9895 ro rootflags=subvol=@ quiet splash forcepae vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably
