[Touch-packages] [Bug 2017840] Re: ifupdown resolved script has typo
My apologies, I neglected to specify these details: OS: Ubuntu 22.04.2 LTS Package: ifupdown Version: 0.8.36+nmu1ubuntu3 It's the latest version of ifupdown. ** Package changed: systemd (Ubuntu) => ifupdown (Ubuntu) -- 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/2017840 Title: ifupdown resolved script has typo Status in ifupdown package in Ubuntu: New Bug description: This error happens when you try to run ifup or ifdown: ``` # ifdown enp3s0 /etc/network/if-down.d/resolved: 12: mystatedir: not found # ifup enp3s0 /etc/network/if-up.d/resolved: 12: mystatedir: not found ``` Here's the first 12 lines of those scripts: ``` # head -n 12 /etc/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` used to appear before `mystatedir` on line 12, but that was when it was a function. When it was converted back from being a function, the 'local' keyword was removed, but the variables remained. Either make it into a function again, or delete line 12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2017840/+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 2018255] Re: Failed to upgrade to release 23
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- 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/2018255 Title: Failed to upgrade to release 23 Status in initramfs-tools package in Ubuntu: New Bug description: Failed to upgrade to Kubuntu 23. I've now rebooted so I can't tell which exact package failed; here's the last capture I have: dependency problems - leaving unconfigured Errors were encountered while processing: linux-firmware linux-image-generic linux-generic ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sddm 2282 F wireplumber /dev/snd/controlC1: sddm 2282 F wireplumber /dev/snd/seq:sddm 2281 F pipewire CasperMD5CheckResult: unknown Date: Tue May 2 07:20:56 2023 Dependencies: firmware-sof-signed 2.2.4-1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=67788873-0ab9-4395-880f-57ebe65682ce InstallationDate: Installed on 2018-01-23 (1924 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-41-generic root=/dev/mapper/vg500G4-lvKubuntuRoot ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: initramfs-tools Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-01 (0 days ago) dmi.bios.date: 10/30/2008 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0804 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0804:bd10/30/2008:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2018255/+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 2007728] Re: resolved does not send .local requests to upstream DNS by default
[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/2007728 Title: resolved does not send .local requests to upstream DNS by default Status in systemd package in Ubuntu: Expired Bug description: On a network with multiple DNS servers provided by DHCP, only the first two of which cover local names, resolved returns universally known names but fails to return the special names even when the "Current DNS Server" shown by `resolvectl status` returns the special names. Suppose that 172.16.9.5 and 172.16.10.5 are the two internal DNS servers with the local names. Windows servers with Active Directory enabled in this case. The DHCP server (a Cisco 4451 in this case) provides DNS servers 172.16.9.5, 172.16.10.5, 192.168.0.1, and 8.8.8.8. `resolvectl status` shows all of these as "DNS Servers" and 172.16.9.5 as the "Current DNS Server". `host localdomain.local` returns SRVFAIL, and `host localdomain.local 127.0.0.53` returns SRVFAIL, but `host localdomain.local 172.16.9.5` returns the correct result. This all happens regardless of the "Current DNS Server". Sometimes the "Current DNS Server" switches to 8.8.8.8 for reasons that are not clear even when the other servers are working properly, which seems to violate the principle of RFC 2132 section 3.8 that servers are listed in order of preference. So, in short, it seems that the correct behavior is that (1) resolved returns results consistent with its "Current DNS Server" and (2) resolved picks as its "Current DNS Server" the first reachable server in the list. The current behavior is that (1) resolved returns results sometimes inconsistent with its "Current DNS Server" and (2) resolved sometimes picks as its "Current DNS Server" some server other than the first reachable server in the list. The first issue is consistently reproducible, and the second is readily reproducible in a short period of time. The problem appears on Ubuntu 22.04 and seems not to be present on Ubuntu 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2007728/+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 2008964] Re: resolved falls back to a non-preferred name server when the preferred name server appears to be working.
[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/2008964 Title: resolved falls back to a non-preferred name server when the preferred name server appears to be working. Status in systemd package in Ubuntu: Expired Bug description: This is split from bug #2007728. On a network with multiple DNS servers provided by DHCP, the "Current DNS Server" shown by `resolvectl status` is sometimes not the first server or even the second server, even when those servers appear to be working (and other hosts continue to use them). This appears to occur on Ubuntu 22.04 but not on Ubuntu 20.04, Ubuntu 18.04, or Windows 10. RFC 2132 section 3.8 provides that servers are listed in order of preference. It seems that the correct behavior is that resolved picks as its "Current DNS Server" the first reachable server in the list provided by the DHCP server. The observed behavior is that resolved sometimes picks as its "Current DNS Server" some server other than the first reachable server in the list. My hypothesis is that there is some name server availability check that is too stringent and that there is no mechanism to retry the preferred server after that check fails. I have not looked at the code or captured packets. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2008964/+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 2018268] [NEW] Buzzing sound external speakers
Public bug reported: So I've tested other speakers too and this isn't a problem with the speaker itself. It also works perfectly fine on Windows 10 and 11. External speaker creates buzzing sound when sound settings not open, the sound is random at times, can happen at start up or when opening new applications or even when doing nothing. I apologise if I've not filed this issue correctly it's my first time. I've selected the alsa-driver package (the ubuntu-bug apport gave it as an option) but I don't know if it's in it or where it is as I said I'm very new to this sorry. You can contact me at nicholas.iliev.2...@gmail.com if you would like any further information. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 2 05:10:05 2023 InstallationDate: Installed on 2022-11-16 (166 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-04-27 (4 days ago) dmi.bios.date: 02/14/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Alienware dmi.bios.version: 1.15.0 dmi.board.name: 0X5DF0 dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.modalias: dmi:bvnAlienware:bvr1.15.0:bd02/14/2023:br1.15:svnAlienware:pnAlienwarem15R7:pvr:rvnAlienware:rn0X5DF0:rvrA03:cvnAlienware:ct10:cvr:sku0B54: dmi.product.family: Alienware dmi.product.name: Alienware m15 R7 dmi.product.sku: 0B54 dmi.sys.vendor: Alienware mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-03-01T23:52:14.302132 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2018268 Title: Buzzing sound external speakers Status in alsa-driver package in Ubuntu: New Bug description: So I've tested other speakers too and this isn't a problem with the speaker itself. It also works perfectly fine on Windows 10 and 11. External speaker creates buzzing sound when sound settings not open, the sound is random at times, can happen at start up or when opening new applications or even when doing nothing. I apologise if I've not filed this issue correctly it's my first time. I've selected the alsa-driver package (the ubuntu-bug apport gave it as an option) but I don't know if it's in it or where it is as I said I'm very new to this sorry. You can contact me at nicholas.iliev.2...@gmail.com if you would like any further information. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 2 05:10:05 2023 InstallationDate: Installed on 2022-11-16 (166 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-04-27 (4 days ago) dmi.bios.date: 02/14/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Alienware dmi.bios.version: 1.15.0 dmi.board.name: 0X5DF0 dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.modalias: dmi:bvnAlienware:bvr1.15.0:bd02/14/2023:br1.15:svnAlienware:pnAlienwarem15R7:pvr:rvnAlienware:rn0X5DF0:rvrA03:cvnAlienware:ct10:cvr:sku0B54: dmi.product.family: Alienware dmi.product.name: Alienware m15 R7 dmi.product.sku: 0B54 dmi.sys.vendor: Alienware mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-03-01T23:52:14.302132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2018268/+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 2017948] Re: Launchpad recipe builds for Mantic append Lunar version string
** Changed in: launchpad Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2017948 Title: Launchpad recipe builds for Mantic append Lunar version string Status in Launchpad itself: Fix Released Status in base-files package in Ubuntu: Fix Released Bug description: I'm seeing recipe builds being produced by the buildd for Mantic getting published with the '~ubuntu23.04.1' suffix which is the same one that's used for Lunar builds. Admittedly, I can't recall if it this was always the behavior for prerelease Ubuntu versions, but I don't think so, since this stood out as amiss when I had no other reason to scrutinize the version strings on a PPA page. Can someone possessing deeper familiarity with the recipe build process look into this? To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2017948/+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 2017840] Re: ifupdown resolved script has typo
Whoops, found another bug: ``` # ifup enp2s0 /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-enp2s0: DNS=1.1.1.1: not found /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-enp2s0: DOMAINS=example.org: not found Failed to parse DNS server address: DNS Failed to set DNS configuration: Invalid argument # cat /run/network/ifupdown-inet-enp2s0 "DNS"="1.1.1.1" "DOMAINS"="example.org" ``` And that comes from lines 47-51 of /etc/network/if-up.d/resolved: ``` if [ -n "$NEW_DNS" ]; then cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface" "$DNS"="$NEW_DNS" EOF if [ -n "$NEW_DOMAINS" ]; then cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface" "$DOMAINS"="$NEW_DOMAINS" EOF ``` Basically, the double-quotes around "$DNS" and "$DOMAINS" shouldn't be there, because it's a here-doc. But this reveals another bug: the variable $DOMAINS is used to hold either "DOMAINS" or "DOMAINS6" in lines 41 or 44, but the actual search domains in line 95. Has this code ever worked? -- 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/2017840 Title: ifupdown resolved script has typo Status in systemd package in Ubuntu: New Bug description: This error happens when you try to run ifup or ifdown: ``` # ifdown enp3s0 /etc/network/if-down.d/resolved: 12: mystatedir: not found # ifup enp3s0 /etc/network/if-up.d/resolved: 12: mystatedir: not found ``` Here's the first 12 lines of those scripts: ``` # head -n 12 /etc/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` used to appear before `mystatedir` on line 12, but that was when it was a function. When it was converted back from being a function, the 'local' keyword was removed, but the variables remained. Either make it into a function again, or delete line 12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017840/+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 2017840] Re: ifupdown resolved script has typo
After fixing those lines, there's yet another bug: ``` search example.org DOMAINS ``` Somehow it's deciding that the DNS search domains for static interfaces is "DOMAINS". Sample /etc/network/interface file: ``` auto enp3s0 iface enp3s0 inet static address 172.16.198.5 netmask 255.255.255.0 ``` and it creates this file: ``` # cat /run/systemd/resolve/netif/3 # This is private data. Do not parse. LLMNR=yes MDNS=no SERVERS=DNS DOMAINS=DOMAINS ``` Oh, and when you run `ifup enp3s0` by hand, you get this error: ``` # ifup enp3s0 ifup: interface enp3s0 already configured # ifdown enp3s0 # ifup enp3s0 mkdir: missing operand Try 'mkdir --help' for more information. ``` It looks like this error is from line 26 of /etc/network/if-up.d/resolved: ``` if [ ! "$ifindex" ]; then return fi # mystatedir=/run/network mkdir -p $mystatedir statedir=/run/systemd/resolve/netif mkdir -p $statedir chown systemd-resolve:systemd-resolve $statedir ``` Not sure why mystatedir is commented out, but it looks like that's what's wrong this time. -- 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/2017840 Title: ifupdown resolved script has typo Status in systemd package in Ubuntu: New Bug description: This error happens when you try to run ifup or ifdown: ``` # ifdown enp3s0 /etc/network/if-down.d/resolved: 12: mystatedir: not found # ifup enp3s0 /etc/network/if-up.d/resolved: 12: mystatedir: not found ``` Here's the first 12 lines of those scripts: ``` # head -n 12 /etc/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` used to appear before `mystatedir` on line 12, but that was when it was a function. When it was converted back from being a function, the 'local' keyword was removed, but the variables remained. Either make it into a function again, or delete line 12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017840/+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 2017840] Re: ifupdown resolved script has typo
There's another similar typo in the /etc/network/if-up.d/resolved script, on line 71: ``` if ! cmp --silent "$oldstate" "$newstate" 2>/dev/null; then DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE # v4 first ``` Comment it out, as it's not valid code. -- 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/2017840 Title: ifupdown resolved script has typo Status in systemd package in Ubuntu: New Bug description: This error happens when you try to run ifup or ifdown: ``` # ifdown enp3s0 /etc/network/if-down.d/resolved: 12: mystatedir: not found # ifup enp3s0 /etc/network/if-up.d/resolved: 12: mystatedir: not found ``` Here's the first 12 lines of those scripts: ``` # head -n 12 /etc/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` used to appear before `mystatedir` on line 12, but that was when it was a function. When it was converted back from being a function, the 'local' keyword was removed, but the variables remained. Either make it into a function again, or delete line 12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017840/+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 2018262] Re: nm-connection-editor exits with coredump when importing ovpn file
I was steered here by google and I guess this is the wrong place. I did report this, if you care to follow it, here.. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1286 Otherwise feel free to delete this report. ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1286 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1286 -- 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/2018262 Title: nm-connection-editor exits with coredump when importing ovpn file Status in network-manager package in Ubuntu: New Bug description: Software versions: Networkmanager: 1.42.6-1 nm-connection-editor: 1.32.0-1 networkmanager-openvpn: 1.10.2-1 openvpn: 2.6.2-1 Arch Linux kernel: 6.2.13-zen-1-zen While trying to import an ovpn file downloaded from NordVPN, nm- connection-editor exits with a coredump. Downgrading to nm-connection-editor ver 1.30.0-1 allowed me to import the configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2018262/+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 2018262] [NEW] nm-connection-editor exits with coredump when importing ovpn file
Public bug reported: Software versions: Networkmanager: 1.42.6-1 nm-connection-editor: 1.32.0-1 networkmanager-openvpn: 1.10.2-1 openvpn: 2.6.2-1 Arch Linux kernel: 6.2.13-zen-1-zen While trying to import an ovpn file downloaded from NordVPN, nm- connection-editor exits with a coredump. Downgrading to nm-connection-editor ver 1.30.0-1 allowed me to import the configuration. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "debug trace with symbols (debuginfod)" https://bugs.launchpad.net/bugs/2018262/+attachment/5670170/+files/gdb.txt -- 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/2018262 Title: nm-connection-editor exits with coredump when importing ovpn file Status in network-manager package in Ubuntu: New Bug description: Software versions: Networkmanager: 1.42.6-1 nm-connection-editor: 1.32.0-1 networkmanager-openvpn: 1.10.2-1 openvpn: 2.6.2-1 Arch Linux kernel: 6.2.13-zen-1-zen While trying to import an ovpn file downloaded from NordVPN, nm- connection-editor exits with a coredump. Downgrading to nm-connection-editor ver 1.30.0-1 allowed me to import the configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2018262/+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 2016597] Re: Tests create ~/.ssh/authorized_keys group writable due to wrong umask
** Changed in: tinyssh (Ubuntu) Status: In Progress => Fix Committed -- 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/2016597 Title: Tests create ~/.ssh/authorized_keys group writable due to wrong umask Status in systemd package in Ubuntu: Invalid Status in tinyssh package in Ubuntu: Fix Committed Bug description: Traditionally, the default umask as been 0022, which is still the case on Debian and for the root user on Ubuntu. But for non-root users PAM sets a user's session umask to 0002 by default (/etc/pam.d/common-session*), as defined in "/etc/login.defs" via USERGROUPS_ENAB. tinyssh's sshd will reject connections if ~/.ssh/authorized_key is writable by group/other. The test case (re-)creates ~/.ssh/authorized_keys by echoing some strings/keys into it, which creates a new file on the default umask, breaking the test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2016597/+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 2018261] [NEW] package udev 249.11-0ubuntu3.9 failed to install/upgrade: le sous-processus paquet udev script post-installation installé a renvoyé un état de sortie d'erreur 1
Public bug reported: upgrade error from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.gnome-characters.rules 95-oem-hotkey-osd.rules 70-snap.ubuntu-frame.rules 70-snap.firefox.rules 70-snap.snap-store.rules 70-snap.snapd.rules 70-snap.cups.rules 70-snap.gnome-calculator.rules 10-ubports.rules 70-snap.multipass.rules 70-snap.gnome-system-monitor.rules 70-snap.xibo-player.rules 70-snap.chromium.rules 70-snap.gnome-logs.rules Date: Mon May 1 21:25:19 2023 ErrorMessage: le sous-processus paquet udev script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2021-01-22 (829 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20180507-04:30 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 413c:2106 Dell Computer Corp. QuietKey Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation NUC7i5DNKE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-148-generic root=UUID=527a0826-742d-45c2-bd7b-cb43d2f0fa5c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.9 SourcePackage: systemd Title: package udev 249.11-0ubuntu3.9 failed to install/upgrade: le sous-processus paquet udev script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to jammy on 2023-05-01 (0 days ago) dmi.bios.date: 03/04/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: DNKBLi5v.86A.0062.2019.0304.1757 dmi.board.name: NUC7i5DNB dmi.board.vendor: Intel Corporation dmi.board.version: J57626-506 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrDNKBLi5v.86A.0062.2019.0304.1757:bd03/04/2019:svnIntelCorporation:pnNUC7i5DNKE:pvrJ72865-506:rvnIntelCorporation:rnNUC7i5DNB:rvrJ57626-506:cvnIntelCorporation:ct35:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i5DNKE dmi.product.version: J72865-506 dmi.sys.vendor: Intel Corporation ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2018261 Title: package udev 249.11-0ubuntu3.9 failed to install/upgrade: le sous- processus paquet udev script post-installation installé a renvoyé un état de sortie d'erreur 1 Status in systemd package in Ubuntu: New Bug description: upgrade error from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.gnome-characters.rules 95-oem-hotkey-osd.rules 70-snap.ubuntu-frame.rules 70-snap.firefox.rules 70-snap.snap-store.rules 70-snap.snapd.rules 70-snap.cups.rules 70-snap.gnome-calculator.rules 10-ubports.rules 70-snap.multipass.rules 70-snap.gnome-system-monitor.rules 70-snap.xibo-player.rules 70-snap.chromium.rules 70-snap.gnome-logs.rules Date: Mon May 1 21:25:19 2023 ErrorMessage: le sous-processus paquet udev script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2021-01-22 (829 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20180507-04:30 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 413c:2106 Dell Computer Corp. QuietKey Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation NUC7i5DNKE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-148-generic root=UUID=527a0826-742d-45c2-bd7b-cb43d2f0fa5c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.9 SourcePackage: systemd Title: package udev 249.11-0ubuntu3.9 failed to
[Touch-packages] [Bug 2018255] Re: Failed to upgrade to release 23
** Tags removed: need-duplicate-check -- 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/2018255 Title: Failed to upgrade to release 23 Status in initramfs-tools package in Ubuntu: New Bug description: Failed to upgrade to Kubuntu 23. I've now rebooted so I can't tell which exact package failed; here's the last capture I have: dependency problems - leaving unconfigured Errors were encountered while processing: linux-firmware linux-image-generic linux-generic ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sddm 2282 F wireplumber /dev/snd/controlC1: sddm 2282 F wireplumber /dev/snd/seq:sddm 2281 F pipewire CasperMD5CheckResult: unknown Date: Tue May 2 07:20:56 2023 Dependencies: firmware-sof-signed 2.2.4-1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=67788873-0ab9-4395-880f-57ebe65682ce InstallationDate: Installed on 2018-01-23 (1924 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-41-generic root=/dev/mapper/vg500G4-lvKubuntuRoot ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: initramfs-tools Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-01 (0 days ago) dmi.bios.date: 10/30/2008 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0804 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0804:bd10/30/2008:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2018255/+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 2018255] [NEW] Failed to upgrade to release 23
Public bug reported: Failed to upgrade to Kubuntu 23. I've now rebooted so I can't tell which exact package failed; here's the last capture I have: dependency problems - leaving unconfigured Errors were encountered while processing: linux-firmware linux-image-generic linux-generic ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sddm 2282 F wireplumber /dev/snd/controlC1: sddm 2282 F wireplumber /dev/snd/seq:sddm 2281 F pipewire CasperMD5CheckResult: unknown Date: Tue May 2 07:20:56 2023 Dependencies: firmware-sof-signed 2.2.4-1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=67788873-0ab9-4395-880f-57ebe65682ce InstallationDate: Installed on 2018-01-23 (1924 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-41-generic root=/dev/mapper/vg500G4-lvKubuntuRoot ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: initramfs-tools Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-01 (0 days ago) dmi.bios.date: 10/30/2008 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0804 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0804:bd10/30/2008:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- 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/2018255 Title: Failed to upgrade to release 23 Status in initramfs-tools package in Ubuntu: New Bug description: Failed to upgrade to Kubuntu 23. I've now rebooted so I can't tell which exact package failed; here's the last capture I have: dependency problems - leaving unconfigured Errors were encountered while processing: linux-firmware linux-image-generic linux-generic ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sddm 2282 F wireplumber /dev/snd/controlC1: sddm 2282 F wireplumber /dev/snd/seq:sddm 2281 F pipewire CasperMD5CheckResult: unknown Date: Tue May 2 07:20:56 2023 Dependencies: firmware-sof-signed 2.2.4-1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=67788873-0ab9-4395-880f-57ebe65682ce InstallationDate: Installed on 2018-01-23 (1924 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-41-generic root=/dev/mapper/vg500G4-lvKubuntuRoot ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as
[Touch-packages] [Bug 2017948] Re: Launchpad recipe builds for Mantic append Lunar version string
This bug was fixed in the package base-files - 12.3ubuntu3 --- base-files (12.3ubuntu3) mantic; urgency=medium * /etc/issue{,.net}, /etc/{lsb,os}-release: Welcome to Mantic Minotaur! (LP: #2017948) -- Graham Inggs Fri, 28 Apr 2023 08:38:19 + ** Changed in: base-files (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2017948 Title: Launchpad recipe builds for Mantic append Lunar version string Status in Launchpad itself: In Progress Status in base-files package in Ubuntu: Fix Released Bug description: I'm seeing recipe builds being produced by the buildd for Mantic getting published with the '~ubuntu23.04.1' suffix which is the same one that's used for Lunar builds. Admittedly, I can't recall if it this was always the behavior for prerelease Ubuntu versions, but I don't think so, since this stood out as amiss when I had no other reason to scrutinize the version strings on a PPA page. Can someone possessing deeper familiarity with the recipe build process look into this? To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2017948/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
Now that I've had some time to look at the patch, I really don't see it solving anything. After seeing Steve's comment, I do agree, it simply puts up needless barriers to updating metapackages. Sorry, but from Ubuntu Studio and Edubuntu, this is a Nack. I hope other flavors follow suit and don't accept this patch. ** Changed in: ubuntustudio-meta (Ubuntu) Importance: Medium => Undecided ** Changed in: ubuntustudio-meta (Ubuntu) Status: New => Won't Fix ** Changed in: ubuntustudio-meta (Ubuntu) Assignee: Erich Eickmeyer (eeickmeyer) => (unassigned) ** Changed in: edubuntu-meta (Ubuntu) Importance: Medium => Undecided ** Changed in: edubuntu-meta (Ubuntu) Status: New => Won't Fix ** Changed in: edubuntu-meta (Ubuntu) Assignee: Erich Eickmeyer (eeickmeyer) => (unassigned) -- 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/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in edubuntu-meta package in Ubuntu: Won't Fix Status in kubuntu-meta package in Ubuntu: New Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-unity-meta package in Ubuntu: New Status in ubuntucinnamon-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in ubuntustudio-meta package in Ubuntu: Won't Fix Status in xubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
I do not see what this change was supposed to solve. I disagree with the *existing* version check in germinate, and do not want to see more of these - it imposes needless barriers for updating the metapackages. -- 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/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in edubuntu-meta package in Ubuntu: New Status in kubuntu-meta package in Ubuntu: New Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-unity-meta package in Ubuntu: New Status in ubuntucinnamon-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in ubuntustudio-meta package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
** Changed in: ubuntu-budgie-meta (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-budgie-meta (Ubuntu) Assignee: (unassigned) => fossfreedom (fossfreedom) -- 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/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in edubuntu-meta package in Ubuntu: New Status in kubuntu-meta package in Ubuntu: New Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-unity-meta package in Ubuntu: New Status in ubuntucinnamon-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in ubuntustudio-meta package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+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 2017984] Re: "Save as" window from browser is not in dark mode
Thanks for the bug report. Which browser are you using? ** Package changed: xorg (Ubuntu) => ubuntu ** Package changed: ubuntu => yaru-theme (Ubuntu) ** Changed in: yaru-theme (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/2017984 Title: "Save as" window from browser is not in dark mode Status in yaru-theme package in Ubuntu: Incomplete Bug description: After update to 23.04 I'm having the following issue. In dark mode of Yaru-dark theme, when downloading the file and choosing the "Save as" option - popup window for folder selection is not in dark mode. When using Xorg session problem is not reproduced. The same applies for upload logic. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 28 12:31:55 2023 DistUpgraded: 2023-04-25 21:06:12,927 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:508f] InstallationDate: Installed on 2022-08-26 (244 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20X4S1GH08 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-25 (2 days ago) dmi.bios.date: 11/22/2022 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: R1JET60W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20X4S1GH08 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrR1JET60W(1.60):bd11/22/2022:br1.60:efr1.48:svnLENOVO:pn20X4S1GH08:pvrThinkPadL15Gen2:rvnLENOVO:rn20X4S1GH08:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20X4_BU_Think_FM_ThinkPadL15Gen2: dmi.product.family: ThinkPad L15 Gen 2 dmi.product.name: 20X4S1GH08 dmi.product.sku: LENOVO_MT_20X4_BU_Think_FM_ThinkPad L15 Gen 2 dmi.product.version: ThinkPad L15 Gen 2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2017984/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
This bug was fixed in the package ubuntu-meta - 1.502 --- ubuntu-meta (1.502) mantic; urgency=medium * Fix update script to include germinate in 'dependency' check and refactor script LP: #2017786 -- Tim Andersson Fri, 28 Apr 2023 09:09:28 +0100 ** Changed in: ubuntu-meta (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in edubuntu-meta package in Ubuntu: New Status in kubuntu-meta package in Ubuntu: New Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-unity-meta package in Ubuntu: New Status in ubuntucinnamon-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in ubuntustudio-meta package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+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 2017366] Re: Sound Not Working
** No longer affects: pipewire (Ubuntu) ** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New -- 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/2017366 Title: Sound Not Working Status in linux-hwe-5.19 package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Windows 11 - Hyper-V Ubuntu 22.0.4 Tried various solutions! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-22 (2 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Package: pulseaudio PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2017366/+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 2018233] [NEW] Xorg crash / Wayland
Public bug reported: I'm not sure if it's Xorg crashing, i'm using wayland. Clean installation Ubuntu 22.10 and upgraded to 23.04. The bug can be re-produced. Symptom: Moving firefox with ongoing video for example Youtube. Moving the firefox window from screen 2 or 3 to screen1 then it crashes 100% of times. Screen 1 is in vertical view mode. Screen 2 and 3 landscape. ## unk@unk-ThinkPad-X1-Carbon-Gen-10:~$ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 1 15:17:51 2023 DistUpgraded: 2023-04-23 20:27:46,523 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2023-03-22 (39 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CB00AYMX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to lunar on 2023-04-23 (7 days ago) dmi.bios.date: 03/02/2023 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET72W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CB00AYMX dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrN3AET72W(1.37):bd03/02/2023:br1.37:efr1.18:svnLENOVO:pn21CB00AYMX:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CB00AYMX:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CB00AYMX dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash lunar 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/2018233 Title: Xorg crash / Wayland Status in xorg package in Ubuntu: New Bug description: I'm not sure if it's Xorg crashing, i'm using wayland. Clean installation Ubuntu 22.10 and upgraded to 23.04. The bug can be re-produced. Symptom: Moving firefox with ongoing video for example Youtube. Moving the firefox window from screen 2 or 3 to screen1 then it crashes 100% of times. Screen 1 is in vertical view mode. Screen 2 and 3 landscape. ## unk@unk-ThinkPad-X1-Carbon-Gen-10:~$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 1 15:17:51 2023 DistUpgraded: 2023-04-23 20:27:46,523 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2023-03-22 (39 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CB00AYMX
[Touch-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
This bug was fixed in the package indicator-messages - 13.10.1+18.10.20180918-0ubuntu5 --- indicator-messages (13.10.1+18.10.20180918-0ubuntu5) lunar; urgency=medium * debian/conrol, debian/*.install: drop the libmessaging-menu0, libmessaging-menu-dev and gir1.2-messagingmenu-1.0 binary packages. Those are built and provided by ayatana-indicator-messages and cannot realistically be published to the archive during builds right now. They have been removed from the archive already when copied-forward. * debian/rules: change --fail-missing to --list-missing so that we don't fail when we don't install all the built files. Remove unneeded removal of *.la files as we don't install the library bits anymore. * debian/rules: make sure dh_auto_install does what it's supposed to. -- Łukasz 'sil2100' Zemczak Wed, 19 Apr 2023 16:55:12 +0100 ** Changed in: indicator-messages (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Committed Status in ayatana-indicator-messages package in Ubuntu: Incomplete Status in indicator-messages package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+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 2017229] Re: Update evolution-data-server to 3.48.1
This bug was fixed in the package evolution-data-server - 3.48.1-0ubuntu1 --- evolution-data-server (3.48.1-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2017229) * debian/*.symbols: Add new symbols -- Jeremy Bicha Fri, 21 Apr 2023 12:41:37 +0200 ** Changed in: evolution-data-server (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 evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2017229 Title: Update evolution-data-server to 3.48.1 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Lunar: Fix Committed Bug description: Impact -- This is a new stable release in the stable 3.48 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.48.1/NEWS It is required to update the evolution app to 3.48.1 (LP: #2017231) Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME evolution-data-server is included in all the Ubuntu Desktop flavors except for Kubuntu, Lubuntu, and Xubuntu Other Info -- There will be new evolution-data-server bugfix releases monthly until September. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2017229/+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 2002789] Re: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1
** Changed in: sysvinit (Debian) Status: New => Fix Committed -- 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/2002789 Title: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1 Status in sysvinit package in Ubuntu: Fix Released Status in sysvinit package in Debian: Fix Committed Bug description: The following file used to be provided by the lsb-base package in Ubuntu and it now supposed to be provided by the sysvinit-utils package. * lsb/init-functions.d/50-ubuntu-logging The file is Ubuntu specific but is not included in Ubuntu using a delta from Debian. Instead, the debian source tree includes the file but conditional statements in debian/rules makes it absent from the binary packages in Debian. Sadly, when moving the file from src:lsb to src:sysvinit, the conditional statements are not consistent anymore, resulting in the file being absent from the Ubuntu binary package as well. Affected version: sysvinit-utils 3.05-7ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2002789/+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 2011458] Re: ssh fails to rebind when it is killed with -HUP
Thanks for the pointer, Steve. That seems to work; here are autopkgtest logs from amd64 (it passed on all other arches too): https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-enr0n-proposed-migration/lunar/arm64/o/openssh/20230501_094525_a9c97@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-enr0n-proposed-migration/kinetic/amd64/o/openssh/20230501_092612_e544b@/log.gz I also added some output as Andreas requested. -- 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/2011458 Title: ssh fails to rebind when it is killed with -HUP Status in openssh package in Ubuntu: In Progress Status in openssh source package in Kinetic: In Progress Bug description: [Impact] The sshd re-execution logic is generally broken with systemd socket activation, which means that (1) sshd fails when it is told to re-exec via SIGHUP (e.g. systemctl reload ssh), and (2) sshd fails when started in debug mode. [Test Case] (1) Test systemctl reload ssh: * On a machine with openssh-server installed, make a connection to localhost to activate ssh.service (the connection does not need to be complete, so you can just say "no" at the host key verification stage): $ ssh localhost [...] * Send SIGHUP to sshd by calling systemctl reload ssh: $ systemctl reload ssh * Check the service state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:43:27 UTC; 4s ago Duration: 2min 44.132s TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1112 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Process: 1152 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1153 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 1112 (code=exited, status=255/EXCEPTION) CPU: 79ms Apr 17 20:40:43 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Apr 17 20:41:06 lunar sshd[1113]: Connection closed by 127.0.0.1 port 54666 [preauth] Apr 17 20:43:27 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure Shell server... Apr 17 20:43:27 lunar sshd[1112]: Received SIGHUP; restarting. Apr 17 20:43:27 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell server. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on :: failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: fatal: Cannot bind any address. Apr 17 20:43:27 lunar systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Apr 17 20:43:27 lunar systemd[1]: ssh.service: Failed with result 'exit-code'. * On an affected machine, the service will fail as shown above. (2) Test debug mode: * On a machine with openssh-server installed, edit /etc/default/ssh to configure debug mode for sshd: $ cat /etc/default/ssh # Default settings for openssh-server. This file is sourced by /bin/sh from # /etc/init.d/ssh. # Options to pass to sshd SSHD_OPTS=-ddd * Attempt to make a connection to localhost: $ ssh localhost kex_exchange_identification: read: Connection reset by peer Connection reset by 127.0.0.1 port 22 * On an affected machine, the attempt will fail as shown above, and the service will be in a failed state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:46:34 UTC; 2min 27s ago Duration: 5ms TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1166 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1167 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Main PID: 1167 (code=exited, status=255/EXCEPTION) CPU: 40ms Apr 17 20:46:34 lunar sshd[1167]: Server listening on :: port 22. Apr 17 20:46:34 lunar sshd[1167]: debug3: fd 4 is not O_NONBLOCK Apr 17 20:46:34 lunar sshd[1167]: debug1: Server will not fork when running in debugging mode. Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: entering fd = 7 config len 3456 Apr 17 20:46:34 lunar sshd[1167]: debug3: ssh_msg_send: type 0 Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: done Apr 17 20:46:34 lunar sshd[1167]: debug1: rexec start in 4 out 4
[Touch-packages] [Bug 2011458] Re: ssh fails to rebind when it is killed with -HUP
** Patch added: "openssh_9.0p1-1ubuntu8.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2011458/+attachment/5670029/+files/openssh_9.0p1-1ubuntu8.1.debdiff -- 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/2011458 Title: ssh fails to rebind when it is killed with -HUP Status in openssh package in Ubuntu: In Progress Status in openssh source package in Kinetic: In Progress Bug description: [Impact] The sshd re-execution logic is generally broken with systemd socket activation, which means that (1) sshd fails when it is told to re-exec via SIGHUP (e.g. systemctl reload ssh), and (2) sshd fails when started in debug mode. [Test Case] (1) Test systemctl reload ssh: * On a machine with openssh-server installed, make a connection to localhost to activate ssh.service (the connection does not need to be complete, so you can just say "no" at the host key verification stage): $ ssh localhost [...] * Send SIGHUP to sshd by calling systemctl reload ssh: $ systemctl reload ssh * Check the service state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:43:27 UTC; 4s ago Duration: 2min 44.132s TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1112 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Process: 1152 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1153 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 1112 (code=exited, status=255/EXCEPTION) CPU: 79ms Apr 17 20:40:43 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Apr 17 20:41:06 lunar sshd[1113]: Connection closed by 127.0.0.1 port 54666 [preauth] Apr 17 20:43:27 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure Shell server... Apr 17 20:43:27 lunar sshd[1112]: Received SIGHUP; restarting. Apr 17 20:43:27 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell server. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on :: failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: fatal: Cannot bind any address. Apr 17 20:43:27 lunar systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Apr 17 20:43:27 lunar systemd[1]: ssh.service: Failed with result 'exit-code'. * On an affected machine, the service will fail as shown above. (2) Test debug mode: * On a machine with openssh-server installed, edit /etc/default/ssh to configure debug mode for sshd: $ cat /etc/default/ssh # Default settings for openssh-server. This file is sourced by /bin/sh from # /etc/init.d/ssh. # Options to pass to sshd SSHD_OPTS=-ddd * Attempt to make a connection to localhost: $ ssh localhost kex_exchange_identification: read: Connection reset by peer Connection reset by 127.0.0.1 port 22 * On an affected machine, the attempt will fail as shown above, and the service will be in a failed state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:46:34 UTC; 2min 27s ago Duration: 5ms TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1166 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1167 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Main PID: 1167 (code=exited, status=255/EXCEPTION) CPU: 40ms Apr 17 20:46:34 lunar sshd[1167]: Server listening on :: port 22. Apr 17 20:46:34 lunar sshd[1167]: debug3: fd 4 is not O_NONBLOCK Apr 17 20:46:34 lunar sshd[1167]: debug1: Server will not fork when running in debugging mode. Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: entering fd = 7 config len 3456 Apr 17 20:46:34 lunar sshd[1167]: debug3: ssh_msg_send: type 0 Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: done Apr 17 20:46:34 lunar sshd[1167]: debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7 Apr 17 20:46:34 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Apr 17 20:46:34 lunar systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Apr 17 20:46:34 lunar systemd[1]: ssh.service:
[Touch-packages] [Bug 2011458] Re: ssh fails to rebind when it is killed with -HUP
** Patch added: "openssh_9.0p1-1ubuntu7.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2011458/+attachment/5670028/+files/openssh_9.0p1-1ubuntu7.2.debdiff -- 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/2011458 Title: ssh fails to rebind when it is killed with -HUP Status in openssh package in Ubuntu: In Progress Status in openssh source package in Kinetic: In Progress Bug description: [Impact] The sshd re-execution logic is generally broken with systemd socket activation, which means that (1) sshd fails when it is told to re-exec via SIGHUP (e.g. systemctl reload ssh), and (2) sshd fails when started in debug mode. [Test Case] (1) Test systemctl reload ssh: * On a machine with openssh-server installed, make a connection to localhost to activate ssh.service (the connection does not need to be complete, so you can just say "no" at the host key verification stage): $ ssh localhost [...] * Send SIGHUP to sshd by calling systemctl reload ssh: $ systemctl reload ssh * Check the service state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:43:27 UTC; 4s ago Duration: 2min 44.132s TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1112 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Process: 1152 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1153 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 1112 (code=exited, status=255/EXCEPTION) CPU: 79ms Apr 17 20:40:43 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Apr 17 20:41:06 lunar sshd[1113]: Connection closed by 127.0.0.1 port 54666 [preauth] Apr 17 20:43:27 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure Shell server... Apr 17 20:43:27 lunar sshd[1112]: Received SIGHUP; restarting. Apr 17 20:43:27 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell server. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on :: failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: fatal: Cannot bind any address. Apr 17 20:43:27 lunar systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Apr 17 20:43:27 lunar systemd[1]: ssh.service: Failed with result 'exit-code'. * On an affected machine, the service will fail as shown above. (2) Test debug mode: * On a machine with openssh-server installed, edit /etc/default/ssh to configure debug mode for sshd: $ cat /etc/default/ssh # Default settings for openssh-server. This file is sourced by /bin/sh from # /etc/init.d/ssh. # Options to pass to sshd SSHD_OPTS=-ddd * Attempt to make a connection to localhost: $ ssh localhost kex_exchange_identification: read: Connection reset by peer Connection reset by 127.0.0.1 port 22 * On an affected machine, the attempt will fail as shown above, and the service will be in a failed state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:46:34 UTC; 2min 27s ago Duration: 5ms TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1166 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1167 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Main PID: 1167 (code=exited, status=255/EXCEPTION) CPU: 40ms Apr 17 20:46:34 lunar sshd[1167]: Server listening on :: port 22. Apr 17 20:46:34 lunar sshd[1167]: debug3: fd 4 is not O_NONBLOCK Apr 17 20:46:34 lunar sshd[1167]: debug1: Server will not fork when running in debugging mode. Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: entering fd = 7 config len 3456 Apr 17 20:46:34 lunar sshd[1167]: debug3: ssh_msg_send: type 0 Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: done Apr 17 20:46:34 lunar sshd[1167]: debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7 Apr 17 20:46:34 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Apr 17 20:46:34 lunar systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Apr 17 20:46:34 lunar systemd[1]: ssh.service:
[Touch-packages] [Bug 2017924] Re: package libssl1.1 1.1.1f-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libssl1.1/changelog.Debian.gz', which is different from other
** Changed in: openssl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2017924 Title: package libssl1.1 1.1.1f-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libssl1.1/changelog.Debian.gz', which is different from other instances of package libssl1.1:amd64 Status in openssl package in Ubuntu: Invalid Bug description: cannot install unifi network controller due unspecified unmet dependencies ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libssl1.1 1.1.1f-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-71.78~20.04.1-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 AptOrdering: libssl1.1:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 27 12:18:31 2023 DpkgTerminalLog: Preparing to unpack .../libssl1.1_1.1.1f-1ubuntu2.18_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.1f-1ubuntu2.18) over (1.1.1f-1ubuntu2) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libssl1.1_1.1.1f-1ubuntu2.18_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libssl1.1/changelog.Debian.gz', which is different from other instances of package libssl1.1:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libssl1.1/changelog.Debian.gz', which is different from other instances of package libssl1.1:amd64 InstallationDate: Installed on 2021-03-05 (782 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: openssl Title: package libssl1.1 1.1.1f-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libssl1.1/changelog.Debian.gz', which is different from other instances of package libssl1.1:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2017924/+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 1535840] Re: systemd ignoring /etc/modules due to blacklist
In some systems, like embedded devices, it is needed to have the control of the (hardware) watchdog in the application itself, not managed by systemd. In this case, the solution of /etc/default/watchdog doesn't work. Then, if all modules are blacklisted, I have to create a script and manually load them, this is not the best thing, especially for a watchdog! So, this issue still exists for watchdog not managed by the watchdog daemon. The question should be: why ubuntu needs to blacklist all these modules? -- 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/1535840 Title: systemd ignoring /etc/modules due to blacklist Status in systemd package in Ubuntu: Opinion Bug description: I tried the daily build of 16.04 32-bit to test out the watchdog daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in /etc/modules so it is loaded at boot-time, as watchdog timer modules are not normally auto-loaded due to the risk of an unexpected reboot. However I now find that systemd is choosing to ignore my command to load the module in /etc/modules since it appears in the watchdog blacklist. Typical syslog entries look like this: Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted This is just dumb! I have explicitly told the system to load the module, an action that works perfectly well using modprobe or by adding it to the start script for the watchdog, and yet systemd chooses to override that because of the blacklist for auto-loaded modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf). $ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 $ apt-cache policy systemd systemd: Installed: 228-4ubuntu1 Candidate: 228-4ubuntu1 Version table: *** 228-4ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status What I expect to happen is modules added to /etc/modules are loaded at boot time, and not subject to the blacklist for hardware detect / automatic loading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1535840/+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 2017979] Re: [UBUNTU 20.04] Cannot upgrade Ubuntu 20.04.6 LTS to 22.04. because the package language-pack-en-base cannot be updated
** Changed in: language-pack-en-base (Ubuntu Focal) Assignee: (unassigned) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/2017979 Title: [UBUNTU 20.04] Cannot upgrade Ubuntu 20.04.6 LTS to 22.04. because the package language-pack-en-base cannot be updated Status in Ubuntu on IBM z Systems: Confirmed Status in language-pack-en-base package in Ubuntu: New Status in language-pack-en-base source package in Focal: Confirmed Bug description: ---Problem Description--- Cannot upgrade Ubuntu 20.04.6 LTS to 22.04. because the package language-pack-en-base cannot be updated do-release-update does not work Contact Information = pp...@de.ibm.com ---uname output--- Linux lnxut06 5.4.0-148-generic #165-Ubuntu SMP Tue Apr 18 08:52:35 UTC 2023 s390x s390x s390x GNU/Linux Machine Type = 3906 758 M03 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- root@lnxz:/etc/apt# do-release-upgrade Checking for a new Ubuntu release Please install all available updates for your release before upgrading. root@lnxz:/etc/apt# apt update Hit:1 http://de.ports.ubuntu.com/ubuntu-ports focal InRelease Get:2 http://de.ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Ign:4 https://pkg.jenkins.io/debian-stable binary/ InRelease Hit:5 https://pkg.jenkins.io/debian-stable binary/ Release Hit:7 http://de.ports.ubuntu.com/ubuntu-ports focal-backports InRelease Fetched 228 kB in 1s (201 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. root@lnxz:/etc/apt# apt list --upgradable Listing... Done language-pack-en-base/focal-updates 1:20.04+20220818 all [upgradable from: 1:20.04+20220211] N: There are 2 additional versions. Please use the '-a' switch to see them. root@lnxz:/etc/apt# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@lnxz:/etc/apt# apt --only-upgrade install language-pack-en-base Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: language-pack-en-base : Depends: language-pack-en (>= 1:20.04+20220818) but it is not going to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2017979/+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