[Touch-packages] [Bug 1219898] Re: zeitgeist_event_constructv_full declaration makes impossible to compile with -Wunused-function
** Changed in: vala (Ubuntu) Status: Confirmed => Fix Released ** Changed in: zeitgeist (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1219898 Title: zeitgeist_event_constructv_full declaration makes impossible to compile with -Wunused-function Status in Vala: New Status in Zeitgeist Framework: Unknown Status in vala package in Ubuntu: Fix Released Status in zeitgeist package in Ubuntu: Fix Released Bug description: The declaration of zeitgeist_event_constructv_full into zeitgeist- datamodel.h is static and this leads to a warning that makes impossible to compile with -Wunused-function. This seems mostly a Vala issue (maybe lead by https://bugzilla.gnome.org/show_bug.cgi?id=620675 ?), but the library should avoid to expose static symbols in a public header anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/vala/+bug/1219898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824876] Re: /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended-upgrade@2256:main:run:mark_pkgs_to_upgrade:mark_upgrade_adjusted:call_adjusted
The error is is falsely reported against the fixed version, too, with a stack trace from the unfixed version. This happens when reporting a crash occurred before upgrading the package. The error report is generated listing the upgraded package's version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824876 Title: /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended- upgrade@2256:main:run:mark_pkgs_to_upgrade:mark_upgrade_adjusted:call_adjusted Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.10ubuntu3, the problem page at https://errors.ubuntu.com/problem/dbb18e4c8f3777ec91c18aefd3a429f661227655 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1824876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist
@Khairul Please try passing "psmouse.synaptics_intertouch=0" in kernel parameter. If it works, I will send a patch to mainline kernel. Thanks, Aaron -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: In Progress Status in OEM Priority Project: New Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Xenial: In Progress Status in kmod source package in Bionic: In Progress Status in kmod source package in Cosmic: In Progress Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804478] Re: netplan dhcp interface with no default route causes systemd-networkd-wait-online to hang
** Project changed: systemd => ubuntu-translations ** Changed in: ubuntu-translations Importance: Unknown => Undecided ** Changed in: ubuntu-translations Status: Unknown => New ** Changed in: ubuntu-translations Remote watch: github.com/systemd/systemd/issues #3752 => None ** No longer affects: ubuntu-translations ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium ** Bug watch removed: github.com/systemd/systemd/issues #3752 https://github.com/systemd/systemd/issues/3752 -- 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/1804478 Title: netplan dhcp interface with no default route causes systemd-networkd- wait-online to hang Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] systemd-networkd, when configured to use ipv4 dhcp for an interface can hang. This triggers in two known cases: a) if configured to ignore the dhcp server's route b) the server provides no route Then systemd-networkd will hang waiting for the interface's configuration to complete (until it times out). This delays boot as well as any restart to systemd-networkd. The fix is backporting upstream commit [1] [1]: https://github.com/systemd/systemd/commit/223932c7 [test case] There are two ways to test this. A) make the system ignore Routes (slightly less realistic but easier to test) configure an interface using systemd-networkd: $ cat /etc/systemd/network/20-ens7.network [Match] Name=ens7 [Network] DHCP=ipv4 [DHCP] UseRoutes=false then reboot, and check: $ systemctl status systemd-networkd-wait-online ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-04-08 23:59:26 UTC; 2min 59s ago [...] Apr 08 23:57:27 lp1804478 systemd[1]: Starting Wait for Network to be Configured... Apr 08 23:57:30 lp1804478 systemd-networkd-wait-online[593]: managing: ens3 Apr 08 23:57:30 lp1804478 systemd-networkd-wait-online[593]: ignoring: lo Apr 08 23:59:26 lp1804478 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Apr 08 23:59:26 lp1804478 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Apr 08 23:59:26 lp1804478 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Apr 08 23:59:26 lp1804478 systemd[1]: Failed to start Wait for Network to be Configured. B) Make a dhcp server to not provide rules Prepare a Ubuntu Bionic Guest under libvirt, e.g. using uvtool: $ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic arch=amd64 release=bionic label=daily Create a isolated network: $ cat > isolate.xml << EOF isolated EOF $ virsh net-define isolate.xml $ virsh net-start isolated Edit the guest and add that network: $ virsh shutdown bionic $ virsh edit bionic #add this: In the guest make the device use DHCP: Add this to /etc/netplan/50-cloud-init.yaml ens7: dhcp4: true match: macaddress: 52:54:00:c1:69:08 set-name: ens7 $ sudo netplan apply When rebooting the guest again it will fail ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-04-09 07:07:48 UTC; 1min 41s ago Docs: man:systemd-networkd-wait-online.service(8) Process: 563 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=1/FAILURE) Main PID: 563 (code=exited, status=1/FAILURE) Apr 09 07:05:48 bionic-dgx2 systemd[1]: Starting Wait for Network to be Configured... Apr 09 07:05:50 bionic-dgx2 systemd-networkd-wait-online[563]: managing: ens3 Apr 09 07:07:48 bionic-dgx2 systemd-networkd-wait-online[563]: Event loop failed: Connection timed out Apr 09 07:07:48 bionic-dgx2 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Apr 09 07:07:48 bionic-dgx2 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Apr 09 07:07:48 bionic-dgx2 systemd[1]: Failed to start Wait for Network to be Configured. When working cases A and B will both have the service starting fast and happy. $ sudo systemctl status systemd-networkd-wait-online Active: active (exited) since Tue
[Touch-packages] [Bug 1804478] Re: netplan dhcp interface with no default route causes systemd-networkd-wait-online to hang
** Changed in: systemd Importance: Undecided => Unknown ** Changed in: systemd Status: Fix Released => Unknown ** Changed in: systemd Remote watch: None => github.com/systemd/systemd/issues #3752 -- 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/1804478 Title: netplan dhcp interface with no default route causes systemd-networkd- wait-online to hang Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] systemd-networkd, when configured to use ipv4 dhcp for an interface can hang. This triggers in two known cases: a) if configured to ignore the dhcp server's route b) the server provides no route Then systemd-networkd will hang waiting for the interface's configuration to complete (until it times out). This delays boot as well as any restart to systemd-networkd. The fix is backporting upstream commit [1] [1]: https://github.com/systemd/systemd/commit/223932c7 [test case] There are two ways to test this. A) make the system ignore Routes (slightly less realistic but easier to test) configure an interface using systemd-networkd: $ cat /etc/systemd/network/20-ens7.network [Match] Name=ens7 [Network] DHCP=ipv4 [DHCP] UseRoutes=false then reboot, and check: $ systemctl status systemd-networkd-wait-online ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-04-08 23:59:26 UTC; 2min 59s ago [...] Apr 08 23:57:27 lp1804478 systemd[1]: Starting Wait for Network to be Configured... Apr 08 23:57:30 lp1804478 systemd-networkd-wait-online[593]: managing: ens3 Apr 08 23:57:30 lp1804478 systemd-networkd-wait-online[593]: ignoring: lo Apr 08 23:59:26 lp1804478 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Apr 08 23:59:26 lp1804478 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Apr 08 23:59:26 lp1804478 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Apr 08 23:59:26 lp1804478 systemd[1]: Failed to start Wait for Network to be Configured. B) Make a dhcp server to not provide rules Prepare a Ubuntu Bionic Guest under libvirt, e.g. using uvtool: $ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic arch=amd64 release=bionic label=daily Create a isolated network: $ cat > isolate.xml << EOF isolated EOF $ virsh net-define isolate.xml $ virsh net-start isolated Edit the guest and add that network: $ virsh shutdown bionic $ virsh edit bionic #add this: In the guest make the device use DHCP: Add this to /etc/netplan/50-cloud-init.yaml ens7: dhcp4: true match: macaddress: 52:54:00:c1:69:08 set-name: ens7 $ sudo netplan apply When rebooting the guest again it will fail ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-04-09 07:07:48 UTC; 1min 41s ago Docs: man:systemd-networkd-wait-online.service(8) Process: 563 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=1/FAILURE) Main PID: 563 (code=exited, status=1/FAILURE) Apr 09 07:05:48 bionic-dgx2 systemd[1]: Starting Wait for Network to be Configured... Apr 09 07:05:50 bionic-dgx2 systemd-networkd-wait-online[563]: managing: ens3 Apr 09 07:07:48 bionic-dgx2 systemd-networkd-wait-online[563]: Event loop failed: Connection timed out Apr 09 07:07:48 bionic-dgx2 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Apr 09 07:07:48 bionic-dgx2 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Apr 09 07:07:48 bionic-dgx2 systemd[1]: Failed to start Wait for Network to be Configured. When working cases A and B will both have the service starting fast and happy. $ sudo systemctl status systemd-networkd-wait-online Active: active (exited) since Tue 2019-04-09 07:17:16 UTC; 12s ago [...] Apr 09 07:17:16 bionic-dgx2 systemd-networkd-wait-online[575]: managing: ens3 [...] Apr 09 07:17:16 bionic-dgx2 systemd-networkd-wait-online[575]: managing: ens7 [regression potential] this alters how systemd-networkd works when it starts or restarts,
[Touch-packages] [Bug 1747460] Re: [MIR] py-macaroon-bakery, protobuf, pyrfc3339
** No longer affects: protobuf (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1747460 Title: [MIR] py-macaroon-bakery, protobuf, pyrfc3339 Status in py-macaroon-bakery package in Ubuntu: Fix Released Status in pyrfc3339 package in Ubuntu: Fix Released Status in python-nacl package in Ubuntu: Fix Released Bug description: py-macaroon-bakery == 1. Availability: all 2. Rationale: Macaroons is a new form of authorization mechanism. The macaroon bakery builds on pymacaroons, which allows it working at a higher level. In order for MAAS (and other projects) to support macaroon based authentication, this needs to be in main. This will allow projects to support remote/centralized authentication based on macaroons. 3. Security: No CVE's 4. QA: 0 bugs in debian/ubuntu 5. UI standards: None 6. Dependencies: Dependencies in universe: - python3-pymacaroons (MIR LP: #1746772) - python3-nacl - python3-protobuf - python3-rfc3339 7. Standards: No lintian errors. Packaged with debhelper. Source format is 3.0 (quilt) Standards version: 4.4.1 8. Maintenance: Easy. 9. Background information: This is a required dependency to implement third party/centralized authentication alongside with pymacaroons. This is a new dependency that's required by MAAS. python3-protobuf == 1. Availability: any 2. Rationale: Dependency of python3-macaroonbakery. The library from this same source package, libprotobuf10, is already in main. 3. Security: No CVE's 4. QA: protobuf source, 10 bugs in debian, 11 ubuntu 5. UI standards: None 6. Dependencies: All in main 7. Standards: No lintian errors. Packaged with debhelper. Source format is 3.0 (quilt) Standards version: 3.9.8 8. Maintenance: Easy. 9. Background information: protobuf source already has binaries in main. This is just the python bindings that are required by macaroonbakery. rfc3339 == 1. Availability: all 2. Rationale: Dependency of python3-macaroonbakery. 3. Security: No CVE's 4. QA: 0 bugs in debian/ubuntu 5. UI standards: None 6. Dependencies: All in main 7. Standards: No lintian errors. 1 warning: W: pyrfc3339 source: ancient-standards-version 3.9.6 (released 2014-09-17) (current is 4.1.3) Packaged with debhelper. Source format is 3.0 (quilt) 8. Maintenance: Easy. 9. Background information: Parser and generator of RFC 3339-compliant timestamps. This is a dependency for python3-macaroonbakery. python-nacl == 1. Availability: any 2. Rationale: Dependency of python3-macaroonbakery. 3. Security: No CVE's 4. QA: 0 bugs in debian/ubuntu 5. UI standards: None 6. Dependencies: All in main 7. Standards: No lintian errors. Uses standards version 3.9.8 Packaged with debhelper. Source format is 3.0 (quilt) 8. Maintenance: Easy. 9. Background information: PyNaCl is a Python binding to the Networking and Cryptography library. This is a dependency for python3-macaroonbakery. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/py-macaroon-bakery/+bug/1747460/+subscriptions -- Mailing list: https://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 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
Sorry, which faulty units are those? -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 16 Apr 2019, Sebastien Bacher wrote: > Date: Tue, 16 Apr 2019 14:23:23 - > From: Sebastien Bacher > Reply-To: Bug 1824893 <1824...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target > Reboot but then does not reboot > > Thanks, I don't see anything obvious in the log, setting as New again > for now (would be good to see if removing the faulty units pointed in > the previous comment makes a difference though) > > ** Changed in: systemd (Ubuntu) > Status: Incomplete => New > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824893 > > Title: > When I type systemctl reboot system reaches Target Reboot but then > does not reboot > > Status in systemd package in Ubuntu: > New > > Bug description: > This is similar to the bug where systemd used to get stuck in target > Shutdown except that bug affected all my hardware, now it gets stuck > at target Reboot but this only affects my elderly Mac Pro 1,1 and does > not affect my laptop or i7-6700k and i7-6850k based servers. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5 > ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 > Uname: Linux 5.0.0-8-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: MATE > Date: Mon Apr 15 16:30:34 2019 > InstallationDate: Installed on 2018-12-06 (130 days ago) > InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > MachineType: Apple Computer, Inc. MacPro2,1 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency > root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 > SourcePackage: systemd > SystemdDelta: > [EXTENDED] /lib/systemd/system/ondemand.service ÿÿ > /lib/systemd/system/ondemand.service.d/ubuntustudio.conf > [EXTENDED] /lib/systemd/system/rc-local.service ÿÿ > /lib/systemd/system/rc-local.service.d/debian.conf > [EXTENDED] /lib/systemd/system/user@.service ÿÿ > /lib/systemd/system/user@.service.d/timeout.conf > > 3 overridden configuration files found. > UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions > -- 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/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: New Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service →
[Touch-packages] [Bug 1824661] Re: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty.
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1824661 Title: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty. Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in slick-greeter package in Ubuntu: Incomplete Bug description: Hello. I am having issues consistently with this laptop and the Nvidia drivers in 19.04. I have tested this on Ubuntu, Kubuntu, Ubuntu Budgie, and Ubuntu MATE. This is with both the recommended 418 driver as well as 390. Today I tried installing the latest daily of Ubuntu MATE with the proprietary driver option on my Dell XPS 15 9570 with Nvidia GP107M (GeForce GRX 1050 Time Mobile). Boots to blank screen that flashes a couple times. Can't get to tty. Reboot, editing grub to include nomodeset. Boots to underscore character in the top left. I can get tty at least. 418 driver is installed. Looking at logs but nothing seems obvious. If there's anything I can do to help with this please let me know. Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Sat Apr 13 18:27:12 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-11-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-04-13 (0 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) MachineType: Dell Inc. XPS 15 9570 ProcEnviron: TERM=cygwin PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic root=UUID=add8471d-1273-4547-aef3-4be006f9eb9c ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1824661/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824753] Re: When I pass the Qt application to the secondary monitor the characters of the application increase
Thanks. The problem continuing is somewhat good news. It means this isn't some new regression in mutter. ** Changed in: qtbase-opensource-src (Ubuntu) Status: Incomplete => New ** Changed in: vlc (Ubuntu) Status: Incomplete => New ** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1824753 Title: When I pass the Qt application to the secondary monitor the characters of the application increase Status in qtbase-opensource-src package in Ubuntu: New Status in vlc package in Ubuntu: New Bug description: Hi. I have recently installed Ubuntu 19.04 RC. Everything works fine except the Qt applications. I have two monitors and when I pass the Qt application to the secondary monitor the characters of the application increase. They happen to the traditionally installed Qt applications and to those installed with Flatpak and Snap. I leave you a video in which you can see the problem with the VLC application. https://youtu.be/tEZJONsinU4 https://i.imgur.com/R7GubxF.png?fb --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-14 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1824753/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823175] Re: Battery status shows "Estimating..." when fully charged
*** This bug is a duplicate of bug 1745032 *** https://bugs.launchpad.net/bugs/1745032 Oh, that complicates things... That means you were actually experiencing bug 1745032, which just got fixed in a upower update. The upstream bug mentioned here shouldn't be any more. ** Also affects: upower (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-shell ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: gnome-shell (Ubuntu Bionic) ** No longer affects: gnome-shell (Ubuntu Cosmic) ** No longer affects: gnome-shell (Ubuntu Disco) ** This bug has been marked a duplicate of bug 1745032 AC adapter status not detected on Asus ZenBook UX410UAK -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1823175 Title: Battery status shows "Estimating..." when fully charged Status in upower package in Ubuntu: New Status in upower source package in Bionic: New Status in upower source package in Cosmic: New Bug description: My battery is fully charged and it shows 100%. When it's connected to charger, Battery symbol changes to battery-missing-symbol. It also shows "Estimating..." for time remaining. I'm using "Asus VivoBook x510uf" My battery status when connected to AC power: $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC0 native-path: AC0 power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 40.367 Wh energy-empty:0 Wh energy-full: 40.367 Wh energy-full-design: 43.046 Wh energy-rate: 0 W voltage: 11.55 V percentage: 100% capacity:93.7764% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 15543934180.000 unknown History (rate): 15543934180.000 unknown Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no battery present: yes state: unknown warning-level: none energy: 40.367 Wh energy-full: 40.367 Wh energy-rate: 0 W percentage: 100% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.7 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep - ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 17:04:22 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-03-30 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1823175/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated)
** Summary changed: - lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 + lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated) Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1333024] Re: Bluetooth audio Underruns, dropouts or crackling sound
*** This bug is a duplicate of bug 405294 *** https://bugs.launchpad.net/bugs/405294 Hammad, Since you are using 18.10 you would have the fix for bug 405294. That means any remaining issues will be specific to your wifi/bluetooth hardware. Please open a new bug by running: ubuntu-bug bluez and I will assess it. --- Vancouverite, This bug is a duplicate of bug 405294 (unless proven otherwise like Hammad's). Unfortunately that's not fixed in 14.04. ** This bug has been marked a duplicate of bug 405294 A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] -- 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/1333024 Title: Bluetooth audio Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: Confirmed Bug description: My bluetooth performance when connected to an audio device is very poor on my Lenovo T440s. There are multiple problems when I connect to my logitech device: 1) It often disconnects unexpectedly. It will connect for 2-5 seconds before disconnecting. This happens over and over with no messages in dmesg. 2) If I can get it to connect, the audio device is listed in the sound settings only about 50% of the time. I have to disconnect, restart bluetooth (\etc\init.d\bluetooth restart) and try again. 3) If I can get it playing, the audio lags by ~10s and is really, really chopped up. Totally unintelligible. The things I know which might help: Computer Type: Lenovo T440s Operating system: Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty Linux version : 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Bluetooth card: Network controller: Intel Corporation Wireless 7260 (rev 83) Pulseaudio version: pulseaudio 4.0 - I don't think it's pulse audio as the daemon won't start: $ pulseaudio --check $ pulseaudio -D E: [pulseaudio] main.c: Daemon startup failed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seth 2220 F pulseaudio /dev/snd/controlC1: seth 2220 F pulseaudio /dev/snd/pcmC1D0c: seth 2220 F...m pulseaudio CurrentDesktop: Unity Date: Sun Jun 22 14:29:41 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-21 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: (EE)Logitech Adapter Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [(EE)Logitech Adapter, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET64WW (2.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ006HUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET64WW(2.14):bd11/12/2013:svnLENOVO:pn20AQ006HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ006HUS:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ006HUS dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1333024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
okay I have another solution to the timing issue .. add two partition mounts to fstab .. my existing sda1 disco install has /home (sda2) and /home/store1 (sda5) mounted via fstab .. this was the original install configuration .. thus always a mount delay .. to test .. added the same partions to mount on /home/oldhome and /home/store1 respectively on newly installed sda9 - disco xubuntu final and no crashes .. ..plymouth shows up .. xorg/lightdm start normally ..just enough delay to let everything else happen .. all using the "foreign sda1 installed grub" .. so all the errors are due to "faster than expected storage media response time" .. some slumbering boot timing issues waiting to cause trouble .. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
of course the sda1 partition (on the SSD) has never failed to work properly no matter which grub source (installs on sda1,sda6,sda7,sda8,sda9) is used plymouth always appears when sda1 boots.. this disco version was installed jan 10 with a bootstrap log date of oct 13, 2018 .. it has been updated regularly ever since .. daily from proposed .. without issues .. other partition installs through most of febuary tested about once per week not always reported .. appeared to have no issues .. so the question to be answered is what change in late february /early march could have influenced the timing of the boot sequence and the start of plymouth ? any ideas? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
[Touch-packages] [Bug 1509562] Re: no icons for menu, folders, directories, files
however, after setting fallback to oxygen, the xfwm4 is keeping to have SIGSEGV. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1509562 Title: no icons for menu, folders, directories, files Status in dolphin package in Ubuntu: Confirmed Status in kate package in Ubuntu: Confirmed Status in kdepim package in Ubuntu: Confirmed Status in konsole package in Ubuntu: Confirmed Status in kstars package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: no icons for menu, folders, directories, files I am using Xubuntu 15.10 as the Guest in Virtualbox 5.0.8 r103449. This happened after a recent Xubuntu update. Info: $ apt-cache policy dolphin dolphin: Installed: 4:15.08.2-0ubuntu1 Candidate: 4:15.08.2-0ubuntu1 Version table: *** 4:15.08.2-0ubuntu1 0 500 http://mirror.cogentco.com/pub/linux/ubuntu/ wily/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: dolphin 4:15.08.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 23 17:35:08 2015 InstallationDate: Installed on 2015-06-01 (144 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150521) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dolphin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1509562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509562] Re: no icons for menu, folders, directories, files
ah I get it, I forgot to install kde-config-gtk-style -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1509562 Title: no icons for menu, folders, directories, files Status in dolphin package in Ubuntu: Confirmed Status in kate package in Ubuntu: Confirmed Status in kdepim package in Ubuntu: Confirmed Status in konsole package in Ubuntu: Confirmed Status in kstars package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: no icons for menu, folders, directories, files I am using Xubuntu 15.10 as the Guest in Virtualbox 5.0.8 r103449. This happened after a recent Xubuntu update. Info: $ apt-cache policy dolphin dolphin: Installed: 4:15.08.2-0ubuntu1 Candidate: 4:15.08.2-0ubuntu1 Version table: *** 4:15.08.2-0ubuntu1 0 500 http://mirror.cogentco.com/pub/linux/ubuntu/ wily/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: dolphin 4:15.08.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 23 17:35:08 2015 InstallationDate: Installed on 2015-06-01 (144 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150521) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dolphin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1509562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
** Patch added: "fix for cosmic" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1778844/+attachment/5256423/+files/initramfs-tools_0.131ubuntu15.2.debdiff ** Changed in: initramfs-tools (Ubuntu Cosmic) Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: initramfs-tools (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- 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/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Cosmic: In Progress Status in initramfs-tools source package in Disco: Fix Released Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0
[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
** Patch added: "fix for bionic" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1778844/+attachment/5256424/+files/initramfs-tools_0.130ubuntu3.8.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Cosmic: In Progress Status in initramfs-tools source package in Disco: Fix Released Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568
[Touch-packages] [Bug 1509562] Re: no icons for menu, folders, directories, files
@Torbjörn Rathsman (milasudril) How did you did that. I installed qt5 -style-plugins oxygen-icon-theme and systemsettings. But the systemsettings5 give almost empty GUI. There is nothing to set, except the shortcut, network and proxy. I am in 18.04 ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1509562 Title: no icons for menu, folders, directories, files Status in dolphin package in Ubuntu: Confirmed Status in kate package in Ubuntu: Confirmed Status in kdepim package in Ubuntu: Confirmed Status in konsole package in Ubuntu: Confirmed Status in kstars package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: no icons for menu, folders, directories, files I am using Xubuntu 15.10 as the Guest in Virtualbox 5.0.8 r103449. This happened after a recent Xubuntu update. Info: $ apt-cache policy dolphin dolphin: Installed: 4:15.08.2-0ubuntu1 Candidate: 4:15.08.2-0ubuntu1 Version table: *** 4:15.08.2-0ubuntu1 0 500 http://mirror.cogentco.com/pub/linux/ubuntu/ wily/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: dolphin 4:15.08.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 23 17:35:08 2015 InstallationDate: Installed on 2015-06-01 (144 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150521) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dolphin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1509562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
okay turned back the clock .. to a spinning metal disk previously installed in this hardware .. ran a number of test installs all work fine .. cosmic/bionic/disco early version disco final all work boot normally .. always .. thus conclusion is a SSD is very fast and can respond to requests sooner than a spinning metal disk this throws off the timing of a number of boot processes .. which become out of sync.. due to the " slower processor " now the first boot into a fresh install is not effected as a very extended plymouth start occurs .. due to " automatic-updates?? or disk checks or something ?" the rest of the boots are too fast for even plymouth to load properly due to a not yet loaded kernel video module .. thus it only flashes the screen red briefly .. then xorg/lightdm crashes for the same reason(?).. delayed kernel module load .. then a second successful try if still booting from "native" grub ..else no retry and lock-up -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx:
[Touch-packages] [Bug 1774419] Re: easy_install command is missing
Work-around pip install --user setuptools then set $PATH to include ~/.local/bin ** Also affects: python-setuptools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896652 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1774419 Title: easy_install command is missing Status in python-setuptools package in Ubuntu: Confirmed Status in python-setuptools package in Debian: Unknown Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 Package: python-setuptools Version: 39.0.1-2 This package installs the easy_install module, but the command is missing: deploy@controller0:~$ which easy_install deploy@controller0:~$ echo $? 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1774419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
video of sda9 boot using sda9 install of grub (native grub) .. note absence of plymouth .. flash at top edge of screen was missed .. note brief appearance of lightdm .. short gap then lightdm reappears .. xorg.0.log.old records the crash .. similar to others above xorg.0.log records successful xorg/lightdm start .. ** Attachment added: "video of self boot w/ crash and restart" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5256387/+files/20190416_111702.mp4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Touch-packages] [Bug 1816530] Re: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04
Hi Dan, first of all thank you for your time!!! I added the "nameserver 8.8.8.8" line to the /etc/resolvconf/resolv.conf.d/head and it adds this line to the /etc/resolv.conf file I removed the 8.8.8.8 line, restarted the computer and I have internet. $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 29 Aug 4 2016 /etc/resolv.conf -> ../run/resolvconf/resolv.conf $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home $ systemd-resolve --status Global DNS Domain: home DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 5 (virbr0-nic) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 4 (virbr0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (wlp2s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (eno1) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 195.34.133.21 212.186.211.21 DNS Domain: home $ grep . /run/resolvconf/interface/* nameserver 127.0.0.53 search home $ SYSTEMD_LOG_LEVEL=debug systemd-resolve google.com Bus n/a: changing state UNSET → OPENING Bus n/a: changing state OPENING → AUTHENTICATING Resolving google.com (family *, interface *). Bus n/a: changing state AUTHENTICATING → HELLO Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.133 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a Bus n/a: changing state HELLO → RUNNING Sent message type=method_call sender=n/a destination=org.freedesktop.resolve1 path=/org/freedesktop/resolve1 interface=org.freedesktop.resolve1.Manager member=ResolveHostname cookie=2 reply_cookie=0 signature=isit error-name=n/a error-message=n/a Got message type=method_return sender=:1.1 destination=:1.133 path=n/a interface=n/a member=n/a cookie=15 reply_cookie=2 signature=a(iiay)st error-name=n/a error-message=n/a google.com: 172.217.21.110 -- Information acquired via protocol DNS in 13.3ms. -- Data is authenticated: no Bus n/a: changing state RUNNING → CLOSED it seems the problem is solved. The question is whether the patch/fix/change is included into that ISO file which is used for upgrading the older ubuntu releases to the 18.04? I had many updates the last year, but the origin of the problem was that I couldn't connect to the internet right after the upgrade and this way I couldn't update any packages or configuration.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1816530 Title: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04 Status in resolvconf package in Ubuntu: Incomplete Bug description: I upgraded my 16.04 to 18.04 before the official release. After the upgrade I noticed that I don't have internet access. The wired network and the wifi settings looked good, but the internet didn't work. After the login the system always switched itself into airplane mode. I tethered the network via USB and Bluetooth by my mobile but they also didn't work. I found a useful answer from @andrew-woodhead666:
[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
video of sda8 non-native grub boot (a disco-xubuntu iso install) sda9 has installed grub (also a disco-xubuntu iso install ) will show in next video uploaded note the red flash .. plymouth attempt to start .. then cursor appears and then lightdm briefly ** Attachment added: "video of failing boot -- with foreign grub" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5256380/+files/20190416_112248.mp4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1824688] Re: date+%-Y -d "- N years" errors when N > 111
re-assigning bug to glibc ** Package changed: coreutils (Ubuntu) => glibc (Ubuntu) ** Description changed: I have been using 'date +%-Y -d "- 2010 years" in a script for years but today after using the script after upgrading to disco it has failed. After some experimentation it succeeds with upto 111 years but fails from 112 onwards. Error given is: 'date: invalid date '- 112 years'. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: coreutils 8.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Sun Apr 14 10:59:36 2019 InstallationDate: Installed on 2017-10-08 (553 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: coreutils UpgradeStatus: Upgraded to disco on 2019-04-13 (1 days ago) + + BYPASS (probable, not confirmed in all possible scenarios): + + use TZ=UTC: + + export TZ=UTC, or env TZ=UTC program -- 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/1824688 Title: date+%-Y -d "- N years" errors when N > 111 Status in glibc package in Ubuntu: Confirmed Bug description: I have been using 'date +%-Y -d "- 2010 years" in a script for years but today after using the script after upgrading to disco it has failed. After some experimentation it succeeds with upto 111 years but fails from 112 onwards. Error given is: 'date: invalid date '- 112 years'. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: coreutils 8.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Sun Apr 14 10:59:36 2019 InstallationDate: Installed on 2017-10-08 (553 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: coreutils UpgradeStatus: Upgraded to disco on 2019-04-13 (1 days ago) BYPASS (probable, not confirmed in all possible scenarios): use TZ=UTC: export TZ=UTC, or env TZ=UTC program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1824688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824961] Re: AppArmor blocks apport python hook from working
"I guess the question is: Shouldn't we have a python-apport abstraction that apps (or local admin) can include to make debugging work under apparmor? It should probably live in apport, I guess, so apport can define which files it needs." Perhaps an abstraction makes sense to optionally add it in for debugging, but it is not clear what should be in that abstraction. I mean, if these things are running in process and the hooks can do anything, it might simply make sense to temporarily disable the profile while debugging via apparmor_parser -R /path/to/profile. Of course, that changes the environment of the application (but so does adding the abstraction). -- 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/1824961 Title: AppArmor blocks apport python hook from working Status in AppArmor: New Status in apparmor package in Ubuntu: New Status in kopanocore package in Ubuntu: New Bug description: The Python profile is very strict, but it prevents Python applications from producing proper crash reports using apport, as the apport hook cannot be loaded, as it requires access to dpkg's cputable, and likely also apt config files and dpkg status files. I'm wondering what the right approach here is: Should the apport hook work under AppArmor, and do we thus have to add the files the hook needs; or should we just say "screw it, we want the additional security" and not get proper error reporting while AppArmor is confining the program? This can be seen in recent autopkgtest failure for kopanocore: + kopano-search --help Traceback (most recent call last): File "/usr/sbin/kopano-search", line 4, in import kopano_search File "/usr/lib/python3/dist-packages/kopano_search/__init__.py", line 18, in from queue import Empty File "/usr/lib/python3.7/queue.py", line 16, in from _queue import Empty ImportError: /usr/lib/python3.7/lib-dynload/_queue.cpython-37m-x86_64-linux-gnu.so: failed to map segment from shared object Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 35, in apt_pkg.init_system() apt_pkg.Error: E:Error reading the CPU table To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1824961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824688] Re: date+%-Y -d "- N years" errors when N > 111
Trying on the current fedora 30 livecd they have the same issue -- 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/1824688 Title: date+%-Y -d "- N years" errors when N > 111 Status in coreutils package in Ubuntu: Confirmed Bug description: I have been using 'date +%-Y -d "- 2010 years" in a script for years but today after using the script after upgrading to disco it has failed. After some experimentation it succeeds with upto 111 years but fails from 112 onwards. Error given is: 'date: invalid date '- 112 years'. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: coreutils 8.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Sun Apr 14 10:59:36 2019 InstallationDate: Installed on 2017-10-08 (553 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: coreutils UpgradeStatus: Upgraded to disco on 2019-04-13 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1824688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815040] Re: [19.04 FEAT] Hardware support in tool chain - binutils part
** 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 binutils in Ubuntu. https://bugs.launchpad.net/bugs/1815040 Title: [19.04 FEAT] Hardware support in tool chain - binutils part Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: Function: Add new instruction support to binutils Business Case: Improved performance via enhanced instruction support in binutils Available with binutils 2.32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1815040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814765] Re: [19.04 FEAT] zone awareness for lsmem / chmem - util-linux
** 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 util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1814765 Title: [19.04 FEAT] zone awareness for lsmem / chmem - util-linux Status in Ubuntu on IBM z Systems: Fix Released Status in util-linux package in Ubuntu: Fix Released Bug description: Description: Kernel version 4.12 will change the default zone for hotplug memory to the zone-normal. To add memory to the zone movable "online_movable" needs to be echoed into the state attribute of a memory segment. Currently chmem always echos "online" to enable a memory segment. This feature adds an option to lsmem and chmem to distinguish between zone-movable and zone-normal. Business Case: Ensure memory hotplug with enhanced upstream functionality Available with util-linux 2.32. Due to integration of 2.33 already in 19.04, this feature is only for completness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1814765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824103] Re: aplay record file failed always.
This bug was fixed in the package pulseaudio - 1:12.2-2ubuntu3 --- pulseaudio (1:12.2-2ubuntu3) disco; urgency=medium * debian/pulseaudio.links: chmod +x so that dh-exec actually works. pulseaudio (1:12.2-2ubuntu2) disco; urgency=medium * Cherrypick changes from 12.2-3 to stop compiling with -ffast-math and to fix alsa/pulseaudio config file integration (LP: #1824103) -- Adam Conrad Tue, 16 Apr 2019 07:54:26 -0600 ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Fix Released -- 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/1824103 Title: aplay record file failed always. Status in pulseaudio package in Ubuntu: Fix Released Bug description: Test machine: ThinkPad X1 Carbon Image: Ubuntu Disco 19.04 CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, stepping: 0xa) GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) BIOS: N23ET55W (1.30 ) Steps: 1. Install image 19.04 2. Login as default user 3. Open a terminal and type "$ arecord abc.wav" 4. Say something and let laptop recorded your words 5. Cancel the record, please press 'Ctrl + C' 6. Please type "$ aplay abc.wav" in terminal Expected result: The voice played smoothly. Actual result: Step 3, u@u-ThinkPad-X1-Carbon-6th:~$ arecord abc.wav Recording WAVE 'abc.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono ^CAborted by signal Interrupt... arecord: pcm_read:2145: read error: Interrupted system call Step 6, u@u-ThinkPad-X1-Carbon-6th:~$ aplay abc.wav ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave aplay: main:828: audio open error: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1824103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
Launchpad has imported 3 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=110452.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2019-04-16T17:06:03+00:00 El jinete sin cabeza wrote:
Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1758287
"totem crashed with signal 5"
BackTrace:
#0 _g_log_abort (breakpoint=breakpoint@entry=1) at
../../../../glib/gmessages.c:583
debugger_present = 1
#1 0x7f07050f8571 in g_log_writer_default (log_level=6,
log_level@entry=G_LOG_LEVEL_ERROR, fields=fields@entry=0x7fff141276e0,
n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at
../../../../glib/gmessages.c:2735
__func__ = "g_log_writer_default"
#2 0x7f07050f67de in g_log_structured_array (log_level=G_LOG_LEVEL_ERROR,
fields=0x7fff141276e0, n_fields=6) at ../../../../glib/gmessages.c:1970
writer_func = 0x7f07050f8400
writer_user_data = 0x0
recursion = 0
depth =
n_fields = 6
log_level = G_LOG_LEVEL_ERROR
writer_user_data =
depth =
fields = 0x7fff141276e0
writer_func =
recursion =
_g_boolean_var_ =
writer_func =
writer_user_data =
recursion =
depth =
_g_boolean_var_ =
#3 0x7f07050f722e in g_log_structured_standard
(log_domain=log_domain@entry=0x7f070236b28e "Gdk",
log_level=log_level@entry=G_LOG_LEVEL_ERROR, file=file@entry=0x7f0702389a78
"../../../../../gdk/x11/gdkdisplay-x11.c", line=line@entry=0x7f07023894cf
"2766", func=func@entry=0x7f070238a190 <__func__.74387>
"_gdk_x11_display_error_event",
message_format=message_format@entry=0x7f070238a50b "%s") at
../../../../glib/gmessages.c:2027
fields = {{key = 0x7f0705142464 "PRIORITY", value = 0x7f07051422f9,
length = -1}, {key = 0x7f070514246d "CODE_FILE", value = 0x7f0702389a78, length
= -1}, {key = 0x7f0705142477 "CODE_LINE", value = 0x7f07023894cf, length = -1},
{key = 0x7f0705142481 "CODE_FUNC", value = 0x7f070238a190 <__func__.74387>,
length = -1}, {key = 0x7f0705142451 "MESSAGE", value = 0x56326c71ad30, length =
-1}, {key = 0x7f07051424be "GLIB_DOMAIN", value = 0x7f070236b28e, length = -1}}
n_fields =
message_allocated = 0x56326c71ad30 "The program 'totem' received an X
Window System error.\nThis probably reflects a bug in the program.\nThe error
was 'GLXBadContext'.\n (Details: serial 53257 error_code 169 request_code 155
(GLX) minor_"...
buffer = "vec2 UV)\n{\n
vec\377\377\377\377\000\000\000\000l_sample0\222\n\005\a\177\000\000\020\272\247\005\a\177\000\000\000XProtoError\000LIB",
'\000' , "\200?D", '\000' ,
"?\303\000\000\000\000(\345[\002\a\177\000\000\240\202;l2V\000\000\251\000\000\000\000\000\000\000`|\022\024\377\177\000\000\032\000\000\000\000\000\000\000\233\000\000\000\000\000\000\000\303>\211\005\a\177\000\000\005",
'\000' ,
"\060\222\n\005\a\177\000\000\060|\022\024\377\177\000\000"...
args = {{gp_offset = 48, fp_offset = 48, overflow_arg_area =
0x7fff14127c58, reg_save_area = 0x7fff14127b80}}
#4 0x7f070232de31 in _gdk_x11_display_error_event
(display=display@entry=0x56326c2e3110, error=error@entry=0x7fff14127d30) at
../../../../../gdk/x11/gdkdisplay-x11.c:2766
buf = "GLXBadContext", '\000'
msg =
display_x11 = 0x56326c2e3110
tmp_list =
ignore = 0
__func__ = "_gdk_x11_display_error_event"
#5 0x7f070233acb3 in gdk_x_error (xdisplay=0x56326c2d49e0,
error=0x7fff14127d30) at ../../../../../gdk/x11/gdkmain-x11.c:307
error_display = 0x56326c2e3110
manager =
displays = 0x0
error = 0x7fff14127d30
xdisplay = 0x56326c2d49e0
error_display =
manager =
displays =
gdk_display =
__inst =
__t =
__r =
#6 0x7f0704a0cc8d in _XError (dpy=dpy@entry=0x56326c2d49e0,
rep=rep@entry=0x7fff14127e20) at ../../src/XlibInt.c:1434
rtn_val =
event = {type = 0, xany = {type = 0, serial = 94774563260896,
send_event = 0, display = 0xd009, window = 1743785}, xkey = {type = 0, serial =
94774563260896, send_event = 0, display = 0xd009, window = 1743785, root =
8655628632, subwindow = 94774576511872, time = 3437855993206445056, x =
39845959, y = 0, x_root = 0, y_root = 0, state = 1815665024, keycode = 22066,
same_screen = 39845959}, xbutton = {type = 0, serial = 94774563260896,
send_event = 0, display = 0xd009, window = 1743785, root = 8655628632,
subwindow = 94774576511872, time = 3437855993206445056, x = 39845959, y = 0,
x_root = 0, y_root = 0, state = 1815665024, button = 22066, same_screen =
39845959}, xmotion = {type = 0, serial = 94774563260896, send_event
[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles
This bug was fixed in the package console-setup - 1.108ubuntu15.5 --- console-setup (1.108ubuntu15.5) xenial; urgency=medium * setupcon: use /run for tempfiles (and dump the various unnecessary fallback paths), since /run is always mountable rw at least as early as /tmp is and is guaranteed to be safe from tmpcleaners at boot. Only keep /tmp as a fallback in case we have access to write to /tmp and to a console, but not to /run. LP: #1824227. -- Steve Langasek Wed, 10 Apr 2019 13:16:29 -0700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1824227 Title: console-setup failure due to race with systemd-tmpfiles Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Xenial: Fix Released Status in console-setup source package in Bionic: Fix Released Status in console-setup source package in Cosmic: Fix Released Status in console-setup source package in Disco: Fix Released Bug description: [SRU Justification] I'm seeing a console-setup.service failure quite regularly in testing where the temp file that should have been created can't be found. This is a regular xenial cloud image. 19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ... 19:51:13 systemd[1]: Starting Set console font and keymap... 19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.a8FGSs: No such file 19:51:15 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE 19:51:15 systemd[1]: Failed to start Set console font and keymap. 19:51:15 systemd[1]: console-setup.service: Unit entered failed state. 19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'. ... /bin/setupcon has a lovely tempfile function that looks like: if \ TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp 2>/dev/null` Here's our edited IRC conversation on the bug: <@vorlon> so I do think you're being hit by the tmp cleaner <@vorlon> also this seems like bad pathological default behavior for the tmp cleaner, to delete files that have just been created <@vorlon> but we should fix console-setup to not rely on /tmp <@vorlon> and I prefer that we do that instead of trying to fiddle with the ordering of the systemd units on startup <@vorlon> i.e. console-setup has an undeclared dependency on systemd-tmpfiles-clean; let's remove the dependency instead of declaring it <@vorlon> are you failing the race more often now than in the past? <@rcj>vorlon: it feels like it's failing more often but I don't have data to answer that. <@vorlon> are we shipping an image with a dirty rootfs? <@vorlon> dirty in the sense that e2fsck doesn't take one look at it, say "yep, nothing to do here" and exit <@vorlon> in the sense that this is what would make dev-sda1.device slow to complete AIUI <@rcj>would filesystem resize on first boot mark it dirty? Because that will happen <@vorlon> huh good question <@vorlon> it might rcj, unclean shutdown? <@rcj>xnox: first boot [Test case] 1. Install console-setup from -proposed 2. Reboot 3. Verify that `systemctl status console-setup` shows that the service has completed successfully. Since this is a race, additional fuzz testing may be warranted for the cloud images to confirm that the issue experienced in GCE is really fixed. However, that should not block promotion of this SRU fix since there definitely is a race here that should be fixed per se even if there are other issues still causing a failure in GCE. [Regression potential] None known. /run is guaranteed to be mounted rw very early in boot - generally before /tmp is mounted, due to /tmp being on the rootfs that needs to be fscked before remount. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.4 ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18 Uname: Linux 4.15.0-1029-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 19:24:12 2019 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles
This bug was fixed in the package console-setup - 1.178ubuntu2.8 --- console-setup (1.178ubuntu2.8) bionic; urgency=medium * setupcon: use /run for tempfiles (and dump the various unnecessary fallback paths), since /run is always mountable rw at least as early as /tmp is and is guaranteed to be safe from tmpcleaners at boot. Only keep /tmp as a fallback in case we have access to write to /tmp and to a console, but not to /run. LP: #1824227. -- Steve Langasek Wed, 10 Apr 2019 13:13:34 -0700 ** Changed in: console-setup (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: console-setup (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1824227 Title: console-setup failure due to race with systemd-tmpfiles Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Xenial: Fix Released Status in console-setup source package in Bionic: Fix Released Status in console-setup source package in Cosmic: Fix Released Status in console-setup source package in Disco: Fix Released Bug description: [SRU Justification] I'm seeing a console-setup.service failure quite regularly in testing where the temp file that should have been created can't be found. This is a regular xenial cloud image. 19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ... 19:51:13 systemd[1]: Starting Set console font and keymap... 19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.a8FGSs: No such file 19:51:15 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE 19:51:15 systemd[1]: Failed to start Set console font and keymap. 19:51:15 systemd[1]: console-setup.service: Unit entered failed state. 19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'. ... /bin/setupcon has a lovely tempfile function that looks like: if \ TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp 2>/dev/null` Here's our edited IRC conversation on the bug: <@vorlon> so I do think you're being hit by the tmp cleaner <@vorlon> also this seems like bad pathological default behavior for the tmp cleaner, to delete files that have just been created <@vorlon> but we should fix console-setup to not rely on /tmp <@vorlon> and I prefer that we do that instead of trying to fiddle with the ordering of the systemd units on startup <@vorlon> i.e. console-setup has an undeclared dependency on systemd-tmpfiles-clean; let's remove the dependency instead of declaring it <@vorlon> are you failing the race more often now than in the past? <@rcj>vorlon: it feels like it's failing more often but I don't have data to answer that. <@vorlon> are we shipping an image with a dirty rootfs? <@vorlon> dirty in the sense that e2fsck doesn't take one look at it, say "yep, nothing to do here" and exit <@vorlon> in the sense that this is what would make dev-sda1.device slow to complete AIUI <@rcj>would filesystem resize on first boot mark it dirty? Because that will happen <@vorlon> huh good question <@vorlon> it might rcj, unclean shutdown? <@rcj>xnox: first boot [Test case] 1. Install console-setup from -proposed 2. Reboot 3. Verify that `systemctl status console-setup` shows that the service has completed successfully. Since this is a race, additional fuzz testing may be warranted for the cloud images to confirm that the issue experienced in GCE is really fixed. However, that should not block promotion of this SRU fix since there definitely is a race here that should be fixed per se even if there are other issues still causing a failure in GCE. [Regression potential] None known. /run is guaranteed to be mounted rw very early in boot - generally before /tmp is mounted, due to /tmp being on the rootfs that needs to be fscked before remount. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.4 ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18 Uname: Linux 4.15.0-1029-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 19:24:12 2019 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup
[Touch-packages] [Bug 1824227] Update Released
The verification of the Stable Release Update for console-setup has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1824227 Title: console-setup failure due to race with systemd-tmpfiles Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Xenial: Fix Released Status in console-setup source package in Bionic: Fix Released Status in console-setup source package in Cosmic: Fix Released Status in console-setup source package in Disco: Fix Released Bug description: [SRU Justification] I'm seeing a console-setup.service failure quite regularly in testing where the temp file that should have been created can't be found. This is a regular xenial cloud image. 19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ... 19:51:13 systemd[1]: Starting Set console font and keymap... 19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.a8FGSs: No such file 19:51:15 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE 19:51:15 systemd[1]: Failed to start Set console font and keymap. 19:51:15 systemd[1]: console-setup.service: Unit entered failed state. 19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'. ... /bin/setupcon has a lovely tempfile function that looks like: if \ TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp 2>/dev/null` Here's our edited IRC conversation on the bug: <@vorlon> so I do think you're being hit by the tmp cleaner <@vorlon> also this seems like bad pathological default behavior for the tmp cleaner, to delete files that have just been created <@vorlon> but we should fix console-setup to not rely on /tmp <@vorlon> and I prefer that we do that instead of trying to fiddle with the ordering of the systemd units on startup <@vorlon> i.e. console-setup has an undeclared dependency on systemd-tmpfiles-clean; let's remove the dependency instead of declaring it <@vorlon> are you failing the race more often now than in the past? <@rcj>vorlon: it feels like it's failing more often but I don't have data to answer that. <@vorlon> are we shipping an image with a dirty rootfs? <@vorlon> dirty in the sense that e2fsck doesn't take one look at it, say "yep, nothing to do here" and exit <@vorlon> in the sense that this is what would make dev-sda1.device slow to complete AIUI <@rcj>would filesystem resize on first boot mark it dirty? Because that will happen <@vorlon> huh good question <@vorlon> it might rcj, unclean shutdown? <@rcj>xnox: first boot [Test case] 1. Install console-setup from -proposed 2. Reboot 3. Verify that `systemctl status console-setup` shows that the service has completed successfully. Since this is a race, additional fuzz testing may be warranted for the cloud images to confirm that the issue experienced in GCE is really fixed. However, that should not block promotion of this SRU fix since there definitely is a race here that should be fixed per se even if there are other issues still causing a failure in GCE. [Regression potential] None known. /run is guaranteed to be mounted rw very early in boot - generally before /tmp is mounted, due to /tmp being on the rootfs that needs to be fscked before remount. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.4 ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18 Uname: Linux 4.15.0-1029-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 19:24:12 2019 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1824227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles
This bug was fixed in the package console-setup - 1.178ubuntu9.1 --- console-setup (1.178ubuntu9.1) cosmic; urgency=medium * setupcon: use /run for tempfiles (and dump the various unnecessary fallback paths), since /run is always mountable rw at least as early as /tmp is and is guaranteed to be safe from tmpcleaners at boot. Only keep /tmp as a fallback in case we have access to write to /tmp and to a console, but not to /run. LP: #1824227. -- Steve Langasek Wed, 10 Apr 2019 13:02:51 -0700 ** Changed in: console-setup (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 console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1824227 Title: console-setup failure due to race with systemd-tmpfiles Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Xenial: Fix Released Status in console-setup source package in Bionic: Fix Released Status in console-setup source package in Cosmic: Fix Released Status in console-setup source package in Disco: Fix Released Bug description: [SRU Justification] I'm seeing a console-setup.service failure quite regularly in testing where the temp file that should have been created can't be found. This is a regular xenial cloud image. 19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ... 19:51:13 systemd[1]: Starting Set console font and keymap... 19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.a8FGSs: No such file 19:51:15 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE 19:51:15 systemd[1]: Failed to start Set console font and keymap. 19:51:15 systemd[1]: console-setup.service: Unit entered failed state. 19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'. ... /bin/setupcon has a lovely tempfile function that looks like: if \ TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp 2>/dev/null` Here's our edited IRC conversation on the bug: <@vorlon> so I do think you're being hit by the tmp cleaner <@vorlon> also this seems like bad pathological default behavior for the tmp cleaner, to delete files that have just been created <@vorlon> but we should fix console-setup to not rely on /tmp <@vorlon> and I prefer that we do that instead of trying to fiddle with the ordering of the systemd units on startup <@vorlon> i.e. console-setup has an undeclared dependency on systemd-tmpfiles-clean; let's remove the dependency instead of declaring it <@vorlon> are you failing the race more often now than in the past? <@rcj>vorlon: it feels like it's failing more often but I don't have data to answer that. <@vorlon> are we shipping an image with a dirty rootfs? <@vorlon> dirty in the sense that e2fsck doesn't take one look at it, say "yep, nothing to do here" and exit <@vorlon> in the sense that this is what would make dev-sda1.device slow to complete AIUI <@rcj>would filesystem resize on first boot mark it dirty? Because that will happen <@vorlon> huh good question <@vorlon> it might rcj, unclean shutdown? <@rcj>xnox: first boot [Test case] 1. Install console-setup from -proposed 2. Reboot 3. Verify that `systemctl status console-setup` shows that the service has completed successfully. Since this is a race, additional fuzz testing may be warranted for the cloud images to confirm that the issue experienced in GCE is really fixed. However, that should not block promotion of this SRU fix since there definitely is a race here that should be fixed per se even if there are other issues still causing a failure in GCE. [Regression potential] None known. /run is guaranteed to be mounted rw very early in boot - generally before /tmp is mounted, due to /tmp being on the rootfs that needs to be fscked before remount. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.4 ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18 Uname: Linux 4.15.0-1029-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 19:24:12 2019 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this
[Touch-packages] [Bug 1737158] Re: [19.04 FEAT] Rebase openssl > 1.1.0
** 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 openssl in Ubuntu. https://bugs.launchpad.net/bugs/1737158 Title: [19.04 FEAT] Rebase openssl > 1.1.0 Status in Ubuntu on IBM z Systems: Fix Released Status in openssl package in Ubuntu: Fix Released Bug description: Include latest version from upstream openssl > 1.1.0 when available https://www.openssl.org/policies/releasestrat.html LP will be updated once available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1737158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
https://bugs.freedesktop.org/show_bug.cgi?id=110452 ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Bug watch added: freedesktop.org Bugzilla #110452 https://bugs.freedesktop.org/show_bug.cgi?id=110452 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=110452 Importance: Unknown Status: Unknown ** Description changed: https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91 + + --- + + https://bugs.freedesktop.org/show_bug.cgi?id=110452 --- totem crashed with signal 5 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 11:26:51 2018 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-05-04 (323 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 5 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Description changed: + https://bugs.freedesktop.org/show_bug.cgi?id=110452 https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91 - - --- - - https://bugs.freedesktop.org/show_bug.cgi?id=110452 --- totem crashed with signal 5 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 11:26:51 2018 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-05-04 (323 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 5 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- 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/1758287 Title: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() Status in Mesa: Confirmed Status in mesa package in Ubuntu: New Status in totem package in Ubuntu: Confirmed Bug description: https://bugs.freedesktop.org/show_bug.cgi?id=110452 https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91 --- totem crashed with signal 5 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 11:26:51 2018 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-05-04 (323 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 5 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with signal 5 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/mesa/+bug/1758287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783294] Re: [19.04 FEAT] Partial relro support
** 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 binutils in Ubuntu. https://bugs.launchpad.net/bugs/1783294 Title: [19.04 FEAT] Partial relro support Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: Implement partial relro support for Linux on z Separate the non-lazy relocations that get executed directly at load time and the lazy relocations that can occur at any time into distinct sections in the GOT (Global Offset Table Benefit: Improved security via partial relro support Will be made available with next version of binutils > 2.31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1783294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803998] Re: [19.04 FEAT] upgrade binutils >=2.32
** 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 binutils in Ubuntu. https://bugs.launchpad.net/bugs/1803998 Title: [19.04 FEAT] upgrade binutils >=2.32 Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: Upgrade to new version of binutils >= 2.32 Available here: https://www.gnu.org/software/binutils/ LP will be updated, once available upstream! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles
I have built cosmic, bionic, and xenial images in GCE with the packages from -proposed and tested that console setup is functioning correctly with the change. Thanks. I will be marking each of the releases as tested. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1824227 Title: console-setup failure due to race with systemd-tmpfiles Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Xenial: Fix Committed Status in console-setup source package in Bionic: Fix Committed Status in console-setup source package in Cosmic: Fix Committed Status in console-setup source package in Disco: Fix Released Bug description: [SRU Justification] I'm seeing a console-setup.service failure quite regularly in testing where the temp file that should have been created can't be found. This is a regular xenial cloud image. 19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ... 19:51:13 systemd[1]: Starting Set console font and keymap... 19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.a8FGSs: No such file 19:51:15 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE 19:51:15 systemd[1]: Failed to start Set console font and keymap. 19:51:15 systemd[1]: console-setup.service: Unit entered failed state. 19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'. ... /bin/setupcon has a lovely tempfile function that looks like: if \ TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp 2>/dev/null` Here's our edited IRC conversation on the bug: <@vorlon> so I do think you're being hit by the tmp cleaner <@vorlon> also this seems like bad pathological default behavior for the tmp cleaner, to delete files that have just been created <@vorlon> but we should fix console-setup to not rely on /tmp <@vorlon> and I prefer that we do that instead of trying to fiddle with the ordering of the systemd units on startup <@vorlon> i.e. console-setup has an undeclared dependency on systemd-tmpfiles-clean; let's remove the dependency instead of declaring it <@vorlon> are you failing the race more often now than in the past? <@rcj>vorlon: it feels like it's failing more often but I don't have data to answer that. <@vorlon> are we shipping an image with a dirty rootfs? <@vorlon> dirty in the sense that e2fsck doesn't take one look at it, say "yep, nothing to do here" and exit <@vorlon> in the sense that this is what would make dev-sda1.device slow to complete AIUI <@rcj>would filesystem resize on first boot mark it dirty? Because that will happen <@vorlon> huh good question <@vorlon> it might rcj, unclean shutdown? <@rcj>xnox: first boot [Test case] 1. Install console-setup from -proposed 2. Reboot 3. Verify that `systemctl status console-setup` shows that the service has completed successfully. Since this is a race, additional fuzz testing may be warranted for the cloud images to confirm that the issue experienced in GCE is really fixed. However, that should not block promotion of this SRU fix since there definitely is a race here that should be fixed per se even if there are other issues still causing a failure in GCE. [Regression potential] None known. /run is guaranteed to be mounted rw very early in boot - generally before /tmp is mounted, due to /tmp being on the rootfs that needs to be fscked before remount. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.4 ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18 Uname: Linux 4.15.0-1029-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 19:24:12 2019 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1824227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1824688] Re: date+%-Y -d "- N years" errors when N > 111
Assaf's test, attached. ** Attachment added: "inv-year.c" https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1824688/+attachment/5256314/+files/inv-year.c ** Changed in: coreutils (Ubuntu) Status: New => Confirmed -- 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/1824688 Title: date+%-Y -d "- N years" errors when N > 111 Status in coreutils package in Ubuntu: Confirmed Bug description: I have been using 'date +%-Y -d "- 2010 years" in a script for years but today after using the script after upgrading to disco it has failed. After some experimentation it succeeds with upto 111 years but fails from 112 onwards. Error given is: 'date: invalid date '- 112 years'. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: coreutils 8.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Sun Apr 14 10:59:36 2019 InstallationDate: Installed on 2017-10-08 (553 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: coreutils UpgradeStatus: Upgraded to disco on 2019-04-13 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1824688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824688] Re: date+%-Y -d "- N years" errors when N > 111
Further exchange on https://debbugs.gnu.org/35289 suggests this is a libc6 problem, not a coreutils/date one. Assaf Gordon (upstream) provided a test that can be run (attached here are inv-year.c). If it fails on the mktime() call, then it is not 'date', but libc6. I also found that setting TZ=UTC seems to bypass the problem; in my primary test machine, TZ was unset (but I was still getting a failure). Setting TZ to UTC, or an invalid value, works. Setting TZ=America/Chicago fails (perhaps related to DST?): cerdea@piatam:~/Downloads$ env TZ=UTC date --debug +%-Y -d '- 2010 years' date: parsed relative part: -2010 year(s) date: input timezone: TZ="UTC" environment value date: using current time as starting value: '17:28:13' date: using current date as starting value: '(Y-M-D) 2019-04-16' date: starting date/time: '(Y-M-D) 2019-04-16 17:28:13' date: warning: when adding relative months/years, it is recommended to specify the 15th of the months date: after date adjustment (-2010 years, +0 months, +0 days), date: new date/time = '(Y-M-D) 0009-04-16 17:28:13' date: '(Y-M-D) 0009-04-16 17:28:13' = -61874001107 epoch-seconds date: timezone: TZ="UTC" environment value date: final: -61874001107.571934909 (epoch-seconds) date: final: (Y-M-D) 0009-04-16 17:28:13 (UTC) date: final: (Y-M-D) 0009-04-16 17:28:13 (UTC+00) 9 cerdea@piatam:~/Downloads$ env TZ=blah/blah date --debug +%-Y -d '- 2010 years' date: parsed relative part: -2010 year(s) date: input timezone: TZ="blah/blah" environment value date: using current time as starting value: '17:28:26' date: using current date as starting value: '(Y-M-D) 2019-04-16' date: starting date/time: '(Y-M-D) 2019-04-16 17:28:26' date: warning: when adding relative months/years, it is recommended to specify the 15th of the months date: after date adjustment (-2010 years, +0 months, +0 days), date: new date/time = '(Y-M-D) 0009-04-16 17:28:26' date: '(Y-M-D) 0009-04-16 17:28:26' = -61874001094 epoch-seconds date: timezone: TZ="blah/blah" environment value date: final: -61874001094.525620784 (epoch-seconds) date: final: (Y-M-D) 0009-04-16 17:28:26 (UTC) date: final: (Y-M-D) 0009-04-16 17:28:26 (UTC+00) 9 cerdea@piatam:~/Downloads$ env TZ=America/Chicago date --debug +%-Y -d '- 2010 years' date: parsed relative part: -2010 year(s) date: input timezone: TZ="America/Chicago" environment value date: using current time as starting value: '12:28:37' date: using current date as starting value: '(Y-M-D) 2019-04-16' date: starting date/time: '(Y-M-D) 2019-04-16 12:28:37' date: warning: when adding relative months/years, it is recommended to specify the 15th of the months date: error: adding relative date resulted in an invalid date: '(Y-M-D) 0009-04-16 12:28:37' date: invalid date ‘- 2010 years’ 1 cerdea@piatam:~/Downloads$ and, with Assaf's test: cerdea@piatam:~/Downloads$ env TZ=UTC ./inv-year time() = 1555435812 localtime() = 2019-04-16 17:30:12 (mday=16 wday=2, isdst=0) struct tm (after adjustment) = 0009-04-16 17:30:12 (mday=16 wday=2, isdst=0) mktime() after date adjustment = -61874000988 cerdea@piatam:~/Downloads$ env TZ=blahblah ./inv-year time() = 1555435821 localtime() = 2019-04-16 17:30:21 (mday=16 wday=2, isdst=0) struct tm (after adjustment) = 0009-04-16 17:30:21 (mday=16 wday=2, isdst=0) mktime() after date adjustment = -61874000979 cerdea@piatam:~/Downloads$ env TZ=America/Chicago ./inv-year time() = 1555435831 localtime() = 2019-04-16 12:30:31 (mday=16 wday=2, isdst=1) struct tm (after adjustment) = 0009-04-16 12:30:31 (mday=16 wday=2, isdst=1) inv-year: mktime() failed: Value too large for defined data type -- 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/1824688 Title: date+%-Y -d "- N years" errors when N > 111 Status in coreutils package in Ubuntu: Confirmed Bug description: I have been using 'date +%-Y -d "- 2010 years" in a script for years but today after using the script after upgrading to disco it has failed. After some experimentation it succeeds with upto 111 years but fails from 112 onwards. Error given is: 'date: invalid date '- 112 years'. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: coreutils 8.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Sun Apr 14 10:59:36 2019 InstallationDate: Installed on 2017-10-08 (553 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: coreutils UpgradeStatus: Upgraded to disco on 2019-04-13 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1824688/+subscriptions --
[Touch-packages] [Bug 1825021] Re: apt's dpkgpm.cc WriteApportReport function should gather more data
FWIW, apt actually overrides PATH since bionic or cosmic or something
like that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1825021
Title:
apt's dpkgpm.cc WriteApportReport function should gather more data
Status in apt package in Ubuntu:
New
Bug description:
While fixing bug 1813464 it occurred to me that it is not obvious that
the dist-upgrader tarball includes its own copy of invoke-rc.d and
that this has been complicated to debug more than once. The apport
information in that report was gathered by apt's dpkgpm.cc code and I
think we should extend that to gather additional information from the
environment at the time that the package installation failed. For
example the dist-upgrader sets the following:
os.environ["PATH"] = "%s:%s" % (os.getcwd()+"/imported",
os.environ["PATH"])
Gathering path from the environment would have made diagnosing bug
1813464 a lot easier. I tested modifying dpkgpm.cc with the following:
if(const char* env_p = std::getenv("PATH"))
fprintf(report, "EnvPATH: %s\n", env_p);
I then installed the crash-in-postinst package from the daisy-plucker-
seeds PPA and received a crash report with the EnvPATH key and value.
Its worth noting that when apport gathers environment information only
a white listed set of keys is gathered to prevent disclosing
potentially sensitive information. So we should look at what
environment variables the dist-upgrader sets and gather those at a
minimum.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825021/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333024] Re: Bluetooth audio Underruns, dropouts or crackling sound
Same behaviour here - very very similar to https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 but the issue persists. I have a T430, Xubuntu 18.10, inbuilt bluetooth, and pulseaudio 12.2. This makes it very hard to use headphones and wifi at the same time. -- 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/1333024 Title: Bluetooth audio Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: Confirmed Bug description: My bluetooth performance when connected to an audio device is very poor on my Lenovo T440s. There are multiple problems when I connect to my logitech device: 1) It often disconnects unexpectedly. It will connect for 2-5 seconds before disconnecting. This happens over and over with no messages in dmesg. 2) If I can get it to connect, the audio device is listed in the sound settings only about 50% of the time. I have to disconnect, restart bluetooth (\etc\init.d\bluetooth restart) and try again. 3) If I can get it playing, the audio lags by ~10s and is really, really chopped up. Totally unintelligible. The things I know which might help: Computer Type: Lenovo T440s Operating system: Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty Linux version : 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Bluetooth card: Network controller: Intel Corporation Wireless 7260 (rev 83) Pulseaudio version: pulseaudio 4.0 - I don't think it's pulse audio as the daemon won't start: $ pulseaudio --check $ pulseaudio -D E: [pulseaudio] main.c: Daemon startup failed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seth 2220 F pulseaudio /dev/snd/controlC1: seth 2220 F pulseaudio /dev/snd/pcmC1D0c: seth 2220 F...m pulseaudio CurrentDesktop: Unity Date: Sun Jun 22 14:29:41 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-21 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: (EE)Logitech Adapter Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [(EE)Logitech Adapter, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET64WW (2.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ006HUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET64WW(2.14):bd11/12/2013:svnLENOVO:pn20AQ006HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ006HUS:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ006HUS dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1333024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825021] Re: apt's dpkgpm.cc WriteApportReport function should gather more data
In the event that this were SRU'ed for it to be useful we'd need to SRU
apt to the release from which people were upgrading.
** Tags added: disco rls-ee-incoming
** Changed in: apt (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1825021
Title:
apt's dpkgpm.cc WriteApportReport function should gather more data
Status in apt package in Ubuntu:
New
Bug description:
While fixing bug 1813464 it occurred to me that it is not obvious that
the dist-upgrader tarball includes its own copy of invoke-rc.d and
that this has been complicated to debug more than once. The apport
information in that report was gathered by apt's dpkgpm.cc code and I
think we should extend that to gather additional information from the
environment at the time that the package installation failed. For
example the dist-upgrader sets the following:
os.environ["PATH"] = "%s:%s" % (os.getcwd()+"/imported",
os.environ["PATH"])
Gathering path from the environment would have made diagnosing bug
1813464 a lot easier. I tested modifying dpkgpm.cc with the following:
if(const char* env_p = std::getenv("PATH"))
fprintf(report, "EnvPATH: %s\n", env_p);
I then installed the crash-in-postinst package from the daisy-plucker-
seeds PPA and received a crash report with the EnvPATH key and value.
Its worth noting that when apport gathers environment information only
a white listed set of keys is gathered to prevent disclosing
potentially sensitive information. So we should look at what
environment variables the dist-upgrader sets and gather those at a
minimum.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825021/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825021] [NEW] apt's dpkgpm.cc WriteApportReport function should gather more data
Public bug reported:
While fixing bug 1813464 it occurred to me that it is not obvious that
the dist-upgrader tarball includes its own copy of invoke-rc.d and that
this has been complicated to debug more than once. The apport
information in that report was gathered by apt's dpkgpm.cc code and I
think we should extend that to gather additional information from the
environment at the time that the package installation failed. For
example the dist-upgrader sets the following:
os.environ["PATH"] = "%s:%s" % (os.getcwd()+"/imported",
os.environ["PATH"])
Gathering path from the environment would have made diagnosing bug
1813464 a lot easier. I tested modifying dpkgpm.cc with the following:
if(const char* env_p = std::getenv("PATH"))
fprintf(report, "EnvPATH: %s\n", env_p);
I then installed the crash-in-postinst package from the daisy-plucker-
seeds PPA and received a crash report with the EnvPATH key and value.
Its worth noting that when apport gathers environment information only a
white listed set of keys is gathered to prevent disclosing potentially
sensitive information. So we should look at what environment variables
the dist-upgrader sets and gather those at a minimum.
** Affects: apt (Ubuntu)
Importance: High
Status: New
** Tags: disco rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1825021
Title:
apt's dpkgpm.cc WriteApportReport function should gather more data
Status in apt package in Ubuntu:
New
Bug description:
While fixing bug 1813464 it occurred to me that it is not obvious that
the dist-upgrader tarball includes its own copy of invoke-rc.d and
that this has been complicated to debug more than once. The apport
information in that report was gathered by apt's dpkgpm.cc code and I
think we should extend that to gather additional information from the
environment at the time that the package installation failed. For
example the dist-upgrader sets the following:
os.environ["PATH"] = "%s:%s" % (os.getcwd()+"/imported",
os.environ["PATH"])
Gathering path from the environment would have made diagnosing bug
1813464 a lot easier. I tested modifying dpkgpm.cc with the following:
if(const char* env_p = std::getenv("PATH"))
fprintf(report, "EnvPATH: %s\n", env_p);
I then installed the crash-in-postinst package from the daisy-plucker-
seeds PPA and received a crash report with the EnvPATH key and value.
Its worth noting that when apport gathers environment information only
a white listed set of keys is gathered to prevent disclosing
potentially sensitive information. So we should look at what
environment variables the dist-upgrader sets and gather those at a
minimum.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825021/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825015] [NEW] package libudev1:i386 237-3ubuntu10.20 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
Public bug reported: Ubuntu crashed and locked up while installing updates. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libudev1:i386 237-3ubuntu10.20 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue Apr 16 11:00:33 2019 Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2019-04-03 (13 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: i386 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.10 SourcePackage: systemd Title: package libudev1:i386 237-3ubuntu10.20 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to bionic on 2019-04-03 (13 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- 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/1825015 Title: package libudev1:i386 237-3ubuntu10.20 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in systemd package in Ubuntu: New Bug description: Ubuntu crashed and locked up while installing updates. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libudev1:i386 237-3ubuntu10.20 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue Apr 16 11:00:33 2019 Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2019-04-03 (13 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: i386 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.10 SourcePackage: systemd Title: package libudev1:i386 237-3ubuntu10.20 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to bionic on 2019-04-03 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825001] Re: Allow archives to send a 4xx response to tell apt to try again later
apt currently considers the following errors transient:
constexpr unsigned int TransientCodes[] = {
408, // Request Timeout
429, // Too Many Requests
500, // Internal Server Error
502, // Bad Gateway
503, // Service Unavailable
504, // Gateway Timeout
599, // Network Connect Timeout Error
};
and thus does not report them as errors, only as warnings.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1825001
Title:
Allow archives to send a 4xx response to tell apt to try again later
Status in apt package in Ubuntu:
New
Bug description:
As part of a broad plan to improve our ability to manage traffic to
the archive servers, it would be useful if the archives could return a
4xx response to indicate to apt that they were over capacity and it
should try again later, where later could be defined on the client
side as several hours, the next day for unattended-upgrades runs, etc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825001/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825001] Re: Allow archives to send a 4xx response to tell apt to try again later
FWIW, over capacity should be 503 usually, not a 4xx response code. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1825001 Title: Allow archives to send a 4xx response to tell apt to try again later Status in apt package in Ubuntu: New Bug description: As part of a broad plan to improve our ability to manage traffic to the archive servers, it would be useful if the archives could return a 4xx response to indicate to apt that they were over capacity and it should try again later, where later could be defined on the client side as several hours, the next day for unattended-upgrades runs, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825001] Re: Allow archives to send a 4xx response to tell apt to try again later
503 also has a Retry-After field that you can use to communicate when to retry, although we do not have any support for retrying things, apart from twice a day, as systemd does not offer this ability to our type of timer. And for interactive use, well, the user will retry manually. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1825001 Title: Allow archives to send a 4xx response to tell apt to try again later Status in apt package in Ubuntu: New Bug description: As part of a broad plan to improve our ability to manage traffic to the archive servers, it would be useful if the archives could return a 4xx response to indicate to apt that they were over capacity and it should try again later, where later could be defined on the client side as several hours, the next day for unattended-upgrades runs, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest
** Changed in: ubuntu-power-systems Status: In Progress => Fix Released ** Changed in: ubuntu-power-systems Status: Fix Released => Fix Committed ** Also affects: util-linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: util-linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: util-linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: util-linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1764628 Title: incorrect hypervisor and virtualization type reported in compat mode guest Status in The Ubuntu-power-systems project: Fix Committed Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Bug description: [IMPACT] In xenial lscpu prints the wrong "Hypervisor vendor" and "Virtualization type" on PowerVM or KVM systems. Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC. [TEST] Curent output: ubuntu@P8lpar3:~$ dpkg -l "*util-linux*" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii util-linux 2.31.1-0.4ub ppc64el miscellaneous system utilities un util-linux-loc (no description available) ubuntu@P8lpar3:~$ lscpu Architecture:ppc64le Byte Order: Little Endian CPU(s): 128 On-line CPU(s) list: 0-127 Thread(s) per core: 8 Core(s) per socket: 1 Socket(s): 16 NUMA node(s):2 Model: 2.1 (pvr 004b 0201) Model name: POWER8 (architected), altivec supported Hypervisor vendor: pHyp Virtualization type: para L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): NUMA node4 CPU(s): 0-127 ubuntu@P8lpar3:~$ Expected Output: $ lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):128 On-line CPU(s) list: 0-127 Thread(s) per core:8 Core(s) per socket:1 Socket(s): 16 NUMA node(s): 2 Model: 2.1 (pvr 004b 0201) Model name:POWER8 (architected), altivec supported Hypervisor vendor: pHyp Virtualization type: para L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): NUMA node4 CPU(s): 0-127 [Potential Regression] The fix changes the logic to how lscpu-dmi returns from read_hypervisor_dmi() this could introduce potential regression in platforms that has incorrect DMI information. [Other Info] ---uname output--- Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = boston-LC ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC: root@guest:/tmp# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Model: 2.2 (pvr 004e 1202) Model name:POWER8 (architected), altivec supported >> Hypervisor vendor: horizontal >> Virtualization type: full L1d cache: 32K L1i cache: 32K NUMA node0 CPU(s): 0,1 Stack trace output: no Oops output: no We test what is coming along with distro. If you are not able to see issue with : https://launchpad.net/ubuntu/+source/util- linux/2.27.1-6ubuntu3.5 .. can we get this included in 16.04.x train ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest
It's in the xenial-proposed queue. Marking fixed for trunk. ** Changed in: util-linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1764628 Title: incorrect hypervisor and virtualization type reported in compat mode guest Status in The Ubuntu-power-systems project: In Progress Status in util-linux package in Ubuntu: Fix Released Bug description: [IMPACT] In xenial lscpu prints the wrong "Hypervisor vendor" and "Virtualization type" on PowerVM or KVM systems. Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC. [TEST] Curent output: ubuntu@P8lpar3:~$ dpkg -l "*util-linux*" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii util-linux 2.31.1-0.4ub ppc64el miscellaneous system utilities un util-linux-loc (no description available) ubuntu@P8lpar3:~$ lscpu Architecture:ppc64le Byte Order: Little Endian CPU(s): 128 On-line CPU(s) list: 0-127 Thread(s) per core: 8 Core(s) per socket: 1 Socket(s): 16 NUMA node(s):2 Model: 2.1 (pvr 004b 0201) Model name: POWER8 (architected), altivec supported Hypervisor vendor: pHyp Virtualization type: para L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): NUMA node4 CPU(s): 0-127 ubuntu@P8lpar3:~$ Expected Output: $ lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):128 On-line CPU(s) list: 0-127 Thread(s) per core:8 Core(s) per socket:1 Socket(s): 16 NUMA node(s): 2 Model: 2.1 (pvr 004b 0201) Model name:POWER8 (architected), altivec supported Hypervisor vendor: pHyp Virtualization type: para L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): NUMA node4 CPU(s): 0-127 [Potential Regression] The fix changes the logic to how lscpu-dmi returns from read_hypervisor_dmi() this could introduce potential regression in platforms that has incorrect DMI information. [Other Info] ---uname output--- Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = boston-LC ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC: root@guest:/tmp# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Model: 2.2 (pvr 004e 1202) Model name:POWER8 (architected), altivec supported >> Hypervisor vendor: horizontal >> Virtualization type: full L1d cache: 32K L1i cache: 32K NUMA node0 CPU(s): 0,1 Stack trace output: no Oops output: no We test what is coming along with distro. If you are not able to see issue with : https://launchpad.net/ubuntu/+source/util- linux/2.27.1-6ubuntu3.5 .. can we get this included in 16.04.x train ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825001] [NEW] Allow archives to send a 4xx response to tell apt to try again later
Public bug reported: As part of a broad plan to improve our ability to manage traffic to the archive servers, it would be useful if the archives could return a 4xx response to indicate to apt that they were over capacity and it should try again later, where later could be defined on the client side as several hours, the next day for unattended-upgrades runs, etc. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1825001 Title: Allow archives to send a 4xx response to tell apt to try again later Status in apt package in Ubuntu: New Bug description: As part of a broad plan to improve our ability to manage traffic to the archive servers, it would be useful if the archives could return a 4xx response to indicate to apt that they were over capacity and it should try again later, where later could be defined on the client side as several hours, the next day for unattended-upgrades runs, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495580] Re: chfn needs to learn about the --extrausers argument and use libnss-extrausers files when set
Validation done, no errors found. Logs: xenial: https://paste.ubuntu.com/p/PrRPMnmBkN/ ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1495580 Title: chfn needs to learn about the --extrausers argument and use libnss- extrausers files when set Status in Snappy: Fix Released Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Xenial: Fix Committed Status in shadow source package in Bionic: Fix Released Bug description: as seen in bug 1492327, adduser now works for creating users in the extrausers db but when it tries to update the GECOS field at the end of adding a user (interactively and noninteractively) chfn falls over ... chfn needs similar patches to the other shadow binaries that recently got extrausers support. TEST CASE: - create a user "foo" on an Ubuntu Core system - run "chfn --extrausers -f some-name foo" on an Ubuntu Core system REGRESSION POTENTIAL: - low: this requires the new (and optional) --extrausers switch to change anything. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1495580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825000] [NEW] Add ability for mirrors to distinguish interactive and non-interactive apt runs
Public bug reported: As part of a larger scale plan to manage traffic to the main archive servers it would be useful if apt could provide a facility for us to identify interactive vs. non-interactive traffic on the server side, ideally via a header of some kind. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1825000 Title: Add ability for mirrors to distinguish interactive and non-interactive apt runs Status in apt package in Ubuntu: New Bug description: As part of a larger scale plan to manage traffic to the main archive servers it would be useful if apt could provide a facility for us to identify interactive vs. non-interactive traffic on the server side, ideally via a header of some kind. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825000/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825000] Re: Add ability for mirrors to distinguish interactive and non-interactive apt runs
Obviously this may be equally relevant to unattended-upgrades. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1825000 Title: Add ability for mirrors to distinguish interactive and non-interactive apt runs Status in apt package in Ubuntu: New Bug description: As part of a larger scale plan to manage traffic to the main archive servers it would be useful if apt could provide a facility for us to identify interactive vs. non-interactive traffic on the server side, ideally via a header of some kind. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825000/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824961] Re: AppArmor blocks apport python hook from working
> they have to do with python applications with apport hooks that are confined with apparmor. The hook is defined in site.py, so by definition all python applications have the hook, and thus all python applications that are confined with apparmor. So either we want that apport for all of them, or (what I think makes more sense) none of them. I guess the question is: Shouldn't we have a python-apport abstraction that apps (or local admin) can include to make debugging work under apparmor? It should probably live in apport, I guess, so apport can define which files it needs. IIRC, the gcc stuff is irrelevant, that comes from ctypes, imported from magic, not from apport. But that might also be a case where it could be useful to have a python-ctypes abstraction, probably shipped in python. -- 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/1824961 Title: AppArmor blocks apport python hook from working Status in AppArmor: New Status in apparmor package in Ubuntu: New Status in kopanocore package in Ubuntu: New Bug description: The Python profile is very strict, but it prevents Python applications from producing proper crash reports using apport, as the apport hook cannot be loaded, as it requires access to dpkg's cputable, and likely also apt config files and dpkg status files. I'm wondering what the right approach here is: Should the apport hook work under AppArmor, and do we thus have to add the files the hook needs; or should we just say "screw it, we want the additional security" and not get proper error reporting while AppArmor is confining the program? This can be seen in recent autopkgtest failure for kopanocore: + kopano-search --help Traceback (most recent call last): File "/usr/sbin/kopano-search", line 4, in import kopano_search File "/usr/lib/python3/dist-packages/kopano_search/__init__.py", line 18, in from queue import Empty File "/usr/lib/python3.7/queue.py", line 16, in from _queue import Empty ImportError: /usr/lib/python3.7/lib-dynload/_queue.cpython-37m-x86_64-linux-gnu.so: failed to map segment from shared object Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 35, in apt_pkg.init_system() apt_pkg.Error: E:Error reading the CPU table To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1824961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778695] Re: ristretto ignores cr2 files
Due to a now fixed bug in libmagic [1] the file is identified as TIFF image data in 18.10, and therefore Ristretto is allowed to load it. An exception [2] was added to the Ristretto code. --- [1] https://github.com/file/file/commit/750bb84244c22d50fc7e44f68f33764852c0c0c1 [2] https://git.xfce.org/apps/ristretto/commit/?id=6d43825421d77c3fefca3df9202d5e5ae9a5b89c -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1778695 Title: ristretto ignores cr2 files Status in file package in Ubuntu: New Status in ristretto package in Ubuntu: New Bug description: Ristretto does not show canon .cr2 files, neither on 16.04.4 nor on 18.04. For 16.04: lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 apt-cache policy ristretto ristretto: Installed: 0.8.0-1 Candidate: 0.8.0-1 Version table: *** 0.8.0-1 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status for 18.04 lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apt-cache policy ristretto ristretto: Installed: 0.8.2-1ubuntu1 Candidate: 0.8.2-1ubuntu1 Version table: *** 0.8.2-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1778695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824998] [NEW] Zanata is messing up the translations
Public bug reported: Hi Today is actually impossible to keep NM translations in good shape since Zanata (a tool used in Fedora and Red Hat) is messing up the translations. Example: https://translations.launchpad.net/ubuntu/disco/+source/network- manager/+pots/networkmanager/es/870/+translate Which literally means: One of the functions of the swimming boat (3) is a function of the boat's control unit. Or translating "master" as "dominate" This is hilarous but also frustrating. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1824998 Title: Zanata is messing up the translations Status in network-manager package in Ubuntu: New Bug description: Hi Today is actually impossible to keep NM translations in good shape since Zanata (a tool used in Fedora and Red Hat) is messing up the translations. Example: https://translations.launchpad.net/ubuntu/disco/+source/network- manager/+pots/networkmanager/es/870/+translate Which literally means: One of the functions of the swimming boat (3) is a function of the boat's control unit. Or translating "master" as "dominate" This is hilarous but also frustrating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1824998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824661] Re: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty.
I downloaded the latest Ubuntu daily last evening (20190413) and installed it. I was unable to use nomodeset to get to tty. I tried numerous times to no avail. This morning I booted to recovery mode and used the root terminal to run updates. A new kernel version was installed so I thought why not reboot and see if it made any difference. To my surprise, the system booted and was running normally with the 418 Nvidia driver active. I was able to use prime-select to switch to Intel and it works as well. I have no idea why it is working now but am happy to provide any additional logs if you want to investigate further. My next step is to try installing another 19.04 release like Kubuntu or MATE to see if a similar situation occurs. I will answer back with my findings. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1824661 Title: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty. Status in lightdm package in Ubuntu: Incomplete Status in slick-greeter package in Ubuntu: Incomplete Bug description: Hello. I am having issues consistently with this laptop and the Nvidia drivers in 19.04. I have tested this on Ubuntu, Kubuntu, Ubuntu Budgie, and Ubuntu MATE. This is with both the recommended 418 driver as well as 390. Today I tried installing the latest daily of Ubuntu MATE with the proprietary driver option on my Dell XPS 15 9570 with Nvidia GP107M (GeForce GRX 1050 Time Mobile). Boots to blank screen that flashes a couple times. Can't get to tty. Reboot, editing grub to include nomodeset. Boots to underscore character in the top left. I can get tty at least. 418 driver is installed. Looking at logs but nothing seems obvious. If there's anything I can do to help with this please let me know. Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Sat Apr 13 18:27:12 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-11-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-04-13 (0 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) MachineType: Dell Inc. XPS 15 9570 ProcEnviron: TERM=cygwin PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic root=UUID=add8471d-1273-4547-aef3-4be006f9eb9c ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1824661/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
Thanks, I don't see anything obvious in the log, setting as New again for now (would be good to see if removing the faulty units pointed in the previous comment makes a difference though) ** Changed in: systemd (Ubuntu) Status: Incomplete => 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/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: New Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) dmi.bios.date: 07/02/07 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MP21.88Z.007F.B06.0707021348 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F4208DC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208DC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: dmi.product.family: MacPro dmi.product.name: MacPro2,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 984390] Re: $PATH is taken from login.defs not /etc/environment
SRU validated, no issues found. Logs: xenial: https://paste.ubuntu.com/p/9jdjdQns7t/ bionic: https://paste.ubuntu.com/p/P6CZ5WnmmB/ ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/984390 Title: $PATH is taken from login.defs not /etc/environment Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Precise: Won't Fix Status in shadow source package in Xenial: Fix Committed Status in shadow source package in Bionic: Fix Committed Bug description: TEST CASE: $PATH isn't sourced from /etc/environment, instead the version in /etc/login.defs is used. (The example below comes from a precise install.) | james@panlong:~$ echo $PATH | /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games | james@panlong:~$ sudo su - buildd | buildd@panlong:~$ echo $PATH | /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games | buildd@panlong:~$ cat /etc/environment | PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" | buildd@panlong:~$ grep PATH /etc/login.defs | # Three items must be defined: MAIL_DIR, ENV_SUPATH, and ENV_PATH. | # *REQUIRED* The default PATH settings, for superuser and normal users. | ENV_SUPATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin | ENV_PATH PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games | #CRACKLIB_DICTPATH | buildd@panlong:~$ sudo sed -i -e "s#^ENV_PATH.*#ENV_PATH PATH=/wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games#" /etc/login.defs | buildd@panlong:~$ logout | james@panlong:~$ sudo su - buildd | buildd@panlong:~$ echo $PATH | /wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games | buildd@panlong:~$ REGRESSION POTENTIAL: - medium: it changes (incorrect) existing behaviour so https://xkcd.com/1172/ may apply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/984390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804478] Re: netplan dhcp interface with no default route causes systemd-networkd-wait-online to hang
I checked case (B) that I added. First I created a new setup as described (to make sure no old modifications influence the verification) That worked, I saw the wait line on boot: [*** ] A start job is running for Wait for… to be Configured (29s / no limit) After boot I had the wait time in the failed service: $ systemctl status systemd-networkd-wait-online ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-04-16 13:52:04 UTC; 15s ago Installing the version in proposed ... $ sudo apt install systemd=237-3ubuntu10.21 Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: grub-pc-bin Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 42 not upgraded. Need to get 3318 kB of archives. After this operation, 11.3 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libnss-systemd amd64 237-3ubuntu10.21 [105 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libpam-systemd amd64 237-3ubuntu10.21 [108 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 systemd amd64 237-3ubuntu10.21 [2901 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libsystemd0 amd64 237-3ubuntu10.21 [204 kB] Fetched 3318 kB in 1s (4658 kB/s) (Reading database ... 60080 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.21_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.21) over (237-3ubuntu10.19) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.21_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.21) over (237-3ubuntu10.19) ... Preparing to unpack .../systemd_237-3ubuntu10.21_amd64.deb ... Unpacking systemd (237-3ubuntu10.21) over (237-3ubuntu10.19) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.21_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.21) over (237-3ubuntu10.19) ... Setting up libsystemd0:amd64 (237-3ubuntu10.21) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up systemd (237-3ubuntu10.21) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for dbus (1.12.2-1ubuntu1) ... Setting up libnss-systemd:amd64 (237-3ubuntu10.21) ... Setting up libpam-systemd:amd64 (237-3ubuntu10.21) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Rebooting: - bootup was fast - service works fine $ systemctl status systemd-networkd-wait-online ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled) Active: active (exited) since Tue 2019-04-16 13:54:20 UTC; 10s ago Thereby good for case B, once A is confirmed as well please set it to verified. ** Description changed: [impact] systemd-networkd, when configured to use ipv4 dhcp for an interface can hang. This triggers in two known cases: a) if configured to ignore the dhcp server's route b) the server provides no route Then systemd-networkd will hang waiting for the interface's configuration to complete (until it times out). This delays boot as well as any restart to systemd-networkd. The fix is backporting upstream commit [1] [1]: https://github.com/systemd/systemd/commit/223932c7 [test case] There are two ways to test this. A) make the system ignore Routes (slightly less realistic but easier to test) configure an interface using systemd-networkd: $ cat /etc/systemd/network/20-ens7.network [Match] Name=ens7 [Network] DHCP=ipv4 [DHCP] UseRoutes=false then reboot, and check: $ systemctl status systemd-networkd-wait-online ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-04-08 23:59:26 UTC; 2min 59s ago [...] Apr 08 23:57:27 lp1804478 systemd[1]: Starting Wait for Network to be Configured... Apr 08 23:57:30 lp1804478 systemd-networkd-wait-online[593]: managing: ens3 Apr 08 23:57:30 lp1804478 systemd-networkd-wait-online[593]: ignoring: lo Apr 08 23:59:26 lp1804478 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Apr 08 23:59:26 lp1804478 systemd[1]:
[Touch-packages] [Bug 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest
xnox, would you please elaborate what "in unapproved" means ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1764628 Title: incorrect hypervisor and virtualization type reported in compat mode guest Status in The Ubuntu-power-systems project: In Progress Status in util-linux package in Ubuntu: In Progress Bug description: [IMPACT] In xenial lscpu prints the wrong "Hypervisor vendor" and "Virtualization type" on PowerVM or KVM systems. Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC. [TEST] Curent output: ubuntu@P8lpar3:~$ dpkg -l "*util-linux*" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii util-linux 2.31.1-0.4ub ppc64el miscellaneous system utilities un util-linux-loc (no description available) ubuntu@P8lpar3:~$ lscpu Architecture:ppc64le Byte Order: Little Endian CPU(s): 128 On-line CPU(s) list: 0-127 Thread(s) per core: 8 Core(s) per socket: 1 Socket(s): 16 NUMA node(s):2 Model: 2.1 (pvr 004b 0201) Model name: POWER8 (architected), altivec supported Hypervisor vendor: pHyp Virtualization type: para L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): NUMA node4 CPU(s): 0-127 ubuntu@P8lpar3:~$ Expected Output: $ lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):128 On-line CPU(s) list: 0-127 Thread(s) per core:8 Core(s) per socket:1 Socket(s): 16 NUMA node(s): 2 Model: 2.1 (pvr 004b 0201) Model name:POWER8 (architected), altivec supported Hypervisor vendor: pHyp Virtualization type: para L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): NUMA node4 CPU(s): 0-127 [Potential Regression] The fix changes the logic to how lscpu-dmi returns from read_hypervisor_dmi() this could introduce potential regression in platforms that has incorrect DMI information. [Other Info] ---uname output--- Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = boston-LC ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC: root@guest:/tmp# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Model: 2.2 (pvr 004e 1202) Model name:POWER8 (architected), altivec supported >> Hypervisor vendor: horizontal >> Virtualization type: full L1d cache: 32K L1i cache: 32K NUMA node0 CPU(s): 0,1 Stack trace output: no Oops output: no We test what is coming along with distro. If you are not able to see issue with : https://launchpad.net/ubuntu/+source/util- linux/2.27.1-6ubuntu3.5 .. can we get this included in 16.04.x train ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823630] Re: ibus ftbfs in cosmic (s390x only)
Thank you for the report but Cosmic build issues are low priority at this point, tagging as rls-cc-notfixing , that doesn't stop fixing those problems but they are not going to be tracked as rls issues ** Tags removed: rls-cc-incoming ** Tags added: rls-cc-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1823630 Title: ibus ftbfs in cosmic (s390x only) Status in ibus package in Ubuntu: New Bug description: https://launchpadlibrarian.net/418305550/buildlog_ubuntu-cosmic- s390x.ibus_1.5.19-1ubuntu1_BUILDING.txt.gz this is different than the ftbfs in disco (LP: #1823423): gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src -I../../src -include ../../config.h -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -DG_LOG_DOMAIN=\"IBUS\" -DBINDIR=\"/usr/bin\" -DPKGDATADIR=\"/usr/share/ibus\" -DIBUS_DISABLE_DEPRECATED -Wno-unused-variable -Wno-unused-but-set-variable -Wno-unused-function -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -c -o keybindingmanager.o keybindingmanager.c gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src -I../../src -include ../../config.h -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -DG_LOG_DOMAIN=\"IBUS\" -DBINDIR=\"/usr/bin\" -DPKGDATADIR=\"/usr/share/ibus\" -DIBUS_DISABLE_DEPRECATED -Wno-unused-variable -Wno-unused-but-set-variable -Wno-unused-function -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -c -o panel.o panel.c In file included from ../../src/ibusobject.h:41, from ../../src/ibus.h:31, from panel.c:30: ../../src/ibusdebug.h:49:31: warning: ISO C does not permit named variadic macros [-Wvariadic-macros] #define ibus_warning(msg, args...) \ ^~~ In file included from ../../src/ibusobject.h:41, from ../../src/ibus.h:31, from keybindingmanager.c:19: ../../src/ibusdebug.h:49:31: warning: ISO C does not permit named variadic macros [-Wvariadic-macros] #define ibus_warning(msg, args...) \ ^~~ keybindingmanager.c: In function ‘_vala_XIGrabModifiers_array_free’: keybindingmanager.c:812:6: warning: statement with no effect [-Wunused-value] ([i]); ~^~ keybindingmanager.c: In function ‘keybinding_manager_grab_keycode’: keybindingmanager.c:1039:4: warning: statement with no effect [-Wunused-value] (); ~^~~~ keybindingmanager.c: At top level: keybindingmanager.c:1460:1: warning: data definition has no type or storage class ing_manager_type_id__volatile; ^ keybindingmanager.c:1460:1: warning: type defaults to ‘int’ in declaration of ‘ing_manager_type_id__volatile’ [-Wimplicit-int] keybindingmanager.c:1461:1: error: expected identifier or ‘(’ before ‘}’ token } ^ panel.c: In function ‘panel_init_status_icon’: panel.c:1796:2:
[Touch-packages] [Bug 1823636] Re: neon27 ftbfs in cosmic
Thank you for the report but Cosmic build issues are low priority at this point, tagging as rls-cc-notfixing , that doesn't stop fixing those problems but they are not going to be tracked as rls issues ** Tags removed: rls-cc-incoming ** Tags added: rls-cc-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to neon27 in Ubuntu. https://bugs.launchpad.net/bugs/1823636 Title: neon27 ftbfs in cosmic Status in neon27 package in Ubuntu: New Bug description: https://launchpadlibrarian.net/418304976/buildlog_ubuntu-cosmic- amd64.neon27_0.30.2-2build1_BUILDING.txt.gz ssl... 24/65 ssl... 24/65 FAIL - no_client_cert (error message was 'Could not read status line: SSL error: tlsv13 alert certificate required', missing 'client certificate was requested') ssl... 24/65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/1823636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823644] Re: pixman ftbfs in cosmic (ppc64el only)
Thank you for the report but Cosmic build issues are low priority at
this point, tagging as rls-cc-notfixing , that doesn't stop fixing those
problems but they are not going to be tracked as rls issues
** Tags removed: rls-cc-incoming
** Tags added: rls-cc-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pixman in Ubuntu.
https://bugs.launchpad.net/bugs/1823644
Title:
pixman ftbfs in cosmic (ppc64el only)
Status in pixman package in Ubuntu:
New
Bug description:
https://launchpadlibrarian.net/418306030/buildlog_ubuntu-cosmic-
ppc64el.pixman_0.34.0-2_BUILDING.txt.gz
- Test 0x9895a6 failed -
operator: PIXMAN_OP_IN_REVERSE (component alpha)
dest_x, dest_y: 1 1
width, height:6 2
source: format: a8r8g8b8size: 14 x 6
mask: format: r3g3b2 size: 15 x 6
dest: format: a2r2g2b2size: 7 x 3
-- Failed pixel: (1, 2) --
source ARGB: 1.00 1.00 1.00 1.00 (pixel:
)
mask ARGB:1.00 0.00 0.00 0.00 (pixel: 0)
dest ARGB:1.00 1.00 1.00 1.00 (pixel: ff)
expected ARGB:1.00 0.00 0.00 0.00
min acceptable: 3 0 0 0
got: 0 0 0 0 (pixel: 0)
max acceptable: 3 0 0 0
{ PIXMAN_OP_IN_REVERSE,
PIXMAN_a8r8g8b8, 0x,
PIXMAN_r3g3b2,0x0,
PIXMAN_a2r2g2b2, 0xff
},
FAIL tolerance-test (exit status: 1)
Testsuite summary for pixman 0.34.0
# TOTAL: 32
# PASS: 22
# SKIP: 1
# XFAIL: 0
# FAIL: 9
# XPASS: 0
# ERROR: 0
See test/test-suite.log
Please report to pix...@lists.freedesktop.org
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1823644/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823650] Re: v4l-utils ftbfs in cosmic
Thank you for the report but Cosmic build issues are low priority at
this point, tagging as rls-cc-notfixing , that doesn't stop fixing those
problems but they are not going to be tracked as rls issues
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to v4l-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1823650
Title:
v4l-utils ftbfs in cosmic
Status in v4l-utils package in Ubuntu:
New
Bug description:
https://launchpadlibrarian.net/418304769/buildlog_ubuntu-cosmic-amd64
.v4l-utils_1.14.2-1_BUILDING.txt.gz
g++ -I. -I../.. -I../../utils/common -I../../lib/include -Wall
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o v4l2_compliance-v4l2-compliance.o `test -f
'v4l2-compliance.cpp' || echo './'`v4l2-compliance.cpp
In file included from v4l2-compliance.h:42,
from v4l2-compliance.cpp:38:
../../utils/common/cv4l-helpers.h: In member function ‘void
cv4l_buffer::init(const cv4l_buffer&)’:
../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no
trivial copy-assignment; use copy-assignment or copy-initialization instead
[-Wclass-memaccess]
memcpy(this, , sizeof(b));
^
../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared
here
class cv4l_buffer : public v4l_buffer {
^~~
g++ -I. -I../.. -I../../utils/common -I../../lib/include -Wall
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o v4l2_compliance-v4l2-test-debug.o `test -f
'v4l2-test-debug.cpp' || echo './'`v4l2-test-debug.cpp
In file included from v4l2-compliance.h:42,
from v4l2-test-debug.cpp:35:
../../utils/common/cv4l-helpers.h: In member function ‘void
cv4l_buffer::init(const cv4l_buffer&)’:
../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no
trivial copy-assignment; use copy-assignment or copy-initialization instead
[-Wclass-memaccess]
memcpy(this, , sizeof(b));
^
../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared
here
class cv4l_buffer : public v4l_buffer {
^~~
g++ -I. -I../.. -I../../utils/common -I../../lib/include -Wall
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o v4l2_compliance-v4l2-test-input-output.o `test -f
'v4l2-test-input-output.cpp' || echo './'`v4l2-test-input-output.cpp
In file included from v4l2-compliance.h:42,
from v4l2-test-input-output.cpp:32:
../../utils/common/cv4l-helpers.h: In member function ‘void
cv4l_buffer::init(const cv4l_buffer&)’:
../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no
trivial copy-assignment; use copy-assignment or copy-initialization instead
[-Wclass-memaccess]
memcpy(this, , sizeof(b));
^
../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared
here
class cv4l_buffer : public v4l_buffer {
^~~
g++ -I. -I../.. -I../../utils/common -I../../lib/include -Wall
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o v4l2_compliance-v4l2-test-controls.o `test -f
'v4l2-test-controls.cpp' || echo './'`v4l2-test-controls.cpp
In file included from v4l2-compliance.h:42,
from v4l2-test-controls.cpp:33:
../../utils/common/cv4l-helpers.h: In member function ‘void
cv4l_buffer::init(const cv4l_buffer&)’:
../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no
trivial copy-assignment; use copy-assignment or copy-initialization instead
[-Wclass-memaccess]
memcpy(this, , sizeof(b));
^
../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared
here
class cv4l_buffer : public v4l_buffer {
^~~
g++ -I. -I../.. -I../../utils/common -I../../lib/include -Wall
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o v4l2_compliance-v4l2-test-io-config.o `test -f
'v4l2-test-io-config.cpp' || echo
[Touch-packages] [Bug 1824103] Re: aplay record file failed always.
@infinity has found a fix for this in Debian and is looking at syncing it now. -- 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/1824103 Title: aplay record file failed always. Status in pulseaudio package in Ubuntu: Incomplete Bug description: Test machine: ThinkPad X1 Carbon Image: Ubuntu Disco 19.04 CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, stepping: 0xa) GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) BIOS: N23ET55W (1.30 ) Steps: 1. Install image 19.04 2. Login as default user 3. Open a terminal and type "$ arecord abc.wav" 4. Say something and let laptop recorded your words 5. Cancel the record, please press 'Ctrl + C' 6. Please type "$ aplay abc.wav" in terminal Expected result: The voice played smoothly. Actual result: Step 3, u@u-ThinkPad-X1-Carbon-6th:~$ arecord abc.wav Recording WAVE 'abc.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono ^CAborted by signal Interrupt... arecord: pcm_read:2145: read error: Interrupted system call Step 6, u@u-ThinkPad-X1-Carbon-6th:~$ aplay abc.wav ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave aplay: main:828: audio open error: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1824103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824961] Re: AppArmor blocks apport python hook from working
I might also mention on IRC the exact type of thing why we've had these rules in the profile that ship them: [119698.000187] audit: type=1400 audit(1555405334.985:222): apparmor="DENIED" operation="exec" profile="/usr/sbin/kopano-search" name="/usr/bin/x86_64-linux-gnu-gcc-8" pid=15647 comm="kopano-search" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 We aren't going to put compiler execution into the python (or likely any other) abstraction. It is difficult because for security you only want enough access so the application can behave normally which is often at odds with access the the application needs when it crashes or behaves unexpectedly (indeed, we wrap applications with apparmor precisely to limit what they can do when behaving unexpectedly). -- 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/1824961 Title: AppArmor blocks apport python hook from working Status in AppArmor: New Status in apparmor package in Ubuntu: New Status in kopanocore package in Ubuntu: New Bug description: The Python profile is very strict, but it prevents Python applications from producing proper crash reports using apport, as the apport hook cannot be loaded, as it requires access to dpkg's cputable, and likely also apt config files and dpkg status files. I'm wondering what the right approach here is: Should the apport hook work under AppArmor, and do we thus have to add the files the hook needs; or should we just say "screw it, we want the additional security" and not get proper error reporting while AppArmor is confining the program? This can be seen in recent autopkgtest failure for kopanocore: + kopano-search --help Traceback (most recent call last): File "/usr/sbin/kopano-search", line 4, in import kopano_search File "/usr/lib/python3/dist-packages/kopano_search/__init__.py", line 18, in from queue import Empty File "/usr/lib/python3.7/queue.py", line 16, in from _queue import Empty ImportError: /usr/lib/python3.7/lib-dynload/_queue.cpython-37m-x86_64-linux-gnu.so: failed to map segment from shared object Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 35, in apt_pkg.init_system() apt_pkg.Error: E:Error reading the CPU table To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1824961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824961] Re: AppArmor blocks apport python hook from working
Traditionally we have actually put these accesses in the packages that ship the profile, like Marc said, because profilers may not want the profile to automatically have everything apport requires. These accesses should *not* be in the python abstraction because the accesses have nothing to do with python applications, they have to do with python applications with apport hooks that are confined with apparmor. There was always the idea that perhaps we could create an apport abstraction and maybe move distro profiles to using it, but it isn't yet clear this is what we want to do since the accesses aren't fully understood. For now, moving this back to kopanocore and adding an apparmor wishlist task. ** Also affects: kopanocore (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor Importance: Undecided Status: New ** Changed in: apparmor Importance: Undecided => Wishlist -- 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/1824961 Title: AppArmor blocks apport python hook from working Status in AppArmor: New Status in apparmor package in Ubuntu: New Status in kopanocore package in Ubuntu: New Bug description: The Python profile is very strict, but it prevents Python applications from producing proper crash reports using apport, as the apport hook cannot be loaded, as it requires access to dpkg's cputable, and likely also apt config files and dpkg status files. I'm wondering what the right approach here is: Should the apport hook work under AppArmor, and do we thus have to add the files the hook needs; or should we just say "screw it, we want the additional security" and not get proper error reporting while AppArmor is confining the program? This can be seen in recent autopkgtest failure for kopanocore: + kopano-search --help Traceback (most recent call last): File "/usr/sbin/kopano-search", line 4, in import kopano_search File "/usr/lib/python3/dist-packages/kopano_search/__init__.py", line 18, in from queue import Empty File "/usr/lib/python3.7/queue.py", line 16, in from _queue import Empty ImportError: /usr/lib/python3.7/lib-dynload/_queue.cpython-37m-x86_64-linux-gnu.so: failed to map segment from shared object Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 35, in apt_pkg.init_system() apt_pkg.Error: E:Error reading the CPU table To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1824961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial
** Description changed:
+ [SRU Justification]
+
+ == Impact ==
+ The Xenial 4.4 kernel already has a patch applied which implements the
matchall filter. But in order to actually use it, iproute2 needs to pick up the
user-space
+ side of the implementation.
+
+ == Fix ==
+ Backported a patch from iproute2 upstream which adds the missing support.
Tested against the standard 4.4 and the HWE kernel in 16.04 (see testcase).
+
+ == Risk of Regression ==
+ This adds a new filter type which has to be actively selected. This should
not impact existing uses. So low.
+
+ == Testcase ==
+ ip link add dev dummy0 type dummy
+ ip link add dev dummy1 type dummy
+ ip link set dev dummy0 up
+ ip link set dev dummy1 up
+ tc qdisc add dev dummy0 handle 1: root prio
+ tc filter add dev dummy0 parent 1: matchall skip_hw action mirred egress
mirror dev dummy1
+
+ at this point, "tc filter show dev dummy0" should spit out something
+ like:
+
+ filter parent 1: protocol all pref 49152 matchall
+ filter parent 1: protocol all pref 49152 matchall handle 0x1
+ action order 1: mirred (Egress Mirror to device dummy1) pipe
+ index 1 ref 1 bind 1
+
+ and the functionality can be tested via
+
+ tcpdump -n -i dummy1 &
+ ping -I dummy0 1.2.3.4
+
+ ---
+
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with clsact
qdisc (see bug #1642510).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Bug description:
[SRU Justification]
== Impact ==
The Xenial 4.4 kernel already has a patch applied which implements the
matchall filter. But in order to actually use it, iproute2 needs to pick up the
user-space
side of the implementation.
== Fix ==
Backported a patch from iproute2 upstream which adds the missing support.
Tested against the standard 4.4 and the HWE kernel in 16.04 (see testcase).
== Risk of Regression ==
This adds a new filter type which has to be actively selected. This should
not impact existing uses. So low.
== Testcase ==
ip link add dev dummy0 type dummy
ip link add dev dummy1 type dummy
ip link set dev dummy0 up
ip link set dev dummy1 up
tc qdisc add dev dummy0 handle 1: root prio
tc filter add dev dummy0 parent 1: matchall skip_hw action mirred egress
mirror dev dummy1
at this point, "tc filter show dev dummy0" should spit out something
like:
filter parent 1: protocol all pref 49152 matchall
filter parent 1: protocol all pref 49152 matchall handle 0x1
action order 1: mirred (Egress Mirror to device dummy1) pipe
index 1 ref 1 bind 1
and the functionality can be tested via
tcpdump -n -i dummy1 &
ping -I dummy0 1.2.3.4
---
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial
Hello Nicolas, or anyone else affected,
Accepted iproute2 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/4.3.0-1ubuntu3.16.04.5 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: iproute2 (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Tags removed: verification-done-xenial
** Tags added: verification-needed verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Bug description:
[SRU Justification]
== Impact ==
The Xenial 4.4 kernel already has a patch applied which implements the
matchall filter. But in order to actually use it, iproute2 needs to pick up the
user-space
side of the implementation.
== Fix ==
Backported a patch from iproute2 upstream which adds the missing support.
Tested against the standard 4.4 and the HWE kernel in 16.04 (see testcase).
== Risk of Regression ==
This adds a new filter type which has to be actively selected. This should
not impact existing uses. So low.
== Testcase ==
ip link add dev dummy0 type dummy
ip link add dev dummy1 type dummy
ip link set dev dummy0 up
ip link set dev dummy1 up
tc qdisc add dev dummy0 handle 1: root prio
tc filter add dev dummy0 parent 1: matchall skip_hw action mirred egress
mirror dev dummy1
at this point, "tc filter show dev dummy0" should spit out something
like:
filter parent 1: protocol all pref 49152 matchall
filter parent 1: protocol all pref 49152 matchall handle 0x1
action order 1: mirred (Egress Mirror to device dummy1) pipe
index 1 ref 1 bind 1
and the functionality can be tested via
tcpdump -n -i dummy1 &
ping -I dummy0 1.2.3.4
---
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824498] Re: Unable to connect to wifi since wpasupplicant_2.4-0ubuntu6.4_amd64.deb update
you need to click in the "build: " to have the deb, e.g https://bugs.launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/15249000 There is no repo for those though -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1824498 Title: Unable to connect to wifi since wpasupplicant_2.4-0ubuntu6.4_amd64.deb update Status in wpa package in Ubuntu: New Bug description: I'm unable to connect to internet through wifi since this morning, since wpasupplicant_2.4-0ubuntu6.4_amd64.deb was updated on my machine this morning at 3 am and I didn't have trouble ever before I strongly suspect this update to have caused the problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1824498/+subscriptions -- Mailing list: https://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 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
I've added the last 250 lines of the log, if that's not enough let me know. Once it says it's reached target reboot the next thing it does is send a kill signal to all processes, including journalctl so there is not much useful information beyond that point. Also I can not switch virtual terminals at that point, no keyboard input has any effects at that point including magic sys req key. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 16 Apr 2019, Sebastien Bacher wrote: > Date: Tue, 16 Apr 2019 08:49:56 - > From: Sebastien Bacher > Reply-To: Bug 1824893 <1824...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target > Reboot but then does not reboot > > Thank you for your bug report. Could you attach your journalctl log from > that shutdown to the bug? > > The log on > https://launchpadlibrarian.net/419441276/SystemdFailedUnits.txt also > shows that some systemd unit are failing on your system, maybe one of > those is creating the issue... > > (also when it's hanging can you switch into another vt for debugging?) > > ** Changed in: systemd (Ubuntu) > Importance: Undecided => Low > > ** Changed in: systemd (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824893 > > Title: > When I type systemctl reboot system reaches Target Reboot but then > does not reboot > > Status in systemd package in Ubuntu: > Incomplete > > Bug description: > This is similar to the bug where systemd used to get stuck in target > Shutdown except that bug affected all my hardware, now it gets stuck > at target Reboot but this only affects my elderly Mac Pro 1,1 and does > not affect my laptop or i7-6700k and i7-6850k based servers. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5 > ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 > Uname: Linux 5.0.0-8-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: MATE > Date: Mon Apr 15 16:30:34 2019 > InstallationDate: Installed on 2018-12-06 (130 days ago) > InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > MachineType: Apple Computer, Inc. MacPro2,1 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency > root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 > SourcePackage: systemd > SystemdDelta: > [EXTENDED] /lib/systemd/system/ondemand.service ÿÿ > /lib/systemd/system/ondemand.service.d/ubuntustudio.conf > [EXTENDED] /lib/systemd/system/rc-local.service ÿÿ > /lib/systemd/system/rc-local.service.d/debian.conf > [EXTENDED] /lib/systemd/system/user@.service ÿÿ > /lib/systemd/system/user@.service.d/timeout.conf > > 3 overridden configuration files found. > UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions > -- 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/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: Incomplete Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture:
[Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
** Attachment added: "Last 250 lines of journalctl log for shutdown" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+attachment/5256268/+files/journalctl.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: Incomplete Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) dmi.bios.date: 07/02/07 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MP21.88Z.007F.B06.0707021348 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F4208DC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208DC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: dmi.product.family: MacPro dmi.product.name: MacPro2,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824753] Re: When I pass the Qt application to the secondary monitor the characters of the application increase
Now I do. Before I just updated mutter_3.32.0-1_amd64.deb. I have updated all deb and the problem continues. patrick@patrick-pc:~$ dpkg -l | grep mutter ii gir1.2-mutter-4:amd64 3.32.0-1 amd64GObject introspection data for Mutter ii libmutter-4-0:amd643.32.0-1 amd64window manager library from the Mutter window manager iU libmutter-4-dev:amd64 3.32.0-1 amd64Development files for the Mutter window manager ii mutter 3.32.0-1 amd64lightweight GTK+ window manager ii mutter-common 3.32.0-1 all shared files for the Mutter window manager patrick@patrick-pc:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1824753 Title: When I pass the Qt application to the secondary monitor the characters of the application increase Status in mutter package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Incomplete Status in vlc package in Ubuntu: Incomplete Bug description: Hi. I have recently installed Ubuntu 19.04 RC. Everything works fine except the Qt applications. I have two monitors and when I pass the Qt application to the secondary monitor the characters of the application increase. They happen to the traditionally installed Qt applications and to those installed with Flatpak and Snap. I leave you a video in which you can see the problem with the VLC application. https://youtu.be/tEZJONsinU4 https://i.imgur.com/R7GubxF.png?fb --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-14 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1824753/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824949] Re: /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended-upgrade@2256:main:run:mark_pkgs_to_upgrade:mark_upgrade_adjusted:call_adjusted::ver_in_
This bug was fixed in the package unattended-upgrades - 1.10ubuntu5 --- unattended-upgrades (1.10ubuntu5) disco; urgency=medium * Adjust only transitive dependencies in the fallback when a package from an allowed origin can't be marked to install/upgrade. This is a much lighter approach than marking every upgradable package because the full fallback was triggered on packages held back as well, using an excessive amount of CPU time. Also it crashed with packages not having any version in allowed origins. (LP: #1824804, #1824949) -- Balint Reczey Tue, 16 Apr 2019 08:54:49 +0200 ** Changed in: unattended-upgrades (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824949 Title: /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended- upgrade@2256:main:run:mark_pkgs_to_upgrade:mark_upgrade_adjusted:call_adjusted::ver_in_allowed_origin Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.10ubuntu2, the problem page at https://errors.ubuntu.com/problem/fbfbd01360a90ba2d6c2620bffdd9e77843e5671 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1824949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824498] Re: Unable to connect to wifi since wpasupplicant_2.4-0ubuntu6.4_amd64.deb update
@seb128 Is there a repo I can enable/activate to install this previous version? In the page you linked I didn't see any .deb file -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1824498 Title: Unable to connect to wifi since wpasupplicant_2.4-0ubuntu6.4_amd64.deb update Status in wpa package in Ubuntu: New Bug description: I'm unable to connect to internet through wifi since this morning, since wpasupplicant_2.4-0ubuntu6.4_amd64.deb was updated on my machine this morning at 3 am and I didn't have trouble ever before I strongly suspect this update to have caused the problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1824498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824804] Re: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages
This bug was fixed in the package unattended-upgrades - 1.10ubuntu5 --- unattended-upgrades (1.10ubuntu5) disco; urgency=medium * Adjust only transitive dependencies in the fallback when a package from an allowed origin can't be marked to install/upgrade. This is a much lighter approach than marking every upgradable package because the full fallback was triggered on packages held back as well, using an excessive amount of CPU time. Also it crashed with packages not having any version in allowed origins. (LP: #1824804, #1824949) -- Balint Reczey Tue, 16 Apr 2019 08:54:49 +0200 ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824804 Title: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: [Impact] * The fix for LP: #1821101 allowed installing packages for which APT's resolver could not find solution for without adjusting other packages, but also tries to adjust many packages to install packages which are held back. [Test Case] * Set up a system where systemd (or a package that can't be upgraded without also upgrading other packages) need to be upgraded to the version in -security. * Mark systemd on hold apt mark hold systemd * Observe u-u falling back to adjusting all upgradable packages in unfixed versions and adjusting only a few in fixed versions: # unattended-upgrade --verbose --debug ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to marking libnss-systemd, then adjusting changes package libnss-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting all packages adjusting candidate version: 2ping=4.1-1 ... Fixed: ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to adjusting libnss-systemd's dependencies recursively adjusting candidate version: libnss-systemd=237-3ubuntu10.19 adjusting candidate version: libkmod2=24-1ubuntu3 adjusting candidate version: mount=2.31.1-0.4ubuntu3 adjusting candidate version: libmount1=2.31.1-0.4ubuntu3 ... [Regression Potential] * The less extensive fallback may not find solutions for installing packages with special relationships that the full fallback could have found, but I don't know about such special cases in the archive and the autopkgtest cover a fair set of popular packages. Keeping back those packages seems to be better than spending a lot of CPU time on finding a few solutions - which still was not enough to find _all_ solutions. [Other Info] Originally reported at: https://bugs.launchpad.net/ubuntu/+source /unattended-upgrades/+bug/1396787/comments/21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1824804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824103] Re: aplay record file failed always.
The commit of #7 is in the alsa-lib from 1.1.7, so it only affects 19.04 Disco, the Cosmic and lower version works fine. ** Package changed: linux (Ubuntu) => pulseaudio (Ubuntu) -- 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/1824103 Title: aplay record file failed always. Status in pulseaudio package in Ubuntu: Incomplete Bug description: Test machine: ThinkPad X1 Carbon Image: Ubuntu Disco 19.04 CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, stepping: 0xa) GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) BIOS: N23ET55W (1.30 ) Steps: 1. Install image 19.04 2. Login as default user 3. Open a terminal and type "$ arecord abc.wav" 4. Say something and let laptop recorded your words 5. Cancel the record, please press 'Ctrl + C' 6. Please type "$ aplay abc.wav" in terminal Expected result: The voice played smoothly. Actual result: Step 3, u@u-ThinkPad-X1-Carbon-6th:~$ arecord abc.wav Recording WAVE 'abc.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono ^CAborted by signal Interrupt... arecord: pcm_read:2145: read error: Interrupted system call Step 6, u@u-ThinkPad-X1-Carbon-6th:~$ aplay abc.wav ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave aplay: main:828: audio open error: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1824103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795857] Re: enable CONFIG_DRM_BOCHS
just fyi, this also affects newer iso releases of 18.04 (e.g. 18.04.2) i suspect the new xorg in the hwe version needs the bochs drm module -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824103] [NEW] aplay record file failed always.
You have been subscribed to a public bug: Test machine: ThinkPad X1 Carbon Image: Ubuntu Disco 19.04 CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, stepping: 0xa) GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) BIOS: N23ET55W (1.30 ) Steps: 1. Install image 19.04 2. Login as default user 3. Open a terminal and type "$ arecord abc.wav" 4. Say something and let laptop recorded your words 5. Cancel the record, please press 'Ctrl + C' 6. Please type "$ aplay abc.wav" in terminal Expected result: The voice played smoothly. Actual result: Step 3, u@u-ThinkPad-X1-Carbon-6th:~$ arecord abc.wav Recording WAVE 'abc.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono ^CAborted by signal Interrupt... arecord: pcm_read:2145: read error: Interrupted system call Step 6, u@u-ThinkPad-X1-Carbon-6th:~$ aplay abc.wav ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave aplay: main:828: audio open error: Device or resource busy ** Affects: pulseaudio (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: Incomplete ** Tags: ce-qa-concern disco hwe-audio -- aplay record file failed always. https://bugs.launchpad.net/bugs/1824103 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824961] Re: AppArmor blocks apport python hook from working
I don't have any examples atm, but we know it tries to read cputable at least: /usr/share/dpkg/cputable r It might also need access to apt lists, but this needs investigating /var/lib/apt/lists/** r /etc/apt/apt.conf r /etc/apt/apt.conf.d/** r /etc/apt/sources.list r /etc/apt/sources.list.d/** r maybe /etc/apt/preferences r /etc/apt/preferences.d/** r -- 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/1824961 Title: AppArmor blocks apport python hook from working Status in apparmor package in Ubuntu: New Bug description: The Python profile is very strict, but it prevents Python applications from producing proper crash reports using apport, as the apport hook cannot be loaded, as it requires access to dpkg's cputable, and likely also apt config files and dpkg status files. I'm wondering what the right approach here is: Should the apport hook work under AppArmor, and do we thus have to add the files the hook needs; or should we just say "screw it, we want the additional security" and not get proper error reporting while AppArmor is confining the program? This can be seen in recent autopkgtest failure for kopanocore: + kopano-search --help Traceback (most recent call last): File "/usr/sbin/kopano-search", line 4, in import kopano_search File "/usr/lib/python3/dist-packages/kopano_search/__init__.py", line 18, in from queue import Empty File "/usr/lib/python3.7/queue.py", line 16, in from _queue import Empty ImportError: /usr/lib/python3.7/lib-dynload/_queue.cpython-37m-x86_64-linux-gnu.so: failed to map segment from shared object Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 35, in apt_pkg.init_system() apt_pkg.Error: E:Error reading the CPU table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1824961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824961] Re: AppArmor blocks apport python hook from working
This is specifically not a kopanocore issue, but an issue with all Python programs that have an AppArmor profile. Patching each of them to allow Apport to run vs. the Python abstraction would make no sense. ** Package changed: kopanocore (Ubuntu) => apparmor (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1824961 Title: AppArmor blocks apport python hook from working Status in apparmor package in Ubuntu: New Bug description: The Python profile is very strict, but it prevents Python applications from producing proper crash reports using apport, as the apport hook cannot be loaded, as it requires access to dpkg's cputable, and likely also apt config files and dpkg status files. I'm wondering what the right approach here is: Should the apport hook work under AppArmor, and do we thus have to add the files the hook needs; or should we just say "screw it, we want the additional security" and not get proper error reporting while AppArmor is confining the program? This can be seen in recent autopkgtest failure for kopanocore: + kopano-search --help Traceback (most recent call last): File "/usr/sbin/kopano-search", line 4, in import kopano_search File "/usr/lib/python3/dist-packages/kopano_search/__init__.py", line 18, in from queue import Empty File "/usr/lib/python3.7/queue.py", line 16, in from _queue import Empty ImportError: /usr/lib/python3.7/lib-dynload/_queue.cpython-37m-x86_64-linux-gnu.so: failed to map segment from shared object Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 35, in apt_pkg.init_system() apt_pkg.Error: E:Error reading the CPU table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1824961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824961] [NEW] AppArmor blocks apport python hook from working
You have been subscribed to a public bug: The Python profile is very strict, but it prevents Python applications from producing proper crash reports using apport, as the apport hook cannot be loaded, as it requires access to dpkg's cputable, and likely also apt config files and dpkg status files. I'm wondering what the right approach here is: Should the apport hook work under AppArmor, and do we thus have to add the files the hook needs; or should we just say "screw it, we want the additional security" and not get proper error reporting while AppArmor is confining the program? This can be seen in recent autopkgtest failure for kopanocore: + kopano-search --help Traceback (most recent call last): File "/usr/sbin/kopano-search", line 4, in import kopano_search File "/usr/lib/python3/dist-packages/kopano_search/__init__.py", line 18, in from queue import Empty File "/usr/lib/python3.7/queue.py", line 16, in from _queue import Empty ImportError: /usr/lib/python3.7/lib-dynload/_queue.cpython-37m-x86_64-linux-gnu.so: failed to map segment from shared object Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 35, in apt_pkg.init_system() apt_pkg.Error: E:Error reading the CPU table ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- AppArmor blocks apport python hook from working https://bugs.launchpad.net/bugs/1824961 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824341] Re: NoAllowedOrigin cause package removal
The package unattended-upgrades=1.10ubuntu5 fixes the problem on Ubuntu 18.04 LTS bionic. ** Tags removed: verification-needed verification-needed-disco ** Tags added: verification-done verification-done-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824341 Title: NoAllowedOrigin cause package removal Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: unattended-upgrades remove packages that shouldn't when there is a NoAllowedOrigin exception. Version: unattended-upgrades=1.1ubuntu1.18.04.10 Ubuntu 18.04.2 LTS Description of problem: We have a internal package cliente-ldap that depends on samba, when u-u check for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't clear apt.cache and it removes packages that shouldn't. Log that happens package removal: $ sudo unattended-upgrade -d [...] Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules smbclient Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log debug: call_adjusted samba-common debug: marked_pkg: samba: install=False, upgrade=False, delete=True debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 257, in call_adjusted self.allowed_origins) File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin raise NoAllowedOriginError() NoAllowedOriginError debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True Exception: marking samba-common-bin for removal Keeping auto-removable samba-common-bin package(s) because it would also remove the following packages which should be kept in this step: samba-common marking cliente-ldap for removal (Reading database ... 213413 files and directories currently installed.) Removing cliente-ldap (1:2.17.15) ... marking libcephfs2 for removal (Reading database ... 213392 files and directories currently installed.) Removing libcephfs2 (12.2.11-0ubuntu0.18.04.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... marking ldap-auth-config for removal (Reading database ... 213386 files and directories currently installed.) Removing libpam-ldap:amd64 (186-4ubuntu1) ... Removing ldap-auth-config (0.5.3) ... Removing ldap-auth-client (0.5.3) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking python-samba for removal (Reading database ... 213332 files and directories currently installed.) Removing samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Removing samba-common-bin (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Removing python-samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking nss-updatedb for removal (Reading database ... 212865 files and directories currently installed.) Removing nss-updatedb (10-3build1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking samba-vfs-modules for removal (Reading database ... 212859 files and directories currently installed.) Removing samba-vfs-modules (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking librados2 for removal (Reading database ... 212770 files and directories currently installed.) Removing librados2 (12.2.11-0ubuntu0.18.04.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... marking libibverbs1 for removal (Reading database ... 212761 files and directories currently installed.) Removing ibverbs-providers:amd64 (17.1-1ubuntu0.1) ... Removing libibverbs1:amd64 (17.1-1ubuntu0.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... marking libpam-mount for removal (Reading database ... 212731 files and directories currently installed.) Removing libpam-mount (2.16-3ubuntu0.1) ... Processing triggers for sgml-base (1.29) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking ibverbs-providers for removal marking tdb-tools for removal (Reading database ... 212691 files and directories currently installed.) Removing tdb-tools (1.3.15-2) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking samba-dsdb-modules for removal (Reading database ... 212680 files and directories currently installed.) Removing samba-dsdb-modules
[Touch-packages] [Bug 1824961] Re: AppArmor blocks apport python hook from working
Reassigning to the kopanocore package as that is what contains the problematic profile. ** Package changed: apparmor (Ubuntu) => kopanocore (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1824961 Title: AppArmor blocks apport python hook from working Status in kopanocore package in Ubuntu: New Bug description: The Python profile is very strict, but it prevents Python applications from producing proper crash reports using apport, as the apport hook cannot be loaded, as it requires access to dpkg's cputable, and likely also apt config files and dpkg status files. I'm wondering what the right approach here is: Should the apport hook work under AppArmor, and do we thus have to add the files the hook needs; or should we just say "screw it, we want the additional security" and not get proper error reporting while AppArmor is confining the program? This can be seen in recent autopkgtest failure for kopanocore: + kopano-search --help Traceback (most recent call last): File "/usr/sbin/kopano-search", line 4, in import kopano_search File "/usr/lib/python3/dist-packages/kopano_search/__init__.py", line 18, in from queue import Empty File "/usr/lib/python3.7/queue.py", line 16, in from _queue import Empty ImportError: /usr/lib/python3.7/lib-dynload/_queue.cpython-37m-x86_64-linux-gnu.so: failed to map segment from shared object Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 35, in apt_pkg.init_system() apt_pkg.Error: E:Error reading the CPU table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kopanocore/+bug/1824961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
Sorry for asking this again - is the original issue solved? -- 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/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
It seems this was a red herring. I was testing on battery power which is why the audio was being runtime suspended. The hissing remains constant when the laptop is plugged in. -- 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/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824804] Re: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages
** Description changed: - The fix for LP: #1821101 allowed installing packages for which APT's + [Impact] + + * The fix for LP: #1821101 allowed installing packages for which APT's resolver could not find solution for without adjusting other packages, but also tries to adjust many packages to install packages which are held back. - See: - https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1396787/comments/21 + [Test Case] + + * Set up a system where systemd (or a package that can't be upgraded + without also upgrading other packages) need to be upgraded to the + version in -security. + + * Mark systemd on hold +apt mark hold systemd + + * Observe u-u falling back to adjusting all upgradable packages in + unfixed versions and adjusting only a few in fixed versions: + + # unattended-upgrade --verbose --debug + ... + + adjusting candidate version: libnss-systemd=237-3ubuntu10.19 + falling back to marking libnss-systemd, then adjusting changes + package libnss-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) + falling back to adjusting all packages + adjusting candidate version: 2ping=4.1-1 + ... + + Fixed: + ... + adjusting candidate version: libnss-systemd=237-3ubuntu10.19 + falling back to adjusting libnss-systemd's dependencies recursively + adjusting candidate version: libnss-systemd=237-3ubuntu10.19 + adjusting candidate version: libkmod2=24-1ubuntu3 + adjusting candidate version: mount=2.31.1-0.4ubuntu3 + adjusting candidate version: libmount1=2.31.1-0.4ubuntu3 + ... + + [Regression Potential] + + * The less extensive fallback may not find solutions for installing + packages with special relationships that the full fallback could have + found, but I don't know about such special cases in the archive and the + autopkgtest cover a fair set of popular packages. Keeping back those + packages seems to be better than spending a lot of CPU time on finding a + few solutions - which still was not enough to find _all_ solutions. + + + [Other Info] + + Originally reported at: https://bugs.launchpad.net/ubuntu/+source + /unattended-upgrades/+bug/1396787/comments/21 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824804 Title: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: [Impact] * The fix for LP: #1821101 allowed installing packages for which APT's resolver could not find solution for without adjusting other packages, but also tries to adjust many packages to install packages which are held back. [Test Case] * Set up a system where systemd (or a package that can't be upgraded without also upgrading other packages) need to be upgraded to the version in -security. * Mark systemd on hold apt mark hold systemd * Observe u-u falling back to adjusting all upgradable packages in unfixed versions and adjusting only a few in fixed versions: # unattended-upgrade --verbose --debug ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to marking libnss-systemd, then adjusting changes package libnss-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting all packages adjusting candidate version: 2ping=4.1-1 ... Fixed: ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to adjusting libnss-systemd's dependencies recursively adjusting candidate version: libnss-systemd=237-3ubuntu10.19 adjusting candidate version: libkmod2=24-1ubuntu3 adjusting candidate version: mount=2.31.1-0.4ubuntu3 adjusting candidate version: libmount1=2.31.1-0.4ubuntu3 ... [Regression Potential] * The less extensive fallback may not find solutions for installing packages with special relationships that the full fallback could have found, but I don't know about such special cases in the archive and the autopkgtest cover a fair set of popular packages. Keeping back those packages seems to be better than spending a lot of CPU time on finding a few solutions - which still was not enough to find _all_ solutions. [Other Info] Originally reported at: https://bugs.launchpad.net/ubuntu/+source /unattended-upgrades/+bug/1396787/comments/21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1824804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest
In unapproved ** Changed in: util-linux (Ubuntu) Assignee: Canonical Foundations Team (canonical-foundations) => (unassigned) ** Changed in: ubuntu-power-systems Assignee: Canonical Foundations Team (canonical-foundations) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1764628 Title: incorrect hypervisor and virtualization type reported in compat mode guest Status in The Ubuntu-power-systems project: In Progress Status in util-linux package in Ubuntu: In Progress Bug description: [IMPACT] In xenial lscpu prints the wrong "Hypervisor vendor" and "Virtualization type" on PowerVM or KVM systems. Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC. [TEST] Curent output: ubuntu@P8lpar3:~$ dpkg -l "*util-linux*" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii util-linux 2.31.1-0.4ub ppc64el miscellaneous system utilities un util-linux-loc (no description available) ubuntu@P8lpar3:~$ lscpu Architecture:ppc64le Byte Order: Little Endian CPU(s): 128 On-line CPU(s) list: 0-127 Thread(s) per core: 8 Core(s) per socket: 1 Socket(s): 16 NUMA node(s):2 Model: 2.1 (pvr 004b 0201) Model name: POWER8 (architected), altivec supported Hypervisor vendor: pHyp Virtualization type: para L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): NUMA node4 CPU(s): 0-127 ubuntu@P8lpar3:~$ Expected Output: $ lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):128 On-line CPU(s) list: 0-127 Thread(s) per core:8 Core(s) per socket:1 Socket(s): 16 NUMA node(s): 2 Model: 2.1 (pvr 004b 0201) Model name:POWER8 (architected), altivec supported Hypervisor vendor: pHyp Virtualization type: para L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): NUMA node4 CPU(s): 0-127 [Potential Regression] The fix changes the logic to how lscpu-dmi returns from read_hypervisor_dmi() this could introduce potential regression in platforms that has incorrect DMI information. [Other Info] ---uname output--- Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = boston-LC ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC: root@guest:/tmp# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Model: 2.2 (pvr 004e 1202) Model name:POWER8 (architected), altivec supported >> Hypervisor vendor: horizontal >> Virtualization type: full L1d cache: 32K L1i cache: 32K NUMA node0 CPU(s): 0,1 Stack trace output: no Oops output: no We test what is coming along with distro. If you are not able to see issue with : https://launchpad.net/ubuntu/+source/util- linux/2.27.1-6ubuntu3.5 .. can we get this included in 16.04.x train ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd
Hello Heitor, or anyone else affected, Accepted openldap into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openldap/2.4.46 +dfsg-5ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openldap (Ubuntu Cosmic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Confirmed Status in openldap source package in Bionic: Confirmed Status in openldap source package in Cosmic: Fix Committed Status in openldap package in Debian: New Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) 6) Check if systemd has loaded both /run/systemd/generator.late/slapd.service & /usr/lib/systemd/system/slapd.service.d/slapd-remain-after-exit.conf $ systemctl cat slapd [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about
[Touch-packages] [Bug 1804478] Re: netplan dhcp interface with no default route causes systemd-networkd-wait-online to hang
As with any systemd SRUs, the more testing we do, the better. Can we get both A and B test-cases ran as part of the verification? -- 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/1804478 Title: netplan dhcp interface with no default route causes systemd-networkd- wait-online to hang Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] systemd-networkd, when configured to use ipv4 dhcp for an interface can hang. This triggers in two known cases: a) if configured to ignore the dhcp server's route b) the server provides no route Then systemd-networkd will hang waiting for the interface's configuration to complete (until it times out). This delays boot as well as any restart to systemd-networkd. The fix is backporting upstream commit [1] [1]: https://github.com/systemd/systemd/commit/223932c7 [test case] There are two ways to test this. A) make the system ignore Routes (slightly less realistic but easier to test) configure an interface using systemd-networkd: $ cat /etc/systemd/network/20-ens7.network [Match] Name=ens7 [Network] DHCP=ipv4 [DHCP] UseRoutes=false then reboot, and check: $ systemctl status systemd-networkd-wait-online ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-04-08 23:59:26 UTC; 2min 59s ago [...] Apr 08 23:57:27 lp1804478 systemd[1]: Starting Wait for Network to be Configured... Apr 08 23:57:30 lp1804478 systemd-networkd-wait-online[593]: managing: ens3 Apr 08 23:57:30 lp1804478 systemd-networkd-wait-online[593]: ignoring: lo Apr 08 23:59:26 lp1804478 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Apr 08 23:59:26 lp1804478 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Apr 08 23:59:26 lp1804478 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Apr 08 23:59:26 lp1804478 systemd[1]: Failed to start Wait for Network to be Configured. B) Make a dhcp server to not provide rules Prepare a Ubuntu Bionic Guest under libvirt, e.g. using uvtool: $ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=disco $ uvt-kvm create --password ubuntu bionic arch=amd64 release=bionic label=daily Create a isolated network: $ cat > isolate.xml << EOF isolated EOF $ virsh net-define isolate.xml $ virsh net-start isolate.xml Edit the guest and add that network: $ virsh shutdown bionic $ virsh edit bionic $ virsh edit bionic #add this: In the guest make the device use DHCP: Add this to /etc/netplan/50-cloud-init.yaml ens7: dhcp4: true match: macaddress: 52:54:00:c1:69:08 set-name: ens7 $ sudo netplan apply When rebooting the guest again it will fail ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-04-09 07:07:48 UTC; 1min 41s ago Docs: man:systemd-networkd-wait-online.service(8) Process: 563 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=1/FAILURE) Main PID: 563 (code=exited, status=1/FAILURE) Apr 09 07:05:48 bionic-dgx2 systemd[1]: Starting Wait for Network to be Configured... Apr 09 07:05:50 bionic-dgx2 systemd-networkd-wait-online[563]: managing: ens3 Apr 09 07:07:48 bionic-dgx2 systemd-networkd-wait-online[563]: Event loop failed: Connection timed out Apr 09 07:07:48 bionic-dgx2 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Apr 09 07:07:48 bionic-dgx2 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Apr 09 07:07:48 bionic-dgx2 systemd[1]: Failed to start Wait for Network to be Configured. When working cases A and B will both have the service starting fast and happy. $ sudo systemctl status systemd-networkd-wait-online Active: active (exited) since Tue 2019-04-09 07:17:16 UTC; 12s ago [...] Apr 09 07:17:16 bionic-dgx2 systemd-networkd-wait-online[575]: managing: ens3 [...] Apr 09 07:17:16 bionic-dgx2 systemd-networkd-wait-online[575]: managing: ens7 [regression
[Touch-packages] [Bug 1824864] Re: CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on
amd64, meaning set 18 on arm64 s390x ppc64el.
I have a systemd autopkgtest test that asserts that we see Linux kernel
command line in the dmesg (journalctl -k -b). And it is consistently
failing on arm64 scalingstack KVM EFI machines with messages of "missing
81 kernel messages".
config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
range 12 25
default 17
depends on PRINTK
help
Select the minimal kernel log buffer size as a power of 2.
The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
parameter, see below. Any higher size also might be forced
by "log_buf_len" boot parameter.
Examples:
17 => 128 KB
16 => 64 KB
15 => 32 KB
14 => 16 KB
13 => 8 KB
12 => 4 KB
14 sounds like redictiously low for arm64. given that 17 is default
across 32-bit arches, and 18 is default on amd64.
On a related note, we have CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT
policy<{'amd64': '13', 'arm64': '13', 'armhf': '13', 'i386': '13', 'ppc64el':
'13', 's390x': '13'}>
I'm not sure if we want to bump these up to LOG_BUF_SHIFT size or not.
+ Please backport this to xenial and up.
- Please backport this to xenial and up.
+
+
+ === systemd ===
+
+ systemd, boot-and-services test case can bump the ring buffer before
+ running the tests.
--
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/1824864
Title:
CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in linux source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
New
Status in linux source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
New
Status in linux source package in Cosmic:
Confirmed
Status in systemd source package in Cosmic:
New
Status in linux source package in Disco:
Confirmed
Status in systemd source package in Disco:
New
Status in linux source package in EE-Series:
Confirmed
Status in systemd source package in EE-Series:
New
Bug description:
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on
amd64, meaning set 18 on arm64 s390x ppc64el.
I have a systemd autopkgtest test that asserts that we see Linux
kernel command line in the dmesg (journalctl -k -b). And it is
consistently failing on arm64 scalingstack KVM EFI machines with
messages of "missing 81 kernel messages".
config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
range 12 25
default 17
depends on PRINTK
help
Select the minimal kernel log buffer size as a power of 2.
The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
parameter, see below. Any higher size also might be forced
by "log_buf_len" boot parameter.
Examples:
17 => 128 KB
16 => 64 KB
15 => 32 KB
14 => 16 KB
13 => 8 KB
12 => 4 KB
14 sounds like redictiously low for arm64. given that 17 is default
across 32-bit arches, and 18 is default on amd64.
On a related note, we have CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT
policy<{'amd64': '13', 'arm64': '13', 'armhf': '13', 'i386': '13', 'ppc64el':
'13', 's390x': '13'}>
I'm not sure if we want to bump these up to LOG_BUF_SHIFT size or not.
Please backport this to xenial and up.
=== systemd ===
systemd, boot-and-services test case can bump the ring buffer before
running the tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824864/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804478] Re: netplan dhcp interface with no default route causes systemd-networkd-wait-online to hang
Hello Mikko, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.21 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1804478 Title: netplan dhcp interface with no default route causes systemd-networkd- wait-online to hang Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] systemd-networkd, when configured to use ipv4 dhcp for an interface can hang. This triggers in two known cases: a) if configured to ignore the dhcp server's route b) the server provides no route Then systemd-networkd will hang waiting for the interface's configuration to complete (until it times out). This delays boot as well as any restart to systemd-networkd. The fix is backporting upstream commit [1] [1]: https://github.com/systemd/systemd/commit/223932c7 [test case] There are two ways to test this. A) make the system ignore Routes (slightly less realistic but easier to test) configure an interface using systemd-networkd: $ cat /etc/systemd/network/20-ens7.network [Match] Name=ens7 [Network] DHCP=ipv4 [DHCP] UseRoutes=false then reboot, and check: $ systemctl status systemd-networkd-wait-online ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-04-08 23:59:26 UTC; 2min 59s ago [...] Apr 08 23:57:27 lp1804478 systemd[1]: Starting Wait for Network to be Configured... Apr 08 23:57:30 lp1804478 systemd-networkd-wait-online[593]: managing: ens3 Apr 08 23:57:30 lp1804478 systemd-networkd-wait-online[593]: ignoring: lo Apr 08 23:59:26 lp1804478 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out Apr 08 23:59:26 lp1804478 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Apr 08 23:59:26 lp1804478 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Apr 08 23:59:26 lp1804478 systemd[1]: Failed to start Wait for Network to be Configured. B) Make a dhcp server to not provide rules Prepare a Ubuntu Bionic Guest under libvirt, e.g. using uvtool: $ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=disco $ uvt-kvm create --password ubuntu bionic arch=amd64 release=bionic label=daily Create a isolated network: $ cat > isolate.xml << EOF isolated EOF $ virsh net-define isolate.xml $ virsh net-start isolate.xml Edit the guest and add that network: $ virsh shutdown bionic $ virsh edit bionic $ virsh edit bionic #add this: In the guest make the device use DHCP: Add this to /etc/netplan/50-cloud-init.yaml ens7: dhcp4: true match: macaddress: 52:54:00:c1:69:08 set-name: ens7 $ sudo netplan apply When rebooting the guest again it will fail ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-04-09 07:07:48 UTC; 1min 41s ago
[Touch-packages] [Bug 1665695] Re: OpenSSH PKCS#11 interface does not support ECC.
As mentioned in the upstream bug, they plan to add support in openssh 8.0. But I guess 18.04 won't get the upgrade from openssh 7.x to 8.0. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1665695 Title: OpenSSH PKCS#11 interface does not support ECC. Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Bug description: OpenSSH client doesn't support Eliptics Curve keys on PKCS11 smartcard ssh-keygen -v -D /usr/lib/libeTPkcs11.so debug1: manufacturerID cryptokiVersion 2.20 libraryDescription libraryVersion 9.1 debug1: label manufacturerID model serial <> flags 0x60d C_GetAttributeValue failed: 18 debug1: X509_get_pubkey failed or no rsa debug1: X509_get_pubkey failed or no rsa debug1: X509_get_pubkey failed or no rsa no keys cannot read public key from pkcs11 pkcs11-tool --module /usr/lib/libeTPkcs11.so -O ... Public Key Object; EC EC_POINT 256 bits EC_POINT: 04410474c5423bd0aa44b7825b3e79cd839e06736b18466b131d0884dbf8d946fbdc7f3297e73b998acf56550c303dc972a4dec51b9a3b746d3fe9fb4a44bd84b080fc EC_PARAMS: 06082a8648ce3d030107 label: TestECCpair Usage: encrypt, verify, wrap There is upstream bug: https://bugzilla.mindrot.org/show_bug.cgi?id=2474 Suggested patch: https://bugzilla.mindrot.org/attachment.cgi?id=2728 release: Ubuntu 16.04.2 LTS openssh version: 7.2p2-4ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1665695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers
This bug was fixed in the package apparmor - 2.13.2-9ubuntu6 --- apparmor (2.13.2-9ubuntu6) disco; urgency=medium * lp1824812.patch: set SFS_MOUNTPOINT in is_container_with_internal_policy() since it is sometimes called independently of is_apparmor_loaded() - LP: #1824812 -- Jamie Strandboge Mon, 15 Apr 2019 15:59:54 + ** Changed in: apparmor (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1824812 Title: apparmor does not start in Disco LXD containers Status in AppArmor: Triaged Status in apparmor package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Bug description: In LXD apparmor now skips starting. Steps to reproduce: 1. start LXD container $ lxc launch ubuntu-daily:d d-testapparmor (disco to trigger the issue, cosmic as reference) 2. check the default profiles loaded $ aa-status => This will in cosmic and up to recently disco list plenty of profiles active even in the default install. Cosmic: 25 profiles are loaded. 25 profiles are in enforce mode. Disco: 15 profiles are loaded. 15 profiles are in enforce mode. All those 15 remaining are from snaps. The service of apparmor.service actually states that it refuses to start. $ systemctl status apparmor ... Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor in container I can get those profiles (the default installed ones) loaded, for example: $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient makes it appear 22 profiles are in enforce mode. /sbin/dhclient I was wondering as in my case I found my guest with no (=0) profiles loaded. But as shown above after "apparmor_parser -r" and package install profiles seemed fine. Then the puzzle was solved, on package install they will call apparmor_parser via the dh_apparmor snippet and it is fine. To fully disable all of them: $ lxc stop $ lxc start $ lxc exec d-testapparmor aa-status apparmor module is loaded. 0 profiles are loaded. 0 profiles are in enforce mode. 0 profiles are in complain mode. 0 processes have profiles defined. 0 processes are in enforce mode. 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. That would match the service doing an early exit as shown in systemctl status output above. The package install or manual load works, but none are loaded by the service automatically e.g. on container restart. --- --- --- This bug started as: Migrations to Disco trigger "Unable to find security driver for model apparmor" This most likely is related to my KVM-in-LXD setup but it worked fine for years and I'd like to sort out what broke. I have migrated to Disco's qemu 3.1 already which makes me doubts generic issues in qemu 3.1 in general. The virt tests that run cross release work fine starting from X/B/C but all those chains fail at mirgating to Disco now with: $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live kvmguest-bionic-normal qemu+ssh://10.21.151.207/system error: unsupported configuration: Unable to find security driver for model apparmor I need to analyze what changed To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1824812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers
** Tags added: shiftfs -- 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/1824812 Title: apparmor does not start in Disco LXD containers Status in AppArmor: Triaged Status in apparmor package in Ubuntu: In Progress Status in libvirt package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Bug description: In LXD apparmor now skips starting. Steps to reproduce: 1. start LXD container $ lxc launch ubuntu-daily:d d-testapparmor (disco to trigger the issue, cosmic as reference) 2. check the default profiles loaded $ aa-status => This will in cosmic and up to recently disco list plenty of profiles active even in the default install. Cosmic: 25 profiles are loaded. 25 profiles are in enforce mode. Disco: 15 profiles are loaded. 15 profiles are in enforce mode. All those 15 remaining are from snaps. The service of apparmor.service actually states that it refuses to start. $ systemctl status apparmor ... Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor in container I can get those profiles (the default installed ones) loaded, for example: $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient makes it appear 22 profiles are in enforce mode. /sbin/dhclient I was wondering as in my case I found my guest with no (=0) profiles loaded. But as shown above after "apparmor_parser -r" and package install profiles seemed fine. Then the puzzle was solved, on package install they will call apparmor_parser via the dh_apparmor snippet and it is fine. To fully disable all of them: $ lxc stop $ lxc start $ lxc exec d-testapparmor aa-status apparmor module is loaded. 0 profiles are loaded. 0 profiles are in enforce mode. 0 profiles are in complain mode. 0 processes have profiles defined. 0 processes are in enforce mode. 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. That would match the service doing an early exit as shown in systemctl status output above. The package install or manual load works, but none are loaded by the service automatically e.g. on container restart. --- --- --- This bug started as: Migrations to Disco trigger "Unable to find security driver for model apparmor" This most likely is related to my KVM-in-LXD setup but it worked fine for years and I'd like to sort out what broke. I have migrated to Disco's qemu 3.1 already which makes me doubts generic issues in qemu 3.1 in general. The virt tests that run cross release work fine starting from X/B/C but all those chains fail at mirgating to Disco now with: $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live kvmguest-bionic-normal qemu+ssh://10.21.151.207/system error: unsupported configuration: Unable to find security driver for model apparmor I need to analyze what changed To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1824812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
Thank you for your bug report. Could you attach your journalctl log from that shutdown to the bug? The log on https://launchpadlibrarian.net/419441276/SystemdFailedUnits.txt also shows that some systemd unit are failing on your system, maybe one of those is creating the issue... (also when it's hanging can you switch into another vt for debugging?) ** Changed in: systemd (Ubuntu) Importance: Undecided => Low ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: Incomplete Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) dmi.bios.date: 07/02/07 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MP21.88Z.007F.B06.0707021348 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F4208DC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208DC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: dmi.product.family: MacPro dmi.product.name: MacPro2,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
