[Touch-packages] [Bug 1634748] [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: This does this after GUI is logged into... ProblemType: Package DistroRelease: Ubuntu 16.10 Package: account-plugin-google 0.13+16.10.20160831-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Mon Oct 17 22:13:47 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-FwnFQX/033-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 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) ** Affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check 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/1634748 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: This does this after GUI is logged into... ProblemType: Package DistroRelease: Ubuntu 16.10 Package: account-plugin-google 0.13+16.10.20160831-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Mon Oct 17 22:13:47 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-FwnFQX/033-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 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1634748/+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 1223928] Re: replace medibuntu with videolan archive for install-css
** Changed in: libdvdread (Ubuntu) Assignee: (unassigned) => VINITA (chopravini) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdvdread in Ubuntu. https://bugs.launchpad.net/bugs/1223928 Title: replace medibuntu with videolan archive for install-css Status in libdvdread package in Ubuntu: Fix Released Status in libdvdread source package in Precise: Fix Released Status in libdvdread source package in Quantal: Fix Released Status in libdvdread source package in Raring: Fix Released Status in libdvdread source package in Saucy: Fix Released Bug description: The Medibuntu archive is shut down. The videolan developers have put up a new archive for libdvdcss. The install-css.sh script should be updated to use this new archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdvdread/+bug/1223928/+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 1506744] Re: Newly installed applications do not show in the dash
Applications in filters ** Attachment added: "Applications in filters" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1506744/+attachment/4763580/+files/Screenshot%20from%202016-10-19%2009-57-45.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash Status in GLib: Confirmed Status in bamf package in Ubuntu: In Progress Status in gnome-menus package in Ubuntu: Fix Released Status in libunity package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in gnome-menus source package in Xenial: Fix Released Status in libunity source package in Xenial: Fix Released Bug description: [Impact] I am running 15.10 development version fully up to date, I installed it a few days ago and I have an issue with newly installed applications not appearing in the dash when I search for them, they can be started via console but the icons/launchers of newly installed applications will only appear in the dash after session is restarted. [Test case] 1. Install a new applicaiton (using apt-get or the software center) 2. Make sure the application is listed in the Unity Dash [Possible Regressions] Unity fails to list all the applications, not just the newly installed ones. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151002.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Oct 16 08:41:39 2015 InstallationDate: Installed on 2015-10-11 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install)Z To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+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 1506744] Re: Newly installed applications do not show in the dash
I finally found out why the installed Applications were not showing up. Check for Filters options while searching and select the Applications button. Mine was not selected so it was listing due to filters applied. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash Status in GLib: Confirmed Status in bamf package in Ubuntu: In Progress Status in gnome-menus package in Ubuntu: Fix Released Status in libunity package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in gnome-menus source package in Xenial: Fix Released Status in libunity source package in Xenial: Fix Released Bug description: [Impact] I am running 15.10 development version fully up to date, I installed it a few days ago and I have an issue with newly installed applications not appearing in the dash when I search for them, they can be started via console but the icons/launchers of newly installed applications will only appear in the dash after session is restarted. [Test case] 1. Install a new applicaiton (using apt-get or the software center) 2. Make sure the application is listed in the Unity Dash [Possible Regressions] Unity fails to list all the applications, not just the newly installed ones. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151002.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Oct 16 08:41:39 2015 InstallationDate: Installed on 2015-10-11 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install)Z To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+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 1613880] Re: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for six (Ubuntu) because there has been no activity for 60 days.] ** Changed in: six (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1613880 Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in six package in Ubuntu: Expired Bug description: attempting "sudo apt-get install python-matplotlib" with Python 3.5 as my default Python version ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-six 1.10.0-3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Aug 16 15:47:58 2016 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-08-08 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: six Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/six/+bug/1613880/+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 1588915] Re: ifup does not block for interface to be up with static addresses
I would chime in a bit on this too. 14.04 _did_ have such issues. In fact, I had a physical box with static IP's (2 nics), if a cable was unpligged, it would hang forever and also become inconsistent. I had these discussions a year ago or so. Anyway, I had ot abandon ubuntu server (along with some nft issues at the time) and run archlinux as my xen host. But I ran zfs as my xen backend, so on arch, I sometimes* could have issues ~ once a year where it best be I had physical access to the box to be able to fix any potential issues. I am now going to move abroad and so I thought , with archlinux unpriv. lxc containers out, to leave xen (as I don't have the expected network output from the servers) to lxc. With arch and benig abroad, I think ubuntu 16.04 now with systemd would have solved this (my server with arch on xen has always gracefully sorted it out: ~1.5-2 years). Seeing this bug and seein git has to do with ifup makes me think it's partly a remnance from the older logic from sysv/upstart. This probably doesn't help much butjust saying the ifup is a bit archaic now that systemd is in use and is not evebn present in archlinux and creates seemingly less problems. I have only a brief moment before leaving so seeing this now worries me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1588915 Title: ifup does not block for interface to be up with static addresses Status in ifupdown package in Ubuntu: Confirmed Bug description: Description:Ubuntu 16.04 LTS (server) Release:16.04 systemd: Installed: 229-4ubuntu6 Candidate: 229-4ubuntu6 Version table: *** 229-4ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages This issue is more about systemd integration then an issue with systemd package itself. The general problem is the distinction between the network being configured and the network being up and what that means for services that depend on the network. upstream systemd has network.target (network is configured) and network-online.target (network is up), however xenial server (dunno about desktop) doesn't seem to use network-online.target. The result of which is, as soon as the network is configured both network.target and network-online.target are considered complete. At which point services dependent on either of those will get started. However this can lead to problems if the services in question are actually dependent on the network (ie dns lookups) when they are starting up. Here's an example of what I mean. If you install openntpd and add the -s option there is a race on boot if it will or wont be able to do the initial sync. Jun 02 16:58:02 xenial64 systemd[1]: Reached target Network. Jun 02 16:58:02 xenial64 systemd[1]: Starting OpenNTPd Network Time Protocol... Jun 02 16:58:02 xenial64 systemd[1]: Reached target Network is Online. Jun 02 16:58:02 xenial64 ntpd[920]: constraint certificate verification turned off Jun 02 16:58:02 xenial64 ntpd[928]: ntp engine ready Jun 02 16:58:02 xenial64 kernel: tg3 :02:00.0 enp2s0: Link is down Jun 02 16:58:05 xenial64 kernel: tg3 :02:00.0 enp2s0: Link is up at 1000 Mbps, full duplex Jun 02 16:58:05 xenial64 kernel: tg3 :02:00.0 enp2s0: Flow control is on for TX and on for RX Jun 02 16:58:05 xenial64 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready Jun 02 16:58:17 xenial64 ntpd[920]: no reply received in time, skipping initial time setting openntpd was started 3 seconds before the interface even got link. I believe this issue is only going to effect physical servers with static ips. vm's interfaces will instantly have link when they are brought up and dhcp, the interface will already be up or else they wouldn't have been able to get an ip. thanks jim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1588915/+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 1634714] Re: ASUS T300 CHI Keyboard Fn Mappings
** Attachment added: "xkbmap.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634714/+attachment/4763526/+files/xkbmap.txt ** Description changed: + I believe that this is in the incorrect queue, but Launchpad would not + allow me to move it to udev. + I am submitting this bug report following the directions at https://wiki.ubuntu.com/Hotkeys/Troubleshooting 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 16.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Installed: 231-9git1 + Installed: 231-9git1 - - The Fn+F5,F6,F7, and F9 combinations do not produce the desired behavior of changing screen brightness or toggling the touchpad on the ASUS T300 Chi bluetooth keyboard. They do not produce any response whatsoever. + The Fn+F5,F6,F7, and F9 combinations do not produce the desired behavior + of changing screen brightness or toggling the touchpad on the ASUS T300 + Chi bluetooth keyboard. They do not produce any response whatsoever. They key events (as according to evtest) and their functions are listed below. type 2 (EV_REL), code 9 (REL_MISC), value 16 : Brightness Down (Fn + F5) type 2 (EV_REL), code 9 (REL_MISC), value 32 : Brightness Up (Fn + F6) type 2 (EV_REL), code 9 (REL_MISC), value 53 : Disable LCD Backlight (Fn + F7) type 2 (EV_REL), code 9 (REL_MISC), value 107 : Disable Touchpad (Fn + F9) Please let me know if I missed anything, this is my first bug report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: udev 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 20:04:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-18 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. - Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. - Bus 001 Device 012: ID 8087:0a2a Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. + Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. + Bus 001 Device 012: ID 8087:0a2a Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed root=UUID=33082bfc-d5e7-4dd9-869c-01e06d67bb28 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.207:bd08/06/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- 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/1634714 Title: ASUS T300 CHI Keyboard Fn Mappings Status in systemd package in Ubuntu: New Bug description: I believe that this is in the incorrect queue, but Launchpad would not allow me to move it to udev. I am submitting this bug report following the directions at https://wiki.ubuntu.com/Hotkeys/Troubleshooting 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 16.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Installed: 231-9git1 The Fn+F5,F6,F7, and F9 combinations do not produce the desired behavior of changing screen brightness or toggling the touchpad on the ASUS T300 Chi bluetooth keyboard. They do not produce any response whatsoever. They key events (as according to evtest) and their functions are listed below. type 2 (EV_REL), code 9 (REL_MISC), value 16 : Brightness Down (Fn + F5) type 2 (EV_REL), code 9 (REL_MISC), value 32 : Brightness Up (Fn + F6) type 2 (EV_REL), code 9 (REL_MISC), value 53 : Disable LCD Backlight (Fn + F7) type 2 (EV_REL), code 9 (REL_MISC), value 107 : Disable Touchpad (Fn + F9) Please let me know if I missed anything, this is my first
[Touch-packages] [Bug 1634714] Re: ASUS T300 CHI Keyboard Fn Mappings
** Attachment added: "lsiniput.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634714/+attachment/4763523/+files/lsiniput.log -- 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/1634714 Title: ASUS T300 CHI Keyboard Fn Mappings Status in systemd package in Ubuntu: New Bug description: I believe that this is in the incorrect queue, but Launchpad would not allow me to move it to udev. I am submitting this bug report following the directions at https://wiki.ubuntu.com/Hotkeys/Troubleshooting 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 16.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Installed: 231-9git1 The Fn+F5,F6,F7, and F9 combinations do not produce the desired behavior of changing screen brightness or toggling the touchpad on the ASUS T300 Chi bluetooth keyboard. They do not produce any response whatsoever. They key events (as according to evtest) and their functions are listed below. type 2 (EV_REL), code 9 (REL_MISC), value 16 : Brightness Down (Fn + F5) type 2 (EV_REL), code 9 (REL_MISC), value 32 : Brightness Up (Fn + F6) type 2 (EV_REL), code 9 (REL_MISC), value 53 : Disable LCD Backlight (Fn + F7) type 2 (EV_REL), code 9 (REL_MISC), value 107 : Disable Touchpad (Fn + F9) Please let me know if I missed anything, this is my first bug report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: udev 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 20:04:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-18 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 012: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed root=UUID=33082bfc-d5e7-4dd9-869c-01e06d67bb28 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.207:bd08/06/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634714/+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 1634714] Re: ASUS T300 CHI Keyboard Fn Mappings
** Attachment added: "udev-db.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634714/+attachment/4763524/+files/udev-db.txt -- 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/1634714 Title: ASUS T300 CHI Keyboard Fn Mappings Status in systemd package in Ubuntu: New Bug description: I believe that this is in the incorrect queue, but Launchpad would not allow me to move it to udev. I am submitting this bug report following the directions at https://wiki.ubuntu.com/Hotkeys/Troubleshooting 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 16.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Installed: 231-9git1 The Fn+F5,F6,F7, and F9 combinations do not produce the desired behavior of changing screen brightness or toggling the touchpad on the ASUS T300 Chi bluetooth keyboard. They do not produce any response whatsoever. They key events (as according to evtest) and their functions are listed below. type 2 (EV_REL), code 9 (REL_MISC), value 16 : Brightness Down (Fn + F5) type 2 (EV_REL), code 9 (REL_MISC), value 32 : Brightness Up (Fn + F6) type 2 (EV_REL), code 9 (REL_MISC), value 53 : Disable LCD Backlight (Fn + F7) type 2 (EV_REL), code 9 (REL_MISC), value 107 : Disable Touchpad (Fn + F9) Please let me know if I missed anything, this is my first bug report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: udev 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 20:04:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-18 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 012: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed root=UUID=33082bfc-d5e7-4dd9-869c-01e06d67bb28 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.207:bd08/06/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634714/+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 1634714] Re: ASUS T300 CHI Keyboard Fn Mappings
** Attachment added: "xkbcomp.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634714/+attachment/4763525/+files/xkbcomp.txt -- 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/1634714 Title: ASUS T300 CHI Keyboard Fn Mappings Status in systemd package in Ubuntu: New Bug description: I believe that this is in the incorrect queue, but Launchpad would not allow me to move it to udev. I am submitting this bug report following the directions at https://wiki.ubuntu.com/Hotkeys/Troubleshooting 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 16.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Installed: 231-9git1 The Fn+F5,F6,F7, and F9 combinations do not produce the desired behavior of changing screen brightness or toggling the touchpad on the ASUS T300 Chi bluetooth keyboard. They do not produce any response whatsoever. They key events (as according to evtest) and their functions are listed below. type 2 (EV_REL), code 9 (REL_MISC), value 16 : Brightness Down (Fn + F5) type 2 (EV_REL), code 9 (REL_MISC), value 32 : Brightness Up (Fn + F6) type 2 (EV_REL), code 9 (REL_MISC), value 53 : Disable LCD Backlight (Fn + F7) type 2 (EV_REL), code 9 (REL_MISC), value 107 : Disable Touchpad (Fn + F9) Please let me know if I missed anything, this is my first bug report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: udev 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 20:04:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-18 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 012: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed root=UUID=33082bfc-d5e7-4dd9-869c-01e06d67bb28 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.207:bd08/06/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634714/+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 1634714] [NEW] ASUS T300 CHI Keyboard Fn Mappings
Public bug reported: I believe that this is in the incorrect queue, but Launchpad would not allow me to move it to udev. I am submitting this bug report following the directions at https://wiki.ubuntu.com/Hotkeys/Troubleshooting 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 16.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Installed: 231-9git1 The Fn+F5,F6,F7, and F9 combinations do not produce the desired behavior of changing screen brightness or toggling the touchpad on the ASUS T300 Chi bluetooth keyboard. They do not produce any response whatsoever. They key events (as according to evtest) and their functions are listed below. type 2 (EV_REL), code 9 (REL_MISC), value 16 : Brightness Down (Fn + F5) type 2 (EV_REL), code 9 (REL_MISC), value 32 : Brightness Up (Fn + F6) type 2 (EV_REL), code 9 (REL_MISC), value 53 : Disable LCD Backlight (Fn + F7) type 2 (EV_REL), code 9 (REL_MISC), value 107 : Disable Touchpad (Fn + F9) Please let me know if I missed anything, this is my first bug report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: udev 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 20:04:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-18 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp. Bus 001 Device 012: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T300CHI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed root=UUID=33082bfc-d5e7-4dd9-869c-01e06d67bb28 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300CHI.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300CHI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.207:bd08/06/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: T300CHI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1634714/+attachment/4763513/+files/dmesg.log -- 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/1634714 Title: ASUS T300 CHI Keyboard Fn Mappings Status in systemd package in Ubuntu: New Bug description: I believe that this is in the incorrect queue, but Launchpad would not allow me to move it to udev. I am submitting this bug report following the directions at https://wiki.ubuntu.com/Hotkeys/Troubleshooting 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 16.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Installed: 231-9git1 The Fn+F5,F6,F7, and F9 combinations do not produce the desired behavior of changing screen brightness or toggling the touchpad on the ASUS T300 Chi bluetooth keyboard. They do not produce any response whatsoever. They key events (as according to evtest) and their functions are listed below. type 2 (EV_REL), code 9 (REL_MISC), value 16 : Brightness Down (Fn + F5) type 2 (EV_REL), code 9 (REL_MISC), value 32 : Brightness Up (Fn + F6) type 2 (EV_REL), code 9 (REL_MISC), value 53 : Disable LCD Backlight (Fn + F7) type 2 (EV_REL), code 9 (REL_MISC), value 107 : Disable Touchpad (Fn + F9) Please let me know if I missed anything, this is my first bug report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: udev 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 20:04:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-18 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc. Bus 001
[Touch-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
Confirmed still a problem in 16.10. I still do the ->HSP->A2DP switch every time bluetooth audio connects to get it working. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1271955] Re: unity-scope-loader crashed with SIGSEGV
May be linked to some freezing (5-10 secs+) every once in a while when I open the dash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1271955 Title: unity-scope-loader crashed with SIGSEGV Status in libunity: Confirmed Status in libunity package in Ubuntu: Confirmed Bug description: This crash was seen during https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job /trusty-touch-mako-smoke-ubuntu-weather-app- autopilot/127/artifact/clientlogs/ ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.3+14.04.20131106-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l Architecture: armhf CurrentDesktop: Unity Date: Thu Jan 23 07:35:13 2014 Disassembly: => 0x40027f08: Cannot access memory at address 0x40027f08 ExecutablePath: /usr/bin/unity-scope-loader ExecutableTimestamp: 1383715346 MarkForUpload: True ProcCmdline: /usr/bin/unity-scope-loader music/onlinemusic.scope ProcCwd: / Signal: 11 SourcePackage: libunity Stacktrace: #0 0x40027f08 in ?? () No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) StacktraceSource: #0 0x40027f08 in ?? () StacktraceTop: ?? () UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video _LogindSession: /user/32011.user/c1.session To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1271955/+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 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
Regarding: "Aug 8 06:38:33 tau systemd[1]: Started CUPS Scheduler. Aug 8 06:38:33 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get session [pid 12325]: No such device or address" This bug is successfully resolved by removing "samba" and "samba-common" in synaptic. Apparently colord has severe issues with printer sharing when the device is not longer available (possibly by default gufw rules.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe 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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1634697] Re: thin-provisioning-tools needs an initramfs-tools hook to support booting into a rootfs stored in a thin pool
** Description changed: - I found that the boot process would stall within the generated ramfs - images on 16.04 when the rootfs existed within a thin pool with the - actual error referencing a missing /usr/sbin/thin_check executable. I've - attached my own initramfs hook script which pulls in all of the module - and library dependencies in addition to the /usr/sbin/pdata_tools binary - and its thin_* symlinks. It has worked for me on 16.04(.1) on both the - x86_64 and arm architectures, but I see no reason that it wouldn't work - anywhere else where the thin-provisioning-tools package exists and fails - to provide anything similar. Please feel free to include it as-is, or to - make any changes necessary changes to bring it into compliance with any - applicable standards or conventions, or to fix any issues I might have - overlooked. + The boot process stalls within the generated ramfs images on 16.04 when + the rootfs exists within a thin pool due to a missing + /usr/sbin/thin_check. I've attached an initramfs hook script which pulls + in all of the module and library dependencies in addition to the + /usr/sbin/pdata_tools binary and its thin_* symlinks. So far, it has + been tested and found to fix the problem on found to be working on + 16.04(.1) on both the x86_64 and arm architectures, but I see no reason + why it wouldn't work anywhere else where the thin-provisioning-tools + package exists and fails to provide anything similar. ** Description changed: The boot process stalls within the generated ramfs images on 16.04 when the rootfs exists within a thin pool due to a missing /usr/sbin/thin_check. I've attached an initramfs hook script which pulls in all of the module and library dependencies in addition to the /usr/sbin/pdata_tools binary and its thin_* symlinks. So far, it has - been tested and found to fix the problem on found to be working on - 16.04(.1) on both the x86_64 and arm architectures, but I see no reason - why it wouldn't work anywhere else where the thin-provisioning-tools - package exists and fails to provide anything similar. + been tested and found to fix the problem on 16.04(.1) on both the x86_64 + and arm architectures, but I see no reason why it wouldn't work anywhere + else where the thin-provisioning-tools package exists and fails to + provide anything similar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1634697 Title: thin-provisioning-tools needs an initramfs-tools hook to support booting into a rootfs stored in a thin pool Status in lvm2 package in Ubuntu: New Bug description: The boot process stalls within the generated ramfs images on 16.04 when the rootfs exists within a thin pool due to a missing /usr/sbin/thin_check. I've attached an initramfs hook script which pulls in all of the module and library dependencies in addition to the /usr/sbin/pdata_tools binary and its thin_* symlinks. So far, it has been tested and found to fix the problem on 16.04(.1) on both the x86_64 and arm architectures, but I see no reason why it wouldn't work anywhere else where the thin-provisioning-tools package exists and fails to provide anything similar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1634697/+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 1634697] [NEW] thin-provisioning-tools needs an initramfs-tools hook to support booting into a rootfs stored in a thin pool
Public bug reported: I found that the boot process would stall within the generated ramfs images on 16.04 when the rootfs existed within a thin pool with the actual error referencing a missing /usr/sbin/thin_check executable. I've attached my own initramfs hook script which pulls in all of the module and library dependencies in addition to the /usr/sbin/pdata_tools binary and its thin_* symlinks. It has worked for me on 16.04(.1) on both the x86_64 and arm architectures, but I see no reason that it wouldn't work anywhere else where the thin-provisioning-tools package exists and fails to provide anything similar. Please feel free to include it as-is, or to make any changes necessary changes to bring it into compliance with any applicable standards or conventions, or to fix any issues I might have overlooked. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "/usr/share/initramfs-tools/hooks/thin-pool" https://bugs.launchpad.net/bugs/1634697/+attachment/4763496/+files/thin-pool -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1634697 Title: thin-provisioning-tools needs an initramfs-tools hook to support booting into a rootfs stored in a thin pool Status in lvm2 package in Ubuntu: New Bug description: I found that the boot process would stall within the generated ramfs images on 16.04 when the rootfs existed within a thin pool with the actual error referencing a missing /usr/sbin/thin_check executable. I've attached my own initramfs hook script which pulls in all of the module and library dependencies in addition to the /usr/sbin/pdata_tools binary and its thin_* symlinks. It has worked for me on 16.04(.1) on both the x86_64 and arm architectures, but I see no reason that it wouldn't work anywhere else where the thin- provisioning-tools package exists and fails to provide anything similar. Please feel free to include it as-is, or to make any changes necessary changes to bring it into compliance with any applicable standards or conventions, or to fix any issues I might have overlooked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1634697/+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 1634686] [NEW] Problème suite a la migration de 16.04 a la 16.10
Public bug reported: salut a vous pendant ma mise a jours il y a eu un bug le pc a planté au redémarrage j'avais plus rien juste l’écran de session, impossible pour moi de me connecté a ma session avec l'interface ubuntu( par défaut), j'ai relancer un upgrade avec un terminal une fois que j'ai réussi a me connecté a ma session sous gnome metacity sans fond d’écran juste la barre de menu du haut et aucun menu s'ouvre il plante tous. y a juste la fenêtre de mise a jour et le terminal que j'arrive a lancé. je pense que sa dois être un problème avec nvidia, enfin sa dois être un problème graphique je reste a votre disposition pour plus ample information bon courage a vous ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic i686 ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Oct 19 00:48:03 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.132, 4.4.0-43-generic, i686: installed nvidia-304, 304.132, 4.8.0-25-generic, i686: installed virtualbox, 5.1.6, 4.4.0-43-generic, i686: installed virtualbox, 5.1.6, 4.8.0-25-generic, i686: installed GraphicsCard: NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G92 [GeForce 9800 GT] [10de:062d] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-25-generic root=UUID=50b5e4fb-f107-434e-b231-98bf1824eeed ro quiet splash SourcePackage: xorg UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 5: Xlib: extension "GLX" missing on display ":0". Error: GLX is not available on the system UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Default Device" Option "NoLogo""True" EndSection dmi.bios.date: 06/26/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2A-VM HDMI ACPI BIOS Revision 1001 dmi.board.name: M2A-VM HDMI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMHDMIACPIBIOSRevision1001:bd06/26/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VMHDMI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Oct 19 00:32:42 2016 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 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/1634686 Title: Problème suite a la migration de 16.04 a la 16.10 Status in xorg package in Ubuntu: New Bug description: salut a vous pendant ma mise a jours il y a eu un bug le pc a planté au redémarrage j'avais plus rien juste l’écran de session, impossible pour moi de me connecté a ma session avec l'interface ubuntu( par défaut), j'ai relancer un upgrade avec un terminal une fois que j'ai réussi a me connecté a ma session sous gnome metacity sans fond d’écran juste la barre de menu du haut et aucun menu s'ouvre il plante tous. y a juste la fenêtre de mise a jour et le terminal que j'arrive a lancé. je pense que sa dois être un problème avec nvidia, enfin sa dois être un problème graphique je reste a votre disposition pour plus ample information bon courage a vous ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic i686 ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 CompizPlugins: No value set for
[Touch-packages] [Bug 1633794] Re: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
*** This bug is a duplicate of bug 1633791 *** https://bugs.launchpad.net/bugs/1633791 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1633791, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1633791 package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1633794 Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: sub- processo script post-installation instalado retornou estado de saída de erro 1 Status in tzdata package in Ubuntu: New Bug description: r ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2016g-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: tzdata: Install tzdata: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Oct 15 21:40:59 2016 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-08-04 (72 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: tzdata Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1633794/+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 1457400] Re: reduce 90s session kill timeout if the session does not shutdown cleanly
I'm still experiencing this problem on upgrading to ubuntu 16.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1457400 Title: reduce 90s session kill timeout if the session does not shutdown cleanly Status in lvm2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently onwards the ubuntu is taking long to shut down nearly 1:30 minutes. I checked the shutdown log messages and I get the follow message. A stop job is running for Session c2 of user * (25s/ 1min 30 s) It count downs till 1:30 minutes and then shutdown the machine. Why is it happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1457400/+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 1629598] Re: Apps failing to load on M10 (OTA13)
SOLVED! It turns out that these issues were being caused by my SD card, which had failed. (it was a Samsung, so I am glad it didn't explode -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1629598 Title: Apps failing to load on M10 (OTA13) Status in Canonical System Image: New Status in Ubuntu Music App: New Status in Ubuntu Document Viewer App: New Status in camera-app package in Ubuntu: New Status in gallery-app package in Ubuntu: New Bug description: Over the last few months, apps have started failing to start on my M10. Apps affected currently: - camera (stops at 'Loading...' screen), - gallery (stops at 'Gallery' splash screen), - document viewer (stops with white screen and 'Documents' header) I have had issues with Telegram too, which now just goes to a white screen, but that may stem from setup problems I have with the app on my M10 and E4.5 (see https://bugs.launchpad.net/unity-webapps- telegram/+bug/1626728) I had hoped OTA13 would fix it, but sadly not. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629598/+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 1634623] [NEW] package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: el paquete libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar
Public bug reported: Problem occurred after trying to upgrade to yakety but the upgrade crashed so I manually ran the update from synaptic ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 ProcVersionSignature: Ubuntu 4.4.0-44.64-generic 4.4.24 Uname: Linux 4.4.0-44-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Oct 18 16:59:07 2016 Dependencies: gcc-6-base 6.2.0-5ubuntu12 libc6 2.24-3ubuntu1 libcomerr2 1.43.3-1 libgcc1 1:6.2.0-5ubuntu12 libroken18-heimdal 1.7~git20160703+dfsg-1 ErrorMessage: el paquete libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libasn1-8-heimdal:i386 está en una versión diferente (1.7~git20150920+dfsg-4ubuntu1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: heimdal Title: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: el paquete libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libasn1-8-heimdal:i386 está en una versión diferente (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1634623 Title: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: el paquete libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libasn1-8-heimdal:i386 está en una versión diferente (1.7~git20150920 +dfsg-4ubuntu1) Status in heimdal package in Ubuntu: New Bug description: Problem occurred after trying to upgrade to yakety but the upgrade crashed so I manually ran the update from synaptic ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 ProcVersionSignature: Ubuntu 4.4.0-44.64-generic 4.4.24 Uname: Linux 4.4.0-44-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Oct 18 16:59:07 2016 Dependencies: gcc-6-base 6.2.0-5ubuntu12 libc6 2.24-3ubuntu1 libcomerr2 1.43.3-1 libgcc1 1:6.2.0-5ubuntu12 libroken18-heimdal 1.7~git20160703+dfsg-1 ErrorMessage: el paquete libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libasn1-8-heimdal:i386 está en una versión diferente (1.7~git20150920+dfsg-4ubuntu1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: heimdal Title: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: el paquete libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libasn1-8-heimdal:i386 está en una versión diferente (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1634623/+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 1634625] [NEW] package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: el paquete libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar po
Public bug reported: Problem occurred after trying to upgrade to yakety but the upgrade crashed so I manually ran the update from synaptic ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 ProcVersionSignature: Ubuntu 4.4.0-44.64-generic 4.4.24 Uname: Linux 4.4.0-44-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Oct 18 16:59:06 2016 Dependencies: gcc-6-base 6.2.0-5ubuntu12 libc6 2.24-3ubuntu1 libcomerr2 1.43.3-1 libgcc1 1:6.2.0-5ubuntu12 libroken18-heimdal 1.7~git20160703+dfsg-1 ErrorMessage: el paquete libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libwind0-heimdal:i386 está en una versión diferente (1.7~git20150920+dfsg-4ubuntu1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: heimdal Title: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: el paquete libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libwind0-heimdal:i386 está en una versión diferente (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1634625 Title: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: el paquete libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libwind0-heimdal:i386 está en una versión diferente (1.7~git20150920 +dfsg-4ubuntu1) Status in heimdal package in Ubuntu: New Bug description: Problem occurred after trying to upgrade to yakety but the upgrade crashed so I manually ran the update from synaptic ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 ProcVersionSignature: Ubuntu 4.4.0-44.64-generic 4.4.24 Uname: Linux 4.4.0-44-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Oct 18 16:59:06 2016 Dependencies: gcc-6-base 6.2.0-5ubuntu12 libc6 2.24-3ubuntu1 libcomerr2 1.43.3-1 libgcc1 1:6.2.0-5ubuntu12 libroken18-heimdal 1.7~git20160703+dfsg-1 ErrorMessage: el paquete libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libwind0-heimdal:i386 está en una versión diferente (1.7~git20150920+dfsg-4ubuntu1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: heimdal Title: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: el paquete libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libwind0-heimdal:i386 está en una versión diferente (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1634625/+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 1634624] [NEW] package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: el paquete libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configu
Public bug reported: Problem occurred after trying to upgrade to yakety but the upgrade crashed so I manually ran the update from synaptic ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ProcVersionSignature: Ubuntu 4.4.0-44.64-generic 4.4.24 Uname: Linux 4.4.0-44-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Oct 18 16:59:07 2016 ErrorMessage: el paquete libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libhcrypto4-heimdal:i386 está en una versión diferente (1.7~git20150920+dfsg-4ubuntu1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: heimdal Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: el paquete libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libhcrypto4-heimdal:i386 está en una versión diferente (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1634624 Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: el paquete libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libhcrypto4-heimdal:i386 está en una versión diferente (1.7~git20150920+dfsg-4ubuntu1) Status in heimdal package in Ubuntu: New Bug description: Problem occurred after trying to upgrade to yakety but the upgrade crashed so I manually ran the update from synaptic ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ProcVersionSignature: Ubuntu 4.4.0-44.64-generic 4.4.24 Uname: Linux 4.4.0-44-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Oct 18 16:59:07 2016 ErrorMessage: el paquete libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libhcrypto4-heimdal:i386 está en una versión diferente (1.7~git20150920+dfsg-4ubuntu1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: heimdal Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: el paquete libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 no se puede configurar porque libhcrypto4-heimdal:i386 está en una versión diferente (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1634624/+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 1634614] [NEW] CPU usage spikes and mouse flicker
Public bug reported: I am experiencing cpu usage spikes with xorg where everything will lag for about a second. Seems to happen every minute or few. Other possibly related symptoms: Seeing flickering of the mouse pointer when it's over certain interactive fields or just at the top of my laptop monitor. Experiencing screen tearing in a diagonal line across second monitor When I set up the second monitor, backgrounds fail to display. Changing background fixes. Sometimes the second monitor just starts flicking off and on. Setup: Just upgraded from 16.04 to 16.10 (didn't see any of this on previous version) Using a second monitor connected via display port USB mouse and keyboard connected. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 18 20:09:40 2016 DistUpgraded: 2016-10-15 18:08:14,205 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-43-generic, x86_64: installed bbswitch, 0.8, 4.8.0-22-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated Graphics Controller [103c:1909] NVIDIA Corporation GK208GLM [Quadro K610M] [10de:12b9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK208GLM [Quadro K610M] [103c:1909] InstallationDate: Installed on 2016-07-26 (84 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) LightdmDisplayLog: resize called 2560 1440 MachineType: Hewlett-Packard HP ZBook 15 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro apparmor=1 security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-10-15 (3 days ago) dmi.bios.date: 10/28/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.34 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.55 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.34:bd10/28/2015:svnHewlett-Packard:pnHPZBook15:pvrA3009CD10002:rvnHewlett-Packard:rn1909:rvrKBCVersion94.55:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 dmi.product.version: A3009CD10002 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Oct 18 14:59:35 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. 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/1634614 Title: CPU usage spikes and mouse flicker Status in xorg package in Ubuntu: New Bug description: I am experiencing cpu usage spikes with xorg where everything will lag for about a second. Seems to happen every minute or few. Other possibly related symptoms: Seeing flickering of the mouse pointer when it's over certain interactive fields or just at the top of my laptop monitor. Experiencing screen tearing in a diagonal line across second monitor When I set up the second monitor, backgrounds fail to display. Changing background fixes. Sometimes the second monitor just starts flicking off
[Touch-packages] [Bug 1634199] Re: In 16.10, LXD won't work with enforced dsnmasq profile
Yes, so basically we have: - dnsmasq.pid (create + read/write by dnsmasq) - dnsmasq.raw (read by dnsmasq) - dnsmasq.hosts (read by dnsmasq) - dnsmasq.leases (create + read/write by dnsmasq) I'd be tempted to just go with: /var/lib/lxd/networks/*/dnsmasq.pid rw, /var/lib/lxd/networks/*/dnsmasq.leases rw, /var/lib/lxd/networks/*/dnsmasq.* r, That should make things a bit more future proof should we add any more dnsmasq related files in there. -- 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/1634199 Title: In 16.10, LXD won't work with enforced dsnmasq profile Status in AppArmor: New Status in apparmor package in Ubuntu: New Bug description: After upgrading to 16.0, LXD networking stopped working due to enforced dnsmasq profile. audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED" operation="truncate" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540 comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1634199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630014] Re: GPS is unable to find any position
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: location-service (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1630014 Title: GPS is unable to find any position Status in Canonical System Image: New Status in location-service package in Ubuntu: Confirmed Bug description: Even if you enable tracking position on Aquaris E 4.5, either with here drive or just with the GPS on, no position is tracked. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610944] Re: Can't add any online accounts
I found a partial workaround. If you remove the account from online accounts and then reboot. Then you can successfully re-add the account. The account will work until you log out again. Then you will need to remove/reboot. I think there might be a problem with how accounts are stored. This wasn't an issue in 16.04 so I'm pretty sure it's a new bug added with 16.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: Can't add any online accounts Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1610944/+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 1629620] Re: DNS resolver stops accepting queries
I noticed this issue on one of the two computers I upgraded from xenial to yakkety. Specifically the affected computer was an 2016 Dell XPS 13. They're both similarly configured ubuntu installations with Broadcom nics, so it's curious that this only affects one of them. I'm not sure what debug information would be helpful, but I'm happy to provide anything that would be useful. -- 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/1629620 Title: DNS resolver stops accepting queries Status in network-manager package in Ubuntu: Confirmed Bug description: After a while / after resume from suspend, the system becomes unable to respond to DNS queries, with the following output for example: $ nslookup google.com 127.0.1.1 Server: 127.0.1.1 Address: 127.0.1.1#53 ** server can't find google.com: REFUSED This is on an up to date yakkety install. Changing resolv.conf to use 8.8.8.8, or restarting network-manager appears to fix this, at least until it recurs again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 1 21:28:51 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-08-21 (407 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.5 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 63f0b05b-f699-4a68-81ce-f62d2c1a247d /org/freedesktop/NetworkManager/ActiveConnection/0 wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/4 HOME-1622-5 6df3f2f0-fb86-43b5-802a-d59bc5734be3 /org/freedesktop/NetworkManager/ActiveConnection/2 24:DA:9B:B9:09:0E btdisconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629620/+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 1634419] Re: In 16.10, several apps want write access to /run/systemd/journal/socket
*** This bug is a duplicate of bug 1634418 *** https://bugs.launchpad.net/bugs/1634418 ** This bug is no longer a duplicate of bug 1598759 AppArmor nameservice abstraction doesn't allow communication with systemd-resolved ** This bug has been marked a duplicate of bug 1634418 In 16.10, several apps want write access to /run/systemd/journal/socket -- 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/1634419 Title: In 16.10, several apps want write access to /run/systemd/journal/socket Status in apparmor package in Ubuntu: Confirmed Bug description: Several app try to write into /run/systemd/journal/socket Maybe this should be an abstraction ? Firefox: audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/run/systemd/journal/socket" pid=25552 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 evince: audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince" name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 11:00:02 2016 InstallationDate: Installed on 2015-10-04 (379 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED" operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server" interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive" pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443 peer_label="unconfined" Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus mediation is enabled Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634419/+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 1634418] Re: In 16.10, several apps want write access to /run/systemd/journal/socket
** Also affects: apparmor Importance: Undecided Status: New ** Tags added: aa-policy -- 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/1634418 Title: In 16.10, several apps want write access to /run/systemd/journal/socket Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Bug description: Several app try to write into /run/systemd/journal/socket Maybe this should be an abstraction ? Firefox: audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/run/systemd/journal/socket" pid=25552 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 evince: audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince" name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 11:00:02 2016 InstallationDate: Installed on 2015-10-04 (379 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED" operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server" interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive" pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443 peer_label="unconfined" Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus mediation is enabled Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1634418/+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 1610944] Re: Can't add any online accounts
I found a partial workaround. If you remove the account from online accounts and then reboot. Then you can successfully re-add the account. The account will work until you log out again. Then you will need to remove/reboot. I think there might be a problem with how accounts are stored. This wasn't an issue in 16.04 so I'm pretty sure it's a new bug added with 16.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: Can't add any online accounts Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1610944/+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 1628552] Re: on startup gateway & dns- options in /etc/network/interfaces are not always set
bump! definitely a repeatable issue albeit sporadically. lost another system on reboot - no default gateway installed although it's set in /e/n/i. have to manually add route via rc.local and symlink /etc/resolv.conf.d/resolv.conf original to tail as workarounds. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1628552 Title: on startup gateway & dns- options in /etc/network/interfaces are not always set Status in ifupdown package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: recently i have upgraded 4 VM-based systems to 16.04.1 LTS (Xenial Xerus). on startup, settings within /etc/network/interfaces do not appear to be taking effect reliably. specifically, the gateway and dns- settings have been problematic for me. on subsequent restarts, all or some of the settings take effect other times the gateway is set and the dns- options are not set. very problematic when the default gateway is not added to the routing table. the dns- settings were a bit easier to illustrate the issue. i added a comment to /etc/resolvconf/resolv.conf.d/base (# base) & etc/resolvconf/resolv.conf.d/tail (# tail). $ cat /etc/resolvconf/resolv.conf.d/* # base # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail on startup on 1 of the systems showed this: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # tail you can see the "# base" comment wasn't added. let me know if i can add anymore details or if this should be posted somewhere else. $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1.1 Candidate: 0.8.10ubuntu1.1 Version table: *** 0.8.10ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.10ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages $ apt-cache policy resolvconf resolvconf: Installed: 1.78ubuntu2 Candidate: 1.78ubuntu2 Version table: *** 1.78ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628552/+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 1634199] Re: In 16.10, LXD won't work with enforced dsnmasq profile
"c" means to create a file, so you'll need write permissions. Judging on other rules in the profile, you'll also need read permissions. To sum it up: /var/lib/lxd/networks/*/dnsmasq.pid rw, Anything else after adding this? -- 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/1634199 Title: In 16.10, LXD won't work with enforced dsnmasq profile Status in AppArmor: New Status in apparmor package in Ubuntu: New Bug description: After upgrading to 16.0, LXD networking stopped working due to enforced dnsmasq profile. audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED" operation="truncate" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540 comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1634199/+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 1634598] [NEW] gnome-online-accounts Problems on Wayland
Public bug reported: When using gnome-online-accounts + wayland. When tshooting [LP1610944](https://bugs.launchpad.net/bugs/1610944) I noticed that you can't add a google account that utilizes customizations from [Google's Identity Platform](https://developers.google.com/identity/). This is used by many Google Apps for Work systems (including mine). This however does work on gnome with X. I believe this is a wayland specific issue. ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-google-integration gnome-online-accounts wayland -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1634598 Title: gnome-online-accounts Problems on Wayland Status in gnome-online-accounts package in Ubuntu: New Bug description: When using gnome-online-accounts + wayland. When tshooting [LP1610944](https://bugs.launchpad.net/bugs/1610944) I noticed that you can't add a google account that utilizes customizations from [Google's Identity Platform](https://developers.google.com/identity/). This is used by many Google Apps for Work systems (including mine). This however does work on gnome with X. I believe this is a wayland specific issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1634598/+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 1629620] Re: DNS resolver stops accepting queries
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1629620 Title: DNS resolver stops accepting queries Status in network-manager package in Ubuntu: Confirmed Bug description: After a while / after resume from suspend, the system becomes unable to respond to DNS queries, with the following output for example: $ nslookup google.com 127.0.1.1 Server: 127.0.1.1 Address: 127.0.1.1#53 ** server can't find google.com: REFUSED This is on an up to date yakkety install. Changing resolv.conf to use 8.8.8.8, or restarting network-manager appears to fix this, at least until it recurs again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 1 21:28:51 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-08-21 (407 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.5 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 63f0b05b-f699-4a68-81ce-f62d2c1a247d /org/freedesktop/NetworkManager/ActiveConnection/0 wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/4 HOME-1622-5 6df3f2f0-fb86-43b5-802a-d59bc5734be3 /org/freedesktop/NetworkManager/ActiveConnection/2 24:DA:9B:B9:09:0E btdisconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629620/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF
The biggest issue the libnl upgrade will fix are the following libvirt errors with 3.13.0 LTS kernel: internal error: missing IFLA_VF_INFO in netlink response Hence the package should be updated. I had those issues with the xenial LTS kernel too until the libnl was updated -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1567578 Title: libnl should be updated to support up to 63 VFs per single PF Status in libnl3 package in Ubuntu: Confirmed Bug description: Ubuntu 14.04.4 and SRIOV settings. As already documented in https://bugs.launchpad.net/mos/+bug/1501738 there is a bug in the default libnl library release installed on Ubuntu 14.04.4 The library release is the 3.2.21-1 and the bug is impacting on the maximum VFs number that can be enabled (up to 30) even if the PF supports up to 63 VFs in an Openstack SRIOV configuration The workaround is to install a newer library release, the 3.2.24-2: wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb dpkg -i libnl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1634353] Re: file index is not responding
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Are you sure that the bug needs reporting against the xorg package? Thanks! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1634353 Title: file index is not responding Status in xorg package in Ubuntu: Incomplete Bug description: file index is not responding ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Oct 18 05:43:18 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.6, 4.4.0-43-generic, x86_64: installed virtualbox, 5.1.6, 4.8.0-25-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7640G] [103c:1984] InstallationDate: Installed on 2016-07-01 (108 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-25-generic.efi.signed root=UUID=7eb94228-e677-4c99-944a-8d239a78479f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1984 dmi.board.vendor: Hewlett-Packard dmi.board.version: 01.13 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd09/26/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097611405E0620180:rvnHewlett-Packard:rn1984:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.version: 097611405E0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Oct 18 05:17:29 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634353/+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 1538284] Re: Unescaped left brace in regex is deprecated
I confirm that installing postgresql-9.6 still produces multiple messages on a freshly updated 16.04 server instance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1538284 Title: Unescaped left brace in regex is deprecated Status in pam package in Ubuntu: Confirmed Bug description: When installing postgresql on Ubuntu 16.04 (xenial), the following warning are raised: Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/(?https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1538284/+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 1622089] Re: timezone parser in qt-5.5 breaks KDE clock
With libqt5core5a 5.5.1+dfsg-16ubuntu7.2 I have no problem for the Asia/Novosibirsk timezone. Sorry for delay. I faced another bug that I did not noticed just after upgrade to 16.04. Now I see that missing cities such as Europe/Astrakhan or Asia/Barnaul in digital clock settings are unrelated to Qt version. The behavior is the same for 5.5.1+dfsg-16ubuntu7.1 and for 5.5.1+dfsg-16ubuntu7.2. Thank you for backporting of the fix. $ LANG=C apt-cache policy libqt5core5a libqt5core5a: Installed: 5.5.1+dfsg-16ubuntu7.2 Candidate: 5.5.1+dfsg-16ubuntu7.2 Version table: *** 5.5.1+dfsg-16ubuntu7.2 500 500 http://ru.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.5.1+dfsg-16ubuntu7.1 500 500 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 5.5.1+dfsg-16ubuntu7 500 500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ** 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 qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1622089 Title: timezone parser in qt-5.5 breaks KDE clock Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Fix Committed Bug description: [ Impact ] People in certain timezones have buggy time conversions in all Qt apps. [ Test Case ] See bug report. [ Regression Potential ] Should be low, in upstream LTS release and includes unit tests during build time. --- original bug report --- For a set of timezones in tzdata-2016* Qt parser produces wrong result in Qt versions earlier than 5.6. In kubuntu-16.04 xenial xerus the most annoying issue is broken digital clock plasmoid on the default KDE panel if system timezone is set to e.g. Asia/Novosibirsk. All Qt programs that attempts to convert time to non-default timezone are affected as well in xenial and earlier ubuntu released including ubuntu-14.04 LTS trusty. I consider the bug is nasty enough for updating Qt in LTS ubuntu releases. The upstream bug is https://bugreports.qt.io/browse/QTBUG-53071 "QTimeZone mishandles tzdata 2016b and later in Russia, Kazakhstan". The direct link to the patch that fixes the problem is https://codereview.qt-project.org/gitweb?p=qt/qtbase.git;a=patch;h=e9041c7fc1052167f1ec2df0ea9623059e55d00f I have rebuilt qtbase-opensource-src-5.5.1+dfsg (-16ubuntu7.1) from sources with the patch applied and the bug has gone away. A bit more details. I faced the problem with Kubuntu 16.04.1, x86_64. Asia/Novosibirsk has UTC+07:00 offset last a couple of months but KDE clock shows a time that has offset of 14 hours from the actual wall time, so it is rather unusable. Command line tool "date" reports correct local time. KDE digital clock works correctly in e.g. Asia/Krasnoyarsk timezone. It as a workaround if time transition history does not matter. Some other timezones affected by the bug (tzdata-2106f) file europe: Europe/Astrakhan Europe/Kirov Europe/Ulyanovsk Asia/Barnaul Asia/Novosibirsk Asia/Tomsk Asia/Novokuznetsk file asia: Asia/Almaty Asia/Qyzylorda Asia/Aqtobe Asia/Aqtau Asia/Oral A simple program to demonstrate the problem: #include #include #include int main() { QTimeZone tz = QTimeZone(QTimeZone::systemTimeZoneId()); QDateTime current = QDateTime::currentDateTime(); qDebug() << "current offset" << tz.offsetFromUtc(current); return 0; } It reports 0 for incorrectly parsed timezones. The only thing that bothers me is that I had to disable tests when was rebuilding libqt5core5a_5.5.1+dfsg-16ubuntu7.1_amd64.deb using dpg-buildpackage. Otherwise I got error with cmake in tests/auto/cmake/. Cmake was unable to find qt libraries in the build tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1622089/+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 1634549] Re: [webbrowser] sound and video doesn't work with rocket.chat
** Summary changed: - sound and video doesn't work with rocket.chat + [webbrowser] sound and video doesn't work with rocket.chat -- 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/1634549 Title: [webbrowser] sound and video doesn't work with rocket.chat Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: tested on arale/rc-proposed and M10 go to https://demo.rocket.chat/channel/ubuntu-snap it will ask you to login, you can use twitter, g+ etc text, sending attachments works but sending audio or video doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1634549/+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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ufw (Ubuntu) Status: New => Confirmed -- 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: Confirmed 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 1611078] Re: Support snaps inside of lxd containers
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1611078 Title: Support snaps inside of lxd containers Status in Snappy: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: New Status in linux source package in Xenial: Fix Committed Status in lxd source package in Xenial: Fix Committed Status in apparmor source package in Yakkety: Fix Released Status in linux source package in Yakkety: Fix Released Status in lxd source package in Yakkety: Fix Released Bug description: I tried following the instructions on snapcraft.io and got a failure. See the output below. I've also attached the relevant output from running "journalctl -xe". uname: Linux 3.19.0-65-generic x86_64 release: Ubuntu 16.04 package: snapd 2.11+0.16.04 Notably, I'm running this in an LXD container (version: 2.0.0.rc9). - $ sudo snap install hello-world 64.75 MB / 64.75 MB [==] 100.00 % 2.85 MB/s error: cannot perform the following tasks: - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See "systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for details. ) $ ls -la /snap total 4K drwxr-xr-x 3 root root 4096 Aug 8 17:49 ubuntu-core $ ls -la /snap/ubuntu-core/ total 4K drwxr-xr-x 2 root root 4096 Aug 8 17:49 122 $ ls -la /snap/ubuntu-core/122/ total 0K $ systemctl status "snap-ubuntu\\x2dcore-122.mount" ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min ago Where: /snap/ubuntu-core/122 What: /var/lib/snapd/snaps/ubuntu-core_122.snap Process: 31781 ExecMount=/bin/mount /var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs (code=exited, status=32) Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core... Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount failed: Unknown error -1 Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount process exited, code=exited status=32 Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for ubuntu-core. Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1611078/+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 1634549] [NEW] sound and video doesn't work with rocket.chat
Public bug reported: tested on arale/rc-proposed and M10 go to https://demo.rocket.chat/channel/ubuntu-snap it will ask you to login, you can use twitter, g+ etc text, sending attachments works but sending audio or video doesn't work. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Description changed: go to https://demo.rocket.chat/channel/ubuntu-snap - it will ask you to login, you can use twitter, g+ + it will ask you to login, you can use twitter, g+ etc text, sending attachments works but sending audio or video doesn't work. -- 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/1634549 Title: sound and video doesn't work with rocket.chat Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: tested on arale/rc-proposed and M10 go to https://demo.rocket.chat/channel/ubuntu-snap it will ask you to login, you can use twitter, g+ etc text, sending attachments works but sending audio or video doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1634549/+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 1634549] Re: sound and video doesn't work with rocket.chat
https://lists.launchpad.net/ubuntu-phone/msg22664.html ** Description changed: + tested on arale/rc-proposed and M10 go to https://demo.rocket.chat/channel/ubuntu-snap it will ask you to login, you can use twitter, g+ etc text, sending attachments works but sending audio or video doesn't work. -- 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/1634549 Title: sound and video doesn't work with rocket.chat Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: tested on arale/rc-proposed and M10 go to https://demo.rocket.chat/channel/ubuntu-snap it will ask you to login, you can use twitter, g+ etc text, sending attachments works but sending audio or video doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1634549/+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 1610944] Re: Can't add any online accounts
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: Can't add any online accounts Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1610944/+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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
Is there any chance the fix for this bug makes it to OTA-14, as to have not a bluetooth is very limiting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1580792] Re: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do)
Here is my unity8.log with INTEL_DEBUG=perf. It's quite obscure for me as I'm not a developer, but I did find the problems you mentioned it your comments. I'll let you check! ** Attachment added: "unity8.log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1580792/+attachment/4763298/+files/unity8.log -- 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/1580792 Title: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do) Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: (problem forked from bug 1549455) Unity8 on Intel Pineview performs very poorly. Frame times appears to be up to 900ms, Qt's renderer thread using 100% CPU. Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA errors: http://paste.ubuntu.com/16344427/ Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like OpenGL features that Unity8 is hitting but mir-demos don't. So those gl calls are also good candidates for explaining poor performance, especially if Mesa is falling back to software rendering for them." Since Qt tends to perform just fine on that hardware in X11, something isn't right. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
As I suggested in bug 1634176, I think that we can extend the 'ip=' parameter to work as it has a 'autoconf' parameter in it, which indicates the type of "auto" configuration to do: klibc documents the previous ip= syntax at README.ipconfig [1]. :: My suggestion is to extend the 'autoconf' parameter. Previously the supported documented values were 'rarp', 'bootp', 'both', 'dhcp', 'all', 'off', 'static', 'none'. I suggest we add 'dhcp6' to the the list. We could also support 'dhcp4,dhcp6' or 'dhcp+dhcp6' indicating both should be tried or possibly dhcp6 if and only if dhcp4 failed. I think though, for the immediate use case that just adding 'dhcp6' to the autoconf types would suffice. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Fix Released Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: Fix Released Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Triaged Status in isc-dhcp source package in Xenial: Fix Released Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: In Progress Status in isc-dhcp source package in Yakkety: Fix Released Status in klibc source package in Yakkety: Won't Fix Status in open-iscsi source package in Yakkety: Fix Released Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 908293] Re: Sound does not work on 12.04 (alpha); suspected regression
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/908293 Title: Sound does not work on 12.04 (alpha); suspected regression Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Speaker does not work (whether external speakers are plugged in or not), and External Speakers do not work either. I can't get any sound to work. I was peviously using 10.04 LTS and decided to try the 12.04 alpha. My sound was working in 10.04 even though both the internal speaker and external speaker output sound at the same time (so i unplugged the internal speaker as a easy solution). I plugged the internal speaker back in for this test since i could get no sound from the external one, but niether seem to work. Relevant results from 'lspci': 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02) 04:00.0 Multimedia controller: Broadcom Corporation BCM70015 Video Decoder [Crystal HD] Results from 'lsb_release -rd': Description: Ubuntu precise (development branch) Release: 12.04 andrew@ubuntu-desktop:~$ apt-cache policy alsa-driver N: Unable to locate package alsa-driver andrew@ubuntu-desktop:~$ apt-cache policy alsa alsa: Installed: (none) Candidate: (none) Version table: I tried using apport, but it also says that 'alsa' and 'alsa-driver' does not exist. Maybe thats the problem? Since there was at least some functionality in 10.04 with Gnome, i'm assuming that this is either a regression or something is not installed correctly. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.24+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6 Uname: Linux 3.2.0-6-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.90-0ubuntu1 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3c', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfed94000 irq 45' Mixer name : 'Realtek ALC1200' Components : 'HDA:10ec0888,105b0d57,00100101' Controls : 21 Simple ctrls : 10 CheckboxCommand: gst_pipeline_test -t 2 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink' CheckboxData: Internal Speaker does not work (whether external speakers are plugged in or not), and External Speakers do not work either. I can't get any sound to work. CheckboxTest: audio/playback_auto Date: Fri Dec 23 16:00:18 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: alsa-driver UpgradeStatus: Upgraded to precise on 2011-12-22 (0 days ago) dmi.bios.date: 01/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: $(Model_Name) dmi.board.vendor: FOXCONN dmi.board.version: Ver 0.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd01/22/2010:svnHONHAIPRECISIONIND.CO.,LTD:pnNETBOXNT-410/510:pvrVer0.001:rvnFOXCONN:rn$(Model_Name):rvrVer0.001:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: NETBOX NT-410/510 dmi.product.version: Ver 0.001 dmi.sys.vendor: HON HAI PRECISION IND.CO.,LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/908293/+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 1633643] Re: unnecessary dependency upon isc-dhcp-client
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1633643 Title: unnecessary dependency upon isc-dhcp-client Status in initramfs-tools package in Ubuntu: New Bug description: with xenial-updates, there is suddenly a dependency [isc-dhcp-client] not previously there. please mark this as recommends/suggests/enhances instead of as a depends, as it is not critical to the core functionality of the software. since ubuntu now defaults to installing recommends unless configured otherwise, this compromise accommodates both the unskilled users as well as those who know what they are doing and have disabled automatic installation of suggested packages. 1] >lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2] >apt-cache policy initramfs-tools initramfs-tools: Installed: 0.122ubuntu8.3 Candidate: 0.122ubuntu8.3 Version table: *** 0.122ubuntu8.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 0.122ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 3] i expected to not be forced to install unnecessary packages 4] i was forced to thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1633643/+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 1634464] Re: cloudimg apt missing dirmngr
@juliank apt-key adv is not deprecated. Maybe it should be marked as deprecated. > Drop files in trusted.gpg.d instead. can the man page for apt-key include how to do this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1634464 Title: cloudimg apt missing dirmngr Status in apt package in Ubuntu: Invalid Bug description: apt-key adv --keyserver keyserver.ubuntu.com --recv 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 Warning: apt-key output should not be parsed (stdout is not a terminal) Executing: /tmp/tmp.Qv81Vl3Idi/gpg.1.sh --keyserver keyserver.ubuntu.com --recv 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory gpg: connecting dirmngr at '/tmp/tmp.Qv81Vl3Idi/S.dirmngr' failed: No such file or directory gpg: keyserver receive failed: No dirmngr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1634464/+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 1634464] Re: cloudimg apt missing dirmngr
APT recommends gnupg, and gnupg recommends dirmngr, so all is working as intended. If you want to use optional (deprecated) features of apt-key like adv, you have to manually install gnupg. If you want to use optional features depending on key servers, you have to install dirmngr manually. The adv option is deprecated, like almost everything else. Drop files in trusted.gpg.d instead. The recommends on gnupg will be downgraded to a suggests at a later point. ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1634464 Title: cloudimg apt missing dirmngr Status in apt package in Ubuntu: Invalid Bug description: apt-key adv --keyserver keyserver.ubuntu.com --recv 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 Warning: apt-key output should not be parsed (stdout is not a terminal) Executing: /tmp/tmp.Qv81Vl3Idi/gpg.1.sh --keyserver keyserver.ubuntu.com --recv 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory gpg: connecting dirmngr at '/tmp/tmp.Qv81Vl3Idi/S.dirmngr' failed: No such file or directory gpg: keyserver receive failed: No dirmngr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1634464/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
subwoofer doesn't work in ubuntu 16.10. Lenovo Y700-15ISK -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Expired Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1633776] Re: Crash due to SATA 3 issue in Skylake chip
** Package changed: apport (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1633776 Title: Crash due to SATA 3 issue in Skylake chip Status in linux package in Ubuntu: New Bug description: Minor bug - I have an annoying work around ASRock Z170 Extreme7+ Mboard has 10 SATA 3 ports off 2 controller chips CPU is Skylake 6700. One SATA chip does 6 ports in pairs which also serve as either SATA Express or M.2 drive controllers. these are SATA 3-0 to SATA 3-5, other has 4 SATA ports. System worked in Win 7, but when booting to Kubuntu 16.10 it kept coming crashing during boot with an error of 'Unable to initiate SATA child Parent inactive.' I tried every possible combination, and eventually got the system to load by placing an Optical drive as SAT 3-0, and writing off one of the SATA Express links. Once I got it going I started adding drives back in one at a time, and hit the same problem when I got to the first SATA port on the 2nd chip, and optical drive plugged in there soon fixed that. Another issue was I couldn't create an M.2 drive as the system drive while there was a hard drive connected to the system. Cut it back to just the optical and the M.2 and it let me use the M.2 as the system drive. System now working with SATA 3-0 as optical, SATA 3-1 as 2TB HDD, SATA 3-2/3 as 500GB M.2, SATA 3 -4/5 as 500GB M.2, SATA 3A-0 as optical, SATA 3A-2 as 2TB HDD. Tested, as soon as I move an optical from the first SATA port for the chip I get the error message during the boot- up and it doesn't load. Switch back and it loads OK. I've a work around, but it costs me a SATA Express line. However, you may see others with Skylake chips havign the same issue. I suspect it's an issue with the package checking the hardware during the boot-up, but don't know enough to say for sure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633776/+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 1634418] Re: In 16.10, several apps want write access to /run/systemd/journal/socket
** This bug is no longer a duplicate of bug 1598759 AppArmor nameservice abstraction doesn't allow communication with systemd-resolved -- 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/1634418 Title: In 16.10, several apps want write access to /run/systemd/journal/socket Status in apparmor package in Ubuntu: Confirmed Bug description: Several app try to write into /run/systemd/journal/socket Maybe this should be an abstraction ? Firefox: audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/run/systemd/journal/socket" pid=25552 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 evince: audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince" name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 11:00:02 2016 InstallationDate: Installed on 2015-10-04 (379 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED" operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server" interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive" pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443 peer_label="unconfined" Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus mediation is enabled Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634418/+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 1580792] Re: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do)
The original bug description is a bit vague here. In comment #3 I was aiming to make this bug very definite. If you add INTEL_DEBUG=perf then you will see the errors I mentioned. I think this bug should be about those errors in comment #3 since the bug description is a bit too vague. Please add INTEL_DEBUG=perf to your /etc/environment to help us determine if you are experiencing this bug or something different. -- 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/1580792 Title: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do) Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: (problem forked from bug 1549455) Unity8 on Intel Pineview performs very poorly. Frame times appears to be up to 900ms, Qt's renderer thread using 100% CPU. Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA errors: http://paste.ubuntu.com/16344427/ Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like OpenGL features that Unity8 is hitting but mir-demos don't. So those gl calls are also good candidates for explaining poor performance, especially if Mesa is falling back to software rendering for them." Since Qt tends to perform just fine on that hardware in X11, something isn't right. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580792/+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 1634412] Re: Unity8 session fails to start due to unity-system-compositor
Is there any more log I can provide that could shed a light on this? This bug is very easily reproducible on my computer, so I should be able to provide relevant logs! My computer is not a fresh install and has been upgraded every step of the way since 14.10. I'll try a LiveUSB of 16.10 to see if the problem persists. -- 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/1634412 Title: Unity8 session fails to start due to unity-system-compositor Status in Light Display Manager: New Status in Unity System Compositor: New Status in lightdm package in Ubuntu: New Bug description: Hi, I've upgraded to 16.10 to try out the latest and the greatest. Unfortunately, the Unity8 session does not work anymore. It was working as expected on 16.04 with the overlay PPA. When I select "Unity8" in lightdm and enter my password, the password box disappears, and nothing else happens. I can still access all the indicators, so lightdm is not completely frozen. I then have to reboot or restart lightdm in tty1 to log in Unity 7. I do have a "system problem detected" warning and I did send the report, but I can't find it on Launchpad, that's why I'm filing this bug manually. I'm using Ubuntu 16.10 64bits, with the opensource radeon driver. Further info from the automatic bug report: Title : unity-system-compositor crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() I'm attaching some logs that might be useful. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1634412/+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 1634418] Re: In 16.10, several apps want write access to /run/systemd/journal/socket
dino99, please note, this bug is for writing to the journald socket, which is unrelated to the dbus system socket that is referenced in the other bug. Thanks ** This bug is no longer a duplicate of bug 1598759 AppArmor nameservice abstraction doesn't allow communication with systemd-resolved -- 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/1634418 Title: In 16.10, several apps want write access to /run/systemd/journal/socket Status in apparmor package in Ubuntu: Confirmed Bug description: Several app try to write into /run/systemd/journal/socket Maybe this should be an abstraction ? Firefox: audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/run/systemd/journal/socket" pid=25552 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 evince: audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince" name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 11:00:02 2016 InstallationDate: Installed on 2015-10-04 (379 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED" operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server" interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive" pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443 peer_label="unconfined" Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus mediation is enabled Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634418/+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 1628956] Re: From v49.0, Firefox needs read access to @{PROC}/net/arp
Motivation for this new requirement is: ## Why Each particular network your computer and browser run in has its own set of network conditions, routers, proxies and MITM situations. Changing between networks also changes proxies. Intercepting or explicit, willing or unwilling, HTTP or even HTTPS with custom installed trust-roots. This makes the web content cache, the cookie store and others to save contents from one network that is potentially different than what is received over other networks. It can lead to content pollution and information leaks, on purpose by malicious actors or just by mistake. see the details here https://bug1240932.bmoattachments.org/attachment.cgi?id=8709691 -- 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/1628956 Title: From v49.0, Firefox needs read access to @{PROC}/net/arp Status in apparmor package in Ubuntu: New Bug description: Since the latest upgrade of Firefox to 49.0, it will need read access to @{PROC}/net/arp I don't know what the security implications are, so I don't know if we want to give read access to explicitely deny it. Both seem to work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor-profiles 2.10.95-0ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 29 16:55:21 2016 InstallationDate: Installed on 2015-10-04 (361 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Sep 29 10:37:52 franck-ThinkPad-T430s dbus[2546]: [system] AppArmor D-Bus mediation is enabled Sep 29 16:50:57 franck-ThinkPad-T430s dbus[2410]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.sbin.klogd: [modified] modified.conffile..etc.apparmor.d.sbin.syslogd: [modified] modified.conffile..etc.apparmor.d.usr.bin.chromium-browser: [modified] modified.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: [modified] modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified] modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified] modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.nscd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified] mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535 mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968 mtime.conffile..etc.apparmor.d.usr.bin.chromium-browser: 2015-10-05T12:02:05.273141 mtime.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: 2016-04-13T19:13:25.829679 mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2016-04-13T19:13:05.941424 mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323 mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403 mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523 mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794 mtime.conffile..etc.apparmor.d.usr.sbin.nscd: 2016-04-13T19:14:17.520643 mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628956/+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 1634199] Re: In 16.10, LXD won't work with enforced dsnmasq profile
Another message: audit: type=1400 audit(1476791887.152:118): apparmor="DENIED" operation="mknod" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd/networks/lxdbr0/dnsmasq.pid" pid=5480 comm="dnsmasq" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 -- 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/1634199 Title: In 16.10, LXD won't work with enforced dsnmasq profile Status in AppArmor: New Status in apparmor package in Ubuntu: New Bug description: After upgrading to 16.0, LXD networking stopped working due to enforced dnsmasq profile. audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED" operation="truncate" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540 comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1634199/+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 1634418] Re: In 16.10, several apps want write access to /run/systemd/journal/socket
*** This bug is a duplicate of bug 1598759 *** https://bugs.launchpad.net/bugs/1598759 ** This bug has been marked a duplicate of bug 1598759 AppArmor nameservice abstraction doesn't allow communication with systemd-resolved -- 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/1634418 Title: In 16.10, several apps want write access to /run/systemd/journal/socket Status in apparmor package in Ubuntu: Confirmed Bug description: Several app try to write into /run/systemd/journal/socket Maybe this should be an abstraction ? Firefox: audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/run/systemd/journal/socket" pid=25552 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 evince: audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince" name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 11:00:02 2016 InstallationDate: Installed on 2015-10-04 (379 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED" operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server" interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive" pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443 peer_label="unconfined" Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus mediation is enabled Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634418/+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 1634419] Re: In 16.10, several apps want write access to /run/systemd/journal/socket
*** This bug is a duplicate of bug 1598759 *** https://bugs.launchpad.net/bugs/1598759 ** This bug is no longer a duplicate of bug 1634418 In 16.10, several apps want write access to /run/systemd/journal/socket ** This bug has been marked a duplicate of bug 1598759 AppArmor nameservice abstraction doesn't allow communication with systemd-resolved -- 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/1634419 Title: In 16.10, several apps want write access to /run/systemd/journal/socket Status in apparmor package in Ubuntu: Confirmed Bug description: Several app try to write into /run/systemd/journal/socket Maybe this should be an abstraction ? Firefox: audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/run/systemd/journal/socket" pid=25552 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 evince: audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince" name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 11:00:02 2016 InstallationDate: Installed on 2015-10-04 (379 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED" operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server" interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive" pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443 peer_label="unconfined" Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus mediation is enabled Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634419/+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 1634412] Re: Unity8 session fails to start due to unity-system-compositor
I can't reproduce any such problem on a pure 16.10 install. The error: what(): option cannot be specified more than once implies that your lightdm is passing an extra option when it executes the unity-system-compositor command. ** Also affects: lightdm Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1634412 Title: Unity8 session fails to start due to unity-system-compositor Status in Light Display Manager: New Status in Unity System Compositor: New Status in lightdm package in Ubuntu: New Bug description: Hi, I've upgraded to 16.10 to try out the latest and the greatest. Unfortunately, the Unity8 session does not work anymore. It was working as expected on 16.04 with the overlay PPA. When I select "Unity8" in lightdm and enter my password, the password box disappears, and nothing else happens. I can still access all the indicators, so lightdm is not completely frozen. I then have to reboot or restart lightdm in tty1 to log in Unity 7. I do have a "system problem detected" warning and I did send the report, but I can't find it on Launchpad, that's why I'm filing this bug manually. I'm using Ubuntu 16.10 64bits, with the opensource radeon driver. Further info from the automatic bug report: Title : unity-system-compositor crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() I'm attaching some logs that might be useful. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1634412/+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 1592006] Re: package udev 229-4ubuntu6 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1592006 Title: package udev 229-4ubuntu6 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in systemd package in Ubuntu: Confirmed Bug description: m ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CustomUdevRuleFiles: 56-hpmud.rules Date: Mon Jun 13 16:06:04 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2016-05-10 (33 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E6400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=75bdb0e0-b9d3-4a55-adb8-ca944b37dd6b ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package udev 229-4ubuntu6 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0U695R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd10/30/2009:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0U695R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1592006/+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 1634419] Re: In 16.10, several apps want write access to /run/systemd/journal/socket
*** This bug is a duplicate of bug 1634418 *** https://bugs.launchpad.net/bugs/1634418 ** This bug has been marked a duplicate of bug 1634418 In 16.10, several apps want write access to /run/systemd/journal/socket -- 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/1634419 Title: In 16.10, several apps want write access to /run/systemd/journal/socket Status in apparmor package in Ubuntu: Confirmed Bug description: Several app try to write into /run/systemd/journal/socket Maybe this should be an abstraction ? Firefox: audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/run/systemd/journal/socket" pid=25552 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 evince: audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince" name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 11:00:02 2016 InstallationDate: Installed on 2015-10-04 (379 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED" operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server" interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive" pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443 peer_label="unconfined" Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus mediation is enabled Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634419/+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 1622089] Re: timezone parser in qt-5.5 breaks KDE clock
** Tags removed: xenia ** Tags added: xenial -- 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/1622089 Title: timezone parser in qt-5.5 breaks KDE clock Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Fix Committed Bug description: [ Impact ] People in certain timezones have buggy time conversions in all Qt apps. [ Test Case ] See bug report. [ Regression Potential ] Should be low, in upstream LTS release and includes unit tests during build time. --- original bug report --- For a set of timezones in tzdata-2016* Qt parser produces wrong result in Qt versions earlier than 5.6. In kubuntu-16.04 xenial xerus the most annoying issue is broken digital clock plasmoid on the default KDE panel if system timezone is set to e.g. Asia/Novosibirsk. All Qt programs that attempts to convert time to non-default timezone are affected as well in xenial and earlier ubuntu released including ubuntu-14.04 LTS trusty. I consider the bug is nasty enough for updating Qt in LTS ubuntu releases. The upstream bug is https://bugreports.qt.io/browse/QTBUG-53071 "QTimeZone mishandles tzdata 2016b and later in Russia, Kazakhstan". The direct link to the patch that fixes the problem is https://codereview.qt-project.org/gitweb?p=qt/qtbase.git;a=patch;h=e9041c7fc1052167f1ec2df0ea9623059e55d00f I have rebuilt qtbase-opensource-src-5.5.1+dfsg (-16ubuntu7.1) from sources with the patch applied and the bug has gone away. A bit more details. I faced the problem with Kubuntu 16.04.1, x86_64. Asia/Novosibirsk has UTC+07:00 offset last a couple of months but KDE clock shows a time that has offset of 14 hours from the actual wall time, so it is rather unusable. Command line tool "date" reports correct local time. KDE digital clock works correctly in e.g. Asia/Krasnoyarsk timezone. It as a workaround if time transition history does not matter. Some other timezones affected by the bug (tzdata-2106f) file europe: Europe/Astrakhan Europe/Kirov Europe/Ulyanovsk Asia/Barnaul Asia/Novosibirsk Asia/Tomsk Asia/Novokuznetsk file asia: Asia/Almaty Asia/Qyzylorda Asia/Aqtobe Asia/Aqtau Asia/Oral A simple program to demonstrate the problem: #include #include #include int main() { QTimeZone tz = QTimeZone(QTimeZone::systemTimeZoneId()); QDateTime current = QDateTime::currentDateTime(); qDebug() << "current offset" << tz.offsetFromUtc(current); return 0; } It reports 0 for incorrectly parsed timezones. The only thing that bothers me is that I had to disable tests when was rebuilding libqt5core5a_5.5.1+dfsg-16ubuntu7.1_amd64.deb using dpg-buildpackage. Otherwise I got error with cmake in tests/auto/cmake/. Cmake was unable to find qt libraries in the build tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1622089/+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 1634419] Re: In 16.10, several apps want write access to /run/systemd/journal/socket
** This bug is no longer a duplicate of bug 1598759 AppArmor nameservice abstraction doesn't allow communication with systemd-resolved -- 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/1634419 Title: In 16.10, several apps want write access to /run/systemd/journal/socket Status in apparmor package in Ubuntu: Confirmed Bug description: Several app try to write into /run/systemd/journal/socket Maybe this should be an abstraction ? Firefox: audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/run/systemd/journal/socket" pid=25552 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 evince: audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince" name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 11:00:02 2016 InstallationDate: Installed on 2015-10-04 (379 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED" operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server" interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive" pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443 peer_label="unconfined" Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus mediation is enabled Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634419/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets
If this is still a problem, what do we do now? Do I just keep testing with new releases and file new bugs? -- 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/1569925 Title: Shutdown hang on 16.04 with iscsi targets Status in systemd package in Ubuntu: Expired Bug description: I have 4 servers running the latest 16.04 updates from the development branch (as of right now). Each server is connected to NetApp storage using iscsi software initiator. There are a total of 56 volumes spread across two NetApp arrays. Each volume has 4 paths available to it which are being managed by device mapper. While logged into the iscsi sessions all I have to do is reboot the server and I get a hang. I see a message that says: "Reached target Shutdown" followed by "systemd-shutdown[1]: Failed to finalize DM devices, ignoring" and then I see 8 lines that say: "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" NOTE: the actual values of the *'s differ for each line above. This seems like a bug somewhere but I am unaware of any additional logging that I could turn on to pinpoint the problem. Note I also have similar setups that are not doing iscsi and they don't have this problem. Here is a screenshot of what I see on the shell when I try to reboot: https://www.dropbox.com/s/93mv7cj8asspcpa/ShutdownCapture.JPG?dl=0 This is being tracked in NetApp bug tracker CQ number 860251. If I log out of all iscsi sessions before rebooting then I do not experience the hang: iscsiadm -m node -U all We are wondering if this could be some kind of shutdown ordering problem. Like the network devices have already disappeared and then iscsi tries to perform some operation (hence the ping timeouts). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1622089] Re: timezone parser in qt-5.5 breaks KDE clock
** Tags removed: xenial ** Tags added: kubuntul xenia ** Tags removed: kubuntul ** Tags added: kubuntu -- 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/1622089 Title: timezone parser in qt-5.5 breaks KDE clock Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Fix Committed Bug description: [ Impact ] People in certain timezones have buggy time conversions in all Qt apps. [ Test Case ] See bug report. [ Regression Potential ] Should be low, in upstream LTS release and includes unit tests during build time. --- original bug report --- For a set of timezones in tzdata-2016* Qt parser produces wrong result in Qt versions earlier than 5.6. In kubuntu-16.04 xenial xerus the most annoying issue is broken digital clock plasmoid on the default KDE panel if system timezone is set to e.g. Asia/Novosibirsk. All Qt programs that attempts to convert time to non-default timezone are affected as well in xenial and earlier ubuntu released including ubuntu-14.04 LTS trusty. I consider the bug is nasty enough for updating Qt in LTS ubuntu releases. The upstream bug is https://bugreports.qt.io/browse/QTBUG-53071 "QTimeZone mishandles tzdata 2016b and later in Russia, Kazakhstan". The direct link to the patch that fixes the problem is https://codereview.qt-project.org/gitweb?p=qt/qtbase.git;a=patch;h=e9041c7fc1052167f1ec2df0ea9623059e55d00f I have rebuilt qtbase-opensource-src-5.5.1+dfsg (-16ubuntu7.1) from sources with the patch applied and the bug has gone away. A bit more details. I faced the problem with Kubuntu 16.04.1, x86_64. Asia/Novosibirsk has UTC+07:00 offset last a couple of months but KDE clock shows a time that has offset of 14 hours from the actual wall time, so it is rather unusable. Command line tool "date" reports correct local time. KDE digital clock works correctly in e.g. Asia/Krasnoyarsk timezone. It as a workaround if time transition history does not matter. Some other timezones affected by the bug (tzdata-2106f) file europe: Europe/Astrakhan Europe/Kirov Europe/Ulyanovsk Asia/Barnaul Asia/Novosibirsk Asia/Tomsk Asia/Novokuznetsk file asia: Asia/Almaty Asia/Qyzylorda Asia/Aqtobe Asia/Aqtau Asia/Oral A simple program to demonstrate the problem: #include #include #include int main() { QTimeZone tz = QTimeZone(QTimeZone::systemTimeZoneId()); QDateTime current = QDateTime::currentDateTime(); qDebug() << "current offset" << tz.offsetFromUtc(current); return 0; } It reports 0 for incorrectly parsed timezones. The only thing that bothers me is that I had to disable tests when was rebuilding libqt5core5a_5.5.1+dfsg-16ubuntu7.1_amd64.deb using dpg-buildpackage. Otherwise I got error with cmake in tests/auto/cmake/. Cmake was unable to find qt libraries in the build tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1622089/+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 1633912] Re: Problem with DNS resolution after suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1633912 Title: Problem with DNS resolution after suspend Status in network-manager package in Ubuntu: Confirmed Bug description: I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I have network issues, one time I was not able to connect to a wifi network (might report another bug if this occurees again, but maybe it is related, as in network-manager is in some broken state after suspend). Here is whats happening pretty often: After resume from suspend I have a solid network connection, no problem to ping machines in LAN or on the internet. But DNS resolution is broken until I restart the network-manager service. I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it should be in there. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 21:01:09 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-09-28 (18 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev br-541a0f9bec93 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-541a0f9bec93 proto kernel scope link src 172.18.0.1 192.168.0.0/24 dev wlp58s0 proto kernel scope link src 192.168.0.118 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633912/+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 1624738] Re: Firefox search and location boxes have black borders when unselected
this seems to be a Firefox bug that should be fixed in Firefox 50: https://bugzilla.mozilla.org/show_bug.cgi?id=1266914 ** Bug watch added: Mozilla Bugzilla #1266914 https://bugzilla.mozilla.org/show_bug.cgi?id=1266914 -- 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/1624738 Title: Firefox search and location boxes have black borders when unselected Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: In Progress Bug description: [Impact] As seen in the attached screen shot the borders around Firefox location and search entry boxes are black when unselected, but they should be grey. The black borders are inconsistent with the rest of the Ubuntu theming and it looks jarring. The issue is resolved by styling the 'frame' selector, which Firefox uses to style the Search and Location entry boxes. Some overrides are then applied to prevent frames incorrectly rendering borders in other applications. [Test Case] To observe the issue simply open Firefox and look at the Search or Location entry boxes while they are unselected, the borders will be black. After installing the patched theme doing to same will result in the borders being rendered using an appropriate shade of grey. [Regression Potential] It is possible that some GTK3+ applications may now render frames with a border where they previously did not. That said, the default applications in Ubuntu have been checked for this regression and the appropriate overrides have been added. The default installed applications in Ubuntu have been tested to ensure they do not regress in the manner described above. [Other Info] Should Firefox style the Search and Location entry boxes with a discrete selector in the future then the styling added to work around the black border could be removed/updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1624738/+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 1634494] Re: build.sh script fails to build needed dependencies
We do run that, things that may have happened: 1) Was not a clean build, i think we don't run it again for successive builds 2) You Cltrl+C'ed it when it asked for the root password, then since we don't run it for successive builds it was never run again. Can you try to actually reproduce this? -- 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/1634494 Title: build.sh script fails to build needed dependencies Status in unity8 package in Ubuntu: New Bug description: I branched Unity8 and tried to build it on top of my fresh Ubuntu 16.10 but build.sh script failed with following: https://paste.ubuntu.com/23343453/ I needed to run sudo mk-build-deps -ir debian/control manually to get the needed dependencies working and on the next run build script worked. By looking at the build.sh script looks like it should run something similar but for some reason it failed for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1634494/+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 1634494] [NEW] build.sh script fails to build needed dependencies
Public bug reported: I branched Unity8 and tried to build it on top of my fresh Ubuntu 16.10 but build.sh script failed with following: https://paste.ubuntu.com/23343453/ I needed to run sudo mk-build-deps -ir debian/control manually to get the needed dependencies working and on the next run build script worked. By looking at the build.sh script looks like it should run something similar but for some reason it failed for me. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1634494 Title: build.sh script fails to build needed dependencies Status in unity8 package in Ubuntu: New Bug description: I branched Unity8 and tried to build it on top of my fresh Ubuntu 16.10 but build.sh script failed with following: https://paste.ubuntu.com/23343453/ I needed to run sudo mk-build-deps -ir debian/control manually to get the needed dependencies working and on the next run build script worked. By looking at the build.sh script looks like it should run something similar but for some reason it failed for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1634494/+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 1580792] Re: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do)
Did a few tests, dialogs with a black/transparent backgrounds are definitely the worst (Terminal password prompt, shut down dialog, set a code or password in System Settings, connect to a hidden wifi network). The dialog can take up to 20s to fully open. Even then, they remain slow, for example when you type your password to unlock the Terminal (30s from the end of the splash screen to a workable terminal). Other dialogs also perform very poorly, for example the "new VPN connection" form, or the calendar-app's bottom edge (tested with the snap version) in which you can't really type anything. The alt-tab switcher is also very (very) laggy and completely unusable. The pointer only move every 1 or 2 seconds which makes it hard to aim correctly at anything. In all those examples, there is some kind of transparency layer involved. Could it be the cause? As noted in the title, performance is generally slow, so it might also be interesting to see what does work well. For example, tab switching in the browser (bottom-edge style) animates quite nicely once it's opened (though it's a bit slow to open). Moving around in the calendar-app is also quite smooth. I would have liked to test lists as well, but the address-book-app snap won't work and Dekko isn't in the repos (neither deb nor snap)… Let me know if there's any kind of test I can do or log I can provide. And let me know if I do have to file another bug! -- 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/1580792 Title: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do) Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: (problem forked from bug 1549455) Unity8 on Intel Pineview performs very poorly. Frame times appears to be up to 900ms, Qt's renderer thread using 100% CPU. Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA errors: http://paste.ubuntu.com/16344427/ Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like OpenGL features that Unity8 is hitting but mir-demos don't. So those gl calls are also good candidates for explaining poor performance, especially if Mesa is falling back to software rendering for them." Since Qt tends to perform just fine on that hardware in X11, something isn't right. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580792/+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 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1504254 Title: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction Status in systemd package in Ubuntu: Confirmed Bug description: I want my computer to suspend when there is NO opened user session. So, I have activated following lines inside '/etc/systemd/logind.conf' : IdleAction=suspend IdleActionSec=15min - Systematically , under Ubuntu Vivid (15.04), this works correctly : During user interaction, the computer does NOT automatically suspend, but stays continuously alive. Once all users have closed their session, the computer automatically suspends after 15 min. - But systematically , under Ubuntu Wily (15.10 beta2), the computer automatically suspends after 15 min EVEN during user interaction. Hitting the keyboard makes the computer resume without data loss, but this is still annoying. In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must systematically be inhibited during user interaction. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z_admin1665 F pulseaudio /dev/snd/controlC1: z_admin1665 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 8 19:26:59 2015 HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140 InstallationDate: Installed on 2015-09-27 (10 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-14-generic N/A linux-backports-modules-4.2.0-14-generic N/A linux-firmware1.149 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1504254/+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 1602628] Re: can't drag/move window if it's semi-maximized by Ctrl+Super+Left/Right
** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-zesty-2026 -- 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/1602628 Title: can't drag/move window if it's semi-maximized by Ctrl+Super+Left/Right Status in Canonical System Image: Fix Committed Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Fix Released Bug description: ubuntu 16.10 can't drag/move window if it's semi-maximized open random app, semi-miaximize left or rigt (CTRL SUPER + Left or Right), try to move the window by draggin' it from the title bar. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1602628/+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 1611859] Re: Keyboard layout isn't applied in dash after wizard
** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-zesty-2026 -- 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/1611859 Title: Keyboard layout isn't applied in dash after wizard Status in Canonical System Image: Fix Committed Status in unity8 package in Ubuntu: Fix Committed Bug description: In https://requests.ci-train.ubuntu.com/#/ticket/1771 Steps: * connect a BT or a physical keyboard * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot * go through the wizard Expected: * I can use the selected layout in the dash after completing the wizard Current: * layout is only applied on first app focus change ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8 8.14+16.04.20160810.2-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-landing-001] ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 10 19:04:24 2016 InstallationDate: Installed on 2016-05-06 (95 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 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/1611859/+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 1634416] Re: Firefox need access to org.freedesktop.resolve1 ResolvehostName
*** This bug is a duplicate of bug 1598759 *** https://bugs.launchpad.net/bugs/1598759 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1598759, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed ** This bug has been marked a duplicate of bug 1598759 AppArmor nameservice abstraction doesn't allow communication with systemd-resolved -- 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/1634416 Title: Firefox need access to org.freedesktop.resolve1 ResolvehostName Status in apparmor package in Ubuntu: Confirmed Bug description: In 16.10, FF 49.0, it seems that Firefox want to use the systemd resolved service via dbus: audit: type=1107 audit(1476778477.837:122): pid=3449 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/resolve1" interface="org.freedesktop.resolve1.Manager" member="ResolveHostname" mask="send" name="org.freedesktop.resolve1" pid=9652 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=3909 peer_label="unconfined" ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 10:55:46 2016 InstallationDate: Installed on 2015-10-04 (379 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED" operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server" interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive" pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443 peer_label="unconfined" Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus mediation is enabled Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634416/+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 1634418] Re: In 16.10, several apps want write access to /run/systemd/journal/socket
*** This bug is a duplicate of bug 1598759 *** https://bugs.launchpad.net/bugs/1598759 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1598759, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed ** This bug has been marked a duplicate of bug 1598759 AppArmor nameservice abstraction doesn't allow communication with systemd-resolved -- 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/1634418 Title: In 16.10, several apps want write access to /run/systemd/journal/socket Status in apparmor package in Ubuntu: Confirmed Bug description: Several app try to write into /run/systemd/journal/socket Maybe this should be an abstraction ? Firefox: audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/run/systemd/journal/socket" pid=25552 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 evince: audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince" name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 11:00:02 2016 InstallationDate: Installed on 2015-10-04 (379 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED" operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server" interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive" pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443 peer_label="unconfined" Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus mediation is enabled Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634418/+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 1634419] Re: In 16.10, several apps want write access to /run/systemd/journal/socket
*** This bug is a duplicate of bug 1598759 *** https://bugs.launchpad.net/bugs/1598759 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1598759, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed ** This bug has been marked a duplicate of bug 1598759 AppArmor nameservice abstraction doesn't allow communication with systemd-resolved -- 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/1634419 Title: In 16.10, several apps want write access to /run/systemd/journal/socket Status in apparmor package in Ubuntu: Confirmed Bug description: Several app try to write into /run/systemd/journal/socket Maybe this should be an abstraction ? Firefox: audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED" operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/run/systemd/journal/socket" pid=25552 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 evince: audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince" name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 11:00:02 2016 InstallationDate: Installed on 2015-10-04 (379 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED" operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server" interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive" pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443 peer_label="unconfined" Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus mediation is enabled Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634419/+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 1634463] Re: If the down arrow is pressed when using the address bar with no suggestions in private mode, the address bar is emptied
** Changed in: webbrowser-app (Ubuntu) Status: Confirmed => In Progress -- 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/1634463 Title: If the down arrow is pressed when using the address bar with no suggestions in private mode, the address bar is emptied Status in webbrowser-app package in Ubuntu: In Progress Bug description: What happened: 1) Open the browser and private mode 2) Start typing random letters so that there are no suggestions 3) Press the down arrow 4) Notice that what you have entered into the address bar is lost What I expected to happen: At step 3 for the address bar to remain the same and not lose any data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1634463/+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 1634463] Re: If the down arrow is pressed when using the address bar with no suggestions in private mode, the address bar is emptied
The problem only happens when on a "new tab" page. If you focus the address bar for a tab that already loaded a webpage, the issue doesn’t happen. I think what happens is that pressing down transfers focus to the new tab page, but it shouldn’t do, because the new tab page in incognito mode doesn’t have any content that the user may want to interact with with a keyboard. ** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed ** Changed in: webbrowser-app (Ubuntu) Importance: Undecided => Medium ** 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/1634463 Title: If the down arrow is pressed when using the address bar with no suggestions in private mode, the address bar is emptied Status in webbrowser-app package in Ubuntu: In Progress Bug description: What happened: 1) Open the browser and private mode 2) Start typing random letters so that there are no suggestions 3) Press the down arrow 4) Notice that what you have entered into the address bar is lost What I expected to happen: At step 3 for the address bar to remain the same and not lose any data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1634463/+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 1634463] Re: If the down arrow is pressed when using the address bar with no suggestions in private mode, the address bar is emptied
** Branch linked: lp:~osomon/webbrowser-app/1634463-focus-transfer -- 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/1634463 Title: If the down arrow is pressed when using the address bar with no suggestions in private mode, the address bar is emptied Status in webbrowser-app package in Ubuntu: In Progress Bug description: What happened: 1) Open the browser and private mode 2) Start typing random letters so that there are no suggestions 3) Press the down arrow 4) Notice that what you have entered into the address bar is lost What I expected to happen: At step 3 for the address bar to remain the same and not lose any data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1634463/+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 1634199] Re: In 16.10, LXD won't work with enforced dsnmasq profile
dnsmasq.leases added in trunk r3573 (before noticing comment #5 ;-) comment #5 means you'll need to add /var/lib/lxd/networks/*/dnsmasq.hosts r, After adding this (and reloading the profile), do you see more DENIED messages? -- 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/1634199 Title: In 16.10, LXD won't work with enforced dsnmasq profile Status in AppArmor: New Status in apparmor package in Ubuntu: New Bug description: After upgrading to 16.0, LXD networking stopped working due to enforced dnsmasq profile. audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED" operation="truncate" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540 comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1634199/+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 1634199] Re: In 16.10, LXD won't work with enforced dsnmasq profile
** Branch linked: lp:apparmor -- 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/1634199 Title: In 16.10, LXD won't work with enforced dsnmasq profile Status in AppArmor: New Status in apparmor package in Ubuntu: New Bug description: After upgrading to 16.0, LXD networking stopped working due to enforced dnsmasq profile. audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED" operation="truncate" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540 comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1634199/+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 1634463] [NEW] If the down arrow is pressed when using the address bar with no suggestions in private mode, the address bar is emptied
Public bug reported: What happened: 1) Open the browser and private mode 2) Start typing random letters so that there are no suggestions 3) Press the down arrow 4) Notice that what you have entered into the address bar is lost What I expected to happen: At step 3 for the address bar to remain the same and not lose any data ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- 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/1634463 Title: If the down arrow is pressed when using the address bar with no suggestions in private mode, the address bar is emptied Status in webbrowser-app package in Ubuntu: New Bug description: What happened: 1) Open the browser and private mode 2) Start typing random letters so that there are no suggestions 3) Press the down arrow 4) Notice that what you have entered into the address bar is lost What I expected to happen: At step 3 for the address bar to remain the same and not lose any data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1634463/+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 1634464] [NEW] cloudimg apt missing dirmngr
Public bug reported: apt-key adv --keyserver keyserver.ubuntu.com --recv 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 Warning: apt-key output should not be parsed (stdout is not a terminal) Executing: /tmp/tmp.Qv81Vl3Idi/gpg.1.sh --keyserver keyserver.ubuntu.com --recv 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory gpg: connecting dirmngr at '/tmp/tmp.Qv81Vl3Idi/S.dirmngr' failed: No such file or directory gpg: keyserver receive failed: No dirmngr ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1634464/+attachment/4763202/+files/Dependencies.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1634464/+attachment/4763203/+files/JournalErrors.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1634464/+attachment/4763204/+files/ProcEnviron.txt ** Description changed: apt-key adv --keyserver keyserver.ubuntu.com --recv 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 Warning: apt-key output should not be parsed (stdout is not a terminal) Executing: /tmp/tmp.Qv81Vl3Idi/gpg.1.sh --keyserver keyserver.ubuntu.com --recv 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory gpg: connecting dirmngr at '/tmp/tmp.Qv81Vl3Idi/S.dirmngr' failed: No such file or directory gpg: keyserver receive failed: No dirmngr - - ProblemType: Bug - DistroRelease: Ubuntu 16.10 - Package: apt 1.3.1 - ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 - Uname: Linux 4.8.0-22-generic x86_64 - ApportVersion: 2.20.3-0ubuntu8 - Architecture: amd64 - CurrentDesktop: GNOME - Date: Tue Oct 18 12:12:17 2016 - InstallationDate: Installed on 2016-01-05 (286 days ago) - InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) - SourcePackage: apt - UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1634464 Title: cloudimg apt missing dirmngr Status in apt package in Ubuntu: New Bug description: apt-key adv --keyserver keyserver.ubuntu.com --recv 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 Warning: apt-key output should not be parsed (stdout is not a terminal) Executing: /tmp/tmp.Qv81Vl3Idi/gpg.1.sh --keyserver keyserver.ubuntu.com --recv 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory gpg: connecting dirmngr at '/tmp/tmp.Qv81Vl3Idi/S.dirmngr' failed: No such file or directory gpg: keyserver receive failed: No dirmngr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1634464/+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 1573720] Re: Unencrypted private keys are insecure error reported even when key is encrypted
I work on Ubuntu 16.04 with all recent updates, but I still keep getting a series of this same messages: "Unencrypted private keys are insecure - The selected private key does not appear to be protected by a password." when I edit settings to the company's WiFi: Security:WPA Enterprise Authentication: TLS + password protected key When I "okey" through all the messages and try to connect to the WiFi - I wait some time and then get the messages all over again. -- 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/1573720 Title: Unencrypted private keys are insecure error reported even when key is encrypted Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Triaged Bug description: When I enter an EAP-TLS wifi config, I get the error: "Unencrypted private keys are insecure The selected private key does not appear to be protected by a password. This could allow your security credentials to be compromised. Please select a password-protected private key. (You can password-protect your private key with openssl)" I have verified that my key is, in fact, encrypted, and I have tried using both des3 and aes256. I have also verified the password used to encrypt the key. For a while, it wouldn't even let me save the config. I managed to save it eventually, but now when I try to connect to the saved connection, I get the same error. I am on Ubuntu mate 16.04 network-manager 1.1.93 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Apr 22 13:25:16 2016 InstallationDate: Installed on 2015-08-19 (246 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) IpRoute: default via 192.168.151.254 dev eth1 proto static metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.151.0/24 dev eth1 proto kernel scope link src 192.168.151.95 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 ed50d4f9-c810-4be0-b06c-8acd58015c50 /org/freedesktop/NetworkManager/ActiveConnection/0 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/1 -- ---- eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1573720/+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 1634457] [NEW] Failed to send sms to multiple users if with MMS group chat enabled
Public bug reported: $ system-image-cli -i current build number: 203 device name: turbo channel: ubuntu-touch/rc-proposed/meizu-pd.en last update: 2016-10-18 17:23:14 version version: 203 version ubuntu: 20161018 version device: 20160824-d33b825 version custom: 20160831-992-8-12 Steps to reproduce: 1. Launch Messaging app 2. Enable MMS group chat from settings 3. Try to send a sms message to multiple users Failed to send sms to multiple users if with MMS group chat enabled, it's ok if disabled MMS group chat. ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20161018_184608292.png" https://bugs.launchpad.net/bugs/1634457/+attachment/4763175/+files/screenshot20161018_184608292.png -- 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/1634457 Title: Failed to send sms to multiple users if with MMS group chat enabled Status in messaging-app package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 203 device name: turbo channel: ubuntu-touch/rc-proposed/meizu-pd.en last update: 2016-10-18 17:23:14 version version: 203 version ubuntu: 20161018 version device: 20160824-d33b825 version custom: 20160831-992-8-12 Steps to reproduce: 1. Launch Messaging app 2. Enable MMS group chat from settings 3. Try to send a sms message to multiple users Failed to send sms to multiple users if with MMS group chat enabled, it's ok if disabled MMS group chat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1634457/+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 1634457] Re: Failed to send sms to multiple users if with MMS group chat enabled
** Attachment added: "application-legacy-messaging-app-.log" https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1634457/+attachment/4763176/+files/application-legacy-messaging-app-.log -- 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/1634457 Title: Failed to send sms to multiple users if with MMS group chat enabled Status in messaging-app package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 203 device name: turbo channel: ubuntu-touch/rc-proposed/meizu-pd.en last update: 2016-10-18 17:23:14 version version: 203 version ubuntu: 20161018 version device: 20160824-d33b825 version custom: 20160831-992-8-12 Steps to reproduce: 1. Launch Messaging app 2. Enable MMS group chat from settings 3. Try to send a sms message to multiple users Failed to send sms to multiple users if with MMS group chat enabled, it's ok if disabled MMS group chat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1634457/+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 1034928] Re: Fontconfig warning: Having multiple values in isn't supported and may not works as expected
This bug is easy to fix. For example, it will be caused by a section like this: zh-cn zh-sg The correct syntax would be zh-cn zh-sg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-arphic-ukai in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in isn't supported and may not works as expected Status in culmus package in Ubuntu: Fix Released Status in fonts-arphic-ukai package in Ubuntu: Fix Released Status in fonts-arphic-uming package in Ubuntu: Fix Released Status in fonts-baekmuk package in Ubuntu: Fix Released Status in fonts-droid package in Ubuntu: Fix Released Status in fonts-nanum package in Ubuntu: Fix Released Status in fonts-nanum-coding package in Ubuntu: Fix Released Status in fonts-sil-andika package in Ubuntu: Fix Released Status in fonts-tlwg package in Ubuntu: Fix Released Status in fonts-unfonts-core package in Ubuntu: Fix Released Status in fonts-unfonts-extra package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in ttf-wqy-zenhei package in Ubuntu: Fix Released Status in culmus source package in Quantal: Fix Released Status in fonts-arphic-ukai source package in Quantal: Fix Released Status in fonts-arphic-uming source package in Quantal: Fix Released Status in fonts-baekmuk source package in Quantal: Fix Released Status in fonts-droid source package in Quantal: Fix Released Status in fonts-nanum source package in Quantal: Fix Released Status in fonts-nanum-coding source package in Quantal: Fix Released Status in fonts-sil-andika source package in Quantal: Fix Released Status in fonts-tlwg source package in Quantal: Fix Released Status in fonts-unfonts-core source package in Quantal: Fix Released Status in fonts-unfonts-extra source package in Quantal: Fix Released Status in language-selector source package in Quantal: Fix Released Status in ttf-wqy-zenhei source package in Quantal: Fix Released Status in fonts-arphic-ukai package in Debian: Fix Released Status in fonts-arphic-uming package in Debian: Fix Released Status in fonts-baekmuk package in Debian: Fix Released Status in fonts-droid package in Debian: Fix Released Status in fonts-nanum package in Debian: Fix Released Status in fonts-sil-andika package in Debian: Fix Released Status in fonts-unfonts-core package in Debian: Fix Released Status in fonts-unfonts-extra package in Debian: Fix Released Status in ttf-wqy-zenhei package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: "/etc/fonts/conf.d/90-fonts-unfonts-core.conf", line 11: Having multiple values in isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf [Test Case] 1) Install the fonts in question 2) Open a terminal 3) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal [Regression Potential] In case of a regression, the font in question can be affected. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/culmus/+bug/1034928/+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 1616079] Re: [Latitude E7270, Realtek ALC3235, Speaker, Internal] Pulseaudio fails to detect card, no sound in speaker nor in line out
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/1616079 Title: [Latitude E7270, Realtek ALC3235, Speaker, Internal] Pulseaudio fails to detect card, no sound in speaker nor in line out Status in pulseaudio package in Ubuntu: Confirmed Bug description: No sound in speakers or in headphones after upgrade to ubuntu 16.04. No devices shown in Sound settings -> Play sound through Previously in ubuntu 14.04 sound works good. sglukhov@Galvatron:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3235 Analog [ALC3235 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Aug 23 16:24:58 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-01-25 (210 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Latitude E7270, Realtek ALC3235, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to xenial on 2016-07-05 (49 days ago) dmi.bios.date: 11/09/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 00DTF3 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd11/09/2015:svnDellInc.:pnLatitudeE7270:pvr:rvnDellInc.:rn00DTF3:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7270 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1616079/+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 1580792] Re: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do)
well, if it is a dialog-specific problem it could be worth having a separate bug, that only tackles dialog. otherwise you end up fixing too many things as part of the same bug -- 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/1580792 Title: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do) Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: (problem forked from bug 1549455) Unity8 on Intel Pineview performs very poorly. Frame times appears to be up to 900ms, Qt's renderer thread using 100% CPU. Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA errors: http://paste.ubuntu.com/16344427/ Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like OpenGL features that Unity8 is hitting but mir-demos don't. So those gl calls are also good candidates for explaining poor performance, especially if Mesa is falling back to software rendering for them." Since Qt tends to perform just fine on that hardware in X11, something isn't right. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580792/+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 1633274] Re: Systemd-networkd crashes with core dump
Nice! Thanks for all help. When can i expect the SRU to be released? -- 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/1633274 Title: Systemd-networkd crashes with core dump Status in systemd: Unknown Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Yakkety: In Progress Status in systemd source package in Zesty: Fix Committed Bug description: Systemd-networkd crashes with core dump, this happends in Yakkety and Xenial. The latest patch that was commited to Xenial-updates and Yakkety is the one that broke this. Everything works just fine with Xenial without latest update or Yakkety Beta 2. The log entries i see is: Oct 14 02:37:42 Router01 systemd-networkd[3402]: Assertion 't' failed at ../src/network/networkd-netdev-tunnel.c:210, function netdev_vti_fill_message_key(). Aborting. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Main process exited, code=dumped, status=6/ABRT Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered failed state. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. Oct 14 02:37:42 Router01 systemd[1]: Stopped Network Service. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Start request repeated too quickly. Oct 14 02:37:42 Router01 systemd[1]: Failed to start Network Service. Oct 14 02:37:42 Router01 systemd[1]: Dependency failed for Wait for Network to be Configured. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd-wait-online.service: Job systemd-networkd-wait-online.service/start failed with result 'dependency'. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered failed state. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with result 'start-limit-hit'. SRU TEST CASE: See https://github.com/systemd/systemd/issues/4371#issuecomment-253697041 Regression potential: Very low, this just fixes an obvious type cast in networkd and touches no code that applies to other network interfaces. The service manager (pid 1) and other tools are entirely unaffected. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Oct 14 02:39:05 2016 InstallationDate: Installed on 2016-10-13 (0 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Dell Inc. OptiPlex 755 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd06/11/2012:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1633274/+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 1634208] Re: VPN cannot resolve DNS entries on second connect
** Description changed: - The first time I connect to a VPN (vpnc) everything works fine, but if I - disconnect and then reconnect I can no longer resolve DNS entries - although I can connect directly via IP address. The only solution seems - to be a reboot. + Ubuntu 16.10 + The first time I connect to a VPN (vpnc) everything works fine, but if I disconnect and then reconnect I can no longer resolve DNS entries although I can connect directly via IP address. The only solution seems to be a reboot. This was working fine in 16.04. -- 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/1634208 Title: VPN cannot resolve DNS entries on second connect Status in network-manager package in Ubuntu: New Bug description: Ubuntu 16.10 The first time I connect to a VPN (vpnc) everything works fine, but if I disconnect and then reconnect I can no longer resolve DNS entries although I can connect directly via IP address. The only solution seems to be a reboot. This was working fine in 16.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1634208/+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 1580792] Re: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do)
Please keep the discussion in this bug and don't log a new one. Just add an ubuntu-ui-toolkit task here. -- 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/1580792 Title: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do) Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: (problem forked from bug 1549455) Unity8 on Intel Pineview performs very poorly. Frame times appears to be up to 900ms, Qt's renderer thread using 100% CPU. Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA errors: http://paste.ubuntu.com/16344427/ Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like OpenGL features that Unity8 is hitting but mir-demos don't. So those gl calls are also good candidates for explaining poor performance, especially if Mesa is falling back to software rendering for them." Since Qt tends to perform just fine on that hardware in X11, something isn't right. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580792/+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 1580792] Re: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do)
@Guillame: that is interesting, it might be useful to see if that happens for all dialogs like that (there should be a few in system settings app). If it does, it's probably worth reporting a bug against ubuntu-ui-toolkit to investigate that -- 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/1580792 Title: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do) Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: (problem forked from bug 1549455) Unity8 on Intel Pineview performs very poorly. Frame times appears to be up to 900ms, Qt's renderer thread using 100% CPU. Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA errors: http://paste.ubuntu.com/16344427/ Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like OpenGL features that Unity8 is hitting but mir-demos don't. So those gl calls are also good candidates for explaining poor performance, especially if Mesa is falling back to software rendering for them." Since Qt tends to perform just fine on that hardware in X11, something isn't right. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580792/+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 1634436] [NEW] When focus is given to a suggestion, typing should move the focus back to the address bar
Public bug reported: What Happened: 1) Open the webbrowser-app 2) Start typing in the address bar to reveal suggestions, eg type "BBC" 3) Move the cursor/focus to the first suggested item (by pressing down arrow) 4) Start attempting to type, to edit the address bar (eg to add "News" or "Sport") 5) Notice that typing does not work as the field is not focused What I expected to happen: At step 4 if you have a suggestion focused and you start to type it should focus the address bar. Note that other browsers, eg Firefox and Chrome, both do the expected case. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- 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/1634436 Title: When focus is given to a suggestion, typing should move the focus back to the address bar Status in webbrowser-app package in Ubuntu: New Bug description: What Happened: 1) Open the webbrowser-app 2) Start typing in the address bar to reveal suggestions, eg type "BBC" 3) Move the cursor/focus to the first suggested item (by pressing down arrow) 4) Start attempting to type, to edit the address bar (eg to add "News" or "Sport") 5) Notice that typing does not work as the field is not focused What I expected to happen: At step 4 if you have a suggestion focused and you start to type it should focus the address bar. Note that other browsers, eg Firefox and Chrome, both do the expected case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1634436/+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 1633274] Re: Systemd-networkd crashes with core dump
Yes to both; I already did that, it'll be part of the next SRUs. -- 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/1633274 Title: Systemd-networkd crashes with core dump Status in systemd: Unknown Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Yakkety: In Progress Status in systemd source package in Zesty: Fix Committed Bug description: Systemd-networkd crashes with core dump, this happends in Yakkety and Xenial. The latest patch that was commited to Xenial-updates and Yakkety is the one that broke this. Everything works just fine with Xenial without latest update or Yakkety Beta 2. The log entries i see is: Oct 14 02:37:42 Router01 systemd-networkd[3402]: Assertion 't' failed at ../src/network/networkd-netdev-tunnel.c:210, function netdev_vti_fill_message_key(). Aborting. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Main process exited, code=dumped, status=6/ABRT Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered failed state. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. Oct 14 02:37:42 Router01 systemd[1]: Stopped Network Service. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Start request repeated too quickly. Oct 14 02:37:42 Router01 systemd[1]: Failed to start Network Service. Oct 14 02:37:42 Router01 systemd[1]: Dependency failed for Wait for Network to be Configured. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd-wait-online.service: Job systemd-networkd-wait-online.service/start failed with result 'dependency'. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered failed state. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with result 'start-limit-hit'. SRU TEST CASE: See https://github.com/systemd/systemd/issues/4371#issuecomment-253697041 Regression potential: Very low, this just fixes an obvious type cast in networkd and touches no code that applies to other network interfaces. The service manager (pid 1) and other tools are entirely unaffected. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Oct 14 02:39:05 2016 InstallationDate: Installed on 2016-10-13 (0 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Dell Inc. OptiPlex 755 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd06/11/2012:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1633274/+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
@pat: have added this to the backlog of things to investigate. Will see if it's possible to reliably reproduce this issue and identify the root cause. -- 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