[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
Exim upstream has switched, 4.96~RC0 and later use pcre2. ** Changed in: exim4 (Ubuntu) Status: Incomplete => In Progress -- 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/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: In Progress Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Fix Released Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Fix Released Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in tilix package in Ubuntu: New Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Incomplete Status in zsh package in Debian: Confirmed Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1970402] Re: Initrd out of memory error after upgrade to 22.04
I had the same issue compiling a 5.15.36 kernel on Ubuntu 22.04, initrd.img (.tmp) below was causing Out of memory: -rw-r--r-- 1 root root 13628696 May 23 22:58 initrd.img-5.15.36+ -rw-r--r-- 1 root root 515731970 May 23 22:58 initrd.img-5.15.36+.tmp Switching MODULES=most (which produced .tmp above) to MODULES=dep in /etc/initramfs-tools/initramfs.conf produced the smaller initrd.img, and fixed the issue. $ cat /proc/meminfo MemTotal: 16065036 kB ... -- 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/1970402 Title: Initrd out of memory error after upgrade to 22.04 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: After upgrading to 22.04 system is unbootable because of "out of memory" error when loading initial ramdisk. I was able to fix it by editing cat /etc/initramfs-tools/initramfs.conf and changing configuration to: MODULES=dep COMPRESS=xz RUNSIZE=15% Not sure which one helped, but I can test it if needed. System information: Description:Ubuntu 22.04 LTS Release:22.04 initramfs-tools: Installed: 0.140ubuntu13 Candidate: 0.140ubuntu13 Version table: *** 0.140ubuntu13 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+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 1973270] Update Released
The verification of the Stable Release Update for json-c 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 json-c in Ubuntu. https://bugs.launchpad.net/bugs/1973270 Title: json-c please mark package as multiarch Status in json-c package in Ubuntu: Fix Released Status in json-c source package in Jammy: Fix Released Status in json-c source package in Kinetic: Fix Released Bug description: [Impact] People using multi-arch to build for different architectures [Test Plan] * Install json-c on M-A environment [Where problems could occur] * Specially now that we don't have anymore real i386 env [Other Info] json-c (0.15-3) unstable; urgency=medium * Mark dev package as M-A: same (Closes: #1009805) - thanks Tomeu Vizoso for the hint. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1973270/+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 1972721] Re: Include gtk3 changes needed for mutter 42.1
This bug was fixed in the package gtk+3.0 - 3.24.33-1ubuntu2 --- gtk+3.0 (3.24.33-1ubuntu2) jammy; urgency=medium * Cherry-pick gtk-3-24 commits needed for mutter 42.1 (LP: #1972721) -- Jeremy Bicha Mon, 09 May 2022 16:15:04 -0400 ** Changed in: gtk+3.0 (Ubuntu Jammy) Status: Fix Committed => 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/1972721 Title: Include gtk3 changes needed for mutter 42.1 Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Jammy: Fix Released Bug description: Impact -- We need to update gtk3 before updating mutter to 42.1. Otherwise, in gtk3 apps like gedit, it's not possible to scroll past the cursor position. The mutter issue with more details is https://gitlab.gnome.org/GNOME/mutter/-/issues/2261 We need to update mutter 42.1 since it includes a lot of bug fixes. GNOME Shell 42.1 (with the corresponding changes to mutter, gtk3 and gtk4) will better comply with the Wayland specifications. The gtk4 bug is LP: #1972722 Test Case - Install the updated gtk3 packages. Use gedit to open a long text file. Scroll down past the page break. The document should scroll normally. What Could Go Wrong --- Ideally, GNOME would have done a new GTK3 release for this issue. They will eventually, but it seems better for Ubuntu to be proactive and not further delay the mutter/gnome-shell 42.1 releases. These commits are cherry-picks from the stable branch https://gitlab.gnome.org/GNOME/gtk/-/commits/gtk-3-24/ NOTE To avoid a temporary mismatch related to phased updates, we want this update to be 100% phased before releasing mutter 42.1 to jammy-updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1972721/+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 1972721] Update Released
The verification of the Stable Release Update for gtk+3.0 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 gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972721 Title: Include gtk3 changes needed for mutter 42.1 Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Jammy: Fix Released Bug description: Impact -- We need to update gtk3 before updating mutter to 42.1. Otherwise, in gtk3 apps like gedit, it's not possible to scroll past the cursor position. The mutter issue with more details is https://gitlab.gnome.org/GNOME/mutter/-/issues/2261 We need to update mutter 42.1 since it includes a lot of bug fixes. GNOME Shell 42.1 (with the corresponding changes to mutter, gtk3 and gtk4) will better comply with the Wayland specifications. The gtk4 bug is LP: #1972722 Test Case - Install the updated gtk3 packages. Use gedit to open a long text file. Scroll down past the page break. The document should scroll normally. What Could Go Wrong --- Ideally, GNOME would have done a new GTK3 release for this issue. They will eventually, but it seems better for Ubuntu to be proactive and not further delay the mutter/gnome-shell 42.1 releases. These commits are cherry-picks from the stable branch https://gitlab.gnome.org/GNOME/gtk/-/commits/gtk-3-24/ NOTE To avoid a temporary mismatch related to phased updates, we want this update to be 100% phased before releasing mutter 42.1 to jammy-updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1972721/+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 1973270] Re: json-c please mark package as multiarch
This bug was fixed in the package json-c - 0.15-3~ubuntu1.22.04.1 --- json-c (0.15-3~ubuntu1.22.04.1) jammy; urgency=medium * SRU to Ubuntu 22.04.1 (LP: #1973270) json-c (0.15-3) unstable; urgency=medium * Mark dev package as M-A: same (Closes: #1009805) - thanks Tomeu Vizoso for the hint. -- Gianfranco Costamagna Fri, 13 May 2022 09:27:59 +0200 ** Changed in: json-c (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1973270 Title: json-c please mark package as multiarch Status in json-c package in Ubuntu: Fix Released Status in json-c source package in Jammy: Fix Released Status in json-c source package in Kinetic: Fix Released Bug description: [Impact] People using multi-arch to build for different architectures [Test Plan] * Install json-c on M-A environment [Where problems could occur] * Specially now that we don't have anymore real i386 env [Other Info] json-c (0.15-3) unstable; urgency=medium * Mark dev package as M-A: same (Closes: #1009805) - thanks Tomeu Vizoso for the hint. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1973270/+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 1974037] Re: openssl: EVP_EC_gen() segfault without init
** Tags added: patch
--
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/1974037
Title:
openssl: EVP_EC_gen() segfault without init
Status in openssl package in Ubuntu:
In Progress
Status in openssl source package in Jammy:
Confirmed
Status in openssl source package in Kinetic:
In Progress
Status in openssl package in Debian:
Fix Released
Bug description:
[Impact]
The fix for
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997 has
broken some code paths as the new string comparison functions now need
initialization, triggering segafults.
The provided debdiff fixes the immediate issue and also settles on a
new implementation not requiring the initialization in the first
place.
[Test Plan]
Since this is a regression fix, we first need to check that the
original bug hasn't cropped up again:
sudo locale-gen tr_TR.UTF-8
LANG=C curl https://ubuntu.com/ > /dev/null # This work
LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This should work as
well
For the regression itself:
sudo apt install libssl-dev
cat < openssl_test.c
#include
int main()
{
EVP_PKEY_Q_keygen(NULL, NULL, "EC", "P-256");
}
EOF
gcc openssl_test.c -lcrypto -lssl -o openssl_test
./openssl_test
[Where problems could occur]
This new patch set is relatively massive, on top of another massive one.
Some new regressions could crop up of a similar kind. Furthermore, the
homegrown string comparison function could be buggy, leading to algorithm
name mismatches.
[Other info]
The patches all come from upstream and have been merged on their 3.0
maintenance branch.
[Original report]
Source: sscg
Version: 3.0.2-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1
...
1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11
SIGSEGV
04:32:21 MALLOC_PERTURB_=87
/<>/obj-x86_64-linux-gnu/generate_rsa_key_test
...
Summary of Failures:
1/10 generate_rsa_key_test FAIL 0.01s killed by signal
11 SIGSEGV
Ok: 9
Expected Fail: 0
Fail: 1
Unexpected Pass:0
Skipped:0
Timeout:0
dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8
MESON_TESTTHREADS=4 ninja test returned exit code 1
make: *** [debian/rules:6: binary-arch] Error 25
This has also been reported on the openssl-users mailing list:
https://www.mail-archive.com/openssl-users@openssl.org/msg90830.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+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 1975621] [NEW] screen flashes on-off unless PSR is turned off
Public bug reported: Laptop is a Starlabs Lite Mv IV Integrated graphic card is Mesa Intel® UHD Graphics 605 (GLK 3) Screen backlight turns off and on quickly from time to time Seems to be random : can happen several times per minute, then nothing happens for a few minutes. Seems to happen more often if the graphic card load is increased. Might be related to the graphic card core temperature/load-related. Fixed the problem by adding the following kernel option : i915.enable_psr=0 [3.868968] i915 :00:02.0: [drm] Unknown revid 0x06 [3.869555] i915 :00:02.0: [drm] VT-d active for gfx access [3.869566] fb0: switching to i915 from EFI VGA [3.869878] i915 :00:02.0: vgaarb: deactivate vga console [3.921387] i915 :00:02.0: [drm] couldn't get memory information [3.922325] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [3.923660] i915 :00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v1.4) [4.222037] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 [4.222440] snd_hda_intel :00:0e.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.561945] fbcon: i915drmfb (fb0) is primary device [4.593816] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device [ 4954.090871] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Machine has latest firmware (CoreBoot) And its Ubuntu is the latest LTS, kept up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 24 19:38:39 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation GeminiLake [UHD Graphics 605] [8086:2212] InstallationDate: Installed on 2022-04-26 (28 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Star Labs Lite ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash mitigations=off i915.enable_psr=0 vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2022 dmi.bios.release: 4.16 dmi.bios.vendor: coreboot dmi.bios.version: 4.16 dmi.board.name: Lite dmi.board.vendor: Star Labs dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Star Labs dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4: dmi.product.family: I4 dmi.product.name: Lite dmi.product.sku: I4 dmi.product.version: 1.0 dmi.sys.vendor: Star Labs version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1975621 Title: screen flashes on-off unless PSR is turned off Status in xorg package in Ubuntu: New Bug description: Laptop is a Starlabs Lite Mv IV Integrated graphic card is Mesa Intel® UHD Graphics 605 (GLK 3) Screen backlight turns off and on quickly from time to time Seems to be random : can happen several times per minute, then nothing happens for a few minutes. Seems to happen more often if the graphic card load is increased. Might be related to the graphic card core temperature/load-related. Fixed the problem by adding the
[Touch-packages] [Bug 1975620] [NEW] evolution-calendar-factory memory corruption crash on caldav sync
Public bug reported: evolution-calendar-factory memory corruption crash on caldav sync To reproduce: 1) Connect evolution data server to a caldav account (methods vary but I used https://github.com/pcrockett/Gnome-DAV-Support-Shim plus my icloud account) 2) Open gnome calendar 3) Watch the journal as the calendar factory tries to sync I'd like the sync to complete successfully, but Bug reported directly to GNOME / evolution data server project here: https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/359 The above bug report has a fix attached which (per the author) can be backported into current ubuntu packages. I'd like to request that this backport be performed. I hope this is the right way to do so! ~> lsb_release -rd Description:Pop!_OS 22.04 LTS Release:22.04 ~> apt-cache policy evolution-data-server evolution-data-server: Installed: 3.44.1-0ubuntu2 Candidate: 3.44.1-0ubuntu2 Version table: *** 3.44.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.44.0-2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1975620 Title: evolution-calendar-factory memory corruption crash on caldav sync Status in evolution-data-server package in Ubuntu: New Bug description: evolution-calendar-factory memory corruption crash on caldav sync To reproduce: 1) Connect evolution data server to a caldav account (methods vary but I used https://github.com/pcrockett/Gnome-DAV-Support-Shim plus my icloud account) 2) Open gnome calendar 3) Watch the journal as the calendar factory tries to sync I'd like the sync to complete successfully, but Bug reported directly to GNOME / evolution data server project here: https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/359 The above bug report has a fix attached which (per the author) can be backported into current ubuntu packages. I'd like to request that this backport be performed. I hope this is the right way to do so! ~> lsb_release -rd Description: Pop!_OS 22.04 LTS Release: 22.04 ~> apt-cache policy evolution-data-server evolution-data-server: Installed: 3.44.1-0ubuntu2 Candidate: 3.44.1-0ubuntu2 Version table: *** 3.44.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.44.0-2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1975620/+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 1975620] Re: evolution-calendar-factory memory corruption crash on caldav sync
To add: here's what I see in the journal for evidence of the crash: ~> journalctl -t evolution-calendar-factory May 05 07:48:25 pop-os evolution-calendar-factory[3837]: munmap_chunk(): invalid pointer -- Boot f0f41bc7144944048358cf949b5dff68 -- May 05 19:14:22 pop-os evolution-calendar-factory[3855]: free(): invalid pointer -- Boot 9bc59a17d79d403e9b9cb2254fc91904 -- May 06 15:22:29 pop-os evolution-calendar-factory[3975]: double free or corruption (out) -- Boot 30e2a4ef06374b2aa87049a664034ed0 -- May 12 20:04:21 pop-os evolution-calendar-factory[3868]: free(): invalid pointer -- Boot 1c9623ec04b14d4dbcc73ef90969397d -- May 13 16:51:09 pop-os evolution-calendar-factory[3972]: free(): invalid pointer -- Boot 8fe01e6616b94385b3cf7340bb0b728f -- May 20 12:27:28 pop-os evolution-calendar-factory[4245]: double free or corruption (out) -- Boot 8f0eca5e851c44edb147384494af7b62 -- May 22 18:55:22 pop-os evolution-calendar-factory[21584]: double free or corruption (out) -- Boot 5e3e871437ac4984a2d7d7c6442a78e6 -- May 23 23:35:30 pop-os evolution-calendar-factory[3968]: double free or corruption (out) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1975620 Title: evolution-calendar-factory memory corruption crash on caldav sync Status in evolution-data-server package in Ubuntu: New Bug description: evolution-calendar-factory memory corruption crash on caldav sync To reproduce: 1) Connect evolution data server to a caldav account (methods vary but I used https://github.com/pcrockett/Gnome-DAV-Support-Shim plus my icloud account) 2) Open gnome calendar 3) Watch the journal as the calendar factory tries to sync I'd like the sync to complete successfully, but Bug reported directly to GNOME / evolution data server project here: https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/359 The above bug report has a fix attached which (per the author) can be backported into current ubuntu packages. I'd like to request that this backport be performed. I hope this is the right way to do so! ~> lsb_release -rd Description: Pop!_OS 22.04 LTS Release: 22.04 ~> apt-cache policy evolution-data-server evolution-data-server: Installed: 3.44.1-0ubuntu2 Candidate: 3.44.1-0ubuntu2 Version table: *** 3.44.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.44.0-2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1975620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1974250] Re: ~/.pam_environment gets created as owned by root
** Changed in: accountsservice (Ubuntu Kinetic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1974250 Title: ~/.pam_environment gets created as owned by root Status in accountsservice package in Ubuntu: Fix Committed Status in accountsservice source package in Jammy: Fix Released Status in accountsservice source package in Kinetic: Fix Committed Bug description: Something has happened lately with accountsservice, which makes it act as root instead of the current user when creating ~/.pam_environment. The very old bug #904395 comes to mind, and this smells a security issue. The function which is supposed to prevent this behavior is here: https://salsa.debian.org/freedesktop- team/accountsservice/-/blob/ubuntu/debian/patches/0010-set- language.patch#L75 Haven't investigated further yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1974250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
update installed and ~$ NetworkManager -V 1.36.6 To test i need to be at another location. Feedback Thursday Thanks -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1975628] [NEW] package linux-image-5.4.0-114-generic 5.4.0-114.128 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: This is a bug which makes it impossible to upgrade system ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-114-generic 5.4.0-114.128 ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: king 2079 F pulseaudio /dev/snd/pcmC0D0p: king 2079 F...m pulseaudio /dev/snd/controlC1: king 2079 F pulseaudio CasperMD5CheckResult: skip Date: Tue May 24 14:28:38 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=de6ce9fa-f517-4514-b7f4-b373ae5e9f01 InstallationDate: Installed on 1980-01-01 (15484 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-113-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 SourcePackage: initramfs-tools Title: package linux-image-5.4.0-114-generic 5.4.0-114.128 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.40 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pn:pvrA1029CD1:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr: dmi.product.version: A1029CD1 dmi.sys.vendor: Hewlett-Packard ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-from-proposed -- 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/1975628 Title: package linux-image-5.4.0-114-generic 5.4.0-114.128 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: This is a bug which makes it impossible to upgrade system ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-114-generic 5.4.0-114.128 ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: king 2079 F pulseaudio /dev/snd/pcmC0D0p: king 2079 F...m pulseaudio /dev/snd/controlC1: king 2079 F pulseaudio CasperMD5CheckResult: skip Date: Tue May 24 14:28:38 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=de6ce9fa-f517-4514-b7f4-b373ae5e9f01 InstallationDate: Installed on 1980-01-01 (15484 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-113-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 SourcePackage: initramfs-tools Title: package linux-image-5.4.0-114-generic 5.4.0-114.128 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.40 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pn:pvrA1029CD1:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr: dmi.product.version: A1029CD1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to:
[Touch-packages] [Bug 1975614] Re: audispd daemon missing in 22.04
Thank you for your bug report. https://salsa.debian.org/debian/audit/-/commit/a59e6203 suggests it was merged in the main service, could you explain in detail what is missing for you? ** Changed in: audit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1975614 Title: audispd daemon missing in 22.04 Status in audit package in Ubuntu: Incomplete Bug description: audispd was part of auditd package in 20.04. In 22.04 it is not anymore. Moreover, it is not part of any package according to "apt-file search audispd". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1975614/+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 1974230] Re: Negative cache results from dnsmasq do not include SOA as required in RFC2308
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dnsmasq (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1974230 Title: Negative cache results from dnsmasq do not include SOA as required in RFC2308 Status in dnsmasq package in Ubuntu: Confirmed Bug description: RFC2308 states: 6 - Negative answers from the cache When a server, in answering a query, encounters a cached negative response it MUST add the cached SOA record to the authority section of the response with the TTL decremented by the amount of time it was stored in the cache. This allows the NXDOMAIN / NODATA response to time out correctly. The effect is that the negative cache results returned by dnsmasq cannot be cached by other resolvers such as systemd-resolved. A good example of why this is a problem: Two clients with systemd-resolved send DNS queries to dnsmasq for the same record The first one makes a query and gets NXDOMAIN with SOA. This results in systemd-resolved caching the negative result. The second client makes a query and gets NODATA without the SOA. This results in systemd-resolved not caching the negative result. Consider a domain name that only has an A record published. When connecting to that domain a lookup happens for the and A record. One can end up in a situation where systemd-resolved has the A record cached locally, but it still goes out to the network to perform the lookup only to get the same negative cache result that is missing the SOA I see this behavior in 18.04 and 22.04 First query to dnsmasq can be cached: dig @10.0.1.21 a.google.com ; <<>> DiG 9.16.1-Ubuntu <<>> @10.0.1.21 a.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3107 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;a.google.com. IN A ;; AUTHORITY SECTION: google.com. 60 IN SOA ns1.google.com. dns-admin.google.com. 449437361 900 900 1800 60 ;; Query time: 15 msec ;; SERVER: 10.0.1.21#53(10.0.1.21) ;; WHEN: Thu May 19 15:00:12 EDT 2022 ;; MSG SIZE rcvd: 91 Cached response from dnsmasq cannot be cached: dig @10.0.1.21 a.google.com ; <<>> DiG 9.16.1-Ubuntu <<>> @10.0.1.21 a.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61408 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;a.google.com. IN A ;; Query time: 0 msec ;; SERVER: 10.0.1.21#53(10.0.1.21) ;; WHEN: Thu May 19 15:00:13 EDT 2022 ;; MSG SIZE rcvd: 41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1974230/+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 1974037] Re: openssl: EVP_EC_gen() segfault without init
Attached is a debdiff for the Jammy changes. I'm still working on Kinetic as this will be folded into the merge, but I still need to do some more work as some new patches have surfaced upstream since then, as well as a new Debian revision. I feel the Jammy SRU should still move forward. Note that the patchset is consequent as upstream has changed their approach to the issue a couple of times, now settling into reimplementing the string comparison functions entirely rather than relying on a C locale. This last approach has the benefit of not requiring initialization, which seems to have been the cause of all the regressions observed so far with the first solution. The patches for that last approach haven't made their way to Debian yet, AFAICT. ** Patch added: "openssl.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+attachment/5592652/+files/openssl.debdiff -- 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/1974037 Title: openssl: EVP_EC_gen() segfault without init Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: Confirmed Status in openssl source package in Kinetic: In Progress Status in openssl package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/1010958: Source: sscg Version: 3.0.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1 ... 1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11 SIGSEGV 04:32:21 MALLOC_PERTURB_=87 /<>/obj-x86_64-linux-gnu/generate_rsa_key_test ... Summary of Failures: 1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11 SIGSEGV Ok: 9 Expected Fail: 0 Fail: 1 Unexpected Pass:0 Skipped:0 Timeout:0 dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1 make: *** [debian/rules:6: binary-arch] Error 25 This has also been reported on the openssl-users mailing list: https://www.mail-archive.com/openssl-users@openssl.org/msg90830.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+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 1975620] Re: evolution-calendar-factory memory corruption crash on caldav sync
Thank you for your bug report, now that the fix is upstream we will get it in one of the next updates ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => High ** Changed in: evolution-data-server (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1975620 Title: evolution-calendar-factory memory corruption crash on caldav sync Status in evolution-data-server package in Ubuntu: In Progress Bug description: evolution-calendar-factory memory corruption crash on caldav sync To reproduce: 1) Connect evolution data server to a caldav account (methods vary but I used https://github.com/pcrockett/Gnome-DAV-Support-Shim plus my icloud account) 2) Open gnome calendar 3) Watch the journal as the calendar factory tries to sync I'd like the sync to complete successfully, but Bug reported directly to GNOME / evolution data server project here: https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/359 The above bug report has a fix attached which (per the author) can be backported into current ubuntu packages. I'd like to request that this backport be performed. I hope this is the right way to do so! ~> lsb_release -rd Description: Pop!_OS 22.04 LTS Release: 22.04 ~> apt-cache policy evolution-data-server evolution-data-server: Installed: 3.44.1-0ubuntu2 Candidate: 3.44.1-0ubuntu2 Version table: *** 3.44.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.44.0-2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1975620/+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 1823420] Re: audit ftbfs in disco
** Changed in: audit (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
https://bugs.launchpad.net/bugs/1823420
Title:
audit ftbfs in disco
Status in audit package in Ubuntu:
Fix Released
Bug description:
https://launchpadlibrarian.net/417924448/buildlog_ubuntu-
disco-i386.audit_1%3A2.8.3-1ubuntu3_BUILDING.txt.gz
gcc -DHAVE_CONFIG_H -I. -I../../../lib -I.. -I. -I../../..
-I../../../auparse '-DTABLE_H="flagtab.h"' -g -O2 -c -o
gen_flagtabs_h-gen_tables.o `test -f 'gen_tables.c' || echo
'../../../lib/'`gen_tables.c
In file included from ../../../lib/gen_tables.c:40:
../../../lib/libaudit.h:292: warning: "AUDIT_FILTER_EXCLUDE" redefined
#define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
In file included from ../../../lib/libaudit.h:35,
from ../../../lib/gen_tables.c:40:
/usr/include/linux/audit.h:161: note: this is the location of the previous
definition
#define AUDIT_FILTER_EXCLUDE 0x05 /* Apply rule before record creation */
In file included from ../../../lib/gen_tables.c:40:
../../../lib/libaudit.h:292: warning: "AUDIT_FILTER_EXCLUDE" redefined
#define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
In file included from ../../../lib/libaudit.h:35,
from ../../../lib/gen_tables.c:40:
/usr/include/linux/audit.h:161: note: this is the location of the previous
definition
#define AUDIT_FILTER_EXCLUDE 0x05 /* Apply rule before record creation */
In file included from ../../../lib/gen_tables.c:40:
../../../lib/libaudit.h:292: warning: "AUDIT_FILTER_EXCLUDE" redefined
#define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
In file included from ../../../lib/libaudit.h:35,
from ../../../lib/gen_tables.c:40:
/usr/include/linux/audit.h:161: note: this is the location of the previous
definition
#define AUDIT_FILTER_EXCLUDE 0x05 /* Apply rule before record creation */
In file included from ../../../lib/gen_tables.c:40:
../../../lib/libaudit.h:292: warning: "AUDIT_FILTER_EXCLUDE" redefined
#define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
In file included from ../../../lib/libaudit.h:35,
from ../../../lib/gen_tables.c:40:
/usr/include/linux/audit.h:161: note: this is the location of the previous
definition
#define AUDIT_FILTER_EXCLUDE 0x05 /* Apply rule before record creation */
../../../lib/libaudit.h:292:30: error: ‘AUDIT_FILTER_EXCLUDE’ undeclared here
(not in a function)
#define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
^
../../../lib/gen_tables.c:89:23: note: in definition of macro ‘_S’
#define _S(VAL, S) { (VAL), (S), 0, 0 },
^~~
../../../lib/flagtab.h:26:4: note: in expansion of macro
‘AUDIT_FILTER_EXCLUDE’
_S(AUDIT_FILTER_EXCLUDE, "exclude" )
^~~~
make[4]: *** [Makefile:1003: gen_flagtabs_h-gen_tables.o] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory '/<>/debian/build/lib'
make[3]: *** [Makefile:469: all-recursive] Error 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1823420/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1974250] Re: ~/.pam_environment gets created as owned by root
This bug was fixed in the package accountsservice - 22.07.5-2ubuntu2 --- accountsservice (22.07.5-2ubuntu2) kinetic; urgency=medium [ Marc Deslauriers ] * SECURITY UPDATE: accountsservice incorrect privilege dropping (LP: #1974250) - debian/patches/0009-language-tools.patch: updated to not reset effective uid, and migrate root-owned .pam_environment file. - This change was originally known as CVE-2020-16126 and got reverted by mistake in 0.6.55-3ubuntu1. - CVE-2022-1804 * Fix FTBFS with a newer python-dbusmock package: - debian/patches/adduser_invocation.patch: fix invocation of AddUser in tests/dbusmock/accounts_service.py. - debian/patches/setlocked_signature.patch: fix the signature for the SetLocked call in tests/dbusmock/accounts_service.py. -- Gunnar Hjalmarsson Tue, 24 May 2022 19:53:07 +0200 ** Changed in: accountsservice (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1974250 Title: ~/.pam_environment gets created as owned by root Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Jammy: Fix Released Status in accountsservice source package in Kinetic: Fix Released Bug description: Something has happened lately with accountsservice, which makes it act as root instead of the current user when creating ~/.pam_environment. The very old bug #904395 comes to mind, and this smells a security issue. The function which is supposed to prevent this behavior is here: https://salsa.debian.org/freedesktop- team/accountsservice/-/blob/ubuntu/debian/patches/0010-set- language.patch#L75 Haven't investigated further yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1974250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1974037] Re: openssl: EVP_EC_gen() segfault without init
** Description changed:
- Imported from Debian bug http://bugs.debian.org/1010958:
+ [Impact]
+
+ The fix for
+ https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997 has
+ broken some code paths as the new string comparison functions now need
+ initialization, triggering segafults.
+
+ The provided debdiff fixes the immediate issue and also settles on a new
+ implementation not requiring the initialization in the first place.
+
+ [Test Plan]
+
+ Since this is a regression fix, we first need to check that the original
+ bug hasn't cropped up again:
+
+ sudo locale-gen tr_TR.UTF-8
+ LANG=C curl https://ubuntu.com/ > /dev/null # This work
+ LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This should work as
well
+
+ For the regression itself:
+
+ sudo apt install libssl-dev
+ cat < openssl_test.c
+ #include
+ int main()
+ {
+ EVP_PKEY_Q_keygen(NULL, NULL, "EC", "P-256");
+ }
+ EOF
+ gcc openssl_test.c -lcrypto -lssl -o openssl_test
+ ./openssl_test
+
+
+ [Where problems could occur]
+
+ This new patch set is relatively massive, on top of another massive one.
+ Some new regressions could crop up of a similar kind. Furthermore, the
+ homegrown string comparison function could be buggy, leading to algorithm
name mismatches.
+
+ [Other info]
+
+ The patches all come from upstream and have been merged on their 3.0
+ maintenance branch.
+
+ [Original report]
Source: sscg
Version: 3.0.2-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1
...
1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11
SIGSEGV
04:32:21 MALLOC_PERTURB_=87
/<>/obj-x86_64-linux-gnu/generate_rsa_key_test
...
Summary of Failures:
1/10 generate_rsa_key_test FAIL 0.01s killed by signal
11 SIGSEGV
Ok: 9
Expected Fail: 0
Fail: 1
Unexpected Pass:0
Skipped:0
Timeout:0
dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8
MESON_TESTTHREADS=4 ninja test returned exit code 1
make: *** [debian/rules:6: binary-arch] Error 25
This has also been reported on the openssl-users mailing list:
https://www.mail-archive.com/openssl-users@openssl.org/msg90830.html
--
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/1974037
Title:
openssl: EVP_EC_gen() segfault without init
Status in openssl package in Ubuntu:
In Progress
Status in openssl source package in Jammy:
Confirmed
Status in openssl source package in Kinetic:
In Progress
Status in openssl package in Debian:
Fix Released
Bug description:
[Impact]
The fix for
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997 has
broken some code paths as the new string comparison functions now need
initialization, triggering segafults.
The provided debdiff fixes the immediate issue and also settles on a
new implementation not requiring the initialization in the first
place.
[Test Plan]
Since this is a regression fix, we first need to check that the
original bug hasn't cropped up again:
sudo locale-gen tr_TR.UTF-8
LANG=C curl https://ubuntu.com/ > /dev/null # This work
LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This should work as
well
For the regression itself:
sudo apt install libssl-dev
cat < openssl_test.c
#include
int main()
{
EVP_PKEY_Q_keygen(NULL, NULL, "EC", "P-256");
}
EOF
gcc openssl_test.c -lcrypto -lssl -o openssl_test
./openssl_test
[Where problems could occur]
This new patch set is relatively massive, on top of another massive one.
Some new regressions could crop up of a similar kind. Furthermore, the
homegrown string comparison function could be buggy, leading to algorithm
name mismatches.
[Other info]
The patches all come from upstream and have been merged on their 3.0
maintenance branch.
[Original report]
Source: sscg
Version: 3.0.2-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1
...
1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11
SIGSEGV
04:32:21 MALLOC_PERTURB_=87
/<>/obj-x86_64-linux-gnu/generate_rsa_key_test
...
Summary of Failures:
1/10 generate_rsa_key_test FAIL 0.01s killed by signal
11 SIGSEGV
Ok: 9
Expected Fail: 0
Fail: 1
Unexpected Pass:0
Skipped:0
Timeout:0
dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8
MESON_TESTTHREADS=4 ninja test returned exit code 1
make: *** [debian/rules:6: binary-arch] Error 25
This has also been reported on the openssl-users mailing list:
https://www.mail-archive.com/openssl-users@openssl.org/msg90830.html
To manage notifications about this bug go to:
[Touch-packages] [Bug 1975614] Re: audispd daemon missing in 22.04
I did not know the dispatcher is part of the main daemon now. My issue was about wrong ownership (non-root) of my plug-in, and I wrongly attributed it to the missing dispatcher. Thanks for the help, I guess the bug can be closed as not-a-bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1975614 Title: audispd daemon missing in 22.04 Status in audit package in Ubuntu: Incomplete Bug description: audispd was part of auditd package in 20.04. In 22.04 it is not anymore. Moreover, it is not part of any package according to "apt-file search audispd". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1975614/+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 1975650] [NEW] Display stuck in low resolution
Public bug reported: I often have to forcibly power down my PC because of this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the most recent time I did that, when the computer restarted, the resolution is stuck on 1024x768 even though I am on a 1920x1080 monitor. I restarted my PC again and it is still stuck on the low resolution. This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did allow me to force my resolution to 1920x1080, but a few things still seemed off: - The display settings page in the Gnome settings app still showed my display as "unknown display" and did not have any options for changing the resolution. - A WebGL-based application I use for work was very slow compared to normal. I reverted the change to my Grub config and now I'm back to 1024x768. I have an Nvidia GTX 1060 connected to a 1920x1080 monitor via HDMI. Let me know of any other information I can provide that would be helpful. Also let me know if there is a workaround other than reinstalling the OS. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 24 20:14:55 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] InstallationDate: Installed on 2022-04-23 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy resolution ubuntu ** Attachment added: "Display settings" https://bugs.launchpad.net/bugs/1975650/+attachment/5592732/+files/Screenshot%20from%202022-05-24%2020-18-45.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1975650 Title: Display stuck in low resolution Status in xorg package in Ubuntu: New Bug description: I often have to forcibly power down my PC because of this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the most recent time I did that, when the computer restarted, the resolution is stuck on 1024x768 even though I am on a 1920x1080 monitor. I restarted my PC again and it is still stuck on the low resolution. This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did allow me to force my resolution to 1920x1080, but a few things still seemed off: - The display settings page in the Gnome settings app still showed my display as "unknown display" and did not have any options for changing the resolution. - A WebGL-based application I use for work was very slow compared to normal. I reverted the change to my Grub config and now I'm back to
[Touch-packages] [Bug 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
Pipewire isn't involved in putting pixels on the screen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]
Also affected (bug 1975647). Notably, this happened after I attempted to dual boot Debian 11 (stable, then testing). The workspace indicator extension worked before then, but disappeared after I switched back. user@host:~$ gnome-extensions-app Gdk-Message: 20:03:19.701: Error flushing display: Protocol error user@host:~$ cheese (cheese:32950): Gdk-WARNING **: 20:04:45.134: Native Windows taller than 65535 pixels are not supported Gdk-Message: 20:04:46.246: Error 71 (Protocol error) dispatching to Wayland display. user@host:~$ In syslog: gnome-shell[2051]: WL: error in client communication (pid 32877) cheese[32877]: Error reading events from display: Protocol error -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1965563 Title: gnome-extensions-app fails to start [Error reading events from display: Protocol error] Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1871148] Re: services start before apparmor profiles are loaded
Oh, thanks Alex, I forgot that we have our own service for loading the AppArmor profiles of the snaps! Etienne, could you please show the output of sudo systemctl status snapd.apparmor ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1975644] [NEW] package ca-certificates 20211016 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
Public bug reported: upgrade from focal->jammy requested me to report this issue ProblemType: Package DistroRelease: Ubuntu 22.04 Package: ca-certificates 20211016 ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue May 24 21:42:23 2022 Ec2AMI: ami-000ab5e1 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: vps2020-essential-2-4-80 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: ca-certificates Title: package ca-certificates 20211016 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-05-24 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package ec2-images jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1975644 Title: package ca-certificates 20211016 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: upgrade from focal->jammy requested me to report this issue ProblemType: Package DistroRelease: Ubuntu 22.04 Package: ca-certificates 20211016 ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181 Uname: Linux 5.4.0-113-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue May 24 21:42:23 2022 Ec2AMI: ami-000ab5e1 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: vps2020-essential-2-4-80 Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: ca-certificates Title: package ca-certificates 20211016 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-05-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1975644/+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 1784499] Re: AppArmor treats regular NFS file access as network op
@rikka0w0 are you willing to test a kernel patch for this issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1784499 Title: AppArmor treats regular NFS file access as network op Status in AppArmor: Confirmed Status in snapd: Invalid Status in apparmor package in Ubuntu: Confirmed Bug description: I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic. I have the usr.bin.man profile enforced, and home directories in NFS. The log excerpt copied below is the result of a single invocation of "man ls" by an unprivileged user. (The program did display the man page correctly to the user.) It does not seem appropriate for AppArmor to report the man(1) program as having attempted to contact the NFS server directly, when it only tried to access an NFS-served file in the normal way. "man" is not a network-aware program and the log below misleadingly implies otherwise. Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 callbacks suppressed Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 audit(1532986715.862:221): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.062006] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.062014] audit: type=1400 audit(1532986715.862:222): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.066404] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.066434] audit: type=1400 audit(1532986715.866:223): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2788 comm="man"
[Touch-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
[Expired for modemmanager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: modemmanager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Expired Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+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 1958019]
It seems the path to endian.h may have changed from /usr/include/sys/endian.h to /usr/include/endian.h. In the failing file(s), try changing it from: #include To: #include On 5/24/22 05:37, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #617 from singo (hnsinan...@gmail.com) --- > Thanks for the quick reply and the pointer to the github tutorial. I've tried > going down this rabbit hole but face numerous error messages when following > the > guide. Unfortunately I failed at building the js qemu fork. Maybe it fails > because I'm on Ubuntu 22.04.? Anyways, I can't build it and thus can't even > continue with the actual hard part. > > Here's the output for the failed configuration of qemu: > https://pastebin.com/Lfq5vPz6 > > Maybe it has to do with the dependencies? When executing sudo apt install > build-essential && apt build-dep qemu-system-x86 it will says something along > the lines of "choosing qemu instead of quemu-system-x86". > > > (In reply to Cameron Berkenpas from comment #613) >> There's no patch for your laptop yet. >> >> Assuming your sound bar is initialized through verbs (I suspect it is), >> you'll need to find the verb sequence yourself: >> https://github.com/thiagotei/linux-realtek-alc287/tree/cameron >> >> Once there's a working verb sequence, a patch can be created. >> >> On 5/23/22 04:50, bugzilla-dae...@kernel.org wrote: >>> https://bugzilla.kernel.org/show_bug.cgi?id=208555 >>> >>> --- Comment #611 from singo (hnsinan...@gmail.com) --- >>> Hello everyone, >>> >>> I really appreciate this thread and all of the solutions that have been >>> produced for this issue. Thanks to everyone contributing, especially >> Cameron >>> Berkenpas who has been very helpful to a number of users and the main >> driving >>> force for fixes:) >>> >>> Now to my issue: I own a Lenovo Yoga 7i 15ITL05 82AC with the ALC287. >>> Currently >>> it runs Ubuntu 22.04. LTS with the included 5.15 Kernel. Before I have run >>> Pop_OS 21.04. and 22.04. With all these distros, the sound worked partially >>> but >>> never fully. The experience is the same as many other users here, where >> there >>> would only be sound coming out the from the downward firing speakers, but >> not >>> from the soundbar above the keyboard, which are the bass speakers judging >> by >>> the tinny sound I get now. The sound works beautifully in Windows, since >> the >>> lower end frequencies can be replayed. >>> >>> Quite honestly, I've lost the overview over this thread and am not so sure >>> which patch I should apply. I've tried manually update my Ubuntu 22.04. to >>> the >>> mainline 5.17 Kernel, which worked OS-wise but didn't change sound. My hope >>> was >>> that the sound patches have been included in that Kernel, but it seems >>> they're >>> only working for the Legion 7. >>> >>> Could someone point me to the right patch or verbs that have to be applied >>> for >>> my Lenovo model in order for the bass speakers to work? Maybe someone has >>> figured it out for this particular case? >>> >>> Much thanks in advance. >>> >>> Here's my alsa-info: >>> >>> http://alsa-project.org/db/?f=ad3990bed59a24417ea6429250275012611a0302 >>> -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266
[Touch-packages] [Bug 1958019]
Thanks for the quick reply and the pointer to the github tutorial. I've tried going down this rabbit hole but face numerous error messages when following the guide. Unfortunately I failed at building the js qemu fork. Maybe it fails because I'm on Ubuntu 22.04.? Anyways, I can't build it and thus can't even continue with the actual hard part. Here's the output for the failed configuration of qemu: https://pastebin.com/Lfq5vPz6 Maybe it has to do with the dependencies? When executing sudo apt install build-essential && apt build-dep qemu-system-x86 it will says something along the lines of "choosing qemu instead of quemu- system-x86". (In reply to Cameron Berkenpas from comment #613) > There's no patch for your laptop yet. > > Assuming your sound bar is initialized through verbs (I suspect it is), > you'll need to find the verb sequence yourself: > https://github.com/thiagotei/linux-realtek-alc287/tree/cameron > > Once there's a working verb sequence, a patch can be created. > > On 5/23/22 04:50, bugzilla-dae...@kernel.org wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > > > --- Comment #611 from singo (hnsinan...@gmail.com) --- > > Hello everyone, > > > > I really appreciate this thread and all of the solutions that have been > > produced for this issue. Thanks to everyone contributing, especially > Cameron > > Berkenpas who has been very helpful to a number of users and the main > driving > > force for fixes:) > > > > Now to my issue: I own a Lenovo Yoga 7i 15ITL05 82AC with the ALC287. > > Currently > > it runs Ubuntu 22.04. LTS with the included 5.15 Kernel. Before I have run > > Pop_OS 21.04. and 22.04. With all these distros, the sound worked partially > > but > > never fully. The experience is the same as many other users here, where > there > > would only be sound coming out the from the downward firing speakers, but > not > > from the soundbar above the keyboard, which are the bass speakers judging > by > > the tinny sound I get now. The sound works beautifully in Windows, since > the > > lower end frequencies can be replayed. > > > > Quite honestly, I've lost the overview over this thread and am not so sure > > which patch I should apply. I've tried manually update my Ubuntu 22.04. to > > the > > mainline 5.17 Kernel, which worked OS-wise but didn't change sound. My hope > > was > > that the sound patches have been included in that Kernel, but it seems > > they're > > only working for the Legion 7. > > > > Could someone point me to the right patch or verbs that have to be applied > > for > > my Lenovo model in order for the bass speakers to work? Maybe someone has > > figured it out for this particular case? > > > > Much thanks in advance. > > > > Here's my alsa-info: > > > > http://alsa-project.org/db/?f=ad3990bed59a24417ea6429250275012611a0302 > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release:
[Touch-packages] [Bug 1958019]
Appears that these kernels are including these drivers. You might have to figure out how to build your own kernel while enabling the necessary kernel options yourself after all. On 5/24/22 01:46, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #616 from she...@liang.at (she...@liang.at) --- > Oh, sorry I was in the wrong one version cuz I tried reverting to the older > one > when nvidia didn't work anymore. > > In kernel 5.17.0 the first command gives > $ sudo modprobe snd-hda-codec-cs35l41-i2c > modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory > /lib/modules/5.17.0-051700-generic > > while the other two give nothing. > > > (In reply to Cameron Berkenpas from comment #615) >> Your error message shows you're 5.13, which definitely doesn't have support. >> >> >> >> On 5/23/22 08:46, bugzilla-dae...@kernel.org wrote: >>> https://bugzilla.kernel.org/show_bug.cgi?id=208555 >>> >>> --- Comment #614 from she...@liang.at (she...@liang.at) --- >>> The first two modprobe commands returned >>> ` >>> modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory >>> /lib/modules/5.13.0-051300-generic >>> ` >>> The third one returns nothing. >>> >>> I tried reinstalling my nvidia driver too but even after purging all it >>> doesn't >>> seem to work :\ >>> >>> I tried following these instructions: >>> >> >> https://forums.developer.nvidia.com/t/nvidia-smi-has-failed-because-it-couldnt-communicate-with-the-nvidia-driver-make-sure-that-the-latest-nvidia-driver-is-installed-and-running/197141/6 >>> (In reply to Cameron Berkenpas from comment #612) I would try try 5.17. 5.18 only came out yesterday, and therefore doesn't even have any point releases so chances are reasonably high you'll run >> into bugs. Additionally, I don't have the ACHg6. It's possible you'll need to specify which modules to load. In the likely event that 5.17 doesn't work, perhaps someone can provide information on what's needed there. Possibly these steps will work: sudo modprobe snd-hda-codec-cs35l41-i2c sudo modeprobe snd_soc_cs35l41_i2c sudo modeprobe i2c-multi-instantiate (In reply to she...@liang.at from comment #609) > Thanks for the quick responses. I followed the instructions to install >> the > latest version. Is it supposed to work if I installed 5.18 too? It's not > working and it stopped recognising my external monitors too. > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6
[Touch-packages] [Bug 1892825] Re: update-locale not perform correctly sanity checks
This bug was fixed in the package glibc - 2.27-3ubuntu1.6 --- glibc (2.27-3ubuntu1.6) bionic; urgency=medium [ Gunnar Hjalmarsson ] * d/local/usr_sbin/update-locale: improve sanity checks. (LP: #1892825) [ Aurelien Jarno ] * debian/debhelper.in/libc.preinst: drop the check for kernel release > 255 now that glibc and preinstall script are fixed. (LP: #1962225) -- Michael Hudson-Doyle Tue, 03 May 2022 22:19:39 +1200 ** Changed in: glibc (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1892825 Title: update-locale not perform correctly sanity checks Status in glibc package in Ubuntu: Fix Released Status in pam package in Ubuntu: New Status in glibc source package in Bionic: Fix Released Status in pam source package in Bionic: New Status in glibc source package in Focal: Fix Released Status in pam source package in Focal: New Status in glibc source package in Hirsute: Won't Fix Status in pam source package in Hirsute: New Status in glibc source package in Impish: New Status in pam source package in Impish: New Bug description: [impact] A simple typo using the update-locale script can render a system inoperable without booting into single user mode or similar: $ sudo update-locale LANGUAGE = en_US.UTF-8 $ sudo -s sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization [test case] $ cp /etc/default/locale /tmp/locale $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8 "diff -u /etc/default/locale /tmp/locale" should be empty. $ update-locale --locale-file /tmp/locale LANGUAGE=en_US.UTF-8 The LANGUAGE=en_US.UTF-8 line should have been replaced by LANGUAGE=en_GB.UTF-8. $ update-locale --locale-file /tmp/locale LANGUAGE The LANGUAGE setting is now commented out. [regression potential] Apart from the general concerns about a glibc rebuild, this is a simple change to a simple script. Performing the test as in the test case section is enough to ensure it still works. [original description] By passing wrong input as following: sudo update-locale LANGUAGE = en_US.UTF-8 result is: ... #LANGUAGE=en = This "equal" sign that was added makes system completely unusable(can't run sudo anymore): bentzy@bentzy-nb:~$ sudo vim /etc/default/locale sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization Fixed it booting from installation disk and fixing corrupted /etc/default/locale ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: locales 2.31-0ubuntu9 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Aug 25 09:36:03 2020 InstallationDate: Installed on 2020-08-17 (7 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+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 1958019]
Oh, sorry I was in the wrong one version cuz I tried reverting to the older one when nvidia didn't work anymore. In kernel 5.17.0 the first command gives $ sudo modprobe snd-hda-codec-cs35l41-i2c modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory /lib/modules/5.17.0-051700-generic while the other two give nothing. (In reply to Cameron Berkenpas from comment #615) > Your error message shows you're 5.13, which definitely doesn't have support. > > > > On 5/23/22 08:46, bugzilla-dae...@kernel.org wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > > > --- Comment #614 from she...@liang.at (she...@liang.at) --- > > The first two modprobe commands returned > > ` > > modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory > > /lib/modules/5.13.0-051300-generic > > ` > > The third one returns nothing. > > > > I tried reinstalling my nvidia driver too but even after purging all it > > doesn't > > seem to work :\ > > > > I tried following these instructions: > > > > > https://forums.developer.nvidia.com/t/nvidia-smi-has-failed-because-it-couldnt-communicate-with-the-nvidia-driver-make-sure-that-the-latest-nvidia-driver-is-installed-and-running/197141/6 > > > > (In reply to Cameron Berkenpas from comment #612) > >> I would try try 5.17. 5.18 only came out yesterday, and therefore doesn't > >> even have any point releases so chances are reasonably high you'll run > into > >> bugs. > >> > >> Additionally, I don't have the ACHg6. It's possible you'll need to specify > >> which modules to load. In the likely event that 5.17 doesn't work, perhaps > >> someone can provide information on what's needed there. > >> > >> Possibly these steps will work: > >> sudo modprobe snd-hda-codec-cs35l41-i2c > >> sudo modeprobe snd_soc_cs35l41_i2c > >> sudo modeprobe i2c-multi-instantiate > >> > >> (In reply to she...@liang.at from comment #609) > >>> Thanks for the quick responses. I followed the instructions to install > the > >>> latest version. Is it supposed to work if I installed 5.18 too? It's not > >>> working and it stopped recognising my external monitors too. > >>> -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7
[Touch-packages] [Bug 1975650] Re: Display stuck in low resolution
** Description changed: I often have to forcibly power down my PC because of this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the most recent time I did that, when the computer restarted, the resolution is stuck on 1024x768 even though I am on a 1920x1080 monitor. I restarted my PC again and it is still stuck on the low resolution. This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did allow me to force my resolution to 1920x1080, but a few things still seemed off: - The display settings page in the Gnome settings app still showed my display as "unknown display" and did not have any options for changing the resolution. - A WebGL-based application I use for work was very slow compared to normal. I reverted the change to my Grub config and now I'm back to 1024x768. I have an Nvidia GTX 1060 connected to a 1920x1080 monitor via HDMI. Let me know of any other information I can provide that would be helpful. Also let me know if there is a workaround other than reinstalling the OS. + Edit: I have a Windows dual boot on this PC, with Windows installed on a + separate SSD. I booted into Windows and everything seems completely + fine. This provides further evidence that this is a software issue, not + a hardware one. + ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 24 20:14:55 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] + NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] InstallationDate: Installed on 2022-04-23 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/usr/bin/zsh + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1975650 Title: Display stuck in low resolution Status in xorg package in Ubuntu: New Bug description: I often have to forcibly power down my PC because of this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the most recent time I did that, when the computer restarted, the resolution is stuck on 1024x768 even though I am on a 1920x1080 monitor. I restarted my PC again and it is still stuck on the low resolution. This Ask Ubuntu answer
[Touch-packages] [Bug 1888347] Re: blk-availability unmounts filesystems before applications have finished using them
** Tags added: rls-ff-incoming -- 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/1888347 Title: blk-availability unmounts filesystems before applications have finished using them Status in lvm2 package in Ubuntu: Confirmed Bug description: This bug is similar to the following: Red Hat - https://bugzilla.redhat.com/show_bug.cgi?id=1701234#c2 Debian - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946882 The blk-availability service is short-cutting RequiresMountsFor= dependencies during system shutdown and unmounting filesystems before those services have stopped, resulting in data file corruption and/or data loss. This can be worked around by adding "After=blk-availability.service" to the unit file for the service in question, but this is not self- evident and shouldn't be necessary. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jul 21 16:37:17 2020 InstallationDate: Installed on 2014-05-01 (2272 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: lvm2 UpgradeStatus: Upgraded to focal on 2020-05-05 (77 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1888347/+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 591713] Re: Illegal instruction in AES ciphers on WinChip C6
No, I can't check because I don't have the hardware anymore. -- 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/591713 Title: Illegal instruction in AES ciphers on WinChip C6 Status in openssl package in Ubuntu: Incomplete Bug description: Binary package hint: openssl Some ciphers from openssl-0.9.8k-7ubuntu8 in Ubuntu 10.04 terminate with an Illegal instruction signal (SIGILL) when running on a WinChip C6 processor: $ cat openssl.sh #!/bin/sh for c in `openssl list-cipher-commands` do echo $c echo -n Hello | openssl enc -$c -K 0 -iv 0 > /dev/null done $ openssl.sh aes-128-cbc Illegal instruction aes-128-ecb Illegal instruction aes-192-cbc Illegal instruction aes-192-ecb Illegal instruction aes-256-cbc Illegal instruction aes-256-ecb Illegal instruction base64 bf bf-cbc bf-cfb bf-ecb bf-ofb cast cast-cbc cast5-cbc cast5-cfb cast5-ecb cast5-ofb des des-cbc des-cfb des-ecb des-ede des-ede-cbc des-ede-cfb des-ede-ofb des-ede3 des-ede3-cbc des-ede3-cfb des-ede3-ofb des-ofb des3 desx rc2 rc2-40-cbc rc2-64-cbc rc2-cbc rc2-cfb rc2-ecb rc2-ofb rc4 rc4-40 I'm using a default kernel: $ uname -a Linux vdr 2.6.32-22-386 #36-Ubuntu SMP Fri Jun 4 00:27:09 UTC 2010 i586 GNU/Linux This is the CPU info: $ cat /proc/cpuinfo processor : 0 vendor_id : CentaurHauls cpu family : 5 model : 4 model name : WinChip C6 stepping: 1 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de msr mce cx8 mmx centaur_mcr up bogomips: 399.48 clflush size: 32 cache_alignment : 32 address sizes : 32 bits physical, 32 bits virtual power management: I ran into this when I couldn't access this machine via ssh 4.7p1, because this version selects the aes128-cbc cipher by default. Ssh immediately terminates with "Connection closed by ...". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/591713/+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 1975621] Re: [Star Labs Lite IV] screen flashes on-off unless PSR is turned off
** Summary changed: - screen flashes on-off unless PSR is turned off + [Star Labs Lite IV] screen flashes on-off unless PSR is turned off ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: psr -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1975621 Title: [Star Labs Lite IV] screen flashes on-off unless PSR is turned off Status in linux package in Ubuntu: New Bug description: Laptop is a Starlabs Lite Mv IV Integrated graphic card is Mesa Intel® UHD Graphics 605 (GLK 3) Screen backlight turns off and on quickly from time to time Seems to be random : can happen several times per minute, then nothing happens for a few minutes. Seems to happen more often if the graphic card load is increased. Might be related to the graphic card core temperature/load-related. Fixed the problem by adding the following kernel option : i915.enable_psr=0 [3.868968] i915 :00:02.0: [drm] Unknown revid 0x06 [3.869555] i915 :00:02.0: [drm] VT-d active for gfx access [3.869566] fb0: switching to i915 from EFI VGA [3.869878] i915 :00:02.0: vgaarb: deactivate vga console [3.921387] i915 :00:02.0: [drm] couldn't get memory information [3.922325] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [3.923660] i915 :00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v1.4) [4.222037] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 [4.222440] snd_hda_intel :00:0e.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.561945] fbcon: i915drmfb (fb0) is primary device [4.593816] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device [ 4954.090871] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Machine has latest firmware (CoreBoot) And its Ubuntu is the latest LTS, kept up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 24 19:38:39 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation GeminiLake [UHD Graphics 605] [8086:2212] InstallationDate: Installed on 2022-04-26 (28 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Star Labs Lite ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash mitigations=off i915.enable_psr=0 vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2022 dmi.bios.release: 4.16 dmi.bios.vendor: coreboot dmi.bios.version: 4.16 dmi.board.name: Lite dmi.board.vendor: Star Labs dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Star Labs dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4: dmi.product.family: I4 dmi.product.name: Lite dmi.product.sku: I4 dmi.product.version: 1.0 dmi.sys.vendor: Star Labs version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
> It's a bit weird, https://launchpadlibrarian.net/602981658/nmcli-dev.txt
> shows no connection associated to the usb device nor IP for it
Thanks again Sebastien.
This may be because I booted the machine with the phone unplugged.
I can run apport again with the phone plugged in (and then reboot) to
duplicate the issue.
Would you like me to run apport again after booting with the phone
plugged in?
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions
--
Mailing list:
[Touch-packages] [Bug 1975566] Re: radeon / amdgpu bad performance or panics
The errors in comment #2 are kernel bugs so please also try the official Ubuntu kernel (5.15) instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+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 1975566] Re: radeon / amdgpu bad performance or panics
Thanks for the bug report. Please run: sudo apt install mesa-utils vulkan-tools glxinfo > glxinfo.txt vulkaninfo > vulkaninfo.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+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 1975566] [NEW] radeon / amdgpu bad performance or panics
Public bug reported: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy performance ubuntu uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in xorg package in Ubuntu: New Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be
[Touch-packages] [Bug 1975566] Re: radeon / amdgpu bad performance or panics
Already tried out some different things: - Tried the latest linux kernel - Fiddled with amdgpu & radeon kernel module options - Tried running the amdgpu kernel module instead of radeon Had to SSH into the machine to do anything (usually the system locks up). Some error messages from the fiddling: # kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=19833, emitted seq=19835 # kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1758 thread Xorg:cs0 pid 1798 # kernel: [drm] Fence fallback timer expired on ring sdma1 # kernel: [drm] Fence fallback timer expired on ring gfx -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
What's the status in 22.04? Wasn't it fixed in https://bugs.launchpad.net/ubuntu/+source/keyutils/1.6.1-2ubuntu3 ? Should we reopen for the current serie? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Released Status in keyutils source package in Focal: Incomplete Status in keyutils source package in Impish: Incomplete Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
you don't need to patch, just install the standard Ubuntu update provided on bug #1974428 -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
Thank you for your bug report, could you do
$ apport-collect 1975549
on the machine at the time you are having the issue?
** 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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975561] Re: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/1975561 Title: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: it automatically cme up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 24 06:39:36 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-05-13 (10 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) 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.8 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1975561/+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 1975566] Re: radeon / amdgpu bad performance or panics
** Attachment added: "vulkaninfo.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5592574/+files/vulkaninfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+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 1975578] [NEW] NetworkManager does not push search domains to systemd-resolved
Public bug reported: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: 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/1975578 Title: NetworkManager does not push search domains to systemd-resolved Status in network-manager package in Ubuntu: New Bug description: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975578/+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 1975566] Re: radeon / amdgpu bad performance or panics
OK so multiple problems there, which may have the same root cause: * Your shell/compositor seems to be causing stalling. * vulkaninfo says your GPU is "not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)" Sounds fundamentally like the kernel graphics driver isn't working. Please try the supported Ubuntu kernel instead. Also what desktop environment is this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+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 1975566] Re: radeon / amdgpu bad performance or panics
Noticed something quite weird when using the default kernel module (radeon). - when running glxgears, it starts running normally, but stalls quickly. If I active movement (hightling a part of my terminal and moving the mouse around simultaneously), it seems to skyrocket and run normally. Until I stop moving my mouse (which highlightning a piece of the terminal), then it stops running again (5FPS, not being re-drawn). - When using Firefox, it appears to 'stall' regularly. But if I hide the window, it seems like the page is being processed (for example when visiting a site) and when I show the window again, it is updated. This does not happen when the window is being showed, it just appears to hang. Additional piece of info: I have a 4K 60hz monitor. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+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 1975566] Re: radeon / amdgpu bad performance or panics
am currently using AwesomeWM ( https://awesomewm.org/ ) with LightDM. - when I ran the vulkaninfo this time, I temporarily switched back to 'stock' config (which is radeon, not amdgpu). So that might be correct. Should I switch to amdgpu and run it again? - between first post and now, I also switched back to the stock jammy kernel - thanks for the pointer about the compositor, didn't look into that yet. Checked and I didn't have a compositor installed (probably). So I installed "compton" as a compositor again (used it as well on my previous system), but that didn't help one bit (made it worse actually). So I uninstalled it again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+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 1975566] Re: radeon / amdgpu bad performance or panics
** Attachment added: "glxinfo.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5592573/+files/glxinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+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 1975566] Re: radeon / amdgpu bad performance or panics
** Attachment added: "lsmod.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5592575/+files/lsmod.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: radeon / amdgpu bad performance or panics Status in mesa package in Ubuntu: Incomplete Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+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 1974037] Re: openssl: EVP_EC_gen() segfault without init
** Changed in: openssl (Ubuntu Kinetic) Status: Confirmed => In Progress -- 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/1974037 Title: openssl: EVP_EC_gen() segfault without init Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: Confirmed Status in openssl source package in Kinetic: In Progress Status in openssl package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/1010958: Source: sscg Version: 3.0.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1 ... 1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11 SIGSEGV 04:32:21 MALLOC_PERTURB_=87 /<>/obj-x86_64-linux-gnu/generate_rsa_key_test ... Summary of Failures: 1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11 SIGSEGV Ok: 9 Expected Fail: 0 Fail: 1 Unexpected Pass:0 Skipped:0 Timeout:0 dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1 make: *** [debian/rules:6: binary-arch] Error 25 This has also been reported on the openssl-users mailing list: https://www.mail-archive.com/openssl-users@openssl.org/msg90830.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+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 1950095] Re: [github] 20.04: Apt fails to download URLs with non-encoded querystrings
I have used TJ's ppa for some months, and it worked flawlessly. Thanks TJ! Unfortunately, Ubuntu released 2.0.8 for focal, which overwrites 2.0.6.2 from TJ's ppa. Therefore, I created my own ppa[1]. My ppa is based on 2.0.8 and includes the same fixes as TJ's ppa. I've just tested it while updating the linux-surface kernel for one of my surface devices, and it worked as expected. I expect to maintain the ppa as long I use focal myself, which I expect to be at least one year from now, and possibly longer. [1]: https://launchpad.net/~gpxbv/+archive/ubuntu/apt-urlfix -- 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/1950095 Title: [github] 20.04: Apt fails to download URLs with non-encoded querystrings Status in apt package in Ubuntu: Fix Released Bug description: I've just helped a group of Ubuntu 20.04 users with Microsoft Surface devices. They rely upon a github repository releases pocket as the apt archive. Those users recently hit a bug "Ubuntu: Apt update fails with Error 401 Unauthorized" [1] The initial simple Github URL gets a Location: redirect to a complex URL with un-escaped query-string. The resulting complex URL causes apt to fail to fetch the resource. $ sudo apt upgrade -y Err:1 https://pkg.surfacelinux.com/debian release/main amd64 libwacom-surface amd64 1.12-2 401 Unauthorized [IP: 185.199.110.133 443] The URL can be manually corrected. One of the Surface users provided this example: bad: https://objects.githubusercontent.com/github-production-release- asset-2e65be/139604852/86019e52-7bfa-4bc6-8cc1-52147027aee6?X-Amz- Algorithm=AWS4-HMAC-SHA256 Credential=AKIAIWNJYAX4CSVEH53A/20211105/us- east-1/s3/aws4_request=20211105T161053Z Expires=300 Signature=2bc0c28946db539ada250b1030c37249dae909d73a68c90b5e7bfe7fecd5d347 SignedHeaders=host_id=0_id=0_id=139604852 content-disposition=attachment; filename=libwacom- surface_1.12-2_amd64.deb=application/octet- stream good: https://objects.githubusercontent.com/github-production-release- asset-2e65be/139604852/86019e52-7bfa-4bc6-8cc1-52147027aee6?X-Amz- Algorithm=AWS4-HMAC-SHA256 Credential=AKIAIWNJYAX4CSVEH53A%2F20211105%2Fus- east-1%2Fs3%2Faws4_request=20211105T160935Z Expires=300 Signature=44d9307e66dfb5b3672ee0082b8801ad2532ac4b6be61c3442fb265ffce72852 SignedHeaders=host_id=0_id=0_id=139604852 content-disposition=attachment%3B%20filename%3Dlibwacom- surface_1.12-2_amd64.deb=application%2Foctet- stream I found this also affects a github repository I recently added for Zotero on 20.04. The problem is fixed in later versions of apt upstream, in Debian and Ubuntu releases. I cherry-picked the 4 commits [3] and provided a package for Focal in my PPA [2] which multiple users have reported (in [1]) solves the issue. It would be really good to get those patches included in 20.04 as an SRU. As the code is in later versions of apt and is focused on the URL encoding only it has minimal potential for causing regressions. [1] https://github.com/linux-surface/linux-surface/issues/625 [2] https://launchpad.net/~tj/+archive/ubuntu/bugfixes [3] https://salsa.debian.org/apt- team/apt/-/commit/06ec0067057e0578f3bc515f6a97d6a9d70824f6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1950095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1974250] Re: ~/.pam_environment gets created as owned by root
** Information type changed from Private Security to Public Security ** Also affects: accountsservice (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Kinetic) Importance: High Status: Fix Released ** Changed in: accountsservice (Ubuntu Jammy) Status: New => Fix Released ** Changed in: accountsservice (Ubuntu Kinetic) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1974250 Title: ~/.pam_environment gets created as owned by root Status in accountsservice package in Ubuntu: Confirmed Status in accountsservice source package in Jammy: Fix Released Status in accountsservice source package in Kinetic: Confirmed Bug description: Something has happened lately with accountsservice, which makes it act as root instead of the current user when creating ~/.pam_environment. The very old bug #904395 comes to mind, and this smells a security issue. The function which is supposed to prevent this behavior is here: https://salsa.debian.org/freedesktop- team/accountsservice/-/blob/ubuntu/debian/patches/0010-set- language.patch#L75 Haven't investigated further yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1974250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967082] Re: SIGSEGV and out-of-bounds write during processing file via objdump
Hello, this is still working on the latest release of binutils for Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1967082 Title: SIGSEGV and out-of-bounds write during processing file via objdump Status in binutils package in Ubuntu: Incomplete Bug description: SIGSEGV and out-of-bounds write during processing file via objdump # Description During processing of the attached elf file via ``` objdump -S testcase ``` an out-of-bounds write is triggered and causes a segmentation fault (SIGSEGV) This allows an attacker to perform a denial of service and possibly opens up other attack vectors if files from untrusted sources are processed. For reproduction of the crash, I attached the following script(s): - reproduce-ubuntu.sh : Reproduction on Ubuntu 20.04 Since I was unable to reproduce the bug upstream, I report it here. If you need further assistance, please do not hesitate to ask. # Ubuntu version # apt show binutils Package: binutils Version: 2.34-6ubuntu1.3 Priority: optional Build-Essential: yes Section: devel Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Matthias Klose Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 110 kB Provides: binutils-gold, elf-binutils Depends: binutils-common (= 2.34-6ubuntu1.3), libbinutils (= 2.34-6ubuntu1.3), binutils-x86-64-linux-gnu (= 2.34-6ubuntu1.3) Suggests: binutils-doc (>= 2.34-6ubuntu1.3) Conflicts: binutils-mingw-w64-i686 (<< 2.23.52.20130612-1+3), binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3), binutils-multiarch (<< 2.27-8), modutils (<< 2.4.19-1) Homepage: https://www.gnu.org/software/binutils/ Task: ubuntustudio-video, ubuntu-mate-core, ubuntu-mate-desktop Download-Size: 3380 B APT-Manual-Installed: yes APT-Sources: http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages Description: GNU assembler, linker and binary utilities # Ubuntu valgrind ==1== Memcheck, a memory error detector ==1== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==1== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==1== Command: objdump -S /testcase ==1== objdump: warning: /testcase has a corrupt section with a size (3c3b031b01) larger than the file size objdump: /testcase: warning: loop in section dependencies detected objdump: warning: /testcase has a corrupt section with a size (3c3b031b01) larger than the file size ==1== Invalid write of size 4 ==1==at 0x4A40248: bfd_section_from_shdr (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x4A3BD4F: bfd_elf64_object_p (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x4A1AB01: bfd_check_format_matches (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x116402: ??? (in /usr/bin/x86_64-linux-gnu-objdump) ==1==by 0x116532: ??? (in /usr/bin/x86_64-linux-gnu-objdump) ==1==by 0x111B3C: ??? (in /usr/bin/x86_64-linux-gnu-objdump) ==1==by 0x4B360B2: (below main) (libc-start.c:308) ==1== Address 0x4d469f4 is 1,940 bytes inside a block of size 4,064 free'd ==1==at 0x483CA3F: free (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==1==by 0x4ABC85B: objalloc_free_block (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x4A1AABF: bfd_check_format_matches (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x116402: ??? (in /usr/bin/x86_64-linux-gnu-objdump) ==1==by 0x116532: ??? (in /usr/bin/x86_64-linux-gnu-objdump) ==1==by 0x111B3C: ??? (in /usr/bin/x86_64-linux-gnu-objdump) ==1==by 0x4B360B2: (below main) (libc-start.c:308) ==1== Block was alloc'd at ==1==at 0x483B7F3: malloc (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==1==by 0x4ABC65B: _objalloc_alloc (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x4A227D4: bfd_alloc (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x4A22CED: bfd_zalloc (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x4A41DE9: _bfd_elf_new_section_hook (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x4A2485E: ??? (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x4A40CEB: _bfd_elf_make_section_from_shdr (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x4A401DE: bfd_section_from_shdr (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x4A3BD4F: bfd_elf64_object_p (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x4A1AB01: bfd_check_format_matches (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so) ==1==by 0x116402: ??? (in /usr/bin/x86_64-linux-gnu-objdump) ==1==by 0x116532: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
Some updates, while I'm still investigating this on a QEMU running Ubuntu Core 22. The "snap auto-import" command is only needed on Ubuntu Core systems, so the plan is to remove the /lib/udev/rules.d/66-snapd-autoimport.rules from the snapd deb package (and consequently also from the snapd snap). We do still need it in UC, but as a matter of fact the script is already provided by the Ubuntu Core repositories: - UC22: https://github.com/snapcore/core-base/blob/main/static/usr/lib/udev/rules.d/66-snapd-autoimport.rules - UC20: https://github.com/snapcore/core20/blob/master/static/usr/lib/udev/rules.d/66-snapd-autoimport.rules - UC18: https://github.com/snapcore/core18/blob/master/static/lib/udev/rules.d/66-snapd-autoimport.rules - UC16: **missing** The file in UC22 seems already correct, in that it does not call unshare. So the only one left out is UC16, where we will add the udev rule that we currently have in snapd; after that, we will remove the rule from snapd and this bug for the desktop will be gone for good. There is a remaining problem, however: the systemd-udevd.service in Ubuntu 22 disallows the mount operation, so we'll have to update the unit file to allow it. I think we'll also need to update the auto-import command itself, because it appears that all errors while accessing the devices are silenced, so we would have never known of this problem, if it wasn't for this bug report. -- 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
** Also affects: libnotify (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libnotify (Ubuntu Bionic) Status: New => In Progress ** Changed in: libnotify (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: libnotify (Ubuntu Bionic) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Bionic: In Progress Status in libnotify source package in Focal: Fix Committed Status in libnotify source package in Jammy: Fix Committed Bug description: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap (or install it from the attached files to this bug): git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime To use the pre-built snap (https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7) snap install --dangerous notify-send-test-snap_*.snap Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path notify-send-test-snap.image-uri Ensure that desktop entry is correctly sent, monitoring the dbus session: In a terminal: dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" In the other: notify-send-test-snap.desktop-entry notify-send-test-snap.desktop-entry-explicit-id notify-send-test-snap.desktop-entry-explicit-file-name notify-send-test-snap.desktop-entry-explicit-path notify-send-test-snap.desktop-entry-explicit-uri notify-send-test-snap.desktop-entry-explicit-snapped-uri The `desktop-entry` value sent to dbus should be either: - A `notify-send-test-snap_`-prefixed desktop ID - A .desktop file path (readable from both inside and outside the snap) - A .desktop file uri (readable from both inside and outside the snap) [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1975587] [NEW] systemd: fix test-execute autotest failure with kernel 5.15 in focal
Public bug reported:
[Impact]
test-execute autotest is failing in focal with kernel 5.15. This is
because the following kernel commit changed the ABI for ioprio:
e70344c05995 ("block: fix default IO priority handling")
Previously setting IOPRIO_CLASS_NONE for a process would report
IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
IOPRIO_CLASS_BE instead.
[Test case]
Run systemd autopkgtest and check for the test-execute result.
[Fix]
Change test/test-execute/exec-ioschedulingclass-none.service to
recognize both "none" and "best-effort" as valid returned strings from
ionice.
This change is already available in jammy and above.
[Regression potential]
We may see regressions in systemd autopkgtest, we won't introduce any
potential regressions in systemd itself, because this is only affecting
the specific unit test.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/1975587
Title:
systemd: fix test-execute autotest failure with kernel 5.15 in focal
Status in systemd package in Ubuntu:
New
Bug description:
[Impact]
test-execute autotest is failing in focal with kernel 5.15. This is
because the following kernel commit changed the ABI for ioprio:
e70344c05995 ("block: fix default IO priority handling")
Previously setting IOPRIO_CLASS_NONE for a process would report
IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
IOPRIO_CLASS_BE instead.
[Test case]
Run systemd autopkgtest and check for the test-execute result.
[Fix]
Change test/test-execute/exec-ioschedulingclass-none.service to
recognize both "none" and "best-effort" as valid returned strings from
ionice.
This change is already available in jammy and above.
[Regression potential]
We may see regressions in systemd autopkgtest, we won't introduce any
potential regressions in systemd itself, because this is only
affecting the specific unit test.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+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 1970647] Re: notify-send exit code doesn't match result
On focal: ❯ apt-cache policy libnotify-bin libnotify-bin: Installato: 0.7.9-1ubuntu3.20.04.2 Candidato: 0.7.9-1ubuntu3.20.04.2 Tabella versione: *** 0.7.9-1ubuntu3.20.04.2 400 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.7.9-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ❯ env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo exit-error L'indirizzo fornito è vuoto exit-error ** Description changed: No error exit code is returned by notify-send on failure [ Test case ] 1. Run: -jhbuild run env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error + env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error 2. In a terminal "error" should be printed [ Regression potential ] Programs relying on notify-send may have errors when they did not. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1970647 Title: notify-send exit code doesn't match result Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Focal: Fix Committed Status in libnotify source package in Jammy: Fix Committed Bug description: No error exit code is returned by notify-send on failure [ Test case ] 1. Run: env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error 2. In a terminal "error" should be printed [ Regression potential ] Programs relying on notify-send may have errors when they did not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1970647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1974250] Re: ~/.pam_environment gets created as owned by root
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1974250 Title: ~/.pam_environment gets created as owned by root Status in accountsservice package in Ubuntu: Confirmed Status in accountsservice source package in Jammy: Fix Released Status in accountsservice source package in Kinetic: Confirmed Bug description: Something has happened lately with accountsservice, which makes it act as root instead of the current user when creating ~/.pam_environment. The very old bug #904395 comes to mind, and this smells a security issue. The function which is supposed to prevent this behavior is here: https://salsa.debian.org/freedesktop- team/accountsservice/-/blob/ubuntu/debian/patches/0010-set- language.patch#L75 Haven't investigated further yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1974250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal
This seems to fix the test failure.
** Patch added: "systemd-test-make-test-execute-pass-on-Linux-5.15.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592621/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.debdiff
** Patch removed: "systemd-test-make-test-execute-pass-on-Linux-5.15.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592620/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.patch
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/1975587
Title:
systemd: fix test-execute autotest failure with kernel 5.15 in focal
Status in systemd package in Ubuntu:
New
Status in systemd source package in Focal:
New
Bug description:
[Impact]
test-execute autotest is failing in focal with kernel 5.15. This is
because the following kernel commit changed the ABI for ioprio:
e70344c05995 ("block: fix default IO priority handling")
Previously setting IOPRIO_CLASS_NONE for a process would report
IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
IOPRIO_CLASS_BE instead.
[Test case]
Run systemd autopkgtest and check for the test-execute result.
[Fix]
Change test/test-execute/exec-ioschedulingclass-none.service to
recognize both "none" and "best-effort" as valid returned strings from
ionice.
This change is already available in jammy and above.
[Regression potential]
We may see regressions in systemd autopkgtest, we won't introduce any
potential regressions in systemd itself, because this is only
affecting the specific unit test.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+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 1975496] Re: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status
Thanks for taking the time to report this bug and trying to make Ubuntu better. >From the sshd logs in the description we can see: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 125: Bad configuration option: Host /etc/ssh/sshd_config: line 126: Bad configuration option: ForwardX11 /etc/ssh/sshd_config: terminating, 2 bad configuration options Which tells us that your sshd_config file has some bad configuration on line 125 and 126. Please, revisit your configuration file and fix it up. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- 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/1975496 Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: I had fixed an earlier problem with /etc/ssh/sshd_config but this error persists. I've tried removing the package, rebooting, and adding the openssh-server. package. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: firefox-locale-en:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 23 06:37:07 2022 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-10-06 (593 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 125: Bad configuration option: Host /etc/ssh/sshd_config: line 126: Bad configuration option: ForwardX11 /etc/ssh/sshd_config: terminating, 2 bad configuration options SourcePackage: openssh Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-09-29 (235 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1975496/+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 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal
** Patch added: "systemd-test-make-test-execute-pass-on-Linux-5.15.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592620/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.patch
--
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/1975587
Title:
systemd: fix test-execute autotest failure with kernel 5.15 in focal
Status in systemd package in Ubuntu:
New
Status in systemd source package in Focal:
New
Bug description:
[Impact]
test-execute autotest is failing in focal with kernel 5.15. This is
because the following kernel commit changed the ABI for ioprio:
e70344c05995 ("block: fix default IO priority handling")
Previously setting IOPRIO_CLASS_NONE for a process would report
IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
IOPRIO_CLASS_BE instead.
[Test case]
Run systemd autopkgtest and check for the test-execute result.
[Fix]
Change test/test-execute/exec-ioschedulingclass-none.service to
recognize both "none" and "best-effort" as valid returned strings from
ionice.
This change is already available in jammy and above.
[Regression potential]
We may see regressions in systemd autopkgtest, we won't introduce any
potential regressions in systemd itself, because this is only
affecting the specific unit test.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+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 1970647] Re: notify-send exit code doesn't match result
On Jammy: ❯ apt-cache policy libnotify4 libnotify4: Installato: 0.7.9-3ubuntu5.22.04.1 Candidato: 0.7.9-3ubuntu5.22.04.1 Tabella versione: *** 0.7.9-3ubuntu5.22.04.1 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.7.9-3ubuntu5 400 400 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ❯ env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo exit-error The given address is empty exit-error ** 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 libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1970647 Title: notify-send exit code doesn't match result Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Focal: Fix Committed Status in libnotify source package in Jammy: Fix Committed Bug description: No error exit code is returned by notify-send on failure [ Test case ] 1. Run: env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error 2. In a terminal "error" should be printed [ Regression potential ] Programs relying on notify-send may have errors when they did not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1970647/+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 1975557] [NEW] blank screen does not turn off display backlight
You have been subscribed to a public bug: I updated a system from 21.10 to 22.04 and noticed that when the screen is blanked by no keyboard or mouse activity that the backlight in the VGA monitor is still on. The "settings->Displays" has "Unknown Display" which I assume means the system does not know what commands to send to the monitor to shut it off. I booted a live DVD of 21.10 and the settings has the VGA display as 'AOC 22" ' which is correct and the screen blanking works correctly. So it seems that the definition for the AOC displays have been removed from 22.04. This behavior is different on Ubuntu 21.10, the VGA display is blank and the backlight is off. A minor nit is on 21.10 the "settings->Displays" shows the VGA display manufacture name, on 22.04 the VGA display manufacture name is "Unknown Display". I have discovered that the settings have the following options "settings->Power->Screen Blank" with a time value to be selected and the following text on the next line "Turns the screen off after a period of inactivity" "settings->Privacy->Screen->Blank Screen Display" with a time value to be selected and the following text on the next line "Period of inactivity after which the screen will go blank" The two options have different actions but seem to be connected because changing the time on one changes the time on the other. My guess is that the update changed the action for Ubuntu 22.04. I would like the 21.10 behavior, that is to turn off the VGA display not just blank the display when selecting the "settings->Power->Screen Blank" for 22.04. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- blank screen does not turn off display backlight https://bugs.launchpad.net/bugs/1975557 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1975557] Re: blank screen does not turn off display backlight
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1975557 Title: blank screen does not turn off display backlight Status in xorg package in Ubuntu: New Bug description: I updated a system from 21.10 to 22.04 and noticed that when the screen is blanked by no keyboard or mouse activity that the backlight in the VGA monitor is still on. The "settings->Displays" has "Unknown Display" which I assume means the system does not know what commands to send to the monitor to shut it off. I booted a live DVD of 21.10 and the settings has the VGA display as 'AOC 22" ' which is correct and the screen blanking works correctly. So it seems that the definition for the AOC displays have been removed from 22.04. This behavior is different on Ubuntu 21.10, the VGA display is blank and the backlight is off. A minor nit is on 21.10 the "settings->Displays" shows the VGA display manufacture name, on 22.04 the VGA display manufacture name is "Unknown Display". I have discovered that the settings have the following options "settings->Power->Screen Blank" with a time value to be selected and the following text on the next line "Turns the screen off after a period of inactivity" "settings->Privacy->Screen->Blank Screen Display" with a time value to be selected and the following text on the next line "Period of inactivity after which the screen will go blank" The two options have different actions but seem to be connected because changing the time on one changes the time on the other. My guess is that the update changed the action for Ubuntu 22.04. I would like the 21.10 behavior, that is to turn off the VGA display not just blank the display when selecting the "settings->Power->Screen Blank" for 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1975557/+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 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
Note that in kinetic we are switching to pipewire, unsure if that has the same issue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
All autopackage tests succeeded after multiple trials. Canonical customer with golang client against openssl server, where bug was first noticed, will be testing. -- 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/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Committed Bug description: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 The issue leads to various client failures with TLS 1.3 as described in, e.g. https://github.com/golang/go/issues/35722 https://github.com/golang/go/issues/34040 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1969375] Re: systemd-cryptenroll does not support TPM2 devices
This seems to be a really easy fix in the rules file. patch for version systemd_249.11-0ubuntu3: # diff -Naur rules.old rules.new --- rules.old 2022-03-08 14:53:55.0 +0100 +++ rules.new 2022-05-24 16:17:07.548254564 +0200 @@ -84,7 +84,7 @@ -Dfdisk=false \ -Dpwquality=false \ -Dp11kit=false \ - -Dtpm2=false \ + -Dtpm2=true \ -Doomd=true \ -Dsysext=true \ -Dnscd=true \ -- 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/1969375 Title: systemd-cryptenroll does not support TPM2 devices Status in systemd package in Ubuntu: Confirmed Bug description: systemd-cryptenroll can make use of tpm2 modules to bind against secure boot pcrs and enable auto unlocking of luks devices. Following the instructions here: https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll the following commands fail on ubuntu jammy (5.15.0-25-generic) root@testbox:~# systemd-cryptenroll --tpm2-device=list TPM2 not supported on this build. root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3 Please enter current passphrase for disk /dev/sda3: *** root@testbox:~# echo $? 1 It appears that this issue has been resolved in the debian build for systemd here: https://salsa.debian.org/systemd- team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8 Can we get the same modifications to the Jammy systemd build? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969375/+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 1560722] Re: repositórios sumiram
** Changed in: glib2.0 (Ubuntu) Status: New => Incomplete -- 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/1560722 Title: repositórios sumiram Status in glib2.0 package in Ubuntu: Incomplete Bug description: repositórios sumiram não sei o que fiz de errado. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-notification-daemon 1.12.1-1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 22 19:41:03 2016 ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon InstallationDate: Installed on 2016-03-22 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon Signal: 5 SourcePackage: mate-notification-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so Title: mate-notification-daemon crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1560722/+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 1974046] Re: Please merge wget 1.21.3 (main) from Debian unstable (main)
This bug was fixed in the package wget - 1.21.3-1ubuntu1 --- wget (1.21.3-1ubuntu1) kinetic; urgency=low * Merge from Debian unstable. Remaining changes: (LP: #1974046) - d/control: Don't Build-Depend on libgnutls28-dev, only on libssl-dev. - d/rules: Pass --with-ssl=openssl wget (1.21.3-1) unstable; urgency=medium * new upstream from 2022-02-26 * remove now included patch from 1.21.2-2 ssl_Removesupriousprintstatements_wget61125.patch -- Nathan Pratta Teodosio Wed, 18 May 2022 14:23:07 -0300 ** Changed in: wget (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1974046 Title: Please merge wget 1.21.3 (main) from Debian unstable (main) Status in wget package in Ubuntu: Fix Released Bug description: Please merge wget 1.21.3 from Debian stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1974046/+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 1975549] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592635/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] NetDevice.enp4s0.txt
apport information
** Attachment added: "NetDevice.enp4s0.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592638/+files/NetDevice.enp4s0.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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592646/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592644/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] PciNetwork.txt
apport information
** Attachment added: "PciNetwork.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592643/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592645/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] NetDevice.wlp3s0.txt
apport information
** Attachment added: "NetDevice.wlp3s0.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592641/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] NetDevice.usb0.txt
apport information
** Attachment added: "NetDevice.usb0.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592640/+files/NetDevice.usb0.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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
> Thank you for your bug report, could you do
>
> $ apport-collect 1975549
>
> on the machine at the time you are having the issue?
Thanks Sebastien.
This caught my eye (from the apport generated files):
Android phone:
* ID_NET_LINK_FILE=/usr/lib/systemd/network/73-usb-net-by-mac.link
NIC adapter:
* ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link
I can envision a situation where 73 is given higher precedence than 99.
What I don't know is, why things changed recently (assuming they were
the same way in the past).
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage
[Touch-packages] [Bug 1975578] Re: NetworkManager does not push search domains to systemd-resolved
The description should at least provide the Ubuntu serie you are using -- 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/1975578 Title: NetworkManager does not push search domains to systemd-resolved Status in network-manager package in Ubuntu: Incomplete Bug description: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975578/+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 1975578] Re: NetworkManager does not push search domains to systemd-resolved
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** 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/1975578 Title: NetworkManager does not push search domains to systemd-resolved Status in network-manager package in Ubuntu: Incomplete Bug description: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975578/+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 1970402] Re: Initrd out of memory error after upgrade to 22.04
Running on a laptop with 32GB of RAM. I noticed that my ramdisk was well over 100MB and I was getting this error. I'm not sure what the exact cause is, but I changed these two settings in /etc/initramfs- tools/initramfs.conf to the following values: MODULES=dep COMPRESS=lz4 (requires running "sudo apt install lz4" first) That decreased the size significantly, but it was still over 100MB. I ultimately had to uninstall the proprietary Nvidia driver and now my ramdisk is down to 60MB and I can boot normally. -- 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/1970402 Title: Initrd out of memory error after upgrade to 22.04 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: After upgrading to 22.04 system is unbootable because of "out of memory" error when loading initial ramdisk. I was able to fix it by editing cat /etc/initramfs-tools/initramfs.conf and changing configuration to: MODULES=dep COMPRESS=xz RUNSIZE=15% Not sure which one helped, but I can test it if needed. System information: Description:Ubuntu 22.04 LTS Release:22.04 initramfs-tools: Installed: 0.140ubuntu13 Candidate: 0.140ubuntu13 Version table: *** 0.140ubuntu13 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+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 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
apport information
** Tags added: apport-collected focal
** Description changed:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It literally
calls the connection "ethernet", as if it was using the network adapter.
This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called "ethernet"
instead of something more meaningful like "USB" or "Android" or "wired
hotspot".
The third item ("ethernet" name when using Android phone) was misleading
enough to waste a lot of time troubleshooting the issue. I thought I had
an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is the
Android phone uses Wifi and it is on a different VLAN and subnet to keep
traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.24
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2022-02-05 (107 days ago)
+ InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
+ IpRoute:
+ default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
+ 169.254.0.0/16 dev enp4s0 scope link metric 1000
+ 172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
+ Package: network-manager 1.22.10-1ubuntu2.3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
+ Tags: focal
+ Uname: Linux 5.13.0-44-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ nmcli-con:
+ NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
+ Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
+ nmcli-nm:
+ RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
+ running 1.22.10 connected started full enabled enabled
enabled enabled enabled
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592634/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android
[Touch-packages] [Bug 1975549] IpAddr.txt
apport information
** Attachment added: "IpAddr.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592636/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592637/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] NetDevice.lo.txt
apport information
** Attachment added: "NetDevice.lo.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592639/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] NetworkManager.conf.txt
apport information
** Attachment added: "NetworkManager.conf.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592642/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592647/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1975549] nmcli-dev.txt
apport information
** Attachment added: "nmcli-dev.txt"
https://bugs.launchpad.net/bugs/1975549/+attachment/5592648/+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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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 1619258] Re: netplan should allow NICs to be disconnected and not stall the boot
What is the actual fix for this. I have run into this multiple times. Is there a specific edit that needs to be made to the stanza in netplan? After reviewing the netplan docs I was unable to find a corresponding directive for allow-hotplug with /etc/network/interfaces. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.4 LTS Release:20.04 Codename: focal $ sudo dpkg --list | grep netplan ii libnetplan0:amd64 0.104-0ubuntu2~20.04.1 ii netplan.io0.104-0ubuntu2~20.04.1 ```yaml network: ethernets: eno1: dhcp4: true eno2: dhcp4: true eno3: dhcp4: true eno4: dhcp4: true enp130s0: dhcp4: true enp130s0d1: dhcp4: true enp134s0f0: dhcp4: true enp134s0f1: dhcp4: true enp135s0f0: dhcp4: true enp135s0f1: dhcp4: true version: 2 ``` -- 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/1619258 Title: netplan should allow NICs to be disconnected and not stall the boot Status in Snappy: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: in older snappy image we used to set "allow-hotplug" in /etc/network/interfaces.d/ when configuring a NIC to avoid the boot to completely stall or to be stuck for 5min when trying to find an internet connection. with recent versions of netplan the configuration seems to be back to require a network to be up before moving on with them boot so that booting takes forever until the network connection times out. netplan should make the system check the physical link status when trying to bring up a network device instead of stalling the boot. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1619258/+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 1975614] [NEW] audispd daemon missing in 22.04
Public bug reported: audispd was part of auditd package in 20.04. In 22.04 it is not anymore. Moreover, it is not part of any package according to "apt-file search audispd". ** Affects: audit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1975614 Title: audispd daemon missing in 22.04 Status in audit package in Ubuntu: New Bug description: audispd was part of auditd package in 20.04. In 22.04 it is not anymore. Moreover, it is not part of any package according to "apt-file search audispd". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1975614/+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 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal
** Tags added: patch
--
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/1975587
Title:
systemd: fix test-execute autotest failure with kernel 5.15 in focal
Status in systemd package in Ubuntu:
New
Status in systemd source package in Focal:
New
Bug description:
[Impact]
test-execute autotest is failing in focal with kernel 5.15. This is
because the following kernel commit changed the ABI for ioprio:
e70344c05995 ("block: fix default IO priority handling")
Previously setting IOPRIO_CLASS_NONE for a process would report
IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
IOPRIO_CLASS_BE instead.
[Test case]
Run systemd autopkgtest and check for the test-execute result.
[Fix]
Change test/test-execute/exec-ioschedulingclass-none.service to
recognize both "none" and "best-effort" as valid returned strings from
ionice.
This change is already available in jammy and above.
[Regression potential]
We may see regressions in systemd autopkgtest, we won't introduce any
potential regressions in systemd itself, because this is only
affecting the specific unit test.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+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 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
It's a bit weird, https://launchpadlibrarian.net/602981658/nmcli-dev.txt
shows no connection associated to the usb device nor IP for it
** 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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+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
