[Touch-packages] [Bug 2026307] Re: ssh-askpass-gnome pops up for every sudo command
Thanks for getting back. I refactored my application to use pkexec, so idk when i'll get around to testing this. Unfortunately, due to the super old policykit package in debian/ubuntu my app still doesn't work in ubuntu and probably won't support ubuntu until 23.10, assuming policykit-1 122 makes it in. Also, looks like it has some gtk4 bugs that don't happen in fedora. I'll see how 23.10 fairs. Just some volunteered data for the project. :) -- 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/2026307 Title: ssh-askpass-gnome pops up for every sudo command Status in openssh package in Ubuntu: New Status in openssh source package in Jammy: Triaged Status in openssh source package in Kinetic: Triaged Status in openssh source package in Lunar: Triaged Bug description: When running multiple commands like this: SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup /usr/local/bin/ from my gtk4 app, the ssh-askpass-gnome dialog and the gnome inhibitShortcutsDialog pops up. i click allow on the inhibitShortcutsDialog, then enter my password, which is accepted, then they both pop up again for each of these sudo commands my app calls. This happens in ubuntu 22.04-23.04 (completely updated) using gnome. If i use xfce in the same ubuntu versions, the gnome dialog doesn't pop up, of course, and ssh-askpass-gnome works properly (one entry and then all commands executed without further prompting). Fedora 37 works properly with gnome x11 or wayland, and xfce. Not sure if this is a bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something else. ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome 1:9.0p1-1ubuntu8.2 fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2026307/+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 189517] Re: pkexec needs ability to retain user HOME and possibly other environment
my fedora computer has pkexec version 121 which has the --keep-cwd option. if ubuntu would update pkexec i'm guessing it would have that option too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/189517 Title: pkexec needs ability to retain user HOME and possibly other environment Status in gparted package in Ubuntu: Invalid Status in policykit-1 package in Ubuntu: Confirmed Bug description: Launching gui applications with pkexec strips their environment bare and points the home directory to /root, causing the gnome file dialog to behave badly. It needs a way to preserve the user home the way sudo and gksu do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/189517/+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 2026307] Re: ssh-askpass-gnome pops up for every sudo command
adding the .desktop file and logging back in and re-running did not fix the issue for me with 23.04, unfortunately. To be clear, my app is calling multiple of these commands and the bug is that one "allow" and one password entry are not enough. both dialogs pop up for each invocation of the SUOD_ASKPASS commands as if no gnome inhibitShortcuts preference or password were entered. -- 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/2026307 Title: ssh-askpass-gnome pops up for every sudo command Status in openssh package in Ubuntu: New Status in openssh source package in Jammy: Triaged Status in openssh source package in Kinetic: Triaged Status in openssh source package in Lunar: Triaged Bug description: When running multiple commands like this: SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup /usr/local/bin/ from my gtk4 app, the ssh-askpass-gnome dialog and the gnome inhibitShortcutsDialog pops up. i click allow on the inhibitShortcutsDialog, then enter my password, which is accepted, then they both pop up again for each of these sudo commands my app calls. This happens in ubuntu 22.04-23.04 (completely updated) using gnome. If i use xfce in the same ubuntu versions, the gnome dialog doesn't pop up, of course, and ssh-askpass-gnome works properly (one entry and then all commands executed without further prompting). Fedora 37 works properly with gnome x11 or wayland, and xfce. Not sure if this is a bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something else. ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome 1:9.0p1-1ubuntu8.2 fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2026307/+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 2026307] Re: ssh-askpass-gnome pops up for every sudo command
my mistake ** Package changed: gnome-shell (Ubuntu) => openssh (Ubuntu) -- 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/2026307 Title: ssh-askpass-gnome pops up for every sudo command Status in openssh package in Ubuntu: New Status in openssh source package in Jammy: Triaged Status in openssh source package in Kinetic: Triaged Status in openssh source package in Lunar: Triaged Bug description: When running multiple commands like this: SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup /usr/local/bin/ from my gtk4 app, the ssh-askpass-gnome dialog and the gnome inhibitShortcutsDialog pops up. i click allow on the inhibitShortcutsDialog, then enter my password, which is accepted, then they both pop up again for each of these sudo commands my app calls. This happens in ubuntu 22.04-23.04 (completely updated) using gnome. If i use xfce in the same ubuntu versions, the gnome dialog doesn't pop up, of course, and ssh-askpass-gnome works properly (one entry and then all commands executed without further prompting). Fedora 37 works properly with gnome x11 or wayland, and xfce. Not sure if this is a bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something else. ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome 1:9.0p1-1ubuntu8.2 fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2026307/+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 2026307] Re: ssh-askpass-gnome pops up for every sudo command
** Package changed: openssh (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Triaged => 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/2026307 Title: ssh-askpass-gnome pops up for every sudo command Status in openssh package in Ubuntu: New Status in openssh source package in Jammy: Triaged Status in openssh source package in Kinetic: Triaged Status in openssh source package in Lunar: Triaged Bug description: When running multiple commands like this: SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup /usr/local/bin/ from my gtk4 app, the ssh-askpass-gnome dialog and the gnome inhibitShortcutsDialog pops up. i click allow on the inhibitShortcutsDialog, then enter my password, which is accepted, then they both pop up again for each of these sudo commands my app calls. This happens in ubuntu 22.04-23.04 (completely updated) using gnome. If i use xfce in the same ubuntu versions, the gnome dialog doesn't pop up, of course, and ssh-askpass-gnome works properly (one entry and then all commands executed without further prompting). Fedora 37 works properly with gnome x11 or wayland, and xfce. Not sure if this is a bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something else. ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome 1:9.0p1-1ubuntu8.2 fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2026307/+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 2026307] Re: ssh-askpass-gnome pops up for every sudo command
btw, if i sit there and click "allow" and enter the sudo password for every sudo command my app envokes, it will eventually process all of them. So, it's like the preference for the "inhibit shortcuts" dialog is not being saved, and the sudo auth is not being saved for the 15 min or whatever it's set for. I find it odd that both of these things would fail, but maybe one is interfering with the other. -- 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/2026307 Title: ssh-askpass-gnome pops up for every sudo command Status in openssh package in Ubuntu: New Bug description: When running multiple commands like this: SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup /usr/local/bin/ from my gtk4 app, the ssh-askpass-gnome dialog and the gnome inhibitShortcutsDialog pops up. i click allow on the inhibitShortcutsDialog, then enter my password, which is accepted, then they both pop up again for each of these sudo commands my app calls. This happens in ubuntu 22.04-23.04 (completely updated) using gnome. If i use xfce in the same ubuntu versions, the gnome dialog doesn't pop up, of course, and ssh-askpass-gnome works properly (one entry and then all commands executed without further prompting). Fedora 37 works properly with gnome x11 or wayland, and xfce. Not sure if this is a bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something else. ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome 1:9.0p1-1ubuntu8.2 fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2026307/+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 2026307] Re: ssh-askpass-gnome pops up for every sudo command
** Description changed: When running multiple commands like this: - SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup - /usr/local/bin/ from my gtk4 app the ssh-askpass-gnome dialog and the - gnome inhibitShortcutsDialog pops up, i click allow on the - inhibitShortcutsDialog, then enter my password which is accepted, then + + SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup /usr/local/bin/ + + from my gtk4 app, the ssh-askpass-gnome dialog and the gnome + inhibitShortcutsDialog pops up. i click allow on the + inhibitShortcutsDialog, then enter my password, which is accepted, then they both pop up again for each of these sudo commands my app calls. This happens in ubuntu 22.04-23.04 (completely updated) using gnome. If - i use xfce in same ubuntu versions, the gnome dialog doesn't pop up, of - course, and ssh-askpass-gnome works properly (one entry and then all - commands executed without further prompting). fedora 37 works properly + i use xfce in the same ubuntu versions, the gnome dialog doesn't pop up, + of course, and ssh-askpass-gnome works properly (one entry and then all + commands executed without further prompting). Fedora 37 works properly with gnome x11 or wayland, and xfce. Not sure if this is a bug in - ubuntu's ssh-askpass-gnome, gnome-shell, or both. + ubuntu's ssh-askpass-gnome, gnome-shell, or both/something else. ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome 1:9.0p1-1ubuntu8.2 fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6 thanks -- 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/2026307 Title: ssh-askpass-gnome pops up for every sudo command Status in openssh package in Ubuntu: New Bug description: When running multiple commands like this: SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup /usr/local/bin/ from my gtk4 app, the ssh-askpass-gnome dialog and the gnome inhibitShortcutsDialog pops up. i click allow on the inhibitShortcutsDialog, then enter my password, which is accepted, then they both pop up again for each of these sudo commands my app calls. This happens in ubuntu 22.04-23.04 (completely updated) using gnome. If i use xfce in the same ubuntu versions, the gnome dialog doesn't pop up, of course, and ssh-askpass-gnome works properly (one entry and then all commands executed without further prompting). Fedora 37 works properly with gnome x11 or wayland, and xfce. Not sure if this is a bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something else. ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome 1:9.0p1-1ubuntu8.2 fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2026307/+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 2026307] [NEW] ssh-askpass-gnome pops up for every sudo command
Public bug reported: When running multiple commands like this: SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup /usr/local/bin/ from my gtk4 app the ssh-askpass-gnome dialog and the gnome inhibitShortcutsDialog pops up, i click allow on the inhibitShortcutsDialog, then enter my password which is accepted, then they both pop up again for each of these sudo commands my app calls. This happens in ubuntu 22.04-23.04 (completely updated) using gnome. If i use xfce in same ubuntu versions, the gnome dialog doesn't pop up, of course, and ssh-askpass-gnome works properly (one entry and then all commands executed without further prompting). fedora 37 works properly with gnome x11 or wayland, and xfce. Not sure if this is a bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both. ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome 1:9.0p1-1ubuntu8.2 fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6 thanks ** Affects: openssh (Ubuntu) Importance: Undecided Status: 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/2026307 Title: ssh-askpass-gnome pops up for every sudo command Status in openssh package in Ubuntu: New Bug description: When running multiple commands like this: SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup /usr/local/bin/ from my gtk4 app the ssh-askpass-gnome dialog and the gnome inhibitShortcutsDialog pops up, i click allow on the inhibitShortcutsDialog, then enter my password which is accepted, then they both pop up again for each of these sudo commands my app calls. This happens in ubuntu 22.04-23.04 (completely updated) using gnome. If i use xfce in same ubuntu versions, the gnome dialog doesn't pop up, of course, and ssh-askpass-gnome works properly (one entry and then all commands executed without further prompting). fedora 37 works properly with gnome x11 or wayland, and xfce. Not sure if this is a bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both. ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome 1:9.0p1-1ubuntu8.2 fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2026307/+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 2009598] [NEW] Error when I run "sudo apt upgrade"
Public bug reported: When I run sudo apt upgrade, I have this error : package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Tue Mar 7 14:07:39 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2023-02-25 (9 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230216) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=3274a782-2ac3-4126-ae6f-61555798cd06 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.20ubuntu2 apt 2.5.6 SourcePackage: mesa Title: package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2014 dmi.bios.release: 1.11 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.11 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.54 dmi.chassis.asset.tag: CNU422B518 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 21.84 dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:br1.11:efr21.84:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:skuF9W54UP#UUZ: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.sku: F9W54UP#UUZ dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar single-occurrence ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2009598 Title: Error when I run "sudo apt upgrade" Status in mesa package in Ubuntu: New Bug description: When I run sudo apt upgrade, I have this error : package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux- gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber- dri:amd64 21.3.7-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Tue Mar 7 14:07:39 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so », qui appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1 ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2023-02-25 (9 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230216) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vml
[Touch-packages] [Bug 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible
Hey Tommy, I'm in a similar boot to Frederick. Thanks for taking the time to list your steps. What command did you use to unpack your initrd? After copying over the drivers what command or tool did you use to repack it? Was it dracut, initramfs-tools, or something else entirely? Thanks again! -- 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/1950996 Title: Missing all modules for usb nics in initrd which makes PXE boot impossible Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Confirmed Status in initramfs-tools source package in Hirsute: Confirmed Status in initramfs-tools source package in Impish: Won't Fix Status in initramfs-tools source package in Jammy: Fix Released Status in initramfs-tools package in Debian: Unknown Bug description: initrd taken from the live iso for PXE boot does not contain USB NIC drivers which makes PXE installation/netboot impossible via usb. This is the case on 20.04 server iso (both hwe and normal kernel/initrd) and desktop iso. "kernel/drivers/net/usb" is empty and needs to be included in the initramfs build. As most modern thin laptops lack physical rj45 ethernet this is a big issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18 Uname: Linux 5.8.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 16:47:45 2021 PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to focal on 2020-05-11 (552 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950996/+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 1851649] [NEW] Package bug
Public bug reported: I couldn't change brightness. Probably this bug is related to the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 7 14:54:15 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:397d] NVIDIA Corporation GF119M [GeForce 410M] [10de:1054] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF119M [GeForce 410M] [17aa:397d] InstallationDate: Installed on 2019-11-06 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO HuronRiver Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=3f6eec95-af31-4261-96ff-7e5695b716cc ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 44CN43WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr44CN43WW:bd10/27/2011:svnLENOVO:pnHuronRiverPlatform:pvrLenovoB570e:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: HuronRiver Platform dmi.product.sku: System SKUNumber dmi.product.version: Lenovo B570e dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1851649 Title: Package bug Status in xorg package in Ubuntu: New Bug description: I couldn't change brightness. Probably this bug is related to the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 7 14:54:15 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:397d] NVIDIA Corporation GF119M [GeForce 410M] [10de:1054] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF119M [GeForce 410M] [17aa:397d] InstallationDate: Installed on 2019-11-06 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO HuronRiver Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=3f6eec95-af31-4261-96ff-7e5695b716cc ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 44CN43WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr44CN43WW:bd10/27/2011:svnLENOVO:pnHuronRiverPlatform:pvrLenovoB570e:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: HuronRiver Platform dmi.product.sku: System SKUNumber dmi.product.version: Lenovo B570e dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libg
[Touch-packages] [Bug 1825378] Re: systemd-networkd doesn't set wireguard peer endpoint
I don't have access to the affected systems at the moment, but the test case and your summary looks correct. Thanks for taking a look at this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825378 Title: systemd-networkd doesn't set wireguard peer endpoint Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [impact] systemd does not set endpoints for wireguard interfaces correctly. This makes wireguard unusable. [test case] install a disco or eoan system and set up a wireguard interface: $ sudo add-apt-repository ppa:wireguard/wireguard $ sudo apt install wireguard ...(this does a lot of stuff)... create a file as below; There is no need to setup remote server to reproduce this issue, but PublicKey/PrivateKey should be valid one (used instructions from https://www.linode.com/docs/networking/vpn /set-up-wireguard-vpn-on-ubuntu/#configure-wireguard-server): $ cat /etc/systemd/network/wg0.netdev [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=uMuCbguKYdKanRYMbDSriIdgxGxJR57Us1zEy8wRc1M= ListenPort=51820 [WireGuardPeer] PublicKey=ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 $ sudo systemctl restart systemd-networkd $ sudo wg show wg0 interface: wg0 public key: BnvFgvPiVb5xURfzZ5liV1P77qeGeJDIX3C1iNquA2k= private key: (hidden) listening port: 51820 peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= allowed ips: 10.0.0.0/8 the last command should print remote endpoint address, e.g.: peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 [regression potential] any changes to systemd contain the potential for serious regressions. However, this is cherry picked directly from upstream, with the releases requiring patching (disco and eoan) being at exactly the same version and very close to upstream already. Additionally, while this does add 2 new functions (from upstream commit https://github.com/systemd/systemd/pull/11580/commits/abd48ec87f2ac5dd571a99dcb4db88c4affdffc8), they are only used - and code is only changed in - wireguard.c, so any regressions should be limited to wireguard interfaces (unless systemd crashes completely). [other info] this bug is not present in cosmic and earlier, and is already fixed in upstream systemd, so this is needed only for disco and eoan. original description: --- systemd/disco 240 shipped with Ubuntu 19.04 beta does not set endpoints for [WireguradPeer] properly. This regression was introduced in v241 and merged into v240. systemd 241 doesn't set wireguard peer endpoint https://github.com/systemd/systemd/issues/11579 Revert of the regression was landed on v240 stable branch https://github.com/systemd/systemd-stable/pull/39 1)2) confirmed with, systemd/disco 240-6ubuntu5 amd64 3) put a netdev file /etc/systemd/network/wg0.netdev --- [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=** ListenPort=51820 [WireGuardPeer] PublicKey=* AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 and run --- # systemctl restart systemd-networkd # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * allowed ips: 10.0.0.0/8 4) the last command should print remote endpoint address. --- # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825378/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825378] Re: systemd-networkd doesn't set wireguard peer endpoint
Hi all, could the package maintainer(s) please take a look at this? This breaks (almost) any WireGuard endpoint configured by systemd- networkd. Worse, it breaks them silently, which makes for a fun debugging adventure. The fixed patch (https://github.com/systemd/systemd-stable/pull/39) has been applied upstream since early February, how did the broken one get backported without testing during a release freeze? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825378 Title: systemd-networkd doesn't set wireguard peer endpoint Status in systemd package in Ubuntu: Confirmed Bug description: systemd/disco 240 shipped with Ubuntu 19.04 beta does not set endpoints for [WireguradPeer] properly. This regression was introduced in v241 and merged into v240. systemd 241 doesn't set wireguard peer endpoint https://github.com/systemd/systemd/issues/11579 Revert of the regression was landed on v240 stable branch https://github.com/systemd/systemd-stable/pull/39 1)2) confirmed with, systemd/disco 240-6ubuntu5 amd64 3) put a netdev file /etc/systemd/network/wg0.netdev --- [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=** ListenPort=51820 [WireGuardPeer] PublicKey=* AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 and run --- # systemctl restart systemd-networkd # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * allowed ips: 10.0.0.0/8 4) the last command should print remote endpoint address. --- # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825378/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755202] Re: Clone Mac Address Function On Default Wifi Setting Does Not Work (Ubuntu 17.10)
** Description changed: I am Just Using Ubuntu 17.10. My Uname -a Result -> Linux user 4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. Before Using Ubuntu 17.10, I was on fedora 26. I notice that there is also (MAC Address Randomization issue). I can fixed it and can use default mac address spoofing function from wifi setting -> Network Profile Setting (*) -> Identity -> Cloned Address -> And Add mac address to spoof for particular network. This Default mac address spoof function is very useful for me. Clearly, I doesn't mean (MAC Address Randomization issue) https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513 Now I have a trouble with this feature (default mac spoffing). I can connect Wifi-s with great signal easily without using cloned address function. But when I added spoof address to setting, the wifi-s cannot be connected. I tried two wifi-s from near me which can connect on fedora 26. One is open type network and the other is WPA Enterprise network. If this function doesn't work for anyone, this must be a bug. If it is a bug, hope it will fix it next release. Please, Don't Hesitate to ask more information. I really want to help to fix bug. + Hardware Info + Lenovo Z470 - Core i5 Second Gen + I used external wifi adapter - Card King http://a.co/gMrHzZQ (RT3072 Chipset) + + #info lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 network-manager: Installed: 1.8.4-1ubuntu3 Candidate: 1.8.4-1ubuntu3 Version table: *** 1.8.4-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status - - journalctl log is pasted here. - https://pastebin.com/Ki3R48pw + Update Journalctl with network-manager log + First I Connect my wifi named "blizzart" without using spoof address. Connected and works fine. + After 2 minutes later, I disconnected. + And then add spoof address and try to connect again. + But It is still trying to connect. You can see in the log. + https://pastebin.com/vmFMefih -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1755202 Title: Clone Mac Address Function On Default Wifi Setting Does Not Work (Ubuntu 17.10) Status in network-manager package in Ubuntu: Incomplete Bug description: I am Just Using Ubuntu 17.10. My Uname -a Result -> Linux user 4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. Before Using Ubuntu 17.10, I was on fedora 26. I notice that there is also (MAC Address Randomization issue). I can fixed it and can use default mac address spoofing function from wifi setting -> Network Profile Setting (*) -> Identity -> Cloned Address -> And Add mac address to spoof for particular network. This Default mac address spoof function is very useful for me. Clearly, I doesn't mean (MAC Address Randomization issue) https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513 Now I have a trouble with this feature (default mac spoffing). I can connect Wifi-s with great signal easily without using cloned address function. But when I added spoof address to setting, the wifi-s cannot be connected. I tried two wifi-s from near me which can connect on fedora 26. One is open type network and the other is WPA Enterprise network. If this function doesn't work for anyone, this must be a bug. If it is a bug, hope it will fix it next release. Please, Don't Hesitate to ask more information. I really want to help to fix bug. Hardware Info Lenovo Z470 - Core i5 Second Gen I used external wifi adapter - Card King http://a.co/gMrHzZQ (RT3072 Chipset) #info lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 network-manager: Installed: 1.8.4-1ubuntu3 Candidate: 1.8.4-1ubuntu3 Version table: *** 1.8.4-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Update Journalctl with network-manager log First I Connect my wifi named "blizzart" without using spoof address. Connected and works fine. After 2 minutes later, I disconnected. And then add spoof address and try to connect again. But It is still trying to connect. You can see in the log. https://pastebin.com/vmFMefih To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755202/+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 1755202] Re: Clone Mac Address Function On Default Wifi Setting Does Not Work (Ubuntu 17.10)
** Description changed: I am Just Using Ubuntu 17.10. My Uname -a Result -> Linux user 4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. Before Using Ubuntu 17.10, I was on fedora 26. I notice that there is also (MAC Address Randomization issue). I can fixed it and can use default mac address spoofing function from wifi setting -> Network Profile Setting (*) -> Identity -> Cloned Address -> And Add mac address to spoof for particular network. This Default mac address spoof function is very useful for me. Clearly, I doesn't mean (MAC Address Randomization issue) https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513 Now I have a trouble with this feature (default mac spoffing). I can connect Wifi-s with great signal easily without using cloned address function. But when I added spoof address to setting, the wifi-s cannot be connected. I tried two wifi-s from near me which can connect on fedora 26. One is open type network and the other is WPA Enterprise network. If this function doesn't work for anyone, this must be a bug. If it is a bug, hope it will fix it next release. Please, Don't Hesitate to ask more information. I really want to help to fix bug. #info lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 network-manager: Installed: 1.8.4-1ubuntu3 Candidate: 1.8.4-1ubuntu3 Version table: *** 1.8.4-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status + + + journalctl log is pasted here. + https://pastebin.com/Ki3R48pw -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1755202 Title: Clone Mac Address Function On Default Wifi Setting Does Not Work (Ubuntu 17.10) Status in network-manager package in Ubuntu: Incomplete Bug description: I am Just Using Ubuntu 17.10. My Uname -a Result -> Linux user 4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. Before Using Ubuntu 17.10, I was on fedora 26. I notice that there is also (MAC Address Randomization issue). I can fixed it and can use default mac address spoofing function from wifi setting -> Network Profile Setting (*) -> Identity -> Cloned Address -> And Add mac address to spoof for particular network. This Default mac address spoof function is very useful for me. Clearly, I doesn't mean (MAC Address Randomization issue) https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513 Now I have a trouble with this feature (default mac spoffing). I can connect Wifi-s with great signal easily without using cloned address function. But when I added spoof address to setting, the wifi-s cannot be connected. I tried two wifi-s from near me which can connect on fedora 26. One is open type network and the other is WPA Enterprise network. If this function doesn't work for anyone, this must be a bug. If it is a bug, hope it will fix it next release. Please, Don't Hesitate to ask more information. I really want to help to fix bug. #info lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 network-manager: Installed: 1.8.4-1ubuntu3 Candidate: 1.8.4-1ubuntu3 Version table: *** 1.8.4-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status journalctl log is pasted here. https://pastebin.com/Ki3R48pw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755202/+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 1755202] Re: Clone Mac Address Function On Default Wifi Setting Does Not Work (Ubuntu 17.10)
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1755202 Title: Clone Mac Address Function On Default Wifi Setting Does Not Work (Ubuntu 17.10) Status in network-manager package in Ubuntu: New Bug description: I am Just Using Ubuntu 17.10. My Uname -a Result -> Linux user 4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. Before Using Ubuntu 17.10, I was on fedora 26. I notice that there is also (MAC Address Randomization issue). I can fixed it and can use default mac address spoofing function from wifi setting -> Network Profile Setting (*) -> Identity -> Cloned Address -> And Add mac address to spoof for particular network. This Default mac address spoof function is very useful for me. Clearly, I doesn't mean (MAC Address Randomization issue) https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513 Now I have a trouble with this feature (default mac spoffing). I can connect Wifi-s with great signal easily without using cloned address function. But when I added spoof address to setting, the wifi-s cannot be connected. I tried two wifi-s from near me which can connect on fedora 26. One is open type network and the other is WPA Enterprise network. If this function doesn't work for anyone, this must be a bug. If it is a bug, hope it will fix it next release. Please, Don't Hesitate to ask more information. I really want to help to fix bug. #info lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 network-manager: Installed: 1.8.4-1ubuntu3 Candidate: 1.8.4-1ubuntu3 Version table: *** 1.8.4-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755202/+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 1583237] Re: lxc-attach strange tty behavior (kills command) when stderr is redirected to a file
"sudo lxc-attach -n utest -- dd if=/dev/zero of=/tmp/foo bs=1M count=10 2>&1" Works -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1583237 Title: lxc-attach strange tty behavior (kills command) when stderr is redirected to a file Status in autopkgtest package in Ubuntu: New Status in lxc package in Ubuntu: New Bug description: On a fresh Ubuntu 16 release, commands started by lxc-attach such as dd are being killed WHEN REDIRECTING stderr (to a file), and lxc- attach return a zero status. Command works fine without the redirection. This scenario is working on Ubuntu 15 with previous lxc release, but not on new LXC 2.0.0 (same issue on 2.0.1 too) sudo apt-get -y install lxc sudo lxc-create -n utest -t ubuntu -- -a amd64 -b $USER sudo lxc-start -d --name utest sudo lxc-attach -n utest -- dd if=/dev/zero of=/tmp/foo bs=1M count=10 2>/tmp/bar sudo lxc-attach -n utest -- ls -lh /tmp/foo -rw-r--r-- 1 root root 0 May 18 05:46 /tmp/foo Might be related to bug 1553097 (and/or https://github.com/lxc/lxc/pull/873) NOTE: Sometimes the "sudo lxc-attach -n utest_bizio_tests -- ls -lh /tmp/foo" ALSO does not return anything (no output) I'm available for any additional info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1583237/+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 1534115] [NEW] apt-add-repository ppa:user/distro/repository pattern not recognized
Public bug reported: add-apt-repository --help shows ppa:user/distro/repository as possible pattern to add. sudo apt-add-repository ppa:nginx/stable works as expected. sudo apt-add-repository ppa:nginx/vivid/stable doesn't works. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1534115 Title: apt-add-repository ppa:user/distro/repository pattern not recognized Status in software-properties package in Ubuntu: New Bug description: add-apt-repository --help shows ppa:user/distro/repository as possible pattern to add. sudo apt-add-repository ppa:nginx/stable works as expected. sudo apt-add-repository ppa:nginx/vivid/stable doesn't works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1534115/+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 1440539] Re: auto capitalization is capitalizing first two letters instead of one
** Summary changed: - auto capitalization is capitalizing first two letters insted of one + auto capitalization is capitalizing first two letters instead of one -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1440539 Title: auto capitalization is capitalizing first two letters instead of one Status in ubuntu-keyboard package in Ubuntu: New Bug description: Nexus 4 owner here! I installed Ubuntu Touch stable channel (14.10 r17). So problem that i noticed is when auto capitalization is turned on it always capitalizes 2 letters instead only first one! No matter where, on login, on beginning of each sentence and everywhere where keyboard is used, and it does that every time. Im sorry if that's already reported or maybe its not a bug, but i couldn't find the solution so i decided to report it! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1440539/+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 1440539] Re: auto capitalization is capitalizing first two letters insted of one
Hello Michael, thank you for checking that! I didn't check all languages, but I had same problem on English, German and Croatian keyboard. System language is English (US). Problem appeared immediately after flashing, and I flashed 3 times! First time I tried with fresh ubuntu install but was the same, then i tried flashing android and then ubuntu again so after that problem was still there. After all that i tried flashing devel channel but i found it to pretty much buggy so i flashed again to stable and ofc problem with capitalization persisted. Might be that im the only one with problem, but i didn't do anything special, just simple install with: ubuntu-device-flash touch --channel=stable --bootstrap Can i check something else? Maybe some logs or what? I mean if there could be something interesting or specific.. This problem is nothing to worry about, but i find it rather annoying if im in rush with writing something because i often have to correct words. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1440539 Title: auto capitalization is capitalizing first two letters insted of one Status in ubuntu-keyboard package in Ubuntu: New Bug description: Nexus 4 owner here! I installed Ubuntu Touch stable channel (14.10 r17). So problem that i noticed is when auto capitalization is turned on it always capitalizes 2 letters instead only first one! No matter where, on login, on beginning of each sentence and everywhere where keyboard is used, and it does that every time. Im sorry if that's already reported or maybe its not a bug, but i couldn't find the solution so i decided to report it! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1440539/+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 1440539] [NEW] auto capitalization is capitalizing first two letters insted of one
Public bug reported: Nexus 4 owner here! I installed Ubuntu Touch stable channel (14.10 r17). So problem that i noticed is when auto capitalization is turned on it always capitalizes 2 letters instead only first one! No matter where, on login, on beginning of each sentence and everywhere where keyboard is used, and it does that every time. Im sorry if that's already reported or maybe its not a bug, but i couldn't find the solution so i decided to report it! ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1440539 Title: auto capitalization is capitalizing first two letters insted of one Status in ubuntu-keyboard package in Ubuntu: New Bug description: Nexus 4 owner here! I installed Ubuntu Touch stable channel (14.10 r17). So problem that i noticed is when auto capitalization is turned on it always capitalizes 2 letters instead only first one! No matter where, on login, on beginning of each sentence and everywhere where keyboard is used, and it does that every time. Im sorry if that's already reported or maybe its not a bug, but i couldn't find the solution so i decided to report it! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1440539/+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
