[Touch-packages] [Bug 1975875] Re: libgail-3-0 install blocked by "=" dependency
Sounds like you enabled the updates source and then disabled it, in which case it's a configuration issue ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gtk+3.0 (Ubuntu) Status: New => Invalid -- 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: Invalid 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 1974428] Re: Update to the current 1.36 stable version
The autopkgtest listed before worked on a retry -- 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/1974428 Title: Update to the current 1.36 stable version Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Jammy: Fix Committed Bug description: * Impact It's a stable update from upstream, the changes are listed in the NEWS https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS * Test Case Since it's an update with several fixes the testing should focus on a specific point but rather by validating that the testplan is green, https://wiki.ubuntu.com/NetworkManager/DistroTesting * Regression potential There are fixes around IPv6 handling, VPN connections and the hotspot feature, verify that those configurations are still working as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1974428/+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 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'
** Changed in: netplan.io (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951653 Title: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged' Status in netplan.io package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Confirmed Bug description: I have tried to tell netplan to let my ethernet device be managed by NetworkManager, so that I can then configure a pppoe connection on top of this device. This fails with: # nmcli c up netplan-wan Error: Connection activation failed: No suitable device found for this connection (device lo not available because device is strictly unmanaged). # I don't know why it mentions 'lo' in that message, but the wan interface is unmanaged (as are all devices on the system, but this one is supposed to be managed): # nmcli d status | grep wan wan ethernet unmanaged -- # After much searching, I've figured out that this comes from /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf: keyfile] unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma Even though I've told netplan to use the NM renderer for this device, the configuration emitted by netplan is insufficient to override this. Using the workaround from https://askubuntu.com/questions/71159/network-manager-says-device-not- managed (sudo touch /etc/NetworkManager/conf.d/10-globally-managed- devices.conf) doesn't work, but if I set NetworkManager as the toplevel renderer in /etc/netplan, /run/NetworkManager/conf.d/10-globally-managed-devices.conf is emitted, which evidently DOES work. But I only have one device that I want rendered by NM, so I shouldn't have to declare NM at the top level of the yaml with a lot of duplication in order to get this result. I would argue that the 10-globally-managed-devices.conf should not be there at all. But if it is going to be, then netplan needs to consistently override it whenever there is any use of the NetworkManager backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1951653/+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
@Kevin, we cherrypicked that patch in 22.04 before release https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3 -- 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 1976119] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*
** Changed in: at-spi2-core (Ubuntu) Importance: Undecided => Low -- 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 1976233] [NEW] "File has unexpected size" error on Focal ddebs repository
Public bug reported: Similar to https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865 but affecting Ubuntu 20.04 "Focal" Steps to reproduce: 1. Configure the debug repositories, like how it is explained in https://wiki.ubuntu.com/Debug%20Symbol%20Packages I ran these commands on a newly created Docker container (docker run --pull always --rm -ti ubuntu:20.04), but a typical bare metal installation should present the same issue: apt-get update ; apt-get install --yes gnupg apt-key adv \ --keyserver keyserver.ubuntu.com \ --recv-keys F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 source /etc/lsb-release tee /etc/apt/sources.list.d/ddebs.list >/dev/null
[Touch-packages] [Bug 1976233] Re: "File has unexpected size" error on Focal ddebs repository
This has been happening since at least as early as May 24th (i.e. last week) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1976233 Title: "File has unexpected size" error on Focal ddebs repository Status in apt package in Ubuntu: New Bug description: Similar to https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865 but affecting Ubuntu 20.04 "Focal" Steps to reproduce: 1. Configure the debug repositories, like how it is explained in https://wiki.ubuntu.com/Debug%20Symbol%20Packages I ran these commands on a newly created Docker container (docker run --pull always --rm -ti ubuntu:20.04), but a typical bare metal installation should present the same issue: apt-get update ; apt-get install --yes gnupg apt-key adv \ --keyserver keyserver.ubuntu.com \ --recv-keys F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 source /etc/lsb-release tee /etc/apt/sources.list.d/ddebs.list >/dev/null
[Touch-packages] [Bug 1975865] Re: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz
I just filed a similar bug affecting Ubuntu 20.04 Focal: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1976233 There seems to be a problem with a recent update of the ddebs repositories. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1975865 Title: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz Status in apt package in Ubuntu: New Bug description: When adding the debug repos, I am getting: E: Failed to fetch http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz File has unexpected size (795886 != 795487). Mirror sync in progress? [IP: 91.189.91.49 80] Hashes of expected file: - Filesize:795487 [weak] - SHA512:982169cbaaa6b0fe84e2cac755c140f52c578619beea451baa90234af2cfdaef90ac936eb7a7de24364ee860a6b021f852f11a87b7cd6dcb98923a248bc45a81 - SHA256:4a69b95e20ac09bb3de2d5e3c652b2c027bcfa4d6df9dea0a4aed16c805869e6 - SHA1:11dded397ab87e4fff81acf4aed6af18f8eee0b2 [weak] - MD5Sum:9045f9c8424cf15e897f682708f158b8 [weak] Release file created at: Thu, 26 May 2022 08:04:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. When I manually go to the repositories... many (all?) of the hashes listed in http://ddebs.ubuntu.com/dists/bionic-updates/Release do not match the files (e.g. http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz ) Note: I filed this against `apt` because `ubuntu-bug` forced me to specify a package and I didn't know any other way to file the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.14 Uname: Linux 5.16.18-1rodete2-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Thu May 26 18:36:21 2022 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865/+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 1959375] Re: [SRU] Please support group manipulation with "extrausers"
Hey Chris! Any reason you only released the focal one? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Bionic: Fix Committed Status in shadow source package in Focal: Fix Released Status in shadow source package in Impish: Won't Fix Status in shadow source package in Jammy: Fix Released Bug description: [Impact] * In order to use the microk8s snap in Ubuntu Core, one currently needs to be root. This is far from optimal, since normally (on desktop and server installations) this is not necessary. * This make it hard to provide consistent documentation on microk8s across all supported device, if we have to take the "sudo" command into account, and how file permissions for generated files might be affected. [Test Plan] The issue can be reproduced on Ubuntu Core 18, 20 and 22. The steps are as following (replace "" with the actual path of your Ubuntu Core image file: qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=,format=raw After configuring your account, connect to youd device via SSH: ssh @localhost -p 8022 And issue these commands sudo snap install microk8s --channel=latest/edge/stable # microk8s is going to eat up all your disk space, so stop it as soon # as the prompt comes back: sudo microk8s stop # Add your user to the microk8s group sudo usermod -G snap_microk8s $(whoami) The last command will fail unless this bug is fixed. If the bug is fixed, the command will succeed, and after logging out and in again, you can verify that you've been added to the snap_microk8s group by running the "groups" command. [Where problems could occur] * The patch only touches error code paths and adds a fallback mechanism in them. Therefore, "normal" operations, where these commands would have succeeded before, will not be affected at all. * In those cases when usermod fails because it failed to find or load the requested user/group, we reset the user/group database paths to our writable user/group databases, and retry the operation. Note that the path for our database is hardcoded in the program source, so the security risk seems contained. We do not add additional command-line parameters. [Other Info] Original bug description Currently doing something like: sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+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 1933491] Update Released
The verification of the Stable Release Update for kmod has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1933491 Title: kmod add zstd support Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Focal: Fix Released Status in kmod source package in Impish: Fix Released Status in kmod source package in Jammy: Fix Released Status in kmod package in Debian: New Bug description: [Impact] * To safe diskspace, upcoming devel series / hwe kernels may turn on zstd kernel module compression. Kmod since impish support zstd support. But in order to keep hwe kernels at parity, or allow inspecting jammy modules from focal host, it would be beneficial for kmod in focal to support zstd compressed modules. [Test Plan] * Pick any kernel module * Compress it with zstd: $ zstd *.ko * Check that modinfo can read it: $ modinfo *.ko.zst [Where problems could occur] * kmod will gain a new dependecy on libzstd1, however it should already be present, because dpkg in focal depends on libzstd1 already. * initramfs-tools already supports compressed modules, but in focal at the moment it does so in an inefficient manner (regresses bootspeed), this has been improved in https://launchpad.net/ubuntu/+source/initramfs-tools/0.140ubuntu8 and is yet to be SRUed into Focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1933491/+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 1933491] Re: kmod add zstd support
This bug was fixed in the package kmod - 27-1ubuntu2.1 --- kmod (27-1ubuntu2.1) focal; urgency=medium * Build with zstd compression and testsuite enabled. LP: #1933491 -- Dimitri John Ledkov Fri, 28 Jan 2022 14:49:50 + ** Changed in: kmod (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1933491 Title: kmod add zstd support Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Focal: Fix Released Status in kmod source package in Impish: Fix Released Status in kmod source package in Jammy: Fix Released Status in kmod package in Debian: New Bug description: [Impact] * To safe diskspace, upcoming devel series / hwe kernels may turn on zstd kernel module compression. Kmod since impish support zstd support. But in order to keep hwe kernels at parity, or allow inspecting jammy modules from focal host, it would be beneficial for kmod in focal to support zstd compressed modules. [Test Plan] * Pick any kernel module * Compress it with zstd: $ zstd *.ko * Check that modinfo can read it: $ modinfo *.ko.zst [Where problems could occur] * kmod will gain a new dependecy on libzstd1, however it should already be present, because dpkg in focal depends on libzstd1 already. * initramfs-tools already supports compressed modules, but in focal at the moment it does so in an inefficient manner (regresses bootspeed), this has been improved in https://launchpad.net/ubuntu/+source/initramfs-tools/0.140ubuntu8 and is yet to be SRUed into Focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1933491/+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 1851154] Re: libindicator ftbfs: G_ADD_PRIVATE
https://bugs.launchpad.net/ubuntu/+source/libindicator/16.10.0+18.04.20180321.1-0ubuntu3 ** Changed in: libindicator (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/1851154 Title: libindicator ftbfs: G_ADD_PRIVATE Status in libindicator package in Ubuntu: Fix Released Bug description: libindicator fails to build with this error: ../../libindicator/indicator-object.c: In function ‘indicator_object_init’: ../../libindicator/indicator-object.c:307:13: error: G_ADD_PRIVATE [-Werror] 307 | IndicatorObjectPrivate * priv = G_TYPE_INSTANCE_GET_PRIVATE (self, INDICATOR_OBJECT_TYPE, IndicatorObjectPrivate); | ^~~ g_type_class_add_private was deprecated See attached full build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1851154/+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 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)
as ~larsoner mentioned, those scripts contain some `return` but not in functions, so they may fail in some cases; you should change all `return` to `exit 0` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1907878 Title: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found) Status in ifupdown package in Ubuntu: Fix Released Bug description: Syslog error: nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir: not found I think it's because of this line: if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface <- this is interpreted as a 'mystatedir' command and fails interface=$IFACE if [ ! "$interface" ]; then Perhaps the intention was to 'export mystatedir statedir ...' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 1870829] Re: AptX and AptX HD unavailable as Bluetooth audio quality options
** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1870829 Title: AptX and AptX HD unavailable as Bluetooth audio quality options Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio package in Debian: Fix Released Bug description: Current situation: When one connects a Bluetooth audio device, at best one can choose between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback (A2DP Sink)". That is sad when the audio device supports AptX or AptX HD. Expected situation: One can select AptX or AptX HD as the Bluetooth audio output profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870829/+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 1956059] Re: Backport gspawn fixes to impish
Thank you for the report and the work, sorry that it didn't get triaged and acted on before though. It doesn't make sense to SRU to that serie anymore so closing the bug ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Low ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1956059 Title: Backport gspawn fixes to impish Status in glib2.0 package in Ubuntu: Fix Released Bug description: A few changes for gspawn landed in the 2.67 series that had some bugs which were later fixed and backported to 2.70 as seen in https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2394. These bugs are present in 2.68 as on impish, but that series won't see any more updates upstream. Currently this is causing a bug in the OSTree test suite as seen in https://github.com/ostreedev/ostree/issues/2495 with https://github.com/ostreedev/ostree/issues/2495#issuecomment-1000247260 confirming from glib's maintainer that these bugs are likely the issue. Attached is a debdiff with the 3 patches that were backported to 2.70. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1956059/+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 1887270] Re: brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset()
Is that still an issue in newer series? ** Changed in: glib2.0 (Ubuntu) Status: New => Incomplete ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1887270 Title: brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset() Status in brisk-menu package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Incomplete Bug description: Happened on MATE groovy live. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: mate-applet-brisk-menu 0.6.0-2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: MATE Date: Sun Jul 12 08:25:47 2020 ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200712) ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu//brisk-menu ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f07befc5d3e : mov(%r15,%rax,1),%r15 PC (0x7f07befc5d3e) ok source "(%r15,%rax,1)" (0x3ff8) not located in a known VMA region (needed readable region)! destination "%r15" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: brisk-menu StacktraceTop: g_slice_free_chain_with_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1887270/+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 1956388] Re: gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
The issue is fixed in the current version ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1956388 Title: gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 package in Debian: Fix Released Bug description: apt-get source -b libgtk-3-dev Reading package lists... Done Picking 'gtk+3.0' as source package instead of 'libgtk-3-dev' NOTICE: 'gtk+3.0' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/gnome-team/gtk3.git -b ubuntu/focal Please use: git clone https://salsa.debian.org/gnome-team/gtk3.git -b ubuntu/focal to retrieve the latest (possibly unreleased) updates to the package. Need to get 22.9 MB of source archives. Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (dsc) [3,639 B] Get:2 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (tar) [22.7 MB] Get:3 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (diff) [171 kB] Fetched 22.9 MB in 28s (815 kB/s) dpkg-source: info: extracting gtk+3.0 in gtk+3.0-3.24.20 dpkg-source: info: unpacking gtk+3.0_3.24.20.orig.tar.xz dpkg-source: info: unpacking gtk+3.0_3.24.20-0ubuntu1.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series ... dwz: debian/libgtk-3-0/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2404.16: DWARF compression not beneficial - old size 8243658 new size 8376050 dh_strip -O--buildsystem=autoconf debian/rules override_dh_makeshlibs make[1]: Entering directory '/root/gtk+3.0-3.24.20' sed: couldn't write 35 items to stdout: Broken pipe dh_makeshlibs -plibgtk-3-0 --add-udeb=libgtk-3-0-udeb -Xusr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0 -- -c4 dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libgtk-3-0/DEBIAN/symbols doesn't match completely debian/libgtk-3-0.symbols --- debian/libgtk-3-0.symbols (libgtk-3-0_3.24.20-0ubuntu1_amd64) +++ dpkg-gensymbolsrezAkY 2022-01-04 20:54:52.551202248 + @@ -1,5 +1,8 @@ libgdk-3.so.0 libgtk-3-0 #MINVER# * Build-Depends-Package: libgtk-3-dev + _gdk_get_resource@Base 3.24.20-0ubuntu1 + _gdk_register_resource@Base 3.24.20-0ubuntu1 + _gdk_unregister_resource@Base 3.24.20-0ubuntu1 gdk__private__@Base 3.16.2 gdk_add_option_entries_libgtk_only@Base 3.0.0 gdk_anchor_hints_get_type@Base 3.21.5 @@ -758,6 +761,9 @@ gdk_x11_xatom_to_atom@Base 3.0.0 gdk_x11_xatom_to_atom_for_display@Base 3.0.0 libgtk-3.so.0 libgtk-3-0 #MINVER# + _gtk_get_resource@Base 3.24.20-0ubuntu1 + _gtk_register_resource@Base 3.24.20-0ubuntu1 + _gtk_unregister_resource@Base 3.24.20-0ubuntu1 gtk_about_dialog_add_credit_section@Base 3.3.16 gtk_about_dialog_get_artists@Base 3.0.0 gtk_about_dialog_get_authors@Base 3.0.0 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:243: override_dh_makeshlibs] Error 2 make[1]: Leaving directory '/root/gtk+3.0-3.24.20' make: *** [debian/rules:135: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 W: Download is performed unsandboxed as root as file 'gtk+3.0_3.24.20-0ubuntu1.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) E: Build command 'cd gtk+3.0-3.24.20 && dpkg-buildpackage -b -uc' failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-dev (not installed) ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Uname: Linux 5.4.0-92-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jan 5 00:02:06 2022 InstallationDate: Installed on 2020-04-23 (621 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1956388/+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 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level
** Description changed: - openssl.cnf as provided misses some directive, which make it a bit - difficult to change security level, which since openssl 3 disables SHA1 - signatures. + [Impact] + + The OpenSSL 3.0 lead to a lot of broken setups. Some of them are + regressions, but others are simply broken due to the use of outdated + algorithms, such as SHA-1 signature on certificates. Changing the + security level is a common action to identify and work around such + cases, and as such the user should be able to change it easily in the + default config file. + + The fix is to partially revert our delta that ignored a Debian patch: + instead of ignoring the patch entirely, we modify it to only affect the + default configuration file, and in a way that matches our patchset. + Using this approach will allow us to pick up on Debian's changes more + easily during subsequent merges. + + [Test Plan] + + To easily check that the setting is taken into account, one can use + 'openssl ciphers -s' + + $ openssl ciphers -v -s | wc -l # Uses the default value + 30 + $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=2' | wc -l + 30 + $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=3' | wc -l + 24 + $ vim /etc/ssl/openssl.cf # edit the config file to bump the seclevel to 3 + $ openssl ciphers -v -s | wc -l # Uses the new value from the config file + 24 + + [Where problems could occur] + + The changes could break the overall configuration of OpenSSL! + + [Origin report] + openssl.cnf as provided misses some directive, which make it a bit difficult to change security level, which since openssl 3 disables SHA1 signatures. See also this Debian bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1010360 and the committed fix: https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4 Can you please sync this change in Ubuntu openssl? This way one should just add a single directive to change the security level. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1972056 Title: [openssl3] please sync openssl.cnf to ease changing security level Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Jammy: Confirmed Status in openssl source package in Kinetic: Confirmed Status in openssl package in Debian: Fix Released Bug description: [Impact] The OpenSSL 3.0 lead to a lot of broken setups. Some of them are regressions, but others are simply broken due to the use of outdated algorithms, such as SHA-1 signature on certificates. Changing the security level is a common action to identify and work around such cases, and as such the user should be able to change it easily in the default config file. The fix is to partially revert our delta that ignored a Debian patch: instead of ignoring the patch entirely, we modify it to only affect the default configuration file, and in a way that matches our patchset. Using this approach will allow us to pick up on Debian's changes more easily during subsequent merges. [Test Plan] To easily check that the setting is taken into account, one can use 'openssl ciphers -s' $ openssl ciphers -v -s | wc -l # Uses the default value 30 $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=2' | wc -l 30 $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=3' | wc -l 24 $ vim /etc/ssl/openssl.cf # edit the config file to bump the seclevel to 3 $ openssl ciphers -v -s | wc -l # Uses the new value from the config file 24 [Where problems could occur] The changes could break the overall configuration of OpenSSL! [Origin report] openssl.cnf as provided misses some directive, which make it a bit difficult to change security level, which since openssl 3 disables SHA1 signatures. See also this Debian bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1010360 and the committed fix: https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4 Can you please sync this change in Ubuntu openssl? This way one should just add a single directive to change the security level. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1972056/+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 1976255] [NEW] accountsservice ftbfs in the jammy release pocket
Public bug reported: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216054/buildlog_ubuntu-jammy- amd64.accountsservice_22.07.5-2ubuntu1_BUILDING.txt.gz Ok: 2 Expected Fail: 0 Fail: 10 Unexpected Pass:0 Skipped:0 Timeout:0 Full log written to /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt ==> meson-logs/testlog.txt <== Log of Meson test suite run on 2022-05-30T08:33:42.861398 Inherited environment: SCHROOT_GID=2501 DEB_HOST_MULTIARCH=x86_64-linux- gnu LC_ALL=C.UTF-8 DEB_HOST_GNU_SYSTEM=linux-gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_LDFLAGS_MAINT_APPEND=-Wl,--as- needed DEB_TARGET_ARCH_LIBC=gnu DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_BUILD_ARCH_BITS=64 DEB_BUILD_OPTIONS=parallel=4 DEB_HOST_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little DEB_BUILD_PROFILES=noudeb SOURCE_DATE_EPOCH=1645543676 V=1 DEB_HOST_ARCH_BITS=64 LANG=C.UTF-8 MAKEFLAGS='' SCHROOT_GROUP=buildd DEB_TARGET_ARCH=amd64 DEB_HOST_GNU_CPU=x86_64 DEB_BUILD_ARCH_LIBC=gnu MFLAGS='' DEB_TARGET_ARCH_BITS=64 DEB_BUILD_ARCH_CPU=amd64 SCHROOT_ALIAS_NAME=build-PACKAGEBUILD-23614463 DEB_HOST_ARCH_OS=linux SHELL=/bin/sh DEB_HOST_ARCH_CPU=amd64 SCHROOT_USER=buildd PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games DEB_BUILD_ARCH_ABI=base DEB_BUILD_ARCH=amd64 DEB_HOST_ARCH_LIBC=gnu SCHROOT_SESSION_ID=build-PACKAGEBUILD-23614463 DEB_TARGET_ARCH_CPU=amd64 DEB_HOST_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux LOGNAME=buildd DEB_TARGET_MULTIARCH=x86_64-linux-gnu DEB_BUILD_GNU_CPU=x86_64 DEB_TARGET_ARCH_OS=linux USER=buildd DEB_HOST_ARCH_ABI=base DEB_BUILD_MULTIARCH=x86_64-linux-gnu DEB_TARGET_GNU_TYPE=x86_64-linux-gnu DEB_TARGET_ARCH_ABI=base SCHROOT_UID=2001 SCHROOT_COMMAND='dpkg-buildpackage -us -uc -mLaunchpad Build Daemon -b -rfakeroot' DEB_TARGET_GNU_CPU=x86_64 APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/<>/debian/.debhelper/generated/_source/home DEB_RULES_REQUIRES_ROOT=binary-targets DEB_TARGET_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_ENDIAN=little TERM=unknown SCHROOT_CHROOT_NAME=build- PACKAGEBUILD-23614463 MAKELEVEL=1 DH_INTERNAL_BUILDFLAGS=1 ASFLAGS='' CFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat- lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security' CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' CXXFLAGS='-g -O2 -ffile-prefix- map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat- lto-objects -fstack-protector-strong -Wformat -Werror=format-security' DFLAGS=-frelease FCFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong' FFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong' GCJFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong' LDFLAGS='-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto -Wl,-z,relro -Wl,--as-needed' OBJCFLAGS='-g -O2 -ffile- prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format- security' OBJCXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong -Wformat -Werror=format-security' XDG_RUNTIME_DIR=/tmp/dh-xdg-rundir-JPi9I5rR MESON_TESTTHREADS=4 1/12 accountsservice:accounts-service+libaccountsservice+TestAccountsService / TestAccountsService.test_cache_user FAIL0.33s exit status 1 08:33:42 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice GI_TYPELIB_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice G_DEBUG=fatal-criticals G_MESSAGES_DEBUG=all MALLOC_PERTURB_=58 /usr/bin/python3 /<>/obj-x86_64-linux-gnu/../tests/test-libaccountsservice.py TestAccountsService.test_cache_user --- output --- test_cache_user (__main__.TestAccountsService) ... (process:11790): accountsservice-DEBUG: 08:33:43.062: Finding a graphical session for user 2001 (process:11790): accountsservice-DEBUG: 08:33:43.062: Failed to identify the current session (process:11790): accountsservice-DEBUG: 08:33:43.062: ActUserManager: seat unloaded, so trying to set loaded property (process:11790): accountsservice-DEBUG: 08:33:43.062: ActUserManager: Seat wouldn't load, so giving up on it and setting loaded property (process:11790): accountsservice-DEBUG: 08:33:43.062: ActUserManager: already loaded, so not setting loaded property (process:11790): accountsservice-DEBUG: 08:33:43.063: ActUserManager: Creating user 'user', 'I am User', 1 (process:11790): accountsservice-DEBUG: 08:33:43.063: ActUserManager: calling 'ListCachedUsers' (process:11790): accountsservic
[Touch-packages] [Bug 1976259] [NEW] librsvg ftbfs in the jammy release pocket
Public bug reported: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216345/buildlog_ubuntu- jammy-i386.librsvg_2.52.5+dfsg-3_BUILDING.txt.gz test url_resolver::tests::allows_relative ... ok failures: transform::tests::parses_transform_list stdout thread 'transform::tests::parses_transform_list' panicked at 'assertion failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9 transform::tests::parses_valid_transform stdout thread 'transform::tests::parses_valid_transform' panicked at 'assertion failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9 failures: transform::tests::parses_transform_list transform::tests::parses_valid_transform test result: FAILED. 254 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s error: test failed, to rerun pass '--lib' make[5]: *** [Makefile:1537: check-local] Error 101 ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs rls-jj-incoming ** Tags added: ftbfs rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1976259 Title: librsvg ftbfs in the jammy release pocket Status in librsvg package in Ubuntu: New Bug description: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216345/buildlog_ubuntu- jammy-i386.librsvg_2.52.5+dfsg-3_BUILDING.txt.gz test url_resolver::tests::allows_relative ... ok failures: transform::tests::parses_transform_list stdout thread 'transform::tests::parses_transform_list' panicked at 'assertion failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9 transform::tests::parses_valid_transform stdout thread 'transform::tests::parses_valid_transform' panicked at 'assertion failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9 failures: transform::tests::parses_transform_list transform::tests::parses_valid_transform test result: FAILED. 254 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s error: test failed, to rerun pass '--lib' make[5]: *** [Makefile:1537: check-local] Error 101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1976259/+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 1976258] [NEW] icu ftbfs in the jammy release pocket
Public bug reported: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy- amd64.icu_70.1-2_BUILDING.txt.gz [...] make[4]: Leaving directory '/<>/source/test/cintltst' - | *** FAILING TEST SUMMARY FOR: intltest TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest --- ALL TESTS SUMMARY: ok: testdata iotest cintltst = ERRS: intltest make[3]: *** [Makefile:91: check-recursive] Error 1 ** Affects: icu (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs rls-jj-incoming ** Tags added: ftbfs rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1976258 Title: icu ftbfs in the jammy release pocket Status in icu package in Ubuntu: New Bug description: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy- amd64.icu_70.1-2_BUILDING.txt.gz [...] make[4]: Leaving directory '/<>/source/test/cintltst' - | *** FAILING TEST SUMMARY FOR: intltest TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest --- ALL TESTS SUMMARY: ok: testdata iotest cintltst = ERRS: intltest make[3]: *** [Makefile:91: check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1976258/+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 1976255] Re: accountsservice ftbfs in the jammy release pocket
This was fixed via accountsservice 22.07.5-2ubuntu1.3 in jammy-updates. ** Changed in: accountsservice (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1976255 Title: accountsservice ftbfs in the jammy release pocket Status in accountsservice package in Ubuntu: Fix Released Bug description: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216054/buildlog_ubuntu-jammy- amd64.accountsservice_22.07.5-2ubuntu1_BUILDING.txt.gz Ok: 2 Expected Fail: 0 Fail: 10 Unexpected Pass:0 Skipped:0 Timeout:0 Full log written to /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt ==> meson-logs/testlog.txt <== Log of Meson test suite run on 2022-05-30T08:33:42.861398 Inherited environment: SCHROOT_GID=2501 DEB_HOST_MULTIARCH=x86_64-linux-gnu LC_ALL=C.UTF-8 DEB_HOST_GNU_SYSTEM=linux-gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_LDFLAGS_MAINT_APPEND=-Wl,--as-needed DEB_TARGET_ARCH_LIBC=gnu DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_BUILD_ARCH_BITS=64 DEB_BUILD_OPTIONS=parallel=4 DEB_HOST_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little DEB_BUILD_PROFILES=noudeb SOURCE_DATE_EPOCH=1645543676 V=1 DEB_HOST_ARCH_BITS=64 LANG=C.UTF-8 MAKEFLAGS='' SCHROOT_GROUP=buildd DEB_TARGET_ARCH=amd64 DEB_HOST_GNU_CPU=x86_64 DEB_BUILD_ARCH_LIBC=gnu MFLAGS='' DEB_TARGET_ARCH_BITS=64 DEB_BUILD_ARCH_CPU=amd64 SCHROOT_ALIAS_NAME=build-PACKAGEBUILD-23614463 DEB_HOST_ARCH_OS=linux SHELL=/bin/sh DEB_HOST_ARCH_CPU=amd64 SCHROOT_USER=buildd PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games DEB_BUILD_ARCH_ABI=base DEB_BUILD_ARCH=amd64 DEB_HOST_ARCH_LIBC=gnu SCHROOT_SESSION_ID=build-PACKAGEBUILD-23614463 DEB_TARGET_ARCH_CPU=amd64 DEB_HOST_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux LOGNAME=buildd DEB_TARGET_MULTIARCH=x86_64-linux-gnu DEB_BUILD_GNU_CPU=x86_64 DEB_TARGET_ARCH_OS=linux USER=buildd DEB_HOST_ARCH_ABI=base DEB_BUILD_MULTIARCH=x86_64-linux-gnu DEB_TARGET_GNU_TYPE=x86_64-linux- gnu DEB_TARGET_ARCH_ABI=base SCHROOT_UID=2001 SCHROOT_COMMAND='dpkg- buildpackage -us -uc -mLaunchpad Build Daemon -b -rfakeroot' DEB_TARGET_GNU_CPU=x86_64 APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/<>/debian/.debhelper/generated/_source/home DEB_RULES_REQUIRES_ROOT=binary-targets DEB_TARGET_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_ENDIAN=little TERM=unknown SCHROOT_CHROOT_NAME=build- PACKAGEBUILD-23614463 MAKELEVEL=1 DH_INTERNAL_BUILDFLAGS=1 ASFLAGS='' CFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat- lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security' CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' CXXFLAGS='-g -O2 -ffile-prefix- map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat- lto-objects -fstack-protector-strong -Wformat -Werror=format-security' DFLAGS=-frelease FCFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong' FFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong' GCJFLAGS='-g -O2 -ffile-prefix- map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector- strong' LDFLAGS='-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto -Wl,-z,relro -Wl,--as-needed' OBJCFLAGS='-g -O2 -ffile- prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format- security' OBJCXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong -Wformat -Werror=format-security' XDG_RUNTIME_DIR=/tmp/dh-xdg-rundir-JPi9I5rR MESON_TESTTHREADS=4 1/12 accountsservice:accounts-service+libaccountsservice+TestAccountsService / TestAccountsService.test_cache_user FAIL0.33s exit status 1 08:33:42 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice GI_TYPELIB_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice G_DEBUG=fatal-criticals G_MESSAGES_DEBUG=all MALLOC_PERTURB_=58 /usr/bin/python3 /<>/obj-x86_64-linux-gnu/../tests/test-libaccountsservice.py TestAccountsService.test_cache_user --- output --- test_cache_user (__main__.TestAccountsService) ... (process:11790): accountsservice-DEBUG: 08:33:43.062: Finding a graphical session for user 2001 (process:11790): accountsservice-DEBUG: 08:33:43.062: Failed to identify the current session (process:11790): ac
[Touch-packages] [Bug 1947588] Re: Infinite Loop in OpenSSL s_server
** Description changed: + [Impact] + + The TLS test server `openssl s_server` can very easily be led into an + infinite loop if configured with incompatible settings and used via + DTLS. This makes it harder to test one's TLS configuration. + + [Test plan] + + In one session: + $ openssl s_server -nocert -psk 01020304 -dtls1 + In parallel: + $ openssl s_client -dtls1 -psk 01020304 + + The server session will enter an infinite loop: + Using default temp DH parameters + ACCEPT + ERROR + 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: + ERROR + 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: + ERROR + ... etc... + + [Where problems could occur] + + The patch is fairly self-contained, so regressions should only occur in + the `openssl s_server` application, and not in the libssl or libcrypto + libraries. + However, the patch could break said server, which might be used in e.g. + autopkgtests. + + [Original report] Launching openssl s_server as follows: $ openssl s_server -nocert -psk 01020304 -dtls1 And using openssl s_client to connect to it like this: $ openssl s_client -dtls1 -psk 01020304 Results in s_server entering an infinite loop: - Using default temp DH parameters ACCEPT ERROR 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: ERROR 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: ERROR ...and so on... I have confirmed that upstream OpenSSL does not have this issue in a default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug with these commands (https://github.com/openssl/openssl/issues/16707) and it was while working on the fix for that issue (https://github.com/openssl/openssl/pull/16838) that I noticed this problem in the Ubuntu packages. $ lsb_release -rd - Description: Ubuntu 21.04 - Release: 21.04 + Description: Ubuntu 21.04 + Release: 21.04 $ apt-cache policy openssl openssl: Installed: 1.1.1j-1ubuntu3.5 Candidate: 1.1.1j-1ubuntu3.5 Version table: *** 1.1.1j-1ubuntu3.5 500 500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status 1.1.1j-1ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages $ openssl version -a - OpenSSL 1.1.1j 16 Feb 2021 + OpenSSL 1.1.1j 16 Feb 2021 built on: Mon Aug 23 17:02:39 2021 UTC platform: debian-amd64 - options: bn(64,64) rc4(16x,int) des(int) blowfish(ptr) + options: bn(64,64) rc4(16x,int) des(int) blowfish(ptr) compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 OPENSSLDIR: "/usr/lib/ssl" ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1" Seeding source: os-specific -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1947588 Title: Infinite Loop in OpenSSL s_server Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Focal: Confirmed Status in openssl source package in Impish: Confirmed Status in openssl source package in Jammy: Confirmed Bug description: [Impact] The TLS test server `openssl s_server` can very easily be led into an infinite loop if configured with incompatible settings and used via DTLS. This makes it harder to test one's TLS configuration. [Test plan] In one session: $ openssl s_server -nocert -psk 01020304 -dtls1 In parallel: $ openssl s_client -dtls1 -psk 01020304 The server session will enter an infinite loop: Using default temp DH parameters ACCEPT ERROR 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: ERROR 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: ERROR ... etc... [Where problems could occur] The patch is fairly self-contained, so regressions should only occur in the `openssl s_server` application, and not in the libssl or libcrypto libraries. However, the patch could brea
[Touch-packages] [Bug 1973629] [NEW] Wifi hotspot not configured correctly on restart
You have been subscribed to a public bug: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) ** Affects: network-manager (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug jammy -- Wifi hotspot not configured correctly on restart https://bugs.launchpad.net/bugs/1973629 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager 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 1973629] Re: Wifi hotspot not configured correctly on restart
Thank you for your bug report. If the status is wrong at system start then the problem is probably due to network-manager itself. Could you trigger the bug and then when the system is in the buggy state do $ apport-collect 1973629 The issue is probably also worth reporting upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Package changed: gnome-control-center (Ubuntu) => network-manager (Ubuntu) ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1974428] Re: Update to the current 1.36 stable version
1.36.6-0ubuntu1 is working as expected testing wifi, VPN, hotspot and standard desktop options. The autopkgtests showed no problem and we didn't get report of new problems. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1974428 Title: Update to the current 1.36 stable version Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Jammy: Fix Committed Bug description: * Impact It's a stable update from upstream, the changes are listed in the NEWS https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS * Test Case Since it's an update with several fixes the testing should focus on a specific point but rather by validating that the testplan is green, https://wiki.ubuntu.com/NetworkManager/DistroTesting * Regression potential There are fixes around IPv6 handling, VPN connections and the hotspot feature, verify that those configurations are still working as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1974428/+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 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
** Changed in: software-properties (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: New Status in software-properties package in Ubuntu: Fix Committed Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center software-properties-gtk 0.99.22 3) What you expected to happen No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. 4) What happened instead It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+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 1973629] Re: Wifi hotspot not configured correctly on restart
apport information ** Tags added: apport-collected wayland-session ** Description changed: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-12-08 (173 days ago) + InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + IpRoute: + default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 + 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 + 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 + 169.254.0.0/16 dev enp2s0 scope link metric 1000 + 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 + NonfreeKernelModules: nvidia_modeset nvidia + Package: network-manager 1.36.4-2ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 + Tags: wayland-session jammy + Uname: Linux 5.15.0-33-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) + UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers + _MarkForUpload: True + nmcli-nm: + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.36.4 connected started full enabled enabled enabled enabled enabled + no_proxy: localhost,127.0.0.0/8,::1 ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593875/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri
[Touch-packages] [Bug 1973629] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593876/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593877/+files/IpAddr.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593878/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] NetDevice.docker0.txt
apport information ** Attachment added: "NetDevice.docker0.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593879/+files/NetDevice.docker0.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593881/+files/NetDevice.lo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] NetDevice.veth2665f1e.txt
apport information ** Attachment added: "NetDevice.veth2665f1e.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593882/+files/NetDevice.veth2665f1e.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] NetDevice.enp2s0.txt
apport information ** Attachment added: "NetDevice.enp2s0.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593880/+files/NetDevice.enp2s0.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] NetDevice.veth3b712b0.txt
apport information ** Attachment added: "NetDevice.veth3b712b0.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593883/+files/NetDevice.veth3b712b0.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] NetDevice.veth542edda.txt
apport information ** Attachment added: "NetDevice.veth542edda.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593884/+files/NetDevice.veth542edda.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593888/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593892/+files/nmcli-con.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593893/+files/nmcli-dev.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593886/+files/NetworkManager.conf.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593887/+files/PciNetwork.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] NetDevice.wlp3s0.txt
apport information ** Attachment added: "NetDevice.wlp3s0.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593885/+files/NetDevice.wlp3s0.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593889/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593890/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1973629] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593891/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1964763] Re: QtChooser doesn't support qt6
There also needs to be a default.conf, to avoid having to set QT_SELECT -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtchooser in Ubuntu. https://bugs.launchpad.net/bugs/1964763 Title: QtChooser doesn't support qt6 Status in qtchooser package in Ubuntu: Confirmed Bug description: qtchooser doesn't run qt6 applications because it doesn't have a qt6.conf/6.conf file yet. In order to work, it must have two files `/usr/lib/x86_64-linux- gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux- gnu/qtchooser/6.conf` with this content: ``` /usr/lib/qt6/bin /usr/lib/x86_64-linux-gnu ``` Without it, lupdate, lrelease, and any other qt6 tools show this error: `could not find a Qt installation of ''` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1964763/+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
Re: [Touch-packages] [Bug 1975865] Re: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz
Yep, this affects all versions. FWIW, the ddebs repository seems to break like this every 1-2 years and after reporting it, it's usually cleaned up in a week or two. On Mon, May 30, 2022 at 2:31 AM Juan Navarro <1975...@bugs.launchpad.net> wrote: > I just filed a similar bug affecting Ubuntu 20.04 Focal: > https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1976233 > > There seems to be a problem with a recent update of the ddebs > repositories. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1975865 > > Title: > Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic- > updates/main/binary-amd64/Packages.gz > > Status in apt package in Ubuntu: > New > > Bug description: > When adding the debug repos, I am getting: > > E: Failed to fetch > http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz > File has unexpected size (795886 != 795487). Mirror sync in progress? [IP: > 91.189.91.49 80] > Hashes of expected file: > - Filesize:795487 [weak] > - > SHA512:982169cbaaa6b0fe84e2cac755c140f52c578619beea451baa90234af2cfdaef90ac936eb7a7de24364ee860a6b021f852f11a87b7cd6dcb98923a248bc45a81 > - > SHA256:4a69b95e20ac09bb3de2d5e3c652b2c027bcfa4d6df9dea0a4aed16c805869e6 > - SHA1:11dded397ab87e4fff81acf4aed6af18f8eee0b2 [weak] > - MD5Sum:9045f9c8424cf15e897f682708f158b8 [weak] > Release file created at: Thu, 26 May 2022 08:04:16 + > E: Some index files failed to download. They have been ignored, or old > ones used instead. > > When I manually go to the repositories... many (all?) of the hashes > listed in http://ddebs.ubuntu.com/dists/bionic-updates/Release do not > match the files (e.g. http://ddebs.ubuntu.com/dists/bionic- > updates/main/binary-amd64/Packages.gz ) > > Note: I filed this against `apt` because `ubuntu-bug` forced me to > specify a package and I didn't know any other way to file the bug. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: apt 1.6.14 > Uname: Linux 5.16.18-1rodete2-amd64 x86_64 > ApportVersion: 2.20.9-0ubuntu7.28 > Architecture: amd64 > Date: Thu May 26 18:36:21 2022 > ProcEnviron: >TERM=xterm >PATH=(custom, no user) > SourcePackage: apt > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1975865 Title: Hash and size mismatch with http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz Status in apt package in Ubuntu: New Bug description: When adding the debug repos, I am getting: E: Failed to fetch http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-amd64/Packages.gz File has unexpected size (795886 != 795487). Mirror sync in progress? [IP: 91.189.91.49 80] Hashes of expected file: - Filesize:795487 [weak] - SHA512:982169cbaaa6b0fe84e2cac755c140f52c578619beea451baa90234af2cfdaef90ac936eb7a7de24364ee860a6b021f852f11a87b7cd6dcb98923a248bc45a81 - SHA256:4a69b95e20ac09bb3de2d5e3c652b2c027bcfa4d6df9dea0a4aed16c805869e6 - SHA1:11dded397ab87e4fff81acf4aed6af18f8eee0b2 [weak] - MD5Sum:9045f9c8424cf15e897f682708f158b8 [weak] Release file created at: Thu, 26 May 2022 08:04:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. When I manually go to the repositories... many (all?) of the hashes listed in http://ddebs.ubuntu.com/dists/bionic-updates/Release do not match the files (e.g. http://ddebs.ubuntu.com/dists/bionic- updates/main/binary-amd64/Packages.gz ) Note: I filed this against `apt` because `ubuntu-bug` forced me to specify a package and I didn't know any other way to file the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.14 Uname: Linux 5.16.18-1rodete2-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 Date: Thu May 26 18:36:21 2022 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1968876] Re: ssh-agent: Error connecting to agent: Connection refused
** Tags added: jammy rpi -- 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/1968876 Title: ssh-agent: Error connecting to agent: Connection refused Status in openssh package in Ubuntu: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh 1:8.9p1-3 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: MATE raspberry pi 4. The keys are added, but for example, when cloning a repository via ssh, the ssh agent crashes, restarting does not help, the repository is not cloned. When launch the command ssh-add -L Error connecting to agent: Connection refused. I rolled back to the package version 1: 8.8p1-1 and everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968876/+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 1973629] Re: Wifi hotspot not configured correctly on restart
thanks ** Changed in: network-manager (Ubuntu) Status: Incomplete => New -- 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/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: New Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+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 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
** Also affects: lvm2 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: lvm2 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: lvm2 (Ubuntu) Importance: Low => Undecided ** Changed in: lvm2 (Ubuntu Focal) Status: New => In Progress ** Changed in: lvm2 (Ubuntu Focal) Importance: Undecided => Low ** Changed in: lvm2 (Ubuntu Focal) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Tags added: sts-sponsor-mfo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: In Progress Bug description: sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.0-17-generic Found initrd image: /boot/initrd.img-5.0.0-17-generic Found linux image: /boot/vmlinuz-5.0.0-16-generic Found initrd image: /boot/initrd.img-5.0.0-16-generic /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Adding boot menu entry for EFI firmware configuration done -- lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda8:00 3.7T 0 disk ├─sda1 8:10 512M 0 part /boot/efi ├─sda2 8:20 732M 0 part /boot └─sda3 8:30 3.7T 0 part └─sda3_crypt 253:00 3.7T 0 crypt ├─kubuntu--vg-swap_1 253:10 976M 0 lvm [SWAP] └─kubuntu--vg-root 253:20 3.7T 0 lvm / sdb8:16 0 3.7T 0 disk └─sdb1 8:17 0 3.7T 0 part sdg8:96 0 7.3T 0 disk └─sdg1 8:97 0 7.3T 0 part /media/scott/8TB Ext Drive sr0 11:01 15.7G 0 rom -- cat /etc/default/grub GRUB_DEFAULT=0 GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on" GRUB_CMDLINE_LINUX="" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2-common 2.02+dfsg1-12ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jun 25 15:05:29 2019 InstallationDate: Installed on 2019-06-14 (10 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190614) SourcePacka
[Touch-packages] [Bug 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot
** This bug is no longer a duplicate of bug 1969162 bad interaction between snapd and update-notifier when snapd package is being upgraded -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1968845 Title: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot Status in dbus package in Ubuntu: Incomplete Bug description: Upgrading on a virtual machine from 20.04 to 22.04. I have had this happen twice now, I got one upgrade done without this bug. Basically the package installation stops at dbus package asking for a reboot as it was unable to upgrade as dbus-daemon was running. And rebooting at this stage obviously will cause a non-functioning system. Added a screenshot of the upgrade window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
Setup:
--
Add '/dev/sda' from the host to a Focal LXD container:
$ lxc launch ubuntu:focal 'focal-container'
$ lxc config device add 'focal-container' 'lxc-dev-sda' unix-block
source='/dev/sda' path='/dev/sda'
Device:
---
$ grep ^ /sys/block/sda/{removable,device/{vendor,model,rev}}
/sys/block/sda/removable:1
/sys/block/sda/device/vendor:Generic-
/sys/block/sda/device/model:SD/MMC
/sys/block/sda/device/rev:1.00
Original:
---
Error messages:
$ sudo vgs
/dev/sda: open failed: No medium found
/dev/sda: open failed: No medium found
$ echo $?
0
NOTE syscalls/error codes for /dev/sda:
$ sudo strace -f -e openat vgs 2>&1 | grep /dev/sda
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1
ENOMEDIUM (No medium found)
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No
medium found)
/dev/sda: open failed: No medium found
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1
ENOMEDIUM (No medium found)
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No
medium found)
/dev/sda: open failed: No medium found
Patched:
---
No messages:
$ sudo vgs
$ echo $?
0
SAME syscalls/error codes for /dev/sda:
$ sudo strace -f -e openat vgs 2>&1 | grep /dev/sda
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1
ENOMEDIUM (No medium found)
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No
medium found)
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1
ENOMEDIUM (No medium found)
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No
medium found)
** Description changed:
+ [Impact]
+
+ * `update-grub` (actually `vgs`) complains about
+'No medium found' on systems with card readers
+that have no card in.
+
+ * This may confuse users who aren't sure whether
+it means problems occurred with the bootloader,
+and concern their ability to safely boot again.
+
+ * The workaround is to add a filter to LVM config,
+but this might be hard to find and error prone.
+(And not even seem relate to `update-grub` at
+all, specially on non-LVM storage layouts.)
+
+ [Test Plan]
+
+ * Run `vgs` on a system with a card reader
+and check for 'No medium found' messages.
+
+ [Where problems could occur]
+
+ * The patch changes syscall error reporting on the
+'scan' path, so problems could occur when listing
+LVM resources in block devices (e.g., list volume
+groups with `vgs`).
+
+ * There's little to no changes upstream on this area,
+and the change is present in Jammy; both help with
+a lower chance of regression.
+
+ [Info]
+
+ * This upload is being staged (`block-proposed-focal`)
+as it's just a cosmetic change, but affects `lvm2`,
+which is present in so many systems, triggering a
+lot of upgrades/boot risk (in case something else
+broke and this upgrade could reveal it indirectly).
+
+ * So, it will probably only be released once a more
+serious issue has to be fixed in `lvm2`.
+
+ [Original Bug Description]
+
sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: open failed: No medium found
- /dev/sdd: open failed: No medium found
- /dev/sde: open failed: No medium found
- /dev/sdf: open failed: No medium found
- /dev/sdc: o
[Touch-packages] [Bug 1973629] Re: Wifi hotspot not configured correctly on restart
I have also reported the issue upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1016 ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1016 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1016 ** Description changed: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). - The expectation is that the hotpot to be fully functional on startup + The expectation is that the hotspot is fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. - Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: - default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 - 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 - 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 - 169.254.0.0/16 dev enp2s0 scope link metric 1000 - 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 + default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 + 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 + 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 + 169.254.0.0/16 dev enp2s0 scope link metric 1000 + 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.36.4 connected started full enabled enabled enabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 -- 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/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: New Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotspot is fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_6
[Touch-packages] [Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
** Description changed: [Impact] * `update-grub` (actually `vgs`) complains about 'No medium found' on systems with card readers that have no card in. * This may confuse users who aren't sure whether it means problems occurred with the bootloader, and concern their ability to safely boot again. * The workaround is to add a filter to LVM config, but this might be hard to find and error prone. (And not even seem relate to `update-grub` at all, specially on non-LVM storage layouts.) -[See comment #16] + [See comment #16] [Test Plan] * Run `vgs` on a system with a card reader and check for 'No medium found' messages. - * Run `strace -f -e openat vgs` to confirm -system calls/error codes have no changes. + * Run `strace -f -e openat vgs` to confirm + system calls/error codes have no changes. - * [See comment #20] + * [See comment #20] [Where problems could occur] * The patch changes syscall error reporting on the 'scan' path, so problems could occur when listing LVM resources in block devices (e.g., list volume groups with `vgs`). * There's little to no changes upstream on this area, and the change is present in Jammy; both help with a lower chance of regression. - [Info] + [Other Info] - * This upload is being staged (`block-proposed-focal`) + * `block-proposed-focal`: The upload is being staged as it's just a cosmetic change, but affects `lvm2`, which is present in so many systems, triggering a lot of upgrades/boot risk (in case something else broke and this upgrade could reveal it indirectly). * So, it will probably only be released once a more serious issue has to be fixed in `lvm2`. + + * Scope: Jammy has the fix, and Impish will EOL soon. [Original Bug Description] sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.0-17-generic Found initrd image: /boot/initrd.img-5.0.0-17-generic Found linux image: /boot/vmlinuz-5.0.0-16-generic Found initrd image: /boot/initrd.img-5.0.0-16-generic /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Adding boot menu entry for EFI firmware configuration done -- lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda8:00 3.7T 0 disk ├─sda1 8:10 512M 0 part /boot/efi ├─sda2 8:20 732M 0 part /boot └─sda3 8:30 3.7T 0 part └─sda3_crypt 253:00 3.7T 0 crypt ├─kubuntu--vg-swap_1 253:10 976M 0 lvm [SWAP] └─kubuntu--vg-roo
[Touch-packages] [Bug 1976302] [NEW] software-properties Additional Drivers tab informational text enhancement
Public bug reported: The Kubuntu installation process offers this check-box on the second screen: "Install third-party software for graphics and Wi-Fi hardware, Flash, MP3 and other media" box while installing Kubuntu as another form of manual installation." If you check that box, your video drivers are handled for you by a collaboration between Ubuntu and NVIDIA. The "Additional Drivers" tab in Software Sources then displays these messages when you open it: * "This device is using a manually-installed driver." * "Continue using a manually installed driver" * "No proprietary drivers are in use." It wasn't obvious to me that "manually-installed" included those of us who checked the little check-box during the installation of the operating system to have our video drivers automatically installed and managed by Ubuntu and NVIDIA. I would like to suggest that the first two messages in the "Additional Drivers" tab get changed to something like this to make it obvious that they include us: * "This device is using a manually-installed or third-party driver." * "Continue using a manually-installed or third-party driver" Or if you'd like to word it differently: * "This device is using a manually-installed or automatically-installed driver." * "Continue using a manually-installed or automatically-installed driver" ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "The two places in which the text appears in the "Additional "Drivers" tab are marked here with arrows." https://bugs.launchpad.net/bugs/1976302/+attachment/5593898/+files/AdditionalDriversTab.png -- 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/1976302 Title: software-properties Additional Drivers tab informational text enhancement Status in software-properties package in Ubuntu: New Bug description: The Kubuntu installation process offers this check-box on the second screen: "Install third-party software for graphics and Wi-Fi hardware, Flash, MP3 and other media" box while installing Kubuntu as another form of manual installation." If you check that box, your video drivers are handled for you by a collaboration between Ubuntu and NVIDIA. The "Additional Drivers" tab in Software Sources then displays these messages when you open it: * "This device is using a manually-installed driver." * "Continue using a manually installed driver" * "No proprietary drivers are in use." It wasn't obvious to me that "manually-installed" included those of us who checked the little check-box during the installation of the operating system to have our video drivers automatically installed and managed by Ubuntu and NVIDIA. I would like to suggest that the first two messages in the "Additional Drivers" tab get changed to something like this to make it obvious that they include us: * "This device is using a manually-installed or third-party driver." * "Continue using a manually-installed or third-party driver" Or if you'd like to word it differently: * "This device is using a manually-installed or automatically-installed driver." * "Continue using a manually-installed or automatically-installed driver" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1976302/+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 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
Uploaded to Focal, and tagged block-proposed-focal. Attaching slightly modified debdiff (local build version), for users who want to build lvm2 before a SRU is released. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: In Progress Bug description: [Impact] * `update-grub` (actually `vgs`) complains about 'No medium found' on systems with card readers that have no card in. * This may confuse users who aren't sure whether it means problems occurred with the bootloader, and concern their ability to safely boot again. * The workaround is to add a filter to LVM config, but this might be hard to find and error prone. (And not even seem relate to `update-grub` at all, specially on non-LVM storage layouts.) [See comment #16] * The fix replaces calls to `dev_open_readonly()` with `dev_open_readonly_quiet()` in scan path, where such errors are not a problem. [Test Plan] * Run `vgs` on a system with a card reader and check for 'No medium found' messages. * Run `strace -f -e openat vgs` to confirm system calls/error codes have no changes. * [See comment #20] [Where problems could occur] * The patch changes syscall error reporting on the 'scan' path, so problems could occur when listing LVM resources in block devices (e.g., list volume groups with `vgs`). * There's little to no changes upstream on this area, and the change is present in Jammy; both help with a lower chance of regression. [Other Info] * `block-proposed-focal`: The upload is being staged as it's just a cosmetic change, but affects `lvm2`, which is present in so many systems, triggering a lot of upgrades/boot risk (in case something else broke and this upgrade could reveal it indirectly). * So, it will probably only be released once a more serious issue has to be fixed in `lvm2`. * Scope: Jammy has the fix, and Impish will EOL soon. [Original Bug Description] sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.0-17-generic Found initrd image: /boot/initrd.img-5.0.0-17-generic Found linux image: /boot/vmlinuz-5.0.0-16-generic Found initrd image: /boot/initrd.img-5.0.0-16-generic /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Adding boot menu entry for EFI firmware configuration done -- lsblk
[Touch-packages] [Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
** Patch added: "lp1834250_lvm2_focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1834250/+attachment/5593897/+files/lp1834250_lvm2_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: In Progress Bug description: [Impact] * `update-grub` (actually `vgs`) complains about 'No medium found' on systems with card readers that have no card in. * This may confuse users who aren't sure whether it means problems occurred with the bootloader, and concern their ability to safely boot again. * The workaround is to add a filter to LVM config, but this might be hard to find and error prone. (And not even seem relate to `update-grub` at all, specially on non-LVM storage layouts.) [See comment #16] * The fix replaces calls to `dev_open_readonly()` with `dev_open_readonly_quiet()` in scan path, where such errors are not a problem. [Test Plan] * Run `vgs` on a system with a card reader and check for 'No medium found' messages. * Run `strace -f -e openat vgs` to confirm system calls/error codes have no changes. * [See comment #20] [Where problems could occur] * The patch changes syscall error reporting on the 'scan' path, so problems could occur when listing LVM resources in block devices (e.g., list volume groups with `vgs`). * There's little to no changes upstream on this area, and the change is present in Jammy; both help with a lower chance of regression. [Other Info] * `block-proposed-focal`: The upload is being staged as it's just a cosmetic change, but affects `lvm2`, which is present in so many systems, triggering a lot of upgrades/boot risk (in case something else broke and this upgrade could reveal it indirectly). * So, it will probably only be released once a more serious issue has to be fixed in `lvm2`. * Scope: Jammy has the fix, and Impish will EOL soon. [Original Bug Description] sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.0-17-generic Found initrd image: /boot/initrd.img-5.0.0-17-generic Found linux image: /boot/vmlinuz-5.0.0-16-generic Found initrd image: /boot/initrd.img-5.0.0-16-generic /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Adding boot menu entry for EFI firmware configuration done -- lsblk NAME
[Touch-packages] [Bug 1973134] Re: Gnome 42 lock screen issue RX6500XT
** Summary changed: - Ubuntu 22.04 lock screen issue RX6500XT + Gnome 42 lock screen issue RX6500XT ** Description changed: - Hi, I have a problem with lock screen function with Ubuntu 22.04. When I - activate this feature, the system hangs and cannot be restored. You must - turn off/on PC to restore session. I suppose that this issue is - connected with AMD Video card RX6500XT and bad video driver which is - default for the system AMD® Beige_goby, because with other video cards - like RX5500XT, 550 and Nvidia working well. Is there any solution to fix - this? + Hi, I have a problem with lock screen function with Ubuntu 22.04/Fedora + 36. When I activate this feature, the system hangs and cannot be + restored. You must turn off/on PC to restore session. I suppose that + this issue is connected with AMD Video card RX6500XT and bad video + driver which is default for the system AMD® Beige_goby, because with + other video cards like RX5500XT, 550 and Nvidia working well. Is there + any solution to fix this? ** Package changed: vim (Ubuntu) => ubuntu ** Description changed: - Hi, I have a problem with lock screen function with Ubuntu 22.04/Fedora - 36. When I activate this feature, the system hangs and cannot be - restored. You must turn off/on PC to restore session. I suppose that - this issue is connected with AMD Video card RX6500XT and bad video - driver which is default for the system AMD® Beige_goby, because with - other video cards like RX5500XT, 550 and Nvidia working well. Is there - any solution to fix this? + Hi, I have a problem with lock screen and idle functions with Ubuntu + 22.04/Fedora 36. When I activate this feature, the system hangs and + cannot be restored. You must turn off/on PC to restore session. I + suppose that this issue is connected with AMD Video card RX6500XT and + bad video driver which is default for the system AMD® Beige_goby, + because with other video cards like RX5500XT, 550 and Nvidia working + well. Is there any solution to fix this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1973134 Title: Gnome 42 lock screen issue RX6500XT Status in Ubuntu: New Bug description: Hi, I have a problem with lock screen and idle functions with Ubuntu 22.04/Fedora 36. When I activate this feature, the system hangs and cannot be restored. You must turn off/on PC to restore session. I suppose that this issue is connected with AMD Video card RX6500XT and bad video driver which is default for the system AMD® Beige_goby, because with other video cards like RX5500XT, 550 and Nvidia working well. Is there any solution to fix this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1973134/+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 1976306] [NEW] package grub-common 2.04-1ubuntu26.13 failed to install/upgrade: installed grub-common package post-installation script subprocess returned error exit status 1
Public bug reported: running apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub-common 2.04-1ubuntu26.13 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: libgtksourceview-3.0-common:amd64: Install libgtksourceview-3.0-1:amd64: Install gir1.2-gtksource-3.0:amd64: Install meld:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 30 15:16:53 2022 DpkgHistoryLog: Start-Date: 2022-05-30 15:16:23 Commandline: packagekit role='install-packages' Requested-By: sgbeamer (1000) Install: libgtksourceview-3.0-common:amd64 (3.24.11-2, automatic), gir1.2-gtksource-3.0:amd64 (3.24.11-2, automatic), meld:amd64 (3.20.2-1ubuntu1), libgtksourceview-3.0-1:amd64 (3.24.11-2, automatic) ErrorMessage: installed grub-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-08-08 (660 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcCmdLine: BOOT_IMAGE=/BOOT/ubuntu_yw61q6@/vmlinuz-5.11.0-43-generic root=ZFS=rpool/ROOT/ubuntu_yw61q6 ro quiet splash vt.handoff=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 grub-common 2.04-1ubuntu26.13 failed to install/upgrade: installed grub-common package post-installation script subprocess returned error exit status 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/1976306 Title: package grub-common 2.04-1ubuntu26.13 failed to install/upgrade: installed grub-common package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: running apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub-common 2.04-1ubuntu26.13 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: libgtksourceview-3.0-common:amd64: Install libgtksourceview-3.0-1:amd64: Install gir1.2-gtksource-3.0:amd64: Install meld:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 30 15:16:53 2022 DpkgHistoryLog: Start-Date: 2022-05-30 15:16:23 Commandline: packagekit role='install-packages' Requested-By: sgbeamer (1000) Install: libgtksourceview-3.0-common:amd64 (3.24.11-2, automatic), gir1.2-gtksource-3.0:amd64 (3.24.11-2, automatic), meld:amd64 (3.20.2-1ubuntu1), libgtksourceview-3.0-1:amd64 (3.24.11-2, automatic) ErrorMessage: installed grub-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-08-08 (660 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcCmdLine: BOOT_IMAGE=/BOOT/ubuntu_yw61q6@/vmlinuz-5.11.0-43-generic root=ZFS=rpool/ROOT/ubuntu_yw61q6 ro quiet splash vt.handoff=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 grub-common 2.04-1ubuntu26.13 failed to install/upgrade: installed grub-common package post-installation script subprocess returned error exit status 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/1976306/+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
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- 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: Invalid 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 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Jammy) Milestone: None => ubuntu-22.04.1 -- 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/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: New Status in software-properties package in Ubuntu: Fix Committed Status in software-properties source package in Jammy: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center software-properties-gtk 0.99.22 3) What you expected to happen No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. 4) What happened instead It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+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 1976313] [NEW] GPG Key Expired
Public bug reported: I get the following error when trying to run `sudo apt update`: W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ddebs.ubuntu.com focal-updates Release: The following signatures were invalid: BADSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) W: Failed to fetch http://ddebs.ubuntu.com/dists/focal-updates/Release.gpg The following signatures were invalid: BADSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) W: Some index files failed to download. They have been ignored, or old ones used instead. I'm using Ubuntu 20.04.4 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-dbgsym-keyring 2020.02.11.4 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 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue May 31 00:32:43 2022 Dependencies: InstallationDate: Installed on 2020-05-11 (749 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-keyring (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 ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1976313 Title: GPG Key Expired Status in ubuntu-keyring package in Ubuntu: New Bug description: I get the following error when trying to run `sudo apt update`: W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ddebs.ubuntu.com focal-updates Release: The following signatures were invalid: BADSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) W: Failed to fetch http://ddebs.ubuntu.com/dists/focal-updates/Release.gpg The following signatures were invalid: BADSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) W: Some index files failed to download. They have been ignored, or old ones used instead. I'm using Ubuntu 20.04.4 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-dbgsym-keyring 2020.02.11.4 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 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue May 31 00:32:43 2022 Dependencies: InstallationDate: Installed on 2020-05-11 (749 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1976313/+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 1842320] Re: Out of Memory on boot with 5.2.0 kernel
the problem seems to me that memory allocation issue with higher resolution monitor. When issue happening, the grub shell not able to read some files (depends on current memory usage). For instance, I create 20M, 30M, 40M, 50M ... 80M, 90M, 100M, 101M, 102M ... 110M, 120M, 130M, etc... files and try to read them in grub shell. The "ls -al" only list the part of files. sometimes: "20M, 30M, 40M, 50M ... 80M, 90M, 100M, 101M, 102M" sometimes: "20M, 30M, 40M, 50M ... 80M, 90M" sometimes: "20M, 30M, 40M, 50M ... 80M" when force "ls -al test-130M", it will show "out-of-memory" it looks to me that depends the current memory usage. Based on my test, this issue is likely relate to EFI or grub (or initramfs config) instead of kernel. For the people be blocked by this issue, the best practice should change the initramfs compression method to reduce the file size as what ybdjkfd shared in comment#41. ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: grub2-signed (Ubuntu) Importance: Undecided Status: New -- 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/1842320 Title: Out of Memory on boot with 5.2.0 kernel Status in OEM Priority Project: In Progress Status in grub2-signed package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d". Can still boot using the previous 5.0.0-25-generic kernel, but the 5.2.0-15-generic fails to start. On selecting Ubuntu from Grub, the message "error: out of memory." is immediately shown. Pressing a key attempts to start boot-up but fails to mount root fs. Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free shows the following (run from Gnome terminal): totalusedfree shared buff/cache available Mem:7906564 1761196 3833240 1020216 2312128 4849224 Swap: 1003516 0 1003516 Kernel packages installed: linux-generic 5.2.0.15.16 amd64 linux-headers-5.2.0-15 5.2.0-15.16 all linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64 linux-headers-generic 5.2.0.15.16 amd64 linux-image-5.0.0-25-generic 5.0.0-25.26 amd64 linux-image-5.2.0-15-generic 5.2.0-15.16+signed1 amd64 linux-image-generic5.2.0.15.16 amd64 linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64 linux-modules-extra-5.0.0-25-generic 5.0.0-25.26 amd64 linux-modules-extra-5.2.0-15-generic 5.2.0-15.16 amd64 Photo of kernel panic attached. NVMe drive partition layout (GPT): Device StartEnd Sectors Size Type /dev/nvme0n1p120481050623 1048576 512M EFI System /dev/nvme0n1p2 10506242549759 1499136 732M Linux filesystem /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem $ sudo pvs PV VGFmt Attr PSizePFree /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a-- <475.71g0 $ sudo lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root ubuntu-vg -wi-ao 474.75g swap_1 ubuntu-vg -wi-ao 980.00m Partition 3 is LUKS encrypted. Root LV is ext4. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gmckeown 1647 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-15 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision FHD Camera Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.181 Tags: eoan Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago) UserGroups: adm cdrom dip lpadmin plugde
