[Touch-packages] [Bug 1846702] [NEW] wifi
Public bug reported: Bonjour, je ne parvient pas à installer la wifi sur mon ordinateur ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Fri Oct 4 11:44:45 2019 DistUpgraded: 2019-03-02 13:28:53,256 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:124d] InstallationDate: Installed on 2019-01-25 (251 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: ASUSTeK COMPUTER INC. X550CA ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=d60ac68b-590e-48c4-b2a0-9ec3efa253d7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-02 (215 days ago) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Mar 2 11:26:17 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1846702 Title: wifi Status in xorg package in Ubuntu: New Bug description: Bonjour, je ne parvient pas à installer la wifi sur mon ordinateur ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Fri Oct 4 11:44:45 2019 DistUpgraded: 2019-03-02 13:28:53,256 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:124d] InstallationDate: Installed on 2019-01-25 (251 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: ASUSTeK COMPUTER INC. X550CA ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=d60ac68b-590e-48c4-b2a0-9ec3efa253d7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-02 (215 days ago) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CA
[Touch-packages] [Bug 1719445] [NEW] package libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h usr/include/X11
Public bug reported: I don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h usr/include/X11/Xutil.h] ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 AptOrdering: libx11-dev: Install libx11-dev: Configure libx11-dev: Configure NULL: ConfigurePending 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 Date: Mon Sep 25 22:30:49 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-36-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) broadcom-sta, 6.30.223.271, 4.4.0-59-generic, x86_64: installed DpkgHistoryLog: Start-Date: 2017-09-25 22:30:48 Commandline: apt-get -f install Requested-By: adrien (1000) Upgrade: libx11-dev:i386 (2:1.4.99.1-0ubuntu2.3, 2:1.6.3-1ubuntu2) DpkgLog: 2017-09-25 22:30:48 startup archives unpack 2017-09-25 22:30:49 upgrade libx11-dev:i386 2:1.4.99.1-0ubuntu2.3 2:1.6.3-1ubuntu2 2017-09-25 22:30:49 status half-installed libx11-dev:i386 2:1.4.99.1-0ubuntu2.3 2017-09-25 22:30:49 status unpacked libx11-dev:i386 2:1.4.99.1-0ubuntu2.3 DpkgTerminalLog: Preparing to unpack .../libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb ... Unpacking libx11-dev:i386 (2:1.6.3-1ubuntu2) over (2:1.4.99.1-0ubuntu2.3) ... dpkg: error processing archive /var/cache/apt/archives/libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb (--unpack): trying to overwrite shared '/usr/include/X11/Xcms.h', which is different from other instances of package libx11-dev:i386 DuplicateSignature: package:libx11-dev:2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h usr/include/X11/Xutil.h] Unpacking libx11-dev:i386 (2:1.6.3-1ubuntu2) over (2:1.4.99.1-0ubuntu2.3) ... dpkg: error processing archive /var/cache/apt/archives/libx11-dev_2%3a1.6.3-1ubuntu2_i386.deb (--unpack): trying to overwrite shared '/usr/include/X11/Xcms.h', which is different from other instances of package libx11-dev:i386 ErrorMessage: trying to overwrite shared '/usr/include/X11/Xcms.h', which is different from other instances of package libx11-dev:i386 GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Broadwell-U Integrated Graphics [1179:f840] InstallationDate: Installed on 2016-09-03 (387 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: TOSHIBA Satellite C55-C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=5a16cdbd-726a-45b9-944a-6b66f4f8e612 ro quiet splash radeon.audio=1 vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: libx11 Title: package libx11-dev 2:1.6.3-1ubuntu2 [modified: usr/include/X11/Xcms.h usr/include/X11/Xlibint.h usr/include/X11/Xlocale.h usr/include/X11/Xregion.h usr/include/X11/Xutil.h] failed to install/upgrade: trying to overwrite shared '/usr/include/X11/Xcms.h', which is different from other instances of package libx11-dev:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 5.10 dmi.board.name: 06F2 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr5.10:bd09/11/2015:svnTOSHIBA:pnSatelliteC55-C:pvrPSCPJU-00R011:rvnFF50:rn06F2:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C55-C dmi.product.version: PSCPJU-00R011 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime:
[Touch-packages] [Bug 1718729] [NEW] Black screen with a few white pixels on Virtualbox VM
Public bug reported: I installed Ubuntu 17.04 from a daily image downloaded yesterday in a Virtualbox VM (Host Ubuntu version is 17.04). The installation works fine and without any issues. However, when I install all the updates and reboot, I am no longer able to log in. GDM doesn't start. Instead, I see a completely black screen with a few (one or two) white pixels. I am still able to SSH into the installation after this. Steps to reproduce: * Create a Virtualbox VM * Install Ubuntu 17.10 from daily image (I downloaded mine on 9/20/2017 @ 12:49pm Eastern) * Install all updates (sudo apt-get update && sudo apt-get dist-upgrade) * Reboot ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Thu Sep 21 12:11:34 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-09-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=17aae2c8-ba3d-4c56-92cc-ab06d2c85d68 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful corruption regression reproducible ubuntu -- 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/1718729 Title: Black screen with a few white pixels on Virtualbox VM Status in xorg package in Ubuntu: New Bug description: I installed Ubuntu 17.04 from a daily image downloaded yesterday in a Virtualbox VM (Host Ubuntu version is 17.04). The installation works fine and without any issues. However, when I install all the updates and reboot, I am no longer able to log in. GDM doesn't start. Instead, I see a completely black screen with a few (one or two) white pixels. I am still able to SSH into the installation after this. Steps to reproduce: * Create a Virtualbox VM * Install Ubuntu 17.10 from daily image (I downloaded mine on 9/20/2017 @ 12:49pm Eastern) * Install all updates (sudo apt-get update && sudo apt-get dist-upgrade) * Reboot ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Thu Sep 21 12:11:34 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-09-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=17aae2c8-ba3d-4c56-92cc-ab06d2c85d68 ro quiet splash SourcePackage: xorg Symptom: display
[Touch-packages] [Bug 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable
In my case, I am also using keepassxc. But I'm using the AppImage version rather than the Snap package. (The Snap version doesn't seem to be able to display a status/tray icon, while the AppImage version does). It's possible keepassxc is related, or it's a coincidence. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: alt + left/right arrows switch between tty consoles, cannot disable Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+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 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable
I run into this problem every now and then. I am not sure what causes it. At the moment, this is not happening. I press ALT+Left/Right with no issue. But at some point this bug seems to appear. It's frustrating because ALT+Left in Firefox, for example, is a keyboard shortcut I use to go back a page. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: alt + left/right arrows switch between tty consoles, cannot disable Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+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 1589401] Re: cannot view wifi networks after re-enabling wifi
Network Manager is the culprit, not anyone's routers. This is evident by the fact that earlier versions of Ubuntu didn't experience this issue, this issue happens regardless of which router we're connecting to, it happens regardless of which location we are at, and the underlying issue is that Network Manager cannot see ANY access points, not just the one we normally connect to. There is literally no scenario in which it is someone's router that is causing this. -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1589401] Re: cannot view wifi networks after re-enabling wifi
Why do that? This is a bug with Network Manager, not our routers. -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1589401] Re: cannot view wifi networks after re-enabling wifi
Again, you shouldn't need to restart network manager or the applet. You can simply rescan your wireless networks manually. sudo iwlist scan The applet should be doing this as soon as the machine wakes up, but it's clearly not. -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
I still run into this problem from time to time. On my end, I resolve it by running the following command: sudo iwlist [wifi interface] scan Once I did that, it immediately connected. I'm under the impression that when resuming from suspend, Network Manager isn't automatically scanning for access points. -- 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/1636282 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks Status in network-manager package in Ubuntu: Confirmed Bug description: As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm creating my own bug report. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy network-manager network-manager: Installiert: 1.2.2-0ubuntu0.16.04.3 Installationskandidat: 1.2.2-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.2-0ubuntu0.16.04.3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi icon anytime while being connected to my WiFi network. Also, I expect to see all the WiFi networks around me (at least one other network with good reception and about 3 with bad reception). 4) What happened instead After waking up the laptop from suspend, there appears the ethernet icon (arrow symbols) instead of the WiFi icon. Also, in this state there are no other WiFi networks visible in the network-manager. However, the laptop is still connected with my WiFi and the connection works as usual. Using "service network-manager restart" in the console I can get the wireless icon back and all the other networks around me are visible again. This can be reproduced anytime and with 100% "success rate". The problem appeared with Ubuntu 16.10 and was persistent since. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 20:06:09 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.244 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 wlo1wifi connected/org/freedesktop/NetworkManager/Devices/2 WiNet 2 162de978-4466-46b0-957b-5f9c141d702a /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+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 1496163] Re: i915 firmware is not copied to initrd
Yep, that's good. Thanks! ** Tags added: verification-done ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1496163 Title: i915 firmware is not copied to initrd Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: Fix Committed Status in initramfs-tools source package in Vivid: Won't Fix Status in initramfs-tools source package in Wily: Fix Released Bug description: [ Impact ] On Skylake, skl_dmc firmware is not incorporated into the initramfs. This is because it is a symlink to a versioned blob and the initramfs- tools hook does not dereference symlinks. As the driver is actually loaded from the initramfs, the firmware is missing for the lifetime of the boot, which means that the GPU cannot enter its lowest available power states plus some hotplugging scenarios are broken. This all manifests itself as such in dmesg: [0.728803] i915 :00:02.0: Direct firmware load for i915/skl_dmc_ver1.bin failed with error -2 [0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to load firmware i915/skl_dmc_ver1.bin (0) [ Test Case ] After the fix has been applied and the initrd regenerates, the firmware should load successfully after a reboot. [ Regression Potential ] Unlikely, as the fix is part of Ubuntu since Wily. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1496163/+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 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
Any idea when this will be released to Trusty? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 Status in cryptsetup package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Status in cryptsetup source package in Trusty: Invalid Status in initramfs-tools source package in Trusty: Fix Committed Status in cryptsetup source package in Vivid: Invalid Status in initramfs-tools source package in Vivid: Won't Fix Bug description: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more severe error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. [Test case] 1. On an affected system boot into kernel 3.19.0-30 [Solution] The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a real solution). PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+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 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
i915 drivers are now in the initramfs, as required. ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 Status in cryptsetup package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Status in cryptsetup source package in Trusty: Invalid Status in initramfs-tools source package in Trusty: Fix Committed Status in cryptsetup source package in Vivid: Invalid Status in initramfs-tools source package in Vivid: Won't Fix Bug description: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more severe error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. [Test case] 1. On an affected system boot into kernel 3.19.0-30 [Solution] The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a real solution). PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+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 1642704] Re: initramfs-tools on Trusty doesn't handle symlinks in newer linux-firmware packages correctly
*** This bug is a duplicate of bug 1496163 *** https://bugs.launchpad.net/bugs/1496163 This duplicate mark is true, but that bug isn't gaining much traction. We really need this fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1642704 Title: initramfs-tools on Trusty doesn't handle symlinks in newer linux- firmware packages correctly Status in initramfs-tools package in Ubuntu: Confirmed Bug description: $ update-initramfs -k 4.4.0-47-generic -c update-initramfs: Generating /boot/initrd.img-4.4.0-47-generic $ sudo cat /boot/initrd.img-4.4.0-47-generic |unxz |cpio -i --no-absolute-filenames 185780 blocks $ ls lib/firmware/i915/ $ ls /lib/firmware/i915/ bxt_dmc_ver1_04.bin bxt_dmc_ver1.bin@skl_dmc_ver1.bin@ skl_guc_ver4_3.bin bxt_dmc_ver1_05.bin skl_dmc_ver1_23.bin skl_guc_ver1_1059.bin skl_guc_ver4.bin@ bxt_dmc_ver1_06.bin skl_dmc_ver1_26.bin skl_guc_ver1.bin@ $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642704/+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 1642707] Re: initramfs-tools on Trusty doesn't include i915_bpo.ko
*** This bug is a duplicate of bug 1500751 *** https://bugs.launchpad.net/bugs/1500751 Checked, and this is fixed in the version in -proposed- from that bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1642707 Title: initramfs-tools on Trusty doesn't include i915_bpo.ko Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: New Bug description: initramfs-tools on Trusty doesn't include i915_bpo.ko, causing problems on Skylake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642707/+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 1642707] Re: initramfs-tools on Trusty doesn't include i915_bpo.ko
*** This bug is a duplicate of bug 1500751 *** https://bugs.launchpad.net/bugs/1500751 Trusty is the one I care about, not Zesty. What does a "test case" mean in detail? Happy to help, I just want to know exactly what I need to do. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1642707 Title: initramfs-tools on Trusty doesn't include i915_bpo.ko Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: New Bug description: initramfs-tools on Trusty doesn't include i915_bpo.ko, causing problems on Skylake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642707/+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 1496163] Re: i915 firmware is not copied to initrd
Hi guys, This is still biting us. Can we please have this fixed? See LP #1642704 for details. The fix is one character. Justin -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1496163 Title: i915 firmware is not copied to initrd Status in Skylinux: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: In Progress Status in initramfs-tools source package in Vivid: In Progress Status in initramfs-tools source package in Wily: Fix Released Bug description: On Skylake, the skl_dmc firmware is failing to load. From dmesg: [0.728803] i915 :00:02.0: Direct firmware load for i915/skl_dmc_ver1.bin failed with error -2 [0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to load firmware i915/skl_dmc_ver1.bin (0) This means the GPU can't enter its lowest available power states, plus many display hotplugging scenarios (that only the skl_dmc firmware can handle) are broken. On a whim I tried some other firmware versions: 1) pointed the skl_dmc_ver1.bin symlink to skl_dmc_ver1_18.bin (instead of skl_dmc_ver1_19.bin) 2) downloaded the latest (skl_dmc_ver1_21.bin) and pointed the skl_dmc_ver1.bin symlink to it But neither corrected the situation. Thanks! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-10-generic 4.2.0-10.11 ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem1251 F pulseaudio CurrentDesktop: Unity Date: Tue Sep 15 16:21:24 2015 HibernationDevice: RESUME=UUID=637df075-0afa-420f-a3ca-342be8bf297f IwConfig: enp4s0no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:0833 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 004: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-10-generic root=UUID=f967534a-9cc3-4d1a-a7f3-72d28959e3c6 ro i915.verbose_state_checks=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-10-generic N/A linux-backports-modules-4.2.0-10-generic N/A linux-firmware1.147 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: Default string dmi.board.name: Z170-P D3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd08/19/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-PD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1496163/+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 1447756] Re: [SRU] segfault in log.c code causes phone reboot loops
Not really. The bug is hugely intermittent as it stands.
However, I can confirm we're experiencing this on our fleet.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
[SRU] segfault in log.c code causes phone reboot loops
Status in Canonical System Image:
Fix Released
Status in upstart :
Fix Committed
Status in upstart package in Ubuntu:
Fix Released
Status in upstart source package in Utopic:
Won't Fix
Status in upstart source package in Vivid:
Won't Fix
Status in upstart source package in Wily:
Fix Released
Status in upstart package in Ubuntu RTM:
Fix Released
Bug description:
= Summary =
The version of Upstart in vivid is affected by a coule of bugs relating
to the flushing data from early-boot jobs to disk which can both result
in a crash:
== Problem 1 ==
An internal list is mishandled meaning a crash could occur randomly.
== Problem 2 ==
Jobs which spawn processes in the background then themselves exit can
cause a crash due.
= Explanation of how Upstart flushes early job output =
If an Upstart job starts *and ends* early in the boot sequence (before
the log partition is mounted and writable) and produces output to its
stdout/stderr, Upstart will cache the output for later flushing by
adding the 'Log' object associated with the 'Job' to a list.
When the log partition is mounted writable, the
/etc/init/flush-early-job-log.conf job is run which calls "initctl
notify-disk-writeable". This is a signal to Upstart to flush its cache
of early-boot job output which takes the form of iterating the
'log_unflushed_files' list and flushing all the 'Log' entries to disk.
= Code Specifics =
There are 2 issues (note that the numbers used below match those used in
the Summary).
== Problem 1 detail ==
Due to a bug in the way the 'log_unflushed_files' list is handled (the
'Log' cannot be added to the list directly, so is added via an
intermediary ('NihListElem') node), a crash can result when iterating
the list since the 'Log' is freed, but NOT the intermediary node. The
implication is that it is possible for the intermediary node to be
attempt to dereference already-freed data, resulting in a crash.
== Problem 2 detail ==
If a job spawns a process in the background, then itself exits, that
jobs 'Log' entry will be added to the 'log_unflushed_files' list. But,
if the background process produces output and then exits before Upstart
attempts to flush the original jobs data to disk, the 'NihIo'
corresponding to the log will be serviced automatically and the data
flushed to disk. The problem comes when Upstart receives the
notification to flush the 'log_unflushed_files' list, since that list
now contains an entry which has already been freed (since all its data
has already been flushed). The result is an assertion failure.
= Fix =
== Problem 1 fix ==
Correct the 'log_unflushed_files' list handling by freeing the
'NihListElem' (which will automatically free the 'Log' object), not by
simply freeing the 'Log' object itself.
* Branch: lp:~jamesodhunt/ubuntu/vivid/upstart/bug-1447756/
* New Upstart test added to avoid regression?: Yes.
== Problem 2 fix ==
Correct the assumption that the only entries in the
'log_unflushed_files' list will always have data to flush by checking if
there is in fact any data to flush; if not, remove the entry from the
'log_unflushed_files' list since it has already been handled
automatically by the 'NihIo'.
* Branch: lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix
* New Upstart test added to avoid regression?: Yes.
= Workarounds =
If a system is affected by this bug, it will be manifested by a crash
early in the boot sequence.
To overcome the issue, either:
a) Boot by adding "--no-log" to the kernel command-line.
b) Disable the flush-early-job-log job (assuming the machine is
bootable) by running the following:
$ echo manual | sudo tee -a /etc/init/flush-early-job-log.override
= Impact =
The issue has been present in Upstart since logging was introduced but
no known instances of crashes relating to these problems have been
reported prior to this bug being reported (which relates the the issue
being seen on a very small subset of specific Ubuntu Touch phone
hardware where Upstart is used as the system init daemon).
Note that vivid still uses Upstart for managing the graphical session,
but now uses systemd by default for the system init daemon. Since the session
(Upstart) init does not even require
a flush-early-job-log, the exposure to both the bug and the updated fix
codepath is extremely limited.
= Test Case =
This bug is extremely hard to surface so the approach is simply to
check that the internal list can be iterated correctly by:
1) Booting the system
[Touch-packages] [Bug 1642704] [NEW] initramfs-tools on Trusty doesn't handle symlinks in newer linux-firmware packages correctly
Public bug reported: $ update-initramfs -k 4.4.0-47-generic -c update-initramfs: Generating /boot/initrd.img-4.4.0-47-generic $ sudo cat /boot/initrd.img-4.4.0-47-generic |unxz |cpio -i --no-absolute-filenames 185780 blocks $ ls lib/firmware/i915/ $ ls /lib/firmware/i915/ bxt_dmc_ver1_04.bin bxt_dmc_ver1.bin@skl_dmc_ver1.bin@ skl_guc_ver4_3.bin bxt_dmc_ver1_05.bin skl_dmc_ver1_23.bin skl_guc_ver1_1059.bin skl_guc_ver4.bin@ bxt_dmc_ver1_06.bin skl_dmc_ver1_26.bin skl_guc_ver1.bin@ $ ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1642704 Title: initramfs-tools on Trusty doesn't handle symlinks in newer linux- firmware packages correctly Status in initramfs-tools package in Ubuntu: Confirmed Bug description: $ update-initramfs -k 4.4.0-47-generic -c update-initramfs: Generating /boot/initrd.img-4.4.0-47-generic $ sudo cat /boot/initrd.img-4.4.0-47-generic |unxz |cpio -i --no-absolute-filenames 185780 blocks $ ls lib/firmware/i915/ $ ls /lib/firmware/i915/ bxt_dmc_ver1_04.bin bxt_dmc_ver1.bin@skl_dmc_ver1.bin@ skl_guc_ver4_3.bin bxt_dmc_ver1_05.bin skl_dmc_ver1_23.bin skl_guc_ver1_1059.bin skl_guc_ver4.bin@ bxt_dmc_ver1_06.bin skl_dmc_ver1_26.bin skl_guc_ver1.bin@ $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642704/+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 1642707] Re: initramfs-tools on Trusty doesn't include i915_bpo.ko
Bug is on hooks/framebuffer: add a line "copy_modules_dir kernel/ubuntu/i915" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1642707 Title: initramfs-tools on Trusty doesn't include i915_bpo.ko Status in initramfs-tools package in Ubuntu: Confirmed Bug description: initramfs-tools on Trusty doesn't include i915_bpo.ko, causing problems on Skylake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642707/+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 1642707] [NEW] initramfs-tools on Trusty doesn't include i915_bpo.ko
Public bug reported: initramfs-tools on Trusty doesn't include i915_bpo.ko, causing problems on Skylake ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: trusty ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1642707 Title: initramfs-tools on Trusty doesn't include i915_bpo.ko Status in initramfs-tools package in Ubuntu: Confirmed Bug description: initramfs-tools on Trusty doesn't include i915_bpo.ko, causing problems on Skylake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642707/+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 1589401] Re: cannot view wifi networks after re-enabling wifi
Running 'sudo iw dev wlan0 scan' does work around the issue for me. I have this issue on two computers, they have the following wireless cards from Intel: Intel Wireless 7260 (rev bb) Intel Wireless 7260 (rev 73) Just to be clear, should I be creating a new bug for each of these two cards? Would this be the 'linux' package, or 'iwlwifi'? -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1447756] Re: [SRU] segfault in log.c code causes phone reboot loops
Yep, this is definitely affecting Trusty as well. Is there any chance
the fix will be backported?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
[SRU] segfault in log.c code causes phone reboot loops
Status in Canonical System Image:
Fix Released
Status in upstart :
Fix Committed
Status in upstart package in Ubuntu:
Fix Released
Status in upstart source package in Utopic:
Won't Fix
Status in upstart source package in Vivid:
Won't Fix
Status in upstart source package in Wily:
Fix Released
Status in upstart package in Ubuntu RTM:
Fix Released
Bug description:
= Summary =
The version of Upstart in vivid is affected by a coule of bugs relating
to the flushing data from early-boot jobs to disk which can both result
in a crash:
== Problem 1 ==
An internal list is mishandled meaning a crash could occur randomly.
== Problem 2 ==
Jobs which spawn processes in the background then themselves exit can
cause a crash due.
= Explanation of how Upstart flushes early job output =
If an Upstart job starts *and ends* early in the boot sequence (before
the log partition is mounted and writable) and produces output to its
stdout/stderr, Upstart will cache the output for later flushing by
adding the 'Log' object associated with the 'Job' to a list.
When the log partition is mounted writable, the
/etc/init/flush-early-job-log.conf job is run which calls "initctl
notify-disk-writeable". This is a signal to Upstart to flush its cache
of early-boot job output which takes the form of iterating the
'log_unflushed_files' list and flushing all the 'Log' entries to disk.
= Code Specifics =
There are 2 issues (note that the numbers used below match those used in
the Summary).
== Problem 1 detail ==
Due to a bug in the way the 'log_unflushed_files' list is handled (the
'Log' cannot be added to the list directly, so is added via an
intermediary ('NihListElem') node), a crash can result when iterating
the list since the 'Log' is freed, but NOT the intermediary node. The
implication is that it is possible for the intermediary node to be
attempt to dereference already-freed data, resulting in a crash.
== Problem 2 detail ==
If a job spawns a process in the background, then itself exits, that
jobs 'Log' entry will be added to the 'log_unflushed_files' list. But,
if the background process produces output and then exits before Upstart
attempts to flush the original jobs data to disk, the 'NihIo'
corresponding to the log will be serviced automatically and the data
flushed to disk. The problem comes when Upstart receives the
notification to flush the 'log_unflushed_files' list, since that list
now contains an entry which has already been freed (since all its data
has already been flushed). The result is an assertion failure.
= Fix =
== Problem 1 fix ==
Correct the 'log_unflushed_files' list handling by freeing the
'NihListElem' (which will automatically free the 'Log' object), not by
simply freeing the 'Log' object itself.
* Branch: lp:~jamesodhunt/ubuntu/vivid/upstart/bug-1447756/
* New Upstart test added to avoid regression?: Yes.
== Problem 2 fix ==
Correct the assumption that the only entries in the
'log_unflushed_files' list will always have data to flush by checking if
there is in fact any data to flush; if not, remove the entry from the
'log_unflushed_files' list since it has already been handled
automatically by the 'NihIo'.
* Branch: lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix
* New Upstart test added to avoid regression?: Yes.
= Workarounds =
If a system is affected by this bug, it will be manifested by a crash
early in the boot sequence.
To overcome the issue, either:
a) Boot by adding "--no-log" to the kernel command-line.
b) Disable the flush-early-job-log job (assuming the machine is
bootable) by running the following:
$ echo manual | sudo tee -a /etc/init/flush-early-job-log.override
= Impact =
The issue has been present in Upstart since logging was introduced but
no known instances of crashes relating to these problems have been
reported prior to this bug being reported (which relates the the issue
being seen on a very small subset of specific Ubuntu Touch phone
hardware where Upstart is used as the system init daemon).
Note that vivid still uses Upstart for managing the graphical session,
but now uses systemd by default for the system init daemon. Since the session
(Upstart) init does not even require
a flush-early-job-log, the exposure to both the bug and the updated fix
codepath is extremely limited.
= Test Case =
This bug is extremely hard to surface so the approach is simply to
check that the internal list can be iterated correctly by:
1) Booting the system with upstart
