[Touch-packages] [Bug 1572752] Re: improve UTC setting migration on upgrades
This appears to still be unresolved. What are the next steps? Do we still want to add a Pre-Depends? How will d-i and image builds be verified to not regress? ** Changed in: sysvinit (Ubuntu Xenial) Status: In Progress => Triaged ** Changed in: sysvinit (Ubuntu Xenial) Assignee: Steve Langasek (vorlon) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1572752 Title: improve UTC setting migration on upgrades Status in sysvinit package in Ubuntu: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: [SRU Justification] On upgrade, some users who have selected a non-default setting for their clock handling in the installer will see prompts for a conffile they never edited by hand. [Regression potential] Because we are adding a pre-dependency to a package, there is risk of this causing upgrade failures. The upgrade path should be tested aggressively with different profiles from both 14.04 and 15.10 before publishing to -updates. [Test case] 1. On a newly-installed 14.04 system, edit /etc/default/rcS to contain 'UTC=no' instead of 'UTC=yes'. Make no other changes to this file. 2. Enable -proposed in your apt sources. 3. Run do-release-upgrade or update-manager to upgrade to 16.04. 4. Confirm that the upgrade succeeds. 5. Confirm that you are not shown a conffile prompt for /etc/default/rcS on upgrade. 6. Confirm that /etc/adjtime has been created, with 'LOCAL' as the third line of the file. 7. Repeat steps 1-6 for a newly-installed 15.10 system. slangasek | pitti: I see sysvinit Breaks: systemd (<< 228-5ubuntu3), but that doesn't enforce systemd 228-5ubuntu3 being configured before sysvinit, which means the conffile may already be migrated away before systemd postinst runs... I think the right way to do this is with initscripts Pre-Depends: systemd, and for initscripts' preinst script to handle any conffile cleaning so that users are spared conffile prompts on upgrade pitti | slangasek: ah, good point; this needs to be tested thoroughly, pre-depends have some habit of causing trouble See bug 1541532 and http://launchpadlibrarian.net/236311219/systemd_228-5ubuntu2_228-5ubuntu3.diff.gz and http://launchpadlibrarian.net/236367969/sysvinit_2.88dsf-59.3ubuntu1_2.88dsf-59.3ubuntu2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1572752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
** Tags added: rls-x-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Trusty: In Progress Status in rsyslog source package in Xenial: In Progress Status in rsyslog source package in Zesty: Won't Fix Status in rsyslog source package in Artful: Fix Released Status in rsyslog package in Debian: Fix Released Bug description: [Impact] Servers or cloud instances will not log important messages after initial deployment. Manual reboot or restart of services is necessary to get expected behaviour. [Test Case] 1) Install, enable and start haproxy 2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed 3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT created 4) Restart rsyslog service 5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created 6) Restart haproxy service and observe that log now is filled with entries With the patched deb steps 3,4 and 6 becomes irrelevant and everything works out of the box. [Regression Potential] Minimal. This patch merges a patch from Debian where a trigger is added to the rsyslog package that fires when other debs drop files into /etc/rsyslog.d. [Original Bug Description] rsyslog should reload its configuration when other packages drop configuration in /etc/rsyslog.d https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337 https://anonscm.debian.org/cgit/collab- maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302777] Re: Bluetooth turns itself off continuously.
I'm surprised that this bug still isn't getting fixed. I'm having the same problem in 18.04. Doesn't anyone use Bluetooth? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1302777 Title: Bluetooth turns itself off continuously. Status in bluez package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 64 bit daily build, fully updated to today (April 4, 2014). I noticed on my Lenovo E430 when I try to enable bluetooth, it continuously disables itself. I installed "Bluetooth Manager" from the Software Center and it activated and stayed lit like it should have. Once I removed Bluetooth Manager, disabled Bluetooth, and tried to enable again, it failed despite having the default "Bluetooth" application installed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 15:06:15 2014 InstallationDate: Installed on 2014-04-04 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 3254CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic root=UUID=58de4412-6390-4ffc-abeb-3d7978795c18 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET32WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 3254CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH0ET32WW(1.14):bd06/15/2012:svnLENOVO:pn3254CTO:pvrThinkPadEdgeE430:rvnLENOVO:rn3254CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3254CTO dmi.product.version: ThinkPad Edge E430 dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1302777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604737] Re: headless installations are degraded due to failed setvtrgb.service
Assigning Dimitri who last updated this; is it still an issue? ** Changed in: console-setup (Ubuntu Xenial) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- 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/1604737 Title: headless installations are degraded due to failed setvtrgb.service Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Xenial: In Progress Bug description: s390x installations are degraded due to failed setvtrgb.service on z/vm, suspecting that it should be limited to just kvm on s390x, somehow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1604737/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825378] Re: systemd-networkd doesn't set wireguard peer endpoint
I don't have access to the affected systems at the moment, but the test case and your summary looks correct. Thanks for taking a look at this. -- 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/1825378 Title: systemd-networkd doesn't set wireguard peer endpoint Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [impact] systemd does not set endpoints for wireguard interfaces correctly. This makes wireguard unusable. [test case] install a disco or eoan system and set up a wireguard interface: $ sudo add-apt-repository ppa:wireguard/wireguard $ sudo apt install wireguard ...(this does a lot of stuff)... create a file as below; There is no need to setup remote server to reproduce this issue, but PublicKey/PrivateKey should be valid one (used instructions from https://www.linode.com/docs/networking/vpn /set-up-wireguard-vpn-on-ubuntu/#configure-wireguard-server): $ cat /etc/systemd/network/wg0.netdev [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=uMuCbguKYdKanRYMbDSriIdgxGxJR57Us1zEy8wRc1M= ListenPort=51820 [WireGuardPeer] PublicKey=ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 $ sudo systemctl restart systemd-networkd $ sudo wg show wg0 interface: wg0 public key: BnvFgvPiVb5xURfzZ5liV1P77qeGeJDIX3C1iNquA2k= private key: (hidden) listening port: 51820 peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= allowed ips: 10.0.0.0/8 the last command should print remote endpoint address, e.g.: peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 [regression potential] any changes to systemd contain the potential for serious regressions. However, this is cherry picked directly from upstream, with the releases requiring patching (disco and eoan) being at exactly the same version and very close to upstream already. Additionally, while this does add 2 new functions (from upstream commit https://github.com/systemd/systemd/pull/11580/commits/abd48ec87f2ac5dd571a99dcb4db88c4affdffc8), they are only used - and code is only changed in - wireguard.c, so any regressions should be limited to wireguard interfaces (unless systemd crashes completely). [other info] this bug is not present in cosmic and earlier, and is already fixed in upstream systemd, so this is needed only for disco and eoan. original description: --- systemd/disco 240 shipped with Ubuntu 19.04 beta does not set endpoints for [WireguradPeer] properly. This regression was introduced in v241 and merged into v240. systemd 241 doesn't set wireguard peer endpoint https://github.com/systemd/systemd/issues/11579 Revert of the regression was landed on v240 stable branch https://github.com/systemd/systemd-stable/pull/39 1)2) confirmed with, systemd/disco 240-6ubuntu5 amd64 3) put a netdev file /etc/systemd/network/wg0.netdev --- [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=** ListenPort=51820 [WireGuardPeer] PublicKey=* AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 and run --- # systemctl restart systemd-networkd # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * allowed ips: 10.0.0.0/8 4) the last command should print remote endpoint address. --- # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825378/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
** Changed in: rsyslog (Ubuntu Zesty) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Trusty: In Progress Status in rsyslog source package in Xenial: In Progress Status in rsyslog source package in Zesty: Won't Fix Status in rsyslog source package in Artful: Fix Released Status in rsyslog package in Debian: Fix Released Bug description: [Impact] Servers or cloud instances will not log important messages after initial deployment. Manual reboot or restart of services is necessary to get expected behaviour. [Test Case] 1) Install, enable and start haproxy 2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed 3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT created 4) Restart rsyslog service 5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created 6) Restart haproxy service and observe that log now is filled with entries With the patched deb steps 3,4 and 6 becomes irrelevant and everything works out of the box. [Regression Potential] Minimal. This patch merges a patch from Debian where a trigger is added to the rsyslog package that fires when other debs drop files into /etc/rsyslog.d. [Original Bug Description] rsyslog should reload its configuration when other packages drop configuration in /etc/rsyslog.d https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337 https://anonscm.debian.org/cgit/collab- maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829430] Re: [nouveau] Xorg freeze
Thanks for the bug report. 1. If you have any gnome-shell extensions (other than the default Ubuntu ones) then please uninstall them and retest. We find a large number of bugs are caused by Gnome extensions. 2. Your kernel log mentions a few errors from the nouveau kernel driver: [ 274.310794] nouveau :01:00.0: bus: MMIO read of FAULT at 619444 [ IBUS ] [ 274.959650] nouveau :01:00.0: bus: MMIO read of FAULT at 619444 [ IBUS ] [ 294.627149] nouveau :01:00.0: bus: MMIO read of FAULT at 619444 [ IBUS ] [ 305.108717] nouveau :01:00.0: bus: MMIO read of FAULT at 619444 [ IBUS ] but we can't know for sure if those are related to what you see. Please try installing the proprietary Nvidia driver instead, as it usually provides better stability: sudo apt install nvidia-driver-418 I am confident one of those two suggestions will solve the problem. Please tell us which (if any) works. ** Summary changed: - Xorg freeze + [nouveau] Xorg freeze ** Tags added: nouveau ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829430 Title: [nouveau] Xorg freeze Status in Ubuntu: Incomplete Bug description: Every time i press the "windows" key which is by default mapped to "launch gnome search" the search launches but i cannot close it. The Escape key doesn't work at all and as far as i know the only solution to this problem is to log out and login again. This didnt occur when I was using 18.10 but after the upgrade to 19.04 this is indeed a problem. I'm aware that this issue might have something to so with the graphics drivers. root@aeshatter-XPS-15-9550:/home/aeshatter# lshw -c video *-display description: 3D controller product: GM107M [GeForce GTX 960M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:126 memory:dc00-dcff memory:b000-bfff memory:c000-c1ff ioport:e000(size=128) memory:dd00-dd07 *-display description: VGA compatible controller product: HD Graphics 530 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:127 memory:db00-dbff memory:7000-7fff ioport:f000(size=64) memory:c-d ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 16 22:00:45 2019 DistUpgraded: 2019-05-06 07:50:18,514 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell XPS 15 9550 [1028:06e4] Subsystem: Dell XPS 15 9550 [1028:06e4] InstallationDate: Installed on 2016-06-07 (1073 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=a31f340c-9c8b-441e-a80e-2684dd9d9ae9 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to disco on 2019-05-06 (10 days ago) dmi.bios.date: 10/11/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd10/11/2018:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name:
[Touch-packages] [Bug 1537635] Re: Reduce zlib compression level for massive performance increase
** Changed in: apport (Ubuntu Eoan) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu Eoan) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1537635 Title: Reduce zlib compression level for massive performance increase Status in Apport: In Progress Status in apport package in Ubuntu: In Progress Status in apport source package in Eoan: In Progress Bug description: When apport takes a core dump of a large application, it uses 100% CPU for a _long_ time (often 30 seconds or more) to compress the core dump. The system is virtually unusable during this time, especially if the application was the window manager and won’t be restarted until the core dump is complete. This is a longstanding known problem; it motivated the switch from bzip2 to zlib level 9 back in apport 0.24. That made it much better, but it’s still quite bad. So why not switch from zlib level 9 to zlib level 1? I tested this on a core dump of gnome-shell, and while it increased the size of the .crash file by 24% (68.5 MB to 85.0 MB), it decreased the needed CPU time by a FACTOR OF EIGHT (58.6 seconds to 7.3 seconds). This tradeoff seems more than worthwhile for this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1537635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664844] Re: No distinction between link-up and link-down interfaces
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags removed: verification-done-artful verification-done-xenial verification-done-zesty ** Changed in: systemd (Ubuntu) Status: New => In Progress ** Changed in: systemd (Ubuntu Zesty) Status: New => Won't Fix ** Package changed: nplan (Ubuntu) => netplan.io (Ubuntu) ** Changed in: systemd (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: netplan.io (Ubuntu Xenial) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Bug description: [Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan will not be able to do anything "nice" for the interface, such as rename it to what the user specified in MAAS. If I include the interface but don't specify any addresses or DHCP, it isn't clear if it will be link up (my current assumption) or link down. There should be a way to allow an interface to be recognized by netplan (and even partially configured, waiting for the user to run something like 'ifup ' on a manual but not auto-started interface in ifupdown), but marked administratively disabled. (adminStatus down) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
It is fixed in Ubuntu Bionic and late but this LP bug have never been mentioned in the changelog, which explains why the status didn't change until now (after a manual status change from my part) Xenial hasn't been fix, I did some quick verification and base on the fix, which add a Depends as follow: debian/control: init-system-helpers (>= 1.47~) and considering rmadison: init-system-helpers | 1.29ubuntu1 | xenial | source, all init-system-helpers | 1.29ubuntu4 | xenial-updates | source, all I'm afraid the fix won't work for Xenial. With that being said, I will set Xenial to "Won't fix". Please feel free to re-open it if you judge Xenial need the fix by providing good justification/rational. - Eric ** Changed in: rsyslog (Ubuntu Zesty) Status: Won't Fix => Fix Released ** Changed in: rsyslog (Ubuntu Xenial) Status: In Progress => Fix Released ** Changed in: rsyslog (Ubuntu Xenial) Status: Fix Released => Won't Fix ** Changed in: rsyslog (Ubuntu Trusty) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Trusty: Won't Fix Status in rsyslog source package in Xenial: Won't Fix Status in rsyslog source package in Zesty: Fix Released Status in rsyslog source package in Artful: Fix Released Status in rsyslog package in Debian: Fix Released Bug description: [Impact] Servers or cloud instances will not log important messages after initial deployment. Manual reboot or restart of services is necessary to get expected behaviour. [Test Case] 1) Install, enable and start haproxy 2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed 3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT created 4) Restart rsyslog service 5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created 6) Restart haproxy service and observe that log now is filled with entries With the patched deb steps 3,4 and 6 becomes irrelevant and everything works out of the box. [Regression Potential] Minimal. This patch merges a patch from Debian where a trigger is added to the rsyslog package that fires when other debs drop files into /etc/rsyslog.d. [Original Bug Description] rsyslog should reload its configuration when other packages drop configuration in /etc/rsyslog.d https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337 https://anonscm.debian.org/cgit/collab- maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
It is fixed in Ubuntu Bionic and late but this LP bug have never been mentioned in the changelog, which explains why the status didn't change until now (after a manual status change from my part) Trusty and Xenial hasn't been fix, I did some quick verifications and base on the fix, which add a Depends as follow: debian/control: init-system-helpers (>= 1.47~) and considering rmadison: init-system-helpers | 1.29ubuntu1 | xenial | source, all init-system-helpers | 1.29ubuntu4 | xenial-updates | source, all init-system-helpers | 1.14| trusty | source, all init-system-helpers | 1.14ubuntu1 | trusty-updates | source, all I'm afraid the fix won't work for Trusty and Xenial. Trusty is also in EOL. With that being said, I will set Trusty/Xenial to "Won't fix". Please feel free to re-open it if you judge Xenial need the fix by providing good justification/rational. - Eric ** Tags removed: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Trusty: Won't Fix Status in rsyslog source package in Xenial: Won't Fix Status in rsyslog source package in Zesty: Fix Released Status in rsyslog source package in Artful: Fix Released Status in rsyslog package in Debian: Fix Released Bug description: [Impact] Servers or cloud instances will not log important messages after initial deployment. Manual reboot or restart of services is necessary to get expected behaviour. [Test Case] 1) Install, enable and start haproxy 2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed 3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT created 4) Restart rsyslog service 5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created 6) Restart haproxy service and observe that log now is filled with entries With the patched deb steps 3,4 and 6 becomes irrelevant and everything works out of the box. [Regression Potential] Minimal. This patch merges a patch from Debian where a trigger is added to the rsyslog package that fires when other debs drop files into /etc/rsyslog.d. [Original Bug Description] rsyslog should reload its configuration when other packages drop configuration in /etc/rsyslog.d https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337 https://anonscm.debian.org/cgit/collab- maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
Strange, that link seems to suggest it is in proposed already, but when I try to run 'do-release-upgrade -p -f DistUpgradeViewNonInteractive', I don't seem to get that. Do I need to do some other manual step to get it first, or do I need it from xenial instead since that's where I'm coming from? Even though I used -p, proposed doesn't seem to be on in /etc/apt/source.list (after I got the error from above again, I killed the upgrader and checked this) $ apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:18.04.32 Candidate: 1:18.04.32 Version table: *** 1:18.04.32 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1:18.04.17 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages -- 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: Fix Committed Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to
[Touch-packages] [Bug 1829400] Re: [Intel Core 2 Duo T7250] screen loop after suspension. Kernel 4.15 fails but 4.4.0 works.
Thanks for the bug report. Please try to find the two closest kernel versions where one works and one doesn't. You can download them from: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ** Summary changed: - screen loop after suspension + [Intel Core 2 Duo T7250] screen loop after suspension. Kernel 4.15 fails but 4.4.0 works. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829400 Title: [Intel Core 2 Duo T7250] screen loop after suspension. Kernel 4.15 fails but 4.4.0 works. Status in linux package in Ubuntu: New Bug description: Hello, I have a DELL PA-10 wtih GM965 intel graphic card. It couldn't boot with 4.15 kernel and I have to use 4.4.0. I'm using the default driver, I didn't find an other. The computer boot faster aplying this fix but I continue to have a problem with the suspension. After after a suspension the screen blink between two kind of blank screen and never start. Is there a solution for that? Thanks, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 16 17:03:54 2019 DistUpgraded: 2019-04-27 17:06:11,246 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude D630 [1028:01f9] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:01f9] InstallationDate: Installed on 2016-06-18 (1062 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Dell Inc. Latitude D630 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-146-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2019-04-27 (18 days ago) dmi.bios.date: 11/24/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd11/24/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829364] Re: Will not play sound via HDMI unless you run pavucontrol first
When pavucontrol is not running, it depends on sample rate of playback, whether or not the sound is audible: $ speaker-test -r 48000 not audible $ speaker-test -r 47999 audible -- 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/1829364 Title: Will not play sound via HDMI unless you run pavucontrol first Status in pulseaudio package in Ubuntu: New Bug description: Does not play sound via sink output:iec958-stereo unless I start pavucontrol before running the player such as paplay. Player does not show any error and takes its time to play, but there is no sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825448] Re: gnupg2 autopkgtest 'simple-tests' should be included in x/b/c
** Tags added: rls-x-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1825448 Title: gnupg2 autopkgtest 'simple-tests' should be included in x/b/c Status in gnupg package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Fix Released Status in gnupg source package in Xenial: In Progress Status in gnupg2 source package in Xenial: In Progress Status in gnupg2 source package in Bionic: In Progress Status in gnupg2 source package in Cosmic: In Progress Bug description: [impact] b/c currently only have gpgv-win32 test, which is limited in what it tests and what archs it runs on. additionally, it always fails (see bug 1825186). x currently has no tests at all for gnupg or gnupg2. [test case] run autopkgtests for gnupg2 on b/c. [regession potential] adding a testcase may result in the testcase incorrectly failing in the future. [other info] this test case is cherry-picked from gnupg2 in disco. the test case required slight modification for gnupg v1, as 'Key-Type: default' only works with v2. Note that Xenial is the last release that carries gnupg v1; Bionic and later carry only gnupg v2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1825448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825186] Re: gpgv-win32 autopkgtest always fails
** Tags added: rls-x-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1825186 Title: gpgv-win32 autopkgtest always fails Status in gnupg package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Opinion Status in gnupg source package in Xenial: In Progress Status in gnupg2 source package in Bionic: In Progress Status in gnupg2 source package in Cosmic: In Progress Status in gnupg2 source package in Disco: Fix Released Bug description: [impact] gpgv-win32 autopkgtest always fails [test case] check http://autopkgtest.ubuntu.com/packages/g/gnupg2 or run autopkgtest manually note the gpgv-win32 test is skipped on ppc64el and s390x for b/c, and has been removed from d/t/control entirely in d [regression potential] little to none; this affects the test case only [other info] as mentioned, in disco, the gpgv-win32 test has been removed from the tests/control completely. not sure if that is a better approach than fixing the test case. For now, I marked this Fix Released for disco since it doesn't fail there (since the testcase was removed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1825186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828892] Re: systemctl - alias service reports inactive while aliased is active
@joalif shouldn't we include the manpage correction as well? https://github.com/systemd/systemd/pull/7997/commits/71c9f49d730c8e8d072258f5ba30fc1ff360ce91 -- 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/1828892 Title: systemctl - alias service reports inactive while aliased is active Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Bug description: [Impact] 'systemctl is-active' command reports an alias service as inactive even though the aliased service is active. Currently the 'systemctl is-active' command does not load units to minimise its effect on the system (i.e. that a monitoring command does not itself alter the state of the system). However, this behaviour leads to inconsistencies when services are aliased. [Test case] - Test case 1 - libvirtd alias service : libvirtd aliased service : libvirt-bin /etc/systemd/system$ ls -la libvirtd.service lrwxrwxrwx 1 root root 39 May 13 20:49 libvirtd.service -> /lib/systemd/system/libvirt-bin.service $ systemctl is-active libvirtd inactive $ systemctl is-active libvirt-bin active - Test case 2 - sshd alias service : sshd aliased service : ssh /ect/systemd/system$ ls -la sshd.service lrwxrwxrwx 1 root root 31 Mar 19 19:44 sshd.service -> /lib/systemd/system/ssh.service $ systemctl is-active sshd inactive $ systemctl is-active ssh active [Regression Potential] This fix may result into systemctl reporting inconsistent information concerning the status of a service. [Other] Upstream issue : https://github.com/systemd/systemd/issues/7875 Upstream fix : https://github.com/systemd/systemd/pull/7997 Xenial is affected, fix exists on Bionic onward. $ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $ apt-cache policy systemd systemd: Installed: 229-4ubuntu21.21 Candidate: 229-4ubuntu21.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780985] Re: apport-unpack crashed with ValueError in extract_keys(): ['ProcEnviron'] has no binary content
** 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1780985 Title: apport-unpack crashed with ValueError in extract_keys(): ['ProcEnviron'] has no binary content Status in apport package in Ubuntu: New Bug description: Sometimes apport creates a crash file with an empty field for 'ProcEnviron'. In that situation, I want to be able to continue extracting fields from the crash file rather than aborting. Workaround is to add some made up values for ProcEnviron in the crash file, such as " LANG=en_US.UTF-8 ". ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jul 10 08:02:35 2018 ExecutablePath: /usr/bin/apport-unpack InstallationDate: Installed on 2018-04-27 (73 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-unpack /var/crash/_usr_bin_kdeinit5.1000.crash crash_files/ Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonArgs: ['/usr/bin/apport-unpack', '/var/crash/_usr_bin_kdeinit5.1000.crash', 'crash_files/'] PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 SourcePackage: apport Title: apport-unpack crashed with ValueError in extract_keys(): ['ProcEnviron'] has no binary content UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio bluetooth cdrom dialout dip floppy lpadmin netdev plugdev sambashare scanner sudo systemd-journal tty vboxusers video wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-05-18T07:41:41.681859 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1780985/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806012] Re: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server
** Tags added: rls-x-notfixing -- 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/1806012 Title: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Bug description: Whilst debugging 'slow instance performance' on a Ubuntu Bionic based cloud, I observed that the default cpu governor configuration was set to 'powersave'; toggling this to 'performance' (while in not anyway a particularly green thing todo) resulted in the instance slowness disappearing and the cloud performance being as expected (based on a prior version of the deploy on Ubuntu Xenial). AFAICT Xenial does the same thing albeit in a slight different way, but we definitely did not see the same performance laggy-ness under a Xenial based cloud. Raising against systemd (as this package sets the governor to 'powersave') - I feel that the switch to 'performance' although appropriate then obscures what might be a performance/behavioural difference in the underlying kernel when a machine is under load. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.9 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 30 10:05:46 2018 Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=a361a524-47eb-46c3-8a04-e5eaa65188c9 ro hugepages=103117 iommu=pt intel_iommu=on SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828892] Re: systemctl - alias service reports inactive while aliased is active
** Tags added: rls-x-notfixing -- 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/1828892 Title: systemctl - alias service reports inactive while aliased is active Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Bug description: [Impact] 'systemctl is-active' command reports an alias service as inactive even though the aliased service is active. Currently the 'systemctl is-active' command does not load units to minimise its effect on the system (i.e. that a monitoring command does not itself alter the state of the system). However, this behaviour leads to inconsistencies when services are aliased. [Test case] - Test case 1 - libvirtd alias service : libvirtd aliased service : libvirt-bin /etc/systemd/system$ ls -la libvirtd.service lrwxrwxrwx 1 root root 39 May 13 20:49 libvirtd.service -> /lib/systemd/system/libvirt-bin.service $ systemctl is-active libvirtd inactive $ systemctl is-active libvirt-bin active - Test case 2 - sshd alias service : sshd aliased service : ssh /ect/systemd/system$ ls -la sshd.service lrwxrwxrwx 1 root root 31 Mar 19 19:44 sshd.service -> /lib/systemd/system/ssh.service $ systemctl is-active sshd inactive $ systemctl is-active ssh active [Regression Potential] This fix may result into systemctl reporting inconsistent information concerning the status of a service. [Other] Upstream issue : https://github.com/systemd/systemd/issues/7875 Upstream fix : https://github.com/systemd/systemd/pull/7997 Xenial is affected, fix exists on Bionic onward. $ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $ apt-cache policy systemd systemd: Installed: 229-4ubuntu21.21 Candidate: 229-4ubuntu21.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825856] Re: gnupg package 'gpgv-udeb' conflicts with gnupg2 (xenial)
** Tags added: rls-x-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1825856 Title: gnupg package 'gpgv-udeb' conflicts with gnupg2 (xenial) Status in gnupg package in Ubuntu: Fix Released Status in gnupg source package in Xenial: In Progress Bug description: [impact] both the 'gnupg' and 'gnupg2' sources build 'gpgv-udeb' for xenial. therefore, gnupg FTUFS since its version is < gnupg2 version. [test case] attempt to upload 'gnupg' and 'gnupg2' into a PPA. for example see this ppa: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1825186/+packages?field.name_filter=_filter=superseded_filter= version 1.4.20-1ubuntu3.3+bug1825186v20190422b1 shows this problem; all archs failed because: INFO gpgv-udeb_1.4.20-1ubuntu3.3+bug1825186v20190422b1_amd64.udeb: Version older than that in the archive. 1.4.20-1ubuntu3.3+bug1825186v20190422b1 <= 2.1.11-6ubuntu2.1+bug1825186v20190419b3 from: https://launchpadlibrarian.net/420547534/upload_16673848_log.txt [regression potential] low; the gpgv-udeb pkg is provided by gnupg2 in xenial and should not be built by gnupg. [other info] the v1 pkg is not what is reported by rmadison: $ rmadison gpgv-udeb | grep xenial gpgv-udeb | 2.1.11-6ubuntu2| xenial/main/debian-installer | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x gpgv-udeb | 2.1.11-6ubuntu2.1 | xenial-security/main/debian-installer | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x gpgv-udeb | 2.1.11-6ubuntu2.1 | xenial-updates/main/debian-installer | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1825856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829017] Re: [SRU] Enable support for Train Cloud Archive
This bug was fixed in the package software-properties - 0.98.2 --- software-properties (0.98.2) eoan; urgency=medium * cloudarchive: Enable support for the Train Ubuntu Cloud Archive on 18.04 (LP: #1829017). -- Corey Bryant Tue, 14 May 2019 09:51:17 -0400 ** Changed in: software-properties (Ubuntu Eoan) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1829017 Title: [SRU] Enable support for Train Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Triaged Status in software-properties source package in Eoan: Fix Released Bug description: Please add support for: cloud-archive:train cloud-archive:train-proposed This will also need to be SRU'd back to bionic. [Impact] End users have to manually enable the train cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:train sudo add-apt-repository cloud-archive:train-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824002] Re: python3-launchpadlib needs promotion from suggests
** Changed in: apport (Ubuntu) Status: Triaged => In Progress ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Tags removed: rls-ee-incoming ** Also affects: apport (Ubuntu Eoan) Importance: Medium Assignee: Brian Murray (brian-murray) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1824002 Title: python3-launchpadlib needs promotion from suggests Status in apport package in Ubuntu: In Progress Status in apport source package in Eoan: In Progress Bug description: If one wants to apport-collect, one gets an error about python3-launchpadlib needing to be installed. One can easily install it, but it really should be a Recommend, if not a Depend so one doesn't have to go through this trouble. Right now, it's a Suggest. It seems that during the whole Python2/3 transition some things got switched around, but it had been a Depend for a long time before that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1824002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302777] Re: Bluetooth turns itself off continuously.
JaSaunders, Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer release and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is still a paid support option: https://www.ubuntu.com/esm --- Grashdur, We released a fix that might help you just today, so please try that: https://launchpad.net/ubuntu/+source/gnome-bluetooth/3.28.0-2ubuntu0.2 If that doesn't help then please open a new bug by running: ubuntu-bug bluez ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1302777 Title: Bluetooth turns itself off continuously. Status in bluez package in Ubuntu: Won't Fix Bug description: Ubuntu 14.04 64 bit daily build, fully updated to today (April 4, 2014). I noticed on my Lenovo E430 when I try to enable bluetooth, it continuously disables itself. I installed "Bluetooth Manager" from the Software Center and it activated and stayed lit like it should have. Once I removed Bluetooth Manager, disabled Bluetooth, and tried to enable again, it failed despite having the default "Bluetooth" application installed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 15:06:15 2014 InstallationDate: Installed on 2014-04-04 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 3254CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic root=UUID=58de4412-6390-4ffc-abeb-3d7978795c18 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET32WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 3254CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH0ET32WW(1.14):bd06/15/2012:svnLENOVO:pn3254CTO:pvrThinkPadEdgeE430:rvnLENOVO:rn3254CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3254CTO dmi.product.version: ThinkPad Edge E430 dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1302777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563026] Re: LXC/LXD installed by default on Ubuntu server
This is a more complex issue; it's not just about LXD, but the general story for installing "minimal" installs. The fact that openssh-server was not installed as part of the ubuntu- server is a separate bug we've covered in a different bug report. Currently, desktops allow picking a "full" install or "minimal" installation. You also somewhat have that option for the d-i mini.iso; but IIRC not really on the new Subiquity installer. I think this needs to be a larger question than just for LXD; and will need addressing elsewhere than in ubuntu-meta in any case. Reassigning to debian-cd (where we have the grub menus and more magic for selecting "minimal" install). ** Package changed: ubuntu-meta (Ubuntu) => debian-cd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1563026 Title: LXC/LXD installed by default on Ubuntu server Status in debian-cd package in Ubuntu: Confirmed Bug description: When performing a new installation of Ubuntu server 16.04 Beta 2, LXC and LXD are included in the default packages even when "Virtual Server" is not selected as an installation task. This brings in all of the required dependencies as well, obviously, which seems like it is not the best default behavior to have. When installing from a non-UEFI boot, the user may select "minimal install" from the "F4" menu. This menu is not available from the UEFI grub environment, making it apparently impossible to select an installation that does not include the LXC and LXD suite by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1563026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829430] [NEW] Xorg freeze
Public bug reported: Every time i press the "windows" key which is by default mapped to "launch gnome search" the search launches but i cannot close it. The Escape key doesn't work at all and as far as i know the only solution to this problem is to log out and login again. This didnt occur when I was using 18.10 but after the upgrade to 19.04 this is indeed a problem. I'm aware that this issue might have something to so with the graphics drivers. root@aeshatter-XPS-15-9550:/home/aeshatter# lshw -c video *-display description: 3D controller product: GM107M [GeForce GTX 960M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:126 memory:dc00-dcff memory:b000-bfff memory:c000-c1ff ioport:e000(size=128) memory:dd00-dd07 *-display description: VGA compatible controller product: HD Graphics 530 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:127 memory:db00-dbff memory:7000-7fff ioport:f000(size=64) memory:c-d ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 16 22:00:45 2019 DistUpgraded: 2019-05-06 07:50:18,514 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell XPS 15 9550 [1028:06e4] Subsystem: Dell XPS 15 9550 [1028:06e4] InstallationDate: Installed on 2016-06-07 (1073 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=a31f340c-9c8b-441e-a80e-2684dd9d9ae9 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to disco on 2019-05-06 (10 days ago) dmi.bios.date: 10/11/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd10/11/2018:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 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 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue May 29 09:51:38 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829430 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Every time i press the "windows" key which is by default mapped to "launch gnome search" the search launches but i cannot close it. The Escape key doesn't work at all and as far as i know the only solution to this problem is to log out and login again. This didnt occur when I was using 18.10 but after the upgrade to 19.04 this is indeed a
[Touch-packages] [Bug 1828901] Re: add PTY support for runuser
** Tags added: rls-x-notfixing -- 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/1828901 Title: add PTY support for runuser Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: In Progress Status in util-linux package in Debian: Fix Released Bug description: [IMPACT] [TEST CASE] [REGRESSION POTENTIAL] [OTHER INFORMATION] Debbug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815922 This is fixing a CVE vulnerability: https://security-tracker.debian.org/tracker/CVE-2016-2779 Restricting ioctl on the kernel side seems the better approach, patches have been posted to kernel-hardening list http://www.openwall.com/lists/oss-security/2016/02/27/1 https://marc.info/?l=util-linux-ng=145694736107128=2 2.31 introduces a new --pty option to separate privileged and unprivileged shells (not enabled by default and the cli switch is necessary). [ORIGINAL DESCRIPTION] After a discussion with security team on what would be their recommended way to run command as 'juju-user' inside the sosreport juju plugin which is run as root, in order to avoid using 'sudo' or 'su' command. The recommendation was to use 'runuser -P' runuser PTY support is present in Bionic and late, but not in Xenial. I'm opening this bug in the effort to update util-linux/runuser code in Xenial to add the PTY support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1828901/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829450] [NEW] test_systemd_fsck_with_plymouth_failure passes but marked expected failure
Public bug reported: [impact] this test case was marked as expected failure in the past to try to ignore failures, but it now passes and so causes autopkgtest failures. [test case] run autopkgtest and check for the 'test_systemd_fsck_with_plymouth_failure' test, e.g.: test_systemd_fsck_with_plymouth_failure (__main__.FsckdTest) Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... bash: line 1: 786 Killed /tmp/autopkgtest.84SCbj/build.1op/src/debian/tests/systemd-fsckd 2> >(tee -a /tmp/autopkgtest.84SCbj/systemd-fsckd-stderr >&2) > >(tee -a /tmp/autopkgtest.84SCbj/systemd-fsckd-stdout) autopkgtest [16:47:57]: test process requested reboot with marker test_systemd_fsck_with_plymouth_failure:0 Connection to 10.44.40.6 closed by remote host. autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds... test_systemd_fsck_with_plymouth_failure (__main__.FsckdTest) Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... unexpected success -- Ran 1 test in 17.952s FAILED (unexpected successes=1) [regression potential] low; test case expectation fix only. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829450 Title: test_systemd_fsck_with_plymouth_failure passes but marked expected failure Status in systemd package in Ubuntu: New Bug description: [impact] this test case was marked as expected failure in the past to try to ignore failures, but it now passes and so causes autopkgtest failures. [test case] run autopkgtest and check for the 'test_systemd_fsck_with_plymouth_failure' test, e.g.: test_systemd_fsck_with_plymouth_failure (__main__.FsckdTest) Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... bash: line 1: 786 Killed /tmp/autopkgtest.84SCbj/build.1op/src/debian/tests/systemd-fsckd 2> >(tee -a /tmp/autopkgtest.84SCbj/systemd-fsckd-stderr >&2) > >(tee -a /tmp/autopkgtest.84SCbj/systemd-fsckd-stdout) autopkgtest [16:47:57]: test process requested reboot with marker test_systemd_fsck_with_plymouth_failure:0 Connection to 10.44.40.6 closed by remote host. autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds... test_systemd_fsck_with_plymouth_failure (__main__.FsckdTest) Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... unexpected success -- Ran 1 test in 17.952s FAILED (unexpected successes=1) [regression potential] low; test case expectation fix only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829450/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829458] [NEW] [ubuntu 19.04]All .desktop configuration files are opening in text editor
Public bug reported: All .desktop configuration files are opening in text editor. Because of that we can't creat custom shortcuts and having troubles while application making. Please fix this bug on next update. I have an Ubuntu 19.04. Tanks ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829458 Title: [ubuntu 19.04]All .desktop configuration files are opening in text editor Status in glib2.0 package in Ubuntu: New Bug description: All .desktop configuration files are opening in text editor. Because of that we can't creat custom shortcuts and having troubles while application making. Please fix this bug on next update. I have an Ubuntu 19.04. Tanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1829458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624071] Re: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624071 Title: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in the hosts line of /etc/nsswitch.conf. This makes DNSSEC validation impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf, because if libnss_resolve returns a validation failure, glibc will simply fall back to libnss_dns. It also makes NXDOMAIN lookups twice as slow. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624071/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693327] Re: Unable to open file: /etc/ima/ima-policy (-2)
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1693327 Title: Unable to open file: /etc/ima/ima-policy (-2) Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd package in Debian: Fix Released Bug description: dmesg: [4.496266] Unable to open file: /etc/ima/ima-policy (-2) [4.496274] IMA: policy update failed ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-6ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 14:30:01 2017 InstallationDate: Installed on 2015-07-26 (668 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-05-15 (8 days ago) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1693327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682154] Re: loginctl ignoring user given sessions IDs at command-line
** Changed in: systemd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1682154 Title: loginctl ignoring user given sessions IDs at command-line Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] loginctl command does not process session IDs given on the command-line, like the documentation suggests. This makes it impossible to use simple command-line calls to check properties of a given session. [Fix] Backport upstream patch to fix the issue [Testcase] Use loginctl command and specify multiple session IDs at the command-line and verify that details about these sessons are brought up in the output. [Regression Potential] Minimal, current behaviour is not sane at all, and it is a typpo fix from '1' to 'i' meaning that first argument was always used, instead of the current iterated one. Kubuntu zesty, 232-21ubuntu2 See upstream bug https://github.com/systemd/systemd/issues/5733 with patch attached. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1682154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682484] Re: systemd: Logging from gnome session is passed on to all syslog facilities
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1682484 Title: systemd: Logging from gnome session is passed on to all syslog facilities Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * untagged messages in journal do not have any syslog facility specified, this may result in spamming logs. * The solution is to cherrypick upstream fix which sanity checks and provides default syslog facility, e.g. it sets user facility on user/desktop session syslog/journal entries. [Test Case] * launch gnome terminal * check output of $ journalctl -o verbose -e * entries from gnome-terminal (e.g. "Allocating size to GtkBox without calling gtk_widget_get_preferred_width/height()") should have a syslog facility listed as one of the variables. [Regression Potential] * We are changing (fixing regression) in logging, thus release images have those messages untagged, and may require different filtering rules before this update is applied. [Other Info] * Original bug report from debian. Bug imported from Debian https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=837893 Package: systemd Version: 231-6 Severity: normal Since recently, log messages from programs running under the gnome session have started appearing in all logs in /var/logs, including /var/logs/kern.log, even though my rsyslog configuration has not changed, and correctly only routes kern.* there. This is very annoying since it fills the logs with messages that don't belong there, and makes running logcheck tedious. It seems this is a recent regression, since before I was able to route these messages to a low-priority log using the following rsyslog configuration: user.=info;user.=notice;\ user.=warn -/var/log/user-low.log If I look at the messages directly with journalctl -o verbose, it seems they do not set the syslog facility, which should make them end up with user facility, but doesn't. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1682484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673215] Re: Second unity8 user session hangs with a black screen
** Changed in: systemd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1673215 Title: Second unity8 user session hangs with a black screen Status in Canonical System Image: In Progress Status in systemd: Fix Released Status in systemd package in Ubuntu: Incomplete Bug description: Login to user1 using u8 as the session login to a second session and select u8 as the session The screen goes black and the fan comes on indicating something is in a tight loop Waited for several minutes and it stays in that state. A hard power cycle is needed. This is with the Zesty as of 3/15, no extra packages installed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668296] Re: not failing back to IPv4 when AAAA returns SERVFAIL
** Changed in: systemd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668296 Title: not failing back to IPv4 when returns SERVFAIL Status in systemd: Fix Released Status in systemd package in Ubuntu: New Bug description: A reocrd exists, returns SERVFAIL, in this case resolution fails instead of falling back to IPv4 A record $ host www.fidelityrewards.com www.fidelityrewards.com has address 170.135.184.45 Host www.fidelityrewards.com not found: 2(SERVFAIL) $ wget www.fidelityrewards.com --2017-02-27 07:41:57-- http://www.fidelityrewards.com/ Resolving www.fidelityrewards.com (www.fidelityrewards.com)... failed: Name or service not known. wget: unable to resolve host address ‘www.fidelityrewards.com /etc/nsswitch.conf hosts: files myhostname mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns wins libnss-resolve 231-9ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623003] Re: udev-generated /dev/disk/by-path names broken for virtio disks
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1623003 Title: udev-generated /dev/disk/by-path names broken for virtio disks Status in systemd: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: The udev-generated /dev/disk/by-path names for virtio disks are broken on z Systems as they have the format virtio-pci-h.h.[-partn], where h.h. is the CCW devno of the virtio device representing the whole disk. Historically, the standard CCW naming was applied, which was ccw-h.h.[-partn] ---uname output--- Linux ubuntu 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = 2964-703 running KVM for IBM z Systems ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install Ubuntu LTS 16.04.1 on KVM for IBM z Systems 1.1.1 2. Issue ls -l /dev/disk/by-path Userspace tool common name: udev The userspace tool has the following bit modes: 64-bit Userspace rpm: udev Userspace tool obtained from project website: na There are basically two problems with this: 1. The naming is technically incorrect, since the virtio devices on z are no PCI devices but CCW devices 2. Then naming based on virtio- is backwards incompatible. This may seem not to be an issue for Xenial but customers may be confused if they have been running Linux on KVM for IBM z before. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1623003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1591411 Title: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay Status in D-Bus: Fix Released Status in systemd: Fix Released Status in dbus package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Xenial: Fix Released Status in systemd source package in Xenial: Invalid Status in dbus source package in Yakkety: Won't Fix Status in systemd source package in Yakkety: Invalid Bug description: [Impact] The bug affects multiple users and introduces an user visible delay (~25 seconds) on SSH connections after a large number of sessions have been processed. This has a serious impact on big systems and servers running our software. The currently proposed fix is actually a safe workaround for the bug as proposed by the dbus upstream. The workaround makes uid 0 immune to the pending_fd_timeout limit that kicks in and causes the original issue. [Test Case] lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done Then checking the log file if there are any ssh sessions that are taking 25+ seconds to complete. Multiple instances of the same script can be used at the same time. [Regression Potential] The fix has a rather low regression potential as the workaround is a very small change only affecting one particular case - handling of uid 0. The fix has been tested by multiple users and has been around in zesty for a while, with multiple people involved in reviewing the change. It's also a change that has been proposed by upstream. [Original Description] I noticed on a system that accepts large numbers of SSH connections that after awhile, SSH sessions were taking ~25 seconds to complete. Looking in /var/log/auth.log, systemd-logind starts failing with the following: Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for user ubuntu by (uid=0) Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu. Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: Transport endpoint is not connected Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without replying I reproduced this in an LXD container by doing something like: lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done In my case, after 1052 logins, the 1053rd and thereafter were taking 25+ seconds to complete. Here are some snippets from the log file: $ cat log | grep 0m0 | wc -l 1052 $ cat log | grep 0m25 | wc -l 4 $ tail -5 log real 0m0.222s real 0m25.232s real 0m25.235s real 0m25.236s real 0m25.239s ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Jun 11 00:09:34 2016 MachineType: Notebook W230SS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1591411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1600000] Re: libnss-resolve treats two trailing dots on a domain name incorrectly
** Changed in: systemd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/160 Title: libnss-resolve treats two trailing dots on a domain name incorrectly Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Bug description: [Impact] libnss-resolve is an optional component not used by default in xenial. However it treats doubledot incorrectly, meaning it gets resolved when it shouldn't. [Fix] Cherrypick upstream patch to resolve this issue. [Testcase] * Enable resolve nss module * attempt resolving www.gnu.org.. * It should fail to resolve (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org.. 208.118.235.148 STREAM wildebeest.gnu.org 208.118.235.148 DGRAM 208.118.235.148 RAW (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ resolve dns/ dns/' /etc/nsswitch.conf (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org.. (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ dns/ resolve dns/' /etc/nsswitch.conf (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org.. 208.118.235.148 STREAM wildebeest.gnu.org 208.118.235.148 DGRAM 208.118.235.148 RAW (base)adconrad@nosferatu:~$ This is responsible for the new regression in glibc: -- FAIL: posix/tst-getaddrinfo5 original exit status 1 resolving "localhost." worked, proceeding to test resolving "localhost.." failed, test passed resolving "www.gnu.org." worked, proceeding to test resolving "www.gnu.org.." worked, test failed -- [Regression potential] Minimal, since this component is not used by default. However, systems that have this enabled exhibit standards non-compliant behavior. It is not expected for anybody to depend on this broken behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699850] Re: Reliable network connectivity for apt-daily
** Changed in: systemd Status: Unknown => 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/1699850 Title: Reliable network connectivity for apt-daily Status in systemd: New Status in apt package in Ubuntu: Fix Released Bug description: [Impact] apt-daily.service is launched by a timer that depends on network- online.target (after the fixes for bug 1686470 are in everywhere) At boot that is mostly sufficient for it to have network online, but it does not seem to work all the time, and we might be disagreeing with network-manager and friends what online state means. At resume time, network-online.target is still active, so the service is started as soon as possible when it tries to catch up. Depending on the timing, the network connectivity might not be there yet, and it will fail and only retry 12 hours later. [Proposed solution] Introduce a new apt-helper wait-online that waits for the machine being online, using both network-manager and systemd-networkd helpers. If the service is active, we use the respective online wait helper to wait for it to signal onlineness. Once all helpers have reported onlineness, we continue. [Original proposal, to be done later] original plan: It tries to connect() to remote hosts specified in sources.list until one connection works or a TIMEOUT is reached. The proposed algorithm looks something like this: while (time elapsed < TIMEOUT): for each entry: host = getaddrinfo() if host failed: continue fd = connect to it if fd is invalid: continue all fds += fd if poll(all fds, 100 ms timeout) finds a connected one: exit(0) exit(42) # timeout There are two things to consider: * getaddrinfo() and connect() may fail if network is not up yet, so we need to retry (we might need to sleep somewhere) * If poll() fails, we likely sleep enough, so no extra sleep needed. I believe the time out should be something like 30s. On the systemd service side, we add: ExecStartPre=/usr/lib/apt/apt-helper wait-online RestartForceExitStatus=42 RestartSec=15m To retry the service after 15 minutes. [Test case] * Start apt-daily.service after turning off network -> It should wait (in ExecStartPre) * Turn on network -> apt-daily.service should start [Regression potential] There might be increased I/O activity after resume, if that did not work before. The helper is launched in an ExecStartPre unit and failures are marked as ignored by "-". systemd automatically kills all ExecStartPre processes when the main ExecStartPre process exits, so there is no chance of ending with some child process still running. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1699850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644330] Re: resolved: correctly handle address families with /etc/hosts lookups
** Changed in: systemd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1644330 Title: resolved: correctly handle address families with /etc/hosts lookups Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: I have an ipv4 entry for a key host on my network listed in /etc/hosts, for network recovery purposes. This host also has ipv6 connectivity; the ipv6 address is resolvable via DNS, but I do not have it in /etc/hosts. Resolution of hostname should be independent for each address family. Two days ago (I don't know what changed to trigger this), I stopped being able to resolve the ipv6 address for this host. I traced this down to systemd-resolved, returning a lookup failure for the nss request, because the ipv6 address is not listed in /etc/hosts. Removing resolve from /etc/nsswitch.conf restores the correct behavior. Removing the ipv4 entry for the host restores the correct behavior. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 23 08:13:33 2016 InstallationDate: Installed on 2010-09-24 (2252 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-28 (25 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1644330/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1647485 Title: NVMe symlinks broken by devices with spaces in model or serial strings Status in maas-images: Fix Released Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Yakkety: Fix Released Status in systemd source package in Zesty: Fix Released Status in systemd package in Debian: Fix Released Bug description: [Impact] After including the patch from bug 1642903, NVMe devices that include spaces in their model or serial strings result in incorrect symlinks, e.g. if the model string is "XYZ Corp NVMe drive" then instead of creating: /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1 it creates: /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1 /dev/Corp -> nvme0n1 /dev/NVMe -> nvme0n1 /dev/drive_SERIAL -> nvme0n1 This is because of the way udev handles the SYMLINK value strings; by default, it does not do any whitespace replacement. To enable whitespace replacement of a symlink value, the rule must also include OPTIONS+="string_escape=replace". This is done for 'md' and 'dm' devices in their rules. However, there are no rules that actually want to specify multiple symlinks, and defaulting to not replacing whitespace makes no sense; instead, the default should be to replace all whitespace in each symlink value, unless the rule explicitly specifies OPTIONS+="string_escape=none". [Test Case] This assumes using udev with the patch from bug 1642903. Without this patch, when using a NVMe drive that contains spaces in its model and/or serial strings, check the /dev/disk/by-id/ directory. It should contain a partially-correct symlink to the NVMe drive, with the name up to the first space. All following space-separated parts of the mode/serial string should have symlinks in the /dev/ directory. This is the incorrect behavior. With this patch, check the /dev/disk/by-id/ directory. It should contain a fully-correct symlink to the NVMe drive, and no part of the drive's model/serial number string should be a link in the /dev directory. An example of the correct/incorrect naming is in the Impact section. There should be no other changes to any of the symlinks under /dev before and after this patch. Typical locations for symlinks are /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/, /dev/disk/by-label/ [Regression Potential] Errors in udev rules can lead to an unbootable or otherwise completely broken system if they unintentionally break or clobber existing /dev/disks/ symlinks. [Other Info] This is also tracked with upstream systemd (udev) bug 4833: https://github.com/systemd/systemd/issues/4833 Also note, this can be worked around in individual rules ONLY (i.e. not fixed for all rules) by appending OPTIONS+="string_escape=replace" to each of the NVMe rules with SYMLINK+="..." assignment, e.g.: KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*", ENV{ID_SERIAL_SHORT}=="?*", ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace" Related bugs: * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives * bug 1651602: NVMe driver regression for non-smp/1-cpu systems * bug 1649635: export nvme drive model/serial strings via sysfs (trusty) To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1647485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627950] Re: Stopped (with error) ... messages on encrypted LVM shutdown
** Changed in: systemd Status: Unknown => 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/1627950 Title: Stopped (with error) ... messages on encrypted LVM shutdown Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: Install (Default + crypted LVM) in Ubuntu Server s390x in Yakkety Daily Everything seems to work only on shutdown there is a bunch of "fail" messages related to the disks from systemd: [ OK ] Stopped Network Time Synchronization. [ 33.971312] systemd[1]: Stopped (with error) /dev/disk/by-id/dm-name-vda2_crypt. [FAILED] Stopped (with error) /dev/disk/by-id/dm-name-vda2_crypt. [ 33.971469] systemd[1]: Stopped (with error) /dev/disk/by-id/dm-uuid-CRYPT-LUKS1-ef8aced3ceb640fe80c2c700c4504ccb-vda2_crypt. [FAILED] Stopped (with error) /dev/disk/by-i...40fe80c2c700c4504ccb-vda2_crypt. [ 33.971595] systemd[1]: Stopped (with error) /dev/disk/by-id/lvm-pv-uuid-9hfIOG-dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq. [FAILED] Stopped (with error) /dev/disk/by-i...dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq. [FAILED] Stopped (with error) /dev/mapper/vda2_crypt. [FAILED] Stopped (with error) /dev/dm-0. [FAILED] Stopped (with error) /sys/devices/virtual/block/dm-0. [ OK ] Stopped Create Volatile Files and Directories. [ OK ] Stopped Raise network interfaces. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1627950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633274] Re: Systemd-networkd crashes with core dump
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1633274 Title: Systemd-networkd crashes with core dump Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Yakkety: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: Systemd-networkd crashes with core dump, this happends in Yakkety and Xenial. The latest patch that was commited to Xenial-updates and Yakkety is the one that broke this. Everything works just fine with Xenial without latest update or Yakkety Beta 2. The log entries i see is: Oct 14 02:37:42 Router01 systemd-networkd[3402]: Assertion 't' failed at ../src/network/networkd-netdev-tunnel.c:210, function netdev_vti_fill_message_key(). Aborting. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Main process exited, code=dumped, status=6/ABRT Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered failed state. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. Oct 14 02:37:42 Router01 systemd[1]: Stopped Network Service. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Start request repeated too quickly. Oct 14 02:37:42 Router01 systemd[1]: Failed to start Network Service. Oct 14 02:37:42 Router01 systemd[1]: Dependency failed for Wait for Network to be Configured. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd-wait-online.service: Job systemd-networkd-wait-online.service/start failed with result 'dependency'. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered failed state. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with result 'start-limit-hit'. SRU TEST CASE: See https://github.com/systemd/systemd/issues/4371#issuecomment-253697041 Regression potential: Very low, this just fixes an obvious type cast in networkd and touches no code that applies to other network interfaces. The service manager (pid 1) and other tools are entirely unaffected. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Oct 14 02:39:05 2016 InstallationDate: Installed on 2016-10-13 (0 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Dell Inc. OptiPlex 755 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd06/11/2012:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1633274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records
** Changed in: systemd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1647031 Title: systemd-resolved’s 127.0.0.53 server does not follow CNAME records Status in Nextcloud: Fix Released Status in systemd: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in network-manager source package in Yakkety: Invalid Status in systemd source package in Yakkety: Fix Released Bug description: [SRU Justification] Ubuntu 16.10 server uses systemd-resolved by default, configured both as a DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved talking to the dbus service. The DNS stub resolver has a bug that causes it to fail to resolve CNAME records. This went unnoticed before release because by default the NSS module is used. But a chroot or container on the system that does not include libnss-resolved and is configured to use the stub resolver will experience DNS failures. [Test case] 1. On a yakkety server system, create a xenial chroot with mk-sbuild (or equivalent). 2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53. 2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such. 3. Install the iputils-ping package. 4. ping www.freedesktop.org 5. Confirm that the hostname does not resolve. 6. Install the systemd package from yakkety-proposed onto the host system. 7. ping www.freedesktop.org 8. Confirm that the hostname does now resolve. [Regression potential] With a 247-line patch to a key service, there is some risk of regression. Regression risk is mitigated because this patch is already present in zesty and upstream, where no regressions have been reported, and because it only touches the DNS stub resolver which is not the code path used by default on host systems. $ systemd-resolve www.freedesktop.org www.freedesktop.org: 131.252.210.176 2610:10:20:722:a800:ff:feda:470f (annarchy.freedesktop.org) -- Information acquired via protocol DNS in 673.6ms. -- Data is authenticated: no $ ping www.freedesktop.org ping: www.freedesktop.org: Name or service not known $ 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 $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53 ;www.freedesktop.org. IN A www.freedesktop.org. 7146IN CNAME annarchy.freedesktop.org. $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8 ;www.freedesktop.org. IN A www.freedesktop.org. 14399 IN CNAME annarchy.freedesktop.org. annarchy.freedesktop.org. 14399 IN A 131.252.210.176 I trust it needn’t be explained why this makes the internet almost completely useless in zesty. To manage notifications about this bug go to: https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628778] Re: systemd-resolved: after network reconnection, DNSSEC unsigned zones treated as bogus, stop resolving
** Changed in: systemd Status: Unknown => 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/1628778 Title: systemd-resolved: after network reconnection, DNSSEC unsigned zones treated as bogus, stop resolving Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: On the MIT network (which runs some ancient version of BIND 9), systemd-resolved stops resolving anything that isn’t DNSSEC-signed after I disconnect and reconnect the network. Signed zones continue to resolve. This happens with either DNSSEC=yes or the default DNSSEC=allow- downgrade. $ systemd-resolve github.com github.com: 192.30.253.113 -- Information acquired via protocol DNS in 15.6ms. -- Data is authenticated: no $ # (disconnect and reconnect wifi) $ systemd-resolve github.com github.com: resolve call failed: DNSSEC validation failed: no-signature More debug information is available in my upstream report (https://github.com/systemd/systemd/issues/4175), which has gotten no response in the last week and a half. I’m refiling this here because I believe that this regression and others (bug 1588230, bug 1624071, bug 1624317, bug 1449001) indicate that systemd-resolved is not ready for production, and with final freeze just a week away, leaving systemd-resolved enabled for the yakkety release would be reckless. [Edit: Oh, I see that conclusion was already reached yesterday.] To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1628778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703393] Re: TCP offloads disabled by default
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1703393 Title: TCP offloads disabled by default Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Fix Released Status in systemd package in Debian: Fix Released Bug description: [Impact] Regression in systemd v232 resulted in IPv4 TCP segmentation offload ("tso" in ethtool) to be disabled by default, yet previously it was enabled. [Fix] Backport upstream patch to fix the regression [Testcase] Use ethtool to verify that tso is enabled on e.g. e1000e card with fixed package. [Regression Potential] Link features were incorrectly initialised, this fix changes the initialisation code back to the correct default values. This changes the defaults back to what they are in all other releases. Users on zesty release may have been accustomed to the wrong defaults and may need to adjust .link files to e.g. disable tso if that is the behavior they want. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1703393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703987] Re: New style permitnonkernelfacility imklog option inside module() doesn't work
** Changed in: rsyslog Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1703987 Title: New style permitnonkernelfacility imklog option inside module() doesn't work Status in Rsyslog: Fix Released Status in rsyslog package in Ubuntu: Fix Released Bug description: artful 8.16.0-1ubuntu5 (which is way behind upstream and debian, btw) There are two ways to load the imklog module and pass it an option (PermitNonKernelFacility in this case). a) legacy $ModLoad imklog $KLogPermitNonKernelFacility on b) "new style", also referred to as "v6+": module(load="imklog" permitnonkernelfacility="on") For a while the ubuntu package was using a mix: loading the module with the new style, but setting the option via the legacy method. In bug #1531622 this was fixed for yakkety+. Problem is, upstream isn't honouring the new style option setting due to a bug of its own: https://github.com/rsyslog/rsyslog/issues/477 With the legacy config: #module(load="imklog" permitnonkernelfacility="on") $ModLoad imklog $KLogPermitNonKernelFacility on I get kernel messages in /var/log/syslog: root@nsn7:~# grep andreas-was-here /var/log/syslog root@nsn7:~# echo andreas-was-here > /dev/kmsg root@nsn7:~# grep andreas-was-here /var/log/syslog Jul 12 16:46:33 nsn7 kernel: [27774.476193] andreas-was-here root@nsn7:~# But with this new v6 config style: module(load="imklog" permitnonkernelfacility="on") # provides kernel logging support #$ModLoad imklog #$KLogPermitNonKernelFacility on The text doesn't show up in /var/log/syslog. That's the upstream bug. To manage notifications about this bug go to: https://bugs.launchpad.net/rsyslog/+bug/1703987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668722] Re: 60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check
** Changed in: sddm Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1668722 Title: 60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check Status in SDDM: New Status in sddm package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Status in sddm source package in Bionic: Fix Released Status in xorg source package in Bionic: Invalid Bug description: This file: /etc/X11/Xsession.d/60x11-common_xdg_path contains references to $DESKTOP_SESSION variable. On one of my Ubuntu installs this variable contains: "plasma", on the other it contains: "/usr/share/xsessions/plasma". I don't know where either example comes from, but the upshot is that paths are added to XDG_DATA_DIRS and XDG_CONFIG_DIRS that don't exist. MANDATORY_PATH is also affected I believe, maybe others. Surely a sanity check of the generated paths is in order. Seems pointless to add non-existent ones. $XDG_SESSION_DESKTOP looks like a replacement for $DESKTOP_SESSION, but is that true? Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/sddm/+bug/1668722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688689] Re: Owner and group of few files and folders from Bind directory visible as nobody/nogroup within nspawn container
** Changed in: systemd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1688689 Title: Owner and group of few files and folders from Bind directory visible as nobody/nogroup within nspawn container Status in systemd: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: Owner and group of few files and folders from Bind directory visible as nobody/nogroup when I check permission from within nspawn container. Create testing.nspawn: [Files] Bind=/patch/to/folder Use some folder with many subfolders, to expand the test coverage. Check if owners of all subfolders and files in Bind directory inside container is the same as on host. Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu Server 17.10 (systemd 233). To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1688689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1826222] Re: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/eoan
** Changed in: python-apt (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1826222 Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/eoan Status in python-apt package in Ubuntu: Fix Released Bug description: [Impact] The 'Configuration' button of update-manager does not work. [Test Case] $ sudo update-manager Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 115, in __init__ SoftwareProperties.__init__(self, options=options, datadir=datadir) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 117, in __init__ self.reload_sourceslist() File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 612, in reload_sourceslist self.distro.get_sources(self.sourceslist) File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in get_sources (self.id, self.codename)) aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Ubuntu/eoan ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: software-properties-gtk 0.97.11 Uname: Linux 5.1.0-050100rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 10:21:47 2019 InstallationDate: Installed on 2018-12-02 (142 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828892] Re: systemctl - alias service reports inactive while aliased is active
** Tags added: ddstreet-next -- 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/1828892 Title: systemctl - alias service reports inactive while aliased is active Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Bug description: [Impact] 'systemctl is-active' command reports an alias service as inactive even though the aliased service is active. Currently the 'systemctl is-active' command does not load units to minimise its effect on the system (i.e. that a monitoring command does not itself alter the state of the system). However, this behaviour leads to inconsistencies when services are aliased. [Test case] - Test case 1 - libvirtd alias service : libvirtd aliased service : libvirt-bin /etc/systemd/system$ ls -la libvirtd.service lrwxrwxrwx 1 root root 39 May 13 20:49 libvirtd.service -> /lib/systemd/system/libvirt-bin.service $ systemctl is-active libvirtd inactive $ systemctl is-active libvirt-bin active - Test case 2 - sshd alias service : sshd aliased service : ssh /ect/systemd/system$ ls -la sshd.service lrwxrwxrwx 1 root root 31 Mar 19 19:44 sshd.service -> /lib/systemd/system/ssh.service $ systemctl is-active sshd inactive $ systemctl is-active ssh active [Regression Potential] This fix may result into systemctl reporting inconsistent information concerning the status of a service. [Other] Upstream issue : https://github.com/systemd/systemd/issues/7875 Upstream fix : https://github.com/systemd/systemd/pull/7997 Xenial is affected, fix exists on Bionic onward. $ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $ apt-cache policy systemd systemd: Installed: 229-4ubuntu21.21 Candidate: 229-4ubuntu21.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829401] Re: /usr/bin/software-properties-gtk:TypeError:on_pktask_finish:on_pktask_finish:new_init:__init__:new_init:__init__:new_init
I think this code originated from ximion, maybe he has an idea. ** Tags added: rls-ee-incoming ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.98.2, the problem page at https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d 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/. + + [Back trace] + Traceback (most recent call last): + File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", line 86, in on_pktask_finish + results = self._pktask.generic_finish(result) + gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support (8) + + During handling of the above exception, another exception occurred: + + Traceback (most recent call last): + File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", line 89, in on_pktask_finish + Gtk.ButtonsType.CANCEL, _("Error while refreshing cache")) + File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init + return super_init_func(self, **new_kwargs) + File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in __init__ + self._init(*args, **new_kwargs) + File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init + return super_init_func(self, **new_kwargs) + File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in __init__ + _window_init(self, *args, **kwargs) + File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init + return super_init_func(self, **new_kwargs) + TypeError: could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1829401 Title: /usr/bin/software-properties- gtk:TypeError:on_pktask_finish:on_pktask_finish:new_init:__init__:new_init:__init__:new_init Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.98.2, the problem page at https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d 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/. [Back trace] Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", line 86, in on_pktask_finish results = self._pktask.generic_finish(result) gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support (8) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", line 89, in on_pktask_finish Gtk.ButtonsType.CANCEL, _("Error while refreshing cache")) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in __init__ self._init(*args, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in __init__ _window_init(self, *args, **kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) TypeError: could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1537635] Re: Reduce zlib compression level for massive performance increase
** Changed in: apport Status: New => In Progress ** Changed in: apport Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1537635 Title: Reduce zlib compression level for massive performance increase Status in Apport: In Progress Status in apport package in Ubuntu: In Progress Status in apport source package in Eoan: In Progress Bug description: When apport takes a core dump of a large application, it uses 100% CPU for a _long_ time (often 30 seconds or more) to compress the core dump. The system is virtually unusable during this time, especially if the application was the window manager and won’t be restarted until the core dump is complete. This is a longstanding known problem; it motivated the switch from bzip2 to zlib level 9 back in apport 0.24. That made it much better, but it’s still quite bad. So why not switch from zlib level 9 to zlib level 1? I tested this on a core dump of gnome-shell, and while it increased the size of the .crash file by 24% (68.5 MB to 85.0 MB), it decreased the needed CPU time by a FACTOR OF EIGHT (58.6 seconds to 7.3 seconds). This tradeoff seems more than worthwhile for this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1537635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
There is a mailing list discussion on this topic currently active here: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2019-May/018345.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: Confirmed Bug description: I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. Note: for quick reference to anyone coming to this bug, this behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
** Description changed: - We should update bionic with the (now quite old!) point release + [ Description ] + + We should keep up with GStreamer's bugfix releases in the 1.14 series + that 18.04 shipped with. + + [ QA and testing ] + + Play a range of videos in Totem. Play a range of audio tracks in + Rhythmbox. Try to stream audio and/or video. Try to install a missing + codec. + + In all cases, make sure that everything which worked before still works. + + [ Regression potential ] + + If one of the fixes is bad then it might break video or audio playback, + or could crash any application that tries to use gstreamer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 source package in Bionic: New Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1826387] Re: systemd-networkd restart brings down bond slaves
** Bug watch added: github.com/systemd/systemd/issues #10118 https://github.com/systemd/systemd/issues/10118 ** Also affects: systemd via https://github.com/systemd/systemd/issues/10118 Importance: Unknown Status: Unknown -- 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/1826387 Title: systemd-networkd restart brings down bond slaves Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Bug description: Reported upstream as https://github.com/systemd/systemd/issues/10118 Ubuntu bionic, systemd version 237-3ubuntu10.19 When systemd-networkd is used to manage network bonds, upon systemd- networkd, bonds are brought down for ~10 seconds affecting connectivity to the server. From networkd logs (truncated to: ``` # journalctl -b -u systemd-networkd | grep enp3s0f Apr 25 12:45:33 compute01 systemd-networkd[30824]: Ignoring /etc/systemd/network/01-enp3s0f1.network, because it's not a regular file with suffix .netdev. Apr 25 12:45:33 compute01 systemd-networkd[30824]: Ignoring /etc/systemd/network/00-enp3s0f0.network, because it's not a regular file with suffix .netdev. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Flags change: +SLAVE +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link 6 added Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: udev initialized link Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Saved original MTU: 9000 Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Flags change: +SLAVE +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link 3 added Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: udev initialized link Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Saved original MTU: 9000 Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link state is up-to-date Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: found matching network '/etc/systemd/network/01-enp3s0f1.network' Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Started LLDP. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Enslaving by 'bond0' Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Link 'enp3s0f1' was up when attempting to enslave it. Bringing link down. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Bringing link down Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Enslaving link 'enp3s0f1' Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link state is up-to-date Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: found matching network '/etc/systemd/network/00-enp3s0f0.network' Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link does not request DHCPv6 prefix delegation Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Started LLDP. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Enslaving by 'bond0' Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Link 'enp3s0f0' was up when attempting to enslave it. Bringing link down. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Bringing link down Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Enslaving link 'enp3s0f0' Apr 25 12:45:33 compute01
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
** Changed in: gst-libav1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-bad1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-ugly1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-python1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-rtsp-server1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gstreamer-editing-services1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gstreamer-vaapi (Ubuntu) Status: New => Fix Released ** Changed in: gst-libav1.0 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gst-libav1.0 (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gst-plugins-bad1.0 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gst-plugins-bad1.0 (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gst-plugins-base1.0 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gst-plugins-base1.0 (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gst-plugins-good1.0 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gst-plugins-good1.0 (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gst-plugins-ugly1.0 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gst-plugins-ugly1.0 (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gst-python1.0 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gst-python1.0 (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gst-rtsp-server1.0 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gst-rtsp-server1.0 (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gstreamer-editing-services1.0 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gstreamer-editing-services1.0 (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gstreamer-vaapi (Ubuntu Bionic) Status: New => In Progress ** Changed in: gstreamer-vaapi (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gstreamer1.0 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gstreamer1.0 (Ubuntu Bionic) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: In Progress Status in gst-plugins-bad1.0 source package in Bionic: In Progress Status in gst-plugins-base1.0 source package in Bionic: In Progress Status in gst-plugins-good1.0 source package in Bionic: In Progress Status in gst-plugins-ugly1.0 source package in Bionic: In Progress Status in gst-python1.0 source package in Bionic: In Progress Status in gst-rtsp-server1.0 source package in Bionic: In Progress Status in gstreamer-editing-services1.0 source package in Bionic: In Progress Status in gstreamer-vaapi source package in Bionic: In Progress Status in gstreamer1.0 source package in Bionic: In Progress Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts
I don't think it's *-control-center. At the time, that was filed there by pitti, who correctly pointed out that something might need to depend on libnss-myhostname (from systemd) for a fallback to resolving hostname via just /etc/hostname (since /etc/hosts isn't changed). At this point though, it looks like this is no longer required. Now, AFAICT the desktop correctly calls to systemd via dbus to ask for the change. I'll leave to you to make sure this is indeed the case (since you had commented on the bug previously, and I can't see any issues changing hostname as it is now, but maybe I'm not quite doing the same tests you were). unity-control-center is an obvious Won't Fix for Eoan or Disco, but I'll let the Desktop Team decide whether this needs to be fixed in other releases. Finally, this is still assigned to systemd, low priority, because hostnamed *doesn't* change /etc/hosts, and probably should (at the very least for consistency, to avoid keeping a reference to an old name for the system); but I didn't notice ill effects from not changing that file. sudo certainly doesn't hang here trying to resolve the new or old hostname. -- 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/1162475 Title: [hostnamed] Changing hostname doesn't update /etc/hosts Status in gnome-control-center package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in unity-control-center package in Ubuntu: Won't Fix Status in gnome-control-center source package in Xenial: New Status in systemd source package in Xenial: Triaged Status in unity-control-center source package in Xenial: New Status in gnome-control-center package in Debian: Fix Released Bug description: GUI --- 1a. Run sudo gnome-control-center, or... 1b. Save the gnome-control-center.pkla from https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run gnome-control-center as an admin user 2. Enter the Details panel 3. The "Device name" (hostname) text field should be editable; change the text to something else. 4. The hostname is updated instantly which can be verified by looking in /etc/hostname. However /etc/hosts/ is not updated. Command line hostnamectl set-hostname The hostnamed documentation at http://www.freedesktop.org/wiki/Software/systemd/hostnamed says "To properly handle name lookups with changing local hostnames without having to edit /etc/hosts for them we recommend using hostnamed in combination with nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ " Without /etc/hosts being handled correctly, the hostnamed integration is only half-working. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu18 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sun Mar 31 08:52:57 2013 MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.5-0ubuntu1 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1 indicator-datetime 12.10.3daily13.03.26-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1162475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823422] Re: heimdal ftbfs in disco
hi there, I was attempting to update a security issue on heimdal and had these issues with tests (maybe also related) FAIL test_ca (exit status: 1) FAIL: test_chain cert -> root FAIL test_chain (exit status: 1) FAIL: test_cms == not testing ECDSA since hcrypto doesnt support ECDSA create signed data verify signed data hxtool: hx509_cms_verify_signed: Failed to find certificate with id CE776EDE0BF421F878C01A7CC3B966EC4C3D4A23 FAIL test_cms (exit status: 1) Testsuite summary for Heimdal 7.5.0 # TOTAL: 16 # PASS: 13 # SKIP: 0 # XFAIL: 0 # FAIL: 3 # XPASS: 0 # ERROR: 0 See lib/hx509/test-suite.log Please report to https://github.com/heimdal/heimdal/issues >From upstream, it seems there is a probably fix, but the issue is still open and it seems not to work for 32 Oses - see here: https://github.com/heimdal/heimdal/issues/533 If anyone has any clue how to fix this FTBFS it would be appreciate :) - tks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1823422 Title: heimdal ftbfs in disco Status in Heimdal: New Status in heimdal package in Ubuntu: Triaged Bug description: https://launchpadlibrarian.net/417925401/buildlog_ubuntu-disco- amd64.heimdal_7.5.0+dfsg-2.1_BUILDING.txt.gz = Heimdal 7.5.0: lib/hx509/test-suite.log = # TOTAL: 16 # PASS: 15 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test_chain cert -> root cert -> root cert -> root sub-cert -> root sub-cert -> sub-ca -> root sub-cert -> sub-ca sub-cert -> sub-ca -> root sub-cert -> sub-ca -> root sub-cert -> sub-ca -> root max depth 2 (ok) max depth 1 (fail) ocsp non-ca responder ocsp ca responder ocsp no-ca responder, missing cert ocsp no-ca responder, missing cert, in pool ocsp no-ca responder, keyHash ocsp revoked cert ocsp print reply resp1-ocsp-no-cert ocsp print reply resp1-ca ocsp print reply resp1-keyhash ocsp print reply resp2 ocsp verify exists ocsp verify not exists ocsp verify revoked crl non-revoked cert FAIL test_chain (exit status: 1) Testsuite summary for Heimdal 7.5.0 # TOTAL: 16 # PASS: 15 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See lib/hx509/test-suite.log Please report to https://github.com/heimdal/heimdal/issues To manage notifications about this bug go to: https://bugs.launchpad.net/heimdal/+bug/1823422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1010349] Re: Evolution address book inaccessible without killing one time "e-addressbook-factory"
I am experiencing this on Evolution 3.30.1-1build1 and Ubuntu 18.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1010349 Title: Evolution address book inaccessible without killing one time "e -addressbook-factory" Status in evolution-data-server package in Ubuntu: Confirmed Bug description: After a fresh boot of my system, Evolution is not able to access my work address book on LDAP and my personnal address book on Google. With Google address book I get the error "Cannot open book: Source already loaded!" After shutting down Evolution and killing by hand : /usr/lib/evolution/e-addressbook-factory. I relaunch Evolution and everything go right. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution-data-server 3.2.3-0ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Fri Jun 8 09:07:18 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1010349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822270] Re: Debconf readline frontend does not show options
This bug was fixed in the package debconf - 1.5.66ubuntu1 --- debconf (1.5.66ubuntu1) bionic; urgency=medium * Fix readline prompts when run via run-parts (LP: #1822270) - Debconf/FrontEnd/Readline.pm: force output to stdout if both stdout and stderr are pipes -- Heitor Alves de Siqueira Mon, 06 May 2019 13:30:30 -0300 ** Changed in: debconf (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: Fix Released Status in debconf source package in Xenial: Fix Committed Status in debconf source package in Bionic: Fix Released Status in debconf source package in Cosmic: Fix Released Status in debconf source package in Disco: Fix Released Status in debconf source package in Eoan: Fix Released Status in debconf package in Debian: Fix Released Bug description: [Impact] debconf prompts the user for input before displaying options [Description] When upgrading packages with apt or dpkg, debconf scripts are ran through 'run-parts' with the '--report' flag. This causes script output to be handled through pipes set up by run-parts, and buffers output from maintainer scripts nicely for formatting. If debconf makes use of the readline frontend, any prompts will bypass the run-parts buffers and be displayed directly to /dev/tty. This generally causes the prompt to be displayed before the user gets any of the available options for it, and printing will block until the user inputs a valid option. Upstream commit: https://salsa.debian.org/pkg- debconf/debconf/commit/48c5ce38cfd5 [Test Case] 1) Deploy a VM through e.g. uvt-kvm $ uvt-kvm create disco release=disco 2) Remove the whiptail package to force the readline frontend in debconf root@disco:~# apt remove --purge whiptail -y 3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade through run-parts root@disco:~# apt update && apt install -y grub-legacy-ec2 root@disco:~# rm -f /boot/grub/menu.lst* root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst 4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we just need it to think menu.lst needs an upgrade) root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report ... /etc/kernel/postinst.d/x-grub-legacy-ec2: debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... What would you like to do about menu.lst? The "What would you like to do about menu.lst?" prompt will block until the user enter a valid option, even though it's being displayed before the available options. [Regression Potential] We could hit regressions if changing debconf's printing to /dev/tty is expected by other programs. The changes are needed only in the readline frontend, so that would minimize impact of any possible regressions. The fixes will be thoroughly tested with autopkgtest and use-case scenarios. # # # # [Original Description] When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829364] [NEW] Will not play sound via HDMI unless you run pavucontrol first
Public bug reported: Does not play sound via sink output:iec958-stereo unless I start pavucontrol before running the player such as paplay. Player does not show any error and takes its time to play, but there is no sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1829364 Title: Will not play sound via HDMI unless you run pavucontrol first Status in pulseaudio package in Ubuntu: New Bug description: Does not play sound via sink output:iec958-stereo unless I start pavucontrol before running the player such as paplay. Player does not show any error and takes its time to play, but there is no sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779289] Update Released
The verification of the Stable Release Update for gnome-bluetooth 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Fix Released Status in gnome-bluetooth source package in Bionic: Fix Released Bug description: * Impact Bluetooth pointer devices are not always correctly paired, which leads to have them failing to connect or not auto-reconnecting * Test case Pair a bluetooth mouse, it should re-connect automatically after suspend/resume or reboot cycles * Regression potential The change makes all devices go through pairing with the standard code that should work fine but we should keep an eye if it confuses some devices and lead to prompt for a PIN when that shouldn't be needd -- This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829347] Re: systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug
** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829347 Title: systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Status in systemd source package in Disco: New Status in systemd source package in Eoan: New Bug description: [impact] systemd autopkgtest fails [test case] run systemd autopkgtest, check for output like: LUKS device with "tmp" option ... rmmod: ERROR: Module scsi_debug is in use FAIL == FAIL: test_luks_tmp (__main__.CryptsetupTest) LUKS device with "tmp" option -- Traceback (most recent call last): File "/tmp/autopkgtest.It858Q/build.e7O/src/debian/tests/storage", line 59, in setUp self.fail('%s exists already' % self.plaintext_dev) AssertionError: /dev/mapper/testcrypt1 exists already this has attempted to be fixed in various ways so the output is a bit different across different releases, but all of them have the common point of failing to modprobe or rmmod the scsi_debug module, which by itself doesn't indicate a failure. [regression potential] low; this is fixing a testcase only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1826870] Re: cache.commit() doesn't release the archives lock
This bug was fixed in the package python-apt - 1.1.0~beta1ubuntu0.16.04.4 --- python-apt (1.1.0~beta1ubuntu0.16.04.4) xenial; urgency=medium * apt.Cache: Fix (un)locking of archives (Closes: #922416) (LP: #1826870) * apt.Cache: Use explicit, more safe locking in update() * Update mirror lists python-apt (1.1.0~beta1ubuntu0.16.04.3) xenial; urgency=medium * Frontend locking and related locking improvements (LP: #1795407) - apt.Cache: Keep / Re-establish the system lock in commit() - apt.Cache: Keep archive locked during commit()/ in fetch_archives() - apt.Cache: Reinstate locks in a finally / run dpkg inside try - Introduce frontend locking - Convert apt.Cache.commit and apt_pkg.DepCache.commit to FE lock * Other changes to make that work: - travis CI: enable PPA for new apt versions * As always, updated mirror lists -- Julian Andres Klode Mon, 29 Apr 2019 14:11:32 +0200 ** Changed in: python-apt (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 python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1826870 Title: cache.commit() doesn't release the archives lock Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Released Status in python-apt source package in Bionic: Fix Released Status in python-apt source package in Cosmic: Fix Released Status in python-apt package in Debian: Fix Released Bug description: [Impact] cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
This bug was fixed in the package gnome-bluetooth - 3.28.0-2ubuntu0.2 --- gnome-bluetooth (3.28.0-2ubuntu0.2) bionic; urgency=medium * debian/patches/git_set_trusted.patch, debian/patches/git_pair_pointer.patch: - backport upstream commits to fix marking of device trusted on pairing not always working (leading to auto-reconnect not working). Always try to pair pointer devices also, that's expected by most recent devices, removing the specific list of devices which should use the default PIN and do that for all devices (lp: #1779289) -- Sebastien Bacher Fri, 12 Apr 2019 15:06:49 +0200 ** Changed in: gnome-bluetooth (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Fix Released Status in gnome-bluetooth source package in Bionic: Fix Released Bug description: * Impact Bluetooth pointer devices are not always correctly paired, which leads to have them failing to connect or not auto-reconnecting * Test case Pair a bluetooth mouse, it should re-connect automatically after suspend/resume or reboot cycles * Regression potential The change makes all devices go through pairing with the standard code that should work fine but we should keep an eye if it confuses some devices and lead to prompt for a PIN when that shouldn't be needd -- This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent
This bug was fixed in the package bash - 4.3-14ubuntu1.3 --- bash (4.3-14ubuntu1.3) xenial; urgency=medium * Resurrect "Set the default path to comply with Debian policy" in deb-bash-config.diff which went missing since 4.2+dfsg-1 or so. LP: #1792004 LP: #1614080 Closes: #781367 * Add autopkgtest for the built-in path. -- Dimitri John Ledkov Fri, 03 May 2019 14:57:15 +0100 ** Changed in: bash (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1792004 Title: built-in PATH seems to have sbin and bin out of order; and inconsistent Status in apt package in Ubuntu: Fix Released Status in bash package in Ubuntu: Fix Released Status in busybox package in Ubuntu: New Status in dash package in Ubuntu: New Status in dpkg package in Ubuntu: Won't Fix Status in pam package in Ubuntu: New Status in systemd package in Ubuntu: New Status in bash source package in Xenial: Fix Released Status in bash source package in Bionic: Fix Released Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: Fix Released Bug description: [Impact] * For consistency reasons sbin should be ordered before bin in PATH. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' And check that matching pairs in PATH, have /sbin variant leading /bin variant. [Regression Potential] * Ubuntu does not ship duplicate binries, with different behaviour between /sbin and /bin, thus all binaries will continue to be found in all locations. Also PATH is normally already set in the environment, and this change only affects the fallback path when bash is executed without any environment, i.e. booting with 'init=/bin/bash' [Other Info] * Original bug report detailing inconsistent paths between various shells. --- $ env -u PATH /bin/sh -c 'echo $PATH' /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ env -u PATH /bin/dash -c 'echo $PATH' /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ systemd-run --unit test-env env # ... and check journal for PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ env -u PATH /bin/bash -c 'echo $PATH' /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. $ env -u PATH /bin/busybox sh -c 'echo $PATH' /sbin:/usr/sbin:/bin:/usr/bin $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/ initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin' initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} exported as PATH dracut-047+31/modules.d/99shutdown/shutdown.sh:export PATH=/usr/sbin:/usr/bin:/sbin:/bin $ cat /etc/environment PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" apt & dpkg => should probably initiate /usr/local-less PATH Imho the rest should probably be harmonised to: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin === From a duplicate https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 : $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; done 12.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 12.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 14.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 14.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 16.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. I believe later releases of bash, do too include CWD in the built-in PATH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1792004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1826870] Re: cache.commit() doesn't release the archives lock
This bug was fixed in the package python-apt - 1.6.4 --- python-apt (1.6.4) bionic; urgency=medium * apt.Cache: Fix (un)locking of archives (Closes: #922416) (LP: #1826870) * apt.Cache: Use explicit, more safe locking in update() * Update mirror lists -- Julian Andres Klode Mon, 29 Apr 2019 13:49:15 +0200 ** Changed in: python-apt (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1826870 Title: cache.commit() doesn't release the archives lock Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Released Status in python-apt source package in Bionic: Fix Released Status in python-apt source package in Cosmic: Fix Released Status in python-apt package in Debian: Fix Released Bug description: [Impact] cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829366] [NEW] [SRU] Bugfix release 1.14.4
Public bug reported: We should update bionic with the (now quite old!) point release ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: gstreamer1.0 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gstreamer1.0 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 source package in Bionic: New Bug description: We should update bionic with the (now quite old!) point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system
vorlon: Even if it's not technically needed on the apt side, because there is no meta package, it does help to have the list consistent. For eoan, we'll even move to just ^linux-.*$ (to avoid having to add new kernels when they appear), so it will be covered anyway. On the other hand, it does have the advantage that if you do install unsigned kernels for some reason, they'll get automatically removed by unattended-upgrades with the pattern being present if they are outdated as part of the normal versioned kernel removal. ** Changed in: apt (Ubuntu Cosmic) Status: Incomplete => In Progress -- 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/1821640 Title: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: In Progress Status in apt source package in Cosmic: In Progress Status in apt source package in Disco: Fix Committed Status in apt source package in Eoan: Fix Released Bug description: [Impact] Unattended-upgrades keeps versioned kernel packages because they don't match known kernel package patterns: ... Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it would also remove the following packages which should be kept in this step: linux-image-unsigned-4.18.0-14-generic ... For reproduction see LP: #1795696, but running u-u with --verbose. And APT does not apply proper kernel-version based protection to it. [Test case] linux-image-unsigned should popup in the same list in 01autoremove-kernels as linux-signed-image, and should be autoremovable iff it's signed counterpart is autoremovable. [Regression potential] Not really any, it's just an additional string in the entry. The only difference really possible therefore is that the set of autoremovable packages changes and unattended-upgrades and friends might autoremove different sets of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795407] Re: python-apt frontend locking
This bug was fixed in the package python-apt - 1.1.0~beta1ubuntu0.16.04.4 --- python-apt (1.1.0~beta1ubuntu0.16.04.4) xenial; urgency=medium * apt.Cache: Fix (un)locking of archives (Closes: #922416) (LP: #1826870) * apt.Cache: Use explicit, more safe locking in update() * Update mirror lists python-apt (1.1.0~beta1ubuntu0.16.04.3) xenial; urgency=medium * Frontend locking and related locking improvements (LP: #1795407) - apt.Cache: Keep / Re-establish the system lock in commit() - apt.Cache: Keep archive locked during commit()/ in fetch_archives() - apt.Cache: Reinstate locks in a finally / run dpkg inside try - Introduce frontend locking - Convert apt.Cache.commit and apt_pkg.DepCache.commit to FE lock * Other changes to make that work: - travis CI: enable PPA for new apt versions * As always, updated mirror lists -- Julian Andres Klode Mon, 29 Apr 2019 14:11:32 +0200 ** Changed in: python-apt (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 python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Released Status in python-apt source package in Bionic: Fix Released Bug description: [Impact] Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: (1) The archives lock was only taken for a short time, when it should have been kept for the duration of an installation, as otherwise debs could disappear from archives/ while the install is running. (2) There was no lock handling at all. Tools essentially acquire the lock, and then release it before commit(). The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage both the frontend and the normal lock, and allows code to call apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() around dpkg invocations to release the inner lock. Cache.commit() takes care of locking itself now. It releases the inner lock as needed for dpkg invocations. It also now requires apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released 3. Observe that the archive lock is not released until the last dpkg run The locking behavior can be observed via strace. [Regression potential] The dpkg lock changed the most: Some lock counting might go wrong and programs might fail as a result. Any problems will be isolated, though - dpkg still acquires its locks, and if a lock miscount happens, apt would not tell dpkg to skip acquiring the frontend lock, so even if we were losing the lock anywhere, dpkg would still try to acquire it and not run unlocked. The archive lock done by commit()/fetch_archives() in apt.Cache() is now hold as long as the fetcher object exists though (as it uses the fetcher's get_lock method), which might cause unexpected behavior in apps not expecting that. The lists/ lock is unaffected by the changes, so there should not be any regressions when it comes to updating index files. [Other info (1)] CI changes: There were some improvements to type hints for mypy needed to make type checks pass, and changes to the CI's Dockerfile to pull a new apt from the apt stable PPA (as a new enough apt is only in unapproved atm). Neither of those files are used anywhere outside of the package, so they should not cause any problems. [Other info (2)] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html - This SRU depends on the apt SRU above, and breaks unattended- upgrades in bionic without its SRU due to a bug in the u-u code in handling the new API. - xenial depends on unattended-upgrades SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822270] Re: Debconf readline frontend does not show options
This bug was fixed in the package debconf - 1.5.58ubuntu2 --- debconf (1.5.58ubuntu2) xenial; urgency=medium * Fix readline prompts when run via run-parts (LP: #1822270) - Debconf/FrontEnd/Readline.pm: force output to stdout if both stdout and stderr are pipes -- Heitor Alves de Siqueira Mon, 06 May 2019 13:31:57 -0300 ** Changed in: debconf (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 debconf in Ubuntu. https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: Fix Released Status in debconf source package in Xenial: Fix Released Status in debconf source package in Bionic: Fix Released Status in debconf source package in Cosmic: Fix Released Status in debconf source package in Disco: Fix Released Status in debconf source package in Eoan: Fix Released Status in debconf package in Debian: Fix Released Bug description: [Impact] debconf prompts the user for input before displaying options [Description] When upgrading packages with apt or dpkg, debconf scripts are ran through 'run-parts' with the '--report' flag. This causes script output to be handled through pipes set up by run-parts, and buffers output from maintainer scripts nicely for formatting. If debconf makes use of the readline frontend, any prompts will bypass the run-parts buffers and be displayed directly to /dev/tty. This generally causes the prompt to be displayed before the user gets any of the available options for it, and printing will block until the user inputs a valid option. Upstream commit: https://salsa.debian.org/pkg- debconf/debconf/commit/48c5ce38cfd5 [Test Case] 1) Deploy a VM through e.g. uvt-kvm $ uvt-kvm create disco release=disco 2) Remove the whiptail package to force the readline frontend in debconf root@disco:~# apt remove --purge whiptail -y 3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade through run-parts root@disco:~# apt update && apt install -y grub-legacy-ec2 root@disco:~# rm -f /boot/grub/menu.lst* root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst 4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we just need it to think menu.lst needs an upgrade) root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report ... /etc/kernel/postinst.d/x-grub-legacy-ec2: debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... What would you like to do about menu.lst? The "What would you like to do about menu.lst?" prompt will block until the user enter a valid option, even though it's being displayed before the available options. [Regression Potential] We could hit regressions if changing debconf's printing to /dev/tty is expected by other programs. The changes are needed only in the readline frontend, so that would minimize impact of any possible regressions. The fixes will be thoroughly tested with autopkgtest and use-case scenarios. # # # # [Original Description] When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
We should think about cosmic indeed, but it's not really blocking the release for bionic. Currently upgrades from bionic to cosmic will very very very rare. With disco released, there's no 'official' upgrade path - not to mention bionic users by default should be only informed of new LTS versions. So I'll proceed with getting this out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Released Status in libqmi source package in Bionic: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in libmbim source package in Disco: Fix Released Status in libqmi source package in Disco: Fix Released Status in modemmanager source package in Disco: Fix Released Status in libmbim source package in Eoan: Fix Released Status in libqmi source package in Eoan: Fix Released Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819615] Update Released
The verification of the Stable Release Update for modemmanager 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 modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Released Status in libqmi source package in Bionic: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in libmbim source package in Disco: Fix Released Status in libqmi source package in Disco: Fix Released Status in modemmanager source package in Disco: Fix Released Status in libmbim source package in Eoan: Fix Released Status in libqmi source package in Eoan: Fix Released Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
This bug was fixed in the package libqmi - 1.22.0-1.2~ubuntu18.04.1 --- libqmi (1.22.0-1.2~ubuntu18.04.1) bionic; urgency=medium * Build for Bionic (LP: #1819615). * debian/libqmi-glib5.symbols: update symbols for new release. libqmi (1.22.0-1.2) unstable; urgency=medium * Non-maintainer upload. * Add debian/patches/git_reset-offset-before-2nd-call.patch from upstream. - equivalent to 1.22.2 release except the broken manpages in that release. libqmi (1.22.0-1.1) unstable; urgency=medium * Non-maintainer upload * Bump Build-Depends on libmbim-glib-dev to 1.18.0 to fix build (Closes: #921321) libqmi (1.22.0-1) unstable; urgency=medium * New upstream release - Needed by ModemManager 1.10. * debian/patches/0001-qmicli-remove-implicity-casts-to-GDestroyNotify-in-g.patch: Dropped, included upstream. * debian/libqmi-glib5.symbols: update symbols for new release. libqmi (1.20.0-1.1) unstable; urgency=medium * Non-maintainer upload. * Add upstream fix for FTBFS with glib 2.58, thanks to Juhani Numminen. (Closes: #908016) libqmi (1.20.0-1) unstable; urgency=medium * New upstream version 1.20.0. (Closes: #887975) * debian/patches/0001-utils-drop-useless-g_file_test-call.patch: dropped, included upstream. * debian/libqmi-glib5.symbols: update symbols for new release. * debian/control: changing Maintainer field to claim the package. Marius is no longer interested in maintaining it. * debian/control: bump Standards-Version to 4.1.3. -- Till Kamppeter Wed, 20 Mar 2019 14:28:39 +0100 ** Changed in: libqmi (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: libmbim (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Released Status in libqmi source package in Bionic: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in libmbim source package in Disco: Fix Released Status in libqmi source package in Disco: Fix Released Status in modemmanager source package in Disco: Fix Released Status in libmbim source package in Eoan: Fix Released Status in libqmi source package in Eoan: Fix Released Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
This bug was fixed in the package modemmanager - 1.10.0-1~ubuntu18.04.2 --- modemmanager (1.10.0-1~ubuntu18.04.2) bionic; urgency=medium * debian/patches/error-propagation-fix.patch: mm-broadband-modem: Fix error propagation in CDMA service status (LP: #1819615, Upstream Issue #119). modemmanager (1.10.0-1~ubuntu18.04.1) bionic; urgency=medium * New upstream release (LP: #1819615) * debian/control: Update build dependencies as now libmbim >= 1.18.0 and libqmi >= 1.22.0 are required. * debian/libmm-glib0.symbols: update symbols for new release. * debian/patches/0001-m4-compiler_warnings.m4-Let-Werror-be-disabled.patch: Removed, included upstream. -- Till Kamppeter Mon, 06 May 2019 16:09:29 +0200 ** Changed in: modemmanager (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Released Status in libqmi source package in Bionic: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in libmbim source package in Disco: Fix Released Status in libqmi source package in Disco: Fix Released Status in modemmanager source package in Disco: Fix Released Status in libmbim source package in Eoan: Fix Released Status in libqmi source package in Eoan: Fix Released Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
This bug was fixed in the package libmbim - 1.18.0-1~ubuntu18.04.1 --- libmbim (1.18.0-1~ubuntu18.04.1) bionic; urgency=medium * New upstream release - Needed by ModemManager 1.10 (LP: #1819615). * debian/libmbim-glib4.symbols: Updated symbols for new release. * debian/patches/ref_cast.patch: Removed, not applicable any more on 1.18.0. libmbim (1.16.0-1) unstable; urgency=medium * New upstream release 1.16.0 (Closes: #887974) * Adopting the package. (Closes: #888680) * debian/control: bump libglib-dev Depends to (>= 2.36) as required by the new release. * debian/libmbim-glib4.symbols: update symbols for new release. * debian/rules: add DPKG_GENSYMBOLS_CHECK_LEVEL=4; it's more verbose with added or changed symbols then. -- Till Kamppeter Thu, 20 Mar 2019 20:37:29 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Released Status in libqmi source package in Bionic: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in libmbim source package in Disco: Fix Released Status in libqmi source package in Disco: Fix Released Status in modemmanager source package in Disco: Fix Released Status in libmbim source package in Eoan: Fix Released Status in libqmi source package in Eoan: Fix Released Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash
This bug was fixed in the package bash - 4.3-14ubuntu1.3 --- bash (4.3-14ubuntu1.3) xenial; urgency=medium * Resurrect "Set the default path to comply with Debian policy" in deb-bash-config.diff which went missing since 4.2+dfsg-1 or so. LP: #1792004 LP: #1614080 Closes: #781367 * Add autopkgtest for the built-in path. -- Dimitri John Ledkov Fri, 03 May 2019 14:57:15 +0100 ** Changed in: bash (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 bash in Ubuntu. https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash Status in bash package in Ubuntu: Fix Released Status in bash source package in Precise: Fix Released Status in bash source package in Trusty: Won't Fix Status in bash source package in Xenial: Fix Released Status in bash source package in Bionic: Fix Released Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: Fix Released Status in bash source package in Eoan: Fix Released Status in bash package in Debian: New Bug description: [Impact] * The fallback path built into bash contains '.' which leads to unexpected addition of the current working directory. It should not be there, just like it isnt' in pre-precise and cosmic+. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' Should not have '.' as any component. Nor should there be any empty components, i.e. '::'. [Regression Potential] * Normally PATH is always set by either init, systemd, or any other hypervisor. Thus this only affects executions under bash, when it was started without any environment - e.g. booting with 'init=/bin/bash'. [Other Info] * Original bug report. On ubuntu 16.04 (but also 14.04), running bash with PATH unset always adds '.' to PATH: philippe@pv-desktop:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games philippe@pv-desktop:~$ unset PATH philippe@pv-desktop:~$ /bin/bash philippe@pv-desktop:~$ echo $PATH /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. Even when testing in a virtual machine / docker, and erasing /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem still happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829347] Re: systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug
** Changed in: systemd (Ubuntu Eoan) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Disco) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Cosmic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Eoan) Status: New => In Progress ** Changed in: systemd (Ubuntu Disco) Status: New => In Progress ** Changed in: systemd (Ubuntu Cosmic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Description changed: [impact] systemd autopkgtest fails [test case] run systemd autopkgtest, check for output like: LUKS device with "tmp" option ... rmmod: ERROR: Module scsi_debug is in use FAIL == FAIL: test_luks_tmp (__main__.CryptsetupTest) LUKS device with "tmp" option -- Traceback (most recent call last): - File "/tmp/autopkgtest.It858Q/build.e7O/src/debian/tests/storage", line 59, in setUp - self.fail('%s exists already' % self.plaintext_dev) + File "/tmp/autopkgtest.It858Q/build.e7O/src/debian/tests/storage", line 59, in setUp + self.fail('%s exists already' % self.plaintext_dev) AssertionError: /dev/mapper/testcrypt1 exists already - this has attempted to be fixed in various ways so the output is a bit - different across different releases, but all of them have the common - point of failing to modprobe or rmmod the scsi_debug module, which by - itself doesn't indicate a failure. + or for older releases something like: + + autopkgtest [19:27:26]: test storage: [--- + modprobe: FATAL: Module scsi_debug not found in directory /lib/modules/4.18.0-1011-kvm + ERROR + + == + ERROR: setUpClass (__main__.CryptsetupTest) + -- + Traceback (most recent call last): + File "/tmp/autopkgtest.azsL0q/build.Hbd/src/debian/tests/storage", line 21, in setUpClass + subprocess.check_call(['modprobe', 'scsi_debug']) + File "/usr/lib/python3.6/subprocess.py", line 291, in check_call + raise CalledProcessError(retcode, cmd) + subprocess.CalledProcessError: Command '['modprobe', 'scsi_debug']' returned non-zero exit status 1. + + + this has attempted to be fixed in disco/eoan so the output is a bit different across different releases, but all of them have the common point of failing to modprobe or rmmod the scsi_debug module, which by itself doesn't indicate a failure. [regression potential] low; this is fixing a testcase only. ** Tags added: ddstreet-next -- 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/1829347 Title: systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [impact] systemd autopkgtest fails [test case] run systemd autopkgtest, check for output like: LUKS device with "tmp" option ... rmmod: ERROR: Module scsi_debug is in use FAIL == FAIL: test_luks_tmp (__main__.CryptsetupTest) LUKS device with "tmp" option -- Traceback (most recent call last): File "/tmp/autopkgtest.It858Q/build.e7O/src/debian/tests/storage", line 59, in setUp self.fail('%s exists already' % self.plaintext_dev) AssertionError: /dev/mapper/testcrypt1 exists already or for older releases something like: autopkgtest [19:27:26]: test storage: [--- modprobe: FATAL: Module scsi_debug not found in directory /lib/modules/4.18.0-1011-kvm ERROR == ERROR: setUpClass (__main__.CryptsetupTest) -- Traceback (most recent call last): File "/tmp/autopkgtest.azsL0q/build.Hbd/src/debian/tests/storage", line 21, in setUpClass
[Touch-packages] [Bug 1828749] Re: ifconfig dummy0 : Device not found
Thank you for the additional information. I think this report is now complete, and I think I understand exactly what you mean and how you are affected. Unfortunately the use cases you have presented don't change my opinion that this is an unusual end-user configuration that is unlikely to affect the majority of Ubuntu users. Therefore I don't intend to prioritise working on it and don't expect other developers to volunteer their time to do so. My opinion will of course change if it turns out that there is some other use case that is likely to impact a wider range of Ubuntu users. Volunteers to investigate this problem deeper are welcome. Please do continue to use this bug to coordinate any efforts. ** Changed in: ifupdown (Ubuntu) Status: Incomplete => New ** Changed in: ifupdown (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1828749 Title: ifconfig dummy0 : Device not found Status in ifupdown package in Ubuntu: New Status in net-tools package in Ubuntu: New Bug description: Desired behavior: The ifconfig command should be able to deal with the dummy device. This worked fine until recently. Observed behavior: :; ifconfig dummy0 dummy0: error fetching interface information: Device not found This problem appeared when I upgraded to bionic. Highly informative workaround: :; ip link add dummy0 type dummy That command works, and makes the problem go away permanently. The ifconfig command works fine after that. The ifup and ifdown commands also work fine after that. For convenient debugging, you can use the command: :; ip link del dummy0 type dummy which makes the problem come back. You can also experiment with dummy1 et cetera. Package ownership issues: Compare: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909204 That report was filed against ippusbxd, which is almost certainly not the relevant package. For that matter, I have no idea whether the root cause is in the net-tools package or the kernel networking stack. All I know is the ip command plays nicely with the kernel while the ifconfig command does not. Notes: The kernel module for the dummy interface is preloaded in all situations described here. That's not the issue. An apport file is attached, to describe the environment. Also, since you asked: :; apt-cache policy net-tools net-tools: Installed: 1.60-26ubuntu1 Candidate: 1.60-26ubuntu1 Version table: *** 1.60-26ubuntu1 500 500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status :; lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1828749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829347] [NEW] systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug
Public bug reported: [impact] systemd autopkgtest fails [test case] run systemd autopkgtest, check for output like: LUKS device with "tmp" option ... rmmod: ERROR: Module scsi_debug is in use FAIL == FAIL: test_luks_tmp (__main__.CryptsetupTest) LUKS device with "tmp" option -- Traceback (most recent call last): File "/tmp/autopkgtest.It858Q/build.e7O/src/debian/tests/storage", line 59, in setUp self.fail('%s exists already' % self.plaintext_dev) AssertionError: /dev/mapper/testcrypt1 exists already this has attempted to be fixed in various ways so the output is a bit different across different releases, but all of them have the common point of failing to modprobe or rmmod the scsi_debug module, which by itself doesn't indicate a failure. [regression potential] low; this is fixing a testcase only. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829347 Title: systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug Status in systemd package in Ubuntu: New Bug description: [impact] systemd autopkgtest fails [test case] run systemd autopkgtest, check for output like: LUKS device with "tmp" option ... rmmod: ERROR: Module scsi_debug is in use FAIL == FAIL: test_luks_tmp (__main__.CryptsetupTest) LUKS device with "tmp" option -- Traceback (most recent call last): File "/tmp/autopkgtest.It858Q/build.e7O/src/debian/tests/storage", line 59, in setUp self.fail('%s exists already' % self.plaintext_dev) AssertionError: /dev/mapper/testcrypt1 exists already this has attempted to be fixed in various ways so the output is a bit different across different releases, but all of them have the common point of failing to modprobe or rmmod the scsi_debug module, which by itself doesn't indicate a failure. [regression potential] low; this is fixing a testcase only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825378] Re: systemd-networkd doesn't set wireguard peer endpoint
This issue can be reproduced without remote server. thanks for the brushup. ** Description changed: [impact] systemd does not set endpoints for wireguard interfaces correctly. This makes wireguard unusable. [test case] install a disco or eoan system and set up a wireguard interface: $ sudo add-apt-repository ppa:wireguard/wireguard $ sudo apt install wireguard ...(this does a lot of stuff)... - set up a wireguard server on a separate (pre-disco) system - (I used instructions from https://www.linode.com/docs/networking/vpn/set-up-wireguard-vpn-on-ubuntu/#configure-wireguard-server) - - create a file as below; the private key doesn't matter (can create one - with 'wg genkey'), but the WireGuardPeer public key and ip addresses - should match what the wireguard server set up above is using: + create a file as below; There is no need to setup remote server to + reproduce this issue, but PublicKey/PrivateKey should be valid one (used + instructions from https://www.linode.com/docs/networking/vpn/set-up- + wireguard-vpn-on-ubuntu/#configure-wireguard-server): $ cat /etc/systemd/network/wg0.netdev [NetDev] Name=wg0 Kind=wireguard [WireGuard] - PrivateKey=* + PrivateKey=uMuCbguKYdKanRYMbDSriIdgxGxJR57Us1zEy8wRc1M= ListenPort=51820 [WireGuardPeer] - PublicKey=* + PublicKey=ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 $ sudo systemctl restart systemd-networkd $ sudo wg show wg0 interface: wg0 - public key: * - private key: (hidden) - listening port: 51820 + public key: BnvFgvPiVb5xURfzZ5liV1P77qeGeJDIX3C1iNquA2k= + private key: (hidden) + listening port: 51820 - peer: * - allowed ips: 10.0.0.0/8 + peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= + allowed ips: 10.0.0.0/8 the last command should print remote endpoint address, e.g.: - peer: * - endpoint: 192.168.1.1:51820 - allowed ips: 10.0.0.0/8 + peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= + endpoint: 192.168.1.1:51820 + allowed ips: 10.0.0.0/8 [regression potential] any changes to systemd contain the potential for serious regressions. However, this is cherry picked directly from upstream, with the releases requiring patching (disco and eoan) being at exactly the same version and very close to upstream already. Additionally, while this does add 2 new functions (from upstream commit https://github.com/systemd/systemd/pull/11580/commits/abd48ec87f2ac5dd571a99dcb4db88c4affdffc8), they are only used - and code is only changed in - wireguard.c, so any regressions should be limited to wireguard interfaces (unless systemd crashes completely). [other info] this bug is not present in cosmic and earlier, and is already fixed in upstream systemd, so this is needed only for disco and eoan. original description: --- systemd/disco 240 shipped with Ubuntu 19.04 beta does not set endpoints for [WireguradPeer] properly. This regression was introduced in v241 and merged into v240. systemd 241 doesn't set wireguard peer endpoint https://github.com/systemd/systemd/issues/11579 Revert of the regression was landed on v240 stable branch https://github.com/systemd/systemd-stable/pull/39 1)2) confirmed with, systemd/disco 240-6ubuntu5 amd64 3) put a netdev file /etc/systemd/network/wg0.netdev --- [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=** ListenPort=51820 [WireGuardPeer] PublicKey=* AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 and run --- # systemctl restart systemd-networkd # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * allowed ips: 10.0.0.0/8 4) the last command should print remote endpoint address. --- # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 -- 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/1825378 Title: systemd-networkd doesn't set wireguard peer endpoint Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [impact] systemd does not set endpoints for wireguard interfaces correctly. This makes wireguard unusable. [test case] install a disco or eoan system and set up a wireguard interface: $ sudo add-apt-repository ppa:wireguard/wireguard $ sudo apt install wireguard ...(this does a lot of stuff)...
[Touch-packages] [Bug 1822270] Re: Debconf readline frontend does not show options
This bug was fixed in the package debconf - 1.5.69ubuntu1 --- debconf (1.5.69ubuntu1) cosmic; urgency=medium * Fix readline prompts when run via run-parts (LP: #1822270) - Debconf/FrontEnd/Readline.pm: force output to stdout if both stdout and stderr are pipes -- Heitor Alves de Siqueira Mon, 06 May 2019 13:27:55 -0300 ** Changed in: debconf (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 debconf in Ubuntu. https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: Fix Released Status in debconf source package in Xenial: Fix Committed Status in debconf source package in Bionic: Fix Committed Status in debconf source package in Cosmic: Fix Released Status in debconf source package in Disco: Fix Released Status in debconf source package in Eoan: Fix Released Status in debconf package in Debian: Fix Released Bug description: [Impact] debconf prompts the user for input before displaying options [Description] When upgrading packages with apt or dpkg, debconf scripts are ran through 'run-parts' with the '--report' flag. This causes script output to be handled through pipes set up by run-parts, and buffers output from maintainer scripts nicely for formatting. If debconf makes use of the readline frontend, any prompts will bypass the run-parts buffers and be displayed directly to /dev/tty. This generally causes the prompt to be displayed before the user gets any of the available options for it, and printing will block until the user inputs a valid option. Upstream commit: https://salsa.debian.org/pkg- debconf/debconf/commit/48c5ce38cfd5 [Test Case] 1) Deploy a VM through e.g. uvt-kvm $ uvt-kvm create disco release=disco 2) Remove the whiptail package to force the readline frontend in debconf root@disco:~# apt remove --purge whiptail -y 3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade through run-parts root@disco:~# apt update && apt install -y grub-legacy-ec2 root@disco:~# rm -f /boot/grub/menu.lst* root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst 4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we just need it to think menu.lst needs an upgrade) root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report ... /etc/kernel/postinst.d/x-grub-legacy-ec2: debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... What would you like to do about menu.lst? The "What would you like to do about menu.lst?" prompt will block until the user enter a valid option, even though it's being displayed before the available options. [Regression Potential] We could hit regressions if changing debconf's printing to /dev/tty is expected by other programs. The changes are needed only in the readline frontend, so that would minimize impact of any possible regressions. The fixes will be thoroughly tested with autopkgtest and use-case scenarios. # # # # [Original Description] When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828846] Re: ecra
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1828846 Title: ecra Status in xorg package in Ubuntu: Incomplete Bug description: Notebook hp elitebook 8440p com sensor de rotação da tela, ao instalar ubuntu19 ele reconhece a tela virada 180 graus e o ponteiro do mouse no sentindo certo. Ao tentar inverter a tela através de comandos ou configuração ela vira porem o mouse ainda fica invertido. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 13 15:54:42 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:172a] MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=3a114823-2ff8-428d-8823-ecbf3fb1e030 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.0B dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.2C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.0B:bd06/02/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.2C:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.product.sku: SJ905UP#ABA dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A 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.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/xorg/+bug/1828846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822270] Update Released
The verification of the Stable Release Update for debconf 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 debconf in Ubuntu. https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: Fix Released Status in debconf source package in Xenial: Fix Committed Status in debconf source package in Bionic: Fix Committed Status in debconf source package in Cosmic: Fix Committed Status in debconf source package in Disco: Fix Released Status in debconf source package in Eoan: Fix Released Status in debconf package in Debian: Fix Released Bug description: [Impact] debconf prompts the user for input before displaying options [Description] When upgrading packages with apt or dpkg, debconf scripts are ran through 'run-parts' with the '--report' flag. This causes script output to be handled through pipes set up by run-parts, and buffers output from maintainer scripts nicely for formatting. If debconf makes use of the readline frontend, any prompts will bypass the run-parts buffers and be displayed directly to /dev/tty. This generally causes the prompt to be displayed before the user gets any of the available options for it, and printing will block until the user inputs a valid option. Upstream commit: https://salsa.debian.org/pkg- debconf/debconf/commit/48c5ce38cfd5 [Test Case] 1) Deploy a VM through e.g. uvt-kvm $ uvt-kvm create disco release=disco 2) Remove the whiptail package to force the readline frontend in debconf root@disco:~# apt remove --purge whiptail -y 3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade through run-parts root@disco:~# apt update && apt install -y grub-legacy-ec2 root@disco:~# rm -f /boot/grub/menu.lst* root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst 4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we just need it to think menu.lst needs an upgrade) root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report ... /etc/kernel/postinst.d/x-grub-legacy-ec2: debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... What would you like to do about menu.lst? The "What would you like to do about menu.lst?" prompt will block until the user enter a valid option, even though it's being displayed before the available options. [Regression Potential] We could hit regressions if changing debconf's printing to /dev/tty is expected by other programs. The changes are needed only in the readline frontend, so that would minimize impact of any possible regressions. The fixes will be thoroughly tested with autopkgtest and use-case scenarios. # # # # [Original Description] When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822270] Re: Debconf readline frontend does not show options
This bug was fixed in the package debconf - 1.5.71ubuntu1 --- debconf (1.5.71ubuntu1) disco; urgency=medium * Fix readline prompts when run via run-parts (LP: #1822270) - Debconf/FrontEnd/Readline.pm: force output to stdout if both stdout and stderr are pipes -- Heitor Alves de Siqueira Mon, 06 May 2019 13:16:57 -0300 ** Changed in: debconf (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: Fix Released Status in debconf source package in Xenial: Fix Committed Status in debconf source package in Bionic: Fix Committed Status in debconf source package in Cosmic: Fix Committed Status in debconf source package in Disco: Fix Released Status in debconf source package in Eoan: Fix Released Status in debconf package in Debian: Fix Released Bug description: [Impact] debconf prompts the user for input before displaying options [Description] When upgrading packages with apt or dpkg, debconf scripts are ran through 'run-parts' with the '--report' flag. This causes script output to be handled through pipes set up by run-parts, and buffers output from maintainer scripts nicely for formatting. If debconf makes use of the readline frontend, any prompts will bypass the run-parts buffers and be displayed directly to /dev/tty. This generally causes the prompt to be displayed before the user gets any of the available options for it, and printing will block until the user inputs a valid option. Upstream commit: https://salsa.debian.org/pkg- debconf/debconf/commit/48c5ce38cfd5 [Test Case] 1) Deploy a VM through e.g. uvt-kvm $ uvt-kvm create disco release=disco 2) Remove the whiptail package to force the readline frontend in debconf root@disco:~# apt remove --purge whiptail -y 3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade through run-parts root@disco:~# apt update && apt install -y grub-legacy-ec2 root@disco:~# rm -f /boot/grub/menu.lst* root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst 4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we just need it to think menu.lst needs an upgrade) root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report ... /etc/kernel/postinst.d/x-grub-legacy-ec2: debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... What would you like to do about menu.lst? The "What would you like to do about menu.lst?" prompt will block until the user enter a valid option, even though it's being displayed before the available options. [Regression Potential] We could hit regressions if changing debconf's printing to /dev/tty is expected by other programs. The changes are needed only in the readline frontend, so that would minimize impact of any possible regressions. The fixes will be thoroughly tested with autopkgtest and use-case scenarios. # # # # [Original Description] When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent
This bug was fixed in the package bash - 4.4.18-2ubuntu1.1 --- bash (4.4.18-2ubuntu1.1) bionic; urgency=medium * Resurrect "Set the default path to comply with Debian policy" in deb-bash-config.diff which went missing since 4.2+dfsg-1 or so. LP: #1792004 LP: #1614080 Closes: #781367 * Add autopkgtest for the built-in path. -- Dimitri John Ledkov Fri, 03 May 2019 14:50:32 +0100 ** Changed in: bash (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1792004 Title: built-in PATH seems to have sbin and bin out of order; and inconsistent Status in apt package in Ubuntu: Fix Released Status in bash package in Ubuntu: Fix Released Status in busybox package in Ubuntu: New Status in dash package in Ubuntu: New Status in dpkg package in Ubuntu: Won't Fix Status in pam package in Ubuntu: New Status in systemd package in Ubuntu: New Status in bash source package in Xenial: Fix Committed Status in bash source package in Bionic: Fix Released Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: Fix Released Bug description: [Impact] * For consistency reasons sbin should be ordered before bin in PATH. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' And check that matching pairs in PATH, have /sbin variant leading /bin variant. [Regression Potential] * Ubuntu does not ship duplicate binries, with different behaviour between /sbin and /bin, thus all binaries will continue to be found in all locations. Also PATH is normally already set in the environment, and this change only affects the fallback path when bash is executed without any environment, i.e. booting with 'init=/bin/bash' [Other Info] * Original bug report detailing inconsistent paths between various shells. --- $ env -u PATH /bin/sh -c 'echo $PATH' /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ env -u PATH /bin/dash -c 'echo $PATH' /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ systemd-run --unit test-env env # ... and check journal for PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ env -u PATH /bin/bash -c 'echo $PATH' /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. $ env -u PATH /bin/busybox sh -c 'echo $PATH' /sbin:/usr/sbin:/bin:/usr/bin $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/ initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin' initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} exported as PATH dracut-047+31/modules.d/99shutdown/shutdown.sh:export PATH=/usr/sbin:/usr/bin:/sbin:/bin $ cat /etc/environment PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" apt & dpkg => should probably initiate /usr/local-less PATH Imho the rest should probably be harmonised to: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin === From a duplicate https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 : $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; done 12.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 12.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 14.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 14.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 16.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. I believe later releases of bash, do too include CWD in the built-in PATH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1792004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
This looks likely to be some kind of incompatibility with full-disk encrypted systems. I just spotted that the errors I am getting are not about the swap partition at all, but instead about /dev/mapper/xubuntu --vg-root, which is the encrypted root. From /etc/fstab: /dev/mapper/xubuntu--vg-root / ext4errors=remount-ro 0 1 -- 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/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in ubiquity source package in Bionic: Fix Released Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1614080] Update Released
The verification of the Stable Release Update for bash 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 bash in Ubuntu. https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash Status in bash package in Ubuntu: Fix Released Status in bash source package in Precise: Fix Released Status in bash source package in Trusty: Won't Fix Status in bash source package in Xenial: Fix Committed Status in bash source package in Bionic: Fix Committed Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: Fix Released Status in bash source package in Eoan: Fix Released Status in bash package in Debian: New Bug description: [Impact] * The fallback path built into bash contains '.' which leads to unexpected addition of the current working directory. It should not be there, just like it isnt' in pre-precise and cosmic+. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' Should not have '.' as any component. Nor should there be any empty components, i.e. '::'. [Regression Potential] * Normally PATH is always set by either init, systemd, or any other hypervisor. Thus this only affects executions under bash, when it was started without any environment - e.g. booting with 'init=/bin/bash'. [Other Info] * Original bug report. On ubuntu 16.04 (but also 14.04), running bash with PATH unset always adds '.' to PATH: philippe@pv-desktop:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games philippe@pv-desktop:~$ unset PATH philippe@pv-desktop:~$ /bin/bash philippe@pv-desktop:~$ echo $PATH /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. Even when testing in a virtual machine / docker, and erasing /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem still happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash
This bug was fixed in the package bash - 5.0-3ubuntu1.1 --- bash (5.0-3ubuntu1.1) disco; urgency=medium * Resurrect "Set the default path to comply with Debian policy" in deb-bash-config.diff which went missing since 4.2+dfsg-1 or so. LP: #1792004 LP: #1614080 Closes: #781367 * Add autopkgtest for the built-in path. -- Dimitri John Ledkov Fri, 03 May 2019 14:31:24 +0100 ** Changed in: bash (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash Status in bash package in Ubuntu: Fix Released Status in bash source package in Precise: Fix Released Status in bash source package in Trusty: Won't Fix Status in bash source package in Xenial: Fix Committed Status in bash source package in Bionic: Fix Committed Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: Fix Released Status in bash source package in Eoan: Fix Released Status in bash package in Debian: New Bug description: [Impact] * The fallback path built into bash contains '.' which leads to unexpected addition of the current working directory. It should not be there, just like it isnt' in pre-precise and cosmic+. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' Should not have '.' as any component. Nor should there be any empty components, i.e. '::'. [Regression Potential] * Normally PATH is always set by either init, systemd, or any other hypervisor. Thus this only affects executions under bash, when it was started without any environment - e.g. booting with 'init=/bin/bash'. [Other Info] * Original bug report. On ubuntu 16.04 (but also 14.04), running bash with PATH unset always adds '.' to PATH: philippe@pv-desktop:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games philippe@pv-desktop:~$ unset PATH philippe@pv-desktop:~$ /bin/bash philippe@pv-desktop:~$ echo $PATH /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. Even when testing in a virtual machine / docker, and erasing /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem still happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent
This bug was fixed in the package bash - 5.0-3ubuntu1.1 --- bash (5.0-3ubuntu1.1) disco; urgency=medium * Resurrect "Set the default path to comply with Debian policy" in deb-bash-config.diff which went missing since 4.2+dfsg-1 or so. LP: #1792004 LP: #1614080 Closes: #781367 * Add autopkgtest for the built-in path. -- Dimitri John Ledkov Fri, 03 May 2019 14:31:24 +0100 ** Changed in: bash (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1792004 Title: built-in PATH seems to have sbin and bin out of order; and inconsistent Status in apt package in Ubuntu: Fix Released Status in bash package in Ubuntu: Fix Released Status in busybox package in Ubuntu: New Status in dash package in Ubuntu: New Status in dpkg package in Ubuntu: Won't Fix Status in pam package in Ubuntu: New Status in systemd package in Ubuntu: New Status in bash source package in Xenial: Fix Committed Status in bash source package in Bionic: Fix Committed Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: Fix Released Bug description: [Impact] * For consistency reasons sbin should be ordered before bin in PATH. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' And check that matching pairs in PATH, have /sbin variant leading /bin variant. [Regression Potential] * Ubuntu does not ship duplicate binries, with different behaviour between /sbin and /bin, thus all binaries will continue to be found in all locations. Also PATH is normally already set in the environment, and this change only affects the fallback path when bash is executed without any environment, i.e. booting with 'init=/bin/bash' [Other Info] * Original bug report detailing inconsistent paths between various shells. --- $ env -u PATH /bin/sh -c 'echo $PATH' /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ env -u PATH /bin/dash -c 'echo $PATH' /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ systemd-run --unit test-env env # ... and check journal for PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ env -u PATH /bin/bash -c 'echo $PATH' /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. $ env -u PATH /bin/busybox sh -c 'echo $PATH' /sbin:/usr/sbin:/bin:/usr/bin $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/ initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin' initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} exported as PATH dracut-047+31/modules.d/99shutdown/shutdown.sh:export PATH=/usr/sbin:/usr/bin:/sbin:/bin $ cat /etc/environment PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" apt & dpkg => should probably initiate /usr/local-less PATH Imho the rest should probably be harmonised to: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin === From a duplicate https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 : $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; done 12.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 12.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 14.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 14.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 16.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. I believe later releases of bash, do too include CWD in the built-in PATH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1792004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792004] Update Released
The verification of the Stable Release Update for bash 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1792004 Title: built-in PATH seems to have sbin and bin out of order; and inconsistent Status in apt package in Ubuntu: Fix Released Status in bash package in Ubuntu: Fix Released Status in busybox package in Ubuntu: New Status in dash package in Ubuntu: New Status in dpkg package in Ubuntu: Won't Fix Status in pam package in Ubuntu: New Status in systemd package in Ubuntu: New Status in bash source package in Xenial: Fix Committed Status in bash source package in Bionic: Fix Committed Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: Fix Released Bug description: [Impact] * For consistency reasons sbin should be ordered before bin in PATH. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' And check that matching pairs in PATH, have /sbin variant leading /bin variant. [Regression Potential] * Ubuntu does not ship duplicate binries, with different behaviour between /sbin and /bin, thus all binaries will continue to be found in all locations. Also PATH is normally already set in the environment, and this change only affects the fallback path when bash is executed without any environment, i.e. booting with 'init=/bin/bash' [Other Info] * Original bug report detailing inconsistent paths between various shells. --- $ env -u PATH /bin/sh -c 'echo $PATH' /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ env -u PATH /bin/dash -c 'echo $PATH' /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ systemd-run --unit test-env env # ... and check journal for PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin $ env -u PATH /bin/bash -c 'echo $PATH' /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. $ env -u PATH /bin/busybox sh -c 'echo $PATH' /sbin:/usr/sbin:/bin:/usr/bin $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/ initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin' initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} exported as PATH dracut-047+31/modules.d/99shutdown/shutdown.sh:export PATH=/usr/sbin:/usr/bin:/sbin:/bin $ cat /etc/environment PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" apt & dpkg => should probably initiate /usr/local-less PATH Imho the rest should probably be harmonised to: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin === From a duplicate https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 : $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; done 12.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 12.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 14.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 14.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 16.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. I believe later releases of bash, do too include CWD in the built-in PATH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1792004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 652870] Re: Avahi update causes internet connetions to fail
Whether you are shopping online or in store, using coupon sites can save you money. Here are the best coupon websites to save the most forever 21 coupons https://www.couponmall.net/store/forever-21/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/652870 Title: Avahi update causes internet connetions to fail Status in avahi package in Ubuntu: Invalid Bug description: I'm using Lucid with all updates applied as of a week ago. Everthing on my system was working fine until this mornings system update. Part of the update was patches to Avahi "Version 0.6.25-1ubuntu6.1". After reboot, I couldn't get onto the internet. When I looked at ifconfig, I normally have eth2 & lo entries. The problem seems to be a new eth2:avahi entry that had an IP address assigned that isn't in my LAN. The eth2 entry was also there, but didn't have an IP. I solved this, sort of, by editing /etc/default/avahi-daemon and setting AVAHI_DAEMON_DETECT_LOCAL=0 instead of 1. That's a patch I found on http://ubuntuforums.org/showthread.php?t=1339516 answering "How do I disable Avahi??" After a reboot, I could connect to the internet again. However, some things started behaving strangely. Like the colours of everything had changed as though the theme had been changed. Just going into the Preferences/Appearance seemed to be enough to fix it - I didn't have to click anything else. Very odd. Might be related to a different update package. FWIW. I don't think I need the avahi services from what I understand of it. I'm running Ubuntu Lucid within a VMware virtual machine on an XP host. It's a laptop, so the network environment does change twice a day. But, as I said, everything was stable until this mornings update. I've since rolled back to a VM snapshot prior to the update and I'm going to delay updates for a little while, but I can reinstate the snapshot containing the update if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/652870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash
This bug was fixed in the package bash - 4.4.18-2ubuntu1.1 --- bash (4.4.18-2ubuntu1.1) bionic; urgency=medium * Resurrect "Set the default path to comply with Debian policy" in deb-bash-config.diff which went missing since 4.2+dfsg-1 or so. LP: #1792004 LP: #1614080 Closes: #781367 * Add autopkgtest for the built-in path. -- Dimitri John Ledkov Fri, 03 May 2019 14:50:32 +0100 ** Changed in: bash (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash Status in bash package in Ubuntu: Fix Released Status in bash source package in Precise: Fix Released Status in bash source package in Trusty: Won't Fix Status in bash source package in Xenial: Fix Committed Status in bash source package in Bionic: Fix Released Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: Fix Released Status in bash source package in Eoan: Fix Released Status in bash package in Debian: New Bug description: [Impact] * The fallback path built into bash contains '.' which leads to unexpected addition of the current working directory. It should not be there, just like it isnt' in pre-precise and cosmic+. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' Should not have '.' as any component. Nor should there be any empty components, i.e. '::'. [Regression Potential] * Normally PATH is always set by either init, systemd, or any other hypervisor. Thus this only affects executions under bash, when it was started without any environment - e.g. booting with 'init=/bin/bash'. [Other Info] * Original bug report. On ubuntu 16.04 (but also 14.04), running bash with PATH unset always adds '.' to PATH: philippe@pv-desktop:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games philippe@pv-desktop:~$ unset PATH philippe@pv-desktop:~$ /bin/bash philippe@pv-desktop:~$ echo $PATH /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. Even when testing in a virtual machine / docker, and erasing /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem still happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829397] [NEW] package linux-image-4.4.0-148-generic 4.4.0-148.174 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Server reported error - package linux-image-4.4.0-148-generic 4.4.0-148.174 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-148-generic 4.4.0-148.174 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu May 16 06:22:57 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2016-09-21 (967 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: initramfs-tools Title: package linux-image-4.4.0-148-generic 4.4.0-148.174 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1829397 Title: package linux-image-4.4.0-148-generic 4.4.0-148.174 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Server reported error - package linux-image-4.4.0-148-generic 4.4.0-148.174 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-148-generic 4.4.0-148.174 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu May 16 06:22:57 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2016-09-21 (967 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: initramfs-tools Title: package linux-image-4.4.0-148-generic 4.4.0-148.174 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829397/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829400] [NEW] screen loop after suspension
Public bug reported: Hello, I have a DELL PA-10 wtih GM965 intel graphic card. It couldn't boot with 4.15 kernel and I have to use 4.4.0. I'm using the default driver, I didn't find an other. The computer boot faster aplying this fix but I continue to have a problem with the suspension. After after a suspension the screen blink between two kind of blank screen and never start. Is there a solution for that? Thanks, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 16 17:03:54 2019 DistUpgraded: 2019-04-27 17:06:11,246 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude D630 [1028:01f9] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:01f9] InstallationDate: Installed on 2016-06-18 (1062 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Dell Inc. Latitude D630 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-146-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2019-04-27 (18 days ago) dmi.bios.date: 11/24/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd11/24/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1829400 Title: screen loop after suspension Status in xorg package in Ubuntu: New Bug description: Hello, I have a DELL PA-10 wtih GM965 intel graphic card. It couldn't boot with 4.15 kernel and I have to use 4.4.0. I'm using the default driver, I didn't find an other. The computer boot faster aplying this fix but I continue to have a problem with the suspension. After after a suspension the screen blink between two kind of blank screen and never start. Is there a solution for that? Thanks, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 16 17:03:54 2019 DistUpgraded: 2019-04-27 17:06:11,246 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude D630 [1028:01f9] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:01f9] InstallationDate: Installed on 2016-06-18 (1062 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Dell Inc. Latitude D630 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-146-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2019-04-27 (18 days
[Touch-packages] [Bug 1823422] Re: heimdal ftbfs in disco
The upstream issue links to a commit that fixes it: https://github.com/quanah/heimdal/commit/e3cd069e5c40b455541508b81ffeb0563e882aed The above commit, as I understand it, is the result of running some script to regenerate the certificates used in the test suite, and then the results were committed. For deb packages, it's a bit of a challenge because it includes binary changes, which can't be represented in a debian/patch/.patch This comment has a hint about the 32bit issue: https://github.com/heimdal/heimdal/issues/533#issuecomment-477264834 Personally I would prefer to have the test certificates regenerated prior to each test run. That would also handle the 32bit issue, as long as certs expire "soon" (like, on the month of the test run for example). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1823422 Title: heimdal ftbfs in disco Status in Heimdal: New Status in heimdal package in Ubuntu: Triaged Bug description: https://launchpadlibrarian.net/417925401/buildlog_ubuntu-disco- amd64.heimdal_7.5.0+dfsg-2.1_BUILDING.txt.gz = Heimdal 7.5.0: lib/hx509/test-suite.log = # TOTAL: 16 # PASS: 15 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test_chain cert -> root cert -> root cert -> root sub-cert -> root sub-cert -> sub-ca -> root sub-cert -> sub-ca sub-cert -> sub-ca -> root sub-cert -> sub-ca -> root sub-cert -> sub-ca -> root max depth 2 (ok) max depth 1 (fail) ocsp non-ca responder ocsp ca responder ocsp no-ca responder, missing cert ocsp no-ca responder, missing cert, in pool ocsp no-ca responder, keyHash ocsp revoked cert ocsp print reply resp1-ocsp-no-cert ocsp print reply resp1-ca ocsp print reply resp1-keyhash ocsp print reply resp2 ocsp verify exists ocsp verify not exists ocsp verify revoked crl non-revoked cert FAIL test_chain (exit status: 1) Testsuite summary for Heimdal 7.5.0 # TOTAL: 16 # PASS: 15 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See lib/hx509/test-suite.log Please report to https://github.com/heimdal/heimdal/issues To manage notifications about this bug go to: https://bugs.launchpad.net/heimdal/+bug/1823422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1465766] Re: low sound volume
I have a similar issue on Debian 9 (Stretch) on a Lenovo X1 Carbon 6th Gen laptop. DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET63W (1.38 ) 04/20/2019 The built-in speaker volume is limited to about 20% even if the volume is set at 100%. The sound card is a ALC285 handled by the snd_hda_intel driver. On my kernel (4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13)), I managed to find this work-around which addresses the low volume issue: Edit /etc/modprobe.d/alsa-base.conf add the following line: options snd-hda-intel model=nofixup After modprobe -r/modprobe of the snd_hda_intel module (or reboot), the volume works fine. Hopefully this can help others facing this open issue as well. Here is the output of lspci -vvv for the sound card: 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) (prog-if 80) Subsystem: Lenovo Device 225c Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1465766 Title: low sound volume Status in alsa-driver package in Ubuntu: Confirmed Bug description: this is a thinkpad x1 carbon 3rd gen running xubuntu 15.04 sound volume is very low compared to windows (dual boot), even with alsa and pulseaudio controls set to 100% (or greater). this applies to all apps. i can get really loud sound with: pactl set-sink-volume 1 30 but then it is very distorted. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: smwilson 1577 F pulseaudio /dev/snd/controlC0: smwilson 1577 F pulseaudio CurrentDesktop: XFCE Date: Tue Jun 16 06:44:39 2015 InstallationDate: Installed on 2015-06-04 (11 days ago) InstallationMedia: Xubuntu Core 15.04 - amd64 - 20150425 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Volume slider, or mixer problems Title: [20BSCTO1WW, Realtek ALC3232, Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET25W (1.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET25W(1.03):bd12/01/2014:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1465766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1100326] Re: Location requested by websites should be able to use GPS/mobile positioning
** Changed in: firefox Status: Confirmed => Unknown ** Changed in: firefox Importance: Wishlist => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to geoclue-providers in Ubuntu. https://bugs.launchpad.net/bugs/1100326 Title: Location requested by websites should be able to use GPS/mobile positioning Status in Chromium Browser: Fix Committed Status in Mozilla Firefox: Unknown Status in GeoClue: Won't Fix Status in WebKit: Fix Released Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-providers package in Ubuntu: Invalid Bug description: It would be nice if location requested by websites could use location found from GPS or GSM/CDMA positioning. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1100326/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827879] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1827879 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: disco -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp