[Touch-packages] [Bug 1861177] Re: seccomp_rule_add is very slow
I'm leaving the snapd bug task as New so mvo or ian can take a look when it's their triage day, at the latest; I have nothing useful to do here other than "ouch". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1861177 Title: seccomp_rule_add is very slow Status in snapd: Triaged Status in libseccomp package in Ubuntu: Triaged Bug description: There is a known and patched issue with version 2.4 of libseccomp where certain operations have a large performance regression. This is causing some packages that use libseccomp such as container orchestration systems to occasionally time out or otherwise fail under certain workloads. Please consider porting the patch into the various Ubuntu versions that have version 2.4 of libseccomp and into the backports. The performance patch from version 2.5 (yet to be released) applies cleanly on top of the 2.4 branch of libseccomp. For more information, and for a copy of the patch (which can also be cherry picked from the upstream libseccomp repos) see the similar Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1861177/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860540] [NEW] network password entry has no way of displaying what you type
Public bug reported: In Focal the network password / passphrase entry form has no way of displaying what is being typed. I'd expect a checkbox or something... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.442 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CasperVersion: 1.438 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 11:13:41 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal ** Attachment added: "Screenshot from 2020-01-22 11-11-36.png" https://bugs.launchpad.net/bugs/1860540/+attachment/5322131/+files/Screenshot%20from%202020-01-22%2011-11-36.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1860540 Title: network password entry has no way of displaying what you type Status in ubuntu-meta package in Ubuntu: New Bug description: In Focal the network password / passphrase entry form has no way of displaying what is being typed. I'd expect a checkbox or something... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.442 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CasperVersion: 1.438 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 11:13:41 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried
FWIW snapd mounts and unmounts a squashfs on startup to determine whether the system can mount squashfs's. It does this using mount, and cleans up with umount -l. That is, it's not via systemd in this instance in particular. I'm setting it as invalid for snapd, but if this behaviour is somehow tickling a bug and there's a workaround that could avoid it, let us know and we'd be happy to accommodate (set the bug task back to New so our triage picks it up). ** Changed in: snapd (Ubuntu) Status: New => Invalid -- 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/1856871 Title: i/o error if next unused loop device is queried Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: This is reproducible in Bionic and late. Here's an example running 'focal': $ lsb_release -cs focal $ uname -r 5.3.0-24-generic The error is: blk_update_request: I/O error, dev loop2, sector 0 and on more recent kernel: kernel: [18135.185709] blk_update_request: I/O error, dev loop18, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 How to trigger it: $ sosreport -o block or more precisely the cmd causing the situation inside the block plugin: $ parted -s $(losetup -f) unit s print https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52 but if I run it on the next next unused loop device, in this case /dev/loop3 (which is also unused), no errors. While I agree that sosreport shouldn't query unused loop devices, there is definitely something going on with the next unused loop device. What is differentiate loop2 and loop3 and any other unused ones ? 3 things so far I have noticed: * loop2 is the next unused loop device (losetup -f) * A reboot is needed (if some loop modification (snap install, mount loop, ...) has been made at runtime * I have also noticed that loop2 (or whatever the next unused one is) have some stat as oppose to other unused loop devices. The stat exist already right after the system boot for the next unused loop device. /sys/block/loop2/stat :: 2 0 10 0 1 0 0 0 0 0 0 2 = number of read I/Os processed 10 = number of sectors read 1 = number of write I/Os processed Explanation of each column: https://www.kernel.org/doc/html/latest/block/stat.html while /dev/loop3 doesn't /sys/block/loop3/stat :: 0 0 0 0 0 0 0 0 0 0 0 Which tells me that something during the boot process most likely acquired (on purpose or not) the next unused loop and possibly didn't released it well enough. If loop2 is generating errors, and I install a snap, the snap squashfs will take loop2, making loop3 the next unused loop device. If I query loop3 with 'parted' right after, no errors. If I reboot, and query loop3 again, then no I'll have an error. To triggers the errors it need to be after a reboot and it only impact the first unused loop device available (losetup -f). This was tested with focal/systemd whic his very close to latest upstream code. This has been test with latest v5.5 mainline kernel as well. For now, I don't think it's a kernel problem, I'm more thinking of a userspace misbehaviour dealing with loop device (or block device) at boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1856871/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767896] Re: Live images with broken seed causes snapd high CPU usage and periodic short GUI freezes
Moving it back to Won't fix, for snapd at least. I don't see an issue here that snapd itself _can_ fix. ** Changed in: snapd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1767896 Title: Live images with broken seed causes snapd high CPU usage and periodic short GUI freezes Status in OEM Priority Project: Fix Released Status in snapd package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: ThinkPad 25, UEFI mode, Ubuntu 18.04 installed as a _live_ distro in FAT32 partition on SATA SSD in WWAN slot. Grub options allow booting without persistence or with a 256MB persistence file. Only thing "persisted" is TERM in favorites. Without persistence all is well. With persistence snapd uses up to 90% CPU - perhaps more - and cripples the system. Fan runs nearly full speed constantly. I can eliminate the problem by removing snapd - and that persists. Can't kill snapd. PID is constantly changing. 0% fan and low CPU use at idle w/out snapd with persistence, or booted w/out persistence. WORKAROUND: sudo systemctl stop snapd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703194] Re: package snapd 2.25~14.04 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
I suspect you've been able to resolve this, sorry we never got back to you about it. I'm closing it as "Won't fix", because we didn't do anything about this, but if you're still stuck there's probably a cause for this that isn't necessarily snapd itself and we can probably figure it out. Again, sorry. ** Changed in: snapd (Ubuntu) Status: New => Won't Fix -- 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/1703194 Title: package snapd 2.25~14.04 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in apport package in Ubuntu: New Status in snapd package in Ubuntu: Won't Fix Bug description: Пытался откатиться с 16.04 до 14 путём выполнения команды sudo gedit /etc/apt/sources.list. не вышло. как быть? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: snapd 2.25~14.04 ProcVersionSignature: Ubuntu 4.4.0-83.106~14.04.1-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Jul 9 16:18:43 2017 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2017-07-09 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: snapd Title: package snapd 2.25~14.04 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1703194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824342] [NEW] in 19.04, default user cannot access system journal
Public bug reported: in a fresh install of 19.04 from http://cdimage.ubuntu.com/daily- live/20190410/disco-desktop-amd64.iso, journalctl -u snapd, or -u gdm, or -u udisks, results in 'no entries'. journalctl --system -u snapd etc, warns about permissions. $ sudo getfacl /var/log/journal/ getfacl: Removing leading '/' from absolute path names # file: var/log/journal/ # owner: root # group: systemd-journal # flags: -s- user::rwx group::r-x other::r-x default:user::rwx default:group::r-x default:group:adm:r-x default:mask::r-x default:other::r-x this is fixed via sudo setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal ** Affects: systemd (Ubuntu) Importance: High Status: New ** Tags: rls-dd-incoming -- 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/1824342 Title: in 19.04, default user cannot access system journal Status in systemd package in Ubuntu: New Bug description: in a fresh install of 19.04 from http://cdimage.ubuntu.com/daily- live/20190410/disco-desktop-amd64.iso, journalctl -u snapd, or -u gdm, or -u udisks, results in 'no entries'. journalctl --system -u snapd etc, warns about permissions. $ sudo getfacl /var/log/journal/ getfacl: Removing leading '/' from absolute path names # file: var/log/journal/ # owner: root # group: systemd-journal # flags: -s- user::rwx group::r-x other::r-x default:user::rwx default:group::r-x default:group:adm:r-x default:mask::r-x default:other::r-x this is fixed via sudo setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565617] Re: "polkitd.service is masked" warnings on package install while policykit-1 is unpacked but not yet configured
Augh, sorry, wrong bug. -- 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/1565617 Title: "polkitd.service is masked" warnings on package install while policykit-1 is unpacked but not yet configured Status in systemd package in Ubuntu: Fix Released Bug description: Problem Description : = Error messages are seen while installing apport package. System details = uname -a : 4.4.0-15-generic Machine : Power 8 apport : Installed: 2.20-0ubuntu3 Candidate: 2.20-0ubuntu3 Steps to reproduce From a small xenial installation, like a cloud image: 1. apt-get purge -y policykit-1 apport 2. apt-get install apport Error === root@powerkvm5:~# apt-get install apport Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apport-symptoms policykit-1 python3-apport python3-problem-report python3-systemd Suggested packages: apport-gtk | apport-kde python3-launchpadlib The following NEW packages will be installed: apport apport-symptoms policykit-1 python3-apport python3-problem-report python3-systemd 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/304 kB of archives. After this operation, 2,444 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Selecting previously unselected package python3-problem-report. (Reading database ... 134848 files and directories currently installed.) Preparing to unpack .../python3-problem-report_2.20-0ubuntu3_all.deb ... Unpacking python3-problem-report (2.20-0ubuntu3) ... Selecting previously unselected package python3-apport. Preparing to unpack .../python3-apport_2.20-0ubuntu3_all.deb ... Unpacking python3-apport (2.20-0ubuntu3) ... Selecting previously unselected package apport. Preparing to unpack .../apport_2.20-0ubuntu3_all.deb ... Unpacking apport (2.20-0ubuntu3) ... Selecting previously unselected package apport-symptoms. Preparing to unpack .../apport-symptoms_0.20_all.deb ... Unpacking apport-symptoms (0.20) ... Selecting previously unselected package policykit-1. Preparing to unpack .../policykit-1_0.105-14.1_ppc64el.deb ... Created symlink from /run/systemd/system/polkitd.service to /dev/null. Unpacking policykit-1 (0.105-14.1) ... Selecting previously unselected package python3-systemd. Preparing to unpack .../python3-systemd_231-2build1_ppc64el.deb ... Unpacking python3-systemd (231-2build1) ... Processing triggers for systemd (229-3ubuntu1) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for shared-mime-info (1.5-2) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for dbus (1.10.6-1ubuntu2) ... Setting up python3-problem-report (2.20-0ubuntu3) ... Setting up python3-apport (2.20-0ubuntu3) ... Setting up apport (2.20-0ubuntu3) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Setting up apport-symptoms (0.20) ... Setting up policykit-1 (0.105-14.1) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1:
[Touch-packages] [Bug 1565617] Re: "polkitd.service is masked" warnings on package install while policykit-1 is unpacked but not yet configured
This is the diff between the deb-systemd-invoke from init-system- helpers-1.51, and the one in my previous comment. ** Attachment added: "patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1565617/+attachment/5186097/+files/patch -- 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/1565617 Title: "polkitd.service is masked" warnings on package install while policykit-1 is unpacked but not yet configured Status in systemd package in Ubuntu: Fix Released Bug description: Problem Description : = Error messages are seen while installing apport package. System details = uname -a : 4.4.0-15-generic Machine : Power 8 apport : Installed: 2.20-0ubuntu3 Candidate: 2.20-0ubuntu3 Steps to reproduce From a small xenial installation, like a cloud image: 1. apt-get purge -y policykit-1 apport 2. apt-get install apport Error === root@powerkvm5:~# apt-get install apport Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apport-symptoms policykit-1 python3-apport python3-problem-report python3-systemd Suggested packages: apport-gtk | apport-kde python3-launchpadlib The following NEW packages will be installed: apport apport-symptoms policykit-1 python3-apport python3-problem-report python3-systemd 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/304 kB of archives. After this operation, 2,444 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Selecting previously unselected package python3-problem-report. (Reading database ... 134848 files and directories currently installed.) Preparing to unpack .../python3-problem-report_2.20-0ubuntu3_all.deb ... Unpacking python3-problem-report (2.20-0ubuntu3) ... Selecting previously unselected package python3-apport. Preparing to unpack .../python3-apport_2.20-0ubuntu3_all.deb ... Unpacking python3-apport (2.20-0ubuntu3) ... Selecting previously unselected package apport. Preparing to unpack .../apport_2.20-0ubuntu3_all.deb ... Unpacking apport (2.20-0ubuntu3) ... Selecting previously unselected package apport-symptoms. Preparing to unpack .../apport-symptoms_0.20_all.deb ... Unpacking apport-symptoms (0.20) ... Selecting previously unselected package policykit-1. Preparing to unpack .../policykit-1_0.105-14.1_ppc64el.deb ... Created symlink from /run/systemd/system/polkitd.service to /dev/null. Unpacking policykit-1 (0.105-14.1) ... Selecting previously unselected package python3-systemd. Preparing to unpack .../python3-systemd_231-2build1_ppc64el.deb ... Unpacking python3-systemd (231-2build1) ... Processing triggers for systemd (229-3ubuntu1) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for shared-mime-info (1.5-2) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for dbus (1.10.6-1ubuntu2) ... Setting up python3-problem-report (2.20-0ubuntu3) ... Setting up python3-apport (2.20-0ubuntu3) ... Setting up apport (2.20-0ubuntu3) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36)
[Touch-packages] [Bug 1645815] [NEW] apt install of local debs does not tab-complete
Public bug reported: this fails: $ touch xyzzy.deb $ apt install xyzzy because the completion support for install is using _filedir wrong. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.15 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 29 17:51:57 2016 InstallationDate: Installed on 2016-07-05 (147 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Assignee: John Lenton (chipaca) Status: Incomplete ** Tags: amd64 apport-bug xenial -- 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/1645815 Title: apt install of local debs does not tab-complete Status in apt package in Ubuntu: Incomplete Bug description: this fails: $ touch xyzzy.deb $ apt install xyzzy because the completion support for install is using _filedir wrong. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.15 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 29 17:51:57 2016 InstallationDate: Installed on 2016-07-05 (147 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1645815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1559038] Re: timespec parsing is wrong
I can confirm systemd built with the attached patch makes things sane again -- 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/1559038 Title: timespec parsing is wrong Status in systemd package in Ubuntu: Confirmed Bug description: We are affected by upstream bug: https://github.com/systemd/systemd/issues/2682 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1559038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520765] [NEW] package libmircookie1 (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Public bug reported: nothing to add ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libmircookie1 (not installed) ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Nov 27 21:50:03 2015 DuplicateSignature: package:libmircookie1:(not installed):subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-04-27 (579 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: mir SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: package libmircookie1 (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-11-27 (0 days ago) ** Affects: mir (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1520765 Title: package libmircookie1 (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in mir package in Ubuntu: New Bug description: nothing to add ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libmircookie1 (not installed) ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Nov 27 21:50:03 2015 DuplicateSignature: package:libmircookie1:(not installed):subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-04-27 (579 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: mir SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: package libmircookie1 (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-11-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1520765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1413818] Re: Notification sounds aren't being played back on E4.5
I'm sure it's "software, not hardware", but I don't think "system-image-cli" will help; note how Pat was able to get his device "unstuck", above. I'm on this bug because of my involvement with the "postal service" (local notification delivery) early on; I don't have the issue. On 11 September 2015 at 14:30, John McAleelywrote: > @chipaca, assuming yours is one, and it still does it, can you provide > the output from system-image-cli -i please? > > This will be software, not hardware :-) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1413818 > > Title: > Notification sounds aren't being played back on E4.5 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/canonical-devices-system-image/+bug/1413818/+subscriptions -- 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/1413818 Title: Notification sounds aren't being played back on E4.5 Status in Canonical System Image: Confirmed Status in pulseaudio package in Ubuntu: Incomplete Bug description: This affects mostly the push notifications based alerts, SMS et.al. work fine. With export PULSE_PROP='media.role=alert' This has no audible output: paplay /usr/share/sounds/ubuntu/notifications/Slick.ogg This does: paplay /usr/share/sounds/ubuntu/ringtones/Soul.ogg $ system-image-cli -i current build number: 14 device name: mako channel: ubuntu-touch/stable alias: ubuntu-touch/ubuntu-rtm/14.09 last update: 2015-01-16 13:12:29 version version: 14 version ubuntu: 20150116 version device: 20141119 version custom: mako-1.1 The hunch is some buffering going on on the android side for short sound bytes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1413818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413818] Re: Notification sounds aren't being played back on E4.5
You need to get a krillin that doesn't, then, and figure out why it doesn't =) -- 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/1413818 Title: Notification sounds aren't being played back on E4.5 Status in Canonical System Image: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: This affects mostly the push notifications based alerts, SMS et.al. work fine. With export PULSE_PROP='media.role=alert' This has no audible output: paplay /usr/share/sounds/ubuntu/notifications/Slick.ogg This does: paplay /usr/share/sounds/ubuntu/ringtones/Soul.ogg $ system-image-cli -i current build number: 14 device name: mako channel: ubuntu-touch/stable alias: ubuntu-touch/ubuntu-rtm/14.09 last update: 2015-01-16 13:12:29 version version: 14 version ubuntu: 20150116 version device: 20141119 version custom: mako-1.1 The hunch is some buffering going on on the android side for short sound bytes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1413818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1466682] Re: Docker unix socket permission issue on ubuntu-core update
** No longer affects: docker (Ubuntu) ** No longer affects: apparmor (Ubuntu) -- 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/1466682 Title: Docker unix socket permission issue on ubuntu-core update Status in Snappy Ubuntu: New Bug description: I have been running the docker framework (2015-06-15 1.6.1.002) on a Snappy Ubuntu Core (ubuntu-core/15.04/stable) instance on aws EC2. On June 11th the instance automatically upgraded from ubuntu-core version 2 to ubuntu-core version 3 and rebooted. The running Docker containers restarted without any issues, however when I next logged in to run a docker command I got the following error: FATA[] Get http:///var/run/docker.sock/v1.18/containers/json: dial unix /var/run/docker.sock: permission denied. Are you trying to connect to a TLS-enabled daemon without TLS? I rebooted to see if it would help, but the error was still there. I checked the dmesg log and found the following entry was added when I tried to run a docker command: [ 72.230872] audit: type=1400 audit(1434397079.776:12): apparmor=DENIED operation=connect info=Failed name lookup - disconnected path error=-13 profile=docker_docker_1.6.1.002 name=run/docker.sock pid=1025 comm=docker.x86_64 requested_mask=wr denied_mask=wr fsuid=1000 ouid=0 I tried using the docker command both as a nonprivileged user and using sudo. In both cases I was unable to run the docker command. I was able to resolve the issue by uninstalling and reinstalling the docker framework using the commands: sudo snappy remove docker sudo snappy install docker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1466682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434521] Re: account-polld does not recognize when messages are cleared
There aren't any error messages in what you pasted; could you paste the log from a non-manually-initiated run that exhibits this please? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1434521 Title: account-polld does not recognize when messages are cleared Status in account-polld package in Ubuntu: Invalid Status in indicator-messages package in Ubuntu: New Bug description: After each reboot, account-polld stops showing incoming emails after displaying 3 notifications. The reason for that is that account-polld does not recognize when messages are cleared from the messaging indicator and therefore does not show any further notifications. How to reproduce: 1) Reboot your phone. 2) Send yourself 3 test emails 3) Wait 5 minutes until account-polld has been run 4) You'll see three notifications stating that there are new emails 5) Tap on the clear all entry in the notifications indicator 6) Mark your last three emails as read (this is optional) 7) Send yourself another test email 8) Wait 5 minutes again until account-polld has been run 9) No notification about the new unread email is shown Why does it happen: When clicking the clear all button, the internal cache of previous messages isn't cleared. Therefore, account-polld still thinks that there are 3 notifications and does not display any further messages. Log: http://paste.ubuntu.com/10634045/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1434521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385331] [NEW] Notification LED stays on when no messages in notification center
Public bug reported: Observed the notification LED staying on even though there were no notifications in the indicators and the notification icon was greyed out. ** 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/1385331 Title: Notification LED stays on when no messages in notification center Status in “unity8” package in Ubuntu: New Bug description: Observed the notification LED staying on even though there were no notifications in the indicators and the notification icon was greyed out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1385331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371081] [NEW] if “when locked, allow [...] notifications” is disabled, notifications should not be shown
Public bug reported: Under system settings - Privacy Security - Phone locking there's a “When locked, allow: notifications and quick settings” checkbox. When it is unchecked, if the lockscreen is up, notifications should be suppressed. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: Confirmed ** Summary changed: - if when locked, allow [...] notifications is disabled, notifications should not be shown + if “when locked, allow [...] notifications” is disabled, notifications should not be shown -- 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/1371081 Title: if “when locked, allow [...] notifications” is disabled, notifications should not be shown Status in “unity8” package in Ubuntu: Confirmed Bug description: Under system settings - Privacy Security - Phone locking there's a “When locked, allow: notifications and quick settings” checkbox. When it is unchecked, if the lockscreen is up, notifications should be suppressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1371081/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371081] Re: if “when locked, allow [...] notifications” is disabled, notifications should not be shown
Without that toggle it means that you could leak private things (content of SMSes, snippets and senders of email) even though the lockscreen is up, which some people want to avoid. We (in push notifications/poll daemon) were asked to implement this; Ted Gould suggested that unity notifications was where to do this, quite reasonably: if leaking an email sender or snipped was a privacy issue, so is an sms sender/snippet. Given that context, (4) seems to be what we want. Or we want (2), and another checkbox on that list explicitly for bubbles and such. -- 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/1371081 Title: if “when locked, allow [...] notifications” is disabled, notifications should not be shown Status in “unity8” package in Ubuntu: New Bug description: Under system settings - Privacy Security - Phone locking there's a “When locked, allow: notifications and quick settings” checkbox. When it is unchecked, if the lockscreen is up, notifications should be suppressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1371081/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371081] Re: if “when locked, allow [...] notifications” is disabled, notifications should not be shown
What should happen to a blocked snap decision? -- 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/1371081 Title: if “when locked, allow [...] notifications” is disabled, notifications should not be shown Status in “unity8” package in Ubuntu: In Progress Bug description: Under system settings - Privacy Security - Phone locking there's a “When locked, allow: notifications and quick settings” checkbox. When it is unchecked, if the lockscreen is up, notifications should be suppressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1371081/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371081] Re: if “when locked, allow [...] notifications” is disabled, notifications should not be shown
About the settings, if they're to be per app, I guess the ones that go via postal would be under the Notifications preferences. That makes sense, although if it is entirely per app it will make turning them all off a little tedious. Discovering the settings for SMS, if they are not also put under Notifications, will be harder (i'm an advocate of making SMSes use the postal service, but that's a conversation for the sprint). In any case, whether the setting is global or per app, there needs to be support for this at the unity level: doing the check at any other level is just too racy. -- 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/1371081 Title: if “when locked, allow [...] notifications” is disabled, notifications should not be shown Status in “unity8” package in Ubuntu: In Progress Bug description: Under system settings - Privacy Security - Phone locking there's a “When locked, allow: notifications and quick settings” checkbox. When it is unchecked, if the lockscreen is up, notifications should be suppressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1371081/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364935] [NEW] 2FA entry should not be password-style, should use numeric keyboard
Public bug reported: The 2FA entry right now uses a password-style echo, which is wrong, and does not request the numeric keyboard, which isn't right. ** Affects: ubuntuone-credentials (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1364935 Title: 2FA entry should not be password-style, should use numeric keyboard Status in “ubuntuone-credentials” package in Ubuntu: New Bug description: The 2FA entry right now uses a password-style echo, which is wrong, and does not request the numeric keyboard, which isn't right. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1364935/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1356077] Re: Post Office uses URL Dispatcher DBus interface which isn't stable
** Changed in: ubuntu-push Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1356077 Title: Post Office uses URL Dispatcher DBus interface which isn't stable Status in Ubuntu Push Notifications: Fix Released Status in URL Dispatcher: New Status in “url-dispatcher” package in Ubuntu: Fix Released Bug description: Please use liburl-dispatcher, the versioned interface to URL Dispatcher. The DBus interface may change arbitrarily in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-push/+bug/1356077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp