[Bug 1960605] Re: System freeze
In the original post I've added the last lines of the syslog which came to me with ssh. The last lines did not even make it to the disk. After the user starts at the welcome screen on Jan 22 10:31:03 the system halts at Jan 22 10:31:10. Yesterday (20220215) the system booted without any problem. Today I tried to reproduce the problem. After five times rebooting without problems I looked at the /var/log/apt/history.log and found the latest upgrade: Start-Date: 2022-02-14 19:34:26 Commandline: apt upgrade Upgrade: libdrm-nouveau2:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libegl-mesa0:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libglapi-mesa:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), ubuntu-advantage-tools:amd64 (27.5~20.04.1, 27.6~20.04.1), python-apt-common:amd64 (2.0.0ubuntu0.20.04.6, 2.0.0ubuntu0.20.04.7), libxatracker2:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libegl1-mesa:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libgbm1:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libdrm-amdgpu1:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), python3-distupgrade:amd64 (1:20.04.36, 1:20.04.37), ubuntu-release-upgrader-core:amd64 (1:20.04.36, 1:20.04.37), firefox-locale-en:amd64 (96.0+build2-0ubuntu0.20.04.1, 97.0+build2-0ubuntu0.20.04.1), firefox-locale-nl:amd64 (96.0+build2-0ubuntu0.20.04.1, 97.0+build2-0ubuntu0.20.04.1), libdrm2:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libgl1-mesa-dri:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libgl1-mesa-glx:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), ubuntu-release-upgrader-gtk:amd64 (1:20.04.36, 1:20.04.37), libdrm-intel1:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), firefox:amd64 (96.0+build2-0ubuntu0.20.04.1, 97.0+build2-0ubuntu0.20.04.1), libdrm-radeon1:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), mesa-vdpau-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), linux-firmware:amd64 (1.187.25, 1.187.26), mesa-vulkan-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), python3-apt:amd64 (2.0.0ubuntu0.20.04.6, 2.0.0ubuntu0.20.04.7), mesa-va-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libglx-mesa0:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libdrm-common:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1) End-Date: 2022-02-14 19:35:09 Perhaps the problem is solved with one of the patches? The system is also new root@pavilion:~# inxi -F System:Host: pavilion Kernel: 5.13.0-28-generic x86_64 bits: 64 Console: tty 1 Distro: Ubuntu 20.04.3 LTS (Focal Fossa) Machine: Type: Laptop System: HP product: HP Pavilion Gaming Laptop 17-cd1xxx v: Type1ProductConfigId serial: CND1191BY1 Mobo: HP model: 8745 v: 03.34 serial: PJWEUC61UF502Q UEFI: Insyde v: F.21 date: 01/08/2021 Battery: ID-1: BAT1 charge: 43.4 Wh condition: 43.4/52.5 Wh (83%) CPU: Topology: 6-Core model: Intel Core i7-10750H bits: 64 type: MT MCP L2 cache: 12.0 MiB Speed: 820 MHz min/max: 800/5000 MHz Core speeds (MHz): 1: 3300 2: 2869 3: 1139 4: 800 5: 800 6: 936 7: 1056 8: 1342 9: 843 10: 1572 11: 1072 12: 800 Graphics: Device-1: Intel UHD Graphics driver: i915 v: kernel Device-2: NVIDIA driver: nvidia v: 470.86 Display: server: X.org 1.20.13 driver: modesetting,nouveau unloaded: fbdev,vesa tty: 169x38 Message: Advanced graphics data unavailable in console for root. Audio: Device-1: Intel Comet Lake PCH cAVS driver: snd_hda_intel Device-2: NVIDIA driver: snd_hda_intel Sound Server: ALSA v: k5.13.0-28-generic Network: Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi IF: wlo1 state: up mac: 14:18:c3:78:64:0f Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eno1 state: up speed: 100 Mbps duplex: full mac: 48:9e:bd:0e:96:1d Drives:Local Storage: total: 2.05 TiB used: 1.05 TiB (50.9%) ID-1: /dev/nvme0n1 vendor: SK Hynix model: PC601 HFS256GD9TNG-L2A0A size: 238.47 GiB ID-2: /dev/sda vendor: Seagate model: ST1000LM049-2GH172 size: 931.51 GiB ID-3: /dev/sdb type: USB vendor: Seagate model: BUP Slim SL size: 931.51 GiB RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci Partition: ID-1: / size: 233.73 GiB used: 91.28 GiB (39.1%) fs: ext4 dev: /dev/nvme0n1p1 Sensors: System Temperatures: cpu: 33.0 C mobo: 10.0 C Fan Speeds (RPM): N/A Info: Processes: 415 Uptime: 27m Memory: 15.43 GiB used: 2.41 GiB (15.6%) Init: systemd runlevel: 5 Shell: bash inxi: 3.0.38 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960605 Title: System freeze To manage notifications a
[Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
Now we're using test source code from the archive: https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client- tests/commit/?id=1d85c48bb9f6406313b32bcdc76d31efc5461995 ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1960094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961023] [NEW] [MIR] glade
Public bug reported: Either glade should be promoted or libhandy should remove the dep. TBD ** Affects: glade (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961023 Title: [MIR] glade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glade/+bug/1961023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959581] Re: OCFS2 intermittently not mountable on a second Node in Ubuntu 20.04.3 LTS
Thanks @all for not leaving me alone with this issue! Open-iscsi versions: Ubuntu 20.04.3 LTS: 2.0.874-7.1ubuntu6.2 Ubuntu 18.04.6 LTS: 2.0.874-5ubuntu2.10 (Oracle Linux Server 7.9: 6.2.0.874-22) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959581 Title: OCFS2 intermittently not mountable on a second Node in Ubuntu 20.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1959581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960933] Re: rtw89_pci constantly drops connection with old firmware
** Tags added: kern-2469 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960933 Title: rtw89_pci constantly drops connection with old firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953507] Re: [radeon] jammy live - on adjusting display config; one display is unsuable blocky-mess
so this is with X, what about the wayland session which should be the default? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953507 Title: [radeon] jammy live - on adjusting display config; one display is unsuable blocky-mess To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1953507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958019]
(In reply to Lucas Tanure from comment #539) > Hi, > > We are waiting for this patch series to be merged: > > https://lkml.org/lkml/2022/1/21/471 > > Thanks > Lucas Hi, just wanted to confirm, adding these patches on top of 5.17-rc4 works for me on my 2021 Legion 7 (AMD). This is running Ubuntu 21.04. I grabbed the kernel source from the Ubuntu tree, as linked here https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.17-rc4/ And built following the instructions here https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel In the editconfigs step you have to navigate in menuconfig to Device Drivers / X86 Platform Specific Device Drivers / I2C and SPI multi instantiate pseudo device driver and select that module. Then Exit/Save the config and build. It takes a few minutes to build, but the process goes smoothly. Thanks for getting this working! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961024] [NEW] Sync liquidsoap 2.0.2-1 (universe) from Debian unstable (main)
Public bug reported:
Please sync liquidsoap 2.0.2-1 (universe) from Debian unstable (main)
All changelog entries:
liquidsoap (2.0.2-1) unstable; urgency=medium
* New upstream version 2.0.2 (Closes: #1002677)
* Refresh d/patches
* Update d/control with new build-dep versions
* Update d/liquidsoap.links for new version
* Update autopkgtests for new language features
-- Kyle Robbertze Tue, 11 Jan 2022 11:00:10
+0200
liquidsoap (1.4.4-1) unstable; urgency=low
* Update watchfile
* New upstream version 1.4.4
* Update pervasive library links
* Upstream moved homepage location
* Drop Breaks/Replaces for Bookworm
-- Kyle Robbertze Sun, 15 Aug 2021 08:18:42
+0200
liquidsoap (1.4.3-3) unstable; urgency=medium
* Fix pervasive libraries symlink (Closes: 991332)
-- Kyle Robbertze Wed, 21 Jul 2021 16:18:07
+0200
liquidsoap (1.4.3-2) unstable; urgency=medium
* Set BYTE install correctly (Closes: #972272)
* Fix FTBFS type error (Closes: #976355)
* Bump standards-version to 4.5.1 (no change)
-- Kyle Robbertze Tue, 22 Dec 2020 09:17:12
+0200
liquidsoap (1.4.3-1) unstable; urgency=medium
* Update watch file
* New upstream version 1.4.3
* Fix compilation with ocaml-alsa 0.3.0
* Bump dh-compat to 13
-- Kyle Robbertze Mon, 05 Oct 2020 17:46:58
+0200
liquidsoap (1.4.2-1) unstable; urgency=low
* Link pervasive libraries into expected directory
(Closes: #956564, LP: #1875414)
* New upstream version 1.4.2
-- Kyle Robbertze Fri, 22 May 2020 12:12:19
+0200
liquidsoap (1.4.1-1) unstable; urgency=medium
* Install bash completions into packaging dir (Closes: #945246)
* New upstream version 1.4.1
* Bump Standards-Version to 4.5.0 (No change)
-- Kyle Robbertze Wed, 22 Jan 2020 14:04:09
+0200
liquidsoap (1.4.0-1) unstable; urgency=medium
* Ignore bundled releases in watch file
* New upstream version 1.4.0 (Closes: #939580)
* Update dependencies
* Refresh patches
* Use local copy of language.dtd file
* Add patch to work around missing upstream files
* Update install files for new release
* Remove rpath from binary
* Bump Standards-Version to 4.4.1 (no change)
-- Kyle Robbertze Mon, 11 Nov 2019 09:27:17
+0200
liquidsoap (1.3.7-1) unstable; urgency=medium
[ Kyle Robbertze ]
* Drop unsatisfiable recommends on mp3gain
* New upstream version 1.3.7
* Install changelog
* Update dependencies (Closes: #909448)
* Move to debhelper-compat
* Bump Standards-Version to 4.4.0 (No change)
* Patch out syntax error
* Declare recommends on emacs for elpa package
* Refresh patches
* Install example scripts
[ Stephane Glondu ]
* Remove Samuel and Romain from Uploaders
[ Kyle Robbertze ]
* Add override for ocaml-ssl
* Install extract-replaygain correctly
* Drop dh-exec useless build-dependency
* Update copyright years
* Drop DSSI support
-- Kyle Robbertze Mon, 19 Aug 2019 22:42:52
+0200
liquidsoap (1.3.4-1) unstable; urgency=medium
* Remove /usr/share/liquidsoap on purge (Closes: #668751)
* New upstream version 1.3.4
* Bump camomile version
* Bump Standards-Version (no change)
-- Kyle Robbertze Sun, 17 Feb 2019 17:35:44
+0200
liquidsoap (1.3.3-2) unstable; urgency=medium
* Fix build errors on armel and mips*
* Bump Standards-Version (no change)
* Include Breaks/Replaces for old plugin packages
-- Kyle Robbertze Tue, 04 Sep 2018 20:35:40
+0200
liquidsoap (1.3.3-1) unstable; urgency=medium
* New upstream release (closes: #878896, #841871, LP: #378151)
* Remove outdated note about MP3 encoding (closes: #721639)
* Make copyright machine readable
* Drop unmaintained liguidsoap binary package
* Drop unsupported dynamic plugins for static ones
* Bump compat to 10 (no change)
* Bump standards version to 4.2.0 (fix user management)
* Add user to audio group (closes: #827218)
* Convert to use dh
* Add new uploader
-- Kyle Robbertze Mon, 06 Aug 2018 15:29:41
+0200
liquidsoap (1.1.1-7) unstable; urgency=medium
* Patch shine encoder to adapt to new ABI.
-- Romain Beauxis Mon, 11 Aug 2014 20:07:58
-0500
liquidsoap (1.1.1-6) unstable; urgency=low
* Bring back SDL plugin.
-- Romain Beauxis Tue, 11 Jun 2013 18:17:55
-0500
liquidsoap (1.1.1-5) unstable; urgency=low
* Switch GD build-dep to libgd-ocaml-dev.
* Provide alternative build-dep on libgd-gd2-ocaml-dev.
* Bump build-dep on camlimages.
* Drop optional SDL plugin until SDL and gd become compatible
again (conflicts on libtiff{4,5}-dev).
-- Romain Beauxis Wed, 15 May 2013 07:06:38
-0500
liquidsoap (1.1.1-4) unstable; urgency=low
* Added patch to enable dynamically loaded
fdkaac encoder.
* Dropped liquidsoap-plugin-fdkaac.
Closes: #708602
-- Romain Beauxis Tue, 14 May 2013 17:19:49
-0500
liquidsoap (1.1.1-3) unstable; urgency=low
* Added liquidsoap emacs mode package.
* Merge changes from NMU 1.0.1+repack1-1.1
* Added liquidsoap-plugin-fdkaac
-- Romain Beau
[Bug 1960926] Re: [VROC] Installation on RAID volume fails - ubuntu 22.04
** Attachment added: "20.04 sosreport and journal info" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1960926/+attachment/5561251/+files/20.04%20sosreport%20and%20journal.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960926 Title: [VROC] Installation on RAID volume fails - ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1960926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959102] Re: Kernel fails to boot in ScalingStack
This bug is awaiting verification that the linux-raspi/5.4.0-1053.60 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959102 Title: Kernel fails to boot in ScalingStack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1959102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933532] Re: Large Page support disabled on Raspberry Pi kernels
This bug is awaiting verification that the linux-raspi/5.4.0-1053.60 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933532 Title: Large Page support disabled on Raspberry Pi kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1933532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920847] Re: ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20200528/psparse-529)
same issue on Dell XPS 15-i9. using kernel 5.13.0-28-generic. These three errors appear in dmesg, usually in succession. ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20210331/psparse-529) i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=432243 end=432244) time 843 us, min 2385, max 2399, scanline start 2345, end 0 ACPI Error: Thread 1882606336 cannot release Mutex [ECMX] acquired by thread 2269184000 (20210331/exmutex-378) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920847 Title: ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20200528/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1920847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960182] Re: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-z-systems Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960182 Title: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961026] [NEW] xsane GUI window too small on startup
Public bug reported: When starting xsane, the main GUI window comes up with a size too small to show all controls. Enlarging the window to adequate size works, but it has to be done every time xsane ist started. I could not find in the resources how to fix that. This bug is new since Ubuntu 20.04 (compared to 16.04) ** Affects: xsane (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961026 Title: xsane GUI window too small on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/1961026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960933] Re: rtw89_pci constantly drops connection with old firmware
** Also affects: linux-firmware (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
** Description changed:
+ [Impact]
+
This was on a new Lenovo P14s Gen2 AMD. I'm using Ubuntu 21.10 (impish)
The current linux-firmware package (1.201.4+1.201.3) ships with realtek
rtw89_pci firmware (/lib/firmware/rtw89/rtw8852a_fw.bin) version
v0.13.8.0.
My wifi chip wasn't able to keep a connection for more than a minute when
connected to a Rodgers "Advanced Wi-Fi Modem". I searched around tried
disabling the power_save and stuff. But that had little to no effect. I was
about to open an issue on the upstream project and did a last ditch attempt to
see if there were any firmware updates... I found linux-firmware.git and it had
- two newer versions!
+ two newer versions!
- - v0.13.30.0 (was submitted in May 2021, but it took until october 2021 to
show up)
+ - v0.13.30.0 (was submitted in May 2021, but it took until october 2021 to
show up)
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=ec17b637b7ab928ca7ebc0389e0e3921f1cc7d17
- - v0.13.33.0 (was submitted in November 2021 and got merged in December
2021):
+ - v0.13.33.0 (was submitted in November 2021 and got merged in December
2021):
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=4a7e1f5cabaebe5c044b94b91149f35471d1e983
I've downloaded and installed the latest "v0.13.33.0" on a whim and
rebooted. And what a pleasant surprise: Instantly, my wifi connection
lasted until the rest of the day.
Could you please consider updating this realtek firmware in the next
release? Thanks!
+
+ [Test Case]
+
+ See above.
+
+ [Fix]
+
+ Cherry pick two commit to match current Jammy:
+ 4a7e1f5cabae ("rtw89: 8852a: update fw to v0.13.33.0")
+ ec17b637b7ab ("rtw89: 8852a: update fw to v0.13.30.0")
+
+ [Where Problems Could Occur]
+
+ Limited to wifi using RTL8852A HW.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960933
Title:
rtw89_pci constantly drops connection with old firmware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960933/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960875] Re: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call
** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: High Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960875 Title: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960605] Re: System freeze
Please follow the instructions in comment #4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960605 Title: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960926] Re: [VROC] Installation on RAID volume fails - ubuntu 22.04
Oh, it looks like this is caused by this upstream mdadm change: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=1a52f1fc0266d438c996789d4addbfac999a6139. I guess the installer can't rely on udev for array memebership information and will have to run mdadm --detail or similar itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960926 Title: [VROC] Installation on RAID volume fails - ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1960926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954757] Re: Missing overlays/README
** Changed in: linux-raspi (Ubuntu Hirsute) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954757 Title: Missing overlays/README To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1954757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960984] Re: [oneAPI] VPL user space package integrated
also available on ppa:canonical-x/x-staging feel free to test -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960984 Title: [oneAPI] VPL user space package integrated To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1960984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958109] Re: [MIR] v4l2-relayd
I subscribed https://bugs.launchpad.net/ubuntu/+source/v4l2-relayd for https://launchpad.net/~canonical-mainstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958109 Title: [MIR] v4l2-relayd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961027] Re: [FFE] merge virt-manger >3.2 for Jammy once released
Can we pre-acknowledge that way to go, or do you (ubuntu-release) need/want to wait until there is a new release and I can provide that usual requested PPA build, full Diff and install log? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961027 Title: [FFE] merge virt-manger >3.2 for Jammy once released To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1961027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961027] [NEW] [FFE] merge virt-manger >3.2 for Jammy once released
Public bug reported: Hi, virt-manager 3.2 is out for more than a year now and upstream git includes many fixes. That was brought up upstream in [1] already and the estimation is somewhere around our feature freeze [2]. But we also need time to do this in Debian and test it and so on, therefore to be transparent and prepared I wanted to file an FFe bug right away. As there is no release yet I can't provide a diff just yet, but main [3] vs the 3.2 tag [4] shows this and the many fixes and improvements contained. [1]: https://listman.redhat.com/archives/virt-tools-list/2022-January/msg00016.html [2]: https://listman.redhat.com/archives/virt-tools-list/2022-January/msg00017.html [3]: https://github.com/virt-manager/virt-manager/commits/main [4]: https://github.com/virt-manager/virt-manager/commit/cd788e93030a6c24934c96851b23af59c12dc2a7 ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961027 Title: [FFE] merge virt-manger >3.2 for Jammy once released To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1961027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961027] Re: [FFE] merge virt-manger >3.2 for Jammy once released
FYI related to bug 1959976 (asking for features that are in git but not released yet). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961027 Title: [FFE] merge virt-manger >3.2 for Jammy once released To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1961027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961027] Re: [FFE] merge virt-manger >3.2 for Jammy once released
FYI - I pinged upstream again asking for an updated ETA on the new release, see [1] [1]: https://listman.redhat.com/archives/virt-tools- list/2022-February/msg00020.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961027 Title: [FFE] merge virt-manger >3.2 for Jammy once released To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1961027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960083] Re: dirname applet missing from initramfs
Hello Oh!!! jammy-desktop-amd64.iso 2022-02-16 08:353.1GDesktop image for 64-bit PC (AMD64) computers (standard download) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960083 Title: dirname applet missing from initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959569] Re: Focal update: upstream stable patchset 2022-01-31
** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959569 Title: Focal update: upstream stable patchset 2022-01-31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1959569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1118815] Re: Remove python-oauth from the archive
** Changed in: python-oauth (Ubuntu) Importance: Undecided => Medium ** Changed in: python-oauth (Ubuntu) Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro) ** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1118815 Title: Remove python-oauth from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1118815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961030] [NEW] Default firewall rules with firewalld are differnt to the ones with ufw
Public bug reported: I'm no expert on firewalls. But coming from Fedora, I found ufw more complicated than firewalld. So I did run "apt remove ufw" and "apt install firewalld" to replace ufw with firewalld, which I'm more familiar with. I don't expect this operation to change the actual firewall rules, but I found it did. Not by some detailed analysis of the rules, but by the fact that when using firewalld my printer is not detected. I have never installed any driver. AFAIK my printer can be used, as any half modern one, via "IPP Everywhere". So it would seem the default firewalld configuration differs from the ufw, at the very least, in it breaking "IPP Everywhere" support. That same printer was detected from Fedora, using firewalld. For referece: https://src.fedoraproject.org/rpms/firewalld/tree/rawhide ** Affects: firewalld (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961030 Title: Default firewall rules with firewalld are differnt to the ones with ufw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firewalld/+bug/1961030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961033] [NEW] upgrade fail
Public bug reported: from 18.04 upgrade fail ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.45 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 Uname: Linux 5.4.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CrashDB: ubuntu Date: Wed Feb 16 17:08:48 2022 InstallationDate: Installed on 2021-09-30 (138 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2022-02-16 (0 days ago) VarLogDistupgradeAptlog: Log time: 2022-02-16 17:08:02.526154 Log time: 2022-02-16 17:08:07.034890 Log time: 2022-02-16 17:08:48.483384 Log time: 2022-02-16 17:08:51.954301 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961033 Title: upgrade fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1961033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961034] [NEW] Cursor occasionally gets stuck in drag mode
Public bug reported: If I press the left mouse button over something draggable, move it slightly (the shorter the distance the more often it happens), and release it quickly after it, the cursor would occasionally get stuck in the drag mode. Clicking somewhere or pressing Esc returns it to the normal state. For example, I want to click something, but the mouse is moving slightly during the click, resulting in the drag. Even though the left mouse button is released after the click, the cursor gets stuck in the drag mode, even though the button release was registered via `xinput --test- xi2 --root`. This causes constant annoying text drops / links to the desktop, copying something to somewhere else accidentally. This happens many times a day. I'm using a graphics tablet (Wacom C480) and a mouse. This is reproducible with both. `gsettings set org.gnome.settings-daemon.plugins.cursor active false` doesn't help. This is the video of the issue: https://emalm.com/?v=DsBSK System: Kernel: 5.13.0-27-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.2.7 wm: muffin 5.2.0 dm: LightDM 1.30.0 Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal Machine: Type: Desktop Mobo: Gigabyte model: X570 GAMING X v: x.x serial: UEFI: American Megatrends LLC. v: F35 date: 07/08/2021 CPU: Topology: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 182069 Speed: 3231 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 3231 2: 2405 3: 2195 4: 2196 5: 2259 6: 2196 7: 2195 8: 2028 9: 3593 10: 2034 11: 2196 12: 2195 13: 2328 14: 2196 15: 2195 16: 2196 17: 2195 18: 2075 19: 2197 20: 2195 21: 2195 22: 2196 23: 2196 24: 2201 Graphics: Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] vendor: ASUSTeK driver: nvidia v: 510.47.03 bus ID: 08:00.0 chip ID: 10de:1380 Display: x11 server: X.Org 1.20.13 driver: nvidia resolution: 1920x1080~60Hz, 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: NVIDIA GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 510.47.03 direct render: Yes ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: - If I press the left mouse button over something draggable, and release - it quickly after it, the cursor would occasionally get stuck in the drag - mode. Clicking somewhere or pressing Esc returns it to the normal state. + If I press the left mouse button over something draggable, move it + slightly (the shorter the distance the more often it happens), and + release it quickly after it, the cursor would occasionally get stuck in + the drag mode. Clicking somewhere or pressing Esc returns it to the + normal state. For example, I want to click something, but the mouse is moving slightly during the click, resulting in the drag. Even though the left mouse button is released after the click, the cursor gets stuck in the drag mode, even though the button release was registered via `xinput --test- xi2 --root`. This causes constant annoying text drops / links to the desktop, copying something to somewhere else accidentally. This happens many times a day. I'm using a graphics tablet (Wacom C480) and a mouse. This is reproducible with both. `gsettings set org.gnome.settings-daemon.plugins.cursor active false` doesn't help. This is the video of the issue: https://emalm.com/?v=DsBSK System: - Kernel: 5.13.0-27-generic x86_64 bits: 64 compiler: N/A - Desktop: Cinnamon 5.2.7 wm: muffin 5.2.0 dm: LightDM 1.30.0 - Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal + Kernel: 5.13.0-27-generic x86_64 bits: 64 compiler: N/A + Desktop: Cinnamon 5.2.7 wm: muffin 5.2.0 dm: LightDM 1.30.0 + Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal Machine: - Type: Desktop Mobo: Gigabyte model: X570 GAMING X v: x.x - serial: UEFI: American Megatrends LLC. v: F35 - date: 07/08/2021 + Type: Desktop Mobo: Gigabyte model: X570 GAMING X v: x.x + serial: UEFI: American Megatrends LLC. v: F35 + date: 07/08/2021 CPU: - Topology: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP - arch: Zen L2 cache: 6144 KiB - flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 - svm - bogomips: 182069 - Speed: 3231 MHz min/max: 2200/3800 MHz boost: enabled - Core speeds (MHz): 1: 3231 2: 2405 3: 2195 4: 2196 5: 2259 6: 2196 - 7: 2195 8: 2028 9: 3593 10: 2034 11: 2196 12: 2195 13: 2328 - 14: 2196 15: 2195 16: 2196 17: 2195 18: 2075 19: 2197 20: 2195 - 21: 2195 22: 2196 23: 2196 24: 2201 + Topology: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP + arch: Zen L2 cache: 6144 KiB + flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 + svm + bogomips: 182069 + Speed: 3231 MHz min/max: 2200/3800 MHz boost: enabled + Core speeds (MHz): 1: 3231 2: 2405 3: 2195 4: 2196 5: 2259 6: 2196 + 7: 2195 8: 2028 9:
[Bug 1961037] [NEW] WiFi and Bluetooth drivers issue
Public bug reported: We want to inform you that we are facing issue of WiFi and BT drivers in upper kernel of Linux Ubuntu 18.04.6 LTS (5.4.0-84-generic). Till this kernel 5.4.0.84-generic, All working smooth. We have tried latest one 5.4.0.97 as well but not fixed. Please help to fix. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "version.zip" https://bugs.launchpad.net/bugs/1961037/+attachment/5561308/+files/version.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1961037 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954938] Re: Include the QCA WCN 6856 v2.1 support
verified linux-oem-5.14/focal-proposed version 5.14.0-1023.25. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954938 Title: Include the QCA WCN 6856 v2.1 support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942789] Re: On-demand and RTD3 need to be separated
** Changed in: nvidia-prime (Ubuntu Hirsute) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961039] [NEW] Brightness control with integrated AMD GPU and NVidia GPU
Public bug reported: System information -- Distributor ID: Ubuntu Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 Codename: jammy Integrated AMD GPU: AMD Ryzen 7 5800H with Radeon Graphics GPU : NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] with nvidia-driver-510 Description of the problem -- I can't change the brightness of the screen using the hot keys or the settings menu. It is clear that these buttons are acting on the value stored in /sys/class/backlight/nvidia_0/brightness, but has no effect on the actual brightness. However, modifying manually the value in /sys/class/backlight/amdgpu_bl0/brightness changes the actual brightness. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd-gpu brightness nvidia -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961039 Title: Brightness control with integrated AMD GPU and NVidia GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1961039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955844] Re: Enlightenment cannot successfully start the enlightenment_system service since it can't become group root. Missing setuid bit?
e17 is the short name for enlightenment 0.17, so it is a version. e17 is located in universe and is only available for Bionic, but has reached EoS years ago. The package e17 was last updated 5 1/2 years ago. https://packages.ubuntu.com/search?keywords=e17&searchon=names&suite=all§ion=all "LTS" is promised anyway only for main and restricted. The name for the source package "e17 (0.25.3-1)" is a contradiction in terms, simply nonsense. The binary deb package is called enlightenment for Focal, Hirsute, Impish, and Jammy. You should specify this correctly. https://packages.ubuntu.com/search?keywords=enlightenment&searchon=names&suite=all§ion=all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955844 Title: Enlightenment cannot successfully start the enlightenment_system service since it can't become group root. Missing setuid bit? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e17/+bug/1955844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959419] Re: [22.04 FEAT] Upgrade openCryptoki to latest version (>= 3.17)
Uploaded, thanks! ** Changed in: opencryptoki (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959419 Title: [22.04 FEAT] Upgrade openCryptoki to latest version (>= 3.17) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955844] Re: Enlightenment cannot successfully start the enlightenment_system service since it can't become group root. Missing setuid bit?
Your bug report is a month and a half old with enlightenment 0.24.2-8. A development version is in constant movement. Installable now is enlightenment 0.25.3-1. I also had pointed out the following: > Possibly the cause is how enlightenment was installed, > root or sudo, tty or terminal (so with running DE). > > So the question is if you can reproduce the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955844 Title: Enlightenment cannot successfully start the enlightenment_system service since it can't become group root. Missing setuid bit? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e17/+bug/1955844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953575] Re: Update gvnic driver code
** Changed in: linux-gcp (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953575 Title: Update gvnic driver code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1953575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960814] Re: Sync tigervnc 1.12.0+dfsg-2 (universe) from Debian unstable (main)
Meanwhile tigervnc v1.12 landed in jammy, hence closing this ticket as Fix Released. ** Changed in: tigervnc (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960814 Title: Sync tigervnc 1.12.0+dfsg-2 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960937] Re: Libvirtd on 20.04 does not listen on port 16509
Digging into this a bit more, it looks like the libvirtd.service file needs to be changed to enable the tcp listener instead of using the /etc/default/libvirtd config file. Would be nice if the service had the tcp option (commented out by default) My changes were to Remove $libvirtd_opts because any setting here causes the service to fail at startup. Add Wants=libvirtd-tcp.socket and Also=libvirtd-tcp.socket [Unit] Description=Virtualization daemon Requires=virtlogd.socket Requires=virtlockd.socket # Use Wants instead of Requires so that users # can disable these three .socket units to revert # to a traditional non-activation deployment setup Wants=libvirtd.socket Wants=libvirtd-ro.socket Wants=libvirtd-tcp.socket Wants=libvirtd-admin.socket Wants=systemd-machined.service Before=libvirt-guests.service After=network.target After=dbus.service After=iscsid.service After=apparmor.service After=local-fs.target After=remote-fs.target After=systemd-logind.service After=systemd-machined.service After=xencommons.service Conflicts=xendomains.service Documentation=man:libvirtd(8) Documentation=https://libvirt.org [Service] Type=notify EnvironmentFile=-/etc/default/libvirtd ExecStart=/usr/sbin/libvirtd $libvirtd_opts #ExecStart=/usr/sbin/libvirtd -l -d ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure # At least 1 FD per guest, often 2 (eg qemu monitor + qemu agent). # eg if we want to support 4096 guests, we'll typically need 8192 FDs # If changing this, also consider virtlogd.service & virtlockd.service # limits which are also related to number of guests LimitNOFILE=8192 # The cgroups pids controller can limit the number of tasks started by # the daemon, which can limit the number of domains for some hypervisors. # A conservative default of 8 tasks per guest results in a TasksMax of # 32k to support 4096 guests. TasksMax=32768 # With cgroups v2 there is no devices controller anymore, we have to use # eBPF to control access to devices. In order to do that we create a eBPF # hash MAP which locks memory. The default map size for 64 devices together # with program takes 12k per guest. After rounding up we will get 64M to # support 4096 guests. LimitMEMLOCK=64M [Install] WantedBy=multi-user.target Also=virtlockd.socket Also=virtlogd.socket Also=libvirtd.socket Also=libvirtd-ro.socket Also=libvirtd-tcp.socket -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960937 Title: Libvirtd on 20.04 does not listen on port 16509 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1960937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751954] Re: Bluetooth and Wi-Fi items in Power are worded ambiguously
It says above fix released in August, however I still have the bad wording and it has caught me out today. I'm running Ubuntu 20.04.03 gnome 3.36.8. Why has the fix not reached me yet please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751954 Title: Bluetooth and Wi-Fi items in Power are worded ambiguously To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1751954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from
1.) Did first test from Marco trevisan 2.) after that I run 'gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts true' 3.) than restarted to Wayland 4.) got back to xorg exported the data with journalctl -b0 >Journal.txt 5.) this file is around 3MB in size so I compacted it to journal.tar.xz ** Attachment added: "journal.tar.xz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+attachment/5561316/+files/journal.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960875] Re: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call
Thanks! Sent a SRU for Impish and Jammy: https://lists.ubuntu.com/archives/kernel-team/2022-February/128121.html ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: linux (Ubuntu Jammy) Assignee: Skipper Bug Screeners (skipper-screen-team) => Krzysztof Kozlowski (krzk) ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960875 Title: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960826] Re: NFSv4 performance problem with newer kernels
so as not to duplicate effort, I see there is a request for enhancement over at Redhat: https://bugzilla.redhat.com/show_bug.cgi?id=1801326 ** Bug watch added: Red Hat Bugzilla #1801326 https://bugzilla.redhat.com/show_bug.cgi?id=1801326 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957932] Re: [MIR] rustc, cargo
** Changed in: rustc (Ubuntu) Assignee: Simon Chopin (schopin) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957932 Title: [MIR] rustc, cargo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1957932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751954] Re: Bluetooth and Wi-Fi items in Power are worded ambiguously
The fix is in gnome-control-center version 41 and later. So that's in Ubuntu 22.04 only right now. And in fact it was only released to Ubuntu 22.04 in November/December. This doesn't appear to be a severe bug. I'm not sure if such a design change is appropriate for some future 20.04.x release. If you think it is then you can add tag 'rls-ff-incoming'. ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751954 Title: Bluetooth and Wi-Fi items in Power are worded ambiguously To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1751954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from
May importante. I use Wireguard and have a mounted sft there. Since my update to 21.10 it do not work anymore. Goal here is to have imediately after login a mounted drive. I never found a recommended way how to automount a network drive in Ubuntu. $HOME/.local/share/systemd/user/ contain a .mount and .automout file with folowing content. .mount ___ [Unit] Description=Speicher einbinden [Install] WantedBy=multi-user.target [Mount] What=USER@SERVER-IP:/ Where=/media/USER/Mountpoint Type=fuse.sshfs Options=_netdev,allow_other,IdentityFile=/home/USER/.ssh/SSH-FILE,reconnect,ServerAliveInterval=15,ServerAliveCountMax=10,uid=1000,gid=1000 TimeoutSec=60 .automount ___ [Unit] Description=Auto Speicher einbinden [Install] WantedBy=multi-user.target [Automount] Where=/media/USER/sieben -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793242] Re: KDE saves and restores all but Google Chrome in its Desktop saved session
Is there any progress on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793242 Title: KDE saves and restores all but Google Chrome in its Desktop saved session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1793242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961039] Re: Brightness control with integrated AMD GPU and NVidia GPU
** Description changed: System information -- Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy Integrated AMD GPU: AMD Ryzen 7 5800H with Radeon Graphics GPU : NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] with nvidia-driver-510 Description of the problem -- I can't change the brightness of the screen using the hot keys or the settings menu. It is clear that these buttons are acting on the value stored in /sys/class/backlight/nvidia_0/brightness, but has no effect on the actual brightness. However, modifying manually the value in /sys/class/backlight/amdgpu_bl0/brightness changes the actual brightness. + + Troubleshooting attempts + + + If I downgrade the nvidia dirver from 510 to 470, controlling brightness + works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961039 Title: Brightness control with integrated AMD GPU and NVidia GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1961039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959419] Re: [22.04 FEAT] Upgrade openCryptoki to latest version (>= 3.17)
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959419 Title: [22.04 FEAT] Upgrade openCryptoki to latest version (>= 3.17) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961046] [NEW] Duplicate IP address on LSPs in the same LS lead to unpredictable flow output
Public bug reported: In a busy CI cloud we ran into an issue that took us days to get to the bottom of. Essentially what happens is that the CMS is sometimes unable to complete deletion of a LSP (being worked on separately [0]). Subsequently a new LSP is created using the same IP address but a different MAC address. There exists duplicate IP checks in the ovn-nbctl administration tool [1], but the current database schema does not apply any constraints on a CMS adding duplicates and despite [1] citing ovn- northd should log this, it does not appear to do so. When a system is in the above described state the flow output on hypervisors is unpredictable, and this leads to instances not being able to reach the router nor the outside world. What happens inside the ovn-controller is that the function looking up installed flows [2] only does a table, priority and miniflow match, and does not consider the possibility of other collisions. Subsequently an attempt to link an desired flow to an installed flow unexpectedly fails, and the flow is just not processed at all [3]. At the very least I think we need to investigate why this situation is not logged in ovn-northd, but I don't think just logging this is enough. Is there something we can change in the database model that would prevent a CMS from getting itself into this situation in the first place? Should we consider also not generating the lflows? Example lflows: table=15(lr_in_arp_resolve ), priority=500 , match=(ip4.mcast || ip6.mcast), action=(next;) table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "R1_R2" && reg0== 20.0.0.2), action=(eth.dst = 00:00:00:02:03:05; next;) table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "R1_R2" && xxreg0 == fe80::200:ff:fe02:305), action=(eth.dst = 00:00:00:02:03:05; next;) table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:01; next;) table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:02; next;) table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:03; next;) table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:04; next;) table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:05; next;) table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:06; next;) table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:07; next;) table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:08; next;) table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:09; next;) table=15(lr_in_arp_resolve ), priority=0, match=(ip4), action=(get_arp(outport, reg0); next;) table=15(lr_in_arp_resolve ), priority=0, match=(ip6), action=(get_nd(outport, xxreg0); next;) Resulting flow table: cookie=0xe683b51c, duration=0.128s, table=23, n_packets=0, n_bytes=0, idle_age=0, priority=500,ipv6,metadata=0x2,dl_dst=33:33:00:00:00:00/ff:ff:00:00:00:00,ipv6_dst=ff00::/8 actions=resubmit(,24) cookie=0xe683b51c, duration=0.128s, table=23, n_packets=0, n_bytes=0, idle_age=0, priority=500,ipv6,metadata=0x1,dl_dst=33:33:00:00:00:00/ff:ff:00:00:00:00,ipv6_dst=ff00::/8 actions=resubmit(,24) cookie=0xe683b51c, duration=0.128s, table=23, n_packets=0, n_bytes=0, idle_age=0, priority=500,ip,metadata=0x2,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00,nw_dst=224.0.0.0/4 actions=resubmit(,24) cookie=0xe683b51c, duration=0.128s, table=23, n_packets=0, n_bytes=0, idle_age=0, priority=500,ip,metadata=0x1,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00,nw_dst=224.0.0.0/4 actions=resubmit(,24) cookie=0xed4bbf00, duration=0.120s, table=23, n_packets=0, n_bytes=0, idle_age=0, priority=100,reg0=0xfe80,reg1=0,reg2=0x2ff,reg3=0xfe020304,reg15=0x2,metadata=0x2 actions=set_field:00:00:00:02:03:04->eth_dst,resubmit(,24) cookie=0x601769fe, duration=0.114s, table=23, n_packets=0, n_bytes=0, idle_age=0, priority=100,reg0=0xfe80,reg1=0,reg2=0x2ff,reg3=0xfe020305,reg15=0x2,metadata=0x1 actions=set_field:00:00:00:02:03:05->eth_dst,resubmit(,24) cookie=0x92b4073a, duration=0.118s, table=23, n_packets=0, n_bytes=0, idle_age=0, priority=100,reg0=0x1401,reg15=0x2,metadata=0x2 actions=set_field:00:00:00:02:03:04->eth_dst,resubmit(,24) cookie=0x87dacd46, duration=0.118s, table=23, n_packets=0, n_bytes=0, idle_age=0, priority=100,reg0=0x1402,reg15=0x2,metadata=0x1 actions=set_field:00:00:00:02:03:05-
[Bug 1960875] Re: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call
** Changed in: linux (Ubuntu Impish) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960875 Title: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961042] Re: gnome-shell crashed with SIGSEGV in meta_context_run_main_loop()
*** This bug is a duplicate of bug 1961041 *** https://bugs.launchpad.net/bugs/1961041 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1961041, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1961042/+attachment/5561330/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1961042/+attachment/5561332/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1961042/+attachment/5561337/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1961042/+attachment/5561338/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1961042/+attachment/5561339/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1961042/+attachment/5561341/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1961042/+attachment/5561342/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1961041 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961042 Title: gnome-shell crashed with SIGSEGV in meta_context_run_main_loop() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961047] [NEW] swapfile has holes on preinstalled desktop
Public bug reported: The swapfile generated on the current Ubuntu on Raspberry Pi dailies for jammy includes holes which prevents the swapfile from activating on boot. After digging through livecd-rootfs and ubuntu-image I *think* this might be a problem introduced by the latter. However, this seems to come up periodically so rather than repeatedly trying to squash the problem let's just avoid it entirely by having the swapfile allocated on first boot. Using fallocate for this (instead of dd'ing /dev/zero) works happily and is extremely quick. I've proposed the following merge against ubuntu/master which implements this change (and cleans up some cruft in the fstab handling; that's in a separate commit though -- happy to remove it if wanted): https://code.launchpad.net/~waveform/livecd-rootfs/+git/livecd- rootfs/+merge/415625 The change has been tested on the armhf and arm64 preinstalled jammy dailies and works happily. My one concern was that the file-system expansion must happen prior to the swapfile allocation, but given systemd is handling the expansion, and the allocation has "After=local- fs.target" specified, this appears to be sufficient for everything to run in the correct order. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: livecd-rootfs (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Tags: raspi-image ** Also affects: livecd-rootfs (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Jammy) Milestone: None => ubuntu-22.04 ** Tags added: raspi-image ** Summary changed: - swapfile has holes + swapfile has holes on preinstalled desktop ** Changed in: livecd-rootfs (Ubuntu Jammy) Status: New => Confirmed ** Merge proposal linked: https://code.launchpad.net/~waveform/livecd-rootfs/+git/livecd-rootfs/+merge/415625 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961047 Title: swapfile has holes on preinstalled desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1961047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960182] Re: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7
** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Krzysztof Kozlowski (krzk) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960182 Title: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912616] Re: missing GDPR consent for Agenda application for meteo data (Ubuntu 20.10)
Hi Perhaps it's an Ubuntu concern because gnome-weather in agenda app is installed at first Ubuntu installation time, where some user agreements may be collected. Is there a Ubuntu GDPR (or other agreement law) group somewhere to talk about those subjects ? Thanks & cheers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912616 Title: missing GDPR consent for Agenda application for meteo data (Ubuntu 20.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-weather/+bug/1912616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697957] Re: Impress crashes when using smooth fade transition on Gnome based desktop environment
I ran into this problem today with LO Version: 6.4.7.2. (Both the crashes and the jagged, flickering transitions.) Is it possible that this was never fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697957 Title: Impress crashes when using smooth fade transition on Gnome based desktop environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1697957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960972] Re: All snap applications missing from gnome-search after update
I'm also using fish shell so what @iperry83 describes is like the issue. It appears that snapd.fish relies on fish_add_path which is not available until fish 3.3, while Ubuntu 21.10 provides fish 3.1.2. I did not attempt to return to the non-working version, just adding this observation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960972 Title: All snap applications missing from gnome-search after update To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1960972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959596] Re: Applications end up in session scope, rather than per .desktop scope
Possibly related: the user graphical-session.target unit is never reached in Jammy. From Impish and Jammy we have for `systemctl --user is-active graphical-session.target`: - Impish clean install: active - Jammy clean install: inactive Note that this means that the .service units under /usr/lib/systemd/user/graphical-session-pre.target.wants/ are not being executed. These are: gnome-keyring-ssh.service gnome-keyring.service session-migration.service ssh-agent.service (Initially reported in https://bugs.launchpad.net/ubuntu/+source/gnome- session/+bug/1743366) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959596 Title: Applications end up in session scope, rather than per .desktop scope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959596] Re: Applications end up in session scope, rather than per .desktop scope
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959596 Title: Applications end up in session scope, rather than per .desktop scope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961048] [NEW] pcmanfm-qt ugly dithering on mouseover highlights
Public bug reported: I have noticed this issue with pcmanfm-qt only so far. All was working fine when I upgraded from 18.04 to 20.04 about 2 weeks back. About 3 days back I ran: apt-get dist-upgrade And since then I've noticed this issue. Let me know if I should downgrade and hold back any packages for X11 etc. I am not using wayland mode, only pure Xorg. If I take a screenshot it shows perfect display even though the actual screen is as per the video I've attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pcmanfm-qt 0.14.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.14.0-1020.22-oem 5.14.20 Uname: Linux 5.14.0-1020-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Feb 16 16:09:39 2022 InstallationDate: Installed on 2015-04-04 (2510 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: pcmanfm-qt UpgradeStatus: Upgraded to focal on 2022-01-22 (24 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2015-04-17T22:47:15.195638 ** Affects: pcmanfm-qt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "Video of pcmanfm mouseover dithering" https://bugs.launchpad.net/bugs/1961048/+attachment/5561352/+files/WhatsApp%20Video%202022-02-16%20at%204.15.02%20PM.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961048 Title: pcmanfm-qt ugly dithering on mouseover highlights To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1961048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960875] Re: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call
** Changed in: ubuntu-z-systems Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960875 Title: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960182] Re: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7
** Also affects: linux (Ubuntu Jammy) Importance: High Assignee: Krzysztof Kozlowski (krzk) Status: In Progress ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960182 Title: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561357/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] Re: WiFi and Bluetooth drivers issue
apport information ** Tags added: apport-collected bionic ** Description changed: - We want to inform you that we are facing issue of WiFi and BT drivers in - upper kernel of Linux Ubuntu 18.04.6 LTS (5.4.0-84-generic). Till this - kernel 5.4.0.84-generic, All working smooth. We have tried latest one - 5.4.0.97 as well but not fixed. Please help to fix. + We want to inform you that we are facing issue of WiFi and BT drivers in upper kernel of Linux Ubuntu 18.04.6 LTS (5.4.0-84-generic). Till this kernel 5.4.0.84-generic, All working smooth. We have tried latest one 5.4.0.97 as well but not fixed. Please help to fix. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: harshjain 2825 F pulseaudio + /dev/snd/pcmC0D0c: harshjain 2825 F...m pulseaudio + /dev/snd/pcmC0D0p: harshjain 2825 F...m pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-12-03 (806 days ago) + InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + MachineType: Dell Inc. Latitude 5400 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_IN.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic root=UUID=e0cab521-14d2-4c87-9ab0-d7f8ff2fc706 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-84-generic N/A + linux-backports-modules-5.4.0-84-generic N/A + linux-firmware1.173.20 + Tags: bionic + Uname: Linux 5.4.0-84-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/21/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.5.1 + dmi.board.name: 0PD9KD + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5400:pvr:rvnDellInc.:rn0PD9KD:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: Latitude + dmi.product.name: Latitude 5400 + dmi.product.sku: 08B8 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561356/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561358/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561359/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561360/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561363/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561361/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561362/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561365/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561364/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561367/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561368/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561366/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1961037/+attachment/5561369/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861262] Re: Add message/rfc822 to thunderbird.desktop
Thank you for updating the .desktop file. The issue is more hairy than it seems at first glance. E.g. https://debbugs.gnu.org/ sends "Content-disposition" header with ".mbox" suffix when a single comment in mbox format is requested (to reply to particular message). Thunderbird believes that a suitable action is to compose a new message with downloaded file as an attachment. There is no command line option to force thunderbird to open a file as namely mail message. The position of developers is that such file must have ".eml" extension otherwise it is not a message. See https://bugzilla.mozilla.org/show_bug.cgi?id=1755454 for details (bug title has been changed to fix a loosely related issue). ** Bug watch added: Mozilla Bugzilla #1755454 https://bugzilla.mozilla.org/show_bug.cgi?id=1755454 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861262 Title: Add message/rfc822 to thunderbird.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1861262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960149] Re: Include ogre-next in Ubuntu Jammy
Ok, I had a brief look through the copyright - seems to be in order (quite huge, but I could help myself out with a diff against ogre-1.12). The debian/watch file works, is able to re-download and re-package the current source (with a small remark) and fetch new versions from upstream. The source package is lintian clean and most patches have DEB3 headers. Generally it feels like the package is good to go, but we'll need to adjust the versioning. Just a few questions/remarks before I proceed further: * Remark re: the .orig tarball. Even though I think this is generally *fine* but when re-downloading (and auto-repacking) with uscan the current 2.2.5 tarball, there are a few additional files present in the tarball in comparison to the tarball used in the PPA upload (there's some .hgignore, .travis.yaml etc. files in it). I would normally expect to get the exact same tarball contents from running uscan. In this case I think it's fine, but this might mean that the debian/copyright exclude list needs to be modified or, otherwise, no hand modifications done to the source please. * I see that in Debian new a previous version of ogre-next is staged - ogre-next_2.2.5+dfsg3-1. From what I can tell that version has a different set of binary packages (libogre-next2.2 instead of the set of libogrenext*2.2.5 binaries). Would it be possible for you to submit -2 to Debian NEW? In case this gets accepted by Debian, it would be troublesome if a different set of binary packages was generated there. * Regarding that point above ^ - the binary package name numbers feel a bit confusing, with their description and purpose not being quite clear. Are those the 'final' binary package names? If so, could we expand their individual long descriptions to be a bit more clear on what their purpose is? * The version number needs fixing. 2.2.5+dfsg3-2ubuntu2 means that Debian has 2.2.5+dfsg3-2 and we introduce an ubuntu delta on top. Since this package is not accepted into Debian as of yet, the version number needs to be 2.2.5+dfsg3-0ubuntu2 (or, possibly, -0ubuntu1), with -0ubuntuX indicating 'Debian doesn't have this yet, but Ubuntu does'. This makes it easier for us to switch to Debian once the package is available there as well. Could you take a look at those? Thank you. ** Changed in: ubuntu Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960149 Title: Include ogre-next in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961046] Re: Duplicate IP address on LSPs in the same LS lead to unpredictable flow output
** Description changed: In a busy CI cloud we ran into an issue that took us days to get to the bottom of. Essentially what happens is that the CMS is sometimes unable to complete deletion of a LSP (being worked on separately [0]). Subsequently a new LSP is created using the same IP address but a different MAC address. There exists duplicate IP checks in the ovn-nbctl administration tool [1], but the current database schema does not apply any constraints on a CMS adding duplicates and despite [1] citing ovn- northd should log this, it does not appear to do so. When a system is in the above described state the flow output on hypervisors is unpredictable, and this leads to instances not being able to reach the router nor the outside world. What happens inside the ovn-controller is that the function looking up installed flows [2] only does a table, priority and miniflow match, and does not consider the possibility of other collisions. Subsequently an attempt to link an desired flow to an installed flow unexpectedly fails, and the flow is just not processed at all [3]. - - At the very least I think we need to investigate why this situation is not logged in ovn-northd, but I don't think just logging this is enough. + At the very least I think we need to investigate why this situation is + not logged in ovn-northd, but I don't think just logging this is enough. Is there something we can change in the database model that would prevent a CMS from getting itself into this situation in the first place? Should we consider also not generating the lflows? - Example lflows: - table=15(lr_in_arp_resolve ), priority=500 , match=(ip4.mcast || ip6.mcast), action=(next;) - table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "R1_R2" && reg0== 20.0.0.2), action=(eth.dst = 00:00:00:02:03:05; next;) - table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "R1_R2" && xxreg0 == fe80::200:ff:fe02:305), action=(eth.dst = 00:00:00:02:03:05; next;) - table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:01; next;) - table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:02; next;) - table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:03; next;) - table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:04; next;) - table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:05; next;) - table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:06; next;) - table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:07; next;) - table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:08; next;) - table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:09; next;) - table=15(lr_in_arp_resolve ), priority=0, match=(ip4), action=(get_arp(outport, reg0); next;) - table=15(lr_in_arp_resolve ), priority=0, match=(ip6), action=(get_nd(outport, xxreg0); next;) + table=15(lr_in_arp_resolve ), priority=500 , match=(ip4.mcast || ip6.mcast), action=(next;) + table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "R1_R2" && reg0== 20.0.0.2), action=(eth.dst = 00:00:00:02:03:05; next;) + table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "R1_R2" && xxreg0 == fe80::200:ff:fe02:305), action=(eth.dst = 00:00:00:02:03:05; next;) + table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:01; next;) + table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:02; next;) + table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:03; next;) + table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:04; next;) + table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:05; next;) + table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:06; next;) + table=15(lr_in_arp_resolve ), priority=100 , match=(outport == "ls1" && reg0 == 192.168.1.11), action=(eth.dst = f0:00:00:01:01:0
[Bug 1960921] Re: [VROC] Ledmon couldn't be run with latest libsgutils2-2 package - ubuntu 22.04
I installed and verified ledmon-0.95-1build1 package. Fix is OK - ledmon is installed and run without errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960921 Title: [VROC] Ledmon couldn't be run with latest libsgutils2-2 package - ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1960921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 402892] Re: Mouse cursor gets stuck in "drag and drop" mode
I have a similar problem on Linux Mint Cinnamon 20.3: https://bugs.launchpad.net/ubuntu/+bug/1961034 Video: https://emalm.com/?v=DsBSK Is anyone working on fixing this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/402892 Title: Mouse cursor gets stuck in "drag and drop" mode To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/402892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961049] Re: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
It seems it *was* during some automatic apt update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961049 Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1961049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961049] [NEW] package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: It wasn't during any upgrade or installation. The "System program problem detected" just popped in. I just had the browser opened with a few tabs. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 11 11:24:29 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-12-19 (1519 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all 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.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-07-13 (582 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961049 Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1961049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955671] Re: support for rocky linux UEFI
** Changed in: curtin (Ubuntu) Status: New => Incomplete ** Changed in: curtin (Ubuntu) Status: Incomplete => In Progress ** Also affects: curtin Importance: Undecided Status: New ** Changed in: curtin Status: New => In Progress ** Changed in: curtin Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955671 Title: support for rocky linux UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1955671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961027] Re: [FFE] merge virt-manger >3.2 for Jammy once released
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961027 Title: [FFE] merge virt-manger >3.2 for Jammy once released To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1961027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960937] Re: Libvirtd on 20.04 does not listen on port 16509
Hi, thank you for your report! The config in /etc/default/libvirtd is pretty much there for compatibility reasons with older setups and (on Debian) people using still sys-V init. And even with systemd some other options than "-l" can still be sued that way e.g. "-v" for extra verbosity. If one sets that option the error message gladly is pretty clear: libvirtd[2725397]: --listen parameter not permitted with systemd activation sockets, see 'man libvirtd' for further guidance In that man page it explains (as that isn't a Ubuntu only problem): ``` ... In socket activation mode, it will rely on systemd to create and listen on the UNIX, and optionally TCP/IP, sockets and pass them as pre-opened file descriptors. In this mode, it is not permitted to pass the --listen parameter, and most of the socket related config options in /etc/libvirt/libvirtd.conf will no longer have any effect. To enable TCP or TLS sockets use either $ systemctl start libvirtd-tls.socket Or $ systemctl start libvirtd-tcp.socket ... ``` There is no need to change the .service file as you did, and in fact any subsequent update would eliminate that change. As a TL;DR and I hope IIRC it would be like: $ sudo systemctl stop libvirtd $ sudo systemctl start libvirtd-tcp.socket # in any real setup you'd now setup SASL, but for this to # be short I set auth_tcp = "none" in /etc/libvirt/libvirtd.conf With that in place $ virsh -c qemu+tcp://127.0.0.1/system list Will start libvirtd and it accepts tcp connections. In addition there also is TLS which is more complex there is: #setup CA and issue/config certificates for libvirtd # see TLS x509 certificate configuration and any entry related to # *tls* and *certificates* in /etc/libvirt/libvirtd.conf $ sudo systemctl stop libvirtd $ sudo systemctl start libvirtd-tls.socket What to do from here: - I agree that a hint in /etc/default/libvirtd would be great to have as its current form is misleading. - This bug demonstrates that it is unclear how to be used. Therefore a documentation entry in the Ubuntu server guide would be very helpful. It should show how this can be done (for TCP) and also include an example of a cert setup and end by accessing via TLS Triaging the bug with that in mind, but please speak up for a discussion on this if you want. ** Summary changed: - Libvirtd on 20.04 does not listen on port 16509 + Libvirtd conffiles should be less misleading and document tcp/tls usage ** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960937 Title: Libvirtd conffiles should be less misleading and document tcp/tls usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1960937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961037] Re: WiFi and Bluetooth drivers issue
We have run the command (apport-collect 1961037), Please check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961037 Title: WiFi and Bluetooth drivers issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960783] Re: don't install unsigned fwupd efi app by default
debdiff for focal ** Patch added: "fwupd-signed.1.43.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1960783/+attachment/5561379/+files/fwupd-signed.1.43.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960783 Title: don't install unsigned fwupd efi app by default To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944508] Re: [P10] CAS : last kernel not auto booted
** Tags added: jammy ** Changed in: ubuntu-power-systems Importance: Medium => High ** Changed in: grub2 (Ubuntu) Importance: Medium => High ** Description changed: + Feature Freeze Exception (FFe): + + Due to the fact that the work and backlog on grub2 in jammy is pretty + big and the complexity high, I discussed with juliank (Foundations) the + other day, and the outcome was to transfer this ticket into a FFe, just + to be prepared. + + The patch that is in discussion here is especially for Power 10, which is planned to be supported by Ubuntu Server 22.04 (jammy) (and is customer driven). + Since it's uncertain if a re-worked patch can be picked-up in time for the jammy Feature Freeze on Feb. the 24th, I want to raise the attention of the Ubuntu Release Team, + and kindly ask for acknowledge. + + Required tests on this will be done with the help of the customer/partner IBM. + _ + == Comment: #0 - Frederic Bonnard - 2021-04-26 02:32:28 == Hi, testing Debian/Ubuntu installation with OpenQA on a P10 LPAR with a virtual optical device, the LPAR boots the iso till grub menu. First entry is selected and Enter gets pressed. The kernel starts and calls ibm,client-architecture-support . My understanding is that either it returns or reboots with the new feature set and in which case, the grub menu shouldn't pop out again and the last booted kernel should be used with the same parameters. But it is not the case at the moment, the iso grub menu pops out again. This does not happen all the time. Sometimes the kernel does not reboot and (maybe the required settings are ok but in this case, I don't know how it got set). Here is a video showing this behavior on Debian (kernel 5.10.0-6, grub 2.04, http://d-i.debian.org/daily-images/ppc64el/daily/netboot/mini.iso). Same on Ubuntu 20.04 daily (kernel 5.4.0-72.80, grub 2.04, http://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-ppc64el.iso) Regards, F. == Comment: #1 - Frederic Bonnard - 2021-04-26 02:33:14 == - - == Comment: #2 - Frederic Bonnard - 2021-04-26 02:33:48 == - + == Comment: #2 - Frederic Bonnard - 2021-04-26 + 02:33:48 == == Comment: #3 - Diego Pereira Domingos - 2021-04-29 10:52:18 == Hi Fr?deric, we will need to push the required patches for CAS reboot into UBUNTU/DEBIAN. == Comment: #8 - Diego Pereira Domingos - 2021-08-09 08:54:07 == - == Comment: #10 - Diego Pereira Domingos - 2021-08-10 08:13:10 == Hello Canonical, we need this patch in grub so it can support CAS reboot for ppc64le Thanks ** Summary changed: - [P10] CAS : last kernel not auto booted + [FFE] [P10] CAS : last kernel not auto booted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944508 Title: [FFE] [P10] CAS : last kernel not auto booted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1944508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903289] Re: Power guest secure boot with static keys: GRUB2 portion
** Tags added: jammy ** Description changed: - == Comment: #2 - Daniel John Axtens - 2020-11-05 19:50:03 == - This bug covers the grub part of our LPAR Secure Boot design, which I'd like to propose for your 21.04 release. + Feature Freeze Exception (FFe): + + Due to the fact that the work and backlog on grub2 in jammy is pretty + big and the complexity high, I discussed with juliank (Foundations) the + other day, and the outcome was to transfer this ticket into a FFe, just + to be prepared. + + The patch set that is in discussion here is especially for Ubuntu secure boot on PowerVM . + PowerVM is mandatory for the most recent Power 10 family, and Power 10 support is planned for Ubuntu Server 22.04 (and is customer driven). + Since it's uncertain if a re-worked patch can be picked-up in time for the jammy Feature Freeze on Feb. the 24th, I want to raise the attention of the Ubuntu Release Team, + and kindly ask for acknowledge. + + Required tests on this will be done with the help of the customer/partner IBM. + _ + + == Comment: #2 - Daniel John Axtens - 2020-11-05 + 19:50:03 == + This bug covers the grub part of our LPAR Secure Boot design, which I'd like to propose for your 21.04 release. Background == Please find attached an overall outline of the design. Patches === I've posted the 3 main parts of this feature to the grub mailing list: - - Allowing grub to be signed with an appended signature to be verified by firmware: https://lists.gnu.org/archive/html/grub-devel/2020-08/msg00037.html - - Teaching grub how to verify appended signatures on Linux kernels: https://lists.gnu.org/archive/html/grub-devel/2020-10/msg00152.html - - Linking grub's verification to the secure boot status from firmware: https://lists.gnu.org/archive/html/grub-devel/2020-10/msg00048.html + - Allowing grub to be signed with an appended signature to be verified by firmware: https://lists.gnu.org/archive/html/grub-devel/2020-08/msg00037.html + - Teaching grub how to verify appended signatures on Linux kernels: https://lists.gnu.org/archive/html/grub-devel/2020-10/msg00152.html + - Linking grub's verification to the secure boot status from firmware: https://lists.gnu.org/archive/html/grub-devel/2020-10/msg00048.html (We do need one other piece just to increase the amount of memory grub allocates for itself in as it starts. We have a couple of prototypes, one which we've posted to the list and one which we haven't. The one we've posted breaks booting of guests with 512MB of memory, which - as far as I can tell - is still supported by Ubuntu, and indeed is the default for guests created by uvtool. So we'll post an alternative to the list shortly.) Because of the grub development cycle, these patches will not be merged upstream for 2.06. We are hoping, given the incredibly slow pace of grub development and the number of out-of-tree patches that have traditionally been required for UEFI secure-boot support, that you'd be willing to carry these out of tree while we try to have them merged. Next Steps == We need the following information from you: - - If you're willing to take grub changes, what tree would you like us + - If you're willing to take grub changes, what tree would you like us to backport our grub changes onto? I imagine it's just the development tree on launchpad, but I thought I'd check. - - What keys would you like to use? As we are using static keys, we will + - What keys would you like to use? As we are using static keys, we will need to embed an x509 certificate for verifying grub in firmware. We will need a production certificate, and we can also support test keys while firmware is still in development. Either you can supply a test key or you can use the existing 'imprint' keys that we are using. (Neither will be supported in production firmware builds - this is just for before we hit production firmware levels.) - - The addition of a signed binary will make installing grub more + - The addition of a signed binary will make installing grub more complicated, as grub-install (out of the box) will create and install an unsigned binary. There's also likely implications for the installer. What parts of this process do you need us to develop? - Building, Signing and Testing = If you would like to, you can experiment with this already using qemu and SLOF, although our production solution will only support PFW. Details are on the list: https://lists.gnu.org/archive/html/grub- devel/2020-10/msg00048.html A slightly more involved process is required for a fully generic distro- friendly solution, we can share more details on that. ** Summary changed: - Power guest secure boot with static keys: GRUB2 portion + [FFE] Power guest secure boot with static keys: GRUB2 portion ** Changed in: ubuntu-power-sy
[Bug 1960783] Re: don't install unsigned fwupd efi app by default
debdiff for impish ** Patch added: "fwupd-signed-impish.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1960783/+attachment/5561380/+files/fwupd-signed-impish.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960783 Title: don't install unsigned fwupd efi app by default To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960182] Re: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7
** Changed in: ubuntu-z-systems Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960182 Title: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961048] Re: pcmanfm-qt ugly dithering on mouseover highlights
If you read the Lubuntu release notes (https://lubuntu.me/focal-2-released/) you'll have discovered "Note, due to the extensive changes required for the shift in desktop environments, the Lubuntu team does not support upgrading from 18.04 or below to any greater release. Doing so will result in a broken system. If you are on 18.04 or below and would like to upgrade, please do a fresh install." Issues were expected which is why the upgrade path is not supported. I've thus marked this bug as invalid (your system is unsupported). If you believe I'm in error, please leave a comment explaining why and the status can be changed back to new, however a confirmation of the bug report will be required on a fresh install (or install of Lubuntu 18.10 or later which can be upgraded to 20.04) before the issue will be looked at by the Lubuntu team. It may also be your issue is a kernel issue (what your video reminded me of), but this comment deals only with `pcmanfm-qt` or Lubuntu package(s). ** Changed in: pcmanfm-qt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961048 Title: pcmanfm-qt ugly dithering on mouseover highlights To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1961048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961047] Re: swapfile has holes on preinstalled desktop
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961047 Title: swapfile has holes on preinstalled desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1961047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961048] Re: pcmanfm-qt ugly dithering on mouseover highlights
I can also confirm seeing the dithering or missing pixels in Google chrome stable (from google repo) when hovering over an image. The title popup shows this same issue. So its likely an issue with X.Org or some X11 library. Seems to occur in both QT & GTK apps. However custom rendered popups like the LX Panel taskbar and chrome tabs do not show this issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961048 Title: pcmanfm-qt ugly dithering on mouseover highlights To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1961048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960996] Re: [sru] sos upstream 4.3
This bug was fixed in the package sosreport - 4.3-1ubuntu1 --- sosreport (4.3-1ubuntu1) jammy; urgency=medium * New 4.3 upstream. (LP: #1960996) * For more details, full release note is available here: - https://github.com/sosreport/sos/releases/tag/4.3 * New patches: - d/p/0002-fix-setup-py.patch: Add python sos.help module, it was miss in upstream release. * Former patches, now fixed: - d/p/0002-report-implement_estimate-only.patch - d/p/0003-ceph-add-support-for-containerized-ceph-setup.patch - d/p/0004-ceph-split-plugin-by-components.patch - d/p/0005-openvswitch-get-userspace-datapath-implementations.patch - d/p/0006-report-check-for-symlink-before-rmtree.patch * Remaining patches: - d/p/0001-debian-change-tmp-dir-location.patch: -- Eric Desrochers Tue, 15 Feb 2022 23:10:27 -0500 ** Changed in: sosreport (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960996 Title: [sru] sos upstream 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1960996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960947] Re: Graphical issues for GtKGL in software rendering
Hello Sebastien, or anyone else affected, Accepted gtk+3.0 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.20-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gtk+3.0 (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960947 Title: Graphical issues for GtKGL in software rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1960947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
