[Touch-packages] [Bug 1939187] Re: package base-passwd 3.5.49ubuntu1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1939187 Title: package base-passwd 3.5.49ubuntu1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4 Status in base-passwd package in Ubuntu: New Bug description: Error received on do-release-upgrade. ProblemType: Package DistroRelease: Ubuntu 21.04 Package: base-passwd 3.5.49ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-63.71-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 7 01:21:35 2021 ErrorMessage: installed base-passwd package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-08 (1216 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: libc6 libc6 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.1.10ubuntu0.3 SourcePackage: base-passwd Title: package base-passwd 3.5.49ubuntu1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to hirsute on 2021-08-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1939187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939187] [NEW] package base-passwd 3.5.49ubuntu1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4
Public bug reported: Error received on do-release-upgrade. ProblemType: Package DistroRelease: Ubuntu 21.04 Package: base-passwd 3.5.49ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-63.71-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 7 01:21:35 2021 ErrorMessage: installed base-passwd package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-08 (1216 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: libc6 libc6 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.1.10ubuntu0.3 SourcePackage: base-passwd Title: package base-passwd 3.5.49ubuntu1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to hirsute on 2021-08-06 (0 days ago) ** Affects: base-passwd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1939187 Title: package base-passwd 3.5.49ubuntu1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4 Status in base-passwd package in Ubuntu: New Bug description: Error received on do-release-upgrade. ProblemType: Package DistroRelease: Ubuntu 21.04 Package: base-passwd 3.5.49ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-63.71-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 7 01:21:35 2021 ErrorMessage: installed base-passwd package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-08 (1216 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: libc6 libc6 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.1.10ubuntu0.3 SourcePackage: base-passwd Title: package base-passwd 3.5.49ubuntu1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to hirsute on 2021-08-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1939187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931077] Re: emergency shell ignores all keyboard input
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1931077 Title: emergency shell ignores all keyboard input Status in systemd package in Ubuntu: Expired Bug description: An SSD that held my /boot/efi partition failed, took down local-fs.target, which brought up emergency.target. I ended up with no ssh access, and a message on the local console telling me to press Enter to get a root shell, or press Ctrl-D to continue booting normally. The system did not react to either Enter or Ctrl-D. I could switch between virtual consoles (but nothing was running on them, e.g. no getty), toggle Caps Lock, or reboot with Ctrl+Alt+Del. An emergency console that doesn't accept keyboard input is not a useful emergency console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.47 ProcVersionSignature: Ubuntu 4.15.0-144.148-generic 4.15.18 Uname: Linux 4.15.0-144-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Mon Jun 7 11:18:39 2021 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-144-generic root=/dev/mapper/hostname-root ro SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2019-08-12 (664 days ago) dmi.bios.date: 08/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd08/14/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1938005] Re: ufw ignores rules
You have not read description fully. After running `ufw reload` rules should restore completely to iptables but it doesn't happen in complete manner. ** Changed in: ufw (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1938005 Title: ufw ignores rules Status in ufw package in Ubuntu: New Bug description: With my setting I shouldn't be able to surf web, but I can do it (without proxy/vpn) This problem happens after `iptables -F` and only way to solve it, is to reboot PC. I tried `ufw reload` , too ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ufw 0.36-7.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Mon Jul 26 11:53:17 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-06-17 (38 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2021-07-25T22:22:29.221649 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1938005/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939173] Re: Screen flickering white vertical lines
** Description changed: The screen on my HP AIO computer flickers. I'm able to browse the computer, but it's giving me headache. Flickering consists pattern of 2cm height white vertical pixel lines (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section. Flicker also has 1px lines with dashes ending them about 10cm from left of the screen and 2cm from right of the screen. Mathematically letter W being 100% of screen width in above description. + Flickering seems to be consistent to screen refresh state (~60Hz). + Changing refresh rate does not affect in to amount of flickering. - Flickering seems to be consistent to screen refresh state (~60Hz). Changing refresh rate does not affect in to amount of flickering. + Same thing not happening in Windows nor BIOS. Even though this looks a + LOT like a hardware/wiring issue. Best regards, korho. - $ lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy xorg xorg: - Installed: 1:7.7+19ubuntu14 - Candidate: 1:7.7+19ubuntu14 - Version table: - *** 1:7.7+19ubuntu14 500 - 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:7.7+19ubuntu14 + Candidate: 1:7.7+19ubuntu14 + Version table: + *** 1:7.7+19ubuntu14 500 + 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 23:04:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] InstallationDate: Installed on 2021-08-06 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard 120-1100eo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=bf3dba7e-429f-455e-ac68-c016e272a4d9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: LEO_707 dmi.board.name: 2AC5 dmi.board.vendor: Quanta dmi.board.version: 100 dmi.chassis.asset.tag: CZC2128RP3 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-1100eo:pvr:rvnQuanta:rn2AC5:rvr100:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 120-1100eo dmi.product.sku: H1E79EA#UUW dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Description changed: The screen on my HP AIO computer flickers. I'm able to browse the computer, but it's giving me headache. Flickering consists pattern of 2cm height white vertical pixel lines (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section. Flicker also has 1px lines with dashes ending them about 10cm from left of the screen and 2cm from right of the screen. Mathematically letter W being 100% of screen width in above description. Flickering seems to be consistent to screen refresh state (~60Hz). Changing refresh rate does not affect in to amount of flickering. Same thing not happening in Windows nor BIOS. Even though this looks a LOT like a hardware/wiring issue. + + Also the problem is visible in Ubuntu installer, but not in graphic safe + one. Best regards, korho. $ lsb_release -rd: Description: Ubuntu 20.04.2 LTS
[Touch-packages] [Bug 1939173] [NEW] Screen flickering white vertical lines
Public bug reported: The screen on my HP AIO computer flickers. I'm able to browse the computer, but it's giving me headache. Flickering consists pattern of 2cm height white vertical pixel lines (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section. Flicker also has 1px lines with dashes ending them about 10cm from left of the screen and 2cm from right of the screen. Mathematically letter W being 100% of screen width in above description. Flickering seems to be consistent to screen refresh state (~60Hz). Changing refresh rate does not affect in to amount of flickering. Same thing not happening in Windows nor BIOS. Even though this looks a LOT like a hardware/wiring issue. Also the problem is visible in Ubuntu installer, but not in graphic safe one. Best regards, korho. $ lsb_release -rd: Description:Ubuntu 20.04.2 LTS Release:20.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 23:04:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] InstallationDate: Installed on 2021-08-06 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard 120-1100eo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=bf3dba7e-429f-455e-ac68-c016e272a4d9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: LEO_707 dmi.board.name: 2AC5 dmi.board.vendor: Quanta dmi.board.version: 100 dmi.chassis.asset.tag: CZC2128RP3 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-1100eo:pvr:rvnQuanta:rn2AC5:rvr100:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 120-1100eo dmi.product.sku: H1E79EA#UUW dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu wayland-session -- 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/1939173 Title: Screen flickering white vertical lines Status in xorg package in Ubuntu: New Bug description: The screen on my HP AIO computer flickers. I'm able to browse the computer, but it's giving me headache. Flickering consists pattern of 2cm height white vertical pixel lines (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section. Flicker also has 1px lines with dashes ending them about 10cm from left of the screen and 2cm from right of the screen. Mathematically letter W being 100% of screen width in above description. Flickering seems to be consistent to screen refresh state (~60Hz). Changing refresh rate does not affect in to amount of flickering. Same thing not happening in Windows nor BIOS. Even though this looks a LOT like a hardware/wiring issue. Also the problem is visible in Ubuntu installer, but not in graphic safe one. Best regards, korho. $ lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
Uploaded into bionic upload queue, now waiting for SRU approval. - Eric ** Changed in: systemd (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Eric Desrochers (slashd) -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in netplan: Confirmed Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Status in keepalived source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] version: 2 Configure keepalived (again, a working config with IP addresses obfuscated) global_defs # Block id { notification_email { sysadm...@blah.com } notification_email_from keepali...@system3.hq.blah.com smtp_server 10.22.11.7 # IP smtp_connect_timeout 30 # integer, seconds router_id system3 # string identifying the machine, # (doesn't have to be hostname). vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
[Touch-packages] [Bug 1938924] Re: Update crontab(5) manpage to match new behaviour
This bug was fixed in the package cron - 3.0pl1-137ubuntu2 --- cron (3.0pl1-137ubuntu2) impish; urgency=medium * Update crontab(5) manpage to match new behaviour (LP: #1938924) -- Graham Inggs Fri, 06 Aug 2021 10:59:44 + ** Changed in: cron (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1938924 Title: Update crontab(5) manpage to match new behaviour Status in cron package in Ubuntu: Fix Released Bug description: From LP: #1779767 comment 13: In crontab(5) in cron 3.0pl1-136ubuntu2 the manpage is now wrong. It says: > Several environment variables are set up automatically by the cron(8) daemon. > […] PATH is set to "/usr/bin:/bin". HOME, SHELL, and PATH may be overridden > by settings in the crontab […] and also > On the Debian GNU/Linux system, cron supports the pam_env module, and loads > the environment specified by /etc/environment and /etc/security/pam_env.conf. > It also reads locale information from /etc/default/locale. However, the PAM > settings do NOT override the settings described above nor any settings in the > crontab file itself. Note in particular that if you want a PATH other than > "/usr/bin:/bin", you will need to set it in the crontab file. These should be fixed I think. There might be other spots that I didn't notice yet too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1938924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 971555] Re: When logging out (or shuting down), after confirming to log out (shut down) the system goes into text mode for a while (0.5-3/4 seconds) before showing LDM or splash
upstart is no longer included in any currently supported release of Ubuntu. I'm closing this bug report with a status of "Invalid" in order to tidy the list of outstanding '100 Papercuts' issues. ** Changed in: hundredpapercuts Status: Confirmed => Invalid ** Changed in: upstart (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/971555 Title: When logging out (or shuting down), after confirming to log out (shut down) the system goes into text mode for a while (0.5-3/4 seconds) before showing LDM or splash screen. Status in One Hundred Papercuts: Invalid Status in upstart package in Ubuntu: Invalid Bug description: When logging out (or shuting down), after confirming to log out (shut down), the system goes into text mode for a while (0.5-3/4 seconds) before showing LDM or splash screen. In the text mode there is a black screen with a few system messages. How long does this situation last varies a lot. Sometimes it is just approximately 0.5 second and only 2-3 lines of system messages (the last one is then usually '* Checking out battery state') but sometimes it takes 3-4 seconds befor actual LightDM screen or splash appears and then there is a lot of system messages on the black screen. Anyway, the situation happens every sigle time I log out or shut , and it's been so at least since 11.10 (the issue also present there). I realise this is not really a bug, however I've decided to report this since recently I've noticed two people new to Ubuntu, to whom I'd recommended the system, going panic ('The system is broken!') when they saw this black screen with system messages. This is a detail, but the detail that - IMHO - should be improved. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu2 [origin: Ubuntu] ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 1.95-0ubuntu1 Architecture: i386 CasperVersion: 1.312 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CrashDB: unity Date: Mon Apr 2 13:50:35 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328) MachineType: Dell Inc. Latitude D620 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=/ubninit file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/ubnkern SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0TD761 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/16/2008:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D620 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.2-0ubuntu4 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/971555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1084643] Re: Colour casting on black text using the default renderer pdftops (workaround: use gs)
Official support for Ubuntu 12.04.5 ended on April 28, 2017. Official support for Ubuntu 12.10 ended on May 16, 2014. Does this problem still occur on Ubuntu 21.04? ** Changed in: poppler (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1084643 Title: Colour casting on black text using the default renderer pdftops (workaround: use gs) Status in poppler package in Ubuntu: Incomplete Bug description: For some time now (I think the bug is not specific to Ubuntu 12.10 but also present in 12.04), I am having trouble when printing black text with an HP Color LaserJet CP1515n, that worked fine on previous Ubuntu releases and from other Operating Systems. The output is kind of ok, but black text does has a slight red cast, making it look fuzzy. The problem exists when printing from LibreOffice, Firefox and Evince. Trying different settings and drivers to debug the problem, I came to the conclusion that the problem is on the pdftops default renderer. On LibreOffice, I went to File - Printer Settings - Properties - Device - Printer Language Type and chose Postscript (Level from driver). For Firefox and Evince I just used this command from the command line: $ lpadmin -p "HP-Color-LaserJet-cp1515n" -o pdftops-renderer- default=gs (use "pdftops-renderer-default=pdftops" to restore the default) Using this settings (gs), the printing results are fine. $ dpkg -l poppler-utils hplip cups Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii cups 1.6.1-0ubunt amd64Common UNIX Printing System(tm) - ii hplip 3.12.6-3ubun amd64HP Linux Printing and Imaging Sys ii poppler-utils 0.20.4-0ubun amd64PDF utilities (based on Poppler) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1084643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1310564] Re: pdftops can't handle mixed portrait/landscape documents
This is now working correctly on Ubuntu 18.04.5 LTS with poppler-utils 0.62.0-2ubuntu2.12 ** Changed in: poppler (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1310564 Title: pdftops can't handle mixed portrait/landscape documents Status in poppler package in Ubuntu: Fix Released Bug description: I am trying to convert (parts of) a PDF document containing mixed portrait and landscape pages to ps with fixed page sizes (so I can feed it to psbook ... | psnup -2 ...), but pdftops can't handle that: 1. wget http://www.st.com/web/en/resource/technical/document/datasheet/DM00102166.pdf 2. evince DM00102166.pdf Note that pages 44ff contain tables in landscape mode 3. pdftops -paper A4 DM00102166.pdf 4. evince DM00102166.ps Note that pages 44ff are now empty, with: (evince:6788): Gdk-CRITICAL **: gdk_pixbuf_get_from_surface: assertion 'width > 0 && height > 0' failed This may or may not be related to https://bugs.freedesktop.org/show_bug.cgi?id=72312 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: poppler-utils 0.24.5-2ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 21 12:56:08 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) SourcePackage: poppler UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1310564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1310564] Re: pdftops can't handle mixed portrait/landscape documents
(Official support for Ubuntu 14.04 ended in April 2019). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1310564 Title: pdftops can't handle mixed portrait/landscape documents Status in poppler package in Ubuntu: Fix Released Bug description: I am trying to convert (parts of) a PDF document containing mixed portrait and landscape pages to ps with fixed page sizes (so I can feed it to psbook ... | psnup -2 ...), but pdftops can't handle that: 1. wget http://www.st.com/web/en/resource/technical/document/datasheet/DM00102166.pdf 2. evince DM00102166.pdf Note that pages 44ff contain tables in landscape mode 3. pdftops -paper A4 DM00102166.pdf 4. evince DM00102166.ps Note that pages 44ff are now empty, with: (evince:6788): Gdk-CRITICAL **: gdk_pixbuf_get_from_surface: assertion 'width > 0 && height > 0' failed This may or may not be related to https://bugs.freedesktop.org/show_bug.cgi?id=72312 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: poppler-utils 0.24.5-2ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 21 12:56:08 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) SourcePackage: poppler UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1310564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578430] Re: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. ** Changed in: hundredpapercuts Status: Confirmed => Incomplete ** Changed in: qt4-x11 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1578430 Title: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 Status in One Hundred Papercuts: Incomplete Status in qt4-x11 package in Ubuntu: Incomplete Bug description: Happened while installing skype ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqtcore4 4:4.8.7+dfsg-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Wed May 4 19:07:03 2016 DuplicateSignature: Unpacking libqtcore4:i386 (4:4.8.7+dfsg-5ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/libqtcore4_4%3a4.8.7+dfsg-5ubuntu2_i386.deb (--unpack): trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 InstallationDate: Installed on 2016-04-10 (24 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: qt4-x11 Title: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:i386 UpgradeStatus: Upgraded to xenial on 2016-04-22 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1578430/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622378] Re: package libqtcore4 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of packag
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. ** Changed in: hundredpapercuts Status: Confirmed => Incomplete ** Changed in: qt4-x11 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1622378 Title: package libqtcore4 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:amd64 Status in One Hundred Papercuts: Incomplete Status in qt4-x11 package in Ubuntu: Incomplete Bug description: THis came up after I tried to install UNetbootin. I don't really know what's going on ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqtcore4 (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Sep 11 13:42:23 2016 DuplicateSignature: package:libqtcore4:(not installed) Unpacking libqtcore4:amd64 (4:4.8.7+dfsg-5ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/libqtcore4_4%3a4.8.7+dfsg-5ubuntu2_amd64.deb (--unpack): trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:amd64 ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:amd64 InstallationDate: Installed on 2014-08-31 (742 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: qt4-x11 Title: package libqtcore4 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of package libqtcore4:amd64 UpgradeStatus: Upgraded to xenial on 2016-08-06 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1622378/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573015] Re: xenial cloudimage with missing hostname on hosts
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. ** Changed in: hundredpapercuts Status: Confirmed => Incomplete ** Changed in: hostname (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1573015 Title: xenial cloudimage with missing hostname on hosts Status in One Hundred Papercuts: Incomplete Status in hostname package in Ubuntu: Incomplete Bug description: Install Vagrant / Virtualbox On Terminal run: $> vagrant init Edit the Vagrantfile to change the box name from "base" to "ubuntu/xenial64" Then on the terminal again do: $> vagrant up After installing do: $> vagrant ssh $> sudo su You will get a message stating: "sudo: unable to resolve host ubuntu- xenial" The reason for this message is because the entry on /etc/hostname (which have "ubuntu-xenial") doesn't exist on /etc/hosts To Fix: Edit the /etc/hosts: $> sudo vim /etc/hosts (for instance) And on the entry: 127.0.0.1 localhost Change to: 127.0.0.1 localhost ubuntu-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1573015/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
This bug was fixed in the package netplan.io - 0.103-0ubuntu3 --- netplan.io (0.103-0ubuntu3) impish; urgency=medium [ Helmut Grohne ] * Annotate Build-Depends with . (Closes: #961466) [ Lukas Märdian ] * New upstream release: 0.103 - Add YAML generator and Keyfile parser for NetworkManager YAML backend - Add activation-mode parameter, needs systemd v248+ (LP: #1664844) - Make use of systemd-networkd's reload/reconfigure commands - Deprecate gateway4 & gateway6 in favor of defaults routes (LP: #1756590) - Add io.netplan.Netplan.Generate() DBus method - Changed the way of how unmanaged-devices are handled by NetworkManager - Improve integration test suite (LP: #1922126) Bug fixes: - Fix ABI regression introduced in 0.102 (LP: #1922898) - Fix netplan set if used across partitions (LP: #1930675) - Fix handling of multiple gateway4/gateway6 fields (LP: #1901836) - Fix parsing of ovs values with colons (LP: #1913906) - Fix failure with set-name and bridges * Bump systemd dependency to >= v248 for the activation-mode feature * Update debian/watch file * Drop patches applied upstream - Add 0001-parse-nm-fix-32bit-format-string.patch - Add d/p/0002-Revert-cli-apply-reload-reconfigure-networkd-instead.patch This reverts the systemd-networkd reload/reconfigure usage, due to a bug in systemd (< v249) https://github.com/systemd/systemd/issues/18108 * Update Standards-Version to 4.5.1, no changes required * Add Rules-Requires-Root: no to debian/control * Add debian/upstream/metadata file -- Lukas Märdian Fri, 06 Aug 2021 07:56:49 +0200 ** Changed in: netplan.io (Ubuntu) Status: In Progress => Fix Released ** Bug watch added: github.com/systemd/systemd/issues #18108 https://github.com/systemd/systemd/issues/18108 -- 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: Fix Released Status in systemd package in Ubuntu: Fix Released 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 Status in netplan.io source package in Bionic: Won't Fix Status in systemd source package in Bionic: Won't Fix Status in netplan.io source package in Focal: New Status in systemd source package in Focal: Fix Released Status in netplan.io source package in Groovy: New Status in systemd source package in Groovy: Fix Released Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: Fix Released Bug description: [Impact] Since very long, we had a feature request in netplan to determine the activation mode of a given network interface. We got requests to enable marking some interfaces as 'manual', meaning that networkd (or any other backend) would not control its state in any way, requiring the administrator to bring the interface up or down manually. The other request was to mark a interface as 'off', that is: forcing the network interface to always be down until the configuration option isn't changed. This was mainly requested for the networkd backend and requires the new feature of specifying ActivationPolicy= for interfaces, alongside the required netplan changes. This feature is present in systemd 248 - for netplan supported stable series we have decided to cherry-pick and backport this feature on top of current systemd. The networkd feature basically adds the following 5 ActivationPolicy modes: always-down, down, manual, up, always-up. For netplan purposes we only use 'always-down' and 'manual'. The netplan feature, hopefully landing as part of 0.103, is called 'activation-mode' and supports two values: 'manual' and 'off'. [Test Case] For the systemd part: * Bring up a VM test environment with either a dummy interface or an interface that can be safely manipulated. * Upgrade systemd to the -proposed version * For the target interface, create/modify the networkd configuration to include the ActivationPolicy= setting in [Link], for instance: [Match] Name=dummy0 [Network] Address=192.168.10.30/24 Gateway=192.168.10.1 [Link] ActivationPolicy=manual * Try all 5 combinations of ActivationPolicy values: always-down, down, manual, up, always-up - doing `sudo networkctl reload` everytime and checking if the interface behaves as expected. [Where problems could occur] The patchset modifies quite a lot of code in the networkd link handling code paths, so regressions
[Touch-packages] [Bug 411964] Re: Dialog error is somewhat obtrusive in ubuntusounds
Closing as fixed, the "Yaru" theme sounds in recent releases of Ubuntu are definitely less obtrusive than in the much older releases of Ubuntu. ** Changed in: hundredpapercuts Status: Triaged => Fix Released ** Changed in: ubuntu-sounds (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-sounds in Ubuntu. https://bugs.launchpad.net/bugs/411964 Title: Dialog error is somewhat obtrusive in ubuntusounds Status in One Hundred Papercuts: Fix Released Status in ubuntu-sounds package in Ubuntu: Fix Released Bug description: The dialog error is somewhat obstrusive and loud when in deep concetration on a project. Could this be changed to be more subtle less obstrusive sound like the sound incorporated in the freedesktop sound theme? To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/411964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779767] Re: Default cron PATH does not include /snap/bin
crontab(5) manpage being updated in LP: #1938924 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in anacron package in Ubuntu: Fix Released Status in cron package in Ubuntu: Fix Released Status in anacron source package in Bionic: Won't Fix Status in cron source package in Bionic: Won't Fix Status in anacron source package in Focal: Won't Fix Status in cron source package in Focal: Won't Fix Status in anacron source package in Groovy: Won't Fix Status in cron source package in Groovy: Won't Fix Status in anacron source package in Hirsute: Fix Released Status in cron source package in Hirsute: Fix Released Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916341] Re: poppler-utils/pdfimages list function names the wrong color in output table
This bug report is missing system information and log files that will assist in diagnosing the cause of the problem. Please run apport- collect 1916341 to add that information to this bug report. Please also attach a file with which this problem can be reproduced. ** Changed in: poppler (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1916341 Title: poppler-utils/pdfimages list function names the wrong color in output table Status in poppler package in Ubuntu: Incomplete Bug description: When running: $ pdfimages -list grayscale-document.pdf the output is: ``` page num type width height color comp bpc enc interp object ID x-ppi y-ppi size ratio 1 0 image2556 3288 rgb 3 8 jpeg no 7 0 301 300 200K 0.8% 2 1 image2556 3288 rgb 3 8 jpeg no12 0 301 300 275K 1.5% 3 2 image2556 3288 rgb 3 8 jpeg no17 0 301 300 395K 0.8% 4 3 image2556 3288 rgb 3 8 jpeg no22 0 301 300 583K 2.8% 5 4 image2556 3288 rgb 3 8 jpeg no27 0 301 300 317K 1.3% ... ``` "rgb" is incorrect, which is evident after running: 'pdfimages -all -f 1 -l 1 grayscale-document.pdf foo && identify -format "%[type]" foo-000.jpg', which correctly outputs "Grayscale". Strangely, when "pdfimages -list" is fed a bilevel document, it states that every page has color "gray". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1916341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 508220] Re: Lucid alpha 2: first 21 characters of Synaptic "Applying changes" status line are italic
This issue is for Lucid Lynx, which reached EOL in 2013 for desktop packages. I vote we close this issue as WONTFIX (I don't have permission to set WONTFIX status on this issue). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/508220 Title: Lucid alpha 2: first 21 characters of Synaptic "Applying changes" status line are italic Status in gtk+2.0 package in Ubuntu: New Status in synaptic package in Ubuntu: Fix Released Bug description: Lucid alpha 2: first 21 characters of Synaptic "Applying changes" status line (e.g. Preparing blahpackage0-dev) are italic, while the rest of the characters are not. This isn't a major issue, and is purely cosmetic. Screenshots: http://azabani.com/images/lucid-synaptic-italic-1 http://azabani.com/images/lucid-synaptic-italic-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/508220/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
I've tested 237-3ubuntu10.50+testpkg20210802b3 the ppa and it resolves the issue. -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in netplan: Confirmed Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Incomplete Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Status in keepalived source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] version: 2 Configure keepalived (again, a working config with IP addresses obfuscated) global_defs # Block id { notification_email { sysadm...@blah.com } notification_email_from keepali...@system3.hq.blah.com smtp_server 10.22.11.7 # IP smtp_connect_timeout 30 # integer, seconds router_id system3 # string identifying the machine, # (doesn't have to be hostname). vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18 vrrp_mcast_group6 ff02::12 # optional, default ff02::12 enable_traps # enable SNMP traps } vrrp_sync_group collection { group {
[Touch-packages] [Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange
** Also affects: openssh via https://github.com/openssh-gsskex/openssh-gsskex/issues/20 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1938144 Title: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Bug description: I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and server) with the option "GSSAPIKeyExchange=yes", and this causes the connection to fail. The server has GSSAPI (Kerberos authentication) enabled, but is is only used for non-root users (root uses SSH keys). Client command: ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex root@server -v -p -o GSSAPIKeyExchange=yes Client log: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020 debug1: Reading configuration data /home/user/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: Connecting to compute-test [130.75.80.46] port . debug1: Connection established. debug1: identity file /home/rother/.ssh/id_rsa type 0 debug1: identity file /home/rother/.ssh/id_rsa-cert type -1 debug1: identity file /home/rother/.ssh/id_dsa type -1 debug1: identity file /home/rother/.ssh/id_dsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa type -1 debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519 type -1 debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_xmss type -1 debug1: identity file /home/rother/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400 debug1: Authenticating to server: as 'root' debug1: Offering GSSAPI proposal: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q== debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g== debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: Doing group exchange debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Received GSSAPI_COMPLETE debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Rekey has happened - updating saved versions debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent debug1: Will attempt key: /home/user/.ssh/id_dsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk debug1: Will attempt key: /home/user/.ssh/id_ed25519 debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk debug1: Will attempt key: /home/user/.ssh/id_xmss debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: gssapi-with-mic debug1: Delegating credentials debug1: Delegating credentials debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: gssapi-keyex Connection closed by 1.2.3.4 port Server log: debug1: sshd version OpenSSH_8.2, OpenSSL 1.1.1f 31 Mar 2020 debug1: private host key #0: ssh-rsa SHA256:REDACTED debug1: private host key #1: ecdsa-sha2-nistp256 SHA256:REDACTED debug1: private host key #2:
[Touch-packages] [Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange
The issue is reproducible in the latest published versions of openssh carrying the patches in https://github.com/openssh-gsskex/openssh-gsskex for Ubuntu (impish), Debian (unstable), and Fedora (rawhide). I filed a bug report in https://github.com/openssh-gsskex/openssh- gsskex/issues/20 to make sure the gsskex patch upstream is aware of this issue. ** Bug watch added: github.com/openssh-gsskex/openssh-gsskex/issues #20 https://github.com/openssh-gsskex/openssh-gsskex/issues/20 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1938144 Title: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Bug description: I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and server) with the option "GSSAPIKeyExchange=yes", and this causes the connection to fail. The server has GSSAPI (Kerberos authentication) enabled, but is is only used for non-root users (root uses SSH keys). Client command: ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex root@server -v -p -o GSSAPIKeyExchange=yes Client log: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020 debug1: Reading configuration data /home/user/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: Connecting to compute-test [130.75.80.46] port . debug1: Connection established. debug1: identity file /home/rother/.ssh/id_rsa type 0 debug1: identity file /home/rother/.ssh/id_rsa-cert type -1 debug1: identity file /home/rother/.ssh/id_dsa type -1 debug1: identity file /home/rother/.ssh/id_dsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa type -1 debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519 type -1 debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_xmss type -1 debug1: identity file /home/rother/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400 debug1: Authenticating to server: as 'root' debug1: Offering GSSAPI proposal: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q== debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g== debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: Doing group exchange debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Received GSSAPI_COMPLETE debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Rekey has happened - updating saved versions debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent debug1: Will attempt key: /home/user/.ssh/id_dsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk debug1: Will attempt key: /home/user/.ssh/id_ed25519 debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk debug1: Will attempt key: /home/user/.ssh/id_xmss debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: gssapi-with-mic debug1: Delegating credentials debug1: Delegating credentials debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Authentications that can continue:
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
> The "default bionic install" uses only netplan yaml and /etc/systemd/network/ is empty. yes, but netplan creates .network config files named in a deterministic way so you know what the name of the networkd file it creates will be. I don't think netplan currently has a mechanism to include keep- configuration options in the networkd config it creates. > Using '/etc/systemd/network/10-netplan-ens160.network.d/override.conf' with KeepConfiguration works perfectly the same. exactly, which is why you should use the drop-in instead of manually duplicating and editing the entire netplan-created .network config file, as you complained about when you said: > Now I need to have IP and gateway in two files since, no, you don't. Or, drop netplan and just directly configure systemd-networkd. -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in netplan: Confirmed Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Incomplete Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Status in keepalived source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] version: 2 Configure keepalived (again, a
[Touch-packages] [Bug 1938005] Re: ufw ignores rules
Thank you for the bug report. You mentioned that the problem happens after running `iptables -F`. This command removes all the rules from the firewall (see man iptables) so it would be expected that the firewall would not work correctly after running this. I'm going to mark this as Invalid, but if you have more information, feel free to add it. ** Changed in: ufw (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1938005 Title: ufw ignores rules Status in ufw package in Ubuntu: Invalid Bug description: With my setting I shouldn't be able to surf web, but I can do it (without proxy/vpn) This problem happens after `iptables -F` and only way to solve it, is to reboot PC. I tried `ufw reload` , too ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ufw 0.36-7.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Mon Jul 26 11:53:17 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-06-17 (38 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2021-07-25T22:22:29.221649 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1938005/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Hi Sergio, Sorry I don't understand why the bug's importance has decreased to "medium". Du to client side behavior, issue is totally unpredictable, and slapd no longer respond to requests. Morever, the hot fix is not suited for production machines, and can introduce regression. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall Status in openldap package in Ubuntu: Confirmed Status in openldap source package in Bionic: Triaged Bug description: On a production server, sometimes slapd become unbresponsive, some threads loops in sched_yield syscall and consumme all CPU. To recover, slapd needs to restart. No related information is reported in log file. All same issues in OpenLDAP upstream project are old and fixed. So maybe this issue affects only Ubuntu package. It occurs randomly, so I have no steps to reproduce. OS : Bionic Openldap version: libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10 libldap-common 2.4.45+dfsg-1ubuntu1.10 slapd 2.4.45+dfsg-1ubuntu1.10 Modules loaded: olcModuleLoad: {0}back_bdb olcModuleLoad: {1}syncprov olcModuleLoad: {2}back_monitor olcModuleLoad: {3}memberof.la olcModuleLoad: {4}refint.la olcModuleLoad: {5}rwm olcModuleload: {6}back_ldap Backend is BDB. slapd run in (single) master - (multi) slave mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU
** Description changed: - [Steps to reproduce] + [Impact] + Image is distorted with PRIME, caused by mismatch in stride alignment between intel and amdgpu/nvidia after intel bumped the alignment to 256 bytes. + + [Fix] + Upstream fixed it in 21.2-series, and backport to 21.0.x needs four commits in total. + + [Test case] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. - 3. Run below command to launch glxgear + 3. Run below command to launch glxgears Cmd> DRI_PRIME=1 glxgears -info - [Expected result] - The image is not distrorted while running the glxgears + * Expected result + The image is not distorted while running the glxgears - [Actual result] - The image is distrorted while running the glxgears + * Actual result + The image is distorted while running the glxgears + + [Where things might go wrong] + This is a regression caused by the intel driver, so the backports merely fix what got broken. Regressions would only manifest on hybrid graphics platforms. + --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1937988 Title: The image is distorted while use iGPU rendering and output via AMD GPU Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Status in mesa source package in Focal: New Status in mesa source package in Hirsute: New Bug description: [Impact] Image is distorted with PRIME, caused by mismatch in stride alignment between intel and amdgpu/nvidia after intel bumped the alignment to 256 bytes. [Fix] Upstream fixed it in 21.2-series, and backport to 21.0.x needs four commits in total. [Test case] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. 3. Run below command to launch glxgears Cmd> DRI_PRIME=1 glxgears -info * Expected result The image is not distorted while running the glxgears * Actual result The image is distorted while running the glxgears [Where things might go wrong] This is a regression caused by the intel driver, so the backports merely fix what got broken. Regressions would only manifest on hybrid graphics platforms. --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
The "default bionic install" uses only netplan yaml and /etc/systemd/network/ is empty. If I switch to systemd.network style, I have to create config files from scratch anyway and then this KeepConfiguration helps. (Of course I do not need to keep the netplan yaml after enabling systemd-networkd, my remark for having the IP configuration in two files was wrong) Using '/etc/systemd/network/10-netplan-ens160.network.d/override.conf' with KeepConfiguration works perfectly the same. -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in netplan: Confirmed Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Incomplete Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Status in keepalived source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] version: 2 Configure keepalived (again, a working config with IP addresses obfuscated) global_defs # Block id { notification_email { sysadm...@blah.com } notification_email_from keepali...@system3.hq.blah.com smtp_server 10.22.11.7 # IP smtp_connect_timeout 30 # integer, seconds