[Touch-packages] [Bug 1547844] Re: systemd-fsckd does not allow fsck to finish
The machine has been stable for a couple of days, and I tested today that fsck finished OK. ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1547844 Title: systemd-fsckd does not allow fsck to finish Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd package in Debian: Fix Released Bug description: during normal boots, fsck runs fine with small partitions. But I have two big partitions and systemd seems to abort fsck somewhere between 5 to 10 minutes from start. This results in the partition being checked again at every boot. After manual run in recovery mode, everything is OK again. See e.g. sudo tune2fs -l /dev/mapper/xpcvg-home tune2fs 1.42.12 (29-Aug-2014) Filesystem volume name: Last mounted on: /home Filesystem UUID: db583624-afb4-41cb-8b2d-640bee2de61b Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent sparse_super large_file uninit_bg Filesystem flags: signed_directory_hash Default mount options:(none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 65536000 Block count: 262144000 Reserved block count: 13107200 Free blocks: 183474571 Free inodes: 65167292 First block: 0 Block size: 4096 Fragment size:4096 Reserved GDT blocks: 961 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width:384 Filesystem created: Mon Jul 25 12:23:50 2011 Last mount time: Sat Feb 20 09:34:41 2016 Last write time: Sat Feb 20 09:34:41 2016 Mount count: 166 Maximum mount count: 157 Last checked: Sun Nov 29 14:02:12 2015 Check interval: 15552000 (6 months) Next check after: Fri May 27 15:02:12 2016 Lifetime writes: 1113 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode:8 First orphan inode: 65143018 Default directory hash: half_md4 Directory Hash Seed: ea4a0233-d8af-4c51-9302-140a4affacdf Journal backup: inode blocks journalctl says: helmi 20 09:30:21 xpc systemd-fsck[720]: /dev/mapper/xpcvg-home has been mounted 165 times without being checked, check forced. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck: Warning... fsck.ext4 for device /dev/mapper/xpcvg-home exited with signal 13. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck failed with error code 8. helmi 20 09:34:40 xpc systemd-fsck[720]: Ignoring error. helmi 20 09:34:40 xpc systemd[1]: Started File System Check on /dev/mapper/xpcvg-home. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 20 14:20:24 2016 InstallationDate: Installed on 2012-12-22 (1154 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro nomdmonddf nomdmonisw libata.noacpi=1 irqpoll all_generic_ide=1 ide-pci-generic.all-generic-ide=1 usbcore.autosuspend=-1 usbcore.old_scheme_first=1 libata.force=8:1.5G xhci_hcd.quirks=262144 SourcePackage: systemd UpgradeStatus: Upgraded to wily on 2015-10-23 (119 days ago) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VI EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIEXTREME:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system
[Touch-packages] [Bug 1568007] Re: The main app scope doesn't show up
I consider the problem I reported initialy it was fixed from a OTA before OTA-13. This bug should be closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1568007 Title: The main app scope doesn't show up Status in Canonical System Image: Incomplete Status in unity-scopes-api package in Ubuntu: Expired Status in unity8 package in Ubuntu: Expired Bug description: I upload a picture that explains the bug better than me. The apps from the phone doesn't show up in the app scope. After OTA-10 update it happens 2 times. I had to reboot and after that everything was ok. After OTA-10 update I needed to reboot the phone too many times. I don't like this update. It's beautifull as design and many bugs were solved with this update, but many things are slowing down the phone maybe. If you need more info I can search for logs with adb if you can give me more instructions. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1568007/+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 1537389] Re: Unity8 never loads and just stays on a black screen [unity8.log: ERROR: QMirServer - Mir failed to start]
[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity8 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1537389 Title: Unity8 never loads and just stays on a black screen [unity8.log: ERROR: QMirServer - Mir failed to start] Status in Canonical System Image: Incomplete Status in Mir: Expired Status in mir package in Ubuntu: Expired Status in unity8 package in Ubuntu: Expired Status in unity8-desktop-session package in Ubuntu: Expired Bug description: The cursor is also not shown, neither is the Unity 8 Lock Screen or Indicators. Ubuntu 16.04 Daily ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8-desktop-session-mir 1.0.12+15.10.20150609-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.3-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 23 18:44:45 2016 InstallationDate: Installed on 2016-01-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: unity8-desktop-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537389/+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 1537389] Re: Unity8 never loads and just stays on a black screen [unity8.log: ERROR: QMirServer - Mir failed to start]
[Expired for Mir because there has been no activity for 60 days.] ** Changed in: mir Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1537389 Title: Unity8 never loads and just stays on a black screen [unity8.log: ERROR: QMirServer - Mir failed to start] Status in Canonical System Image: Incomplete Status in Mir: Expired Status in mir package in Ubuntu: Expired Status in unity8 package in Ubuntu: Expired Status in unity8-desktop-session package in Ubuntu: Expired Bug description: The cursor is also not shown, neither is the Unity 8 Lock Screen or Indicators. Ubuntu 16.04 Daily ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8-desktop-session-mir 1.0.12+15.10.20150609-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.3-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 23 18:44:45 2016 InstallationDate: Installed on 2016-01-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: unity8-desktop-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537389/+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 1537389] Re: Unity8 never loads and just stays on a black screen [unity8.log: ERROR: QMirServer - Mir failed to start]
[Expired for mir (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mir (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1537389 Title: Unity8 never loads and just stays on a black screen [unity8.log: ERROR: QMirServer - Mir failed to start] Status in Canonical System Image: Incomplete Status in Mir: Expired Status in mir package in Ubuntu: Expired Status in unity8 package in Ubuntu: Expired Status in unity8-desktop-session package in Ubuntu: Expired Bug description: The cursor is also not shown, neither is the Unity 8 Lock Screen or Indicators. Ubuntu 16.04 Daily ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8-desktop-session-mir 1.0.12+15.10.20150609-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.3-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 23 18:44:45 2016 InstallationDate: Installed on 2016-01-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: unity8-desktop-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537389/+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 1537389] Re: Unity8 never loads and just stays on a black screen [unity8.log: ERROR: QMirServer - Mir failed to start]
[Expired for unity8-desktop-session (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity8-desktop-session (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1537389 Title: Unity8 never loads and just stays on a black screen [unity8.log: ERROR: QMirServer - Mir failed to start] Status in Canonical System Image: Incomplete Status in Mir: Expired Status in mir package in Ubuntu: Expired Status in unity8 package in Ubuntu: Expired Status in unity8-desktop-session package in Ubuntu: Expired Bug description: The cursor is also not shown, neither is the Unity 8 Lock Screen or Indicators. Ubuntu 16.04 Daily ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8-desktop-session-mir 1.0.12+15.10.20150609-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.3-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 23 18:44:45 2016 InstallationDate: Installed on 2016-01-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: unity8-desktop-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537389/+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 1631436] Re: Some network configuration cmdline arguments doesn't work anymore with version 0.122ubuntu8.3
*** This bug is a duplicate of bug 1631474 *** https://bugs.launchpad.net/bugs/1631474 I'd really appreciate if you tested the ppa available in bug 1631474, and reported back. I don't have access to a full nfsroot environment so this would be very helpful. Also, Please move back to the ip=:eth0:dhcp, as this should be working once more. IP=eth0, is an undocumented behavior, and ip=:eth0:dhcp should be more universally accepted. Thanks, Dave -- 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/1631436 Title: Some network configuration cmdline arguments doesn't work anymore with version 0.122ubuntu8.3 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: In the past, until the version 0.122ubuntu8.1, we used the syntax "ip=:eth0:dhcp" as described in the kernel's documentation : https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt The version 0.122ubuntu8.3 breaks it. It works only with "ip=eth0" syntax as far as i have tested it. So, the current last package version leaves the machine without network on boot. Any host that needs network on boot (nfsroot / using dropbear for example) might not boot properly. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631436/+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 1628790] Re: Changing the user settings to autologin on Lubuntu 16.04 causes LightDM to get stuck in a login loop
OK I changed my account to an admin in hopes it would stop. But it still gets stuck in the loop as soon as the Auto-Login feature is turned on in Lubuntu. Anyway, "ls .Xauthority -l" returns with: -rw--- 1 joel joel 55 Oct 8 12:35 .Xauthority. -- 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/1628790 Title: Changing the user settings to autologin on Lubuntu 16.04 causes LightDM to get stuck in a login loop Status in lightdm package in Ubuntu: Incomplete Bug description: After setting my account to login automatically through the user and groups setting in Lubuntu. After the computer reboots it gets stuck in a loop on the login screen. Logging in will just send you back to the same screen. The only way I could fix the issue was to press CRTL + ALT + F1, logging in through the CLI and typing: "sudo mv .Xauthority .Xauthority.bak" and then once I was back to the login screen I was able to login and turn the setting off. I did check to see weather that was what caused it, by restarting the computer without turning off the auto-login. However the same issue happened and only turning off auto-login would stop the login loop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1628790/+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 + 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. -- 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: New 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
** Patch added: "lp1631474.yakkety.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757084/+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: New Bug description: 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 fixed up the comment, and the changelog comment and resubmit the debdiff. ** Patch added: "lp1631474.xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757083/+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: New Bug description: 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
** Patch removed: "lp1631474.xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757065/+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: New Bug description: 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 1624571] Re: White lines visible around LibreOffice toolbars in when using GTK3
This bug was fixed in the package ubuntu-themes - 16.10+16.10.20161007-0ubuntu1 --- ubuntu-themes (16.10+16.10.20161007-0ubuntu1) yakkety; urgency=medium [ Martin Wimpress ] * Fix borders of Libreoffice toolbars, so that they don't overlap the window decorations (LP: #1624571) -- i...@orangesquash.org.uk (i...@orangesquash.org.uk) Fri, 07 Oct 2016 16:30:52 + ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1624571 Title: White lines visible around LibreOffice toolbars in when using GTK3 Status in ubuntu-mate: Triaged Status in libreoffice package in Ubuntu: Triaged Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: There are some portions where the theme is not consistent like on the right side "x" and so on. In the pictures you will see a comparation side by side with UBUNTU Mate 16.04 with Mate 1.14 gtk2 ppa The top bar from the picture it's from 16.10 and the next bar it's from 16.04 OS: Ubuntu 16.10 daily Interface : Mate 1.15.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1624571/+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 1561861] Re: ListItemLayout documentation: UbuntuColors.Orange should be UbuntuColors.orange instead
It was great to see that it was fixed :) Thanks for your work. -- 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/1561861 Title: ListItemLayout documentation: UbuntuColors.Orange should be UbuntuColors.orange instead Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.ListItemLayout/ The code: ListItemLayout { id: layout title.text: "Hello..." title.color: UbuntuColors.Orange subtitle.text: "...world!" Rectangle { SlotsLayout.position: SlotsLayout.Leading color: "pink" height: units.gu(6) width: height } UbuntuColors.Orange should be Ubuntu.orange Best regards, XiaoGuo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1561861/+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 1627942] Re: unity8 of 16.10 can't start, keep black screen, lenovo R61i
dmesg: [ 174.877153] unity8-dash[2728]: segfault at 70 ip 7f67d497c984 sp 7ffe8895e3b0 error 6 in libQt5Core.so.5.6.1[7f67d48d7000+4c6000] [ 187.475845] unity8-dash[3101]: segfault at 70 ip 7f12fdb74984 sp 7ffc0544c3e0 error 6 in libQt5Core.so.5.6.1[7f12fdacf000+4c6000] [ 238.719537] perf: interrupt took too long (2551 > 2500), lowering kernel.perf_event_max_sample_rate to 78250 [ 252.793405] unity8-dash[4714]: segfault at 70 ip 7fd3ddb34984 sp 7ffd4bfcfab0 error 6 in libQt5Core.so.5.6.1[7fd3dda8f000+4c6000] [ 265.401260] unity8-dash[5023]: segfault at 70 ip 7f56dffc8984 sp 7ffca23a0100 error 6 in libQt5Core.so.5.6.1[7f56dff23000+4c6000] [ 277.993564] unity8-dash[5320]: segfault at 70 ip 7fbb5032b984 sp 7ffe802a2800 error 6 in libQt5Core.so.5.6.1[7fbb50286000+4c6000] [ 285.183803] perf: interrupt took too long (3191 > 3188), lowering kernel.perf_event_max_sample_rate to 62500 [ 290.306736] unity8-dash[5626]: segfault at 70 ip 7ff01a195984 sp 7fff65fefc60 error 6 in libQt5Core.so.5.6.1[7ff01a0f+4c6000] [ 302.666145] unity8-dash[5914]: segfault at 70 ip 7f9a042c0984 sp 7ffc955e49b0 error 6 in libQt5Core.so.5.6.1[7f9a0421b000+4c6000] [ 589.612686] perf: interrupt took too long (4009 > 3988), lowering kernel.perf_event_max_sample_rate to 49750 [ 591.084779] unity8-dash[7350]: segfault at 70 ip 7fe60eb3e984 sp 7ffc14829ec0 error 6 in libQt5Core.so.5.6.1[7fe60ea99000+4c6000] [ 603.828240] unity8-dash[7646]: segfault at 7fec58a680f8 ip 7fec75ad29e5 sp 7fff71748c80 error 7 in libQt5Core.so.5.6.1[7fec75a2d000+4c6000] [ 616.516594] unity8-dash[7942]: segfault at 7f6e06de70f8 ip 7f6e2be529e5 sp 7fff70319a20 error 7 in libQt5Core.so.5.6.1[7f6e2bdad000+4c6000] [ 628.953358] unity8-dash[8244]: segfault at 70 ip 7f6b8ffcf984 sp 7ffc0625b4c0 error 6 in libQt5Core.so.5.6.1[7f6b8ff2a000+4c6000] [ 641.422200] unity8-dash[8555]: segfault at 70 ip 7f33199dc984 sp 7ffcaa9970a0 error 6 in libQt5Core.so.5.6.1[7f3319937000+4c6000] [ 784.955520] unity8-dash[9150]: segfault at 70 ip 7f89bff92984 sp 7fff3afe0aa0 error 6 in libQt5Core.so.5.6.1[7f89bfeed000+4c6000] [ 797.465281] unity8-dash[9447]: segfault at 70 ip 7fb0398f5984 sp 7ffdb842a230 error 6 in libQt5Core.so.5.6.1[7fb03985+4c6000] [ 805.024075] perf: interrupt took too long (5044 > 5011), lowering kernel.perf_event_max_sample_rate to 39500 [ 978.238697] unity8-dash[10912]: segfault at 70 ip 7f43bb016984 sp 7e7825e0 error 6 in libQt5Core.so.5.6.1[7f43baf71000+4c6000] [ 990.879361] unity8-dash[11204]: segfault at 70 ip 7fd662f71984 sp 7ffc818d0270 error 6 in libQt5Core.so.5.6.1[7fd662ecc000+4c6000] [ 1003.224196] unity8-dash[11499]: segfault at 7f1bf7614898 ip 7f1bf71f19e5 sp 7ffc750c4ba0 error 7 in libQt5Core.so.5.6.1[7f1bf714c000+4c6000] [ 1015.860341] unity8-dash[11797]: segfault at f000a ip 7f2ddaa839c8 sp 7ffef440be70 error 4 in libQt5Core.so.5.6.1[7f2dda9de000+4c6000] [ 1028.268991] unity8-dash[12096]: segfault at 70 ip 7f65ed456984 sp 7ffe9af22410 error 6 in libQt5Core.so.5.6.1[7f65ed3b1000+4c6000] [ 1040.622650] unity8-dash[12390]: segfault at 70 ip 7f717cdfa984 sp 7ffc422af5c0 error 6 in libQt5Core.so.5.6.1[7f717cd55000+4c6000] [ 1053.315821] unity8-dash[12690]: segfault at 1a0017 ip 7f3536d579c8 sp 7ffcf0c99a80 error 4 in libQt5Core.so.5.6.1[7f3536cb2000+4c6000] [ 1065.776643] unity8-dash[12997]: segfault at 55ef000a ip 7fa89c1989c8 sp 7fffac69db70 error 4 in libQt5Core.so.5.6.1[7fa89c0f3000+4c6000] [ 1078.308189] unity8-dash[13290]: segfault at 70 ip 7f6d8a223984 sp 7ffe1500d870 error 6 in libQt5Core.so.5.6.1[7f6d8a17e000+4c6000] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1627942 Title: unity8 of 16.10 can't start, keep black screen, lenovo R61i Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: I only install openbox, LXQT and Unity8 session. LxQt is fine. After input password, The screen is black few seconds. Next in screen there are is a small rectangle with text "Scope". Next In the rectangle there is a ubuntu arc logo is rolling. Next the rolling logo is frozen. Next all are black few seconds. From a ssh console ,I can see the cpu rate of unity8, unity8.dash or applet.y is very high(70% --100%) And again and again. If anybody need more info, comments on the issue. This is its upstart.log: [2016-09-27:13:35:18.182] qtmir.screens: ScreensModel::ScreensModel [2016-09-27 13:35:18.198252] mirplatform: Found graphics driver: mir:mesa-kms (version 0.24.0) [2016-09-27 13:35:18.198494] mirplatform: Found graphics driver: mir:mesa-x11 (version 0.24.0) [2016-09-27:13:35:18.200] qtmir.mir: MirS
[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
The attachment "lp1631474.xenial.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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: New Bug description: 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 1631553] Re: With UFW enabled, kernel reports SYN flooding
Oh, relevant tickets from UFW and procps: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/57091 https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/189565 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1631553 Title: With UFW enabled, kernel reports SYN flooding Status in ufw package in Ubuntu: New Bug description: So, this is a fun one. I have an Epson XP-610 multifunction scanner/printer/coffeemaker/whiskey distillery. It uses an XSane plugin, which spawns an intermediary network app (/usr/lib/iscan/network) which detects and talks to the scanner. These packages can all be obtained from here: http://support.epson.net/linux/en/iscan_c.html. Anyway, if you have UFW disabled, it works. If you enable UFW, however it works intermittently and takes forever to start up. Checking my syslog, I find: Oct 6 22:48:00 hiro kernel: [48176.543355] TCP: request_sock_TCP: Possible SYN flooding on port 40796. Dropping request. Check SNMP counters. A wireshark capture shows two things: 1.) It is communicating on that port on the "lo" interface, not any real interface. 2.) There's one SYN. Not a lot. Just a single SYN. And then TCP retries. And then eventually it works. Sometimes. Anyway, if I edit /etc/ufw/sysctl.conf, and set net/ipv4/tcp_syncookies=1, and then disable and reenable UFW, it works, with the following syslog entry: Oct 7 20:26:18 hiro kernel: [13666.745140] TCP: request_sock_TCP: Possible SYN flooding on port 42751. Sending cookies. Check SNMP counters. Now, to be clear, I think the syncookies is a workaround for a more serious problem. Namely, why does the kernel think it's under attack to begin with? Anyway, I'm not certain this is really a UFW bug, but I'm starting here because UFW seems to make it worse. Feel free to reclassify as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ufw 0.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Oct 7 20:20:00 2016 PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to xenial on 2016-09-30 (7 days ago) mtime.conffile..etc.ufw.sysctl.conf: 2016-10-06T23:11:58.680226 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1631553/+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 1631553] [NEW] With UFW enabled, kernel reports SYN flooding
Public bug reported: So, this is a fun one. I have an Epson XP-610 multifunction scanner/printer/coffeemaker/whiskey distillery. It uses an XSane plugin, which spawns an intermediary network app (/usr/lib/iscan/network) which detects and talks to the scanner. These packages can all be obtained from here: http://support.epson.net/linux/en/iscan_c.html. Anyway, if you have UFW disabled, it works. If you enable UFW, however it works intermittently and takes forever to start up. Checking my syslog, I find: Oct 6 22:48:00 hiro kernel: [48176.543355] TCP: request_sock_TCP: Possible SYN flooding on port 40796. Dropping request. Check SNMP counters. A wireshark capture shows two things: 1.) It is communicating on that port on the "lo" interface, not any real interface. 2.) There's one SYN. Not a lot. Just a single SYN. And then TCP retries. And then eventually it works. Sometimes. Anyway, if I edit /etc/ufw/sysctl.conf, and set net/ipv4/tcp_syncookies=1, and then disable and reenable UFW, it works, with the following syslog entry: Oct 7 20:26:18 hiro kernel: [13666.745140] TCP: request_sock_TCP: Possible SYN flooding on port 42751. Sending cookies. Check SNMP counters. Now, to be clear, I think the syncookies is a workaround for a more serious problem. Namely, why does the kernel think it's under attack to begin with? Anyway, I'm not certain this is really a UFW bug, but I'm starting here because UFW seems to make it worse. Feel free to reclassify as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ufw 0.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Oct 7 20:20:00 2016 PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to xenial on 2016-09-30 (7 days ago) mtime.conffile..etc.ufw.sysctl.conf: 2016-10-06T23:11:58.680226 ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1631553 Title: With UFW enabled, kernel reports SYN flooding Status in ufw package in Ubuntu: New Bug description: So, this is a fun one. I have an Epson XP-610 multifunction scanner/printer/coffeemaker/whiskey distillery. It uses an XSane plugin, which spawns an intermediary network app (/usr/lib/iscan/network) which detects and talks to the scanner. These packages can all be obtained from here: http://support.epson.net/linux/en/iscan_c.html. Anyway, if you have UFW disabled, it works. If you enable UFW, however it works intermittently and takes forever to start up. Checking my syslog, I find: Oct 6 22:48:00 hiro kernel: [48176.543355] TCP: request_sock_TCP: Possible SYN flooding on port 40796. Dropping request. Check SNMP counters. A wireshark capture shows two things: 1.) It is communicating on that port on the "lo" interface, not any real interface. 2.) There's one SYN. Not a lot. Just a single SYN. And then TCP retries. And then eventually it works. Sometimes. Anyway, if I edit /etc/ufw/sysctl.conf, and set net/ipv4/tcp_syncookies=1, and then disable and reenable UFW, it works, with the following syslog entry: Oct 7 20:26:18 hiro kernel: [13666.745140] TCP: request_sock_TCP: Possible SYN flooding on port 42751. Sending cookies. Check SNMP counters. Now, to be clear, I think the syncookies is a workaround for a more serious problem. Namely, why does the kernel think it's under attack to begin with? Anyway, I'm not certain this is really a UFW bug, but I'm starting here because UFW seems to make it worse. Feel free to reclassify as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ufw 0.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Oct 7 20:20:00 2016 PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to xenial on 2016-09-30 (7 days ago) mtime.conffile..etc.ufw.sysctl.conf: 2016-10-06T23:11:58.680226 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1631553/+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 57091] Re: proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to permit SYN flood defense...
Will do, Simon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/57091 Title: proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to permit SYN flood defense... Status in procps package in Ubuntu: Fix Released Bug description: This is intended to be a 'wishlist' wulnerability -- w.r.t. procps and Edgy. In my opinion,the /etc/sysctl.conf should have 'proc/sys/net/ipv4/tcp_syncookies=1' in order to permit the linux SYNcookies syn-flood trivial DoS attack to be mitigated as-necessary, by default. Note that the disadvantages of connections initiated w/ SYNcookies enabled only apply when the system is under attack (SYN queue getting rather full), as the syncookies reply-with-only-one-SYN+ACK behaviour only 'kicks in' when the system has a SYN_RECVD backlog problem. (If SYNcookies were not permitted incoming TCP connections have a very low chance of succeeding at all while under SYN-flood attack). Without this setting enabled, any TCP services on the machine can be DoSed from a dial-up line sending a stream of SYN packets from weird source addresses to open TCP ports like Samba/VNC/http/whatever Does anybody have any legitimate reason tcp_syncookies should be disabled? Some people claimed that SYNcookies break some RFCs once but I have not seen any evidence to this effect, only notes from djb saying that this is not true. Comments wanted please ;-) Thankyou in advance, -- enyc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/57091/+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 with the PPA and it looks good in an initial test. Before, upgrading initramfs-tools and rebooting would result in AWS instance being unreachable. Now, it looks good! $ 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+lp1631474all generic modular initramfs generator (automation) ii initramfs-tools-bin 0.122ubuntu8.3+lp1631474amd64 binaries used by initramfs-tools ii initramfs-tools-core 0.122ubuntu8.3+lp1631474all 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: New Bug description: 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
** Patch added: "lp1631474.xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757065/+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: New Bug description: 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 created a PPA with a proposed solution to this issue. If I could get some testing with this ppa I would appreciate it. Additionally if you test the ppa please report back and include your /proc/cmdline in your comment. Thank you, Dave Chiluk -- 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: New Bug description: 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
Woops I forgot to include the PPA https://launchpad.net/~chiluk/+archive/ubuntu/lp1631474 I will remove this ppa when the package hits -proposed. -- 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: New Bug description: 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 1627056] Re: 48 webbrowser_app autopilot test failures on krillin in CI
When flashing image 405 (with --bootstrap) and then upgrading to image 406 with: ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/meizu.en --revision 406 then the autopilot tests pass. So there is something when bootstrapping image 406 and higher, which doesn’t happen when simply upgrading older images. -- 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/1627056 Title: 48 webbrowser_app autopilot test failures on krillin in CI Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The autopilot tests for webbrowser_app have been failing in CI (system-apps jenkins instance) for about a month. Before that they reliably passed. They are being run on a krillin device that is being flashed anew for every single run. The device hasn’t changed. The last known successful run was on August 10: https://jenkins.canonical.com/system-apps/job/test-0-autopkgtest/243/. The next run on a webbrowser-app branch didn’t happen until August 27, and it failed: https://jenkins.canonical.com/system- apps/job/test-0-autopkgtest/308/. Something happened in between those two dates that broke the tests. It might be something in the infrastructure rather than in webbrowser-app itself, given that the tests all pass when run on my krillin at home. I am attaching the full log for the first failing run on August 27. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627056/+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 1631328] Re: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration"
I think the right answer here is for ceph-osd to Pre-Depend: on ceph- common which sets up the users, then there's no need to reload because the rules will parse correctly the first time. Also, in looking at the binary package, I don't see anywhere that ceph- osd ever calls 'udevadm trigger --subsystem-match=block --action=change' - this still needs to be explicitly done, independent of the reload handling (or not), in order to apply the newly-installed rules to existing devices. -- 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/1631328 Title: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration" Status in ceph package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Status in ceph-osd package in Juju Charms Collection: Invalid Bug description: The "ceph/default," "ceph_radosgw/simple_nonha" and "ceph/harden" mojo specs @ Yakkety are failing like so: Units are consistently blocked in Juju status: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration" Snippets from ceph-osd unit syslog: mkjournal error creating journal on /var/lib/ceph/tmp/mnt.W59Jhd/journal: (13) Permission denied Oct 7 03:13:30 juju-osci-sv13-machine-4 systemd[1]: Failed to start Ceph disk activation: /dev/vdb1. See: http://pastebin.ubuntu.com/23288515/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1631328/+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 1627056] Re: 48 webbrowser_app autopilot test failures on krillin in CI
I can reproduce the failures on my arale after reflashing it with --bootstrap. I did some bisecting, and the issue started happening with image 406 (http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/406.commitlog). -- 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/1627056 Title: 48 webbrowser_app autopilot test failures on krillin in CI Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The autopilot tests for webbrowser_app have been failing in CI (system-apps jenkins instance) for about a month. Before that they reliably passed. They are being run on a krillin device that is being flashed anew for every single run. The device hasn’t changed. The last known successful run was on August 10: https://jenkins.canonical.com/system-apps/job/test-0-autopkgtest/243/. The next run on a webbrowser-app branch didn’t happen until August 27, and it failed: https://jenkins.canonical.com/system- apps/job/test-0-autopkgtest/308/. Something happened in between those two dates that broke the tests. It might be something in the infrastructure rather than in webbrowser-app itself, given that the tests all pass when run on my krillin at home. I am attaching the full log for the first failing run on August 27. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627056/+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 1627056] Re: 48 webbrowser_app autopilot test failures on krillin in CI
I’m attaching the commit log for image 406 (arale), which contains numerous changes. ** Attachment added: "406.commitlog.txt" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627056/+attachment/4757039/+files/406.commitlog.txt -- 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/1627056 Title: 48 webbrowser_app autopilot test failures on krillin in CI Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The autopilot tests for webbrowser_app have been failing in CI (system-apps jenkins instance) for about a month. Before that they reliably passed. They are being run on a krillin device that is being flashed anew for every single run. The device hasn’t changed. The last known successful run was on August 10: https://jenkins.canonical.com/system-apps/job/test-0-autopkgtest/243/. The next run on a webbrowser-app branch didn’t happen until August 27, and it failed: https://jenkins.canonical.com/system- apps/job/test-0-autopkgtest/308/. Something happened in between those two dates that broke the tests. It might be something in the infrastructure rather than in webbrowser-app itself, given that the tests all pass when run on my krillin at home. I am attaching the full log for the first failing run on August 27. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627056/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
Right. Can you please install the version from -proposed (see comment #20) and check if that fixes it, i. e. net.ifnames=0 then gets respected? -- 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/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd package in Debian: Fix Released Bug description: Description:Ubuntu 16.04 LTS Release:16.04 The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB devices. It appears the regression is here: * Set MAC based name for USB network interfaces only for universally administered (i. e. stable) MACs, not for locally administered (i. e. randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link (as link files don't currently support globs for MACAddress=) and replace with an udev rule in /lib/udev/rules.d/73-special-net-names.rules. (Closes: #812575, LP: #1574483) As Raspberry Pi's use eth0 via USB, this breaks running systems. Before: ii systemd229-4ubuntu4 armhfsystem and service manager ii udev 229-4ubuntu4 armhf/dev/ and hotplug management daem 3: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff After: ii systemd 229-4ubuntu6armhf system and service manager ii udev 229-4ubuntu6armhf /dev/ and hotplug management daemon 3: enxb827eb1639e9: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff cat /proc/cmdline dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait With the default interfaces configuration, all networking is lost on reboot after upgrade. SRU TEST CASE = * Boot with "net.ifnames=0" on the kernel command line, and connect an USB ethernet device. It will still be called enxDEADBEEF with current xenial. With the -proposed version it will instead keep the kernel name, like "usb0" as intended. * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules" (the other documented way to disable ifnames) and do the above connect/name check test again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1627056] Re: 48 webbrowser_app autopilot test failures on krillin in CI
** Changed in: webbrowser-app (Ubuntu) Importance: Undecided => High -- 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/1627056 Title: 48 webbrowser_app autopilot test failures on krillin in CI Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The autopilot tests for webbrowser_app have been failing in CI (system-apps jenkins instance) for about a month. Before that they reliably passed. They are being run on a krillin device that is being flashed anew for every single run. The device hasn’t changed. The last known successful run was on August 10: https://jenkins.canonical.com/system-apps/job/test-0-autopkgtest/243/. The next run on a webbrowser-app branch didn’t happen until August 27, and it failed: https://jenkins.canonical.com/system- apps/job/test-0-autopkgtest/308/. Something happened in between those two dates that broke the tests. It might be something in the infrastructure rather than in webbrowser-app itself, given that the tests all pass when run on my krillin at home. I am attaching the full log for the first failing run on August 27. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627056/+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 1631519] Re: No X on boot with external monitor connected
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1631519 ** Tags added: iso-testing -- 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/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 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 Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO 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 xserver.bootTime: Fri Oct 7 20:18:12 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/1631519/+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
As asked by chiluk on IRC, here's my PXE boot configuration (well, representative one anyway, the exact kernel version will obviously change): DEFAULT ubuntu LABEL ubuntu LINUX vmlinuz-4.4.0-36-generic APPEND initrd=initrd.img-4.4.0-36-generic root=/dev/nfs nfsroot=10.17.76.1:/var/lib/tribble/ephemeral ip=dhcp ro nomodeset net.ifnames=0 IPAPPEND 2 -- 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: New Bug description: 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
** Also affects: initramfs-tools (Ubuntu Xenial) 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/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: New Bug description: 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 1631519] Re: No X on boot with external monitor connected
A monitor attached to the Thinkpad x230 via the docking station DVI port is fine (boots to X and no crazy window trails). This is seen when attaching a monitor via DP on the dock or mDP from the laptop. I was using an mDP to HDMI cable or a DP to DualLink-DVI adapter to connect monitors when I found this issue. Multiple monitors were tried and all experienced the issue when connect to the monitor's HDMI port from the laptop's mDP port. -- 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/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 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 Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO 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 xserver.bootTime: Fri Oct 7 20:18:12 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/1631519/+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 1631519] Re: No X on boot with external monitor connected
The attached gif tries to show the effect of moving a window across the screen. Not captured in the low-framerate gif is that the trails of the window are flickering and moving (compiz cpu usage is high when this happens). Hitting WIN+w to display windows and then drop back to the desktop clears the current trail. But that is not a reasonable workaround and does not address the basic issue that the livecd (or a fully installed desktop) does not boot to X with an external monitor attached. -- 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/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 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 Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO 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 xserver.bootTime: Fri Oct 7 20:18:12 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/1631519/+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 1631519] Re: No X on boot with external monitor connected
** Attachment added: "moving a window across the display" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+attachment/4757009/+files/ezgif.com-video-to-gif%20%282%29.gif -- 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/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 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 Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO 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 xserver.bootTime: Fri Oct 7 20:18:12 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/1631519/+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 1631528] [NEW] Blank screen after grub menu
Public bug reported: After a fresh install of Ubuntu Mate 16.04.1 on my laptop I have some problems booting. After the grub menu the screen goes blank and nothing happens after that. I think the system is booting properly apart from the screen not showing anything, I can change the volume using the hardware keys and I can connect with SSH from another machine. I've found two workarounds for this problem. 1) Select recovery mode from the grub meny and then resume normal boot, however, the screen resolution is not set properly. 2) Change my grub config file to boot into text mode. I commented out the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" and changed GRUB_CMDLINE_LINUX="" to GRUB_CMDLINE_LINUX=”text" and uncommented the line #GRUB_TERMINAL=console After running sudo update-grub and rebooting the system boots into MATE and the correct screen resolution is set. I've collected dmesg after a "blank screen" boot, let me know if there is anything else I should provide. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Fri Oct 7 22:41:04 2016 InstallationDate: Installed on 2016-10-06 (1 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze xenial ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/1631528/+attachment/4757005/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631528 Title: Blank screen after grub menu Status in xorg package in Ubuntu: New Bug description: After a fresh install of Ubuntu Mate 16.04.1 on my laptop I have some problems booting. After the grub menu the screen goes blank and nothing happens after that. I think the system is booting properly apart from the screen not showing anything, I can change the volume using the hardware keys and I can connect with SSH from another machine. I've found two workarounds for this problem. 1) Select recovery mode from the grub meny and then resume normal boot, however, the screen resolution is not set properly. 2) Change my grub config file to boot into text mode. I commented out the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" and changed GRUB_CMDLINE_LINUX="" to GRUB_CMDLINE_LINUX=”text" and uncommented the line #GRUB_TERMINAL=console After running sudo update-grub and rebooting the system boots into MATE and the correct screen resolution is set. I've collected dmesg after a "blank screen" boot, let me know if there is anything else I should provide. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Fri Oct 7 22:41:04 2016 InstallationDate: Installed on 2016-10-06 (1 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631528/+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: ubuntu-touch-session (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:~mterry/ubuntu-touch-session/pulse-in-snap -- 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 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 1631436] Re: Some network configuration cmdline arguments doesn't work anymore with version 0.122ubuntu8.3
*** This bug is a duplicate of bug 1631474 *** https://bugs.launchpad.net/bugs/1631474 Marking as duplicate of 1631474 as I'm already working this over there. Normally we'd dupe the newer against the older, but I'm already working over there, and I don't want to lose history in the switch. ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Dave Chiluk (chiluk) ** This bug has been marked a duplicate of bug 1631474 No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option -- 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/1631436 Title: Some network configuration cmdline arguments doesn't work anymore with version 0.122ubuntu8.3 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: In the past, until the version 0.122ubuntu8.1, we used the syntax "ip=:eth0:dhcp" as described in the kernel's documentation : https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt The version 0.122ubuntu8.3 breaks it. It works only with "ip=eth0" syntax as far as i have tested it. So, the current last package version leaves the machine without network on boot. Any host that needs network on boot (nfsroot / using dropbear for example) might not boot properly. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631436/+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 1631519] Re: No X on boot with external monitor connected
** Summary changed: - xorg hall-of-mirrors on external display + No X on boot with external monitor connected ** Description changed: - Running from today's (201610907) daily yakkety livecd I can boot to the - desktop if only using the laptop's LCD (ThinkPad x230, intel graphics). - Attaching a 1920x1080 LCD via miniDP extends the desktop but windows - moved around produce a trail of windows that persist even after the - window is closed. + When booting from today's (201610907) daily yakkety livecd with an + external display attached X does not start. - Also, when booting from the livecd with the external display attached X - does not start. + If the external monitor is attached after X has started I can boot to + the desktop using only using the laptop's LCD (ThinkPad x230, intel + graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop + but windows moved around produce a trail of windows that persist even + after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: - Installed: 1:7.7+13ubuntu4 - Candidate: 1:7.7+13ubuntu4 - Version table: - *** 1:7.7+13ubuntu4 500 - 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:7.7+13ubuntu4 + Candidate: 1:7.7+13ubuntu4 + Version table: + *** 1:7.7+13ubuntu4 500 + 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 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 Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO 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 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset ** Changed in: xorg (Ubuntu) Importance: Undecided => 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.launch
[Touch-packages] [Bug 1493999] Re: xz-utils package is really, really old and should be updated to 5.2.2 with multi-core support
** Changed in: xz-utils (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1493999 Title: xz-utils package is really, really old and should be updated to 5.2.2 with multi-core support Status in xz-utils package in Ubuntu: Triaged Status in xz-utils package in Debian: Fix Released Bug description: Willy is currently using a really old version of xz-utils. The latest version at this time is 5.2.2, released in September 2015. With multi-core support it adds an important feature for xz. http://git.tukaani.org/?p=xz.git;a=blob;f=NEWS;hb=HEAD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1493999/+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 1631519] [NEW] No X on boot with external monitor connected
Public bug reported: Running from today's (201610907) daily yakkety livecd I can boot to the desktop if only using the laptop's LCD (ThinkPad x230, intel graphics). Attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. Also, when booting from the livecd with the external display attached X does not start. This is a regression from Xenial. $ lsb_release -rd Description:Ubuntu Yakkety Yak (development branch) Release:16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 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 Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO 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 xserver.bootTime: Fri Oct 7 20:18:12 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 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/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: Running from today's (201610907) daily yakkety livecd I can boot to the desktop if only using the laptop's LCD (ThinkPad x230, intel graphics). Attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. Also, when booting from the livecd with the external display attached X does not start. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd
[Touch-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
** Attachment added: "_usr_bin_media-hub-server.32011.crash" https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1544477/+attachment/4756983/+files/_usr_bin_media-hub-server.32011.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtmultimedia-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Fix Released Status in indicator-sound package in Ubuntu: Invalid Status in media-hub package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in qtmultimedia-opensource-src package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
http://paste.ubuntu.com/23290548/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtmultimedia-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Fix Released Status in indicator-sound package in Ubuntu: Invalid Status in media-hub package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in qtmultimedia-opensource-src package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1627056] Re: 48 webbrowser_app autopilot test failures on krillin in CI
** Changed in: webbrowser-app (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1627056 Title: 48 webbrowser_app autopilot test failures on krillin in CI Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The autopilot tests for webbrowser_app have been failing in CI (system-apps jenkins instance) for about a month. Before that they reliably passed. They are being run on a krillin device that is being flashed anew for every single run. The device hasn’t changed. The last known successful run was on August 10: https://jenkins.canonical.com/system-apps/job/test-0-autopkgtest/243/. The next run on a webbrowser-app branch didn’t happen until August 27, and it failed: https://jenkins.canonical.com/system- apps/job/test-0-autopkgtest/308/. Something happened in between those two dates that broke the tests. It might be something in the infrastructure rather than in webbrowser-app itself, given that the tests all pass when run on my krillin at home. I am attaching the full log for the first failing run on August 27. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627056/+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 1631302] Re: System becomes unresponsive when running code with deep-recursion under unprivileged user
I tested in Ubuntu 12.04 (but different hardware). Not affected. Everything works - keyboard, mouse, Ctrl-C. ** Description changed: In Ubuntu 16.04 if you run perl -e 'sub x { x() }; x()' (this commands does a deep recursion, eats all memory) under non-root user whole system becomes unresponsive, mouse, keyboard does not work. Screen does not update when you plug/unplug charger, for example. The only way to quit is to press power button and shut down machine. Expected bahaviour: Ctrl-C, Ctrl-Alt-Del, Ctrl-Alt-F1, mouse, at least something should work. - Repsoduced on HP Pavilion 16, SSD with encryption, encrypted Swap. + Repsoduced on HP Pavilion 15, SSD with encryption, encrypted Swap. Reproduced by at least one another person with Ubuntu 16.04 with SSD. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1631302 Title: System becomes unresponsive when running code with deep-recursion under unprivileged user Status in perl package in Ubuntu: New Bug description: In Ubuntu 16.04 if you run perl -e 'sub x { x() }; x()' (this commands does a deep recursion, eats all memory) under non-root user whole system becomes unresponsive, mouse, keyboard does not work. Screen does not update when you plug/unplug charger, for example. The only way to quit is to press power button and shut down machine. Expected bahaviour: Ctrl-C, Ctrl-Alt-Del, Ctrl-Alt-F1, mouse, at least something should work. Repsoduced on HP Pavilion 15, SSD with encryption, encrypted Swap. Reproduced by at least one another person with Ubuntu 16.04 with SSD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1631302/+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 1631208] Re: Tabs in Firefox add-ons are not rendered
As I just discovered & noted in https://bugzilla.mozilla.org/show_bug.cgi?id=1306425#c10 , this doesn't actually require any Firefox add-ons -- you can reproduce it in Firefox's "Certificate Viewer" UI, too. Anyway -- I'm glad we've got a fix in the pipeline here! Thanks, Martin! ** Bug watch added: Mozilla Bugzilla #1306425 https://bugzilla.mozilla.org/show_bug.cgi?id=1306425 ** Summary changed: - Tabs in Firefox add-ons are not rendered + Tabs in Firefox dialogs are not rendered (for add-on options & Certificate Viewer) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1631208 Title: Tabs in Firefox dialogs are not rendered (for add-on options & Certificate Viewer) Status in ubuntu-themes package in Ubuntu: In Progress Bug description: Tabs in the preference dialogues of Firefox add-on don't render anymore in Ubuntu 16.10. Here is the upstream bug report: * https://bugzilla.mozilla.org/show_bug.cgi?id=1306425 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1631208/+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 1631504] [NEW] loadkeys segfaults with certain arguments in 16.10
Public bug reported: This can be reproduced as follows: 1) Switch to VT 1 (ctrl+alt+f1) 2) run: loadkeys garbage 3) loadkeys will segfault The problem appears to be with the implicit declaration of xmalloc in loadkeys.c. It is resolved if #include "xmalloc.h" is added to the top of that file (and in fact all the other source files in kbd that reference xmalloc include that file). Interestingly xmalloc is resolved without include but the returned pointer seems to get truncated. It doesn't do this if the source is built with gcc 5.4 in 16.04 so maybe it has something to do with gcc 6.2 in 16.10. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: kbd 2.0.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 7 15:27:58 2016 InstallationDate: Installed on 2016-10-06 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161006) SourcePackage: kbd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kbd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1631504 Title: loadkeys segfaults with certain arguments in 16.10 Status in kbd package in Ubuntu: New Bug description: This can be reproduced as follows: 1) Switch to VT 1 (ctrl+alt+f1) 2) run: loadkeys garbage 3) loadkeys will segfault The problem appears to be with the implicit declaration of xmalloc in loadkeys.c. It is resolved if #include "xmalloc.h" is added to the top of that file (and in fact all the other source files in kbd that reference xmalloc include that file). Interestingly xmalloc is resolved without include but the returned pointer seems to get truncated. It doesn't do this if the source is built with gcc 5.4 in 16.04 so maybe it has something to do with gcc 6.2 in 16.10. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: kbd 2.0.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 7 15:27:58 2016 InstallationDate: Installed on 2016-10-06 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161006) SourcePackage: kbd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1631504/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
I'm on systemd 229-4ubuntu10 -- 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/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd package in Debian: Fix Released Bug description: Description:Ubuntu 16.04 LTS Release:16.04 The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB devices. It appears the regression is here: * Set MAC based name for USB network interfaces only for universally administered (i. e. stable) MACs, not for locally administered (i. e. randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link (as link files don't currently support globs for MACAddress=) and replace with an udev rule in /lib/udev/rules.d/73-special-net-names.rules. (Closes: #812575, LP: #1574483) As Raspberry Pi's use eth0 via USB, this breaks running systems. Before: ii systemd229-4ubuntu4 armhfsystem and service manager ii udev 229-4ubuntu4 armhf/dev/ and hotplug management daem 3: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff After: ii systemd 229-4ubuntu6armhf system and service manager ii udev 229-4ubuntu6armhf /dev/ and hotplug management daemon 3: enxb827eb1639e9: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff cat /proc/cmdline dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait With the default interfaces configuration, all networking is lost on reboot after upgrade. SRU TEST CASE = * Boot with "net.ifnames=0" on the kernel command line, and connect an USB ethernet device. It will still be called enxDEADBEEF with current xenial. With the -proposed version it will instead keep the kernel name, like "usb0" as intended. * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules" (the other documented way to disable ifnames) and do the above connect/name check test again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1631499] [NEW] package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: Installing new version of config file /etc/X11/Xsession.d/75dbus_dbus-launch ... Setting up gcr (3.18.0-1ubuntu1) ... dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Fri Oct 7 15:22:06 2016 DuplicateSignature: package:libglib2.0-0:i386:2.48.1-1~ubuntu16.04.1:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2014-09-03 (765 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: glib2.0 Title: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-10-07 (0 days ago) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1631499 Title: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: Installing new version of config file /etc/X11/Xsession.d/75dbus_dbus-launch ... Setting up gcr (3.18.0-1ubuntu1) ... dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Fri Oct 7 15:22:06 2016 DuplicateSignature: package:libglib2.0-0:i386:2.48.1-1~ubuntu16.04.1:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2014-09-03 (765 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: glib2.0 Title: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-10-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1631499/+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 1631499] Re: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1631499 Title: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: Installing new version of config file /etc/X11/Xsession.d/75dbus_dbus-launch ... Setting up gcr (3.18.0-1ubuntu1) ... dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Fri Oct 7 15:22:06 2016 DuplicateSignature: package:libglib2.0-0:i386:2.48.1-1~ubuntu16.04.1:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2014-09-03 (765 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: glib2.0 Title: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-10-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1631499/+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 1631491] [NEW] Can't change a configuration option with dconf CLI
Public bug reported: I'm trying to change a configuration option with dconf on command line (to make automatic after that) but always occurs an error: $ dconf write /org/gnome/desktop/interface/monospace-font-name "Noto Mono 10" error: 0-1:unknown keyword Usage: dconf write KEY VALUE ... (all the rest of usage message for write parameter) Works well using dconf-editor, so I think the problem is in the CLI itself. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dconf-cli 0.26.0-2 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 7 16:11:51 2016 InstallationDate: Installed on 2016-05-03 (157 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: d-conf UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: d-conf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1631491 Title: Can't change a configuration option with dconf CLI Status in d-conf package in Ubuntu: New Bug description: I'm trying to change a configuration option with dconf on command line (to make automatic after that) but always occurs an error: $ dconf write /org/gnome/desktop/interface/monospace-font-name "Noto Mono 10" error: 0-1:unknown keyword Usage: dconf write KEY VALUE ... (all the rest of usage message for write parameter) Works well using dconf-editor, so I think the problem is in the CLI itself. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dconf-cli 0.26.0-2 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 7 16:11:51 2016 InstallationDate: Installed on 2016-05-03 (157 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: d-conf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1631491/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
Sorry to say that guys, but... my phone (E4.5 under OTA13) doesn't give a sound any more. Do You want to see any logs before I reboot it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtmultimedia-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Fix Released Status in indicator-sound package in Ubuntu: Invalid Status in media-hub package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in qtmultimedia-opensource-src package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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
** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Dave Chiluk (chiluk) ** Changed in: initramfs-tools (Ubuntu) Status: New => 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 Bug description: 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
Dediff from 8.2 to 8.3. http://launchpadlibrarian.net/286956415/initramfs-tools_0.122ubuntu8.2_0.122ubuntu8.3.diff.gz ** Tags added: cpc sts -- 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: New Bug description: 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
** Tags added: regression-update -- 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: New Bug description: 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
Here's the initial portion of console output, with only a couple of minor redactions related to keys, hostname, MAC address. The most important bit is: ip: SIOCGIFFLAGS: No such device Error getting hardware address for "dhcp": No such device Where the "ip=dhcp" kernel is not being processed correctly per kernel documentation - see https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt === CUT HERE=== [2.179049] registered taskstats version 1 [2.179074] Loading compiled-in X.509 certificates [2.179821] Loaded X.509 cert 'Build time autogenerated kernel key: REDACTED' [2.179848] zswap: loaded using pool lzo/zbud [2.190763] Key type trusted registered [2.195735] Key type encrypted registered [2.195747] AppArmor: AppArmor sha1 policy hashing enabled [2.195753] ima: No TPM chip found, activating TPM-bypass! [2.195778] evm: HMAC attrs: 0x1 [2.213710] blkfront: xvda1: barrier or flush: disabled; persistent grants: disabled; indirect descriptors: enabled; [2.218079] blkfront: xvdb: flush diskcache: enabled; persistent grants: disabled; indirect descriptors: enabled; [2.292145] Magic number: 1:252:3141 [2.292190] hctosys: unable to open rtc device (rtc0) [2.292239] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [2.292244] EDD information not available. [2.292964] Freeing unused kernel memory: 1480K (81f41000 - 820b3000) [2.292973] Write protecting the kernel read-only data: 14336k [2.296529] Freeing unused kernel memory: 1868K (88000182d000 - 880001a0) [2.296620] Freeing unused kernel memory: 176K (880001dd4000 - 880001e0) Loading, please wait... starting version 229 [2.337933] random: udevadm urandom read with 7 bits of entropy available [2.595423] SSE version of gcm_enc/dec engaged. Begin: Loading essential drivers ... [3.942253] md: linear personality registered for level -1 [3.954483] md: multipath personality registered for level -4 [3.957749] md: raid0 personality registered for level 0 [3.975096] md: raid1 personality registered for level 1 [4.059760] raid6: sse2x1 gen() 3697 MB/s [4.124589] raid6: sse2x1 xor() 3003 MB/s [4.192058] raid6: sse2x2 gen() 4609 MB/s [4.260062] raid6: sse2x2 xor() 3242 MB/s [4.335089] raid6: sse2x4 gen() 5511 MB/s [4.400055] raid6: sse2x4 xor() 3912 MB/s [4.400061] raid6: using algorithm sse2x4 gen() 5511 MB/s [4.400064] raid6: xor() 3912 MB/s, rmw enabled [4.400068] raid6: using ssse3x2 recovery algorithm [4.407087] xor: measuring software checksum speed [4.468056]prefetch64-sse: 8536.000 MB/sec [4.524066]generic_sse: 8099.000 MB/sec [4.524076] xor: using function: prefetch64-sse (8536.000 MB/sec) [4.527357] async_tx: api initialized (async) [4.548551] md: raid6 personality registered for level 6 [4.548560] md: raid5 personality registered for level 5 [4.548564] md: raid4 personality registered for level 4 [4.595063] md: raid10 personality registered for level 10 done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [4.687584] Btrfs loaded Scanning for Btrfs filesystems done. Warning: fsck not present, so skipping root file system [4.809766] EXT4-fs (xvda1): mounted filesystem with ordered data mode. Opts: (null) done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... 0 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ ip: SIOCGIFFLAGS: No such device Error getting hardware address for "dhcp": No such device If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ ip: SIOCGIFFLAGS: No such device ip: either "dev" is duplicate, or "permanent" is garbage no link-local IPv6 address for dhcp If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. 0 Warning: overlayroot: debug is busted done. [5.649291] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +G
[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths
** Branch linked: lp:~mterry/unity8/snap-root2 -- 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 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 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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
This was on xenial, unknown if other versions are affected. Related: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631436 https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507 -- 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: New Bug description: 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 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up
This bug was fixed in the package cloud-init - 0.7.8-15-g6e45ffb- 0ubuntu1 --- cloud-init (0.7.8-15-g6e45ffb-0ubuntu1) yakkety; urgency=medium * New upstream snapshot. - systemd: Run cloud-init.service Before dbus.socket not dbus.target [Daniel Watkins] (LP: #1629797). -- Scott Moser Fri, 07 Oct 2016 12:41:38 -0400 ** Changed in: cloud-init (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1629797 Title: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in dbus package in Ubuntu: Triaged Bug description: During boot, cloud-init does DNS resolution checks to if particular metadata services are available (in order to determine which cloud it is running on). These checks happen before systemd-resolved is up[0] and if they resolve unsuccessfully they take 25 seconds to complete. This has substantial impact on boot time in all contexts, because cloud-init attempts to resolve three known-invalid addresses ("does- not-exist.example.com.", "example.invalid." and a random string) to enable it to detect when it's running in an environment where a DNS server will always return some sort of redirect. As such, we're talking a minimum impact of 75 seconds in all environments. This increases when cloud-init is configured to check for multiple environments. This means that yakkety is consistently taking 2-3 minutes to boot on EC2 and GCE, compared to the ~30 seconds of the first boot and ~10 seconds thereafter in xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1629797/+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 1631436] Re: Some network configuration cmdline arguments doesn't work anymore with version 0.122ubuntu8.3
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1631436 Title: Some network configuration cmdline arguments doesn't work anymore with version 0.122ubuntu8.3 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: In the past, until the version 0.122ubuntu8.1, we used the syntax "ip=:eth0:dhcp" as described in the kernel's documentation : https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt The version 0.122ubuntu8.3 breaks it. It works only with "ip=eth0" syntax as far as i have tested it. So, the current last package version leaves the machine without network on boot. Any host that needs network on boot (nfsroot / using dropbear for example) might not boot properly. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631436/+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 1560086] Re: cannot download files with no destination app from webapps
** Changed in: webapps-sprint Milestone: sprint-25 => sprint-26 -- 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/1560086 Title: cannot download files with no destination app from webapps Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in The Webapps-core project: New Status in webapps-sprint: In Progress Status in webbrowser-app package in Ubuntu: In Progress Bug description: Using the webbrowser-app I can download any file, and will be prompted to open in an app (if apps that support that content-type exist on the system) or to download the file in the browser. The same behavior should be available webapps but is not. Steps to reproduce: - Open Gmail webapp - Open a message that has an attachment of a file of unsupported type (like a .tar, .click, etc) - click on the file to download Expected results: - I should be prompted to open the file in supported app or to download - If I choose download the file should be downloaded into ~/Downloads by the webbrowser-app Actual results: - I am told that no apps exist to support this type of file and am not allowed to download it To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1560086/+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 1629466] Re: Can't open a PDF from a webapp
*** This bug is a duplicate of bug 1560086 *** https://bugs.launchpad.net/bugs/1560086 This is a duplicate of https://bugs.launchpad.net/webapps- core/+bug/1560086 for which there is a branch in progress, sorry for the delay on this, I will MR it ASAP, ** This bug has been marked a duplicate of bug 1560086 cannot download files with no destination app from webapps -- 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/1629466 Title: Can't open a PDF from a webapp Status in webbrowser-app package in Ubuntu: New Bug description: And potentially any Content Hub file? When trying to open pdfs in the fastmail or reddit webapps, I get the following and the pdf never opens: file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Content/ContentPeerPicker13.qml:194: TypeError: Cannot read property 'peers' of null file:///usr/share/webbrowser-app/webcontainer/WebappWebview.qml:219: ReferenceError: startDownload is not defined I'm assuming it's the second message that is fatal, so I've opened against webbrowser-app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1629466/+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] [NEW] No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
Public bug reported: 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. ** Affects: initramfs-tools (Ubuntu) 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/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: New Bug description: 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 1628306] Re: network booting fails for iscsi root if no ip is set
initramfs-tools 0.122ubuntu8.3 has resulted in a serious regression for instances running in AWS when the ip=dhcp boot option set. 0.122ubuntu8.2 (and previous versions) do not exhibit the problem. I'll create a new issue for tracking, but wanted to add a comment here. -- 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 1277030] Re: Scrollbar should match overlay-scrollbar style.
Seems fine I guess? I tried to confirm with address-book-app and messaging-app, but on my desktop I wasn't able to get either of them to have a scrollbar (I can neither add contacts nor send messages, so both apps just show an empty, scroll-less window). webbrowser-app at least displays a real scrollbar that I can interact with, unlike what it did those years ago when i reported this bug. Thanks! ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => Fix Released -- 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/1277030 Title: Scrollbar should match overlay-scrollbar style. Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: qml apps on the unity7 desktop don't scroll very well, they technically have a scrollbar but it's non-interactive, and doesn't match the overlay-scrollbar style of gtk and qt apps (instead of being bright orange, it's faint, dark grey, barely noticable, and hides while not actively scrolling). Requiring desktop users to click&drag scroll makes for quite an inconsistent desktop experience and should be fixed. This is blocking a decent webapps-container experience on the 14.04 desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1277030/+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 1611227] Re: Don't use gold linker on powerpc (GCC6)
Hello Timo, or anyone else affected, Accepted llvm-toolchain-3.6 into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm- toolchain-3.6/1:3.6.2-3ubuntu4 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! ** Tags added: verification-needed -- 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/1611227 Title: Don't use gold linker on powerpc (GCC6) Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: GCC is now configured with --enable-secureplt. On powerpc, one may now get /usr/bin/ld.gold: --secure-plt: unknown option According to doko gold linker should not be used on powerpc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1611227/+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 729831] Re: Output controls are not switched to headset
The same thing happens with USB headsets, so, it seems related to having multiple output devices dynamically connected. -- 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/729831 Title: Output controls are not switched to headset Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio After my bluetooth headset is connected to the system, the sound output is switched from the speakers to the headset, but the volume control does not set the volume of the headset. I have to go to "Sound Preferences... -> Output", then choose my headset here. Then I can control the volume. Also, after selecting a new output device, the "Output volume" slider changes its position, but the volume remains the same. I have to either click on the slider or use the volume keys on the keyboard to actually set the volume. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xvro 2336 F pulseaudio /dev/snd/pcmC1D0c: xvro 2336 F...m pulseaudio /dev/snd/controlC0: xvro 2336 F pulseaudio /dev/snd/pcmC0D0p: xvro 2336 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xea40 irq 49' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,1458a002,00100101' Controls : 38 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'SAA7134'/'saa7133[0] at 0xea315000 irq 19' Mixer name : 'SAA7134 Mixer' Components : '' Controls : 6 Simple ctrls : 3 Date: Sat Mar 5 21:36:59 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANGUAGE=en LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: pulseaudio dmi.bios.date: 04/24/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4B dmi.board.name: EX38-DQ6 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4B:bd04/24/2009:svnGigabyteTechnologyCo.,Ltd.:pnEX38-DQ6:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX38-DQ6:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EX38-DQ6 dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.pulse.default.pa: 2010-12-19T18:10:08.489783 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/729831/+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 1628042] Re: Doesn't vibrate on incoming calls if "Other vibrations" not active
** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usensord in Ubuntu. https://bugs.launchpad.net/bugs/1628042 Title: Doesn't vibrate on incoming calls if "Other vibrations" not active Status in Canonical System Image: Fix Committed Status in usensord package in Ubuntu: In Progress Bug description: Steps: 1. Set "Vibrate on ring" and "Vibrate in silent mode" active under "Ringtone" in System settings > Sound. 2. Make sure "Other vibrations" is NOT active in System settings > Sound. 3. Get an incoming call. Expected: Phone vibrates. What happens: Phone doesn't vibrate. If the "Other vibrations" is set active, then the vibration works. Device: E5, stable, OTA-13. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1628042/+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 1277030] Re: Scrollbar should match overlay-scrollbar style.
Hi Robert, I implemented the new scrollbars a few months ago. Can you have a look and confirm if the new scrollbars fix your problems? (I'm not sure I understand, from the description) The Scrollbars I implemented are for Qt apps that use the Ubuntu UI Toolkit -- 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/1277030 Title: Scrollbar should match overlay-scrollbar style. Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: qml apps on the unity7 desktop don't scroll very well, they technically have a scrollbar but it's non-interactive, and doesn't match the overlay-scrollbar style of gtk and qt apps (instead of being bright orange, it's faint, dark grey, barely noticable, and hides while not actively scrolling). Requiring desktop users to click&drag scroll makes for quite an inconsistent desktop experience and should be fixed. This is blocking a decent webapps-container experience on the 14.04 desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1277030/+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 729831] Re: Output controls are not switched to headset
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/729831 Title: Output controls are not switched to headset Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio After my bluetooth headset is connected to the system, the sound output is switched from the speakers to the headset, but the volume control does not set the volume of the headset. I have to go to "Sound Preferences... -> Output", then choose my headset here. Then I can control the volume. Also, after selecting a new output device, the "Output volume" slider changes its position, but the volume remains the same. I have to either click on the slider or use the volume keys on the keyboard to actually set the volume. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xvro 2336 F pulseaudio /dev/snd/pcmC1D0c: xvro 2336 F...m pulseaudio /dev/snd/controlC0: xvro 2336 F pulseaudio /dev/snd/pcmC0D0p: xvro 2336 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xea40 irq 49' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,1458a002,00100101' Controls : 38 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'SAA7134'/'saa7133[0] at 0xea315000 irq 19' Mixer name : 'SAA7134 Mixer' Components : '' Controls : 6 Simple ctrls : 3 Date: Sat Mar 5 21:36:59 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANGUAGE=en LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: pulseaudio dmi.bios.date: 04/24/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4B dmi.board.name: EX38-DQ6 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4B:bd04/24/2009:svnGigabyteTechnologyCo.,Ltd.:pnEX38-DQ6:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX38-DQ6:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EX38-DQ6 dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.pulse.default.pa: 2010-12-19T18:10:08.489783 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/729831/+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 1631447] Re: SlotsLayout padding grouped property needs to assigned member-by-member, can't be assigned as a whole
Thanks Marco! That makes sense, I'll have a look at that next week! ** Summary changed: - SlotsLayout paddings can't be bound to another layout values + SlotsLayout padding grouped property needs to assigned member-by-member, can't be assigned as a whole ** Description changed: + ubuntu-ui-toolkit/staging branch, r2139 + + At the moment to assign paddings of a SlotsLayout you can only do: SlotsLayout { - id: myLayout - padding.top: units.gu(15) - padding.bottom: units.gu(5) + id: myLayout + padding.top: units.gu(15) + padding.bottom: units.gu(5) } + Assigning the whole padding at once is not possible: SlotsLayout { - padding: myLayout.padding + padding: myLayout.padding } - - Would return an error: + as that returns an error: Slots.qml: Invalid property assignment: "padding" is a read-only property So to achieve this we need to manually assign the subvalues. It would be nice to do it all at once. -- 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/1631447 Title: SlotsLayout padding grouped property needs to assigned member-by- member, can't be assigned as a whole Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: ubuntu-ui-toolkit/staging branch, r2139 At the moment to assign paddings of a SlotsLayout you can only do: SlotsLayout { id: myLayout padding.top: units.gu(15) padding.bottom: units.gu(5) } Assigning the whole padding at once is not possible: SlotsLayout { padding: myLayout.padding } as that returns an error: Slots.qml: Invalid property assignment: "padding" is a read-only property So to achieve this we need to manually assign the subvalues. It would be nice to do it all at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1631447/+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 1631447] [NEW] SlotsLayout padding grouped property needs to assigned member-by-member, can't be assigned as a whole
Public bug reported: ubuntu-ui-toolkit/staging branch, r2139 At the moment to assign paddings of a SlotsLayout you can only do: SlotsLayout { id: myLayout padding.top: units.gu(15) padding.bottom: units.gu(5) } Assigning the whole padding at once is not possible: SlotsLayout { padding: myLayout.padding } as that returns an error: Slots.qml: Invalid property assignment: "padding" is a read-only property So to achieve this we need to manually assign the subvalues. It would be nice to do it all at once. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Wishlist Assignee: Andrea Bernabei (faenil) Status: Triaged -- 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/1631447 Title: SlotsLayout padding grouped property needs to assigned member-by- member, can't be assigned as a whole Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: ubuntu-ui-toolkit/staging branch, r2139 At the moment to assign paddings of a SlotsLayout you can only do: SlotsLayout { id: myLayout padding.top: units.gu(15) padding.bottom: units.gu(5) } Assigning the whole padding at once is not possible: SlotsLayout { padding: myLayout.padding } as that returns an error: Slots.qml: Invalid property assignment: "padding" is a read-only property So to achieve this we need to manually assign the subvalues. It would be nice to do it all at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1631447/+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 1561861] Re: UbuntuColors.Orange should be Ubuntu.orange instead
** Branch linked: lp:~faenil/ubuntu-ui- toolkit/listitemlayout_doc_typofix -- 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/1561861 Title: ListItemLayout documentation: UbuntuColors.Orange should be UbuntuColors.orange instead Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.ListItemLayout/ The code: ListItemLayout { id: layout title.text: "Hello..." title.color: UbuntuColors.Orange subtitle.text: "...world!" Rectangle { SlotsLayout.position: SlotsLayout.Leading color: "pink" height: units.gu(6) width: height } UbuntuColors.Orange should be Ubuntu.orange Best regards, XiaoGuo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1561861/+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 1561861] Re: UbuntuColors.Orange should be Ubuntu.orange instead
Hi liu-xiao-guo, I have just sent an MR that fixes the typo you reported. Sorry if it took so long, I was not aware of this bug (as I'm not in the SDK team, but I implemented ListItemLayout) and only just found it while I was doing a random text search for launchpad bugs that were affecting components I wrote. Thanks for reporting the bug, it's important to have a polished and reliable documentation! ** Summary changed: - UbuntuColors.Orange should be Ubuntu.orange instead + UbuntuColors.Orange should be UbuntuColors.orange instead ** Summary changed: - UbuntuColors.Orange should be UbuntuColors.orange instead + ListItemLayout documentation: UbuntuColors.Orange should be UbuntuColors.orange instead ** Also affects: ubuntu-ui-toolkit (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ubuntu-ui-toolkit (Ubuntu RTM) Status: New => In Progress ** Changed in: ubuntu-ui-toolkit (Ubuntu RTM) Importance: Undecided => Low ** Changed in: ubuntu-ui-toolkit (Ubuntu RTM) Assignee: (unassigned) => Andrea Bernabei (faenil) ** No longer affects: ubuntu-ui-toolkit (Ubuntu RTM) -- 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/1561861 Title: ListItemLayout documentation: UbuntuColors.Orange should be UbuntuColors.orange instead Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.ListItemLayout/ The code: ListItemLayout { id: layout title.text: "Hello..." title.color: UbuntuColors.Orange subtitle.text: "...world!" Rectangle { SlotsLayout.position: SlotsLayout.Leading color: "pink" height: units.gu(6) width: height } UbuntuColors.Orange should be Ubuntu.orange Best regards, XiaoGuo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1561861/+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 1561861] Re: UbuntuColors.Orange should be Ubuntu.orange instead
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Andrea Bernabei (faenil) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided => Low ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => In Progress -- 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/1561861 Title: ListItemLayout documentation: UbuntuColors.Orange should be UbuntuColors.orange instead Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.ListItemLayout/ The code: ListItemLayout { id: layout title.text: "Hello..." title.color: UbuntuColors.Orange subtitle.text: "...world!" Rectangle { SlotsLayout.position: SlotsLayout.Leading color: "pink" height: units.gu(6) width: height } UbuntuColors.Orange should be Ubuntu.orange Best regards, XiaoGuo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1561861/+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 1607427] Re: super key not showing scopes home
** Branch linked: lp:~lukas-kde/unity8/superKeyPressFix ** Changed in: mir Status: New => Invalid -- 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/1607427 Title: super key not showing scopes home Status in Canonical System Image: New Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: In Progress Bug description: Hey, if I press super key, the scopes home does not appear. In OTA-11 it worked as it should, but in OTA-12 it doesn't work. I use M10 FHD tablet with OTA-12 and external keyboard Logitech k810. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607427/+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 1622002] Re: dhcp_release6 can be called when it is not present
** Tags removed: newton-rc-potential -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1622002 Title: dhcp_release6 can be called when it is not present Status in neutron: Fix Released Status in dnsmasq package in Ubuntu: New Bug description: If someone enables dhcpv6-stateful addressing on a subnet, but they are running an old version of dnsmasq (<2.76), then the dhcp agent could try and run dhcp_release6 even though it isn't present. An example: http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron- multinode-full-ubuntu- xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272 Checking it's present first would fix this problem. Since the change to call dhcp_release6 was just added in https://review.openstack.org/#/c/301747/ we should fix this before Newton ships and people complain. There is also an effort to get Cirros to support DHCPv6 so that we can test this in the gate, https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so we can add a functional test. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1622002/+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 1631436] [NEW] Some network configuration cmdline arguments doesn't work anymore with version 0.122ubuntu8.3
Public bug reported: In the past, until the version 0.122ubuntu8.1, we used the syntax "ip=:eth0:dhcp" as described in the kernel's documentation : https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt The version 0.122ubuntu8.3 breaks it. It works only with "ip=eth0" syntax as far as i have tested it. So, the current last package version leaves the machine without network on boot. Any host that needs network on boot (nfsroot / using dropbear for example) might not boot properly. Regards ** Affects: initramfs-tools (Ubuntu) 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/1631436 Title: Some network configuration cmdline arguments doesn't work anymore with version 0.122ubuntu8.3 Status in initramfs-tools package in Ubuntu: New Bug description: In the past, until the version 0.122ubuntu8.1, we used the syntax "ip=:eth0:dhcp" as described in the kernel's documentation : https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt The version 0.122ubuntu8.3 breaks it. It works only with "ip=eth0" syntax as far as i have tested it. So, the current last package version leaves the machine without network on boot. Any host that needs network on boot (nfsroot / using dropbear for example) might not boot properly. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631436/+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 1631302] Re: System becomes unresponsive when running code with deep-recursion under unprivileged user
I suspect it's not about perl, probably system can be locked same way with any programming language. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1631302 Title: System becomes unresponsive when running code with deep-recursion under unprivileged user Status in perl package in Ubuntu: New Bug description: In Ubuntu 16.04 if you run perl -e 'sub x { x() }; x()' (this commands does a deep recursion, eats all memory) under non-root user whole system becomes unresponsive, mouse, keyboard does not work. Screen does not update when you plug/unplug charger, for example. The only way to quit is to press power button and shut down machine. Expected bahaviour: Ctrl-C, Ctrl-Alt-Del, Ctrl-Alt-F1, mouse, at least something should work. Repsoduced on HP Pavilion 16, SSD with encryption, encrypted Swap. Reproduced by at least one another person with Ubuntu 16.04 with SSD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1631302/+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 1612367] Re: [Touch] Incoming call gets silent randomly
@anupam thats an interesting theory, I got a log of when the power button is pressed and it goes from paused to stopped almost instantly, whereas your logs generally show a delay and stopped is only issued once the call is answered. @jim I still thinks its a thread issue in media hub, I can't get by the fact that its logging engine playing uri multiple times on each incoming call and logging paused multiple times. Perhaps thats benign but unclear to me why the same code is executed more than once "sometimes". -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up
To determine if this has been fixed, boot an image that has the GCE data source enabled (e.g. the image from cloud-images.ubuntu.com) but not on GCE. Examine the output of `journalctl` and look for the following lines: Oct 07 16:17:39 ubuntu cloud-init[1009]: [CLOUDINIT] __init__.py[DEBUG]: Seeing if we can get any data from Oct 07 16:19:19 ubuntu cloud-init[1009]: [CLOUDINIT] DataSourceGCE.py[DEBUG]: http://metadata.google.internal/computeMetadata/v1/ is not resolvable The timestamps on them should be no more than fractions of a second apart (the above example is on a _broken_ instance). (Note that, (a) there may be lines in between these two, and (b) you have to use `journalctl` because cloud-init.log doesn't have correct timestamps.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1629797 Title: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: In Progress Status in dbus package in Ubuntu: Triaged Bug description: During boot, cloud-init does DNS resolution checks to if particular metadata services are available (in order to determine which cloud it is running on). These checks happen before systemd-resolved is up[0] and if they resolve unsuccessfully they take 25 seconds to complete. This has substantial impact on boot time in all contexts, because cloud-init attempts to resolve three known-invalid addresses ("does- not-exist.example.com.", "example.invalid." and a random string) to enable it to detect when it's running in an environment where a DNS server will always return some sort of redirect. As such, we're talking a minimum impact of 75 seconds in all environments. This increases when cloud-init is configured to check for multiple environments. This means that yakkety is consistently taking 2-3 minutes to boot on EC2 and GCE, compared to the ~30 seconds of the first boot and ~10 seconds thereafter in xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1629797/+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 1631302] Re: System becomes unresponsive when running code with deep-recursion under unprivileged user
Reassigning bug against perl so someone with more knowledge that I can look into it further. I have no idea if this is a bug or not but I can confirm that an Ubuntu 16.10 test system locks up as described. ** Package changed: ubuntu => perl (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1631302 Title: System becomes unresponsive when running code with deep-recursion under unprivileged user Status in perl package in Ubuntu: New Bug description: In Ubuntu 16.04 if you run perl -e 'sub x { x() }; x()' (this commands does a deep recursion, eats all memory) under non-root user whole system becomes unresponsive, mouse, keyboard does not work. Screen does not update when you plug/unplug charger, for example. The only way to quit is to press power button and shut down machine. Expected bahaviour: Ctrl-C, Ctrl-Alt-Del, Ctrl-Alt-F1, mouse, at least something should work. Repsoduced on HP Pavilion 16, SSD with encryption, encrypted Swap. Reproduced by at least one another person with Ubuntu 16.04 with SSD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1631302/+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 1631302] [NEW] System becomes unresponsive when running code with deep-recursion under unprivileged user
You have been subscribed to a public bug: In Ubuntu 16.04 if you run perl -e 'sub x { x() }; x()' (this commands does a deep recursion, eats all memory) under non-root user whole system becomes unresponsive, mouse, keyboard does not work. Screen does not update when you plug/unplug charger, for example. The only way to quit is to press power button and shut down machine. Expected bahaviour: Ctrl-C, Ctrl-Alt-Del, Ctrl-Alt-F1, mouse, at least something should work. Repsoduced on HP Pavilion 16, SSD with encryption, encrypted Swap. Reproduced by at least one another person with Ubuntu 16.04 with SSD. ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- System becomes unresponsive when running code with deep-recursion under unprivileged user https://bugs.launchpad.net/bugs/1631302 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl 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 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up
** Changed in: cloud-init (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1629797 Title: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: In Progress Status in dbus package in Ubuntu: Triaged Bug description: During boot, cloud-init does DNS resolution checks to if particular metadata services are available (in order to determine which cloud it is running on). These checks happen before systemd-resolved is up[0] and if they resolve unsuccessfully they take 25 seconds to complete. This has substantial impact on boot time in all contexts, because cloud-init attempts to resolve three known-invalid addresses ("does- not-exist.example.com.", "example.invalid." and a random string) to enable it to detect when it's running in an environment where a DNS server will always return some sort of redirect. As such, we're talking a minimum impact of 75 seconds in all environments. This increases when cloud-init is configured to check for multiple environments. This means that yakkety is consistently taking 2-3 minutes to boot on EC2 and GCE, compared to the ~30 seconds of the first boot and ~10 seconds thereafter in xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1629797/+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 1624337] Re: Scrollbar tests fail on Qt 5.6.
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- 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/1624337 Title: Scrollbar tests fail on Qt 5.6. Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: FAIL! : components::Scrollbar::test_defaultStylingValues(vertical scrollbar) Wrong styling property default value. Actual (): #5d5d5d Expected (): #11 Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(1205)] FAIL! : components::Scrollbar::test_defaultStylingValues(horizontal scrollbar) Wrong styling property default value. Actual (): #5d5d5d Expected (): #11 Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(1205)] FAIL! : components::Scrollbar::test_dragThumbAndCheckStyling(vertical scrollbar) Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(800)] FAIL! : components::Scrollbar::test_dragThumbAndCheckStyling(horizontal scrollbar) Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(838)] and * Start testing of components * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.4.0 20160609) PASS : components::Scrollbar::initTestCase() FAIL! : components::Scrollbar::test_handlingOfMovingHeader(Standard header) Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar_header.13.qml(230)] FAIL! : components::Scrollbar::test_handlingOfMovingHeader(Edit header (with extensions)) Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar_header.13.qml(230)] PASS : components::Scrollbar::cleanupTestCase() Totals: 2 passed, 2 failed, 0 skipped, 0 blacklisted * Finished testing of components * See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624337/+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 1630167] Re: SlotsLayout with Column as mainSlot: endless loop when resizing view so that Column has negative width
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Triaged => In Progress ** Also affects: ubuntu-ui-toolkit (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: ubuntu-ui-toolkit (Ubuntu RTM) Assignee: (unassigned) => Andrea Bernabei (faenil) ** Changed in: ubuntu-ui-toolkit (Ubuntu RTM) Importance: Undecided => Medium ** Changed in: ubuntu-ui-toolkit (Ubuntu RTM) Status: New => In Progress -- 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/1630167 Title: SlotsLayout with Column as mainSlot: endless loop when resizing view so that Column has negative width Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu RTM: In Progress Bug description: With a simple code such as import QtQuick 2.4 import Ubuntu.Components 1.3 import QtQuick.Window 2.0 Window { SlotsLayout { id: slotsLayout onHeightChanged: print("SlotsLayout height",height) width: parent.width mainSlot: Column { onHeightChanged: print("COlumn height",height) onWidthChanged: console.log("Column width", width) Rectangle { id: rect width: parent.width onWidthChanged: console.log("RECT WIDTH", width) onHeightChanged: console.log("RECT HEIGHT!", height) height: 5 } } } } Or something similar (http://archive.is/N0jnM), when resizing the view horizontally to only use few pixels, an infinite resizing loop starts and the view freezes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630167/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
On Fri, Oct 07, 2016 at 03:20:29PM -, hackeron wrote: > My biggest issue is virtual interfaces do NOT work with these > "predictable" network names. I can do ifconfig eth0:0 192.168.123.123 > but I cannot do ifconfig enxb827djdk:0 192.168.123.123 - it just > overrites the main IP, rather than creating another virtual interface :( I can't help with the bug in general, but for this particular use case, try "ip addr add 192.168.123.123 dev enxb827djdk". ifconfig isn't going away, but all new development has moved to the "ip" command which replaces it. -- 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/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd package in Debian: Fix Released Bug description: Description:Ubuntu 16.04 LTS Release:16.04 The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB devices. It appears the regression is here: * Set MAC based name for USB network interfaces only for universally administered (i. e. stable) MACs, not for locally administered (i. e. randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link (as link files don't currently support globs for MACAddress=) and replace with an udev rule in /lib/udev/rules.d/73-special-net-names.rules. (Closes: #812575, LP: #1574483) As Raspberry Pi's use eth0 via USB, this breaks running systems. Before: ii systemd229-4ubuntu4 armhfsystem and service manager ii udev 229-4ubuntu4 armhf/dev/ and hotplug management daem 3: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff After: ii systemd 229-4ubuntu6armhf system and service manager ii udev 229-4ubuntu6armhf /dev/ and hotplug management daemon 3: enxb827eb1639e9: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff cat /proc/cmdline dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait With the default interfaces configuration, all networking is lost on reboot after upgrade. SRU TEST CASE = * Boot with "net.ifnames=0" on the kernel command line, and connect an USB ethernet device. It will still be called enxDEADBEEF with current xenial. With the -proposed version it will instead keep the kernel name, like "usb0" as intended. * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules" (the other documented way to disable ifnames) and do the above connect/name check test again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1592721] Re: Don't write search domains to resolv.conf in the case of split DNS
I'm afraid this didn't work for me. I installed network-manager 1.2.2-0ubuntu0.16.04.3 from xenial-proposed, ran 'systemctl restart NetworkManager' as root and reconnected to the VPN and I see the same behaviour (i.e. I get DNS resolution failure for non-VPN domains). I am on wifi only and both v4 and v6 are set to route all outbound traffic. -- 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/1592721 Title: Don't write search domains to resolv.conf in the case of split DNS Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Bug description: [Impact] All VPN users meaning to use split-tunnelling in a situation where leaking DNS data to the internet about what might be behind their VPN is undesirable. [Test case] 1) connect to VPN 2) Use dig to request a name that should be on the VPN 3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only gone through the VPN nameservers (only its request number should have increased by one) 4) Use dig to request a name off-VPN, such as google.com. 5) Verify (kill -USR1 again) that the request has caused the non-VPN nameserver request number to increase, and that the VPN number has not increased. It is easier to verify this when there is as little traffic as possible on the system, to avoid spurious DNS requests which would make it harder to validate the counters. [Regression potential] This change modifies the way in which DNS nameservers and search domains are passed to dnsmasq, as such, if a VPN is configured in a non-standard way and intended to be used to resolve all network requests (which is typically not the case for split-tunnelling) or if the public network is intended to always resolve all requests while the VPN still provides search domains, one might observe incorrect behavior. Possible failure cases would include failure to resolve names correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving to the incorrect values (if the wrong nameserver is used). --- Currently, NM will write all search domains to both any DNS-handling plugins running, and also to resolv.conf / resolvconf; in all cases. The issue is that doing so means that in the split-DNS case on VPNs, you might get a negative response from all nameservers, then a new request by glibc with the search tacked on, to nameservers again, which might cause DNS requests for "private" resources (say, on the VPN) to be sent to external, untrusted resolvers, or for DNS queries not meant for VPN nameservers to be sent through the VPN anyway. This is fixable in the case where we have a caching plugin running (such as dnsmasq). dnsmasq will already know about the search domains and use that to limit queries to the right nameservers when a VPN is running. Writing search domains to resolv.conf is unnecessary in this case. We should still write search domains if no caching gets done, as we then need to expect glibc to send requests as it otherwise would. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721/+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 1612367] Re: [Touch] Incoming call gets silent randomly
Excuse this naive comment, but if I'm not mistaken, while the phone rings on an incoming call, pressing the power button pauses the ringtone. Is it possible that the same/similar action is simulated here even when the user is not pressing the power button? -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
hackeron, which systemd version are you using? Note that the one currently in xenial-updates reverted the previous SRU, you need version 229-4ubuntu11. -- 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/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd package in Debian: Fix Released Bug description: Description:Ubuntu 16.04 LTS Release:16.04 The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB devices. It appears the regression is here: * Set MAC based name for USB network interfaces only for universally administered (i. e. stable) MACs, not for locally administered (i. e. randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link (as link files don't currently support globs for MACAddress=) and replace with an udev rule in /lib/udev/rules.d/73-special-net-names.rules. (Closes: #812575, LP: #1574483) As Raspberry Pi's use eth0 via USB, this breaks running systems. Before: ii systemd229-4ubuntu4 armhfsystem and service manager ii udev 229-4ubuntu4 armhf/dev/ and hotplug management daem 3: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff After: ii systemd 229-4ubuntu6armhf system and service manager ii udev 229-4ubuntu6armhf /dev/ and hotplug management daemon 3: enxb827eb1639e9: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff cat /proc/cmdline dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait With the default interfaces configuration, all networking is lost on reboot after upgrade. SRU TEST CASE = * Boot with "net.ifnames=0" on the kernel command line, and connect an USB ethernet device. It will still be called enxDEADBEEF with current xenial. With the -proposed version it will instead keep the kernel name, like "usb0" as intended. * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules" (the other documented way to disable ifnames) and do the above connect/name check test again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1607427] Re: super key not showing scopes home
** Changed in: unity8 (Ubuntu) Status: Incomplete => In Progress ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Lukáš Tinkl (lukas-kde) ** Changed in: mir (Ubuntu) Status: Confirmed => Invalid -- 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/1607427 Title: super key not showing scopes home Status in Canonical System Image: New Status in Mir: New Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: In Progress Bug description: Hey, if I press super key, the scopes home does not appear. In OTA-11 it worked as it should, but in OTA-12 it doesn't work. I use M10 FHD tablet with OTA-12 and external keyboard Logitech k810. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607427/+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 1248044] Re: xzless report an error
** Changed in: xz-utils (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1248044 Title: xzless report an error Status in xz-utils package in Ubuntu: Fix Released Status in xz-utils package in Debian: Fix Released Bug description: when using the command xzless, I have always this line /usr/bin/xzless: line 49: test: 458 (GNU regular expressions): integer expression expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1248044/+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 1607427] Re: super key not showing scopes home
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mir (Ubuntu) Status: New => Confirmed -- 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/1607427 Title: super key not showing scopes home Status in Canonical System Image: New Status in Mir: New Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: In Progress Bug description: Hey, if I press super key, the scopes home does not appear. In OTA-11 it worked as it should, but in OTA-12 it doesn't work. I use M10 FHD tablet with OTA-12 and external keyboard Logitech k810. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607427/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
I'm on Xenial and I ran an apt-get update; apt-get dist-upgrade and my eth0 changed back to enxb827djdk after reboot :( My biggest issue is virtual interfaces do NOT work with these "predictable" network names. I can do ifconfig eth0:0 192.168.123.123 but I cannot do ifconfig enxb827djdk:0 192.168.123.123 - it just overrites the main IP, rather than creating another virtual interface :( Previously, I was able to follow these steps: Edit/boot/firmware/config.txt to add: net.ifnames=0 biosdevname=0 Run: ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules Make sure this file is absent (which it was anyway): /lib/udev/rules.d/73-usb-net-by-mac.rules Run: update-initramfs -k all -u But now, running the above steps no longer works and I'm getting enxb827djdk again :( I also checked /proc/cmdline and I have net.ifnames=0 there so it's definitely being passed. I'm running kernel 4.4.0-1023-raspi2 Sep 6 16:12:44 UTC 2016 Is there a solution/workaround? -- 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/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd package in Debian: Fix Released Bug description: Description:Ubuntu 16.04 LTS Release:16.04 The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB devices. It appears the regression is here: * Set MAC based name for USB network interfaces only for universally administered (i. e. stable) MACs, not for locally administered (i. e. randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link (as link files don't currently support globs for MACAddress=) and replace with an udev rule in /lib/udev/rules.d/73-special-net-names.rules. (Closes: #812575, LP: #1574483) As Raspberry Pi's use eth0 via USB, this breaks running systems. Before: ii systemd229-4ubuntu4 armhfsystem and service manager ii udev 229-4ubuntu4 armhf/dev/ and hotplug management daem 3: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff After: ii systemd 229-4ubuntu6armhf system and service manager ii udev 229-4ubuntu6armhf /dev/ and hotplug management daemon 3: enxb827eb1639e9: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff cat /proc/cmdline dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait With the default interfaces configuration, all networking is lost on reboot after upgrade. SRU TEST CASE = * Boot with "net.ifnames=0" on the kernel command line, and connect an USB ethernet device. It will still be called enxDEADBEEF with current xenial. With the -proposed version it will instead keep the kernel name, like "usb0" as intended. * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules" (the other documented way to disable ifnames) and do the above connect/name check test again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1627795] Re: unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from QObjectPrivate::isSignalConnected from QMetaObject::activate from QMetaObject::activate from QAb
** Changed in: unity-scopes-shell (Ubuntu) Status: In Progress => Fix Released ** Changed in: canonical-devices-system-image Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1627795 Title: unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from QObjectPrivate::isSignalConnected from QMetaObject::activate from QMetaObject::activate from QAbstractItemModel::modelAboutToBeReset Status in Canonical System Image: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.14+15.04.20160831.3-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/0168de360a9e17b6337e0304609320555b011747 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627795/+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 1631409] [NEW] Update usr.sbin.dnsmasq profile for network api in lxd
Public bug reported: Intro: Currently dnsmasq profile includes extra rights for lxd. Current usr.sbin.dnsmasq profile works with current lxd from xenial repository. But in lxd git (available in lxd-git-master ppa now) version network api was introduced, and since lxd quite active, is not too long since new lxd will be xenial repository. And that means people will lose network in all containers in production in future. This could be fixed with this extra rule in usr.sbin.dnsmasq profile: /var/lib/lxd/networks/** rw, in usr.sbin.dnsmasq profile. 1) Ubuntu 16.04.1 LTS 2) apparmor-profiles (currently 2.10.95-0ubuntu2.4). I couldn't select apparmor-profiles, only apparmor or apparmor-profiles-extra. Don't know why, mb launchpad bug. 3) What you expected to happen: network in lxd will start 4) apparmor usr.sbin.dnsmasq profile blocks network in new lxd version Bug original source: https://github.com/lxc/lxd-pkg-ubuntu/issues/21 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- 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/1631409 Title: Update usr.sbin.dnsmasq profile for network api in lxd Status in apparmor package in Ubuntu: New Bug description: Intro: Currently dnsmasq profile includes extra rights for lxd. Current usr.sbin.dnsmasq profile works with current lxd from xenial repository. But in lxd git (available in lxd-git-master ppa now) version network api was introduced, and since lxd quite active, is not too long since new lxd will be xenial repository. And that means people will lose network in all containers in production in future. This could be fixed with this extra rule in usr.sbin.dnsmasq profile: /var/lib/lxd/networks/** rw, in usr.sbin.dnsmasq profile. 1) Ubuntu 16.04.1 LTS 2) apparmor-profiles (currently 2.10.95-0ubuntu2.4). I couldn't select apparmor-profiles, only apparmor or apparmor-profiles-extra. Don't know why, mb launchpad bug. 3) What you expected to happen: network in lxd will start 4) apparmor usr.sbin.dnsmasq profile blocks network in new lxd version Bug original source: https://github.com/lxc/lxd-pkg-ubuntu/issues/21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1631409/+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 1631398] Re: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf',
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1631398 Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 Status in account-plugins package in Ubuntu: New Bug description: hi my frends ProblemType: Package DistroRelease: Ubuntu 16.10 Package: account-plugin-google 0.13+16.10.20160831-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Fri Oct 7 07:55:35 2016 DuplicateSignature: package:account-plugin-google:0.13+16.10.20160831-0ubuntu1 Unpacking account-plugin-google (0.13+16.10.20160929.1-0ubuntu1) over (0.13+16.10.20160831-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-V6mfaf/03-account-plugin-google_0.13+16.10.20160929.1-0ubuntu1_all.deb (--unpack): trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 InstallationDate: Installed on 2016-02-11 (239 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: account-plugins Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.signon-ui.webkit-options.d.accounts.google.com.conf: 2016-07-02T19:13:58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1631398/+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 1593586] Re: Issue with two external screens
This problem is solved for me after applying the latest updates. -- 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/1593586 Title: Issue with two external screens Status in xorg package in Ubuntu: New Bug description: When I boot my Laptop (Dell latitude 7470 + Dell E-Port Plus II docking station) with two external Dell screens attached (via Display port, each separate connected) at the beginning of my session everything works fine. The lid is closed while booting. After starting Firefox the focus of the mouse is some how lost. Then it is not possible to open the context menu of Firefox. Typed letters appear on the other screen. The focus is also lost when I remove the Laptop from the dockingstation and attach it back to the docking station. The focus works fine when only the built-in display is used. WORKAROUND: Boot the laptop at the beginning with only one attached screen (cable disconnected). After login attach the second screen, open the "Displays" configuration menu, and click on something without changing the configuration. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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 Jun 17 08:16:07 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06dc] InstallationDate: Installed on 2016-06-10 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E7470 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jun 17 08:04:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1168 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1593586/+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 1631398] [NEW] package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf
Public bug reported: hi my frends ProblemType: Package DistroRelease: Ubuntu 16.10 Package: account-plugin-google 0.13+16.10.20160831-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Fri Oct 7 07:55:35 2016 DuplicateSignature: package:account-plugin-google:0.13+16.10.20160831-0ubuntu1 Unpacking account-plugin-google (0.13+16.10.20160929.1-0ubuntu1) over (0.13+16.10.20160831-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-V6mfaf/03-account-plugin-google_0.13+16.10.20160929.1-0ubuntu1_all.deb (--unpack): trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 InstallationDate: Installed on 2016-02-11 (239 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: account-plugins Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.signon-ui.webkit-options.d.accounts.google.com.conf: 2016-07-02T19:13:58 ** Affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1631398 Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 Status in account-plugins package in Ubuntu: New Bug description: hi my frends ProblemType: Package DistroRelease: Ubuntu 16.10 Package: account-plugin-google 0.13+16.10.20160831-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Fri Oct 7 07:55:35 2016 DuplicateSignature: package:account-plugin-google:0.13+16.10.20160831-0ubuntu1 Unpacking account-plugin-google (0.13+16.10.20160929.1-0ubuntu1) over (0.13+16.10.20160831-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-V6mfaf/03-account-plugin-google_0.13+16.10.20160929.1-0ubuntu1_all.deb (--unpack): trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 InstallationDate: Installed on 2016-02-11 (239 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: account-plugins Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.signon-ui.webkit-options.d.accounts.google.com.conf: 2016-07-02T19:13:58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1631398/+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 1630167] Re: SlotsLayout with Column as mainSlot: endless loop when resizing view so that Column has negative width
** Branch linked: lp:~faenil/ubuntu-ui- toolkit/slotslayout_implicitwidthloop_bug1630167 -- 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/1630167 Title: SlotsLayout with Column as mainSlot: endless loop when resizing view so that Column has negative width Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: With a simple code such as import QtQuick 2.4 import Ubuntu.Components 1.3 import QtQuick.Window 2.0 Window { SlotsLayout { id: slotsLayout onHeightChanged: print("SlotsLayout height",height) width: parent.width mainSlot: Column { onHeightChanged: print("COlumn height",height) onWidthChanged: console.log("Column width", width) Rectangle { id: rect width: parent.width onWidthChanged: console.log("RECT WIDTH", width) onHeightChanged: console.log("RECT HEIGHT!", height) height: 5 } } } } Or something similar (http://archive.is/N0jnM), when resizing the view horizontally to only use few pixels, an infinite resizing loop starts and the view freezes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1630167/+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