[Touch-packages] [Bug 1975898] [NEW] RM: ntp from kinetic?
Public bug reported: Should we delete it now that ntpsec has migrated? ** Affects: ntp (Ubuntu) Importance: Undecided Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1975898 Title: RM: ntp from kinetic? Status in ntp package in Ubuntu: New Bug description: Should we delete it now that ntpsec has migrated? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1975898/+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 1976006] [NEW] Bluetooth sound card not detected . I can't connect to my samsung galaxy buds+ via bluetooth . But I can connect to apple mouse via bluetooth
Public bug reported: Bluetooth sound card not detected . I can't connect to my samsung galaxy buds+ via bluetooth . But I can connect to apple mouse via bluetooth Galaxy Buds + is visible in bluetooth devices, but it's switch can't be on ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1545 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 27 22:20:45 2022 InstallationDate: Installed on 2022-04-18 (39 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: KBL dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr1.21:svnAcer:pnAspireE5-576G:pvrV1.47:rvnKBL:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire E 15 dmi.product.name: Aspire E5-576G dmi.product.sku: dmi.product.version: V1.47 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1976006 Title: Bluetooth sound card not detected . I can't connect to my samsung galaxy buds+ via bluetooth . But I can connect to apple mouse via bluetooth Status in alsa-driver package in Ubuntu: New Bug description: Bluetooth sound card not detected . I can't connect to my samsung galaxy buds+ via bluetooth . But I can connect to apple mouse via bluetooth Galaxy Buds + is visible in bluetooth devices, but it's switch can't be on ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1545 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 27 22:20:45 2022 InstallationDate: Installed on 2022-04-18 (39 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: KBL dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr1.21:svnAcer:pnAspireE5-576G:pvrV1.47:rvnKBL:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire E 15 dmi.product.name: Aspire E5-576G dmi.product.sku: dmi.product.version: V1.47 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1976006/+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 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
Hello Utkarsh, or anyone else affected, Accepted keyutils into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/keyutils/1.6.1-2ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: keyutils (Ubuntu Impish) Status: Incomplete => Fix Committed ** Tags added: verification-needed-impish ** Changed in: keyutils (Ubuntu Focal) Status: Incomplete => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Released Status in keyutils source package in Focal: Fix Committed Status in keyutils source package in Impish: Fix Committed Status in keyutils source package in Jammy: Fix Released Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+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 1975875] [NEW] libgail-3-0 install blocked by "=" dependency
You have been subscribed to a public bug: The libgtk dependency in libgail-3-0 is set to = *not* >= 3.24.18. Since libgtk has moved on to 3.24.20 the install of libgail is now blocked, which of course blocks everything that depends on it, Nemo in my case but I'm sure there are many others as well. Using Ubuntu 20.04 LTS with all current updates. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- libgail-3-0 install blocked by "=" dependency https://bugs.launchpad.net/bugs/1975875 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1975909] Re: le bluetooth ne suit pas le rythme (perte de connexion au smartphone, reste connecté, garde l'adresse IP assigné alors que inutilisable), le bluetooth c'est Titanic
bluetoothctl power off; #retour :: Changing power off succeeded bluetoothctl power on; #retour Failed to set power on: org.bluez.Error.Busy dmesg :: hci0: command 0x1003 tx timeout dmesg :: hci0: command 0x1001 tx timeout dmesg :: hci0: command 0x1009 tx timeout -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1975909 Title: le bluetooth ne suit pas le rythme (perte de connexion au smartphone, reste connecté, garde l'adresse IP assigné alors que inutilisable), le bluetooth c'est Titanic et petite anecdote c'est pareil sur raspberry pi OS ; ) Status in bluez package in Ubuntu: New Bug description: Network Bluetooth bluetoothctl system-alias Xorg #Changer de Nom bluetoothctl pairable on; bluetoothctl discoverable on; timeout 20s bluetoothctl scan on & bluetoothctl pair [Mac Address]; apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python2 python-pip; #Ub pip2 install dbus-python; bt-pan client -r [Mac Address]; ((bt-pan est requis)) apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python-dev; #Raspbian wget https://bootstrap.pypa.io/pip/2.7/get-pip.py; python2 get-pip.py; #Raspbian ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Fri May 27 07:30:05 2022 ImageMediaBuild: 20220419 InterestingModules: bnep bluetooth Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 006: ID 248a:8367 Maxxter Telink Wireless Receiver Bus 001 Device 012: ID 1e0e:9001 Qualcomm / Option SimTech, Incorporated Bus 001 Device 011: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:F3:20:41 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) acpidump: hciconfig: hci0:Type: Primary Bus: UART BD Address: B8:27:EB:59:8A:EB ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:865087 acl:5840 sco:0 events:4122 errors:0 TX bytes:1491451 acl:5973 sco:0 commands:314 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1975909/+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 1975875] Re: libgail-3-0 install blocked by "=" dependency
** Package changed: ubuntu => gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1975875 Title: libgail-3-0 install blocked by "=" dependency Status in gtk+3.0 package in Ubuntu: New Bug description: The libgtk dependency in libgail-3-0 is set to = *not* >= 3.24.18. Since libgtk has moved on to 3.24.20 the install of libgail is now blocked, which of course blocks everything that depends on it, Nemo in my case but I'm sure there are many others as well. Using Ubuntu 20.04 LTS with all current updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1975875/+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 1962453] Please test proposed package
Hello Utkarsh, or anyone else affected, Accepted keyutils into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/keyutils/1.6-6ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Released Status in keyutils source package in Focal: Fix Committed Status in keyutils source package in Impish: Fix Committed Status in keyutils source package in Jammy: Fix Released Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+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 1975875] Re: libgail-3-0 install blocked by "=" dependency
At the prompting of the bot added a, hopefully correct, package reference. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1975875 Title: libgail-3-0 install blocked by "=" dependency Status in gtk+3.0 package in Ubuntu: New Bug description: The libgtk dependency in libgail-3-0 is set to = *not* >= 3.24.18. Since libgtk has moved on to 3.24.20 the install of libgail is now blocked, which of course blocks everything that depends on it, Nemo in my case but I'm sure there are many others as well. Using Ubuntu 20.04 LTS with all current updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1975875/+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 1965439] Re: applications can no longer launch when called by kdesu
** Changed in: ubuntustudio-default-settings (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: In Progress Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Committed Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: In Progress Status in sudo source package in Kinetic: Confirmed Status in ubuntustudio-default-settings source package in Kinetic: Fix Committed Status in kdesu package in Debian: New Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1945288] Re: Search domains missing from resolv.conf stub
Happens as well on Ubuntu 20.04, very annoying because it works fine if those domains are manually added to /run/systemd/resolve/stub- resolv.conf file so there's not real limit since glibc is not the issue anymore. This of course gets overwritten on any network change, and in case of VPN connections this happens a lot. -- 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/1945288 Title: Search domains missing from resolv.conf stub Status in systemd package in Ubuntu: Confirmed Bug description: System is Mint 20.2, with the relevant packages taken from Ubuntu Focal. This is the output of `systemd-resolv --status vpn0`: Link 7 (vpn0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: 10.0.0.53 DNS Servers: 10.0.0.53 DNS Domain: example.com example.com.rpz privatelink.blob.core.windows.net node.prd.lan.example.com node.stg.lan.example.com node.dev.lan.example.com However that last domain is missing from `/etc/resolv.conf` (symlink to `/run/systemd/resolve/stub-resolv.conf`), instead there is a line # Too many search domains configured, remaining ones ignored. According to resolv.conf(5) since glibc 2.26 the number of search domains should be unlimited, and installed is 2.31-0ubuntu9.3 VPN is PaloAlto GlobalProtect through the OpenConnect plugin on NetworkManager. Exact same setup and behaviour for a colleague using Pop!_OS 20.04 -- systemd: Installed: 245.4-4ubuntu3.13 Candidate: 245.4-4ubuntu3.13 Version table: *** 245.4-4ubuntu3.13 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3.11 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages libc-bin: Installed: 2.31-0ubuntu9.3 Candidate: 2.31-0ubuntu9.3 Version table: *** 2.31-0ubuntu9.3 100 100 /var/lib/dpkg/status 2.31-0ubuntu9.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2.31-0ubuntu9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945288/+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 1975927] [NEW] package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: it is an error regarding intall software ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 25 18:47:09 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-04-04 (52 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 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal 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/1975927 Title: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: it is an error regarding intall software ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 25 18:47:09 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-04-04 (52 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 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1975927/+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 1971299] Re: Merge nss from Debian unstable for kinetic
** Merge proposal linked: https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/nss/+git/nss/+merge/423527 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1971299 Title: Merge nss from Debian unstable for kinetic Status in nss package in Ubuntu: In Progress Bug description: Upstream: tbd Debian: 2:3.77-1 Ubuntu: 2:3.68.2-0ubuntu1 ### New Debian Changes ### nss (2:3.77-1) unstable; urgency=medium * New upstream release. * debian/libnss3.symbols: Add NSS_3.77 symbol version. -- Mike Hommey Wed, 06 Apr 2022 09:18:22 +0900 nss (2:3.75-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Wed, 09 Feb 2022 08:46:51 +0900 nss (2:3.73.1-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Fri, 17 Dec 2021 06:16:55 +0900 nss (2:3.73-1) unstable; urgency=medium * New upstream release. * Fixes MFSA-2021-51, aka CVE-2021-43527: Memory corruption via DER-encoded DSA and RSA-PSS signatures. -- Mike Hommey Thu, 02 Dec 2021 06:04:31 +0900 nss (2:3.72-2) unstable; urgency=medium * debian/control: libnss3-dev breaks libxmlsec1-dev (<< 1.2.33-1). Closes: #998733. -- Mike Hommey Fri, 12 Nov 2021 06:21:05 +0900 nss (2:3.72-1) unstable; urgency=medium * New upstream release. * debian/libnss3.symbols, nss/lib/ssl/sslinfo.c, nss/lib/ssl/sslt.h, nss/cmd/selfserv/selfserv.c, nss/cmd/strsclnt/strsclnt.c, nss/cmd/tstclnt/tstclnt.c: Bump dependency version for SSL_GetChannelInfo symbol and remove the previous workaround. Closes: #990058. * debian/libnss3.lintian-overrides.in, debian/rules, nss/cmd/shlibsign/shlibsign.c, nss/lib/pk11wrap/pk11load.c, nss/lib/util/secload.c, nss/cmd/shlibsign/Makefile, nss/cmd/shlibsign/manifest.mn: Stop putting freebl, softokn, etc. in a subdirectory. It's a deviation from upstream that is causing more problems than it's worth keeping. Closes: #737855, #846012, #979159. * debian/libnss3-dev.links.in: Remove xulrunner-nss.pc. * debian/rules: Stop forcing xz compression. * debian/copyright: Add dot for continuation. * debian/watch: Upgrade to version 4. * debian/control: Upgrade Standard-Version to 4.6.0: - debian/rules: Build with `make -s` when DEB_BUILD_OPTIONS contains terse. - debian/control: Add Rules-Requires-Root: no. * debian/control: Remove conflict with libnss3-1d. The last Debian version with libnss3-1d was jessie, and it had a newer version anyways. * debian/rules: Enable all hardening options. * debian/libnss3-symbols: Add Build-Depends-Package in symbols file. * debian/*.lintian-overrides*: Remove copyright-refers-to-versionless-license-file lintian overrides. * debian/libnss3.lintian-overrides.in: - s/shlib-without-versioned-soname/shared-library-lacks-version/. - Add lacks-unversioned-link-to-shared-library overrides. * debian/nss-config.in, debian/rules: Ship upstream nss-config instead of ours. Closes: #737855, #963136. * debian/rules, debian/control: Always set Multi-Arch: same. * debian/copyright: - Remove commas in `Files`. - Add missing license name for ifparser. - Add missing `Copyright`. - Remove copyright for mkdepend, which is not in the source tree anymore. * debian/upstream/metadata: Add upstream bug tracking metadata. [ Daniel Kahn Gillmor ] * debian/control: correct Homepage (old URL redirects to 404) [ Janitor ] * debian/changelog: Trim trailing whitespace. * debian/copyright: Use secure copyright file specification URI. * debian/compat, debian/control: - Bump debhelper from deprecated 9 to 13. - Set debhelper-compat version in Build-Depends. * debian/upstream/metadata: Set upstream metadata fields: Repository. * debian/rules: Drop transition for old debug package migration. -- Mike Hommey Tue, 02 Nov 2021 06:57:06 +0900 nss (2:3.70-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Wed, 08 Sep 2021 08:31:23 +0900 nss (2:3.68-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Mon, 19 Jul 2021 06:23:39 +0900 ### Old Ubuntu Delta ### nss (2:3.68.2-0ubuntu1) jammy; urgency=medium * New upstream release. (LP: #1959126) * d/p/CVE-2021-43527.patch: drop patch applied upstream. [ Fixed in 3.68.1 ] -- Athos Ribeiro Mon, 21 Feb 2022 14:55:42 -0300 nss (2:3.68-1ubuntu2) jammy; urgency=medium * SECURITY UPDATE: heap overflow when verifying DSA/RSA-PSS DER-encoded signatures - debian/patches/CVE-2021-43527.patch: check signature lengths in nss/lib/cryptohi/secvfy.c. - CVE-2021-43527 -- Marc Deslauriers Mon, 29 Nov 2021 07:12:54 -0500 nss
[Touch-packages] [Bug 1972159] Re: systemd-oomd frequently kills firefox and visual studio code
This is greatly exasperated because systemd until v251 is using MemFree and not MemAvailable to decide how much memory is remaining. Since Linux aggressively uses MemFree for caching, this will result in systemd-oomd excessively killing applications. There's a fix in upstream 030bc91cb98385904b28a839d1e04bb4160a52d2, which was released as v251 about a week ago. -- 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/1972159 Title: systemd-oomd frequently kills firefox and visual studio code Status in systemd package in Ubuntu: Incomplete Bug description: Since I installed Ubuntu 22.04, firefox and visual studio code are frequently killed by systemd-oomd (every 2hours). I have 8 GB memory and never experienced this before the upgrade to Ubuntu 22.04. I thus assume that the claim that there is not enough memory is abusive. Did 64GB of memory become the minimum requirement to run Ubuntu ? The second problem is that it gives a very bad user experience which is critical for new Ubuntu users. There should be a warning prior killing apps to give the opportunity to save the app data. There should at least be an apologize and an explanation after killing the app. The current behavior gives the impression that Ubuntu 22.04 is unreliable and unsafe to use which is a problem for an LTS release that many people might want to use for critical production context. There might be a configuration problem with systemd-oomd or simply a bogus behavior. I would recommend to disable it or remove it completely until this problem is resolved. This is what I will do for myself because I have work to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/+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 1966381] Re: systemd-oomd is counting cached as used and triggering more easily than it should
Sorry, I did not receive any email for your comment: - yes, I was on -proposed, so as I said, I had the version with the fix - I will try to capture those, but I disabled systemd-oomd since, and have not had issue (at all). -- 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/1966381 Title: systemd-oomd is counting cached as used and triggering more easily than it should Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+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 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange
** Changed in: openssh Status: Unknown => New -- 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: New Status in openssh package in Ubuntu: Triaged Status in openssh source package in Focal: Triaged Status in openssh source package in Hirsute: Won't Fix 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:
[Touch-packages] [Bug 1971299] Re: Merge nss from Debian unstable for kinetic
This bug was fixed in the package nss - 2:3.77-1 Sponsored for Athos Ribeiro (athos-ribeiro) --- nss (2:3.77-1) unstable; urgency=medium * New upstream release. * debian/libnss3.symbols: Add NSS_3.77 symbol version. -- Mike Hommey Wed, 06 Apr 2022 09:18:22 +0900 nss (2:3.75-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Wed, 09 Feb 2022 08:46:51 +0900 nss (2:3.73.1-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Fri, 17 Dec 2021 06:16:55 +0900 nss (2:3.73-1) unstable; urgency=medium * New upstream release. * Fixes MFSA-2021-51, aka CVE-2021-43527: Memory corruption via DER-encoded DSA and RSA-PSS signatures. -- Mike Hommey Thu, 02 Dec 2021 06:04:31 +0900 nss (2:3.72-2) unstable; urgency=medium * debian/control: libnss3-dev breaks libxmlsec1-dev (<< 1.2.33-1). Closes: #998733. -- Mike Hommey Fri, 12 Nov 2021 06:21:05 +0900 nss (2:3.72-1) unstable; urgency=medium * New upstream release. * debian/libnss3.symbols, nss/lib/ssl/sslinfo.c, nss/lib/ssl/sslt.h, nss/cmd/selfserv/selfserv.c, nss/cmd/strsclnt/strsclnt.c, nss/cmd/tstclnt/tstclnt.c: Bump dependency version for SSL_GetChannelInfo symbol and remove the previous workaround. Closes: #990058. * debian/libnss3.lintian-overrides.in, debian/rules, nss/cmd/shlibsign/shlibsign.c, nss/lib/pk11wrap/pk11load.c, nss/lib/util/secload.c, nss/cmd/shlibsign/Makefile, nss/cmd/shlibsign/manifest.mn: Stop putting freebl, softokn, etc. in a subdirectory. It's a deviation from upstream that is causing more problems than it's worth keeping. Closes: #737855, #846012, #979159. * debian/libnss3-dev.links.in: Remove xulrunner-nss.pc. * debian/rules: Stop forcing xz compression. * debian/copyright: Add dot for continuation. * debian/watch: Upgrade to version 4. * debian/control: Upgrade Standard-Version to 4.6.0: - debian/rules: Build with `make -s` when DEB_BUILD_OPTIONS contains terse. - debian/control: Add Rules-Requires-Root: no. * debian/control: Remove conflict with libnss3-1d. The last Debian version with libnss3-1d was jessie, and it had a newer version anyways. * debian/rules: Enable all hardening options. * debian/libnss3-symbols: Add Build-Depends-Package in symbols file. * debian/*.lintian-overrides*: Remove copyright-refers-to-versionless-license-file lintian overrides. * debian/libnss3.lintian-overrides.in: - s/shlib-without-versioned-soname/shared-library-lacks-version/. - Add lacks-unversioned-link-to-shared-library overrides. * debian/nss-config.in, debian/rules: Ship upstream nss-config instead of ours. Closes: #737855, #963136. * debian/rules, debian/control: Always set Multi-Arch: same. * debian/copyright: - Remove commas in `Files`. - Add missing license name for ifparser. - Add missing `Copyright`. - Remove copyright for mkdepend, which is not in the source tree anymore. * debian/upstream/metadata: Add upstream bug tracking metadata. [ Daniel Kahn Gillmor ] * debian/control: correct Homepage (old URL redirects to 404) [ Janitor ] * debian/changelog: Trim trailing whitespace. * debian/copyright: Use secure copyright file specification URI. * debian/compat, debian/control: - Bump debhelper from deprecated 9 to 13. - Set debhelper-compat version in Build-Depends. * debian/upstream/metadata: Set upstream metadata fields: Repository. * debian/rules: Drop transition for old debug package migration. -- Mike Hommey Tue, 02 Nov 2021 06:57:06 +0900 nss (2:3.70-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Wed, 08 Sep 2021 08:31:23 +0900 ** Changed in: nss (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 nss in Ubuntu. https://bugs.launchpad.net/bugs/1971299 Title: Merge nss from Debian unstable for kinetic Status in nss package in Ubuntu: Fix Released Bug description: Upstream: tbd Debian: 2:3.77-1 Ubuntu: 2:3.68.2-0ubuntu1 ### New Debian Changes ### nss (2:3.77-1) unstable; urgency=medium * New upstream release. * debian/libnss3.symbols: Add NSS_3.77 symbol version. -- Mike Hommey Wed, 06 Apr 2022 09:18:22 +0900 nss (2:3.75-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Wed, 09 Feb 2022 08:46:51 +0900 nss (2:3.73.1-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Fri, 17 Dec 2021 06:16:55 +0900 nss (2:3.73-1) unstable; urgency=medium * New upstream release. * Fixes MFSA-2021-51, aka CVE-2021-43527: Memory corruption via DER-encoded DSA and RSA-PSS signatures. -- Mike Hommey Thu, 02 Dec 2021 06:04:31 +0900 nss (2:3.72-2) unstable; urgency=medium * debian/control: libnss3-dev breaks libxmlsec1-dev (<< 1.2.33-1). Closes:
[Touch-packages] [Bug 1975875] Re: libgail-3-0 install blocked by "=" dependency
The package libgail-3-0 is built from the source package gtk+3.0 and the new version of the libgail-3-0 has updated the version of the libgtk-3-0 dependency: Package: libgail-3-0 Architecture: amd64 Version: 3.24.20-0ubuntu1.1 Multi-Arch: same Priority: optional Section: libs Source: gtk+3.0 Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian GNOME Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 152 Depends: at-spi2-core, libatk1.0-0 (>= 2.15.1), libc6 (>= 2.4), libglib2.0-0 (>= 2.57.2), libgtk-3-0 (= 3.24.20-0ubuntu1.1), libpango-1.0-0 (>= 1.41.0) Filename: pool/main/g/gtk+3.0/libgail-3-0_3.24.20-0ubuntu1.1_amd64.deb Size: 22380 MD5sum: d28e85b9496d73fcb94c5c6ff533b86f SHA1: 4a1255a35240911b98d31327a2b957cebbf899f8 SHA256: 5809178cadd9849e3748d3f1c2f39a1ccb2ce55378ca02746b8532cd89e45f62 SHA512: d808ffdb03d75e0a4e12c047c024cb8248afb28e6d4abaf00806ef3bfcba706dcf1365a977022442967320a37c680f0b77593cc74f29249c7985caa392001092 Homepage: https://www.gtk.org/ Description-en: GNOME Accessibility Implementation Library -- shared libraries Gail implements ATK interfaces for GTK widgets which are dynamically loadable at runtime by a GTK application. Once loaded, those parts of an application that use standard GTK widgets will have a basic level of accessibility, without the need to modify the application at all. . This package contains the shared library. Description-md5: 280470c176632353e001009f5036985a Task: ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop I was also able to install a package which depends on libgail-3-0. I think you are going to have to show a bit more about the actual problem which you are encountering. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1975875 Title: libgail-3-0 install blocked by "=" dependency Status in gtk+3.0 package in Ubuntu: New Bug description: The libgtk dependency in libgail-3-0 is set to = *not* >= 3.24.18. Since libgtk has moved on to 3.24.20 the install of libgail is now blocked, which of course blocks everything that depends on it, Nemo in my case but I'm sure there are many others as well. Using Ubuntu 20.04 LTS with all current updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1975875/+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 1976133] [NEW] resolvectl omits domains when mixing search and route params
Public bug reported: Distributor ID: Ubuntu Description:Ubuntu 20.04.4 LTS Release:20.04 Codename: focal systemd 245 (245.4-4ubuntu3.16) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid When I execute: sudo resolvectl domain neth0 ~example.com example.com I expect: Link 17 (neth0): ~example.com example.com As per man: "domain [LINK [DOMAIN...]] - The domain command expects valid DNS domains, possibly prefixed with "~", and configures a per-interface search or route-only domain." What I get instead is: sudo resolvectl domain neth0 ~example.com example.com /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf contains search example.com resolvectl domain neth0 Link 17 (neth0): example.com And: sudo resolvectl domain neth0 example.com ~example.com /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf contains no search line resolvectl domain neth0 Link 17 (neth0): ~example.com ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - resolvectl truncates domains when mixing search and route params + resolvectl omits domains when mixing search and route params -- 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/1976133 Title: resolvectl omits domains when mixing search and route params Status in systemd package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description:Ubuntu 20.04.4 LTS Release:20.04 Codename: focal systemd 245 (245.4-4ubuntu3.16) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid When I execute: sudo resolvectl domain neth0 ~example.com example.com I expect: Link 17 (neth0): ~example.com example.com As per man: "domain [LINK [DOMAIN...]] - The domain command expects valid DNS domains, possibly prefixed with "~", and configures a per-interface search or route-only domain." What I get instead is: sudo resolvectl domain neth0 ~example.com example.com /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf contains search example.com resolvectl domain neth0 Link 17 (neth0): example.com And: sudo resolvectl domain neth0 example.com ~example.com /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf contains no search line resolvectl domain neth0 Link 17 (neth0): ~example.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1976133/+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 1975883] Re: package linux-image-5.15.0-33-generic 5.15.0-33.34 failed to install/upgrade: run-parts: /etc/kernel/postint/d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1975883 Title: package linux-image-5.15.0-33-generic 5.15.0-33.34 failed to install/upgrade: run-parts: /etc/kernel/postint/d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: During upgrade to ubuntu 22 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 May 26 23:42 seq crw-rw+ 1 root audio 116, 33 May 26 23:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Thu May 26 23:45:41 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-03-16 (71 days ago) InstallationMedia: Ubuntu-Server 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-113-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-5.15.0-33-generic 5.15.0-33.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2022-05-26 (0 days ago) dmi.board.name: Standard PC (i440FX + PIIX, 1996) dmi.board.vendor: QEMU dmi.board.version: pc-i440fx-4.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.1 dmi.modalias: dmi:bvn:bvr:bd:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:rvnQEMU:rnStandardPC(i440FX+PIIX,1996):rvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1975883/+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 1965439] Re: applications can no longer launch when called by kdesu
This bug was fixed in the package ubuntustudio-default-settings - 22.10.1 --- ubuntustudio-default-settings (22.10.1) kinetic; urgency=medium * Revert changes for Jammy for driver manager (LP: #1965439) -- Erich Eickmeyer Fri, 27 May 2022 09:01:47 -0700 ** Changed in: ubuntustudio-default-settings (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Confirmed Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: New Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1193236] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*
Still happening in May 2022 on xubuntu 22.04 with xfce -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1193236 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* Status in at-spi: Invalid Status in at-spi2-core package in Ubuntu: Invalid Status in gnome-session package in Ubuntu: Invalid Status in at-spi2-core package in Debian: Invalid Bug description: Since a few days, xsession-errors is fullfilled by that kind of errors: ** (nautilus:22621): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused Similar errors are reported all over the net, but Debian have tried to fix it already: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517 But some other devs seems to blame an atk-bridge: https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA And some others suggest a dbus/gdbus race; the good thing is that seems not disturbing that much the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Fri Jun 21 08:35:40 2013 MarkForUpload: True SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/1193236/+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 1976119] [NEW] Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*
Public bug reported: Every time 'evince' runs it prints this on the terminal: dbind-WARNING **: ... Couldn't connect to accessibility bus: Failed to connect to socket /run/user//at-spi/bus_0: Permission denied AFAICT this is the same as a very-old bug 1193236, but that bug was closed with a comment "If you are affected, open your own bug" (https://bugs.launchpad.net/ubuntu/+source/at- spi2-core/+bug/1193236/comments/20). So I am. Xubuntu (xfce) 22.04 evince version 42.0 at-spi2-core Ubuntu package version 2.44.0-3 STEPS TO REPRODUCE: 1. In a terminal, run /usr/bin/evince RESULTS: Error glop appears on terminal EXPECTED RESULTS: Silence unless there is a real error the user can respond to. ** Affects: at-spi2-core (Ubuntu) Importance: Undecided Status: New ** Description changed: Every time 'evince' runs it prints this on the terminal: dbind-WARNING **: ... Couldn't connect to accessibility bus: Failed to connect to socket /run/user//at-spi/bus_0: Permission denied AFAICT this is the same as a very-old bug 1193236, but that bug was closed with a comment "If you are affected, open your own bug" (https://bugs.launchpad.net/ubuntu/+source/at- spi2-core/+bug/1193236/comments/20). So I am. + + Xubuntu (xfce) 22.04 STEPS TO REPRODUCE: 1. In a terminal, run /usr/bin/evince RESULTS: Error glop appears on terminal EXPECTED RESULTS: Silence unless there is a real error the user can respond to. ** Description changed: Every time 'evince' runs it prints this on the terminal: dbind-WARNING **: ... Couldn't connect to accessibility bus: Failed to connect to socket /run/user//at-spi/bus_0: Permission denied AFAICT this is the same as a very-old bug 1193236, but that bug was closed with a comment "If you are affected, open your own bug" (https://bugs.launchpad.net/ubuntu/+source/at- spi2-core/+bug/1193236/comments/20). So I am. Xubuntu (xfce) 22.04 + evince version 42.0 + + at-spi2-core Ubuntu package version 2.44.0-3 + STEPS TO REPRODUCE: 1. In a terminal, run /usr/bin/evince RESULTS: Error glop appears on terminal EXPECTED RESULTS: Silence unless there is a real error the user can respond to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1976119 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* Status in at-spi2-core package in Ubuntu: New Bug description: Every time 'evince' runs it prints this on the terminal: dbind-WARNING **: ... Couldn't connect to accessibility bus: Failed to connect to socket /run/user//at-spi/bus_0: Permission denied AFAICT this is the same as a very-old bug 1193236, but that bug was closed with a comment "If you are affected, open your own bug" (https://bugs.launchpad.net/ubuntu/+source/at- spi2-core/+bug/1193236/comments/20). So I am. Xubuntu (xfce) 22.04 evince version 42.0 at-spi2-core Ubuntu package version 2.44.0-3 STEPS TO REPRODUCE: 1. In a terminal, run /usr/bin/evince RESULTS: Error glop appears on terminal EXPECTED RESULTS: Silence unless there is a real error the user can respond to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1976119/+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 1933775]
I believe this was fixed for 11.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tbb in Ubuntu. https://bugs.launchpad.net/bugs/1933775 Title: libgcc-s1 and libstdc++6 depend on broken libtbb2 package Status in gcc: In Progress Status in tbb package in Ubuntu: New Bug description: The gcc-11 source package produces libgcc-s1 and (I think?) libstdc++6. Both of these binary packages on Hirsute depend on libtbb2 version 2020.3-1. The latter contains deprecated APIs that create #pragma generated warnings whenever is included. See upstream for discussion: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101228 To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1933775/+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 1933775]
Yes, it was fixed by r11-4187 but the problem is still present on the gcc-10 branch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tbb in Ubuntu. https://bugs.launchpad.net/bugs/1933775 Title: libgcc-s1 and libstdc++6 depend on broken libtbb2 package Status in gcc: In Progress Status in tbb package in Ubuntu: New Bug description: The gcc-11 source package produces libgcc-s1 and (I think?) libstdc++6. Both of these binary packages on Hirsute depend on libtbb2 version 2020.3-1. The latter contains deprecated APIs that create #pragma generated warnings whenever is included. See upstream for discussion: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101228 To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1933775/+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 1965439] Re: applications can no longer launch when called by kdesu
** Changed in: kubuntu-settings (Ubuntu Kinetic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Committed Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Confirmed Status in ubuntustudio-default-settings source package in Kinetic: Fix Committed Status in kdesu package in Debian: New Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1971280] Re: Merge heimdal from Debian unstable for kinetic
** Changed in: heimdal (Ubuntu) Assignee: (unassigned) => Utkarsh Gupta (utkarsh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1971280 Title: Merge heimdal from Debian unstable for kinetic Status in heimdal package in Ubuntu: Incomplete Bug description: Upstream: tbd Debian: 7.7.0+dfsg-3 Ubuntu: 7.7.0+dfsg-3ubuntu1 ### New Debian Changes ### heimdal (7.7.0+dfsg-3) unstable; urgency=high * Fix CVE-2021-3671: A null pointer de-reference was found in the way samba kerberos server handled missing sname in TGS-REQ. Closes: #996586. * Fix autoconf 2.7 issues. -- Brian May Wed, 17 Nov 2021 12:12:45 +1100 heimdal (7.7.0+dfsg-2) unstable; urgency=medium * Build using python3. Closes: #936695, #960032. -- Brian May Tue, 12 May 2020 06:56:04 +1000 heimdal (7.7.0+dfsg-1) unstable; urgency=medium * New upstream version. * Fix CVE-2019-14870: The DelegationNotAllowed Kerberos feature restriction was not being applied when processing protocol transition requests (S4U2Self), in the AD DC KDC. Closes: #946786. -- Brian May Tue, 17 Dec 2019 20:23:41 +1100 heimdal (7.5.0+dfsg-3) unstable; urgency=high * CVE-2018-16860: Samba AD DC S4U2Self/S4U2Proxy unkeyed checksum. Closes: #928966. * CVE-2019-12098: Always confirm PA-PKINIT-KX for anon PKINIT. Closes: #929064. * Update test certificates to pre 2038 expiry. Closes: #923930. -- Brian May Tue, 21 May 2019 18:04:35 +1000 heimdal (7.5.0+dfsg-2.1) unstable; urgency=medium * Non-maintainer upload * Add patch to create headers before building (Closes: 906623) -- Hilko Bengen Sun, 28 Oct 2018 15:10:44 +0100 heimdal (7.5.0+dfsg-2) unstable; urgency=medium * Replace 'MAXHOSTNAMELEN' with 'MaxHostNameLen' in kdc/kx509.c for The Hurd. Closes: #900079. -- Brian May Sat, 02 Jun 2018 10:01:46 +1000 heimdal (7.5.0+dfsg-1) unstable; urgency=high * New upstream version. (Closes: #850723) + CVE-2017-17439: Remote unauthenticated DoS in Heimdal-KDC 7.4 (Closes: #878144, #868157) + Refresh patches. * Bump Standards-Version to 4.1.2 and compat level to 10. + Remove explicit reference to dh-autoreconf. * Use uscan to get orig source. + Refrain from mangling some bundled RFC texts; just exclude the mas they are not installed into any binary anyway. + Update d/copyright to DEP-5. + Can now use standard uscan/gbp/pristine-tar workflow. * Fix some lintian errors/warnings. + Strip trailing whitespace from changelog. + Fix some duplicate long descriptions. + Use optional priority everywhere. + Update/remove some overrides. + Enforce set -e in maintainer scripts. + Enable hardening. * Migrate to -dbgsym. * Add myself to uploaders. -- Dominik George Fri, 15 Dec 2017 01:13:04 +0100 heimdal (7.4.0.dfsg.1-2) unstable; urgency=medium [ Jelmer Vernooij ] * Remove myself from uploaders. [ Brian May ] * Be explicit with heimdal.mkey filename in postinst. Closes: #868638. * Tests should respect DEB_BUILD_OPTIONS=nocheck. Closes: #868842. -- Brian May Sun, 23 Jul 2017 10:32:34 +1000 heimdal (7.4.0.dfsg.1-1) unstable; urgency=high * New upstream version. * Update standards version to 4.0.0. * CVE-2017-11103: Fix Orpheus' Lyre KDC-REP service name validation. (Closes: #868208). -- Brian May Sat, 15 Jul 2017 19:47:32 +1000 heimdal (7.1.0+dfsg-13) unstable; urgency=medium * Add missing symbols base64_decode and base64_encode back into libroken. Closes: #848694. -- Brian May Wed, 26 Apr 2017 19:38:20 +1000 heimdal (7.1.0+dfsg-12) unstable; urgency=high ### Old Ubuntu Delta ### heimdal (7.7.0+dfsg-3ubuntu1) jammy; urgency=medium * Merge with Debian unstable (LP: #1946860). Remaining changes: - Disable lto, to regain dep on roken, otherwise dependencies on amd64 are different to i386 resulting in different files on amd64 and i386. LP #1934936 - Remove symbol rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 (LP #1945787) -- Andreas Hasenack Wed, 08 Dec 2021 18:02:13 -0300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1971280/+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 1971296] Re: Merge net-tools from Debian unstable for kinetic
** Changed in: net-tools (Ubuntu) Assignee: (unassigned) => Utkarsh Gupta (utkarsh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1971296 Title: Merge net-tools from Debian unstable for kinetic Status in net-tools package in Ubuntu: Incomplete Bug description: Upstream: tbd Debian: 1.60+git20181103.0eebece-1 Ubuntu: 1.60+git20181103.0eebece-1ubuntu5 ### New Debian Changes ### net-tools (1.60+git20181103.0eebece-1) unstable; urgency=medium * New upstream version 1.60+git20181103.0eebece - Fix nstrcmp() to prevent ifconfig from showing duplicate interfaces. (Closes: #812886) * Fix d/watch to point to upstream git repository * Add patch to fix decoding of MII vendor ids. (Closes: #549397) - Thanks, Ben Hutchings, for the patch. * Add patch to fix Japanese translation which uses a wrong Kanji character. (Closes: #621752) - Thanks, Takeshi Hamasaki, for the patch. * Add patch to fix wrong indentation of 'collisions' in the Japanese translation. (Closes: #653117) - Thanks, NODA, Kai, for the patch. * Fix Uploaders' field. - Add myself as an uploader. - Fix Tina's details. -- Utkarsh Gupta Fri, 02 Oct 2020 15:01:04 +0530 net-tools (1.60+git20180626.aebd88e-1) unstable; urgency=medium * New upstream snapshot * Refresh patches. * Fix typos in German manpages. Thanks to Prof. Dr. Steffen Wendzel and Dr. Tobias Quathamer for the patch. Closes: #900962. -- Martín Ferrari Mon, 24 Sep 2018 19:08:57 + net-tools (1.60+git20161116.90da8a0-4) unstable; urgency=medium * Update maintainer email address. Closes: #899617. * Update Standards-Version with no changes. -- Martín Ferrari Mon, 24 Sep 2018 17:16:31 + net-tools (1.60+git20161116.90da8a0-3) unstable; urgency=medium * debian/control: Update Vcs-* and Standards-Version. * debian/control: remove references to ancient package ja-trans. * debian/gbp.conf: Update repo layout. -- Martín Ferrari Tue, 31 Jul 2018 19:09:00 + net-tools (1.60+git20161116.90da8a0-2) unstable; urgency=medium * Fix typo in French manpage. Thanks to Michel Grigaut for the patch. * Add manpage for iptunnel, thanks to Sergio Durigan Junior. Closes: #88910 * Rename patches so CME does not choke on them. * Automated cme fixes; packaging improvements. * Remove unused and ancient patch. -- Martín Ferrari Sun, 11 Feb 2018 17:29:24 + net-tools (1.60+git20161116.90da8a0-1) unstable; urgency=medium * New upstream snapshot. * Re-synced translations.patch. * Acknowledge NMUs. Thanks a lot to Andrey Rahmatullin for the fixes and uploads. Closes: 846509. * Fix FTCBFS, thanks to Helmut Grohne for the patch. Closes: #811561. + Really assign CC for cross compilation. + Use triplet prefixed pkg-config. * Add debian/NEWS warning about changing output in net-tools commands. Closing bugs that reported problems in 3rd-party scripts arising from these changes. Closes: #845153, #843892, #820212. * Update Standards-Version, with no changes. -- Martín Ferrari Mon, 26 Dec 2016 05:58:42 + net-tools (1.60+git20150829.73cef8a-2.2) unstable; urgency=medium * Non-maintainer upload. * Apply an additional fix for the previous FTBFS for some architectures. -- Andrey Rahmatullin Thu, 01 Dec 2016 22:49:27 +0500 net-tools (1.60+git20150829.73cef8a-2.1) unstable; urgency=medium * Non-maintainer upload. * Fix FTBFS by applying the upstream patch (Closes: #844073). -- Andrey Rahmatullin Sun, 20 Nov 2016 15:23:12 +0500 net-tools (1.60+git20150829.73cef8a-2) unstable; urgency=medium [ Laurent Bigonville ] * Enable SELinux support. Closes: #666204. [ Martín Ferrari ] * Mark the package 'Multi-Arch: foreign', thanks to Frédéric Brière . Closes: #752584. * Fix bug in Portuguese man page, thanks to julianofisc...@gmail.com. Closes: #805377. -- Martín Ferrari Thu, 19 Nov 2015 14:48:47 + net-tools (1.60+git20150829.73cef8a-1) unstable; urgency=medium ### Old Ubuntu Delta ### net-tools (1.60+git20181103.0eebece-1ubuntu5) jammy; urgency=high * No change rebuild for ppc64el baseline bump. -- Julian Andres Klode Thu, 24 Mar 2022 17:20:48 +0100 net-tools (1.60+git20181103.0eebece-1ubuntu4) jammy; urgency=low * Add new DEP8 tests for hostname and ifconfig (LP: #1679346): - d/t/control: add hostname-set-get and ifconfig-lo-info - d/t/hostname-set-get: new test - d/t/ifconfig-lo-info: new test -- Lena Voytek Fri, 22 Oct 2021 07:49:06 -0700 net-tools (1.60+git20181103.0eebece-1ubuntu3) impish; urgency=medium * No-change rebuild to build packages with zstd
[Touch-packages] [Bug 1972055] Re: [20XXS62S00, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1972055 Title: [20XXS62S00, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Confirmed Bug description: After upgrading Carbon X1 gen 9 to Ubuntu 22.04 (from 20.04), there appeared strange problem with speaker sound in video conferences (Zoom) and also with Chrome (for example YouTube & Preply). The problem is as following: the speaker sound level is reduced when somebody speaks after a gap of silence, then the sound level is quickly increased to normal level. This creates the very strange fluctuating up/down sound level which when sound level is low at the start of each sentence. This problem was not there with Ubuntu 20.04 on the same laptop. This problem is also not presented when using Zoom with Windows 11 on the same machine. Thank you for your consideration. Best regards, Rustem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rustem 1576 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 7 11:24:53 2022 InstallationDate: Installed on 2022-04-23 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: May 07 11:15:06 rox1 pulseaudio[1002]: After module unload, module 'module-null-sink' was still loaded! Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [20XXS62S00, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XXS62S00 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.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XXS62S00:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS62S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XXS62S00 dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1972055/+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 1972159] Re: systemd-oomd frequently kills firefox and visual studio code
For me I have 32GB of ram and it was killing my entire user session and dropping me back to the GDM. (It took me over a week to realise this was happening and I was kicked back to login losing all work at least 15 times, having to log back in produced a lot of log spam that hid the OOM message, I was close to having to reinstall or switch distro to fix it) I was using i3 but this was totally unusable for me and I had to remove the service. Does it just not play nice with applications that grab as much RAM as possible and free it when the system is under pressure? Personally if this isn't fixed and OOM gets turned back on at some point it would be severe enough for me to switch distro. -- 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/1972159 Title: systemd-oomd frequently kills firefox and visual studio code Status in systemd package in Ubuntu: Incomplete Bug description: Since I installed Ubuntu 22.04, firefox and visual studio code are frequently killed by systemd-oomd (every 2hours). I have 8 GB memory and never experienced this before the upgrade to Ubuntu 22.04. I thus assume that the claim that there is not enough memory is abusive. Did 64GB of memory become the minimum requirement to run Ubuntu ? The second problem is that it gives a very bad user experience which is critical for new Ubuntu users. There should be a warning prior killing apps to give the opportunity to save the app data. There should at least be an apologize and an explanation after killing the app. The current behavior gives the impression that Ubuntu 22.04 is unreliable and unsafe to use which is a problem for an LTS release that many people might want to use for critical production context. There might be a configuration problem with systemd-oomd or simply a bogus behavior. I would recommend to disable it or remove it completely until this problem is resolved. This is what I will do for myself because I have work to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/+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 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
Hi Seb, Fixed that. And yes, it's already fixed in Jammy. See the first comment. :) ** Also affects: keyutils (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: keyutils (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Released Status in keyutils source package in Focal: Incomplete Status in keyutils source package in Impish: Incomplete Status in keyutils source package in Jammy: Fix Released Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+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 1974250] Re: ~/.pam_environment gets created as owned by root
On 2022-05-20 16:54, Marc Deslauriers wrote: > Or remove those scripts from Debian completely...looks like they > were added because of https://bugs.debian.org/cgi- > bin/bugreport.cgi?bug=756259 , but muon doesn't seem to use them > anymore... FTR I removed 0009-language-tools.patch from Debian. https://salsa.debian.org/freedesktop- team/accountsservice/-/commit/294910b8 Let's see if somebody complains.. Hopefully not. -- 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/1974250 Title: ~/.pam_environment gets created as owned by root Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Jammy: Fix Released Status in accountsservice source package in Kinetic: Fix Released Bug description: Something has happened lately with accountsservice, which makes it act as root instead of the current user when creating ~/.pam_environment. The very old bug #904395 comes to mind, and this smells a security issue. The function which is supposed to prevent this behavior is here: https://salsa.debian.org/freedesktop- team/accountsservice/-/blob/ubuntu/debian/patches/0010-set- language.patch#L75 Haven't investigated further yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1974250/+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 1965439] Re: applications can no longer launch when called by kdesu
** Changed in: kdesu (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: In Progress Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: In Progress Status in sudo source package in Kinetic: Confirmed Status in ubuntustudio-default-settings source package in Kinetic: In Progress Status in kdesu package in Debian: New Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1972159] Re: systemd-oomd frequently kills firefox and visual studio code
Problem definitely disappeared once I upgraded memory to 40GB. But memory usage displayed in top never exceed 6GB. -- 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/1972159 Title: systemd-oomd frequently kills firefox and visual studio code Status in systemd package in Ubuntu: Incomplete Bug description: Since I installed Ubuntu 22.04, firefox and visual studio code are frequently killed by systemd-oomd (every 2hours). I have 8 GB memory and never experienced this before the upgrade to Ubuntu 22.04. I thus assume that the claim that there is not enough memory is abusive. Did 64GB of memory become the minimum requirement to run Ubuntu ? The second problem is that it gives a very bad user experience which is critical for new Ubuntu users. There should be a warning prior killing apps to give the opportunity to save the app data. There should at least be an apologize and an explanation after killing the app. The current behavior gives the impression that Ubuntu 22.04 is unreliable and unsafe to use which is a problem for an LTS release that many people might want to use for critical production context. There might be a configuration problem with systemd-oomd or simply a bogus behavior. I would recommend to disable it or remove it completely until this problem is resolved. This is what I will do for myself because I have work to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/+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 1975909] [NEW] le bluetooth ne suit pas le rythme (perte de connexion au smartphone, reste connecté, garde l'adresse IP assigné alors que inutilisable), le bluetooth c'est Titani
Public bug reported: Network Bluetooth bluetoothctl system-alias Xorg #Changer de Nom bluetoothctl pairable on; bluetoothctl discoverable on; timeout 20s bluetoothctl scan on & bluetoothctl pair [Mac Address]; apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python2 python-pip; #Ub pip2 install dbus-python; bt-pan client -r [Mac Address]; ((bt-pan est requis)) apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python-dev; #Raspbian wget https://bootstrap.pypa.io/pip/2.7/get-pip.py; python2 get-pip.py; #Raspbian ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Fri May 27 07:30:05 2022 ImageMediaBuild: 20220419 InterestingModules: bnep bluetooth Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 006: ID 248a:8367 Maxxter Telink Wireless Receiver Bus 001 Device 012: ID 1e0e:9001 Qualcomm / Option SimTech, Incorporated Bus 001 Device 011: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:F3:20:41 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) acpidump: hciconfig: hci0: Type: Primary Bus: UART BD Address: B8:27:EB:59:8A:EB ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:865087 acl:5840 sco:0 events:4122 errors:0 TX bytes:1491451 acl:5973 sco:0 commands:314 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image jammy raspi-image uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1975909 Title: le bluetooth ne suit pas le rythme (perte de connexion au smartphone, reste connecté, garde l'adresse IP assigné alors que inutilisable), le bluetooth c'est Titanic et petite anecdote c'est pareil sur raspberry pi OS ; ) Status in bluez package in Ubuntu: New Bug description: Network Bluetooth bluetoothctl system-alias Xorg #Changer de Nom bluetoothctl pairable on; bluetoothctl discoverable on; timeout 20s bluetoothctl scan on & bluetoothctl pair [Mac Address]; apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python2 python-pip; #Ub pip2 install dbus-python; bt-pan client -r [Mac Address]; ((bt-pan est requis)) apt -y install libdbus-1-3 libdbus-1-dev libglib2.0-dev python-dev; #Raspbian wget https://bootstrap.pypa.io/pip/2.7/get-pip.py; python2 get-pip.py; #Raspbian ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Fri May 27 07:30:05 2022 ImageMediaBuild: 20220419 InterestingModules: bnep bluetooth Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 006: ID 248a:8367 Maxxter Telink Wireless Receiver Bus 001 Device 012: ID 1e0e:9001 Qualcomm / Option SimTech, Incorporated Bus 001 Device 011: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:F3:20:41 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) acpidump: hciconfig: hci0:Type: Primary Bus: UART BD Address: B8:27:EB:59:8A:EB ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:865087 acl:5840 sco:0 events:4122 errors:0 TX bytes:1491451 acl:5973 sco:0 commands:314 errors:0 To manage notifications about this bug go to:
