[Touch-packages] [Bug 1807077] Re: [SRU] mountall crashes on udev node with missing devname
Per https://wiki.ubuntu.com/QATeam/PerformingSRUVerification I had added the procedure and results to the description: TEST CASE: 1. Enable -proposed 2. apt-get install mountall=2.53ubuntu1 3. update-initramfs -k all -u 4. Reboot VERIFICATION DONE Rebooted successfully on affected Gen10 systems. Confirmed no regression on unaffected systems. ** Changed in: mountall (Ubuntu Trusty) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname Status in mountall package in Ubuntu: Invalid Status in mountall source package in Trusty: Fix Committed Status in mountall source package in Xenial: Won't Fix Bug description: [Impact] * udev block nodes without a devname will crash mountall, resulting in an unbootable system (emergency root shell) * While this is not likely to happen in a matched distro/kernel environment (it was discovered while needing to run a bionic 4.15 kernel on trusty), it is possible. * The code in try_udev_device() assumes a block subsystem will always have a devname; the SRU patches explicitly check for a devname and return if null. [Test Case] * HPE DL385 Gen10, Samsung a822 NVMe controller, trusty install * Kernels <4.15 (or possibly 4.14) do not expose nvme0c33n1 and do not trigger the bug. Tested on 4.13, 4.4 and 3.13. * Kernel 4.15 exposes nvme0c33n1 in udev but does not have a devname, mountall crash ensues. [Regression Potential] * Patch might ignore legitimate block devices on existing installations. Unlikely, since the logic path for null devname leads directly to a program crash. [Other Info] * Additional context for Canonical employees: PS4.5 is a trusty backend cloud, but we now have Gen10 hardware incoming (this was discovered while adding new nova-compute hardware). Older kernels are not usable because Gen10 requires ilorest, which requires a >4.4 kernel (at least artful 4.13 is known good). So trusty+4.15 is the only viable combination for continued support of the cloud while adding new hardware. This is done via apt pinning of bionic for the kernel packages, and, mountall notwithstanding, is working fine so far. TEST CASE: 1. Enable -proposed 2. apt-get install mountall=2.53ubuntu1 3. update-initramfs -k all -u 4. Reboot VERIFICATION DONE Rebooted successfully on affected Gen10 systems. Confirmed no regression on unaffected systems. Original description: Running bionic's 4.15 kernel on trusty on an HPE DL385 Gen10 results in a device node for the NVMe controller, /devices/pci:40/:40:03.1/:43:00.0/nvme/nvme0/nvme0c33n1 which itself does not have a devname. When mountall gets to it: fsck_update: updating check priorities try_mount: /srv/nova/instances waiting for device try_udev_device: ignored /dev/loop5 (not yet ready?) try_udev_device: ignored /dev/loop6 (not yet ready?) try_udev_device: ignored /dev/loop1 (not yet ready?) try_udev_device: ignored /dev/loop0 (not yet ready?) try_udev_device: block (null) (null) (null) and then crashes, leaving the boot at an emergency root shell. A successful scan looks like this for comparison: try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sda (null) (null) try_udev_device: block /dev/nvme0n1 ed56e3a9-60f7-4636-85a2-b53137b598e7 (null) try_udev_device: block /dev/bcache0 756cb2c6-b999-4905-a021-c2e688e81a86 instances The debdiffs check for a null devname in try_udev_device() and will not attempt to process it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- Mailing list: https://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 1811248] Re: systemd--networkd mounts denied for lxc guest
On Fri, Jan 11, 2019 at 02:36:30AM -, km wrote:
> profile="lxc-container-default-cgns"
>
> profile lxc-container-default-cgns
> flags=(attach_disconnected,mediate_deleted) {
> #include
>
> # the container may never be allowed to mount devpts. If it does, it
> # will remount the host's devpts. We could allow it to do it with
> # the newinstance option (but, right now, we don't).
> deny mount fstype=devpts,
> mount fstype=cgroup -> /sys/fs/cgroup/**,
> mount fstype=cgroup2 -> /sys/fs/cgroup/**,
> }
Thanks.
> > flags are being used by the mount(2) system call that's failed
>
> Pardon my ignorance as not being sure what you are asking here. I
> thought it was obvious from the log
>
> pid=8426 comm="(networkd)" flags="rw, rslave"
It's my ignorance here -- I don't know if AppArmor's log message is
sufficient to reconstruct the actual mount() syscall that the process
has performed -- and I don't know if the extra parameters that may be
in the syscall are important or not.
If you could catch the mount() syscall with strace that'd be beautiful.
Thanks
--
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/1811248
Title:
systemd--networkd mounts denied for lxc guest
Status in apparmor package in Ubuntu:
New
Bug description:
Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7
Guest Arch Linux | systemd 240.0
After having upgraded in the guest systemd from 239.370 to 240.0 the
host's AA is exhibiting
> audit: type=1400 audit(1547125168.853:722): apparmor="DENIED"
operation="mount" info="failed flags match" error=-13 profile="lxc-
container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw,
rslave"
and the guest
> systemd-networkd.service: Failed to set up mount namespacing: Permission
denied
> systemd-networkd.service: Failed at step NAMESPACE spawning
/usr/lib/systemd/systemd-networkd: Permission denied
According to lxc bug tracker https://github.com/lxc/lxc/issues/2778
> While we'd like to allow such mounts we cannot do so until the
apparmor_parser is fixed to handle them correctly.
other cross references
https://github.com/systemd/systemd/issues/11371
https://bugs.archlinux.org/task/61313
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804864] Re: autopkgtest regression TEST-22-TMPFILES are not executable
This bug was fixed in the package systemd - 239-7ubuntu10.6 --- systemd (239-7ubuntu10.6) cosmic-security; urgency=medium * SECURITY UPDATE: memory corruption in journald via attacker controlled alloca - debian/patches/CVE-2018-16864.patch: journald: do not store the iovec entry for process commandline on the stack - CVE-2018-16864 * SECURITY UPDATE: memory corruption in journald via attacker controlled alloca - debian/patches/CVE-2018-16865_1.patch: journald: set a limit on the number of fields (1k) - debian/patches/CVE-2018-16865_2.patch: journal-remote: set a limit on the number of fields in a message - CVE-2018-16865 * SECURITY UPDATE: out-of-bounds read in journald - debian/patches/CVE-2018-16866.patch: journal: fix syslog_parse_identifier() - CVE-2018-16866 * Fix LP: #1804603 - btrfs-util: unbreak tmpfiles' subvol creation - add debian/patches/btrfs-util-unbreak-tmpfiles-subvol-creation.patch - update debian/patches/series * Fix LP: #1804864 - test: Set executable bits on TEST-22-TMPFILES shell scripts - add debian/patches/test-Set-executable-bits-on-TEST-22-TMPFILES-shell-script.patch - update debian/patches/series -- Chris Coulson Wed, 09 Jan 2019 14:37:15 + ** Changed in: systemd (Ubuntu Cosmic) Status: Fix Committed => Fix 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/1804864 Title: autopkgtest regression TEST-22-TMPFILES are not executable Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Newly added testcase in a security upload used a traditional GNU patch format, instead of using extended git patch format, as supported by GNU patch. Therefore, executable bits on shells scripts were lost, resulting in autopkgtest failures. [Test Case] * `upstream` test/TEST-22-TMPFILES autopkgtest case should pass. [Regression Potential] * This is testcode change only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
This bug was fixed in the package systemd - 239-7ubuntu10.6 --- systemd (239-7ubuntu10.6) cosmic-security; urgency=medium * SECURITY UPDATE: memory corruption in journald via attacker controlled alloca - debian/patches/CVE-2018-16864.patch: journald: do not store the iovec entry for process commandline on the stack - CVE-2018-16864 * SECURITY UPDATE: memory corruption in journald via attacker controlled alloca - debian/patches/CVE-2018-16865_1.patch: journald: set a limit on the number of fields (1k) - debian/patches/CVE-2018-16865_2.patch: journal-remote: set a limit on the number of fields in a message - CVE-2018-16865 * SECURITY UPDATE: out-of-bounds read in journald - debian/patches/CVE-2018-16866.patch: journal: fix syslog_parse_identifier() - CVE-2018-16866 * Fix LP: #1804603 - btrfs-util: unbreak tmpfiles' subvol creation - add debian/patches/btrfs-util-unbreak-tmpfiles-subvol-creation.patch - update debian/patches/series * Fix LP: #1804864 - test: Set executable bits on TEST-22-TMPFILES shell scripts - add debian/patches/test-Set-executable-bits-on-TEST-22-TMPFILES-shell-script.patch - update debian/patches/series -- Chris Coulson Wed, 09 Jan 2019 14:37:15 + ** Changed in: systemd (Ubuntu Cosmic) Status: Fix Committed => Fix 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811248] Re: systemd--networkd mounts denied for lxc guest
profile="lxc-container-default-cgns"
profile lxc-container-default-cgns flags=(attach_disconnected,mediate_deleted) {
#include
# the container may never be allowed to mount devpts. If it does, it
# will remount the host's devpts. We could allow it to do it with
# the newinstance option (but, right now, we don't).
deny mount fstype=devpts,
mount fstype=cgroup -> /sys/fs/cgroup/**,
mount fstype=cgroup2 -> /sys/fs/cgroup/**,
}
__
> flags are being used by the mount(2) system call that's failed
Pardon my ignorance as not being sure what you are asking here. I
thought it was obvious from the log
pid=8426 comm="(networkd)" flags="rw, rslave"
--
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/1811248
Title:
systemd--networkd mounts denied for lxc guest
Status in apparmor package in Ubuntu:
New
Bug description:
Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7
Guest Arch Linux | systemd 240.0
After having upgraded in the guest systemd from 239.370 to 240.0 the
host's AA is exhibiting
> audit: type=1400 audit(1547125168.853:722): apparmor="DENIED"
operation="mount" info="failed flags match" error=-13 profile="lxc-
container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw,
rslave"
and the guest
> systemd-networkd.service: Failed to set up mount namespacing: Permission
denied
> systemd-networkd.service: Failed at step NAMESPACE spawning
/usr/lib/systemd/systemd-networkd: Permission denied
According to lxc bug tracker https://github.com/lxc/lxc/issues/2778
> While we'd like to allow such mounts we cannot do so until the
apparmor_parser is fixed to handle them correctly.
other cross references
https://github.com/systemd/systemd/issues/11371
https://bugs.archlinux.org/task/61313
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
This bug was fixed in the package systemd - 237-3ubuntu10.11 --- systemd (237-3ubuntu10.11) bionic-security; urgency=medium * SECURITY UPDATE: memory corruption in journald via attacker controlled alloca - debian/patches/CVE-2018-16864.patch: journald: do not store the iovec entry for process commandline on the stack - CVE-2018-16864 * SECURITY UPDATE: memory corruption in journald via attacker controlled alloca - debian/patches/CVE-2018-16865_1.patch: journald: set a limit on the number of fields (1k) - debian/patches/CVE-2018-16865_2.patch: journal-remote: set a limit on the number of fields in a message - CVE-2018-16865 * SECURITY UPDATE: out-of-bounds read in journald - debian/patches/CVE-2018-16866.patch: journal: fix syslog_parse_identifier() - CVE-2018-16866 * Fix LP: #1804603 - btrfs-util: unbreak tmpfiles' subvol creation - add debian/patches/btrfs-util-unbreak-tmpfiles-subvol-creation.patch - update debian/patches/series * Fix LP: #1804864 - test: Set executable bits on TEST-22-TMPFILES shell scripts - add debian/patches/test-Set-executable-bits-on-TEST-22-TMPFILES-shell-script.patch - update debian/patches/series -- Chris Coulson Wed, 09 Jan 2019 15:11:53 + ** Changed in: systemd (Ubuntu Bionic) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16864 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16865 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16866 -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804864] Re: autopkgtest regression TEST-22-TMPFILES are not executable
This bug was fixed in the package systemd - 237-3ubuntu10.11 --- systemd (237-3ubuntu10.11) bionic-security; urgency=medium * SECURITY UPDATE: memory corruption in journald via attacker controlled alloca - debian/patches/CVE-2018-16864.patch: journald: do not store the iovec entry for process commandline on the stack - CVE-2018-16864 * SECURITY UPDATE: memory corruption in journald via attacker controlled alloca - debian/patches/CVE-2018-16865_1.patch: journald: set a limit on the number of fields (1k) - debian/patches/CVE-2018-16865_2.patch: journal-remote: set a limit on the number of fields in a message - CVE-2018-16865 * SECURITY UPDATE: out-of-bounds read in journald - debian/patches/CVE-2018-16866.patch: journal: fix syslog_parse_identifier() - CVE-2018-16866 * Fix LP: #1804603 - btrfs-util: unbreak tmpfiles' subvol creation - add debian/patches/btrfs-util-unbreak-tmpfiles-subvol-creation.patch - update debian/patches/series * Fix LP: #1804864 - test: Set executable bits on TEST-22-TMPFILES shell scripts - add debian/patches/test-Set-executable-bits-on-TEST-22-TMPFILES-shell-script.patch - update debian/patches/series -- Chris Coulson Wed, 09 Jan 2019 15:11:53 + ** Changed in: systemd (Ubuntu Bionic) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16864 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16865 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16866 -- 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/1804864 Title: autopkgtest regression TEST-22-TMPFILES are not executable Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * Newly added testcase in a security upload used a traditional GNU patch format, instead of using extended git patch format, as supported by GNU patch. Therefore, executable bits on shells scripts were lost, resulting in autopkgtest failures. [Test Case] * `upstream` test/TEST-22-TMPFILES autopkgtest case should pass. [Regression Potential] * This is testcode change only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811248] Re: systemd--networkd mounts denied for lxc guest
Could you add to this bug which mount flags are being used by the mount(2) system call that's failed and which mount rules are in the profile? I couldn't find either information in the linked bugs. Thanks -- 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/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1591535] Re: [Satellite A215, Realtek ALC268, Mic, Internal] No sound at all. My built-in internal mic won't record sounds.
** Description changed: + https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/618 + + --- + My built-in internal mic on my Toshiba Satellite-A215 will not pick up sounds. The external speakers work just fine, but once again the mic can't record any sounds. I have an Ubuntu 14.04.4 LTS. Below is a link of my ALSA "info" that may be useful: http://www.alsa- project.org/db/?f=10a2337ec9b863d7414121dff10f30ad0cdf430d I've tried the ALSA DKMS update recommended to me by an ubuntuforums.org user from this link: https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS However after following the instructions from the above link, the mic still has not worked. The same Ubuntu forum user suggested I file a bug. He/she provided me with a link from "an old report from an A215 with the same ALC268 codec": https://bugs.launchpad.net/ubuntu/+s...r/+bug/1081353 I provided this because it may be helpful in the debug process. The version of ALSA I have is shown below: Advanced Linux Sound Architecture Driver Version k3.19.0-61-generic. Any help would be appreciated, please let me know if you need any additional info. - PS + PS I've also provided a link below of the ongoing forum discussion I've been having at ubuntuforums.org below: http://ubuntuforums.org/showthread.php?t=2323851 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21 Uname: Linux 3.19.0-61-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: richard1533 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: richard1533 F pulseaudio CurrentDesktop: Unity Date: Sat Jun 11 10:49:01 2016 InstallationDate: Installed on 2016-01-06 (156 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: richard1533 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: richard1533 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [Satellite A215, Realtek ALC268, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.10 dmi.board.name: IALAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.10:bd05/23/2007:svnTOSHIBA:pnSatelliteA215:pvrPSAEGU-01700U:rvnTOSHIBA:rnIALAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A215 dmi.product.version: PSAEGU-01700U dmi.sys.vendor: TOSHIBA mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-06-06T05:53:22.078529 -- 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/1591535 Title: [Satellite A215, Realtek ALC268, Mic, Internal] No sound at all. My built-in internal mic won't record sounds. Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/618 --- My built-in internal mic on my Toshiba Satellite-A215 will not pick up sounds. The external speakers work just fine, but once again the mic can't record any sounds. I have an Ubuntu 14.04.4 LTS. Below is a link of my ALSA "info" that may be useful: http://www.alsa- project.org/db/?f=10a2337ec9b863d7414121dff10f30ad0cdf430d I've tried the ALSA DKMS update recommended to me by an ubuntuforums.org user from this link: https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS However after following the instructions from the above link, the mic still has not worked. The same Ubuntu forum user suggested I file a bug. He/she provided me with a link from "an old report from an A215 with the same ALC268 codec": https://bugs.launchpad.net/ubuntu/+s...r/+bug/1081353 I provided this because it may be helpful in the debug process. The version of ALSA I have is shown below: Advanced Linux Sound Architecture Driver Version k3.19.0-61-generic. Any help would be appreciated, please let me know if you need any additional info. PS I've also provided a link below of the ongoing forum discussion I've been having at ubuntuforums.org below: http://ubuntuforums.org/showthread.php?t=2323851 ProblemType: Bug DistroRelease: Ubuntu
[Touch-packages] [Bug 1184152] Re: du crashed with SIGABRT in leave_dir()
Thanks for opening this bug up. I've put a hacky patch together so will leave glibc re-building overnight, I'll post a patch *if* I manage to come up with a palatable workaround. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1184152 Title: du crashed with SIGABRT in leave_dir() Status in coreutils package in Ubuntu: Confirmed Bug description: automatically generated. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: coreutils 8.13-3ubuntu3.2 ProcVersionSignature: Ubuntu 3.5.0-31.52~precise1-generic 3.5.7.11 Uname: Linux 3.5.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 Date: Sat May 25 22:57:29 2013 ExecutablePath: /usr/bin/du InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True ProcCmdline: du -sh /media/Learn/ebook_Tutorial/ ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: coreutils StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () ?? () fts_read () Title: du crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1184152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811281] Re: du crashed with SIGABRT in fts_read()
*** This bug is a duplicate of bug 1184152 *** https://bugs.launchpad.net/bugs/1184152 Thanks, appreciated. And sorry for the noise, I'll put my glasses on next time so I don't miss the 'private bug' text I saw after commenting... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1811281 Title: du crashed with SIGABRT in fts_read() Status in coreutils package in Ubuntu: New Bug description: Hopefully this bug report isn't a duplicate (I couldn't find anything more recent than a ~6 year old bug of a similar nature yet different function). The problem is that, on the order of once per boot, a simple "du -shc" ends up calling "abort()" extremely quickly. It appears to be on the random side as directories to be traversed have varied in size, backing filesystem type (XFS, and ext4 iirc) and hard drive type (SSD included) also. Attempts thereafter to reproduce result in, well, what I expected - du not dumping core. I've submitted at least two crash reports on this issue in the past; the first was on/around 2018/09/08 and the last was probably around November of last year also. On reading Ubuntu's bug-reporting guidelines[1], I note that whoopsie needs to be installed for these reports to actually make their way upstream and I *do* have that package installed locally. Is there anything I can do to help get this bug fixed? From a quick scan it seems "fts_read()" lives within glibc; I'm prepared to see if I can debug this further with or without help, but it's been a long time since I debugged anything C-code related and it'll take to get reacquainted with gdb & co. So if anyone has a "look in foo.c:func()" type pointer, it'd be much appreciated! ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 10 19:42:20 2019 ExecutablePath: /usr/bin/du InstallationDate: Installed on 2018-09-08 (124 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: du -shc /var/lib ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_GB:en PATH=(custom, no user) Signal: 6 SourcePackage: coreutils StacktraceTop: ?? () ?? () fts_read () ?? () __libc_start_main (main=0x556220f61d30, argc=3, argv=0x7ffd0ca68378, init=, fini=, rtld_fini=, stack_end=0x7ffd0ca68368) at ../csu/libc-start.c:310 Title: du crashed with SIGABRT in fts_read() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1811281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1571915] Re: Header cpu %'s don't match reality or per-process usage
Not an issue in 18.10 which I now use. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1571915 Title: Header cpu %'s don't match reality or per-process usage Status in procps package in Ubuntu: New Bug description: The header of top (i.e the part that looks as below) is frequently reporting unlikely result. With high load it is reporting mostly idle, even though the per-process cpu usage is reporting multiple processes with 100% and one with 200% cpu usage on a multicore machine. The numbers don't make sense and don't match the kind of numbers reported in trusty. There is clearly some funkiness in what the header is reporting. top - 22:14:53 up 8:31, 2 users, load average: 4.39, 4.79, 5.07 Tasks: 323 total, 2 running, 321 sleeping, 0 stopped, 0 zombie %Cpu(s): 33.9 us, 4.4 sy, 0.0 ni, 61.5 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 65937708 total, 5825444 free, 24041364 used, 36070900 buff/cache KiB Swap: 67067900 total, 67037844 free,30056 used. 41123072 avail Mem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1571915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1184152] Re: du crashed with SIGABRT in leave_dir()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1184152 Title: du crashed with SIGABRT in leave_dir() Status in coreutils package in Ubuntu: Confirmed Bug description: automatically generated. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: coreutils 8.13-3ubuntu3.2 ProcVersionSignature: Ubuntu 3.5.0-31.52~precise1-generic 3.5.7.11 Uname: Linux 3.5.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 Date: Sat May 25 22:57:29 2013 ExecutablePath: /usr/bin/du InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True ProcCmdline: du -sh /media/Learn/ebook_Tutorial/ ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: coreutils StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () ?? () fts_read () Title: du crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1184152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811281] Re: du crashed with SIGABRT in fts_read()
*** This bug is a duplicate of bug 1184152 *** https://bugs.launchpad.net/bugs/1184152 bug 1184152 has been set public. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1811281 Title: du crashed with SIGABRT in fts_read() Status in coreutils package in Ubuntu: New Bug description: Hopefully this bug report isn't a duplicate (I couldn't find anything more recent than a ~6 year old bug of a similar nature yet different function). The problem is that, on the order of once per boot, a simple "du -shc" ends up calling "abort()" extremely quickly. It appears to be on the random side as directories to be traversed have varied in size, backing filesystem type (XFS, and ext4 iirc) and hard drive type (SSD included) also. Attempts thereafter to reproduce result in, well, what I expected - du not dumping core. I've submitted at least two crash reports on this issue in the past; the first was on/around 2018/09/08 and the last was probably around November of last year also. On reading Ubuntu's bug-reporting guidelines[1], I note that whoopsie needs to be installed for these reports to actually make their way upstream and I *do* have that package installed locally. Is there anything I can do to help get this bug fixed? From a quick scan it seems "fts_read()" lives within glibc; I'm prepared to see if I can debug this further with or without help, but it's been a long time since I debugged anything C-code related and it'll take to get reacquainted with gdb & co. So if anyone has a "look in foo.c:func()" type pointer, it'd be much appreciated! ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 10 19:42:20 2019 ExecutablePath: /usr/bin/du InstallationDate: Installed on 2018-09-08 (124 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: du -shc /var/lib ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_GB:en PATH=(custom, no user) Signal: 6 SourcePackage: coreutils StacktraceTop: ?? () ?? () fts_read () ?? () __libc_start_main (main=0x556220f61d30, argc=3, argv=0x7ffd0ca68378, init=, fini=, rtld_fini=, stack_end=0x7ffd0ca68368) at ../csu/libc-start.c:310 Title: du crashed with SIGABRT in fts_read() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1811281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811295] [NEW] systemctl daemon-reexec does not update group membership
Public bug reported: On Ubuntu 16.04.4 LTS using Package: systemd Architecture: amd64 Version: 229-4ubuntu21.10 Changes the group membership are not picked up by the systemd process for a logged-in user or for a user with enable-linger set regardless of login status. Evidently the systemctl --user daemon-reexec command preserves group membership across the daemon restart. This is bad. It means that only a reboot or sudo loginctl terminate-user will update the group membership to the proper set. Both of those things are extreme disruptions for a system/user that runs servers. Can systemctl daemon-reexec be made to update group membership for the user in the systemd process? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1811295 Title: systemctl daemon-reexec does not update group membership Status in systemd package in Ubuntu: New Bug description: On Ubuntu 16.04.4 LTS using Package: systemd Architecture: amd64 Version: 229-4ubuntu21.10 Changes the group membership are not picked up by the systemd process for a logged-in user or for a user with enable-linger set regardless of login status. Evidently the systemctl --user daemon-reexec command preserves group membership across the daemon restart. This is bad. It means that only a reboot or sudo loginctl terminate-user will update the group membership to the proper set. Both of those things are extreme disruptions for a system/user that runs servers. Can systemctl daemon-reexec be made to update group membership for the user in the systemd process? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811281] Re: du crashed with SIGABRT in fts_read()
*** This bug is a duplicate of bug 1184152 *** https://bugs.launchpad.net/bugs/1184152 Oh wait, I think I figured it out. Bug #1184152 is set to private whih means I can't see it or contribute there? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1811281 Title: du crashed with SIGABRT in fts_read() Status in coreutils package in Ubuntu: New Bug description: Hopefully this bug report isn't a duplicate (I couldn't find anything more recent than a ~6 year old bug of a similar nature yet different function). The problem is that, on the order of once per boot, a simple "du -shc" ends up calling "abort()" extremely quickly. It appears to be on the random side as directories to be traversed have varied in size, backing filesystem type (XFS, and ext4 iirc) and hard drive type (SSD included) also. Attempts thereafter to reproduce result in, well, what I expected - du not dumping core. I've submitted at least two crash reports on this issue in the past; the first was on/around 2018/09/08 and the last was probably around November of last year also. On reading Ubuntu's bug-reporting guidelines[1], I note that whoopsie needs to be installed for these reports to actually make their way upstream and I *do* have that package installed locally. Is there anything I can do to help get this bug fixed? From a quick scan it seems "fts_read()" lives within glibc; I'm prepared to see if I can debug this further with or without help, but it's been a long time since I debugged anything C-code related and it'll take to get reacquainted with gdb & co. So if anyone has a "look in foo.c:func()" type pointer, it'd be much appreciated! ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 10 19:42:20 2019 ExecutablePath: /usr/bin/du InstallationDate: Installed on 2018-09-08 (124 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: du -shc /var/lib ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_GB:en PATH=(custom, no user) Signal: 6 SourcePackage: coreutils StacktraceTop: ?? () ?? () fts_read () ?? () __libc_start_main (main=0x556220f61d30, argc=3, argv=0x7ffd0ca68378, init=, fini=, rtld_fini=, stack_end=0x7ffd0ca68368) at ../csu/libc-start.c:310 Title: du crashed with SIGABRT in fts_read() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1811281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811281] Re: du crashed with SIGABRT in fts_read()
*** This bug is a duplicate of bug 1184152 *** https://bugs.launchpad.net/bugs/1184152 Curious. I tapped the link to bug #1184152 as above[1] and I'm getting an error from Launchpad (attached). Is 1184152 the correct bug ID? Might explain why i didnt find this duplicate if it isnt... [1] https://bugs.launchpad.net/bugs/1184152 ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1811281/+attachment/5228406/+files/Screenshot_20190110-221149_Chrome.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1811281 Title: du crashed with SIGABRT in fts_read() Status in coreutils package in Ubuntu: New Bug description: Hopefully this bug report isn't a duplicate (I couldn't find anything more recent than a ~6 year old bug of a similar nature yet different function). The problem is that, on the order of once per boot, a simple "du -shc" ends up calling "abort()" extremely quickly. It appears to be on the random side as directories to be traversed have varied in size, backing filesystem type (XFS, and ext4 iirc) and hard drive type (SSD included) also. Attempts thereafter to reproduce result in, well, what I expected - du not dumping core. I've submitted at least two crash reports on this issue in the past; the first was on/around 2018/09/08 and the last was probably around November of last year also. On reading Ubuntu's bug-reporting guidelines[1], I note that whoopsie needs to be installed for these reports to actually make their way upstream and I *do* have that package installed locally. Is there anything I can do to help get this bug fixed? From a quick scan it seems "fts_read()" lives within glibc; I'm prepared to see if I can debug this further with or without help, but it's been a long time since I debugged anything C-code related and it'll take to get reacquainted with gdb & co. So if anyone has a "look in foo.c:func()" type pointer, it'd be much appreciated! ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 10 19:42:20 2019 ExecutablePath: /usr/bin/du InstallationDate: Installed on 2018-09-08 (124 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: du -shc /var/lib ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_GB:en PATH=(custom, no user) Signal: 6 SourcePackage: coreutils StacktraceTop: ?? () ?? () fts_read () ?? () __libc_start_main (main=0x556220f61d30, argc=3, argv=0x7ffd0ca68378, init=, fini=, rtld_fini=, stack_end=0x7ffd0ca68368) at ../csu/libc-start.c:310 Title: du crashed with SIGABRT in fts_read() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1811281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
I am also seeing this problem: ``` [Jabra MOVE v2.5.0]# info 74:5C:4B:2A:E3:BE Device 74:5C:4B:2A:E3:BE (public) Name: Jabra MOVE v2.5.0 Alias: Jabra MOVE v2.5.0 Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) [Jabra MOVE v2.5.0]# ``` -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 340422] Re: introduce automatic antialiasing/hinting mode and make gnome honour fontconfig
** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Won't Fix ** Changed in: gnome-settings-daemon (Ubuntu) Status: In Progress => Won't Fix ** Changed in: gtk+2.0 (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/340422 Title: introduce automatic antialiasing/hinting mode and make gnome honour fontconfig Status in gnome-control-center package in Ubuntu: Won't Fix Status in gnome-settings-daemon package in Ubuntu: Won't Fix Status in gtk+2.0 package in Ubuntu: Won't Fix Bug description: Binary package hint: gnome-settings-daemon this bug is forked from bug 332172 Currently gtk and settings daemon override the fontconfig default wrt to hinting/antialiasing by setting xdefaults: Xft/* The fix involves: 1. make gtk honour the monitor settings (which are already detected by cairo and libxft2 atm) if we are in "automatic" mode. 2. make gnome-settings-daemon aware of automatic mode and stop setting the Xft/* overrides if automatic mode is used 3. add UI to opt-out from automatic mode in font appearence dialog of gnome-control-center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/340422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811210] Re: intramfs-tools 0.130ubuntu3.3 in bionic-security breaks netplan.io in -security or in release
A rebuild of netplan.io into the security pocket was performed an hour ago and should fix this issue. I am marking this bug as fix released, feel free to re-open it if the issue isn't actually resolved. Thanks! ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released ** Changed in: initramfs-tools (Ubuntu Bionic) Status: New => Fix Released -- 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/1811210 Title: intramfs-tools 0.130ubuntu3.3 in bionic-security breaks netplan.io in -security or in release Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Bug description: Adding Breaks: netplan.io (<< 0.36.2) made initramfs-tools uninstallable by default unattended-upgrades configuration because netplan.io >= 0.36.2 is not available from bionic or bionic-security (only in bionic-updates). This is originally reported as https://github.com/mvo5/unattended- upgrades/issues/165 . U-u's email reporting behaviour is a valid different question, but IMO when such Break is added in -security a non-breaking version of the other package should be added to -security, too, like when we add new dependencies. Please provide a netplan.io version in -security that allows upgrade of initramfs-tools either by uploading 0.36.2 or just cherry-picking the needed fixes and relaxing the Breaks: in initramfs-tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1811210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768026] Re: echo message hides cursor
+1 for adding the fix to 18.04 LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1768026 Title: echo message hides cursor Status in vim: Fix Released Status in vim package in Ubuntu: Confirmed Bug description: https://github.com/w0rp/ale/issues/1536#issuecomment-385056702 upstream bug https://github.com/vim/vim/issues/2612 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim 2:8.0.1453-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:16:35 2018 InstallationDate: Installed on 2017-05-17 (347 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: vim UpgradeStatus: Upgraded to bionic on 2018-04-26 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/vim/+bug/1768026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811281] Re: du crashed with SIGABRT in fts_read()
*** This bug is a duplicate of bug 1184152 *** https://bugs.launchpad.net/bugs/1184152 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1184152, so 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. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1811281/+attachment/5228394/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1811281/+attachment/5228396/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1811281/+attachment/5228399/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1811281/+attachment/5228400/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1811281/+attachment/5228401/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1811281/+attachment/5228402/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1811281/+attachment/5228403/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1184152 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1811281 Title: du crashed with SIGABRT in fts_read() Status in coreutils package in Ubuntu: New Bug description: Hopefully this bug report isn't a duplicate (I couldn't find anything more recent than a ~6 year old bug of a similar nature yet different function). The problem is that, on the order of once per boot, a simple "du -shc" ends up calling "abort()" extremely quickly. It appears to be on the random side as directories to be traversed have varied in size, backing filesystem type (XFS, and ext4 iirc) and hard drive type (SSD included) also. Attempts thereafter to reproduce result in, well, what I expected - du not dumping core. I've submitted at least two crash reports on this issue in the past; the first was on/around 2018/09/08 and the last was probably around November of last year also. On reading Ubuntu's bug-reporting guidelines[1], I note that whoopsie needs to be installed for these reports to actually make their way upstream and I *do* have that package installed locally. Is there anything I can do to help get this bug fixed? From a quick scan it seems "fts_read()" lives within glibc; I'm prepared to see if I can debug this further with or without help, but it's been a long time since I debugged anything C-code related and it'll take to get reacquainted with gdb & co. So if anyone has a "look in foo.c:func()" type pointer, it'd be much appreciated! ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 10 19:42:20 2019 ExecutablePath: /usr/bin/du InstallationDate: Installed on 2018-09-08 (124 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: du -shc /var/lib ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_GB:en PATH=(custom, no user) Signal: 6 SourcePackage: coreutils StacktraceTop: ?? () ?? () fts_read () ?? () __libc_start_main (main=0x556220f61d30, argc=3, argv=0x7ffd0ca68378, init=, fini=, rtld_fini=, stack_end=0x7ffd0ca68368) at ../csu/libc-start.c:310 Title: du crashed with SIGABRT in fts_read() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1811281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441253] Re: hanging suspend job prevents shutdown
Reporting exact same issue. Running 18.04.1 on System76 Serval WS. (1) On clean boot, (most times) no network connection. Have to run: > sudo service network-manager restart (2) Suspend/power off fails, and have to kill existing hanging suspend -- 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/1441253 Title: hanging suspend job prevents shutdown Status in systemd package in Ubuntu: Won't Fix Bug description: poweroff (systemd poweroff) and reboot no longer work running sudo sytemd poweroff generates this: Failed to start poweroff.target: Transaction is destructive. journal log also shows: Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Registered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Apr 07 18:30:12 alice systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive. Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Unregistered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Output of systemctl list-jobs JOB UNITTYPE STATE 6009 suspend.target start waiting 6010 systemd-suspend.service start running 6014 anacron-resume.service start waiting ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Tue Apr 7 18:32:27 2015 MachineType: Hewlett-Packard HP EliteBook 8560w ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-12-generic root=UUID=90fa42f5-708d-4432-9241-315b9c08ba98 ro nomodeset rootflags=subvol=@ SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to vivid on 2015-03-02 (36 days ago) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.50 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790205] Re: systemd journals take up too much space, aren't vacuumed automatically
** Tags added: 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/1790205 Title: systemd journals take up too much space, aren't vacuumed automatically Status in systemd package in Ubuntu: Confirmed Bug description: After running Bionic for 3 months, I had 2.6 GB of journals. I would not expect from a normal desktop user that they should have to run commands like `sudo journalctl --vacuum-time=10d`. I would nominate this command as a sane default to have running at each reboot to ensure that logs do not exceed 500 MB: sudo journalctl --vacuum-size=500M Supposedly, a server should by default retain more logs, so perhaps this should be implemented through a configuration package "systemd- configuration-desktop" as a dependency of the ubuntu-desktop meta package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1591535] Re: [Satellite A215, Realtek ALC268, Mic, Internal] No sound at all. My built-in internal mic won't record sounds.
A new bugreport is opened at https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/618 -- 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/1591535 Title: [Satellite A215, Realtek ALC268, Mic, Internal] No sound at all. My built-in internal mic won't record sounds. Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: My built-in internal mic on my Toshiba Satellite-A215 will not pick up sounds. The external speakers work just fine, but once again the mic can't record any sounds. I have an Ubuntu 14.04.4 LTS. Below is a link of my ALSA "info" that may be useful: http://www.alsa- project.org/db/?f=10a2337ec9b863d7414121dff10f30ad0cdf430d I've tried the ALSA DKMS update recommended to me by an ubuntuforums.org user from this link: https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS However after following the instructions from the above link, the mic still has not worked. The same Ubuntu forum user suggested I file a bug. He/she provided me with a link from "an old report from an A215 with the same ALC268 codec": https://bugs.launchpad.net/ubuntu/+s...r/+bug/1081353 I provided this because it may be helpful in the debug process. The version of ALSA I have is shown below: Advanced Linux Sound Architecture Driver Version k3.19.0-61-generic. Any help would be appreciated, please let me know if you need any additional info. PS I've also provided a link below of the ongoing forum discussion I've been having at ubuntuforums.org below: http://ubuntuforums.org/showthread.php?t=2323851 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21 Uname: Linux 3.19.0-61-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: richard1533 F pulseaudio CurrentDesktop: Unity Date: Sat Jun 11 10:49:01 2016 InstallationDate: Installed on 2016-01-06 (156 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: richard1533 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [Satellite A215, Realtek ALC268, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.10 dmi.board.name: IALAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.10:bd05/23/2007:svnTOSHIBA:pnSatelliteA215:pvrPSAEGU-01700U:rvnTOSHIBA:rnIALAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A215 dmi.product.version: PSAEGU-01700U dmi.sys.vendor: TOSHIBA mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-06-06T05:53:22.078529 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1591535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809093] Re: Internal microphone doesn't work with Realtek ALC268 chipset
*** This bug is a duplicate of bug 1591535 *** https://bugs.launchpad.net/bugs/1591535 A new bugreport is opened at https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/618 -- 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/1809093 Title: Internal microphone doesn't work with Realtek ALC268 chipset Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have this problem with Ubuntu 18.04, 18.10 and Linux Mint 19, on my HP Pavilion dv6700, with a Realtek ALC268 chipset. Audio is working but not internal and external microphones. As explained in https://elubuntero.wordpress.com/tag/realtek-alc268/ , I tried to add linux-backports-modules-*** but this package isn't anymore in Ubuntu and Mint repositories. I tried all options as explained in https://doc.ubuntu- fr.org/audio_intel_hda, without result. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 6306 F pulseaudio CasperVersion: 1.399 Date: Wed Dec 19 09:35:53 2018 LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.58 dmi.board.name: 30D2 dmi.board.vendor: Quanta dmi.board.version: 79.2E dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.58:bd06/16/2008:svnHewlett-Packard:pnHPPaviliondv6700NotebookPC:pvrRev1:rvnQuanta:rn30D2:rvr79.2E:cvnQuanta:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv6700 Notebook PC dmi.product.sku: KS356EA#ABF dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1809093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810560] Re: Internal and external microphone don't work with Realtek ALC268 chipset
*** This bug is a duplicate of bug 1591535 *** https://bugs.launchpad.net/bugs/1591535 A new bugreport is opened at https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/618 -- 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/1810560 Title: Internal and external microphone don't work with Realtek ALC268 chipset Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have this problem with Ubuntu 18.04, 18.10 and Linux Mint 19 on my Acer Extensa 5620Z, with a Realtek ALC268 chipset. Audio is working but not internal and external microphones. As explained in https://elubuntero.wordpress.com/tag/realtek-alc268/ , I tried to add linux-backports-modules-*** but this package isn't anymore in Ubuntu and Mint repositories. I tried all options as explained in https://doc.ubuntu- fr.org/audio_intel_hda without result. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 3307 F pulseaudio CasperVersion: 1.394 Date: Fri Jan 4 21:25:18 2019 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.35 dmi.board.name: Columbia dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5620:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5620 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1810560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]
from IRC discussion, we know that gdb is not affected provided that packages provide .build-id (which glibc does) and we can't think of anything besides gdb, valgrind, and libunwind that uses /usr/lib/debug; so it looks like we should just extend valgrind's lookup path. ** Changed in: valgrind (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: base-files (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1808508 Title: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.] Status in base-files package in Ubuntu: Won't Fix Status in valgrind package in Ubuntu: Triaged Bug description: $ valgrind /bin/ls ==25995== Memcheck, a memory error detector ==25995== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==25995== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==25995== Command: /bin/ls ==25995== valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind:On Debian, Ubuntu: libc6-dbg valgrind:On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: valgrind 1:3.14.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 Date: Fri Dec 14 17:06:03 2018 InstallationDate: Installed on 2018-12-04 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: valgrind UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1808508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]
dh_strip in debhelper v9 mode doesn't use the filename anymore, so gdb should not affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1808508 Title: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.] Status in base-files package in Ubuntu: Won't Fix Status in valgrind package in Ubuntu: Triaged Bug description: $ valgrind /bin/ls ==25995== Memcheck, a memory error detector ==25995== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==25995== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==25995== Command: /bin/ls ==25995== valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind:On Debian, Ubuntu: libc6-dbg valgrind:On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: valgrind 1:3.14.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 Date: Fri Dec 14 17:06:03 2018 InstallationDate: Installed on 2018-12-04 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: valgrind UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1808508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793876] Re: software-properties-qt/kde does not show in menus
** Changed in: software-properties (Ubuntu) Importance: Undecided => Low ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1793876 Title: software-properties-qt/kde does not show in menus Status in software-properties package in Ubuntu: Confirmed Bug description: Cosmic and Bionic Desktop file sets: NoDisplay=true resulting in no software sources menu entry in KDE menu. This was probably just about ok when Plasma Discover was able to launch this via a menu item in its options, but at least for Plasma 5.13 this is currently broken, and Discover's built-in source selection has further issues. Plus many users decide not to use Discover at all, and even uninstall it altogether. Not withstanding all that, it is just desirable that someone can just type "software" or "sources" in to the search box in Plasma's main menu and find the menu item/launcher for this and use software- properties without having to go a more complicated path. Solution is simply removing the "NoDisplay=true" line from the .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1793876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811253] Re: package software-properties-common 0.96.24.32.7 failed to install/upgrade: dpkg-deb --fsys-tarfile el subproceso devolvió un error con estado de salida 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: fsys-tarfile-error ** Changed in: software-properties (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1811253 Title: package software-properties-common 0.96.24.32.7 failed to install/upgrade: dpkg-deb --fsys-tarfile el subproceso devolvió un error con estado de salida 2 Status in software-properties package in Ubuntu: Invalid Bug description: - ProblemType: Package DistroRelease: Ubuntu 18.04 Package: software-properties-common 0.96.24.32.7 Uname: Linux 4.20.0-042000-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: libnss3:amd64: Install software-properties-common:amd64: Install software-properties-gtk:amd64: Install python3-software-properties:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Jan 10 12:56:28 2019 ErrorMessage: dpkg-deb --fsys-tarfile el subproceso devolvió un error con estado de salida 2 InstallationDate: Installed on 2018-04-29 (255 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: software-properties Title: package software-properties-common 0.96.24.32.7 failed to install/upgrade: dpkg-deb --fsys-tarfile el subproceso devolvió un error con estado de salida 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1811253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793876] Re: software-properties-qt/kde does not show in menus
Thank you for your work, could you propose the change as a merge request on https://code.launchpad.net/~ubuntu-core-dev/software-properties/main ? Removing the NoDisplay seems fine but then you should probably add a ShowOnlyIn=KDE to it (and similar =GNOME to the -gtk one if you want to have rather the kde one only listed) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1793876 Title: software-properties-qt/kde does not show in menus Status in software-properties package in Ubuntu: New Bug description: Cosmic and Bionic Desktop file sets: NoDisplay=true resulting in no software sources menu entry in KDE menu. This was probably just about ok when Plasma Discover was able to launch this via a menu item in its options, but at least for Plasma 5.13 this is currently broken, and Discover's built-in source selection has further issues. Plus many users decide not to use Discover at all, and even uninstall it altogether. Not withstanding all that, it is just desirable that someone can just type "software" or "sources" in to the search box in Plasma's main menu and find the menu item/launcher for this and use software- properties without having to go a more complicated path. Solution is simply removing the "NoDisplay=true" line from the .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1793876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811248] [NEW] systemd--networkd mounts denied for lxc guest
Public bug reported: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission > denied > systemd-networkd.service: Failed at step NAMESPACE spawning > /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
I installed a PPA that served as a workaround, until an update this morning. Now there is no type-ahead and the PPA does not work. One more vote for a type-ahead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811152] Re: Locally installed services can't add dbus configuration
Thanks ** Changed in: dbus (Ubuntu) Importance: Undecided => High ** Changed in: dbus (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1811152 Title: Locally installed services can't add dbus configuration Status in dbus package in Ubuntu: Triaged Bug description: A report was received in upstream fwupd about how the daemon wasn't able to start after the following commands: # meson build # ninja -C build # ninja -C build install This placed everything in /usr/local by default. It also created an /usr/local/etc/dbus-1/system.d/org.freedesktop.conf The daemon can (attempt to) be started by: /usr/local/libexec/fwupd/fwupd -v It fails to acquire org.freedesktop.fwupd on dbus system bus however. This is because by default dbus on Ubuntu does not examine files in /usr/local/etc/dbus-1/system.d. This issue can be fixed if the following is added to /usr/share/dbus-1/system.conf: /usr/local/etc/dbus-1/system.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1811152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811152] Re: Locally installed services can't add dbus configuration
I filed the issue upstream as well. https://gitlab.freedesktop.org/dbus/dbus/issues/253 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1811152 Title: Locally installed services can't add dbus configuration Status in dbus package in Ubuntu: New Bug description: A report was received in upstream fwupd about how the daemon wasn't able to start after the following commands: # meson build # ninja -C build # ninja -C build install This placed everything in /usr/local by default. It also created an /usr/local/etc/dbus-1/system.d/org.freedesktop.conf The daemon can (attempt to) be started by: /usr/local/libexec/fwupd/fwupd -v It fails to acquire org.freedesktop.fwupd on dbus system bus however. This is because by default dbus on Ubuntu does not examine files in /usr/local/etc/dbus-1/system.d. This issue can be fixed if the following is added to /usr/share/dbus-1/system.conf: /usr/local/etc/dbus-1/system.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1811152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811240] [NEW] "journalctl -n1000 -r" does not do what you would expect
Public bug reported: I would expect "journalctl -n1000 -r" to display the most recent 1000 log entries in reverse order. Instead, what it appears to do is skip over the 1000 most recent log entries and display the 1001st - 2000th log entries in reverse order. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.4 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 10 07:57:06 2019 InstallationDate: Installed on 2018-09-27 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/vgencrypted-lvencryptedroot ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-11-08 (62 days ago) dmi.bios.date: 11/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET59W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.apport.crashdb.conf: [modified] modified.conffile..etc.systemd.logind.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 mtime.conffile..etc.systemd.logind.conf: 2018-11-08T10:52:42.381229 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1811240 Title: "journalctl -n1000 -r" does not do what you would expect Status in systemd package in Ubuntu: New Bug description: I would expect "journalctl -n1000 -r" to display the most recent 1000 log entries in reverse order. Instead, what it appears to do is skip over the 1000 most recent log entries and display the 1001st - 2000th log entries in reverse order. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.4 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 10 07:57:06 2019 InstallationDate: Installed on 2018-09-27 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/vgencrypted-lvencryptedroot ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-11-08 (62 days ago) dmi.bios.date: 11/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET59W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.apport.crashdb.conf: [modified] modified.conffile..etc.systemd.logind.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 mtime.conffile..etc.systemd.logind.conf: 2018-11-08T10:52:42.381229 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 973382] Re: Clock settings not customizable
the bug is years old without activity nor new report and the code changed quite a lot since, closing, feel free to register new bugs if you have issues in newer versions though ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/973382 Title: Clock settings not customizable Status in Indicator Date and Time: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in indicator-datetime package in Ubuntu: Invalid Bug description: I click on the clock in the top-right-hand corner, and choose "Time and date Settings" I then click the Tab "Clock" I want the clock to show "WeekDay" and "Date and Month" so I check those two boxes BUT NOTHING HAPPENS - the dialog is broken. I am using U 11.10 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic i686 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu4 Architecture: i386 CasperVersion: 1.287.1 Date: Wed Apr 4 15:36:09 2012 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 20.1-0ubuntu0.2 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/973382/+subscriptions -- Mailing list: https://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 1080591] Re: shotwell fails to authenticate with non-primary address
> Do you still see a problem related to the one that you reported in a > currently supported version of Ubuntu? Thanks for following up! I don't use Shotwell any more, if nobody else corroborates the report, I suggest you just can close it. -k -- If I haven't seen further, it is by standing in the footprints of giants -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-control-center- signon in Ubuntu. https://bugs.launchpad.net/bugs/1080591 Title: shotwell fails to authenticate with non-primary address Status in One Hundred Papercuts: Incomplete Status in Shotwell: Incomplete Status in gnome-control-center-signon package in Ubuntu: Incomplete Status in shotwell package in Ubuntu: Incomplete Bug description: I am trying to export some pictures from Shotwell to my Picasa account. I select Picasa from the "publish" list, and push the button to authenticate. I am asked for password, which I enter. I am then told that "Authentication failed". Subsequent attempts go directly to "Authentication failed", and there is no apparent way to enter the password again. (I thought this was due to me logging in with a non-gmail address, and it seemed to work when I changed to the gmail one, but now it fails again) Further suggestions: 1) Shotwell should be more informative about the Authentication Failure, and report what exactly is wrong. I thought I had mistyped the password, and then it's frustrating not to be offered the opportunity to retype it. 2) The login dialog should offer a direct link or pointer to the accounts settings, now I need to select "Add an account" from the drop down. 3) Incidentally, removing accounts doesn't work, in the end I had to disable two (non-working) instances of Google account configurations. Shotwell version 0.13.0-0ubuntu3, on Ubuntu 12.10, 64bit. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1080591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1080591] Re: shotwell fails to authenticate with non-primary address
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014. Do you still see a problem related to the one that you reported in a currently supported version of Ubuntu? Please let us know if you do and in which version of Ubuntu otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: shotwell (Ubuntu) Status: New => Incomplete ** Changed in: gnome-control-center-signon (Ubuntu) Status: New => Incomplete ** Changed in: hundredpapercuts Status: New => Incomplete ** Changed in: shotwell Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-control-center- signon in Ubuntu. https://bugs.launchpad.net/bugs/1080591 Title: shotwell fails to authenticate with non-primary address Status in One Hundred Papercuts: Incomplete Status in Shotwell: Incomplete Status in gnome-control-center-signon package in Ubuntu: Incomplete Status in shotwell package in Ubuntu: Incomplete Bug description: I am trying to export some pictures from Shotwell to my Picasa account. I select Picasa from the "publish" list, and push the button to authenticate. I am asked for password, which I enter. I am then told that "Authentication failed". Subsequent attempts go directly to "Authentication failed", and there is no apparent way to enter the password again. (I thought this was due to me logging in with a non-gmail address, and it seemed to work when I changed to the gmail one, but now it fails again) Further suggestions: 1) Shotwell should be more informative about the Authentication Failure, and report what exactly is wrong. I thought I had mistyped the password, and then it's frustrating not to be offered the opportunity to retype it. 2) The login dialog should offer a direct link or pointer to the accounts settings, now I need to select "Add an account" from the drop down. 3) Incidentally, removing accounts doesn't work, in the end I had to disable two (non-working) instances of Google account configurations. Shotwell version 0.13.0-0ubuntu3, on Ubuntu 12.10, 64bit. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1080591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811225] Re: Mesa 18.2.8 stable release
** Description changed: [Impact] Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point release of the series. This will also be backported to 18.04 as part of the HWE stack update. + + Upstream changes: + + 18.2.3 + - Different patches for the DirectX9 and DRI state trackers. + - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky. + - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in + Radeonsi. + - State Trackers also get different fixes and corrections. + - Finally, fixes for GLSL and NIR are also in this queue. + + 18.2.4 + - Different fixes for different drivers: freedreno, radeonsi, swr, anv and radv. + - Also there are fixes for ac, gallium, spirv and blorp. + + 18.2.5 + - A patch for nine state tracker that fixes several crashes using nine's + thread_submit feature. There are other patches to other state trackers. + - A couple of patches for Meson build system, as well as for autotools. + - In the drivers side, there are a couple of fixes for RADV, one regarding + subgroups and another regarding conditional rendering. There are also fixes for virgl, r600, and i965. + - Finally, the queue contains a couple of fixes for NIR, Wayland, and other + components. + + 18.2.6 + - Several patches fixing leaks in glsl, winsys and r600. + - Improvements in the scripts that helps in preparing releases. + - Added PCI IDs for Amber Lake and Whiskey Lake. + - Fixes for radv, anv, i965 and vc4 drivers. + - A couple of fixes in NIR backend. + - Finally, several fixes in meson build system. + + 18.2.7 + - Several patches fixing leaks in glsl, winsys and r600. + - Improvements in the scripts that helps in preparing releases. + - Added PCI IDs for Amber Lake and Whiskey Lake. + - Fixes for radv, anv, i965 and vc4 drivers. + - A couple of fixes in NIR backend. + - Finally, several fixes in meson build system. + + 18.2.8 + - Several fixes in Meson build system. + - Also several fixes for st/nine subcomponent. + - Patch for RADV driver that fixes a hang in Yakuza using DXVK. + - There are also fixes for Virgl driver. + - Added PCI IDs for VegaM, Vega20 and Vega10. + [Test Case] Check on intel/radeon hw that things still work fine. [Regression potential] Mesa stable releases are tested by vendor CI systems, this is the last of the series so should be safe to update to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1811225 Title: Mesa 18.2.8 stable release Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: New Status in mesa source package in Cosmic: New Bug description: [Impact] Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point release of the series. This will also be backported to 18.04 as part of the HWE stack update. Upstream changes: 18.2.3 - Different patches for the DirectX9 and DRI state trackers. - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky. - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in Radeonsi. - State Trackers also get different fixes and corrections. - Finally, fixes for GLSL and NIR are also in this queue. 18.2.4 - Different fixes for different drivers: freedreno, radeonsi, swr, anv and radv. - Also there are fixes for ac, gallium, spirv and blorp. 18.2.5 - A patch for nine state tracker that fixes several crashes using nine's thread_submit feature. There are other patches to other state trackers. - A couple of patches for Meson build system, as well as for autotools. - In the drivers side, there are a couple of fixes for RADV, one regarding subgroups and another regarding conditional rendering. There are also fixes for virgl, r600, and i965. - Finally, the queue contains a couple of fixes for NIR, Wayland, and other components. 18.2.6 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.7 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.8 - Several fixes in Meson build system. - Also
[Touch-packages] [Bug 1537753] Re: ucf --purge reaches code where basename doesn't have a parameter
Closing as all other bug tasks showing "Fix Released"
** Changed in: hundredpapercuts
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ucf in Ubuntu.
https://bugs.launchpad.net/bugs/1537753
Title:
ucf --purge reaches code where basename doesn't have a parameter
Status in One Hundred Papercuts:
Fix Released
Status in ucf package in Ubuntu:
Fix Released
Status in ucf package in Debian:
Fix Released
Bug description:
When I was clearing up unpurged packages, grub-pc was not being purged
because of an error "basename: missing operand". Looked at the code and "ucf
--purge /etc/default/grub" was bailing out at line 472, which has the code:
old_mdsum_file="$source_dir/$(basename ${new_file}).md5sum";
Looking at ${new_file} at the code above, sure enough, it wasn't being
initialized at purge (line numbers 349 - 374). So I changed the else to test
if $new_file was there and I was able to purge grub-pc.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ucf 3.0032 [modified: usr/bin/ucf]
ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
Uname: Linux 4.3.0-6-generic x86_64
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jan 25 21:08:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-28 (118 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: ucf
UpgradeStatus: Upgraded to xenial on 2016-01-06 (18 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1537753/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1276672] Re: print_tree() fails with StateNotFoundError
Closing as all other bug tasks showing "Fix Released" ** Changed in: hundredpapercuts Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1276672 Title: print_tree() fails with StateNotFoundError Status in Autopilot: Fix Released Status in One Hundred Papercuts: Fix Released Status in autopilot package in Ubuntu: Fix Released Bug description: Dumping widget tree of complex applications with print_tree() fails with StateNotFoundError I pushed an example to lp:~jibel/+junk/sdk_tests pull the branch and run: $ autopilot run sdk_tests ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-autopilot 1.4+14.04.20140123.1-0ubuntu1 [modified: usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py] ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 5 10:57:15 2014 InstallationDate: Installed on 2013-09-03 (154 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) PackageArchitecture: all SourcePackage: autopilot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot/+bug/1276672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811225] [NEW] Mesa 18.2.8 stable release
Public bug reported: [Impact] Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point release of the series. This will also be backported to 18.04 as part of the HWE stack update. [Test Case] Check on intel/radeon hw that things still work fine. [Regression potential] Mesa stable releases are tested by vendor CI systems, this is the last of the series so should be safe to update to. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1811225 Title: Mesa 18.2.8 stable release Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: New Status in mesa source package in Cosmic: New Bug description: [Impact] Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point release of the series. This will also be backported to 18.04 as part of the HWE stack update. [Test Case] Check on intel/radeon hw that things still work fine. [Regression potential] Mesa stable releases are tested by vendor CI systems, this is the last of the series so should be safe to update to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1811225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805978] Re: ubuntu_lxc test is failed with lxc-utils package not installed
Didn't see this issue this cycle for the Bionic OEM kernel testing. Probably it's because all these packages have been released. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1805978 Title: ubuntu_lxc test is failed with lxc-utils package not installed Status in ubuntu-kernel-tests: Fix Released Status in lxc package in Ubuntu: Invalid Bug description: On Bionic since Nov.29, the ubuntu_lxc test is failing with: Running 'apt-get install --yes automake autopkgtest build-essential cloud-image-utils dh-autoreconf lxc texinfo gcc-multilib liblxc1' [stdout] Reading package lists... [stdout] Building dependency tree... [stdout] Reading state information... [stdout] liblxc1 is already the newest version (3.0.3-0ubuntu1~18.04.1). [stdout] Some packages could not be installed. This may mean that you have [stdout] requested an impossible situation or if you are using the unstable [stdout] distribution that some required packages have not yet been created [stdout] or been moved out of Incoming. [stdout] The following information may help to resolve the situation: [stdout] [stdout] The following packages have unmet dependencies: [stdout] lxc : Depends: lxc-utils (>= 3.0.2-0ubuntu1~18.04.1) but it is not going to be installed [stderr] E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1805978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 144276] Re: file chooser: cannot copy, cut, paste, drag, rename, delete
Upstream bug showing "RESOLVED FIXED" on 2015-07-05 Checked ok in Ubuntu 18.04 Marking "Fix Released" to close ** Changed in: hundredpapercuts Status: Confirmed => Fix Released ** Changed in: gtk+2.0 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/144276 Title: file chooser: cannot copy, cut, paste, drag, rename, delete Status in GTK+: Fix Released Status in One Hundred Papercuts: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Bug description: gtk2.0 2.12.0-1ubuntu1 some really important features are missing in the gtk filechooser. These are the use case: Mr. X is saving/opening a file and this might happen: 1) he needs to rename an existing file because he wants to save the new file with the same name, but does not want to loose the old file (SAVE ONLY) 2) he sees a file, in the current view, that is no more needed, and he wants to delete it 3) he sees a spelling mistake in a filename/dirname 4) he wants to create a directory to save the new file, but he gives the wrong name to it, and wants to rename it (SAVE ONLY) 5) he sees a file that is not in the correct directory 6) he creates a new directory to rearrange the current dir, because he has lots of files that can be grouped now if this happesn, Mr X has to open nautilus to do all these things. This is in my opinion not acceptable. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/144276/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764106] Re: ca-certificates fails on update in Bionic
** Package changed: ca-certificates (Ubuntu) => mono (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1764106 Title: ca-certificates fails on update in Bionic Status in mono package in Ubuntu: Confirmed Bug description: Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Updating Mono key store /etc/ca-certificates/update.d/mono-keystore: 10: /etc/ca-certificates/update.d/mono-keystore: /usr/bin/cert-sync: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1764106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 956855] Re: GtkFileChooserButton dialog stretched, when user has a really long name saved to bookmark
Closing as all other bug tasks showing "Fix Released" ** Changed in: hundredpapercuts Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/956855 Title: GtkFileChooserButton dialog stretched, when user has a really long name saved to bookmark Status in GTK+: Fix Released Status in One Hundred Papercuts: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Precise: Fix Released Status in gtk+3.0 source package in Saucy: Fix Released Bug description: [Impact] * file chooser dialog is stretched excessively. [Test Case] 1. Add the long bookmark to gtk places $ echo "file:///home/ritesh a really real long bookmark with long name">> ~/.gtk-bookmarks 2. log out and log in 3. Click on PrintScrn, or run testfilechooserbutton from test suite Stretched out dialog [Regression Potential] * n/a [Other Info] * Upstream commit - https://git.gnome.org/browse/gtk+/commit/?id=3923ba160594ad5e6c83f861cd5aeaba5e58129c To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/956855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764106] Re: ca-certificates fails on update in Bionic
Same happened on Xenial (16.04) with hw enablement. update-initramfs: Generating /boot/initrd.img-4.15.0-43-generic Processing triggers for ca-certificates (20170717~16.04.2) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Updating Mono key store /etc/ca-certificates/update.d/mono-keystore: 10: /etc/ca-certificates/update.d/mono-keystore: /usr/bin/cert-sync: not found Done done. Processing triggers for libc-bin (2.23-0ubuntu10) ... ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1764106 Title: ca-certificates fails on update in Bionic Status in ca-certificates package in Ubuntu: Confirmed Bug description: Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Updating Mono key store /etc/ca-certificates/update.d/mono-keystore: 10: /etc/ca-certificates/update.d/mono-keystore: /usr/bin/cert-sync: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1764106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811210] [NEW] intramfs-tools 0.130ubuntu3.3 in bionic-security breaks netplan.io in -security or in release
Public bug reported: Adding Breaks: netplan.io (<< 0.36.2) made initramfs-tools uninstallable by default unattended-upgrades configuration because netplan.io >= 0.36.2 is not available from bionic or bionic-security (only in bionic- updates). This is originally reported as https://github.com/mvo5/unattended- upgrades/issues/165 . U-u's email reporting behaviour is a valid different question, but IMO when such Break is added in -security a non-breaking version of the other package should be added to -security, too, like when we add new dependencies. Please provide a netplan.io version in -security that allows upgrade of initramfs-tools either by uploading 0.36.2 or just cherry-picking the needed fixes and relaxing the Breaks: in initramfs-tools. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Bionic) Importance: High Status: New ** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Bionic) Importance: Undecided => High -- 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/1811210 Title: intramfs-tools 0.130ubuntu3.3 in bionic-security breaks netplan.io in -security or in release Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Bug description: Adding Breaks: netplan.io (<< 0.36.2) made initramfs-tools uninstallable by default unattended-upgrades configuration because netplan.io >= 0.36.2 is not available from bionic or bionic-security (only in bionic-updates). This is originally reported as https://github.com/mvo5/unattended- upgrades/issues/165 . U-u's email reporting behaviour is a valid different question, but IMO when such Break is added in -security a non-breaking version of the other package should be added to -security, too, like when we add new dependencies. Please provide a netplan.io version in -security that allows upgrade of initramfs-tools either by uploading 0.36.2 or just cherry-picking the needed fixes and relaxing the Breaks: in initramfs-tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1811210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807709] Re: dbus always crashes at session start (on wayland)
And the journalctl log ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1807709/+attachment/5228208/+files/journalctl.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1807709 Title: dbus always crashes at session start (on wayland) Status in dbus package in Ubuntu: Incomplete Bug description: When you login in ubuntu 18.10 using gnome shell and wayland, dbus always crashes and you are welcomed with a dialog to report the crash. Looking into the file `/var/crash/_usr_bin_dbus-daemon.1000.crash` one can see that there is antoher bug, previoulsy reported as #1591548 (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1591548) So may be the bug report is never sent, either ? /var/crash/_usr_bin_dbus-daemon.1000.crash content is: ProblemType: Crash Architecture: amd64 Date: Sun Dec 9 11:16:22 2018 DistroRelease: Ubuntu 18.10 ExecutablePath: /usr/bin/dbus-daemon ExecutableTimestamp: 1536206167 ProcCmdline: /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only ProcCwd: /home/solstice ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcMaps: 55c9bfc7a000-55c9bfc83000 r--p 08:07 787824 /usr/bin/dbus-daemon 55c9bfc83000-55c9bfca5000 r-xp 9000 08:07 787824 /usr/bin/dbus-daemon 55c9bfca5000-55c9bfcb3000 r--p 0002b000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb3000-55c9bfcb5000 r--p 00038000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb5000-55c9bfcb6000 rw-p 0003a000 08:07 787824 /usr/bin/dbus-daemon 55c9c1bd8000-55c9c1f1e000 rw-p 00:00 0 [heap] 7eff0278c000-7eff02792000 r--p 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff02792000-7eff027bd000 r-xp 6000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027bd000-7eff027cc000 r--p 00031000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cc000-7eff027cf000 r--p 0003f000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cf000-7eff027d rw-p 00042000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027d-7eff027d1000 rw-p 00:00 0 7eff027d1000-7eff027d4000 r--p 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027d4000-7eff027db000 r-xp 3000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027db000-7eff027de000 r--p a000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027de000-7eff027df000 r--p c000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027df000-7eff027e rw-p d000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027e-7eff027e6000 rw-p 00:00 0 7eff027e6000-7eff027ea000 r--p 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ea000-7eff027f8000 r-xp 4000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027f8000-7eff027fd000 r--p 00012000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fd000-7eff027fe000 r--p 00016000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fe000-7eff027ff000 rw-p 00017000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ff000-7eff02801000 rw-p 00:00 0 7eff02801000-7eff02803000 r--p 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff02803000-7eff0280b000 r-xp 2000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280b000-7eff0280d000 r--p a000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280d000-7eff0280e000 r--p b000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280e000-7eff0280f000 rw-p c000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280f000-7eff02811000 r--p 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02811000-7eff02817000 r-xp 2000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02817000-7eff02818000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02818000-7eff02819000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02819000-7eff0281a000 rw-p 9000 08:07 654767
[Touch-packages] [Bug 1807709] Re: dbus always crashes at session start (on wayland)
I believe I have the same issue ** Attachment added: "_usr_bin_dbus-daemon.1000.crash" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1807709/+attachment/5228207/+files/_usr_bin_dbus-daemon.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1807709 Title: dbus always crashes at session start (on wayland) Status in dbus package in Ubuntu: Incomplete Bug description: When you login in ubuntu 18.10 using gnome shell and wayland, dbus always crashes and you are welcomed with a dialog to report the crash. Looking into the file `/var/crash/_usr_bin_dbus-daemon.1000.crash` one can see that there is antoher bug, previoulsy reported as #1591548 (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1591548) So may be the bug report is never sent, either ? /var/crash/_usr_bin_dbus-daemon.1000.crash content is: ProblemType: Crash Architecture: amd64 Date: Sun Dec 9 11:16:22 2018 DistroRelease: Ubuntu 18.10 ExecutablePath: /usr/bin/dbus-daemon ExecutableTimestamp: 1536206167 ProcCmdline: /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only ProcCwd: /home/solstice ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcMaps: 55c9bfc7a000-55c9bfc83000 r--p 08:07 787824 /usr/bin/dbus-daemon 55c9bfc83000-55c9bfca5000 r-xp 9000 08:07 787824 /usr/bin/dbus-daemon 55c9bfca5000-55c9bfcb3000 r--p 0002b000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb3000-55c9bfcb5000 r--p 00038000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb5000-55c9bfcb6000 rw-p 0003a000 08:07 787824 /usr/bin/dbus-daemon 55c9c1bd8000-55c9c1f1e000 rw-p 00:00 0 [heap] 7eff0278c000-7eff02792000 r--p 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff02792000-7eff027bd000 r-xp 6000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027bd000-7eff027cc000 r--p 00031000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cc000-7eff027cf000 r--p 0003f000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cf000-7eff027d rw-p 00042000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027d-7eff027d1000 rw-p 00:00 0 7eff027d1000-7eff027d4000 r--p 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027d4000-7eff027db000 r-xp 3000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027db000-7eff027de000 r--p a000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027de000-7eff027df000 r--p c000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027df000-7eff027e rw-p d000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027e-7eff027e6000 rw-p 00:00 0 7eff027e6000-7eff027ea000 r--p 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ea000-7eff027f8000 r-xp 4000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027f8000-7eff027fd000 r--p 00012000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fd000-7eff027fe000 r--p 00016000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fe000-7eff027ff000 rw-p 00017000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ff000-7eff02801000 rw-p 00:00 0 7eff02801000-7eff02803000 r--p 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff02803000-7eff0280b000 r-xp 2000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280b000-7eff0280d000 r--p a000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280d000-7eff0280e000 r--p b000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280e000-7eff0280f000 rw-p c000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280f000-7eff02811000 r--p 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02811000-7eff02817000 r-xp 2000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02817000-7eff02818000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02818000-7eff02819000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so
[Touch-packages] [Bug 1767731] Re: Bluetooth is not working. I cannot even switch bluetooth on in the configuration panel.
*** This bug is a duplicate of bug 1542743 *** https://bugs.launchpad.net/bugs/1542743 ** This bug is no longer a duplicate of bug 1475639 Atheros QCA9565 bluetooth hardware not detected ** This bug has been marked a duplicate of bug 1542743 Bluetooth (Atheros AR3012) does not work -- 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/1767731 Title: Bluetooth is not working. I cannot even switch bluetooth on in the configuration panel. Status in bluez package in Ubuntu: New Bug description: When switching on the bluetooth service it should be available but i cannot even turn it on. 01:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) Subsystem: Samsung Electronics Co Ltd QCA9565 / AR9565 Wireless Network Adapter Kernel driver in use: ath9k Kernel modules: ath9k 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 05) Subsystem: Samsung Electronics Co Ltd RTL810xE PCI Express Fast Ethernet controller Kernel driver in use: r8169 Kernel modules: r8169 lsusb -v | grep -E 'Bluetooth' Couldn't open device, some information will be missing Couldn't open device, some information will be missing Couldn't open device, some information will be missing Couldn't open device, some information will be missing Couldn't open device, some information will be missing Couldn't open device, some information will be missing Bus 002 Device 002: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 bDeviceProtocol 1 Bluetooth idProduct 0x3004 AR3012 Bluetooth 4.0 Couldn't open device, some information will be missing bFunctionProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth $ sudo rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 19:13:25 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bnep btusb bluetooth MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=29635d8f-d4c4-4efe-bc52-2365908a80eb ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RCX.075.160311.JJ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP370E4K-KW2BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8663A03-C01-G001-S0001+10.0.10586 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW2BR:rvrSGL8663A03-C01-G001-S0001+10.0.10586:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 370E4K dmi.product.version: P06RCX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:0 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767731/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
