[Touch-packages] [Bug 1598759] Re: AppArmor nameservice abstraction doesn't allow communication with systemd-resolved
Hello knz, or anyone else affected, Accepted apparmor into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apparmor/2.10.95-4ubuntu5.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: ntp (Ubuntu Yakkety) Importance: High Assignee: Joshua Powers (powersj) Status: Invalid ** Also affects: apparmor (Ubuntu Yakkety) Importance: High Assignee: Tyler Hicks (tyhicks) Status: Triaged ** Changed in: apparmor (Ubuntu Yakkety) Status: Triaged => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1598759 Title: AppArmor nameservice abstraction doesn't allow communication with systemd-resolved Status in AppArmor: In Progress Status in apparmor package in Ubuntu: Fix Committed Status in ntp package in Ubuntu: Invalid Status in apparmor source package in Yakkety: Fix Committed Status in ntp source package in Yakkety: Invalid Bug description: [ Impact ] Processes confined by AppArmor profiles making use of the nameservice AppArmor abstraction are unable to access the systemd-resolved network name resolution service. The nsswitch.conf file shipped in Yakkety puts the nss-resolve plugin to use which talks to systemd-resolved over D-Bus. The D-Bus communication is blocked for the confined processes described above and those processes will fallback to the traditional means of name resolution. [ Test Case ] * Use ntpd to test: $ sudo apt-get install -y ntp ... $ sudo systemctl stop ntp # in another terminal, watch for AppArmor denials $ dmesg -w # in the original terminal, start ntp $ sudo systemctl start ntp # You'll see a number of denials on the system_bus_socket file: audit: type=1400 audit(1476240762.854:35): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=3867 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=126 ouid=0 * Use tcpdump to test: # Capture traffic on whichever network interface you're currently using $ sudo tcpdump -i eth0 # Look in /var/log/syslog for denials on the system_bus_socket file: audit: type=1400 audit(1476240896.021:40): apparmor="DENIED" operation="connect" profile="/usr/sbin/tcpdump" name="/run/dbus/system_bus_socket" pid=4106 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 In both situations, ntpd and tcpdump will seemingly work as expected due to the name resolution fallback configured in nsswitch.conf. However, neither confined process will be using systemd-resolved for name resolution. [ Regression Potential ] This fix will allow ntp, tcpdump, cupsd, dhclient, and other confined- by-default programs to start using systemd-resolved. There is some potential for regression since those applications have not been previously using systemd-resolved. [ Original bug description ] On this plain install of Xenial apparmor complains about ntpd: [ 19.379152] audit: type=1400 audit(1467623330.386:27): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 20.379299] audit: type=1400 audit(1467623331.386:28): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 22.426246] audit: type=1400 audit(146762.434:29): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 22.771326] audit: type=1400 audit(146762.782:30): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 23.568548] audit: type=1400 audit(1467623334.574:31): apparmor="DENIED" operation="connect"
[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
Note: I accepted this into -proposed as 'ip: ether "dev" is duplicate, or "permanent" is garbage' seems to be an unrelated bug. Of course feel free to fix that one as well with a subsequent upload, but this still appears to be an incremental fix as-is. ** Changed in: initramfs-tools (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Changed in: initramfs-tools (Ubuntu Z-series) Status: New => Fix Committed -- 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Yakkety: Fix Committed Status in initramfs-tools source package in z-series: Fix Committed Bug description: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. - The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken - * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
Hello scotte, or anyone else affected, Accepted initramfs-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.122ubuntu8.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: initramfs-tools (Ubuntu Z-series) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Tags added: 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Yakkety: Fix Committed Status in initramfs-tools source package in z-series: Fix Committed Bug description: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. - The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken - * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1631474] Please test proposed package
Hello scotte, or anyone else affected, Accepted initramfs-tools into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.125ubuntu6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Yakkety: Fix Committed Status in initramfs-tools source package in z-series: Fix Committed Bug description: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. - The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken - * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem
+ExecStop=/bin/sh -c 'for f in "$@"; do [ -e "$f" ] || continue; echo "$f existed."; exit 1; done; exit 0' -- /run/initramfs/open-iscsi.interface /run/network/network-root-fs ExecStop=/sbin/ifdown -a --read-environment This will leave networking.service in "failed" state on stop -- *if* you do this hack, then please just put it into the existing ExecStop= line, and simplify this: ExecStop=/bin/sh -c '[ -e /run/initramfs/open-iscsi.interface /run/network/network-root-fs ] || ifdown -a --read-environment' However, this is still a nasty hack. Why would ifdown shut down the interface in the first place? If you use iSCSI, then /e/n/i should *not* have a "dhcp" stanza (and an "auto enXXX) for that interface, but a "manual" one, so that the declaration and behavior don't fight with each other. I. e.: - If ifdown downs a "manual" interface, then let's fix that properly. - If /e/n/i still has a "dhcp" declaration, then drop that (I thought that got fixed ages ago already). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1629972 Title: networking stop incorrectly disconnects from (network) root filesystem Status in MAAS: Triaged Status in ifupdown package in Ubuntu: Confirmed Status in ifupdown source package in Xenial: Confirmed Bug description: With the switch to systemd, all support for iscsi root (and other) filesystems disappeared, since shutdown yanks the rug out from under us. Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i creates..), the DEV check should be expanded to include iscsi devices, and networking.service ExecStop should honor those checks. Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: ipv6 network boot does not work [Impact] With the changes from the above, the iscsi root (at least in the ipv6 case) gets disconneceted prior to clean shutdown (ifdown downs the interface), resulting in a failure to enlist, commission, or deploy cleanly under MAAS. (and a failure to cleanly unmount the root filesystem when it is over iscsi.) [Test Case] Given a MAAS 2.0 installation, and the packages in the other bugs, attempt to enlist, commission, or deploy a host with xenial. [Regression potential] This restores the pre-xenial behavior of not shutting down the interface if there are network drives at the time that neworking is stopped (making it a no-op.) The additional change is to detect "/dev/disk/by-path/*-iscsi-*" as a network disk, replacing the check for the existence of /etc/iscsi/iscsi.initramfs, which was only created by debian-installer (and maas until recently). To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1629972/+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 1589149] Re: the two Hotspots buttons seem to disagree
I confirm on OTA13 on bq e5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1589149 Title: the two Hotspots buttons seem to disagree Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: When i try to activate the hotspot using the menu that you can make appear from above (the black-background one) it seems not to work (no hotspot and no hotspot symbol on the top menu appearing). If I open setting->hotspot, there the hotspot button is deactivated (not green) while the hotspot button in the black menu is green. It seems the button in the Settings if activated can really make the hotspot work (and make the hotspot button in the black menu green) but the hotspot button in the black menu seems to just do nothing (except cutting wifi) On the meizu 4 with ota 11. I think the problem came with ota 11. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1589149/+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 1626935] Re: [Yakkety] desktop in black background on extended HDMI display
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1626935 Title: [Yakkety] desktop in black background on extended HDMI display Status in xorg package in Ubuntu: Confirmed Bug description: Using 16.04 daily image: 20160919(downloading date) With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable Graphic chips: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] [10de:139b] (rev ff) Desktop wallpaper on extended display shows black background only, and the hdmi detection is very unstable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 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: Fri Sep 23 05:30:30 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-09-20 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1626935/+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 1632740] Re: Screen distorts after a period of use, may crash kernel
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High ** Changed in: xorg-server (Ubuntu) Importance: High => Critical -- 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/1632740 Title: Screen distorts after a period of use, may crash kernel Status in xorg-server package in Ubuntu: New Bug description: After using my system for a period of time, usually less than an hour, the screen starts to corrupt. It will vary in intensity, until the system either crashes, or everything goes back to normal for a while. When the system does crash, not even the sysrq-key works. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 16:43:52 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] InstallationDate: Installed on 2016-01-21 (265 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-11 (1 days ago) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 12 16:44:31 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1632740/+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 1626935] Re: [Yakkety] desktop in black background on extended HDMI display
Confirmed. In my case the HDMI display rendered correctly but while plugged in, the desktop on the laptop screen flickered badly (cycling through triple buffers without any glClear()). ** Changed in: xorg (Ubuntu) Importance: Undecided => High -- 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/1626935 Title: [Yakkety] desktop in black background on extended HDMI display Status in xorg package in Ubuntu: Confirmed Bug description: Using 16.04 daily image: 20160919(downloading date) With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable Graphic chips: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] [10de:139b] (rev ff) Desktop wallpaper on extended display shows black background only, and the hdmi detection is very unstable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 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: Fri Sep 23 05:30:30 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-09-20 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1626935/+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 1504698] Re: NetworkManager crashes after reboot
I get this error when upgrading from 15.04 to 15.10 -- 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/1504698 Title: NetworkManager crashes after reboot Status in network-manager package in Ubuntu: Confirmed Bug description: I upgraded my HP Chromebook 14 from 15.04 to 15.10 beta. After cold boot, NetworkManager crashes and I get the popup to send a bug report for a NM crash. There is no network, either. Restarting the NetworkManager service from a terminal fixes the issue ... until next reboot :) ~$ sudo service NetworkManager restart ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Fri Oct 9 16:39:39 2015 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.0.0.1 dev wlan0 proto static metric 600 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.38 metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH wlan0wifi connected /org/freedesktop/NetworkManager/Devices/2 MilanoFamily fbced2d1-aa52-4d01-81dd-9f56594e0911 /org/freedesktop/NetworkManager/ActiveConnection/0 ttyUSB0 gsm disconnected /org/freedesktop/NetworkManager/Devices/3 ------ lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 ------ 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/1504698/+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
Re: [Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Ok, I've found the problem, and reverting this one small change allows all the bluetooth audio hardware I have here to connect and work. For those following along with the technical side, I reverted/removed one hunk from 0502-bluetooth-bluez5-bring-back-SCO-over-PCM- support.patch: @@ -1582,7 +1738,8 @@ static void stop_thread(struct userdata *u) { if (u->transport) { transport_release(u); -u->transport = NULL; +/* Do not set transport pointer to NULL. When failing to switch + * profile NULL u->transport would assert. */ } if (u->sink) { I can only summise that this was relevant for vivid, but work on pulse's bluez5 module between pulse in Vivid and pulse in Xenial improved this situation. As such, I've uploaded a new revision of pulseaudio to my PPA for Xenial, ppa:themuso/ppa, with this hunk reverted. Could everybody affected by *this* bug on Xenial please add my PPA, update to pulseaudio in my Xenial PPA and report back and let me know whether things are working for you. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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
Re: [Touch-packages] [Bug 1608820] Re: Cannot use BT speaker - sink is suspended
Ok, I think I've found the problem... Please update to the latest pulse package from my yakkety PPA, ppa:themuso/ppa. Let me know if it makes a difference. I've re-applied the touch bluez patches, but removed one problematic hunk that was probably needed for vivid, but not for >= xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1608820 Title: Cannot use BT speaker - sink is suspended Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot or resuming from suspend it is possible to connect to a BT speaker but not possible to play anything. Furthermore, if I play a video from youtube, the stream plays fine if the output is the internal speaker, but as soon as I select the BT speaker the stream hangs. It resumes immediately if I switch back to the internal speaker. When I play something over the BT speaker the following lines are logged in the journal: pulseaudio[5340]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile bluetoothd[3230]: /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1: fd(24) ready rtkit-daemon[3950]: Supervising 5 threads of 1 processes of 1 users. rtkit-daemon[3950]: Successfully made thread 28532 of process 5340 (n/a) owned by '1000' RT at priority 5. rtkit-daemon[3950]: Supervising 6 threads of 1 processes of 1 users. pulseaudio[5340]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1 (Operation Not Authorized) kernel: input: B8:69:C2:3D:56:CE as /devices/virtual/input/input26 pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. gnome-session[5383]: ** (zeitgeist-datahub:5874): WARNING **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required wpa_supplicant[3556]: wlan0: WPA: Group rekeying completed with 14:0c:76:71:a1:f4 [GTK=CCMP] pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 2 09:09:18 2016 InstallationDate: Installed on 2013-09-03 (1063 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. UX32VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic.efi.signed root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C4:85:08:A7:45:76 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:3492 acl:70 sco:0 events:137 errors:0 TX bytes:4838 acl:64 sco:0 commands:57 errors:0 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1608820/+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
Re: [Touch-packages] [Bug 1632593] Re: Xorg does not utilize the 3D graphics acceleration capabilities of my device
% apt-cache policy libgbm1-lts-vivid N: Unable to locate package libgbm1-lts-vivid 2016-10-12 23:51 GMT+02:00 Timo Aaltonen : > apt-cache policy > libgbm1-lts-vivid > -- 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/1632593 Title: Xorg does not utilize the 3D graphics acceleration capabilities of my device Status in xorg package in Ubuntu: New Bug description: Everything worked fine in 16.04. I then upgraded to 16.10 a bit early to see if I could find any bugs, and immediately noticed that Unity was running in low-graphics mode, and YouTube chugs noticably. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 09:57:12 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] InstallationDate: Installed on 2016-01-21 (264 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 12 09:59:28 2016 xserver.configfile: default xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: cannot open shared object file: No such file or directory modeset: Failed to load module "glamoregl" (loader failed, 7) modeset(0): Failed to load glamor module. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632593/+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 1574333] Re: LVM-based filesystem does not boot with kernel 4.4 (but works with 4.2)
In case anyone is looking for a (sort of) workaround: a separate non-LVM boot partition (/boot as mountpoint) circumvents the problem. I'm not sure how easy this is to set up on an existing system. I had the luxury of being able to do a clean install without much trouble. Of course, this "workaround" is a bit heavy-handed, and should not be necessary at all, as grub2 supports booting from LVM. But at least it allows having the rest of the root filesystem on LVM volume(s). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1574333 Title: LVM-based filesystem does not boot with kernel 4.4 (but works with 4.2) Status in lvm2 package in Ubuntu: Confirmed Bug description: I‘ve updated my home-made NAS from wily to xenial and it stopped booting. Selecting the 4.2 kernel on the grub menu makes it work again. The working kernel is 4.2.0-35-generic The failing kernel is 4.4.0-21-generic. When the booting sequence freezes, I can have a terminal with the following text : lvmetad is not active yet, using direct activation during sysinit Scannig for Btrfs flesystems _ Actually my set-up is lvm based, and the correponding lines of the output of a mount command are /dev/mapper/clio-root on / type btrfs (rw,relatime,nospace_cache,subvolid=256,subvol=/@) /dev/mapper/clio-root on /mnt/clio-root type btrfs (rw,relatime,nospace_cache,subvolid=5,subvol=/) /dev/mapper/clio-root on /home type btrfs (rw,relatime,nospace_cache,subvolid=257,subvol=/@home) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1574333/+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 1443052] Re: User accounts login history showing incorrect history
Now this is very strange, I restarted my machine, it didn't work. But after restarting it the second time for some reason it started working as it should so I assume that the patch does work, just something odd happened somewhere, but it is all fine now. ** Changed in: accountsservice (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: Triaged Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1632593] Re: Xorg does not utilize the 3D graphics acceleration capabilities of my device
you used 14.04.3 media to install the system, so check 'apt-cache policy libgbm1-lts-vivid' -- 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/1632593 Title: Xorg does not utilize the 3D graphics acceleration capabilities of my device Status in xorg package in Ubuntu: New Bug description: Everything worked fine in 16.04. I then upgraded to 16.10 a bit early to see if I could find any bugs, and immediately noticed that Unity was running in low-graphics mode, and YouTube chugs noticably. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 09:57:12 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] InstallationDate: Installed on 2016-01-21 (264 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 12 09:59:28 2016 xserver.configfile: default xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: cannot open shared object file: No such file or directory modeset: Failed to load module "glamoregl" (loader failed, 7) modeset(0): Failed to load glamor module. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632593/+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 1632593] Re: Xorg does not utilize the 3D graphics acceleration capabilities of my device
Your system was crippled already when it was on 16.04. You probably still have libgbm1-lts-wily or such installed which diverted the lib, because on 14.04.x the original had to be used. xenial-updates has had libgbm1-lts-$foo transitional packages since early august, see bug #1573190 -- 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/1632593 Title: Xorg does not utilize the 3D graphics acceleration capabilities of my device Status in xorg package in Ubuntu: New Bug description: Everything worked fine in 16.04. I then upgraded to 16.10 a bit early to see if I could find any bugs, and immediately noticed that Unity was running in low-graphics mode, and YouTube chugs noticably. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 09:57:12 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] InstallationDate: Installed on 2016-01-21 (264 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 12 09:59:28 2016 xserver.configfile: default xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: cannot open shared object file: No such file or directory modeset: Failed to load module "glamoregl" (loader failed, 7) modeset(0): Failed to load glamor module. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632593/+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 1632593] Re: Xorg does not utilize the 3D graphics acceleration capabilities of my device
the reason why 16.04 worked was that it used the intel X driver which didn't need libgbm1 -- 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/1632593 Title: Xorg does not utilize the 3D graphics acceleration capabilities of my device Status in xorg package in Ubuntu: New Bug description: Everything worked fine in 16.04. I then upgraded to 16.10 a bit early to see if I could find any bugs, and immediately noticed that Unity was running in low-graphics mode, and YouTube chugs noticably. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 09:57:12 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] InstallationDate: Installed on 2016-01-21 (264 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 12 09:59:28 2016 xserver.configfile: default xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: cannot open shared object file: No such file or directory modeset: Failed to load module "glamoregl" (loader failed, 7) modeset(0): Failed to load glamor module. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632593/+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 1632593] Re: Xorg does not utilize the 3D graphics acceleration capabilities of my device
Well, it's certainly a problem which appeared after I did the upgrade. There were no issues before this point. -- 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/1632593 Title: Xorg does not utilize the 3D graphics acceleration capabilities of my device Status in xorg package in Ubuntu: New Bug description: Everything worked fine in 16.04. I then upgraded to 16.10 a bit early to see if I could find any bugs, and immediately noticed that Unity was running in low-graphics mode, and YouTube chugs noticably. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 09:57:12 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] InstallationDate: Installed on 2016-01-21 (264 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 12 09:59:28 2016 xserver.configfile: default xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: cannot open shared object file: No such file or directory modeset: Failed to load module "glamoregl" (loader failed, 7) modeset(0): Failed to load glamor module. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632593/+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 1574333] Re: LVM-based server does not boot with kernel 4.4 (but works with 4.2)
The issue is still present with 4.4.0-42. It's completely preventing me from booting into Ubuntu. The error message is as follows: lvmetad is not active yet, using direct activation during sysinit rootfs: clean, 271911/1831424 files, 1561286/7323648 blocks Here, "rootfs" is my root filesystem (ext4), located on an LVM logical volume. I also tried the following kernels (from http://kernel.ubuntu.com/~kernel-ppa/mainline/) as well: - v4.4.14-xenial (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.14-xenial/) - v4.7.7 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.7/) - v4.8.1 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8.1/) I installed these by booting a live cd and chrooting into the "rootfs" filesystem, and then updating grub. The problem is still present in all of these kernels (with the slight variation that the error message is only shown briefly, and replaced by a blank screen) ** Summary changed: - LVM-based server does not boot with kernel 4.4 (but works with 4.2) + LVM-based filesystem does not boot with kernel 4.4 (but works with 4.2) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1574333 Title: LVM-based filesystem does not boot with kernel 4.4 (but works with 4.2) Status in lvm2 package in Ubuntu: Confirmed Bug description: I‘ve updated my home-made NAS from wily to xenial and it stopped booting. Selecting the 4.2 kernel on the grub menu makes it work again. The working kernel is 4.2.0-35-generic The failing kernel is 4.4.0-21-generic. When the booting sequence freezes, I can have a terminal with the following text : lvmetad is not active yet, using direct activation during sysinit Scannig for Btrfs flesystems _ Actually my set-up is lvm based, and the correponding lines of the output of a mount command are /dev/mapper/clio-root on / type btrfs (rw,relatime,nospace_cache,subvolid=256,subvol=/@) /dev/mapper/clio-root on /mnt/clio-root type btrfs (rw,relatime,nospace_cache,subvolid=5,subvol=/) /dev/mapper/clio-root on /home type btrfs (rw,relatime,nospace_cache,subvolid=257,subvol=/@home) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1574333/+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 1574333] Re: LVM-based filesystem does not boot with kernel 4.4 (but works with 4.2)
I edited the title, as it applies to desktop installs of xenial (such as mine) as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1574333 Title: LVM-based filesystem does not boot with kernel 4.4 (but works with 4.2) Status in lvm2 package in Ubuntu: Confirmed Bug description: I‘ve updated my home-made NAS from wily to xenial and it stopped booting. Selecting the 4.2 kernel on the grub menu makes it work again. The working kernel is 4.2.0-35-generic The failing kernel is 4.4.0-21-generic. When the booting sequence freezes, I can have a terminal with the following text : lvmetad is not active yet, using direct activation during sysinit Scannig for Btrfs flesystems _ Actually my set-up is lvm based, and the correponding lines of the output of a mount command are /dev/mapper/clio-root on / type btrfs (rw,relatime,nospace_cache,subvolid=256,subvol=/@) /dev/mapper/clio-root on /mnt/clio-root type btrfs (rw,relatime,nospace_cache,subvolid=5,subvol=/) /dev/mapper/clio-root on /home type btrfs (rw,relatime,nospace_cache,subvolid=257,subvol=/@home) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1574333/+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 1624922] Re: package sudo 1.8.16-0ubuntu1.2 failed to install/upgrade: subproces pre-removal script geïnstalleerd gaf een foutwaarde 1 terug
*** This bug is a duplicate of bug 1579584 *** https://bugs.launchpad.net/bugs/1579584 ** This bug has been marked a duplicate of bug 1579584 installing guitarpro6 creates a situation where sudo:i386 is scheduled for install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1624922 Title: package sudo 1.8.16-0ubuntu1.2 failed to install/upgrade: subproces pre-removal script geïnstalleerd gaf een foutwaarde 1 terug Status in sudo package in Ubuntu: New Bug description: apt-get install -f ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Sep 18 22:20:32 2016 ErrorMessage: subproces pre-removal script geïnstalleerd gaf een foutwaarde 1 terug InstallationDate: Installed on 2016-09-17 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: sudo Title: package sudo 1.8.16-0ubuntu1.2 failed to install/upgrade: subproces pre-removal script geïnstalleerd gaf een foutwaarde 1 terug UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: ontleden geslaagd /etc/sudoers.d/README: ontleden geslaagd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1624922/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
** No longer affects: unity-scope-click (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Ubuntu File Manager App: Fix Committed Status in address-book-app package in Ubuntu: Fix Committed Status in dialer-app package in Ubuntu: New Status in history-service package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: New Status in indicator-location package in Ubuntu: New Status in indicator-messages package in Ubuntu: New Status in indicator-network package in Ubuntu: New Status in indicator-power package in Ubuntu: New Status in indicator-session package in Ubuntu: New Status in indicator-sound package in Ubuntu: New Status in indicator-transfer package in Ubuntu: New Status in messaging-app package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: Fix Committed Status in ubuntu-terminal-app package in Ubuntu: New Status in ubuntu-touch-session package in Ubuntu: New Status in unity-scope-scopes package in Ubuntu: New Status in unity-scopes-api package in Ubuntu: In Progress Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Status in webbrowser-app package in Ubuntu: In Progress Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1632601] Re: initramfs fails to bring up networking with multiple interfaces, even when an interface is specified
** Tags added: xenial -- 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/1632601 Title: initramfs fails to bring up networking with multiple interfaces, even when an interface is specified Status in initramfs-tools package in Ubuntu: New Bug description: Discovered in Ubuntu 16.04.1 LTS in initramfs-tools version 0.122ubuntu8.3 I expect that, when I set "DEVICE=eth0" in /etc/initramfs- tools/initramfs.conf, my system will bring up DHCP on eth0, and ignore any other interfaces on the system (nothing is plugged into eth1), so that it can bring up dropbear and wait for me to SSH in and unlock my root filesystem. This would also affect anything attempting to netboot with this version of initramfs-tools. Instead, it ignores my DEVICE line, and instead tries and fails to bring up DHCP on a fictional interface called "eth0 eth1". This is caused by _multiple_ bugs in /usr/share/initramfs- tools/scripts/functions. I'd be sending a patch, but I'm not sure where to send it. Here's a detailed breakdown: If the 'ip' bootarg and $IP variable is undefined, then: * It matches the case on line 285 of 'functions': ""|*|on|any|dhcp) * It then matches the 'if' condition on line 288: if ! echo "${IP}" | grep -qc 'BOOTIF'; then * So we execute: DEVICE="${IP#*:*:*:*:*:*}"; It's not at all obvious why that if statement is even there, since if $IP was BOOTIF, it wouldn't match the given case branch. Continuing: * Since $IP was empty, $DEVICE is now empty * Since $DEVICE is empty, on line 295: DEVICE=$(all_netbootable_devices) $DEVICE is now "eth0 eth1", which might be fine, except: * On line 299: for dev in "${DEVICE}"; do This loop would do the right thing -- it would loop through each interface and try it in turn, and stop once one of them was configured successfully -- except that, thanks to that quoting, that 'dev' variable is not set progressively to 'eth0' and then 'eth1'. It is set once, to the string "eth0 eth1". That is clearly not what the rest of the script expects. This is supposed to be the loop where it iterates over 'eth0' and then 'eth1' to decide which of them to set DEVICE to, so the rest of this script can understand the DEVICE variable. But instead, it tries to do silly things like invoke dhclient on a fictional interface called "eth0 eth1", instead of invoking dhclient once on each interface. I don't know how to fix the bug where DEVICE is overridden even if the ip bootarg is absent. Maybe that's the intended behavior? But to at least fix autodetection, someone could just remove the quotes on $DEVICE on line 299. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1632601/+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 1631880] Re: Display error when input wrong SIM code.
Not sure if this is something about how the dialog is done or if it the TextEntry component. On an incorrect pin we do a selectall on the input field and the bubbles should be displayed with the selected text, instead they are drawn where the field would be if the OSK was not also displayed. ** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-system-settings (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-system-settings (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1631880 Title: Display error when input wrong SIM code. Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 446 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-10-10 14:34:11 version version: 446 version ubuntu: 20161008 version device: 20160606-ab415b2 version custom: 20160831-991-38-18 Step: 1. Open System Settings and select Security & Privacy 2. Tap on the SIM PIN item and Tap on the SIM PIN toggle 3. Enter the wrong PIN code and tap on 'Lock' or 'Unlock' as appropriate Actual result: After step 3, two blue circle show on the screen (Please refer to the attachment.) Expect result: No wrong display on screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1631880/+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 1632745] Re: Man page for service is inaccurate since systemd introduction
** Package changed: sysvinit (Ubuntu) => init-system-helpers (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1632745 Title: Man page for service is inaccurate since systemd introduction Status in init-system-helpers package in Ubuntu: New Bug description: The service command man page states that OPTIONS are passed unmodified to the init script. Since the introduction of systemd, service uses a call to systemctl for all basic commands and only uses sysvinit for custom commands. Since systemctl does not allow arguments to be passed to the init script, the man page wrongfully states that arguments are also passed when using basic commands (start, stop, reload...) Man page should be corrected to reflect this behavior or the service command should be modified so it will call sysvinit when arguments are passed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1632745/+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 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem
I've subscribed pitti, in an effort to a.) have him review my changes b.) ask if there is any other way to do this. i've verified in ifupdown source that 'ifdown -a' will ultimately get '/bin/ip link set dev eth0 down' called. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1629972 Title: networking stop incorrectly disconnects from (network) root filesystem Status in MAAS: Triaged Status in ifupdown package in Ubuntu: Confirmed Status in ifupdown source package in Xenial: Confirmed Bug description: With the switch to systemd, all support for iscsi root (and other) filesystems disappeared, since shutdown yanks the rug out from under us. Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i creates..), the DEV check should be expanded to include iscsi devices, and networking.service ExecStop should honor those checks. Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: ipv6 network boot does not work [Impact] With the changes from the above, the iscsi root (at least in the ipv6 case) gets disconneceted prior to clean shutdown (ifdown downs the interface), resulting in a failure to enlist, commission, or deploy cleanly under MAAS. (and a failure to cleanly unmount the root filesystem when it is over iscsi.) [Test Case] Given a MAAS 2.0 installation, and the packages in the other bugs, attempt to enlist, commission, or deploy a host with xenial. [Regression potential] This restores the pre-xenial behavior of not shutting down the interface if there are network drives at the time that neworking is stopped (making it a no-op.) The additional change is to detect "/dev/disk/by-path/*-iscsi-*" as a network disk, replacing the check for the existence of /etc/iscsi/iscsi.initramfs, which was only created by debian-installer (and maas until recently). To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1629972/+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 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem
I have a branch of ifupdown at https://code.launchpad.net/~smoser/ubuntu/+source/ifupdown/+git/ifupdown/+ref/lp-1629972 and just uploaded to https://launchpad.net/~smoser/+archive/ubuntu/ppa It seems to work for me. Please test. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1629972 Title: networking stop incorrectly disconnects from (network) root filesystem Status in MAAS: Triaged Status in ifupdown package in Ubuntu: Confirmed Status in ifupdown source package in Xenial: Confirmed Bug description: With the switch to systemd, all support for iscsi root (and other) filesystems disappeared, since shutdown yanks the rug out from under us. Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i creates..), the DEV check should be expanded to include iscsi devices, and networking.service ExecStop should honor those checks. Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: ipv6 network boot does not work [Impact] With the changes from the above, the iscsi root (at least in the ipv6 case) gets disconneceted prior to clean shutdown (ifdown downs the interface), resulting in a failure to enlist, commission, or deploy cleanly under MAAS. (and a failure to cleanly unmount the root filesystem when it is over iscsi.) [Test Case] Given a MAAS 2.0 installation, and the packages in the other bugs, attempt to enlist, commission, or deploy a host with xenial. [Regression potential] This restores the pre-xenial behavior of not shutting down the interface if there are network drives at the time that neworking is stopped (making it a no-op.) The additional change is to detect "/dev/disk/by-path/*-iscsi-*" as a network disk, replacing the check for the existence of /etc/iscsi/iscsi.initramfs, which was only created by debian-installer (and maas until recently). To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1629972/+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 1443052] Re: User accounts login history showing incorrect history
** Changed in: gnome-control-center (Ubuntu) Status: Fix Released => Confirmed ** Changed in: accountsservice (Ubuntu) Status: Fix Released => Confirmed ** Tags added: yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: Triaged Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1632838] [NEW] /usr/bin/whoopsie:11:__GI___clock_gettime:g_get_monotonic_time:g_main_context_check:g_main_context_iterate:g_main_loop_run
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding whoopsie. This problem was most recently seen with package version 0.2.52, the problem page at https://errors.ubuntu.com/problem/879a5ebae5e297dc1ad837687257ad204af2c4bc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: trusty wily xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1632838 Title: /usr/bin/whoopsie:11:__GI___clock_gettime:g_get_monotonic_time:g_main_context_check:g_main_context_iterate:g_main_loop_run Status in whoopsie package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding whoopsie. This problem was most recently seen with package version 0.2.52, the problem page at https://errors.ubuntu.com/problem/879a5ebae5e297dc1ad837687257ad204af2c4bc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1632838/+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 1632835] [NEW] package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Public bug reported: Referente ao python ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-gobject-2 2.28.6-12ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 10 11:46:09 2016 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-09-26 (15 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.14 SourcePackage: pygobject-2 Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pygobject-2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject-2 in Ubuntu. https://bugs.launchpad.net/bugs/1632835 Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 Status in pygobject-2 package in Ubuntu: New Bug description: Referente ao python ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-gobject-2 2.28.6-12ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 10 11:46:09 2016 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-09-26 (15 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.14 SourcePackage: pygobject-2 Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1632835/+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 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem
** Changed in: ifupdown (Ubuntu) Status: New => Confirmed ** Changed in: ifupdown (Ubuntu) Importance: Undecided => High ** Changed in: ifupdown (Ubuntu Xenial) Status: New => Confirmed ** Changed in: ifupdown (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1629972 Title: networking stop incorrectly disconnects from (network) root filesystem Status in MAAS: Triaged Status in ifupdown package in Ubuntu: Confirmed Status in ifupdown source package in Xenial: Confirmed Bug description: With the switch to systemd, all support for iscsi root (and other) filesystems disappeared, since shutdown yanks the rug out from under us. Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i creates..), the DEV check should be expanded to include iscsi devices, and networking.service ExecStop should honor those checks. Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: ipv6 network boot does not work [Impact] With the changes from the above, the iscsi root (at least in the ipv6 case) gets disconneceted prior to clean shutdown (ifdown downs the interface), resulting in a failure to enlist, commission, or deploy cleanly under MAAS. (and a failure to cleanly unmount the root filesystem when it is over iscsi.) [Test Case] Given a MAAS 2.0 installation, and the packages in the other bugs, attempt to enlist, commission, or deploy a host with xenial. [Regression potential] This restores the pre-xenial behavior of not shutting down the interface if there are network drives at the time that neworking is stopped (making it a no-op.) The additional change is to detect "/dev/disk/by-path/*-iscsi-*" as a network disk, replacing the check for the existence of /etc/iscsi/iscsi.initramfs, which was only created by debian-installer (and maas until recently). To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1629972/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked
** Changed in: canonical-devices-system-image Milestone: backlog => 14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1588526 Title: [mako] Alarm doesn't ring when screen locked Status in Canonical System Image: Incomplete Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1632827] Re: package jackd2 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1632827 Title: package jackd2 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed) Status in jackd2 package in Ubuntu: New Bug description: Installation of jackd2 ran into a problem because it prompts, but, it never showed the prompt when running from the GUI installer. When I installed it with "sudo apt-get install jackd2", then the prompt that came up showed and "Yes" was able to be selected. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 6 22:09:19 2016 ErrorMessage: subprocess installed post-installation script was killed by signal (Killed) InstallationDate: Installed on 2016-10-03 (9 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: jackd2 Title: package jackd2 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1632827/+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 1630014] Re: GPS is unable to find any position
See https://wiki.ubuntu.com/Process/Merges/TestPlan/location- service#Forensics ** Also affects: location-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1630014 Title: GPS is unable to find any position Status in Canonical System Image: New Status in location-service package in Ubuntu: New Bug description: Even if you enable tracking position on Aquaris E 4.5, either with here drive or just with the GPS on, no position is tracked. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630014/+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 1632745] Re: Man page for service is inaccurate since systemd introduction
** Tags added: manpage -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1632745 Title: Man page for service is inaccurate since systemd introduction Status in sysvinit package in Ubuntu: New Bug description: The service command man page states that OPTIONS are passed unmodified to the init script. Since the introduction of systemd, service uses a call to systemctl for all basic commands and only uses sysvinit for custom commands. Since systemctl does not allow arguments to be passed to the init script, the man page wrongfully states that arguments are also passed when using basic commands (start, stop, reload...) Man page should be corrected to reflect this behavior or the service command should be modified so it will call sysvinit when arguments are passed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1632745/+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 1632827] [NEW] package jackd2 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)
Public bug reported: Installation of jackd2 ran into a problem because it prompts, but, it never showed the prompt when running from the GUI installer. When I installed it with "sudo apt-get install jackd2", then the prompt that came up showed and "Yes" was able to be selected. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 6 22:09:19 2016 ErrorMessage: subprocess installed post-installation script was killed by signal (Killed) InstallationDate: Installed on 2016-10-03 (9 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: jackd2 Title: package jackd2 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1632827 Title: package jackd2 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed) Status in jackd2 package in Ubuntu: New Bug description: Installation of jackd2 ran into a problem because it prompts, but, it never showed the prompt when running from the GUI installer. When I installed it with "sudo apt-get install jackd2", then the prompt that came up showed and "Yes" was able to be selected. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 6 22:09:19 2016 ErrorMessage: subprocess installed post-installation script was killed by signal (Killed) InstallationDate: Installed on 2016-10-03 (9 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: jackd2 Title: package jackd2 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1632827/+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 1628306] Re: network booting fails for iscsi root if no ip is set
Regression tracked via bug #1631474 -- 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/1628306 Title: network booting fails for iscsi root if no ip is set Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Released Bug description: [Impact] Remote-root installs (eg. / over iscsi and similar) where the configuration is simple, and no extra parameters are included on the kernel command-line (as opposed to MaaS specifying everything). [Test case] 1) do an installation with /boot on a local disk and / and swap over a remote LUN (iSCSI is simple to do). 2) Update to initramfs-tools with isc-dhcp support. [Regression potential] This is in itself a fix for a regression found in initramfs-tools (0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial). Failure to boot on a remote root filesystem would constitue a regression. -- I did a new install with /boot on /dev/sda, and everything else (/ and swap) on an iSCSI LUN. Booting this with initramfs-tools using ipconfig works without issues. Booting this with initramfs-tools (0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial) fails because no interface is specified. This appears to be because ipconfig interprets "" as meaning to try every interface until one works (or all fail), whereas calling dhclient without an interface name simply returns a failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1628306/+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 1574347] Re: [SRU] Re-read the link type if the name changed
now i'm using ubuntu 16.10 with proposed updates enabled. Network-Manager is at version 1.2.4-0ubuntu1 and seems that the problem is solved thanks -- 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/1574347 Title: [SRU] Re-read the link type if the name changed Status in NetworkManager: Fix Released Status in OEM Priority Project: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released 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 [Testcase] 1. Boot the system. It should include a wireless device. 2. In a terminal, run 'nmcli dev'. 3. In the correct case, the line for the wireless device should read "wifi" under the TYPE column. In a failure case, it will read "ethernet". 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. --- 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. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
Just adding in that there's no change with an upgrade to 16.10 Also, I'm not sure if the link to the Linux Kernel bug is correct as that shows the bug as resolved in Kernels <=3.9-r3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair Status in ALSA driver: Unknown Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Debian: New Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1166529/+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 1626345] Re: After rebooting for updates, reboot is still required.
And the after autoremove log ** Attachment added: "after_history.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4760020/+files/after_history.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After rebooting for updates, reboot is still required. Status in One Hundred Papercuts: Confirmed Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1626345/+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 1626345] Re: After rebooting for updates, reboot is still required.
Brian, Yesterday we had kernel updates. My server, which is set to automatically reboot, reboot fine and no /var/run/reboot-required. This morning there was no second reboot, so everything was as expected. The I ran autoremove to remove the stale kernel. Then I had /var/run/reboot- required and /var/run/reboot-required.pkgs contained linux-base. So I wouldn't think removing a kernel should require a reboot. So is this a bug or am I not understand how this should work? I confirmed this on a second 16.04 server Attached are the /var/log/apt/history.logs from before autoremove and after. ** Attachment added: "before_history.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4760019/+files/before_history.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After rebooting for updates, reboot is still required. Status in One Hundred Papercuts: Confirmed Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1626345/+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 1539896] Re: [enhancement] Support Vulkan
I don't have an official date for Vulkan support but estimate that we are still some months away. We are currently revamping our surface objects for Vulkan and Mesa integration as well as Mir Version 1.0 release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1539896 Title: [enhancement] Support Vulkan Status in Mir: In Progress Status in Ubuntu SDK IDE: Invalid Status in mir package in Ubuntu: Triaged Bug description: full support to the libraries vulkan in mir and in canonical system image. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539896/+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 1632593] Re: Xorg does not utilize the 3D graphics acceleration capabilities of my device
why do you think the bug is there? -- 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/1632593 Title: Xorg does not utilize the 3D graphics acceleration capabilities of my device Status in xorg package in Ubuntu: New Bug description: Everything worked fine in 16.04. I then upgraded to 16.10 a bit early to see if I could find any bugs, and immediately noticed that Unity was running in low-graphics mode, and YouTube chugs noticably. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 09:57:12 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] InstallationDate: Installed on 2016-01-21 (264 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 12 09:59:28 2016 xserver.configfile: default xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: cannot open shared object file: No such file or directory modeset: Failed to load module "glamoregl" (loader failed, 7) modeset(0): Failed to load glamor module. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632593/+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 1628306] Re: network booting fails for iscsi root if no ip is set
(found bug 1631474) -- 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/1628306 Title: network booting fails for iscsi root if no ip is set Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Released Bug description: [Impact] Remote-root installs (eg. / over iscsi and similar) where the configuration is simple, and no extra parameters are included on the kernel command-line (as opposed to MaaS specifying everything). [Test case] 1) do an installation with /boot on a local disk and / and swap over a remote LUN (iSCSI is simple to do). 2) Update to initramfs-tools with isc-dhcp support. [Regression potential] This is in itself a fix for a regression found in initramfs-tools (0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial). Failure to boot on a remote root filesystem would constitue a regression. -- I did a new install with /boot on /dev/sda, and everything else (/ and swap) on an iSCSI LUN. Booting this with initramfs-tools using ipconfig works without issues. Booting this with initramfs-tools (0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial) fails because no interface is specified. This appears to be because ipconfig interprets "" as meaning to try every interface until one works (or all fail), whereas calling dhclient without an interface name simply returns a failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1628306/+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 1628306] Re: network booting fails for iscsi root if no ip is set
lscotte, did you open a 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/1628306 Title: network booting fails for iscsi root if no ip is set Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Released Bug description: [Impact] Remote-root installs (eg. / over iscsi and similar) where the configuration is simple, and no extra parameters are included on the kernel command-line (as opposed to MaaS specifying everything). [Test case] 1) do an installation with /boot on a local disk and / and swap over a remote LUN (iSCSI is simple to do). 2) Update to initramfs-tools with isc-dhcp support. [Regression potential] This is in itself a fix for a regression found in initramfs-tools (0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial). Failure to boot on a remote root filesystem would constitue a regression. -- I did a new install with /boot on /dev/sda, and everything else (/ and swap) on an iSCSI LUN. Booting this with initramfs-tools using ipconfig works without issues. Booting this with initramfs-tools (0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial) fails because no interface is specified. This appears to be because ipconfig interprets "" as meaning to try every interface until one works (or all fail), whereas calling dhclient without an interface name simply returns a failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1628306/+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 1632808] Re: configure_networking exits without any ipv6 routes
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git /initramfs-tools/+ref/lp-1631010 there i added 'ip6=only' and 'ip6=only-S' (we can change the syntax), but '-S' means to pass '-S' to 'dhclient -6'. -- 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/1632808 Title: configure_networking exits without any ipv6 routes Status in MAAS: New Status in initramfs-tools package in Ubuntu: New Bug description: Because DHCPv6 only does addresses, and not routes, configure_networking needs to wait for the kernel to process a router- advertisement before returning claiming an IPv6 config (since all it will have is a /128 and no routes, making for a pretty useless network stack.) See Bug #1609898 for context. (The syntax for ip= should probably also be extended to allow SLAAC configuration. If the user said "dhcp", then we should insist on getting our answer from DHCP.) On the bright side, iscsi retries, so after 1 or more failures to connect, the router-advertisement comes in and the connect succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632808/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
Filed the above 2 issues as (1) Bug #1632804 and (2) Bug #1632808 for yakkety. noting that here because those should be fixed as part of the xenial SRU of this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Released Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in isc-dhcp source package in Xenial: Fix Released Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: Fix Released Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1632767] Re: yakkety: desktop ISO fails to reboot after install: Failed deactivating swap
I saw the same kind of warnings with the Ubuntu GNOME i386 20161012 image when run in GNOME Boxes which I understand is qemu with spice. I just manually power off the VM at that point. ** Description changed: The 20161012.1 yakkety desktop ISO fails to reboot after the install completes (see attached screenshot). Tested on QEMU in BIOS and UEFI mode, which is where the screenshot is from. Same thing is seemingly happening on hardware (reboot hangs), although I don't see this particular debugging output on hardware. - The systemd related logging might be a red haring... I'm not sure this + The systemd related logging might be a red herring... I'm not sure this is actually a systemd bug, just that it seems the correct starting point. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1632767 Title: yakkety: desktop ISO fails to reboot after install: Failed deactivating swap Status in systemd package in Ubuntu: New Bug description: The 20161012.1 yakkety desktop ISO fails to reboot after the install completes (see attached screenshot). Tested on QEMU in BIOS and UEFI mode, which is where the screenshot is from. Same thing is seemingly happening on hardware (reboot hangs), although I don't see this particular debugging output on hardware. The systemd related logging might be a red herring... I'm not sure this is actually a systemd bug, just that it seems the correct starting point. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1632767/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
Attaching a tarbal of everything i have in /var/log, not sure it's useful (not my "ephemeral" environment is read-only with /var/log on a tmpfs, so it's mostly empty). Also here's my exact /proc/cmdline from within the booted ephemeral environment: BOOT_IMAGE=vmlinuz-4.4.0-42-generic initrd=initrd.img-4.4.0-42-generic root=/dev/nfs nfsroot=10.17.76.1:/var/lib/tribble/ephemeral ip=dhcp ro nomodeset net.ifnames=0 BOOTIF=01-80-fa-5b-36-f5-86 ** Attachment added: "log.tgz" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4760012/+files/log.tgz -- 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Confirmed Status in initramfs-tools source package in Yakkety: In Progress Bug description: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. - The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken - * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1632804] Re: ROUNDTTT in configure_networking is effectively ignored
** Also affects: maas Importance: Undecided Status: New ** Tags added: maas-ipv6 -- 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/1632804 Title: ROUNDTTT in configure_networking is effectively ignored Status in MAAS: New Status in initramfs-tools package in Ubuntu: New Bug description: With the changes from Bug #1621507, ROUNDTTT is effectively ignored. The loop checks only for the existence of /run/net-${DEVICE}.conf, and the dhclient scripts ALWAYS (even on failure) create it, it will try to get a lease exactly once before bailing out. Ideally, if both ipv4 and ipv6 are present on the vlan, then both would be configured and (as is done) present in the net-$DEV.conf file. Generally speaking (and why we didn't notice this in testing..), dhclient gets a lease on the first pass. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632804/+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 1632808] [NEW] configure_networking exits without any ipv6 routes
Public bug reported: Because DHCPv6 only does addresses, and not routes, configure_networking needs to wait for the kernel to process a router-advertisement before returning claiming an IPv6 config (since all it will have is a /128 and no routes, making for a pretty useless network stack.) See Bug #1609898 for context. (The syntax for ip= should probably also be extended to allow SLAAC configuration. If the user said "dhcp", then we should insist on getting our answer from DHCP.) On the bright side, iscsi retries, so after 1 or more failures to connect, the router-advertisement comes in and the connect succeeds. ** Affects: maas Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: maas-ipv6 ** Tags added: maas-ipv6 ** Also affects: maas Importance: Undecided Status: New -- 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/1632808 Title: configure_networking exits without any ipv6 routes Status in MAAS: New Status in initramfs-tools package in Ubuntu: New Bug description: Because DHCPv6 only does addresses, and not routes, configure_networking needs to wait for the kernel to process a router- advertisement before returning claiming an IPv6 config (since all it will have is a /128 and no routes, making for a pretty useless network stack.) See Bug #1609898 for context. (The syntax for ip= should probably also be extended to allow SLAAC configuration. If the user said "dhcp", then we should insist on getting our answer from DHCP.) On the bright side, iscsi retries, so after 1 or more failures to connect, the router-advertisement comes in and the connect succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632808/+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 1623294] Re: Black screen on startup after HWE stack update on Ubuntu 14.04 LTS [Radeon R7 graphics]
Possible duplicate of https://launchpad.net/bugs/1600092. -- 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/1623294 Title: Black screen on startup after HWE stack update on Ubuntu 14.04 LTS [Radeon R7 graphics] Status in xorg package in Ubuntu: New Bug description: After updating the HWE stack on Ubuntu 14.04 LTS, my computer now regularly boots to a black screen upon startup. I briefly see the purple screen (but no plymouth), and then nothing. You can hear the ubuntu drum roll, though, and I can reboot using the alt+Sysrq+B option. Adding the nomodeset parameter in GRUB offers a solution of sorts, but the computer boots with Gallium 0.4 on llvmpipe graphics, which makes gaming basically impossible. I can still boot regularly using the 3.16.0-77-generic kernel saved in GRUB. Other info: 1) I tried an Ubuntu live USB stick with both 14.04.5 on it and then 16.04 and got the same problem. 2) My UEFI firmware is up-to-date as of 1 or 2 days ago. 3) The kernel in question is 4.4.0-36-generic. 4) Ubuntu release: 14.04.5 LTS 5) I have never installed the fglrx driver—I have always used the open-source driver. 6) My exact GPU: AMD A10-7700K Radeon R7 (Kaveri). 7) I'm not sure that the dmesg log automatically attached by apport will be helpful because of the "nomodeset" parameter, so I have attached a dmesg log grabbed from a failed boot. With guidance, I can do the same for other relevant logs. Hope that's helpful! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-36.55~14.04.1-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.21 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: Tue Sep 13 21:46:45 2016 DistUpgraded: 2016-08-26 20:07:12,800 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:1313] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:1313] InstallationDate: Installed on 2015-06-24 (447 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=228ea1db-87eb-476d-b97f-5a4a28c618f4 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2016-08-27 (18 days ago) dmi.bios.date: 03/15/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: FM2A78M-HD+ R2.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd03/15/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A78M-HD+R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Sep 13 21:07:07 2016 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.2~trusty3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1623294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-pa
[Touch-packages] [Bug 1632803] [NEW] /usr/bin/whoopsie:11:strip:iconv_open:try_conversion:g_iconv_open:open_converter
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding whoopsie. This problem was most recently seen with package version 0.2.52.1, the problem page at https://errors.ubuntu.com/problem/ab79b8cc4ee25786d26f55868658c95c33a1b9b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1632803 Title: /usr/bin/whoopsie:11:strip:iconv_open:try_conversion:g_iconv_open:open_converter Status in whoopsie package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding whoopsie. This problem was most recently seen with package version 0.2.52.1, the problem page at https://errors.ubuntu.com/problem/ab79b8cc4ee25786d26f55868658c95c33a1b9b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1632803/+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 1632804] [NEW] ROUNDTTT in configure_networking is effectively ignored
Public bug reported: With the changes from Bug #1621507, ROUNDTTT is effectively ignored. The loop checks only for the existence of /run/net-${DEVICE}.conf, and the dhclient scripts ALWAYS (even on failure) create it, it will try to get a lease exactly once before bailing out. Ideally, if both ipv4 and ipv6 are present on the vlan, then both would be configured and (as is done) present in the net-$DEV.conf file. Generally speaking (and why we didn't notice this in testing..), dhclient gets a lease on the first pass. ** Affects: maas Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: maas-ipv6 ** Package changed: klibc (Ubuntu) => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1632804 Title: ROUNDTTT in configure_networking is effectively ignored Status in MAAS: New Status in initramfs-tools package in Ubuntu: New Bug description: With the changes from Bug #1621507, ROUNDTTT is effectively ignored. The loop checks only for the existence of /run/net-${DEVICE}.conf, and the dhclient scripts ALWAYS (even on failure) create it, it will try to get a lease exactly once before bailing out. Ideally, if both ipv4 and ipv6 are present on the vlan, then both would be configured and (as is done) present in the net-$DEV.conf file. Generally speaking (and why we didn't notice this in testing..), dhclient gets a lease on the first pass. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632804/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
After looking into this more (and working on Bug #1629972 some), there are couple of issues with the new configure_networking: 1. since it checks only for the existence of /run/net-${DEVICE}.conf, and the dhclient scripts ALWAYS (even on failure) create it, it will try to get a lease exactly once before bailing out. Ideally, if both ipv4 and ipv6 are present on the vlan, then both would be configured and (as is done) present in the net-$DEV.conf file. 2. Since router-advertisements are needed for the on-link indication (and routes), ipv6 configuration via dhcp should wait until such time as there is at least a (non-fe80) route for some ipv6 cidr on $DEVICE (which RA should create). This will eliminate the iscsi-timeout errors that we see when configure_networking() returns before RA configures routing. Note that a default route is not necessary. Note also that it should timeout on the RA if it doesn't show up in a reasonable time, complain that it got no RA, and then _not_ bring up ipv6 on the interface (RA is required, as per Bug #1609898) ** Tags removed: verification-pending ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Released Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in isc-dhcp source package in Xenial: Fix Released Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: Fix Released Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1632745] Re: Man page for service is inaccurate since systemd introduction
** Package changed: ubuntu => sysvinit (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1632745 Title: Man page for service is inaccurate since systemd introduction Status in sysvinit package in Ubuntu: New Bug description: The service command man page states that OPTIONS are passed unmodified to the init script. Since the introduction of systemd, service uses a call to systemctl for all basic commands and only uses sysvinit for custom commands. Since systemctl does not allow arguments to be passed to the init script, the man page wrongfully states that arguments are also passed when using basic commands (start, stop, reload...) Man page should be corrected to reflect this behavior or the service command should be modified so it will call sysvinit when arguments are passed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1632745/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
@chiluk - I tested the latest package in your PPA, but something seems slightly wonky for my use case. Networking seems to come up correctly, but it takes longer than it should and I see warnings like this repeated several times: ip: ether "dev" is duplicate, or "permanent" is garbage -- 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Confirmed Status in initramfs-tools source package in Yakkety: In Progress Bug description: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. - The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken - * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1632745] [NEW] Man page for service is inaccurate since systemd introduction
You have been subscribed to a public bug: The service command man page states that OPTIONS are passed unmodified to the init script. Since the introduction of systemd, service uses a call to systemctl for all basic commands and only uses sysvinit for custom commands. Since systemctl does not allow arguments to be passed to the init script, the man page wrongfully states that arguments are also passed when using basic commands (start, stop, reload...) Man page should be corrected to reflect this behavior or the service command should be modified so it will call sysvinit when arguments are passed. ** Affects: sysvinit (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Man page for service is inaccurate since systemd introduction https://bugs.launchpad.net/bugs/1632745 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. -- 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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
** Description changed: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot. [Other Info] - * There are a number of other issues in this code base that are not solved by this fix. + * There are a number of other issues in this code base that are not solved by this fix. +- The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken +- * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. -- 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Confirmed Status in initramfs-tools source package in Yakkety: In Progress Bug description: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. - The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken - * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
The latest PPA (0.122ubuntu8.3+lp1631474b2) passes verification for me. $ cat /proc/cmdline root=LABEL=cloudimg-rootfs ro console=hvc0 ip=dhcp tsc=reliable $ dpkg -l|grep initramfs-tools ii initramfs-tools 0.122ubuntu8.3+lp1631474b2 all generic modular initramfs generator (automation) ii initramfs-tools-bin 0.122ubuntu8.3+lp1631474b2 amd64 binaries used by initramfs-tools ii initramfs-tools-core 0.122ubuntu8.3+lp1631474b2 all generic modular initramfs generator (core tools) -- 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Confirmed Status in initramfs-tools source package in Yakkety: In Progress Bug description: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1632794] [NEW] ERROR:broker_posix.cc(41)] Invalid node channel message
Public bug reported: Get that error from a terminal when reporting an issue: oem@u64:~$ ubuntu-bug wine-development oem@u64:~$ Created new window in existing browser session. [25397:25441:1012/184132:ERROR:nss_util.cc(809)] After loading Root Certs, loaded==false: NSS error code: -8018 [25513:25513:1012/184132:ERROR:broker_posix.cc(41)] Invalid node channel message ^C oem@u64:~$ ubuntu-bug apport oem@u64:~$ Created new window in existing browser session. [26655:26700:1012/190737:ERROR:nss_util.cc(809)] After loading Root Certs, loaded==false: NSS error code: -8018 note: - chromium-browser 53 is already loaded on a gnome-shell session - the terminal command is ran, and a new tab is opened (as expected) I'm reporting against apport because it happens when i use it; but the problem could be elsewhere: libnss and/or chromium. So i let you decide about the real affected package(s) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apport 2.20.3-0ubuntu8 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CrashReports: 640:1000:123:35535775:2016-10-11 19:40:01.106713771 +0200:2016-10-11 19:40:02.106713771 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash CurrentDesktop: GNOME Date: Wed Oct 12 19:07:20 2016 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1632794 Title: ERROR:broker_posix.cc(41)] Invalid node channel message Status in apport package in Ubuntu: New Bug description: Get that error from a terminal when reporting an issue: oem@u64:~$ ubuntu-bug wine-development oem@u64:~$ Created new window in existing browser session. [25397:25441:1012/184132:ERROR:nss_util.cc(809)] After loading Root Certs, loaded==false: NSS error code: -8018 [25513:25513:1012/184132:ERROR:broker_posix.cc(41)] Invalid node channel message ^C oem@u64:~$ ubuntu-bug apport oem@u64:~$ Created new window in existing browser session. [26655:26700:1012/190737:ERROR:nss_util.cc(809)] After loading Root Certs, loaded==false: NSS error code: -8018 note: - chromium-browser 53 is already loaded on a gnome-shell session - the terminal command is ran, and a new tab is opened (as expected) I'm reporting against apport because it happens when i use it; but the problem could be elsewhere: libnss and/or chromium. So i let you decide about the real affected package(s) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apport 2.20.3-0ubuntu8 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CrashReports: 640:1000:123:35535775:2016-10-11 19:40:01.106713771 +0200:2016-10-11 19:40:02.106713771 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash CurrentDesktop: GNOME Date: Wed Oct 12 19:07:20 2016 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1632794/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
I tested maas's command line as well. /proc/cmdline from a maas pxe boot is BOOT_IMAGE=ubuntu/amd64/hwe-y/yakkety/daily/boot-kernel nomodeset iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily iscsi_target_ip=192.168.1.5 iscsi_target_port=3260 iscsi_initiator=bonusvm2 ip=bonusvm2:BOOTIF ro root=/dev/disk/by-path/ip-192.168.1.5:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily-lun-1 overlayroot=tmpfs cloud-config-url=http://192.168.1.5/MAAS/metadata/latest/by-id/4y3h7t/?op=get_preseed log_host=192.168.1.5 log_port=514 initrd=ubuntu/amd64/hwe-y/yakkety/daily/boot-initrd BOOTIF=01-52-54-00-ca-c0-9e Notable variables are ip=bonusvm2:BOOTIF BOOTIF=01-52-54-00-ca-c0-9e This use case continues to function. -- 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Confirmed Status in initramfs-tools source package in Yakkety: In Progress Bug description: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1631010] Re: please add a cmdline option to chose between ipv4, ipv6, or dual-stack network boot
I put a branch at https://code.launchpad.net/~smoser/ubuntu/+source /initramfs-tools/+git/initramfs-tools/+ref/lp-1631010 with a fix for this. other improvements too: improvements to dhclient handing of ip= command lines. Improvemnts here are: a.) do not leave /run/net-* around if dhclient failed b.) support ip6= on the kernel cmdline ip6= off : default. ip= does not mean to do ipv6 only : only do ipv6 (no ipv4) on : always do ipv6 even if ipv4 succeeded. iff : do ipv6 if and only if ipv4 fails c.) wait for link local address to settle (dad) before attempting to dhcp -6 d.) do not run through the dhcp configure once for each ROUNDTTT -- 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/1631010 Title: please add a cmdline option to chose between ipv4, ipv6, or dual-stack network boot Status in initramfs-tools package in Ubuntu: New Bug description: Right now, I can boot with "ip=hostname:BOOTIF" in the kernel commandline, and (after bug 1621507), I get whatever it came up with for ipv4 and ipv6. If for nothing more than testing on a dual-stack environment, it would be nice to be able to force that to try both (current behavior, and an excellent default), only try IPv4, or only IPv6. NOT something that needs to be fixed before yakkety, but would be nice to eventually get back to xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631010/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
** Description changed: [Impact] - * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed + * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp - * Regression-updates + * Regression-updates - * The fix better parses the ip= command line argument. + * The fix better parses the ip= command line argument. [Test Case] - * Create a machine that boots using an nfsroot. + * Create a machine that boots using an nfsroot. - * Use ip=:eth0:dhcp on the kernel command line. To set up -networking. + * Use ip=:eth0:dhcp on the kernel command line. To set up + networking. - * Discover that the device never comes up because, networking is not - conifgured correctly. + * Discover that the device never comes up because, networking is not + configured correctly. [Regression Potential] - * Regressions potential is limited to machines using + * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is - already broken regression potential is minimal. + already broken regression potential is minimal. This is common on + machines that use nfsroot or otherwise pxe boot. [Other Info] - - * There are a number of other issues in this code base that are not solved by this fix. - * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. + + * There are a number of other issues in this code base that are not solved by this fix. + * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. -- 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Confirmed Status in initramfs-tools source package in Yakkety: In Progress Bug description: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Pos
[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
** Also affects: initramfs-tools (Ubuntu Yakkety) Importance: High Assignee: Dave Chiluk (chiluk) Status: In Progress -- 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Confirmed Status in initramfs-tools source package in Yakkety: In Progress Bug description: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
I have uploaded a new version of initramfs-tools to my ppa, I would again appreciate testing on this. Notably I fixed an bug that was causing all_netbootable_devices to be tried instead of the interface specified on the command line. I also now handle the case where ip=:bootif , which really shouldn't be a concern to most. I still think ip=bootif might fail *(if /run/net-${DEVICE}.conf does not exist), but as this is an anaconda use case and not a mainline kernel use case I'll ignore it for the purpose of the SRU. -- 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Confirmed Bug description: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1539896] Re: [enhancement] Support Vulkan
? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1539896 Title: [enhancement] Support Vulkan Status in Mir: In Progress Status in Ubuntu SDK IDE: Invalid Status in mir package in Ubuntu: Triaged Bug description: full support to the libraries vulkan in mir and in canonical system image. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539896/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
** Patch added: "lp1631474.yakkety.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4759968/+files/lp1631474.yakkety.debdiff -- 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Confirmed Bug description: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not conifgured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
Updated debdiff to handle ip=:bootif use case. ** Patch added: "lp1631474.xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4759967/+files/lp1631474.xenial.debdiff -- 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Confirmed Bug description: [Impact] * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:eth0:dhcp * Regression-updates * The fix better parses the ip= command line argument. [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not conifgured correctly. [Regression Potential] * Regressions potential is limited to machines using ip={""|*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1632766] Re: time in lxc ubuntu template
After a talk with stgraber, this is a due to the fact that the Ubuntu LXC I build are using a pre-generated image which uses UTC by default. If you want to change the time on Xenial, in my case date command or other technic didn't have positive impact. The only thing that work so far is to unlink /etc/localtime and link it to the desired zone. example : #ls -altr /etc/localtime lrwxrwxrwx 1 root root 27 Oct 12 15:59 /etc/localtime -> /usr/share/zoneinfo/Etc/UTC # unlink /etc/localtime # ls -altr /etc/localtime ls: cannot access '/etc/localtime': No such file or directory # ln -s /usr/share/zoneinfo/America/Toronto /etc/localtime # ls -altr /etc/localtime lrwxrwxrwx 1 root root 35 Oct 12 12:05 /etc/localtime -> /usr/share/zoneinfo/America/Toronto Eric -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1632766 Title: time in lxc ubuntu template Status in lxc package in Ubuntu: Invalid Bug description: With regard to github bug : --- adjust timezone to the host at creation time #47 https://github.com/lxc/lxc/issues/47 --- I still can reproduce the problem on different HW running Xenial with the LXC ubuntu image Trusty and Xenial. * Bare metal (xenial) $ date Wed Oct 12 11:27:55 EDT 2016 LXC (Trusty) $ sudo lxc-attach -n trusty root@trusty:/# date Wed Oct 12 15:28:10 UTC 2016 * Bare metal #2 (xenial) $ date Wed Oct 12 11:28:57 EDT 2016 LXC (Xenial) $ lxc-attach -n xenial $ date Wed Oct 12 15:29:32 UTC 2016 Note, that using the debian template everything works fine : Bare metal #1 (xenial) $ date Wed Oct 12 11:30:40 EDT 2016 $ lxc-attach -n debian8 $ date Wed Oct 12 11:30:45 EDT 2016 However debian and ubuntu got the same piece of code : # lxc-debian.in 149 # set initial timezone as on host 150 if [ -f /etc/timezone ]; then 151 cat /etc/timezone > "$rootfs/etc/timezone" 152 chroot "$rootfs" dpkg-reconfigure -f noninteractive tzdata 153 elif [ -f /etc/sysconfig/clock ]; then 154 . /etc/sysconfig/clock 155 echo "$ZONE" > "$rootfs/etc/timezone" 156 chroot "$rootfs" dpkg-reconfigure -f noninteractive tzdata 157 else 158 echo "Timezone in container is not configured. Adjust it manually." 159 fi 160 161 echo "root:root" | chroot "$rootfs" chpasswd 162 echo "Root password is 'root', please change !" 163 164 return 0 165 } # lxc-ubuntu.in 600 # Set initial timezone as on host 601 if [ -f /etc/timezone ]; then 602 cat /etc/timezone > $rootfs/etc/timezone 603 chroot $rootfs dpkg-reconfigure -f noninteractive tzdata 604 elif [ -f /etc/sysconfig/clock ]; then 605 . /etc/sysconfig/clock 606 echo $ZONE > $rootfs/etc/timezone 607 chroot $rootfs dpkg-reconfigure -f noninteractive tzdata 608 else 609 echo "Timezone in container is not configured. Adjust it manually." 610 fi If I run the above manually it has positive effect on Trusty (persistent across stop/start) $ cat /etc/timezone > /var/lib/lxc/trusty/rootfs/etc/timezone $ chroot /var/lib/lxc/trusty/rootfs dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'America/Toronto' Local time is now: Wed Oct 12 11:35:37 EDT 2016. Universal Time is now: Wed Oct 12 15:35:37 UTC 2016. $ lxc-attach -n trusty $ date Wed Oct 12 11:36:02 EDT 2016 But got no effect on Xenial LXC container : $ cat /etc/timezone > /var/lib/lxc/xenial/rootfs/etc/timezone $ chroot /var/lib/lxc/xenial/rootfs dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Etc/UTC' Local time is now: Wed Oct 12 15:38:00 UTC 2016. Universal Time is now: Wed Oct 12 15:38:00 UTC 2016. # lxc-attach -n xenial $ date Wed Oct 12 15:38:06 UTC 2016 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1632766/+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 1632766] Re: time in lxc ubuntu template
So it's expected that the download template images will not replicate any host settings (locales, timezone, ...) as those are completely self- contained images. As discussed on IRC, it looks like Xenial needs you to also change the /etc/localtime symlink, which is why your manual change worked for trusty but not xenial. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1632766 Title: time in lxc ubuntu template Status in lxc package in Ubuntu: Invalid Bug description: With regard to github bug : --- adjust timezone to the host at creation time #47 https://github.com/lxc/lxc/issues/47 --- I still can reproduce the problem on different HW running Xenial with the LXC ubuntu image Trusty and Xenial. * Bare metal (xenial) $ date Wed Oct 12 11:27:55 EDT 2016 LXC (Trusty) $ sudo lxc-attach -n trusty root@trusty:/# date Wed Oct 12 15:28:10 UTC 2016 * Bare metal #2 (xenial) $ date Wed Oct 12 11:28:57 EDT 2016 LXC (Xenial) $ lxc-attach -n xenial $ date Wed Oct 12 15:29:32 UTC 2016 Note, that using the debian template everything works fine : Bare metal #1 (xenial) $ date Wed Oct 12 11:30:40 EDT 2016 $ lxc-attach -n debian8 $ date Wed Oct 12 11:30:45 EDT 2016 However debian and ubuntu got the same piece of code : # lxc-debian.in 149 # set initial timezone as on host 150 if [ -f /etc/timezone ]; then 151 cat /etc/timezone > "$rootfs/etc/timezone" 152 chroot "$rootfs" dpkg-reconfigure -f noninteractive tzdata 153 elif [ -f /etc/sysconfig/clock ]; then 154 . /etc/sysconfig/clock 155 echo "$ZONE" > "$rootfs/etc/timezone" 156 chroot "$rootfs" dpkg-reconfigure -f noninteractive tzdata 157 else 158 echo "Timezone in container is not configured. Adjust it manually." 159 fi 160 161 echo "root:root" | chroot "$rootfs" chpasswd 162 echo "Root password is 'root', please change !" 163 164 return 0 165 } # lxc-ubuntu.in 600 # Set initial timezone as on host 601 if [ -f /etc/timezone ]; then 602 cat /etc/timezone > $rootfs/etc/timezone 603 chroot $rootfs dpkg-reconfigure -f noninteractive tzdata 604 elif [ -f /etc/sysconfig/clock ]; then 605 . /etc/sysconfig/clock 606 echo $ZONE > $rootfs/etc/timezone 607 chroot $rootfs dpkg-reconfigure -f noninteractive tzdata 608 else 609 echo "Timezone in container is not configured. Adjust it manually." 610 fi If I run the above manually it has positive effect on Trusty (persistent across stop/start) $ cat /etc/timezone > /var/lib/lxc/trusty/rootfs/etc/timezone $ chroot /var/lib/lxc/trusty/rootfs dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'America/Toronto' Local time is now: Wed Oct 12 11:35:37 EDT 2016. Universal Time is now: Wed Oct 12 15:35:37 UTC 2016. $ lxc-attach -n trusty $ date Wed Oct 12 11:36:02 EDT 2016 But got no effect on Xenial LXC container : $ cat /etc/timezone > /var/lib/lxc/xenial/rootfs/etc/timezone $ chroot /var/lib/lxc/xenial/rootfs dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Etc/UTC' Local time is now: Wed Oct 12 15:38:00 UTC 2016. Universal Time is now: Wed Oct 12 15:38:00 UTC 2016. # lxc-attach -n xenial $ date Wed Oct 12 15:38:06 UTC 2016 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1632766/+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 1632772] [NEW] GNOME on Wayland does not start from LightDM
Public bug reported: When picking GNOME on Wayland as session and attempting to login from LightDM then it fails, all you see is a black screen with a blinking cursor. However, manually running: $ dbus-run-session gnome-shell --display-server --wayland from the console/vt1 (Ctrl+Alt+F1) seems to work. But from LightDM it does not work. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-session-wayland 3.20.2-1ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 12 18:06:13 2016 InstallationDate: Installed on 2013-12-26 (1020 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wayland-session yakkety ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/1632772 Title: GNOME on Wayland does not start from LightDM Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: New Bug description: When picking GNOME on Wayland as session and attempting to login from LightDM then it fails, all you see is a black screen with a blinking cursor. However, manually running: $ dbus-run-session gnome-shell --display-server --wayland from the console/vt1 (Ctrl+Alt+F1) seems to work. But from LightDM it does not work. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-session-wayland 3.20.2-1ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 12 18:06:13 2016 InstallationDate: Installed on 2013-12-26 (1020 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1632772/+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 411688] Re: pulseaudio floods network with multicast packets
I am on Ubuntu 14.04.5 platform. I came across the same bug yesterday while trying to set up pulseaudio server on Windows to send audio from my Ubuntu laptop in local network and it rendered the home network unusable. It costed me hours to locate the pest. Dos attack triggered by pavucontrol, when I close it flooding diminishes. I implemented the following workaround `pactl unload-module module-rtp- send` Nobody's patched it for 8 years, so we have to live with this bug and no RTP server until my learning curve reaches a higher level to overcome it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b
[Touch-packages] [Bug 1178402] Re: tracker-extract crashed with signal 5 in g_malloc()
** Changed in: ubuntu-gnome Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1178402 Title: tracker-extract crashed with signal 5 in g_malloc() Status in Tracker: Fix Released Status in Ubuntu GNOME: Fix Released Status in tracker package in Ubuntu: Fix Released Status in tracker source package in Trusty: Fix Released Status in tracker source package in Xenial: Fix Released Bug description: * Impact An integer overflow occurs when tracker-extract comes across an extremely large GIF image or one which is specifically crafted. * Test case If for instance this file https://bugzilla.gnome.org/attachment.cgi?id=326198 is saved on a computer tracker-extract will crash when it gets to it unless the patches are applied. * Regression potential I have not tested these patches but the fix is in the Yakkety version and I do not experience the crash there and no regressions. -- Original report: Lock Interface and PC ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: tracker-extract 0.16.0-2ubuntu1~ubuntu13.04.1 [origin: LP-PPA-gnome3-team-gnome3] ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Thu May 9 16:45:04 2013 ExecutablePath: /usr/lib/tracker/tracker-extract InstallationDate: Installed on 2013-04-29 (9 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True ProcCmdline: /usr/lib/tracker/tracker-extract ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=pt_BR:pt:en LANG=pt_BR.UTF-8 Signal: 5 SourcePackage: tracker StacktraceTop: g_malloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 tracker_extract_get_metadata () from /usr/lib/tracker-0.16/extract-modules/libextract-gif.so ?? () ?? () ?? () Title: tracker-extract crashed with signal 5 in g_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/1178402/+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 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional
this is the bug that causes the thumbnails to be blank for camera-app and gallery-app snaps -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1620635 Title: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional Status in AppArmor: Triaged Status in Snappy: Won't Fix Status in apparmor package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Download and compile the following sample C app that calls aa_query_label wget https://launchpadlibrarian.net/207629699/query_file.c gcc -o query_file query_file.c -l apparmor 2. Install a snap that uses the home interface, for example demo-wget: snap install demo-wget 3. Create a file in your home: touch /home/USERNAME/testfile 4. Ask apparmor if demo-wget can read that file with query_file: ./query_file snap.demo-wget.wget /home/USERNAME/testfile Expected result: output of ./query_file command is read '/home/kaleo/toto' allowed Current result: output of ./query_file command is read '/home/kaleo/toto' denied To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1620635/+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 1632766] Re: time in lxc ubuntu template
LXC Container has been created as follow : $ lxc-create -t download -n trusty -- --dist ubuntu --release trusty --arch amd64 $ lxc-create -t download -n xenial -- --dist ubuntu --release xenial --arch amd64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1632766 Title: time in lxc ubuntu template Status in lxc package in Ubuntu: Invalid Bug description: With regard to github bug : --- adjust timezone to the host at creation time #47 https://github.com/lxc/lxc/issues/47 --- I still can reproduce the problem on different HW running Xenial with the LXC ubuntu image Trusty and Xenial. * Bare metal (xenial) $ date Wed Oct 12 11:27:55 EDT 2016 LXC (Trusty) $ sudo lxc-attach -n trusty root@trusty:/# date Wed Oct 12 15:28:10 UTC 2016 * Bare metal #2 (xenial) $ date Wed Oct 12 11:28:57 EDT 2016 LXC (Xenial) $ lxc-attach -n xenial $ date Wed Oct 12 15:29:32 UTC 2016 Note, that using the debian template everything works fine : Bare metal #1 (xenial) $ date Wed Oct 12 11:30:40 EDT 2016 $ lxc-attach -n debian8 $ date Wed Oct 12 11:30:45 EDT 2016 However debian and ubuntu got the same piece of code : # lxc-debian.in 149 # set initial timezone as on host 150 if [ -f /etc/timezone ]; then 151 cat /etc/timezone > "$rootfs/etc/timezone" 152 chroot "$rootfs" dpkg-reconfigure -f noninteractive tzdata 153 elif [ -f /etc/sysconfig/clock ]; then 154 . /etc/sysconfig/clock 155 echo "$ZONE" > "$rootfs/etc/timezone" 156 chroot "$rootfs" dpkg-reconfigure -f noninteractive tzdata 157 else 158 echo "Timezone in container is not configured. Adjust it manually." 159 fi 160 161 echo "root:root" | chroot "$rootfs" chpasswd 162 echo "Root password is 'root', please change !" 163 164 return 0 165 } # lxc-ubuntu.in 600 # Set initial timezone as on host 601 if [ -f /etc/timezone ]; then 602 cat /etc/timezone > $rootfs/etc/timezone 603 chroot $rootfs dpkg-reconfigure -f noninteractive tzdata 604 elif [ -f /etc/sysconfig/clock ]; then 605 . /etc/sysconfig/clock 606 echo $ZONE > $rootfs/etc/timezone 607 chroot $rootfs dpkg-reconfigure -f noninteractive tzdata 608 else 609 echo "Timezone in container is not configured. Adjust it manually." 610 fi If I run the above manually it has positive effect on Trusty (persistent across stop/start) $ cat /etc/timezone > /var/lib/lxc/trusty/rootfs/etc/timezone $ chroot /var/lib/lxc/trusty/rootfs dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'America/Toronto' Local time is now: Wed Oct 12 11:35:37 EDT 2016. Universal Time is now: Wed Oct 12 15:35:37 UTC 2016. $ lxc-attach -n trusty $ date Wed Oct 12 11:36:02 EDT 2016 But got no effect on Xenial LXC container : $ cat /etc/timezone > /var/lib/lxc/xenial/rootfs/etc/timezone $ chroot /var/lib/lxc/xenial/rootfs dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Etc/UTC' Local time is now: Wed Oct 12 15:38:00 UTC 2016. Universal Time is now: Wed Oct 12 15:38:00 UTC 2016. # lxc-attach -n xenial $ date Wed Oct 12 15:38:06 UTC 2016 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1632766/+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 1632766] [NEW] time in lxc ubuntu template
Public bug reported: With regard to github bug : --- adjust timezone to the host at creation time #47 https://github.com/lxc/lxc/issues/47 --- I still can reproduce the problem on different HW running Xenial with the LXC ubuntu image Trusty and Xenial. * Bare metal (xenial) $ date Wed Oct 12 11:27:55 EDT 2016 LXC (Trusty) $ sudo lxc-attach -n trusty root@trusty:/# date Wed Oct 12 15:28:10 UTC 2016 * Bare metal #2 (xenial) $ date Wed Oct 12 11:28:57 EDT 2016 LXC (Xenial) $ lxc-attach -n xenial $ date Wed Oct 12 15:29:32 UTC 2016 Note, that using the debian template everything works fine : Bare metal #1 (xenial) $ date Wed Oct 12 11:30:40 EDT 2016 $ lxc-attach -n debian8 $ date Wed Oct 12 11:30:45 EDT 2016 However debian and ubuntu got the same piece of code : # lxc-debian.in 149 # set initial timezone as on host 150 if [ -f /etc/timezone ]; then 151 cat /etc/timezone > "$rootfs/etc/timezone" 152 chroot "$rootfs" dpkg-reconfigure -f noninteractive tzdata 153 elif [ -f /etc/sysconfig/clock ]; then 154 . /etc/sysconfig/clock 155 echo "$ZONE" > "$rootfs/etc/timezone" 156 chroot "$rootfs" dpkg-reconfigure -f noninteractive tzdata 157 else 158 echo "Timezone in container is not configured. Adjust it manually." 159 fi 160 161 echo "root:root" | chroot "$rootfs" chpasswd 162 echo "Root password is 'root', please change !" 163 164 return 0 165 } # lxc-ubuntu.in 600 # Set initial timezone as on host 601 if [ -f /etc/timezone ]; then 602 cat /etc/timezone > $rootfs/etc/timezone 603 chroot $rootfs dpkg-reconfigure -f noninteractive tzdata 604 elif [ -f /etc/sysconfig/clock ]; then 605 . /etc/sysconfig/clock 606 echo $ZONE > $rootfs/etc/timezone 607 chroot $rootfs dpkg-reconfigure -f noninteractive tzdata 608 else 609 echo "Timezone in container is not configured. Adjust it manually." 610 fi If I run the above manually it has positive effect on Trusty (persistent across stop/start) $ cat /etc/timezone > /var/lib/lxc/trusty/rootfs/etc/timezone $ chroot /var/lib/lxc/trusty/rootfs dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'America/Toronto' Local time is now: Wed Oct 12 11:35:37 EDT 2016. Universal Time is now: Wed Oct 12 15:35:37 UTC 2016. $ lxc-attach -n trusty $ date Wed Oct 12 11:36:02 EDT 2016 But got no effect on Xenial LXC container : $ cat /etc/timezone > /var/lib/lxc/xenial/rootfs/etc/timezone $ chroot /var/lib/lxc/xenial/rootfs dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Etc/UTC' Local time is now: Wed Oct 12 15:38:00 UTC 2016. Universal Time is now: Wed Oct 12 15:38:00 UTC 2016. # lxc-attach -n xenial $ date Wed Oct 12 15:38:06 UTC 2016 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: With regard to github bug : --- adjust timezone to the host at creation time #47 https://github.com/lxc/lxc/issues/47 --- I still can reproduce the problem on different HW running Xenial with - the LXC ubuntu image Trusty. + the LXC ubuntu image Trusty and Xenial. * Bare metal (xenial) $ date Wed Oct 12 11:27:55 EDT 2016 LXC (Trusty) $ sudo lxc-attach -n trusty root@trusty:/# date Wed Oct 12 15:28:10 UTC 2016 * Bare metal #2 (xenial) $ date Wed Oct 12 11:28:57 EDT 2016 LXC (Xenial) $ lxc-attach -n xenial $ date Wed Oct 12 15:29:32 UTC 2016 Note, that using the debian template everything works fine : Bare metal #1 (xenial) $ date Wed Oct 12 11:30:40 EDT 2016 $ lxc-attach -n debian8 $ date Wed Oct 12 11:30:45 EDT 2016 However debian and ubuntu got the same piece of code : # lxc-debian.in 149 # set initial timezone as on host 150 if [ -f /etc/timezone ]; then 151 cat /etc/timezone > "$rootfs/etc/timezone" 152 chroot "$rootfs" dpkg-reconfigure -f noninteractive tzdata 153 elif [ -f /etc/sysconfig/clock ]; then 154 . /etc/sysconfig/clock 155 echo "$ZONE" > "$rootfs/etc/timezone" 156 chroot "$rootfs" dpkg-reconfigure -f noninteractive tzdata 157 else 158 echo "Timezone in container is not configured. Adjust it manually." 159 fi - 160 + 160 161 echo "root:root" | chroot "$rootfs" chpasswd 162 echo "Root password is 'root', please change !" - 163 + 163 164 return 0 165 } - # lxc-ubuntu.in 600 # Set initial timezone as on host 601 if [ -f /etc/timezone ]; then 602 cat /etc/timezone > $rootfs/etc/timezone 603 chroot $rootfs dpkg-reconfigure -f noninteractive tzdata 604 elif [ -f /etc/sysconfig/clock ]; then 605 . /etc/sysconfig/clock 606 echo $ZONE > $rootfs/etc/timezone 607 chroot $rootfs dpkg-reconfigure -f noninteractive tzdata 608 else 609 echo "Timezone in container
[Touch-packages] [Bug 1632767] [NEW] yakkety: desktop ISO fails to reboot after install: Failed deactivating swap
Public bug reported: The 20161012.1 yakkety desktop ISO fails to reboot after the install completes (see attached screenshot). Tested on QEMU in BIOS and UEFI mode, which is where the screenshot is from. Same thing is seemingly happening on hardware (reboot hangs), although I don't see this particular debugging output on hardware. The systemd related logging might be a red haring... I'm not sure this is actually a systemd bug, just that it seems the correct starting point. Thanks! ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: yakkety ** Attachment added: "Screenshot from 2016-10-12 06-14-05.png" https://bugs.launchpad.net/bugs/1632767/+attachment/4759958/+files/Screenshot%20from%202016-10-12%2006-14-05.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1632767 Title: yakkety: desktop ISO fails to reboot after install: Failed deactivating swap Status in systemd package in Ubuntu: New Bug description: The 20161012.1 yakkety desktop ISO fails to reboot after the install completes (see attached screenshot). Tested on QEMU in BIOS and UEFI mode, which is where the screenshot is from. Same thing is seemingly happening on hardware (reboot hangs), although I don't see this particular debugging output on hardware. The systemd related logging might be a red haring... I'm not sure this is actually a systemd bug, just that it seems the correct starting point. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1632767/+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 1626245] Re: [MIR] fonts-android
** Changed in: fonts-android (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1626245 Title: [MIR] fonts-android Status in fonts-android package in Ubuntu: Fix Released Bug description: Please include the fonts-android package in Ubuntu's component main. fonts-android includes the fonts-droid-fallback binary, and as a result of the discussion at bug 1625734, the server team wants that libgs9-common, which currently recommends fonts-noto-cjk, is changed to instead recommend fonts-droid-fallback. fonts-android is a Debian package and included in Debian's component main. It was included in Ubuntu's component main between trusty and wily. Bugs: http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=fonts-android https://bugs.launchpad.net/ubuntu/+source/fonts-android I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, and haven't found any issues that would prevent the proposed main inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1626245/+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 1632593] Re: Xorg does not utilize the 3D graphics acceleration capabilities of my device
Can someone please change this to be about the package containing the do-release-upgrade command? -- 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/1632593 Title: Xorg does not utilize the 3D graphics acceleration capabilities of my device Status in xorg package in Ubuntu: New Bug description: Everything worked fine in 16.04. I then upgraded to 16.10 a bit early to see if I could find any bugs, and immediately noticed that Unity was running in low-graphics mode, and YouTube chugs noticably. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 09:57:12 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] InstallationDate: Installed on 2016-01-21 (264 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 12 09:59:28 2016 xserver.configfile: default xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: cannot open shared object file: No such file or directory modeset: Failed to load module "glamoregl" (loader failed, 7) modeset(0): Failed to load glamor module. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632593/+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 1632740] Re: Screen distorts after a period of use, may crash kernel
** Attachment added: "Fotos.zip" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632740/+attachment/4759954/+files/Fotos.zip -- 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/1632740 Title: Screen distorts after a period of use, may crash kernel Status in xorg package in Ubuntu: New Bug description: After using my system for a period of time, usually less than an hour, the screen starts to corrupt. It will vary in intensity, until the system either crashes, or everything goes back to normal for a while. When the system does crash, not even the sysrq-key works. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 16:43:52 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] InstallationDate: Installed on 2016-01-21 (265 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-11 (1 days ago) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 12 16:44:31 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632740/+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 1632740] [NEW] Screen distorts after a period of use, may crash kernel
Public bug reported: After using my system for a period of time, usually less than an hour, the screen starts to corrupt. It will vary in intensity, until the system either crashes, or everything goes back to normal for a while. When the system does crash, not even the sysrq-key works. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 16:43:52 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] InstallationDate: Installed on 2016-01-21 (265 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-11 (1 days ago) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 12 16:44:31 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu yakkety -- 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/1632740 Title: Screen distorts after a period of use, may crash kernel Status in xorg package in Ubuntu: New Bug description: After using my system for a period of time, usually less than an hour, the screen starts to corrupt. It will vary in intensity, until the system either crashes, or everything goes back to normal for a while. When the system does crash, not even the sysrq-key works. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 16:43:52 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphic
[Touch-packages] [Bug 1632593] Re: Xorg does not utilize the 3D graphics acceleration capabilities of my device
I reinstalled the package, no dice. I then looked around for it, and found that it had been renamed to old.libgbm1.so, along with the file it linked to. I renamed both, removing the "old.", and now 3D works. It's definitely still a bug though. -- 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/1632593 Title: Xorg does not utilize the 3D graphics acceleration capabilities of my device Status in xorg package in Ubuntu: New Bug description: Everything worked fine in 16.04. I then upgraded to 16.10 a bit early to see if I could find any bugs, and immediately noticed that Unity was running in low-graphics mode, and YouTube chugs noticably. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 09:57:12 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] InstallationDate: Installed on 2016-01-21 (264 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 12 09:59:28 2016 xserver.configfile: default xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: cannot open shared object file: No such file or directory modeset: Failed to load module "glamoregl" (loader failed, 7) modeset(0): Failed to load glamor module. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632593/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
** Also affects: history-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Ubuntu File Manager App: Fix Committed Status in address-book-app package in Ubuntu: Fix Committed Status in dialer-app package in Ubuntu: New Status in history-service package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: New Status in indicator-location package in Ubuntu: New Status in indicator-messages package in Ubuntu: New Status in indicator-network package in Ubuntu: New Status in indicator-power package in Ubuntu: New Status in indicator-session package in Ubuntu: New Status in indicator-sound package in Ubuntu: New Status in indicator-transfer package in Ubuntu: New Status in messaging-app package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: Fix Committed Status in ubuntu-terminal-app package in Ubuntu: New Status in ubuntu-touch-session package in Ubuntu: New Status in unity-scope-click package in Ubuntu: New Status in unity-scope-scopes package in Ubuntu: New Status in unity-scopes-api package in Ubuntu: In Progress Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Status in webbrowser-app package in Ubuntu: In Progress Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1632593] Re: Xorg does not utilize the 3D graphics acceleration capabilities of my device
and how do you verify it's installed? run 'apt-cache policy libgbm1' -- 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/1632593 Title: Xorg does not utilize the 3D graphics acceleration capabilities of my device Status in xorg package in Ubuntu: New Bug description: Everything worked fine in 16.04. I then upgraded to 16.10 a bit early to see if I could find any bugs, and immediately noticed that Unity was running in low-graphics mode, and YouTube chugs noticably. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 09:57:12 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] InstallationDate: Installed on 2016-01-21 (264 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 12 09:59:28 2016 xserver.configfile: default xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: cannot open shared object file: No such file or directory modeset: Failed to load module "glamoregl" (loader failed, 7) modeset(0): Failed to load glamor module. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632593/+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 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed
*** This bug is a duplicate of bug 1357093 *** https://bugs.launchpad.net/bugs/1357093 Richard L Cooper, did you sometimes install new kernels by Software Updater or e.g. by 'sudo apt-get dist-upgrade'? If so, you were affected by Bug #1624644. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1054927 Title: Autoupdater fills /boot and crashes because old kernel images are never removed Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1) Install Ubuntu with the default LVM encryption recipe 2) Set Ubuntu to automatically install security updates on the background 3) Use ubuntu for 5 months Actual results: The system automatically installs security updates for the kernel under /boot. It's never removes previous kernel images. After about five months, the /boot partition created by the install recipe (i.e. sized according to the judgment of Ubuntu developers—not me) fills up and the unattended updater crashes during the next kernel update. Expected results: Expected the unattended updater to leave the nearest kernel and the previous one on /boot and to automatically remove older kernel images. Expected the system installer to set up /boot such that it never runs out of space when the system updater operates automatically. For workaround and sytem repair, see https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Sun Sep 23 12:53:52 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1054927/+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 1630765] Re: webbrowser-app crashed with SIGSEGV in QNetworkConfiguration::~QNetworkConfiguration()
Here's the report for signon: bug 1632687. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1630765 Title: webbrowser-app crashed with SIGSEGV in QNetworkConfiguration::~QNetworkConfiguration() Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I changed the session to unity 7 and I guess the browser didn't stopped. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: webbrowser-app 0.23+16.10.20160928-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity8 Date: Wed Oct 5 22:00:38 2016 ExecutablePath: /usr/bin/webbrowser-app ExecutableTimestamp: 1475051112 InstallationDate: Installed on 2016-10-05 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) ProcCmdline: webbrowser-app ProcCwd: /home/jbenitez ProcEnviron: PATH=(custom, no user) LANGUAGE=es_ES XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd1d609a5df <_ZN21QNetworkConfigurationD2Ev+63>: mov0x8(%rax),%rax PC (0x7fd1d609a5df) ok source "0x8(%rax)" (0x7fd15ef5b7d8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: webbrowser-app StacktraceTop: QNetworkConfiguration::~QNetworkConfiguration() () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 QHashData::free_helper(void (*)(QHashData::Node*)) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 QThreadStorageData::finish(void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 QCoreApplicationPrivate::cleanupThreadData() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 Title: webbrowser-app crashed with SIGSEGV in QNetworkConfiguration::~QNetworkConfiguration() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1630765/+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 1632687] Re: /usr/bin/signonpluginprocess:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QNetworkAccessManagerPrivate::~QNetworkAccessManagerPrivat
*** This bug is a duplicate of bug 1630765 *** https://bugs.launchpad.net/bugs/1630765 ** This bug has been marked a duplicate of bug 1630765 webbrowser-app crashed with SIGSEGV in QNetworkConfiguration::~QNetworkConfiguration() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1632687 Title: /usr/bin/signonpluginprocess:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QNetworkAccessManagerPrivate::~QNetworkAccessManagerPrivate:QNetworkAccessManagerPrivate::~QNetworkAccessManagerPrivate:QScopedPointerDeleter Status in signon package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding signon. This problem was most recently seen with package version 8.59+16.10.20160916-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/cdb7a4fc6d47e3ba3ce18606745c27933f9a7f57 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1632687/+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 1624028] Re: lxc create using debian template fails on ppc64el
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1624028 Title: lxc create using debian template fails on ppc64el Status in lxc package in Ubuntu: Fix Released Bug description: If I try to create a lxc container using the debian template, I get the following error on ppc64el arch: ➜ ~ sudo lxc-create -n debian01 -t debian debootstrap is /usr/sbin/debootstrap Checking cache download in /var/cache/lxc/debian/rootfs-jessie-ppc64le ... gpg: WARNING: unsafe ownership on configuration file `/home/ubuntu/.gnupg/gpg.conf' gpg: key 2B90D010: "Debian Archive Automatic Signing Key (8/jessie) " not changed gpg: Total number processed: 1 gpg: unchanged: 1 Downloading debian minimal ... I: Retrieving InRelease I: Failed to retrieve InRelease I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010) E: Invalid Release file, no entry for main/binary-ppc64le/Packages Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for debian01 failed lxc-create: tools/lxc_create.c: main: 318 Error creating container debian01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1624028/+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 1632681] Re: SonicWall NetExteder broken by new nsswitch.conf configuration
** Package changed: nss (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1632681 Title: SonicWall NetExteder broken by new nsswitch.conf configuration Status in systemd package in Ubuntu: New Bug description: In Ubuntu Yakkety the following line in /etc/nsswitch.conf breaks DNS resolution via the VPN tunnel created by Sonicwall NetExtender application. hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns Changing this line to: hosts: files mdns4_minimal [NOTFOUND=return] resolve [UNAVAIL=return] dns or hosts: files mdns4_minimal [NOTFOUND=return] dns [!UNAVAIL=return] resolve I have not found documentation on what "resolve" means, so im not sure this lines makes global sense, but it solve my dns problem. If i have to guess its another systemd incarnation. As a side note NetExtender modifies /etc/resolv.conf and adds the VPN DNS servers as the first entries. So when NetExtender is connected the first lines in /etc/resolv.conf contains the VPN DNS IP and only after there is the local dnsmasq entry. Sadly i could not found which package creates this file as "dpkg-query -S /etc/nsswitch.conf" returns no results on my system. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libnss3 2:3.26-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0 Uname: Linux 4.8.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 12 13:58:41 2016 InstallationDate: Installed on 2016-07-27 (76 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: nss UpgradeStatus: Upgraded to yakkety on 2016-10-07 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1632681/+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 1632689] [NEW] /usr/bin/webbrowser-app:11:QNetworkSession::~QNetworkSession:QNetworkSession::~QNetworkSession:QObject::event:QApplicationPrivate::notify_helper:QApplication::noti
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding webbrowser-app. This problem was most recently seen with package version 0.23+16.10.20160928-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/afdb8f6b29b8426c2468559fde830cda948dc85a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1632689 Title: /usr/bin/webbrowser- app:11:QNetworkSession::~QNetworkSession:QNetworkSession::~QNetworkSession:QObject::event:QApplicationPrivate::notify_helper:QApplication::notify Status in webbrowser-app package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding webbrowser-app. This problem was most recently seen with package version 0.23+16.10.20160928-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/afdb8f6b29b8426c2468559fde830cda948dc85a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1632689/+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 1385292] Re: can't rename files in nautilus
I installed version 1:3.18.5 of nautilus and it solves the problem : With this new version, when renaming a file (F2 on the file for example) a box pops up in which you can type the new name. Unfortunately with this version you can't paste files from the upper right menu (the option has been removed), neither directly in the task bar with right click button... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1385292 Title: can't rename files in nautilus Status in ibus: Unknown Status in ibus package in Ubuntu: Fix Released Bug description: sometimes can't rename files with F2 button. It is higlight changing, but nothing gonna happen, it is not responding ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 24 17:48:33 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2014-10-24 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1385292/+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 1632684] [NEW] /usr/bin/webbrowser-app:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding webbrowser-app. This problem was most recently seen with package version 0.23+16.10.20160928-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/9ef1aa40b6bdc7984545538af85cf9275d0cced1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1632684 Title: /usr/bin/webbrowser- app:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QHashData::free_helper:QHash:QHash Status in webbrowser-app package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding webbrowser-app. This problem was most recently seen with package version 0.23+16.10.20160928-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/9ef1aa40b6bdc7984545538af85cf9275d0cced1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1632684/+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 1632687] [NEW] /usr/bin/signonpluginprocess:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QNetworkAccessManagerPrivate::~QNetworkAccessManagerPriv
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding signon. This problem was most recently seen with package version 8.59+16.10.20160916-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/cdb7a4fc6d47e3ba3ce18606745c27933f9a7f57 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: signon (Ubuntu) Importance: Undecided Status: New ** Tags: yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1632687 Title: /usr/bin/signonpluginprocess:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QNetworkAccessManagerPrivate::~QNetworkAccessManagerPrivate:QNetworkAccessManagerPrivate::~QNetworkAccessManagerPrivate:QScopedPointerDeleter Status in signon package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding signon. This problem was most recently seen with package version 8.59+16.10.20160916-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/cdb7a4fc6d47e3ba3ce18606745c27933f9a7f57 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1632687/+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 1632681] [NEW] SonicWall NetExteder broken by new nsswitch.conf configuration
Public bug reported: In Ubuntu Yakkety the following line in /etc/nsswitch.conf breaks DNS resolution via the VPN tunnel created by Sonicwall NetExtender application. hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns Changing this line to: hosts: files mdns4_minimal [NOTFOUND=return] resolve [UNAVAIL=return] dns or hosts: files mdns4_minimal [NOTFOUND=return] dns [!UNAVAIL=return] resolve I have not found documentation on what "resolve" means, so im not sure this lines makes global sense, but it solve my dns problem. If i have to guess its another systemd incarnation. As a side note NetExtender modifies /etc/resolv.conf and adds the VPN DNS servers as the first entries. So when NetExtender is connected the first lines in /etc/resolv.conf contains the VPN DNS IP and only after there is the local dnsmasq entry. Sadly i could not found which package creates this file as "dpkg-query -S /etc/nsswitch.conf" returns no results on my system. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libnss3 2:3.26-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0 Uname: Linux 4.8.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 12 13:58:41 2016 InstallationDate: Installed on 2016-07-27 (76 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: nss UpgradeStatus: Upgraded to yakkety on 2016-10-07 (4 days ago) ** Affects: nss (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug nsswitch.conf yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1632681 Title: SonicWall NetExteder broken by new nsswitch.conf configuration Status in nss package in Ubuntu: New Bug description: In Ubuntu Yakkety the following line in /etc/nsswitch.conf breaks DNS resolution via the VPN tunnel created by Sonicwall NetExtender application. hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns Changing this line to: hosts: files mdns4_minimal [NOTFOUND=return] resolve [UNAVAIL=return] dns or hosts: files mdns4_minimal [NOTFOUND=return] dns [!UNAVAIL=return] resolve I have not found documentation on what "resolve" means, so im not sure this lines makes global sense, but it solve my dns problem. If i have to guess its another systemd incarnation. As a side note NetExtender modifies /etc/resolv.conf and adds the VPN DNS servers as the first entries. So when NetExtender is connected the first lines in /etc/resolv.conf contains the VPN DNS IP and only after there is the local dnsmasq entry. Sadly i could not found which package creates this file as "dpkg-query -S /etc/nsswitch.conf" returns no results on my system. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libnss3 2:3.26-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0 Uname: Linux 4.8.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 12 13:58:41 2016 InstallationDate: Installed on 2016-07-27 (76 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: nss UpgradeStatus: Upgraded to yakkety on 2016-10-07 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1632681/+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 1625667] Re: Trusty: apt does not try next mirror if index file download fails with mirror:// source
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1625667 Title: Trusty: apt does not try next mirror if index file download fails with mirror:// source Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Committed Bug description: [SRU justification] This fix is needed to allow correct archive mirroring functionality. [Impact] Without this fix, apt-get update and other apt commands requiring Package file access may fail when there are remote transient errors due to archive availability. [Fix] Use std::npos instead of 0 to test presence of "Translation" in ShortDesc. [Test Case] 1) Setup three containers (archive1, archive2, archive3) with a reprepro configuration mirroring the ubuntu restricted archive (to save on space and time to replicate). 2) Add an apache webserver serving the reprepro archive over http on each container 3) Add the following mirrors.txt file to one of the webserver (archive1): $ cat /var/www/html/mirrors.txt http://archive1/ubuntu/ http://archive2/ubuntu/ http://archive3/ubuntu/ 4) Add a client container. Add the IP adresses of the archive[1-3] containers to /etc/hosts. Alias the archive1 address to archive.ubuntu.com similar to the following : $ cat /etc/hosts 127.0.0.1 localhost 10.0.4.182 archive1mirrors.ubuntu.com 10.0.4.127 archive2 10.0.4.193 archive3 5) Add the following line to the /etc/apt/sources.list, commenting all other entries : $ cat /etc/apt/sources.list #deb http://archive.ubuntu.com/ubuntu trusty main #deb http://archive.ubuntu.com/ubuntu trusty-updates main #deb http://archive.ubuntu.com/ubuntu trusty universe #deb http://archive.ubuntu.com/ubuntu trusty-updates universe deb mirror://mirrors.ubuntu.com/mirrors.txt trusty restricted 6) Run $ apt-get -oDebug::Acquire::mirror=true update The log should display for the Packages file : MirrorMethod::Fetch() Failure to get http://10.0.4.193/ubuntu//dists/trusty/restricted/binary-amd64/Packages Err http://10.0.4.193/ubuntu/ trusty/restricted amd64 Packages With the fix you will see : MirrorMethod::Fetch() Failure to get http://10.0.4.193/ubuntu//dists/trusty/restricted/binary-amd64/Packages.gz TryNextMirror: http://10.0.4.127/ubuntu//dists/trusty/restricted/binary-amd64/Packages.gz [Regression] None expected. Worse that can happen is a retry when none was done previously. [Original description of the problem] When using the mirror://mirrors.ubuntu.com/mirrors.txt functionality on Trusty, if the download of the index file fails, apt will not retry on another archive listed in mirrors.txt and will fail. Running the following on Trusty leads to the following result : sudo apt-get update -qq W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-security/universe/binary-amd64/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-security/main/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-security/restricted/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-security/universe/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/main/binary-amd64/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/restricted/binary-amd64/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/universe/binary-amd64/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/main/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/restricted/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/universe/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] E: Some index files failed to download. They have been ignored, or old ones used instead. The same configuration works correctly on Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1625667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
Re: [Touch-packages] [Bug 1632593] Re: Xorg does not utilize the 3D graphics acceleration capabilities of my device
The package is installed, but the file is not there. On 12 Oct 2016 13:50, "Timo Aaltonen" wrote: > your logfile disagrees > > [ 8.117] (EE) Failed to load /usr/lib/xorg/modules/libglamoregl.so: > libgbm.so.1: cannot open shared object file: No such file or directory > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1632593 > > Title: > Xorg does not utilize the 3D graphics acceleration capabilities of my > device > > Status in xorg package in Ubuntu: > New > > Bug description: > Everything worked fine in 16.04. I then upgraded to 16.10 a bit early > to see if I could find any bugs, and immediately noticed that Unity > was running in low-graphics mode, and YouTube chugs noticably. > > ProblemType: Bug > DistroRelease: Ubuntu 16.10 > Package: xorg 1:7.7+13ubuntu4 > ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 > Uname: Linux 4.4.0-34-generic x86_64 > .tmp.unity_support_test.1: > > ApportVersion: 2.20.3-0ubuntu8 > 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: Wed Oct 12 09:57:12 2016 > DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: > './xorg_fix_proprietary.py' > DistroCodename: yakkety > DistroVariant: ubuntu > EcryptfsInUse: Yes > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 > [VGA controller]) > Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] > InstallationDate: Installed on 2016-01-21 (264 days ago) > InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 > (20150805) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. >Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. >Bus 001 Device 002: ID 8087:0a2a Intel Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. T300CHI > ProcEnviron: >LANGUAGE=en_US:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/zsh > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed > root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 > Renderer: Software > SourcePackage: xorg > Symptom: display > UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) > dmi.bios.date: 03/18/2015 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: T300CHI.206 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: T300CHI > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: ATN12345678901234567 > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015: > svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.: > rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.name: T300CHI > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.70-1 > version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 > version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.2-1ubuntu1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20160706-1ubuntu1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.12-2 > xserver.bootTime: Wed Oct 12 09:59:28 2016 > xserver.configfile: default > xserver.errors: >Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: > cannot open shared object file: No such file or directory >modeset: Failed to load module "glamoregl" (loader failed, 7) >modeset(0): Failed to load glamor module. >AIGLX: reverting to software rendering > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.18.4-1ubuntu6 > xserver.video_driver: modeset > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632593/+subscriptions > -- 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/1632593 Title: Xorg does not utilize the 3D graphics acceleration capabilities of my device
[Touch-packages] [Bug 1632593] Re: Xorg does not utilize the 3D graphics acceleration capabilities of my device
your logfile disagrees [ 8.117] (EE) Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: cannot open shared object file: No such file or directory -- 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/1632593 Title: Xorg does not utilize the 3D graphics acceleration capabilities of my device Status in xorg package in Ubuntu: New Bug description: Everything worked fine in 16.04. I then upgraded to 16.10 a bit early to see if I could find any bugs, and immediately noticed that Unity was running in low-graphics mode, and YouTube chugs noticably. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.3-0ubuntu8 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: Wed Oct 12 09:57:12 2016 DistUpgraded: 2016-10-11 14:56:42,427 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:18fd] InstallationDate: Installed on 2016-01-21 (264 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.206:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 12 09:59:28 2016 xserver.configfile: default xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: libgbm.so.1: cannot open shared object file: No such file or directory modeset: Failed to load module "glamoregl" (loader failed, 7) modeset(0): Failed to load glamor module. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1632593/+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 1178402] Re: tracker-extract crashed with signal 5 in g_malloc()
This bug was fixed in the package tracker - 1.6.2-0ubuntu1.1 --- tracker (1.6.2-0ubuntu1.1) xenial-security; urgency=medium * SECURITY UPDATE: Integer overflow when skipping over decoded image data of extremely large or specially prepared GIF resulting in a program crash (LP: #1178402) - debian/patches/fix-gif-possible-integer-overflow.patch: Avoid integer overflow by reading/skipping over image data line by line in read_metadata in src/tracker-extract/tracker-extract-gif.c. -- Nikita Yerenkov-Scott Sun, 09 Oct 2016 16:06:45 +0100 ** Changed in: tracker (Ubuntu Xenial) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1178402 Title: tracker-extract crashed with signal 5 in g_malloc() Status in Tracker: Fix Released Status in Ubuntu GNOME: In Progress Status in tracker package in Ubuntu: Fix Released Status in tracker source package in Trusty: Fix Released Status in tracker source package in Xenial: Fix Released Bug description: * Impact An integer overflow occurs when tracker-extract comes across an extremely large GIF image or one which is specifically crafted. * Test case If for instance this file https://bugzilla.gnome.org/attachment.cgi?id=326198 is saved on a computer tracker-extract will crash when it gets to it unless the patches are applied. * Regression potential I have not tested these patches but the fix is in the Yakkety version and I do not experience the crash there and no regressions. -- Original report: Lock Interface and PC ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: tracker-extract 0.16.0-2ubuntu1~ubuntu13.04.1 [origin: LP-PPA-gnome3-team-gnome3] ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Thu May 9 16:45:04 2013 ExecutablePath: /usr/lib/tracker/tracker-extract InstallationDate: Installed on 2013-04-29 (9 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True ProcCmdline: /usr/lib/tracker/tracker-extract ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=pt_BR:pt:en LANG=pt_BR.UTF-8 Signal: 5 SourcePackage: tracker StacktraceTop: g_malloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 tracker_extract_get_metadata () from /usr/lib/tracker-0.16/extract-modules/libextract-gif.so ?? () ?? () ?? () Title: tracker-extract crashed with signal 5 in g_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/1178402/+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