[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Ivan Hu]

bisecting kernel from the 6.5.0-42 to latest master-next, the patch
"x86/boot: Omit compression buffer from PE/COFF image memory footprint"
also causes fail to boot up.


03651c884514d311fa3e628ac073afbad04e5c57 is the first bad commit
commit 03651c884514d311fa3e628ac073afbad04e5c57
Author: Ard Biesheuvel 
Date:   Tue Sep 12 09:00:56 2023 +

x86/boot: Omit compression buffer from PE/COFF image memory footprint

BugLink: https://bugs.launchpad.net/bugs/2061814

commit 8eace5b3555606e684739bef5bcdfcfe68235257 upstream.

Now that the EFI stub decompresses the kernel and hands over to the
decompressed image directly, there is no longer a need to provide a
decompression buffer as part of the .BSS allocation of the PE/COFF
image. It also means the PE/COFF image can be loaded anywhere in memory,
and setting the preferred image base is unnecessary. So drop the
handling of this from the header and from the build tool.

Signed-off-by: Ard Biesheuvel 
Signed-off-by: Ingo Molnar 
Link: https://lore.kernel.org/r/20230912090051.4014114-22-a...@google.com
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Portia Stephens 
Signed-off-by: Roxana Nicolescu 

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061940

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Ivan Hu]

Tested with the test kernel 6.5.0-42,
https://launchpad.net/~roxanan/+archive/ubuntu/thermal/+packages

unfortunately, got fail to boot up

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061940

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Ivan Hu]

Test with latest proposed kernel Ubuntu-6.5.0-40.40, can boot up without
problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061940

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921107] Re: The version1.20 don't work anymore

[Ivan Senin]

The FAQ on the official website ausweisapp.bund.de says we must have
version >= 1.26.5. I cannot pair my smartphone with this package
available for Ubuntu at the moment.

Common guys, who's the maintainer here?? We need to be able to use some
digital services

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921107

Title:
  The version1.20 don't work anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ausweisapp2/+bug/1921107/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065747] [NEW] An unknown display appears in both the GNOME display manager and NVIDIA X Server Settings

[Ivan]

Public bug reported:

A short while after this clean installation of Ubuntu 24.04 LTS, a
strange unknown display appeared both in GNOME Settings and in NVIDIA X
Server Settings. I noticed it because I could see my mouse cursor
disappear beyond the boundaries of my monitor as if it is being extended
with a second one. In GNOME Settings it is listed as an"Unknown
Display", but in NVIDIA X Server Settings, it appears as a PRIME display
which is confusing since I am using a desktop configuration.

Currently, setting the second mirror to be mirrored seems to "fix" the
issue, but it is a recurring problem.

The issue concerns an nVidia RTX 2080ti.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nvidia-driver-535 535.171.04-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 15 00:24:20 2024
InstallationDate: Installed on 2024-05-12 (2 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: nvidia-graphics-drivers-535
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-535 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

** Attachment added: "This is how the "display" appears in GNOME settings."
   
https://bugs.launchpad.net/bugs/2065747/+attachment/5778507/+files/Screenshot%20from%202024-05-15%2000-31-50.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065747

Title:
  An unknown display appears in both the GNOME display manager and
  NVIDIA X Server Settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2065747/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Ivan Hu]

** Changed in: linux (Ubuntu)
   Status: In Progress => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061940

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Ivan Hu]

@Roxana,

Checkout tag Ubuntu-6.5.0-34.34 and revert two patches below, it can
boot up without problem.

thermal: core: Store trip pointer in struct thermal_instance
thermal: trip: Drop lockdep assertion from thermal_zone_trip_id()

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061940

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Ivan Hu]

Test latest master-next of mantic with below two patches,

thermal: trip: Drop redundant trips check from for_each_thermal_trip()
thermal: core: Rework and rename __for_each_thermal_trip()

still failed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061940

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Ivan Hu]

seems 6.6.x has this in addition for apply the "thermal: trip: Drop
redundant trips check from for_each_thermal_trip()"

thermal: core: Rework and rename __for_each_thermal_trip()

Rework the currently unused __for_each_thermal_trip() to pass original
pointers to struct thermal_trip objects to the callback, so it can be
used for updating trip data (e.g. temperatures), rename it to
for_each_thermal_trip() and make it available to modular drivers.

Suggested-by: Daniel Lezcano 
Signed-off-by: Rafael J. Wysocki 

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061940

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Ivan Hu]

bisect kernel result, 
the patch 2c7b4bfadef08cc0995c24a7b9eb120fe897165f causes this regression

thermal: core: Store trip pointer in struct thermal_instance

Replace the integer trip number stored in struct thermal_instance with
a pointer to the relevant trip and adjust the code using the structure
in question accordingly.

The main reason for making this change is to allow the trip point to
cooling device binding code more straightforward, as illustrated by
subsequent modifications of the ACPI thermal driver, but it also helps
to clarify the overall design and allows the governor code overhead to
be reduced (through subsequent modifications).

The only case in which it adds complexity is trip_point_show() that
needs to walk the trips[] table to find the index of the given trip
point, but this is not a critical path and the interface that
trip_point_show() belongs to is problematic anyway (for instance, it
doesn't cover the case when the same cooling devices is associated
with multiple trip points).

This is a preliminary change and the affected code will be refined by
a series of subsequent modifications of thermal governors, the core and
the ACPI thermal driver.

The general functionality is not expected to be affected by this change.

Signed-off-by: Rafael J. Wysocki 
Reviewed-by: Daniel Lezcano 

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061940

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Ivan Hu]

testing with Ubuntu-6.5.0-28-generic without this issue, bisecting
kernel

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061940

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Ivan Hu]

testing with Ubuntu-6.5.0-32-generic, it can't boot up as well.

** Changed in: linux (Ubuntu)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061940

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2049733] Re: Dynamically determine acpi_handle_list size

[Ivan Hu]

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049733

Title:
  Dynamically determine acpi_handle_list size

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049733/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060981] Re: ACPI BIOS errors

[Ivan Hu]

From the acpidump log on comment#2, this is buggy bios uses below
objects but are not actually implemented.

all on the ssdt2(DptfTabl) table,

\CTDP, 
\_SB.PC00.LPCB.EC0.SEN1._CRT.S1CT,
\_SB.PC00.LPCB.EC0.SEN1._HOT.S1HT,
\_SB.PC00.LPCB.EC0.SEN1._PSV.S1PT,
\_SB.PC00.LPCB.EC0.SEN1._AC0.S1AT,
\_SB.PC00.LPCB.EC0.SEN2._CRT.S2CT,
\_SB.PC00.LPCB.EC0.SEN2._HOT.S2HT,
\_SB.PC00.LPCB.EC0.SEN2._PSV.S2PT,
\_SB.PC00.LPCB.EC0.SEN2._AC0.S2AT,
\_SB.PC00.LPCB.EC0.SEN3._CRT.S3CT,
\_SB.PC00.LPCB.EC0.SEN3._HOT.S3HT,
\_SB.PC00.LPCB.EC0.SEN3._PSV.S3PT,
\_SB.PC00.LPCB.EC0.SEN4._CRT.S4CT,
\_SB.PC00.LPCB.EC0.SEN4._HOT.S4HT,
\_SB.PC00.LPCB.EC0.SEN4._PSV.S4PT,
\_SB.PC00.LPCB.EC0.SEN4._AC0.S4AT,

All these objects are related DPTF, you should reach your machine vendor for 
update bios.
There is nothing can do on Ubuntu side.

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/2060981

Title:
  ACPI BIOS errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060981/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060981] Re: ACPI BIOS errors

[Ivan Hu]

ACPI AE_NOT_FOUND errors usually come from buggy firmware which uses the
objects but not actually implemented.

Can spot which parts of firmware errors if you can support acpidump log.
$sudo acpidump > acpidump.log

** Changed in: linux (Ubuntu)
   Status: In Progress => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060981

Title:
  ACPI BIOS errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060981/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060981] Re: ACPI BIOS errors

[Ivan Hu]

** Changed in: linux (Ubuntu)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
   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/2060981

Title:
  ACPI BIOS errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060981/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060415] [NEW] package nvidia-dkms-418-server 418.226.00-0ubuntu5~0.22.04.1 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-418-server, o script post-installation retorn

[Edson Ivan Faria]

Public bug reported:

Ola, todos os driver que instalo reconhece apenas monitors com
frequencia maior ou igual a 75hz, com isso não consigo utilizar dois
monitores, caso eu desistale os driver, o sistema não reconhece o
monitor de 75hz e a imagem trava

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-418-server 418.226.00-0ubuntu5~0.22.04.1
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sun Apr  7 22:43:30 2024
ErrorMessage: o subprocesso instalado, do pacote nvidia-dkms-418-server, o 
script post-installation retornou erro do status de saída 10
InstallationDate: Installed on 2024-04-08 (0 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.3
 apt  2.4.12
SourcePackage: nvidia-graphics-drivers-418-server
Title: package nvidia-dkms-418-server 418.226.00-0ubuntu5~0.22.04.1 failed to 
install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-418-server, o 
script post-installation retornou erro do status de saída 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-418-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060415

Title:
  package nvidia-dkms-418-server 418.226.00-0ubuntu5~0.22.04.1 failed to
  install/upgrade: o subprocesso instalado, do pacote nvidia-
  dkms-418-server, o script post-installation retornou erro do status de
  saída 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/2060415/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059170] [NEW] RTL8852BE can't connect on high 5Ghz channels

[Ivan Baldo]

Public bug reported:

Doesn't connect to channels above 64, so when my AP decides to use for
example channel 116 I get disconnected.

Can confirm that on Windows 11 it works in those high channels.

Even a "nmcli d w" doesn't show any WiFi's with high channels when in
other devices I can see them.

Using Ubuntu 24.04 Beta updated as of today, it did happen with 23.10
and 22.04.4 too.

Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
linux-firmware 20240318.git3b128b60-0ubuntu1
linux-image-6.8.0-11-generic 6.8.0-11.11


[   13.442016] rtw89_8852be :01:00.0: loaded firmware 
rtw89/rtw8852b_fw-1.bin
[   13.442305] rtw89_8852be :01:00.0: enabling device ( -> 0003)
[   13.444303] rtw89_8852be :01:00.0: Firmware version 0.29.29.5 
(da87cccd), cmd version 0, type 5
[   13.444309] rtw89_8852be :01:00.0: Firmware version 0.29.29.5 
(da87cccd), cmd version 0, type 3
[   13.726907] rtw89_8852be :01:00.0: chip rfe_type is 41

01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8852BE 
PCIe 802.11ax Wireless Network Controller [1T1R] [10ec:b85b]
DeviceName: Realtek Wireless LAN + BT
Subsystem: Hewlett-Packard Company RTL8852BE PCIe 802.11ax Wireless 
Network Controller [1T1R] [103c:88e6]
Flags: bus master, fast devsel, latency 0, IRQ 84, IOMMU group 8
I/O ports at f000 [size=256]
Memory at fcf0 (64-bit, non-prefetchable) [size=1M]
Capabilities: 
Kernel driver in use: rtw89_8852be
Kernel modules: rtw89_8852be

** Affects: linux (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/2059170

Title:
  RTL8852BE can't connect on high 5Ghz channels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059170/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2033348] Re: Wireless: Update RTL8852BE wifi driver

[Ivan Baldo]

In Ubuntu 24.04 Beta it seems up to date:
[   13.442016] rtw89_8852be :01:00.0: loaded firmware 
rtw89/rtw8852b_fw-1.bin
[   13.442305] rtw89_8852be :01:00.0: enabling device ( -> 0003)
[   13.444303] rtw89_8852be :01:00.0: Firmware version 0.29.29.5 
(da87cccd), cmd version 0, type 5
[   13.444309] rtw89_8852be :01:00.0: Firmware version 0.29.29.5 
(da87cccd), cmd version 0, type 3
[   13.726907] rtw89_8852be :01:00.0: chip rfe_type is 41

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2033348

Title:
  Wireless: Update RTL8852BE wifi driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033348/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056631] [NEW] archivemount: files with unicode characters are not shown

[Ivan]

Public bug reported:

Ubuntu 22.04.4 LTS

When mouting archive that contains filenames with non-ASCII character (I 
suppose), they are not shown.
Reproducing is easy:

touch æ.txt
touch a.txt
zip test.zip -xi a.txt æ.txt
mkdir test
archivemount test.zip test
xdg-open test

Result: only a.txt is shown inside the folder
Expected: two files should be mounted inside

** Affects: archivemount (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/2056631

Title:
  archivemount: files with unicode characters are not shown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/archivemount/+bug/2056631/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972889] Re: Screen reader reads the data while computer is locked

[Ivan Roganov]

Also, I want to make sure that we did not miss this part:

Opened browser is Brave. It's a chromium-based browser, and then I would
lock a computer, with this, pressing Alt+Super+S would start reading
chromium interface.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972889

Title:
  Screen reader reads the data while computer is locked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972889] monitors.xml.txt

[Ivan Roganov]

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1972889/+attachment/5589689/+files/monitors.xml.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972889

Title:
  Screen reader reads the data while computer is locked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972889] ShellJournal.txt

[Ivan Roganov]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1972889/+attachment/5589688/+files/ShellJournal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972889

Title:
  Screen reader reads the data while computer is locked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972889] ProcCpuinfoMinimal.txt

[Ivan Roganov]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1972889/+attachment/5589687/+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/1972889

Title:
  Screen reader reads the data while computer is locked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972889] GsettingsChanges.txt

[Ivan Roganov]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1972889/+attachment/5589686/+files/GsettingsChanges.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972889

Title:
  Screen reader reads the data while computer is locked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972889] Re: Screen reader reads the data while computer is locked

[Ivan Roganov]

apport information

** Tags added: apport-collected wayland-session

** Description changed:

  # lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04
  
  # apt-cache policy gnome-shell
  gnome-shell:
Installed: 42.0-2ubuntu1
Candidate: 42.0-2ubuntu1
Version table:
   *** 42.0-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  
  Ubuntu is installed on a laptop. Within five minutes of inactivity, the
  screen lock activates and locks the system. Computer is secured. 10
  minutes later, my cat (her name is Loaf) comes up to the laptop and sits
  down on the keyboard. This activates a screen reader. (Shortcut is Alt +
  Super + S)
  
  What I've expected:
  Screen reader would start reading the contents of a lock screen
  
  What happened:
  Screen reader app started reading contents of a Brave Browser window that was 
opened on my desktop. It read all tabs and proceeded reading the opened web 
page. 
  
  
  I've reported this bug at secur...@ubuntu.org and got the following answer:
  
  > Nice find - I am able to reproduce this locally in Ubuntu 22.04 LTS too
  > - I suspect this is a vulnerability in gnome-shell as it is
  > responsible for handling the lock screen in standard Ubuntu.
  
  As per further directions, I'm posting this bug here and in gnome repo.
  
  
  P.S. I expect Loaf being credited for this find. She really likes treats.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2021-10-24 (201 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ Package: gnome-shell 42.0-2ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/usr/bin/zsh
+ ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
+ RelatedPackageVersions: mutter-common 42.0-3ubuntu2
+ Tags:  wayland-session jammy
+ Uname: Linux 5.15.0-27-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago)
+ UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1972889/+attachment/5589685/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972889

Title:
  Screen reader reads the data while computer is locked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972802] Re: enable config for fixing 5.17 kernel won't load mok

[Ivan Hu]

** Description changed:

  [Impact]
  Mok keys is not trusted after kernel 5.17
  
  [Fix]
  Enable the CONFIG_IMA_SECURE_AND_OR_TRUSTED_BOOT and CONFIG_IMA_ARCH_POLICY 
for fixing the patch
  "[patch] integrity: Do not load MOK and MOKx when secure boot be disabled" 
was added to check if secureboot enabled for trusting the MOK key
  
  [Test]
  Enroll Mok key and use it to sign kernel modules, make sure secure boot is on 
and load the kernel module by either modprobe or insmod.
  
- [Regression Risk]
+ [Where problems could occur]
  Low. only affect the checking secureboot enable function.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972802

Title:
  enable config for fixing 5.17 kernel won't load mok

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1972802/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969212] Re: libssl1.x dependencies can't be met on 22.04 beta

[Ivan Skorikov]

** Package changed: ubuntu => openssl (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969212

Title:
  libssl1.x dependencies can't be met on 22.04 beta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1969212/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969212] [NEW] libssl1.x dependencies can't be met on 22.04 beta

[Ivan Skorikov]

Public bug reported:

Since Ubuntu 22.04 beta includes only openssl 3.0, any and all packages
that do not recognize newer openssl versions and depend on previous
versions can't be properly installed.

As an example, in my isolated case I'm trying to install SafeNet
Authentication Client to be able to use eToken hardware key:

# dpkg -i /SAC/safenetauthenticationclient_10.8.28_amd64.deb 
Selecting previously unselected package safenetauthenticationclient.
(Reading database ... 202999 files and directories currently installed.)
Preparing to unpack .../safenetauthenticationclient_10.8.28_amd64.deb ...
Unpacking safenetauthenticationclient (10.8.28) ...
dpkg: dependency problems prevent configuration of safenetauthenticationclient:
 safenetauthenticationclient depends on libssl1.0.2 | libssl1.0.0 | libssl1.1; 
however:
  Package libssl1.0.2 is not installed.
  Package libssl1.0.0 is not installed.
  Package libssl1.1:amd64 is not installed.

dpkg: error processing package safenetauthenticationclient (--install):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.35-0ubuntu3) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
Errors were encountered while processing:
 safenetauthenticationclient

The package depends on "libssl1.0.2 | libssl1.0.0 | libssl1.1" and at
the moment this dependency cannot be met without resorting to manually
installing the required library, which is not a good way to go.

Thanks in advance.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: libssl openssl

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969212

Title:
  libssl1.x dependencies can't be met on 22.04 beta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1969212/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964541] Re: Cannot use Drag and Drop in gnome-shell 42 (Wayland session)

[Ivan Sagalaev]

> I hope we get back to Firefox with Wayland enabled soon because the
performance difference was noticeable last time I checked.

Plus, rendering of the entire Firefox window got blurry with fractional
scaling. (Just to add one more reason :-) )

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964541

Title:
  Cannot use Drag and Drop in gnome-shell 42 (Wayland session)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965535] Re: Stop recommending snap

[Ivan]

> Judging by the size of this other thread [1], I'd venture many other
users feel equally about this.

Indeed. Just so that we are clear about the importance of this:

At present, the bug linked to by @guiambros, which triggered opening
this bug in ubuntu-meta as well, is the 3rd highest by heat *for all
bugs recorded in launchpad in all ubuntu packages*:

https://bugs.launchpad.net/ubuntu/+bugs?orderby=-heat=0

I think that says something.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965535

Title:
  Stop recommending snap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961760] Re: `disk-image` not granular enough, often builds unused artifacts

[Ivan Kapelyukhin]

TEST CASE:
1. modified focal and bionic image's series file to use disk-image-uefi instead 
of disk-image
2. built the images

VERIFICATION DONE
Images are built successfully, BIOS disk images aren't built.


** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal
** Tags added: verification-done verification-done-bionic 
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/1961760

Title:
  `disk-image` not granular enough, often builds unused artifacts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1961760/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965535] Re: Stop recommending snap

[Ivan]

So far, 12 people have already indicated that this bug affects them
(several giving more detailed descriptions). This bug is now in the top
5 of open bugs with most heat for ubuntu-meta.

Given that others are affected, would it be reasonable to set the status
to Confirmed so it is given further consideration?

EDIT: simplify text

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965535

Title:
  Stop recommending snap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961760] Re: `disk-image` not granular enough, often builds unused artifacts

[Ivan Kapelyukhin]

TEST CASE:
1. modified an image's series file to use disk-image-uefi instead of disk-image
2. built an image

VERIFICATION DONE
Image is built successfully, BIOS disk image isn't built.

** Tags removed: verification-needed verification-needed-impish
** Tags added: verification-done verification-done-impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961760

Title:
  `disk-image` not granular enough, often builds unused artifacts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1961760/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965535] Re: Stop recommending snap

[Ivan]

** Description changed:

  Currently, ubuntu recommends installing snap by default, and some apps
  are slowly transitioning from DEB-based installation to Snap-based
  installation.
  
  APT is great, and facilitates having a clean, maintainable system.
  
- The snap project is not very well designed or engineered (just changing the 
location of where snap data is located is taking the project more than 5 years 
because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps 
are large and VERY slow. The design of snap, as well as the way decisions are 
made, are very questionable, and are receiving
- increasing amounts of criticism.
+ The snap project is not very well designed or engineered (just changing
+ the location of where snap data is located is taking the project more
+ than 5 years because it was hardcoded:
+ https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY
+ slow. The design of snap, as well as the way that decisions are made,
+ are very questionable, and are receiving increasing amounts of
+ criticism.
  
  I'd like to request that Ubuntu stops recommending snap, stops
  transitioning towards snaps, and we come back to defaulting to DEB/APT-
  based installation for all apps.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965535

Title:
  Stop recommending snap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965535] Re: Stop recommending snap

[Ivan]

** Description changed:

  Currently, ubuntu recommends installing snap by default, and some apps
  are slowly transitioning from DEB-based installation to Snap-based
  installation.
  
  APT is great, and facilitates having a clean, maintainable system.
  
- The snap project is not very well designed or engineered (just changing
- the location of where snap data is located is taking the project more
- than 5 years because it was hardcoded:
- https://bugs.launchpad.net/snapd/+bug/1575053). The design of snap, and
- many decisions made in the project that impact users, are very
- questionable, and snaps are large and VERY slow.
+ The snap project is not very well designed or engineered (just changing the 
location of where snap data is located is taking the project more than 5 years 
because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps 
are large and VERY slow. The design of snap, as well as the way decisions are 
made, are very questionable, and are receiving
+ increasing amounts of criticism.
  
  I'd like to request that Ubuntu stops recommending snap, stops
  transitioning towards snaps, and we come back to defaulting to DEB/APT-
  based installation for all apps.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965535

Title:
  Stop recommending snap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location

[Ivan]

Given that this is affecting so many people: I've opened a request
against Ubuntu-meta so that Snap stops being recommended by default and
we make sure no packages provide snap-based installation only:

https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535

Feel free to comment there.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053

Title:
  Please move the "$HOME/snap" directory to a less obtrusive location

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965535] [NEW] Stop recommending snap

[Ivan]

Public bug reported:

Currently, ubuntu recommends installing snap by default, and some apps
are slowly transitioning from DEB-based installation to Snap-based
installation.

APT is great, and facilitates having a clean, maintainable system.

The snap project is not very well designed or engineered (just changing
the location of where snap data is located is taking the project more
than 5 years because it was hardcoded:
https://bugs.launchpad.net/snapd/+bug/1575053). The design of snap, and
many decisions made in the project that impact users, are very
questionable, and snaps are large and VERY slow.

I'd like to request that Ubuntu stops recommending snap, stops
transitioning towards snaps, and we come back to defaulting to DEB/APT-
based installation for all apps.

** Affects: ubuntu-meta (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/1965535

Title:
  Stop recommending snap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location

[Ivan]

I would not care anymore were it not for the fact that snap is becoming
the default. We will have a less and less usable system if we just
remove snap.

Can we not just request to the Ubuntu team that snap be removed from the
default installation, and that no package should be made available only
via Snap? (for example, currently, chromium is only available via snap).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053

Title:
  Please move the "$HOME/snap" directory to a less obtrusive location

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961760] Re: `disk-image` not granular enough, often builds unused artifacts

[Ivan Kapelyukhin]

** Changed in: livecd-rootfs (Ubuntu)
 Assignee: (unassigned) => Ivan Kapelyukhin (ikapelyukhin)

** Changed in: livecd-rootfs (Ubuntu Bionic)
 Assignee: (unassigned) => Ivan Kapelyukhin (ikapelyukhin)

** Changed in: livecd-rootfs (Ubuntu Focal)
 Assignee: (unassigned) => Ivan Kapelyukhin (ikapelyukhin)

** Changed in: livecd-rootfs (Ubuntu Impish)
 Assignee: (unassigned) => Ivan Kapelyukhin (ikapelyukhin)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961760

Title:
  `disk-image` not granular enough, often builds unused artifacts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1961760/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960564] Re: GCE shielded VM integrity monitoring reports errors

[Ivan Kapelyukhin]

TEST CASE:
1. Built Focal and Impish GCE images from respective `livecd-rootfs` packages 
with the fix
2. Started instances from those images, rebooted, ran the `integrity-tester` 
script
3. Ran `basic-ubuntu` and `google-secure-boot` test suites against those images

VERIFICATION DONE
Tests are passing, integrity tester shows no errors in integrity logs after 
instance reboot.

** Tags removed: verification-needed verification-needed-focal 
verification-needed-impish
** Tags added: verification-done verification-done-focal 
verification-done-impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960564

Title:
  GCE shielded VM integrity monitoring reports errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1960564/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961760] Re: `disk-image` not granular enough, often builds unused artifacts

[Ivan Kapelyukhin]

** Description changed:

- Due to how `disk-image` series file in `ubuntu-cpc` is structured, it
+ [Impact]
+ 
+  * Due to how `disk-image` series file in `ubuntu-cpc` is structured, it
  builds BIOS and UEFI images at the same time. However, certain images
  (e.g., GCE images) require only UEFI image to be built, BIOS image is
  being simply discarded. This results in longer build times.
+ 
+ [Test Plan]
+ 
+  * Build any image that depends on `disk-image` (e.g. a GCE image) with 
`livefs-build` or `ubuntu-bartender`
+  * Read build logs and observe what build artifacts are produced: `disk.ext4` 
is the BIOS image and `disk-uefi.ext4` is the UEFI image
+ 
+ [Where problems could occur]
+ 
+  * Due to changes in the `disk-images` series file the order in which
+ BIOS and UEFI image are built has changed, if there's something
+ sensitive to the order in which those artifacts are built it might break
+ 
+ [Other Info]
+  
+  * CPC images will be switched from `disk-image` to `disk-image-uefi` once 
the update is released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961760

Title:
  `disk-image` not granular enough, often builds unused artifacts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1961760/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961760] [NEW] `disk-image` not granular enough, often builds unused artifacts

[Ivan Kapelyukhin]

Public bug reported:

Due to how `disk-image` series file in `ubuntu-cpc` is structured, it
builds BIOS and UEFI images at the same time. However, certain images
(e.g., GCE images) require only UEFI image to be built, BIOS image is
being simply discarded. This results in longer build times.

** Affects: livecd-rootfs (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/1961760

Title:
  `disk-image` not granular enough, often builds unused artifacts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1961760/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960564] Re: GCE shielded VM integrity monitoring reports errors

[Ivan Kapelyukhin]

** Changed in: livecd-rootfs (Ubuntu Impish)
 Assignee: (unassigned) => Ivan Kapelyukhin (ikapelyukhin)

** Changed in: livecd-rootfs (Ubuntu Focal)
 Assignee: (unassigned) => Ivan Kapelyukhin (ikapelyukhin)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960564

Title:
  GCE shielded VM integrity monitoring reports errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1960564/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960564] [NEW] GCE shielded VM integrity monitoring reports errors

[Ivan Kapelyukhin]

Public bug reported:

[Impact]

 * GCE shielded VM instances created from official Ubuntu images
starting with focal get integrity monitoring errors after second reboot
without any actions or changes by the user.

 * This is due to `initrdless_boot_fallback_triggered` variable in
/boot/grub/grubenv being set to 0 after first boot. /boot/grub/grubenv
is empty in the image prior to boot.

[Test Plan]

 * To reproduce the bug:
   1. Create a GCE shielded VM instance with integrity monitoring enabled:
 a) focal:
   gcloud compute instances create \
 integrity-test-focal \
 --machine-type "n2d-standard-2" \
 --zone "europe-west1-d" \
 --maintenance-policy=TERMINATE \
 --image-family=ubuntu-2004-lts \
 --image-project=ubuntu-os-cloud \
 --service-account YOUR_SERVICE_ACCOUNT_EMAIL \
 --scopes https://www.googleapis.com/auth/logging.read \
 --shielded-integrity-monitoring \
 --shielded-secure-boot
  b) impish:
gcloud compute instances create \
  integrity-test-impish \
  --machine-type "n2d-standard-2" \
  --zone "europe-west1-d" \
  --maintenance-policy=TERMINATE \
  --image-family=ubuntu-2110 \
  --image-project=ubuntu-os-cloud \
  --service-account YOUR_SERVICE_ACCOUNT_EMAIL \
  --scopes https://www.googleapis.com/auth/logging.read \
  --shielded-integrity-monitoring \
  --shielded-secure-boot
  c) jammy:
gcloud compute instances create \
  integrity-test-jammy \
  --machine-type "n2d-standard-2" \
  --zone "europe-west1-d" \
  --maintenance-policy=TERMINATE \
  --image-family=ubuntu-2204-lts \
  --image-project=ubuntu-os-cloud-devel \
  --service-account YOUR_SERVICE_ACCOUNT_EMAIL \
  --scopes https://www.googleapis.com/auth/logging.read \
  --shielded-integrity-monitoring \
  --shielded-secure-boot
   2. SSH into the instance and reboot it: `sudo reboot`
   3. After the instance is rebooted, check integrity monitoring logs:
 a) The easy way -- SSH into the instance and run:
   curl -sSf 
https://raw.githubusercontent.com/ikapelyukhin/gce-integrity-tester/master/integrity.sh
 | bash
 b) Alternatively, see the logs in the web console: 
https://console.cloud.google.com/logs/query

 * To verify the fix:
   1. Build a custom image with the fixed version of `livecd-rootfs`
   2. Upload it to GCE
   3. Register it in GCE with the same secureboot DBX as the official images
   4. Create an instance
   5. Reboot it
   6. Check integrity logs

[Where problems could occur]

 * Any code that expects `initrdless_boot_fallback_triggered` to be explicitly 0
 would break.

[Other Info]

 * I will build and register custom images the same way official images are  
built and registered by CPC.
 * I can also spin up instances created from official/custom images and provide 
SSH access to them on request for bug reproduction/fix verification.

** Affects: livecd-rootfs (Ubuntu)
 Importance: Undecided
 Assignee: Ivan Kapelyukhin (ikapelyukhin)
 Status: New

** Description changed:

  [Impact]
  
-  * GCE shielded VM instances created from official Ubuntu images starting with
-  focal get integrity monitoring errors after second reboot without any actions
-  or changes by the user.
+  * GCE shielded VM instances created from official Ubuntu images
+ starting with focal get integrity monitoring errors after second reboot
+ without any actions or changes by the user.
  
-  * This is due to `initrdless_boot_fallback_triggered` variable in
-  /boot/grub/grubenv being set to 0 after first boot. /boot/grub/grubenv is 
empty
-  in the image prior to boot.
+  * This is due to `initrdless_boot_fallback_triggered` variable in
+ /boot/grub/grubenv being set to 0 after first boot. /boot/grub/grubenv
+ is empty in the image prior to boot.
  
  [Test Plan]
  
-  * To reproduce the bug:
-1. Create a GCE shielded VM instance with integrity monitoring enabled:
-  a) focal:
-gcloud compute instances create \
-  integrity-test-focal \
-  --machine-type "n2d-standard-2" \
-  --zone "europe-west1-d" \
-  --maintenance-policy=TERMINATE \
-  --image-family=ubuntu-2004-lts \
-  --image-project=ubuntu-os-cloud \
-  --service-account YOUR_SERVICE_ACCOUNT_EMAIL \
-  --scopes https://www.googleapis.com/auth/logging.read \
-  --shielded-integrity-monitoring \
-  --shielded-secure-boot
-   b) impish:
- gcloud compute instances create \
-   integrity-test-impish \
-   --machine-type "n2d-standard-2" \
-   --zone "europe-west1-d" \
-   --maintenance-policy=TERMINATE \
-   --image-family=ubuntu-2110 \
- 

[Bug 1956914] Re: Can't resume from suspend on some specific systems using fwts 21.12

[Ivan Hu]

@Kevin,

Yes, the commit 713284e505287611c7e1e6ae61254de3035433b5 add the "--
s3-sleep-type" sleep type selection and make S3(deep) as default if not
specified.

for those failed platforms, don't they support S3?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956914

Title:
  Can't resume from suspend on some specific systems using fwts 21.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwts/+bug/1956914/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956914] Re: Can't resume from suspend on some specific systems using fwts 21.12

[Ivan Hu]

Is there any reason that "deep" cannot work? Shuuld it be an issue?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956914

Title:
  Can't resume from suspend on some specific systems using fwts 21.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwts/+bug/1956914/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926481] Re: lockf returns false-positive EDEADLK in multiprocess multithreaded environment

[Ivan Zuboff]

Posted to more specific mailing list: linux-fsdevel.vger.kernel.org
https://lore.kernel.org/linux-fsdevel/cal-cveifotfbyrfocb0yeyor+sctpwo_2__49tapronhr+t...@mail.gmail.com/T/#u

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926481

Title:
  lockf returns false-positive EDEADLK in multiprocess multithreaded
  environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926481/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956369] [NEW] The headphones work without problems, as does the microphone but there is no sound on the speakers

[Ivan]

Public bug reported:

I have a problem with my Asus GX701LWS, the headphones work without
problems, as does the microphone but there is no sound on the speakers.

hwinfo --sound
22: PCI 1f.3: 0403 Audio device
[Created at pci.386]
Unique ID: nS1_.Qb7ky1jjQRD
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x06c8
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1f01
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0x9830-0x98303fff (rw,non-prefetchable)
Memory Range: 0x9810-0x981f (rw,non-prefetchable)
IRQ: 171 (910 events)
Module Alias: "pci:v8086d06C8sv1043sd1F01bc04sc03i80"
Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
Driver Status: snd_sof_pci_intel_cnl is active
Driver Activation Cmd: "modprobe snd_sof_pci_intel_cnl"
Config Status: cfg=new, avail=yes, need=no, active=unknown17

aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

pacmd list-sinks
1 sink(s) available.
  * index: 0
 name: 
 driver: 
 flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
DYNAMIC_LATENCY
 state: SUSPENDED
 suspend cause: IDLE
 priority: 9039
 volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB
 balance 0,00
 base volume: 65536 / 100% / 0,00 dB
 volume steps: 65537
 muted: no
 current latency: 0,00 ms
 max request: 0 KiB
 max rewind: 0 KiB
 monitor source: 0
 sample spec: s16le 2ch 48000Hz
 channel map: front-left,front-right
  Stereo
 used by: 0
 linked by: 0
 configured latency: 0,00 ms; range is 0,50 .. 2000,00 ms
 card: 1 
 module: 8
 properties:
  alsa.resolution_bits = "16"
  device.api = "alsa"
  device.class = "sound"
  alsa.class = "generic"
  alsa.subclass = "generic-mix"
  alsa.name = "ALC294 Analog"
  alsa.id = "ALC294 Analog"
  alsa.subdevice = "0"
  alsa.subdevice_name = "subdevice #0"
  alsa.device = "0"
  alsa.card = "0"
  alsa.card_name = "HDA Intel PCH"
  alsa.long_card_name = "HDA Intel PCH at 0x9830 irq 171"
  alsa.driver_name = "snd_hda_intel"
  device.bus_path = "pci-:00:1f.3"
  sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0"
  device.bus = "pci"
  device.vendor.id = "8086"
  device.vendor.name = "Intel Corporation"
  device.product.id = "06c8"
  device.form_factor = "internal"
  device.string = "front:0"
  device.buffering.buffer_size = "384000"
  device.buffering.fragment_size = "192000"
  device.access_mode = "mmap+timer"
  device.profile.name = "analog-stereo"
  device.profile.description = "Analog Stereo"
  device.description = "Built-in Audio Analog Stereo"
  module-udev-detect.discovered = "1"
  device.icon_name = "audio-card-pci"
 ports:
  analog-output-speaker: Speakers (priority 1, latency offset 0 usec, 
available: unknown)
   properties:
device.icon_name = "audio-speakers"
  analog-output-headphones: Headphones (priority 9900, latency offset 0 usec, 
available: no)
   properties:
device.icon_name = "audio-headphones"
 active port: 

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: alc294 asus gx701 sound

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956369

Title:
   The headphones work without problems, as does the microphone but
  there is no sound on the speakers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1956369/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1038479] Re: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while

[Ivan]

It doesn't work for my Asus gx701lws.
The headphones work without problems, as does the microphone but there is no 
sound on the speakers.

hwinfo --sound
22: PCI 1f.3: 0403 Audio device
[Created at pci.386]
Unique ID: nS1_.Qb7ky1jjQRD
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x06c8
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1f01
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0x9830-0x98303fff (rw,non-prefetchable)
Memory Range: 0x9810-0x981f (rw,non-prefetchable)
IRQ: 171 (910 events)
Module Alias: "pci:v8086d06C8sv1043sd1F01bc04sc03i80"
Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
Driver Status: snd_sof_pci_intel_cnl is active
Driver Activation Cmd: "modprobe snd_sof_pci_intel_cnl"
Config Status: cfg=new, avail=yes, need=no, active=unknown17

aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

pacmd list-sinks
1 sink(s) available.
  * index: 0
name: 
driver: 
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE
priority: 9039
volume: front-left: 65536 / 100% / 0,00 dB,   front-right: 65536 / 100% 
/ 0,00 dB
balance 0,00
base volume: 65536 / 100% / 0,00 dB
volume steps: 65537
muted: no
current latency: 0,00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 0
sample spec: s16le 2ch 48000Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 0
configured latency: 0,00 ms; range is 0,50 .. 2000,00 ms
card: 1 
module: 8
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC294 Analog"
alsa.id = "ALC294 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0x9830 irq 171"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1f.3"
sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "06c8"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "384000"
device.buffering.fragment_size = "192000"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
analog-output-speaker: Speakers (priority 1, latency offset 
0 usec, available: unknown)
properties:
device.icon_name = "audio-speakers"
analog-output-headphones: Headphones (priority 9900, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "audio-headphones"
active port: 

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038479

Title:
  [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a
  while

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1038479/+subscriptions


-- 
ubuntu-bugs mailing list

[Bug 1899369] Re: ovn-controller: Disable ofctrl probe by default

[Ivan Kolemanov]

Hi, is the fix "released" for Ubuntu Cloud Archive victoria?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899369

Title:
  ovn-controller: Disable ofctrl probe by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1899369/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897371] Re: don't ship libgc with -Wl,-Bsymbolic-functions

[Ivan Maidanski]

This is fixed in upstream v8.0.6

[1] 
https://github.com/ivmai/bdwgc/commit/cf699a0b377494a3ae08cabc067f57485f775c9a
[2] https://github.com/ivmai/bdwgc/releases/tag/v8.0.6

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897371

Title:
  don't ship libgc with -Wl,-Bsymbolic-functions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgc/+bug/1897371/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1950077] [NEW] full screen google chrome goes behind the panel

[Ivan Shkarbut]

Public bug reported:

if you maximize the window with google chrome to full screen or minimize
and maximize the window, it will go beyond the panel. As a result, there
is no access to google chrome control buttons.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: evince (not installed)
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sun Nov  7 11:36:11 2021
InstallationDate: Installed on 2021-09-12 (55 days ago)
InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: evince
UpgradeStatus: Upgraded to impish on 2021-10-14 (23 days ago)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

** Attachment added: "this is how it looks"
   
https://bugs.launchpad.net/bugs/1950077/+attachment/5538627/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0_2021-11-07_12-03-36.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950077

Title:
  full screen google chrome goes behind the panel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1950077/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947618] [NEW] [i915] CPU locks up on Ubuntu 21.10 boot when 2 displays are connected

[Ivan Savyhin]

Public bug reported:

I've updated from 21.04 to 21.10 and that bug has appeared in kernel
5.13.0-19. When 2 displays are connected simulateneously (DP and HDMI)
before graphics server is started the kernel hangs up and reports that
cpu is locked up. Boot with 5.11 kernel doesn't produce that problem.

PC is based on i7-11700 CPU.

Here is part of kernel log with call trace:
кас 18 19:36:24 MWU-2197 kernel: fb0: switching to inteldrmfb from EFI VGA
кас 18 19:36:24 MWU-2197 kernel: Console: switching to colour dummy device 80x25
кас 18 19:36:24 MWU-2197 kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
кас 18 19:36:24 MWU-2197 kernel: snd_hda_intel :00:1f.3: enabling device 
( -> 0002)
кас 18 19:36:24 MWU-2197 kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
кас 18 19:36:24 MWU-2197 kernel: mei_hdcp 
:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops 
i915_hdcp_component_ops [i915])
кас 18 19:36:24 MWU-2197 kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/rkl_dmc_ver2_02.bin (v2.2)
кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM: chip id 63
кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM: features 0x07
кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: Broadcom Bluetooth Device
кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) 
build 1467
кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM20702A1 
'brcm/BCM20702A1-0b05-17cb.hcd' Patch
кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: Broadcom Bluetooth Device
кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) 
build 1467
кас 18 19:36:51 MWU-2197 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 
26s! [systemd-udevd:461]
кас 18 19:36:51 MWU-2197 kernel: Modules linked in: snd_sof_pci_intel_tgl 
snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation 
soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof 
snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi 
soundwire_bus ledtrig_audio snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi 
snd_hda_codec nls_iso8859_1 snd_hda_core fjes(-) mei_hdcp intel_rapl_msr 
i915(+) snd_hwdep snd_pcm intel_rapl_common snd_seq_midi snd_seq_midi_event 
btusb x86_pkg_temp_thermal snd_rawmidi intel_powerclamp btrtl drm_kms_helper 
btbcm snd_seq coretemp btintel crct10dif_pclmul snd_seq_device 
ghash_clmulni_intel cec snd_timer bluetooth rc_core aesni_intel snd crypto_simd 
i2c_algo_bit joydev cryptd fb_sys_fops mei_me ecdh_generic syscopyarea 
input_leds ecc sysfillrect intel_cstate eeepc_wmi wmi_bmof efi_pstore ee1004 
soundcore sysimgblt mei sch_fq_codel mac_hid acpi_pad acpi_tad msr parport_pc 
ppdev
кас 18 19:36:51 MWU-2197 kernel:  lp parport drm ip_tables x_tables autofs4 
hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid mfd_aaeon asus_wmi 
sparse_keymap intel_lpss_pci crc32_pclmul nvme xhci_pci i2c_i801 ahci 
intel_lpss e1000e nvme_core i2c_smbus libahci idma64 xhci_pci_renesas wmi video 
pinctrl_tigerlake
кас 18 19:36:51 MWU-2197 kernel: CPU: 0 PID: 461 Comm: systemd-udevd Not 
tainted 5.13.0-19-generic #19-Ubuntu
кас 18 19:36:51 MWU-2197 kernel: Hardware name: ASUS System Product Name/PRIME 
B560M-A, BIOS 1017 07/12/2021
кас 18 19:36:51 MWU-2197 kernel: RIP: 
0010:skl_commit_modeset_enables+0x1b1/0x540 [i915]
кас 18 19:36:51 MWU-2197 kernel: Code: 39 d8 7e 5d 49 8b 75 20 83 c3 01 8d 43 
ff 48 98 48 8d 0c c5 00 00 00 00 48 29 c1 48 8d 04 ce 4c 8b 20 4c 8b 50 10 4c 
8b 40 18 <4d> 85 e4 74 1a 41 8b 8c 24 f0 03 00 00 41 0f b6 c7 4c 89 55 b8 48
кас 18 19:36:51 MWU-2197 kernel: RSP: 0018:b89600d6b7b8 EFLAGS: 0202
кас 18 19:36:51 MWU-2197 kernel: RAX: 97474f0867b8 RBX: 0002 
RCX: 0007
кас 18 19:36:51 MWU-2197 kernel: RDX: 97474434 RSI: 97474f086780 
RDI: 974748c5ef3c
кас 18 19:36:51 MWU-2197 kernel: RBP: b89600d6b828 R08: 974749b72000 
R09: 0800
кас 18 19:36:51 MWU-2197 kernel: R10: 974741e22000 R11: 97474f086828 
R12: 974752d1e000
кас 18 19:36:51 MWU-2197 kernel: R13: 97474fe5e800 R14: 0003 
R15: 0003
кас 18 19:36:51 MWU-2197 kernel: FS:  7fe5dbb858c0() 
GS:974e7f40() knlGS:
кас 18 19:36:51 MWU-2197 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
кас 18 19:36:51 MWU-2197 kernel: CR2: 7f21b94d3230 CR3: 0001115b6001 
CR4: 00770ef0
кас 18 19:36:51 MWU-2197 kernel: PKRU: 5554
кас 18 19:36:51 MWU-2197 kernel: Call Trace:
кас 18 19:36:51 MWU-2197 kernel:  ? wait_woken+0x80/0x80
кас 18 19:36:51 MWU-2197 kernel:  intel_atomic_commit_tail+0x364/0xa00 [i915]
кас 18 19:36:51 MWU-2197 kernel:  ? __i915_sw_fence_complete+0x111/0x1c0 [i915]
кас 18 19:36:51 MWU-2197 kernel:  intel_atomic_commit+0x331/0x3b0 [i915]
кас 18 19:36:51 MWU-2197 kernel:  drm_atomic_commit+0x47/0x50 

[Bug 1628707] Re: Highlighting a region in emacs is invisible because region color equals window color

[Ivan Zakharyaschev]

I experience this or a similar problem with emacs-26 on Ubuntu 20.04
(the standard Gnome DE).

Somehow having the "region" face set to having gtk_selection_bg_color
makes the selected region not noticeable (or hardly noticeable?..). I
have delete-selection-mode enabled.

After changing it, it is OK; to yellow in my case:

(custom-set-faces
 ;; custom-set-faces was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 '(region ((t (:background "yellow" :distant-foreground 
"gtk_selection_fg_color")

I wonder why the selection in Firefox is noticeable and has the standard
orange-brown color whereas Emacs doesn't get it.

ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Oct  6 20:08:01 2021
Dependencies:
 adduser 3.118ubuntu2
 adwaita-icon-theme 3.36.1-2ubuntu0.20.04.2
 alsa-topology-conf 1.2.2-1
 alsa-ucm-conf 1.2.2-1ubuntu0.10
 apt 2.0.6
 apt-utils 2.0.6
 at-spi2-core 2.36.0-2
 ca-certificates 20210119~20.04.2
 coreutils 8.30-3ubuntu2
 dbus 1.12.16-2ubuntu2.1
 dconf-gsettings-backend 0.36.0-1
 dconf-service 0.36.0-1
 debconf 1.5.73
 debconf-i18n 1.5.73
 dpkg 1.19.7ubuntu3
 emacs-bin-common 1:26.3+1-1ubuntu2
 emacs-common 1:26.3+1-1ubuntu2
 emacs-el 1:26.3+1-1ubuntu2
 emacs-gtk 1:26.3+1-1ubuntu2
 emacsen-common 3.0.4
 fontconfig 2.13.1-2ubuntu3
 fontconfig-config 2.13.1-2ubuntu3
 fonts-dejavu-core 2.37-1
 fonts-droid-fallback 1:6.0.1r16-1.1
 fonts-noto-mono 20200323-1build1~ubuntu20.04.1
 fonts-urw-base35 20170801.1-3
 gcc-10-base 10.3.0-1ubuntu1~20.04
 ghostscript 9.50~dfsg-5ubuntu4.3
 glib-networking 2.64.2-1ubuntu0.1
 glib-networking-common 2.64.2-1ubuntu0.1
 glib-networking-services 2.64.2-1ubuntu0.1
 gpgv 2.2.19-3ubuntu2.1
 gsettings-desktop-schemas 3.36.0-1ubuntu1
 gsfonts 1:8.11+urwcyr1.0.7~pre44-4.4
 gtk-update-icon-cache 3.24.20-0ubuntu1
 hicolor-icon-theme 0.17-2
 humanity-icon-theme 0.6.15
 imagemagick-6-common 8:6.9.10.23+dfsg-2.1ubuntu11.4
 install-info 6.7.0.dfsg.2-5
 krb5-locales 1.17-6ubuntu4.1
 libacl1 2.2.53-6
 libapparmor1 2.13.3-7ubuntu5.1
 libapt-pkg6.0 2.0.6
 libasound2 1.2.2-2.1ubuntu2.4
 libasound2-data 1.2.2-2.1ubuntu2.4
 libatk-bridge2.0-0 2.34.2-0ubuntu2~20.04.1
 libatk1.0-0 2.35.1-1ubuntu2
 libatk1.0-data 2.35.1-1ubuntu2
 libatspi2.0-0 2.36.0-2
 libattr1 1:2.4.48-5
 libaudit-common 1:2.8.5-2ubuntu6
 libaudit1 1:2.8.5-2ubuntu6
 libavahi-client3 0.7-4ubuntu7.1
 libavahi-common-data 0.7-4ubuntu7.1
 libavahi-common3 0.7-4ubuntu7.1
 libblkid1 2.34-0.1ubuntu9.1
 libbrotli1 1.0.7-6ubuntu0.1
 libbsd0 0.10.0-1
 libbz2-1.0 1.0.8-2
 libc6 2.31-0ubuntu9.2
 libcairo-gobject2 1.16.0-4ubuntu1
 libcairo2 1.16.0-4ubuntu1
 libcap-ng0 0.7.9-2.1build1
 libcolord2 1.4.4-2
 libcom-err2 1.45.5-2ubuntu1
 libcrypt1 1:4.4.10-10ubuntu4
 libcups2 2.3.1-9ubuntu1.1
 libdatrie1 0.2.12-3
 libdb5.3 5.3.28+dfsg1-0.6ubuntu2
 libdbus-1-3 1.12.16-2ubuntu2.1
 libdconf1 0.36.0-1
 libepoxy0 1.5.4-1
 libexpat1 2.2.9-1build1
 libffi7 3.3-4
 libfftw3-double3 3.3.8-2ubuntu1
 libfontconfig1 2.13.1-2ubuntu3
 libfreetype6 2.10.1-2ubuntu0.1
 libfribidi0 1.0.8-2
 libgcc-s1 10.3.0-1ubuntu1~20.04
 libgcrypt20 1.8.5-5ubuntu1.1
 libgd3 2.2.5-5.2ubuntu2.1
 libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
 libgdk-pixbuf2.0-bin 2.40.0+dfsg-3ubuntu0.2
 libgdk-pixbuf2.0-common 2.40.0+dfsg-3ubuntu0.2
 libgif7 5.1.9-1
 libglib2.0-0 2.64.6-1~ubuntu20.04.4
 libglib2.0-data 2.64.6-1~ubuntu20.04.4
 libgmp10 2:6.2.0+dfsg-4
 libgnutls30 3.6.13-2ubuntu1.6
 libgomp1 10.3.0-1ubuntu1~20.04
 libgpg-error0 1.37-1
 libgpm2 1.20.7-5
 libgraphite2-3 1.3.13-11build1
 libgs9 9.50~dfsg-5ubuntu4.3
 libgs9-common 9.50~dfsg-5ubuntu4.3
 libgssapi-krb5-2 1.17-6ubuntu4.1
 libgtk-3-0 3.24.20-0ubuntu1
 libgtk-3-bin 3.24.20-0ubuntu1
 libgtk-3-common 3.24.20-0ubuntu1
 libharfbuzz0b 2.6.4-1ubuntu4
 libhogweed5 3.5.1+really3.5.1-2ubuntu0.2
 libice6 2:1.0.10-0ubuntu1
 libicu66 66.1-2ubuntu2
 libidn11 1.33-2.2ubuntu2
 libidn2-0 2.2.0-2
 libijs-0.35 0.35-15
 libjbig0 2.1-3.1build1
 libjbig2dec0 0.18-1ubuntu1
 libjpeg-turbo8 2.0.3-0ubuntu1.20.04.1
 libjpeg8 8c-2ubuntu8
 libjson-glib-1.0-0 1.4.4-2ubuntu2
 libjson-glib-1.0-common 1.4.4-2ubuntu2
 libk5crypto3 1.17-6ubuntu4.1
 libkeyutils1 1.6-6ubuntu1
 libkrb5-3 1.17-6ubuntu4.1
 libkrb5support0 1.17-6ubuntu4.1
 liblcms2-2 2.9-4
 liblocale-gettext-perl 1.07-4
 liblqr-1-0 0.4.2-2.1
 libltdl7 2.4.6-14
 liblz4-1 1.9.2-2ubuntu0.20.04.1
 liblzma5 5.2.4-1ubuntu1
 libm17n-0 1.8.0-2
 libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1ubuntu11.4
 libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1ubuntu11.4
 libmount1 2.34-0.1ubuntu9.1
 libnettle7 3.5.1+really3.5.1-2ubuntu0.2
 libopenjp2-7 2.3.1-1ubuntu4.20.04.1
 libotf0 0.9.13-7
 libp11-kit0 0.23.20-1ubuntu0.1
 libpam-modules 1.3.1-5ubuntu4.2
 libpam-modules-bin 1.3.1-5ubuntu4.2
 libpam0g 1.3.1-5ubuntu4.2
 libpango-1.0-0 1.44.7-2ubuntu4
 libpangocairo-1.0-0 1.44.7-2ubuntu4
 libpangoft2-1.0-0 

[Bug 1628707] Re: Highlighting a region in emacs is invisible because region color equals window color

[Ivan Zakharyaschev]

** Also affects: emacs (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/1628707

Title:
  Highlighting a region in emacs is invisible because region color
  equals window color

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1628707/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945013] [NEW] mysql imposes a silent limit on passwords

[Ivan Popivanov]

Public bug reported:

Install mysql-server package. When configuring, pass a password for root
that is 90 symbols long. Try "mysql -u root -p" afterwards. There will
be a password prompt, pasting the long password will return a login
error. Succeeds for passwords of up to 32 characters.

There is no information online that MYSQL latest version limits
passwords to 32 characters, except for replication. This is a standalone
installation, so something is wrong.

It's time consuming to debug an issue like this so it needs to be
addressed and clearly documented.

** Affects: mysql-8.0 (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/1945013

Title:
  mysql imposes a silent limit on passwords

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1945013/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location

[Ivan]

I would not have that big a problem if Ubuntu had not made it the
preferred way of installing and packaging apps now.

It highlights more fundamental issues with the design of snap, with the
management, and with the way that it was included and promoted. And this
is just one issue that is relatively simple. But if it had been a
serious issue that affected packages, would it also have taken more than
5 years to address?

Is there a way to escalate this to the team at Canonical that made the
decision to bring snap in in the first place?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053

Title:
  Please move the "$HOME/snap" directory to a less obtrusive location

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942600] [NEW] My mousepad isnt working, i dont think it even recognize it

[Ivan Bojanovic]

Public bug reported:

i see that a lot of people had problems with the mousepad, but i dont
know what is the solution and i am new to linux, help me fix my
mousepad, i dont know what the problem is

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  3 12:40:32 2021
InstallationDate: Installed on 2021-09-02 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-signed-hwe-5.11
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942600

Title:
  My mousepad isnt working, i dont think it even recognize it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1942600/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942600] Re: My mousepad isnt working, i dont think it even recognize it

[Ivan Bojanovic]

I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds 
B: PROP=0
B: EV=120013
B: KEY=40200 3803078f800d001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor= Product= Version=
N: Name="Ideapad extra buttons"
P: Phys=ideapad/input0
S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input4
U: Uniq=
H: Handlers=rfkill kbd event4 
B: PROP=0
B: EV=13
B: KEY=81000800100c03 4430 0 2
B: MSC=10

I: Bus=0003 Vendor=174f Product=1176 Version=0028
N: Name="Integrated Camera: Integrated C"
P: Phys=usb-:00:14.0-5/button
S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input6
U: Uniq=
H: Handlers=kbd event6 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus=0019 Vendor= Product=0006 Version=
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
U: Uniq=
H: Handlers=kbd event7 
B: PROP=0
B: EV=3
B: KEY=3e000b 0 0 0

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8
U: Uniq=
H: Handlers=event8 
B: PROP=0
B: EV=21
B: SW=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9
U: Uniq=
H: Handlers=event9 
B: PROP=0
B: EV=21
B: SW=4

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10
U: Uniq=
H: Handlers=event10 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11
U: Uniq=
H: Handlers=event11 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12
U: Uniq=
H: Handlers=event12 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=9"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13
U: Uniq=
H: Handlers=event13 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=10"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14
U: Uniq=
H: Handlers=event14 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=11"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15
U: Uniq=
H: Handlers=event15 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=12"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16
U: Uniq=
H: Handlers=event16 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0003 Vendor=093a Product=2510 Version=0111
N: Name="PixArt USB Optical Mouse"
P: Phys=usb-:00:14.0-1/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:093A:2510.0002/input/input17
U: Uniq=
H: Handlers=mouse0 event5 
B: PROP=0
B: EV=17
B: KEY=7 0 0 0 0
B: REL=903
B: MSC=10

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942600

Title:
  My mousepad isnt working, i dont think it even recognize it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1942600/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939565] Re: kernel signed by mok failed to boot if secure boot is on

[Ivan Hu]

Follow up the tests for comment#12,

the same test kernel v5.14.0-rc7 signed with the original created key in
/var/lib/shim-signed/test_kernel will not boot up with getting the
invalid signature error.

compare the keys between /var/lib/shim-signed/test_kernel and
comment#12(/var/lib/test_ker/), the fail one(in /var/lib/shim-
signed/test_kernel) has the (1.3.6.1.4.1.2312.16.1.2) KeyUsage OID.

It seems it is because using the "Module-signing only"
(1.3.6.1.4.1.2312.16.1.2) KeyUsage OID to sign the test kernel that
cause signature verify failed.

@YC
I know the OEM projects base on the my EFI applicaiton and script to 
generate/enroll MOK keys for test kernels, 
https://github.com/Ivanhu5866/MokEnrollKey/blob/master/mok_testkernel_key.sh
Could you provide the exact script how the MOK has been generated/enrolled and 
maybe openssl.cnf for checking?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939565

Title:
  kernel signed by mok failed to boot if secure boot is on

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1939565/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939565] Re: kernel signed by mok failed to boot if secure boot is on

[Ivan Hu]

Got the Latitude 7520 machine, from the shim's log, it seems something
wrong in the self signed certificate and the binary is not authorized.

And do some tests, basically base on the comment#6, install another test
kernel and signed/enrolled with another MOK key manually.

1. install test kernel(unsigned), v5.14.0-rc7
2. shim and grub have already been updated.
3. create a MOK key 
   * mkdir -p /var/lib/test_ker/
   * openssl genrsa -out /var/lib/test_ker/TestKer.priv 2048
   * openssl req -new -x509 -sha256 -subj '/CN=TestKer-key' -key 
/var/lib/test_ker/TestKer.priv -out /var/lib/test_ker/TestKer.pem
   * openssl x509 -in /var/lib/test_ker/TestKer.pem -inform PEM -out 
/var/lib/test_ker/TestKer.der -outform DER
4. signed kernel
  * sbsign --key /var/lib/test_ker/TestKer.priv --cert 
/var/lib/test_ker/TestKer.pem --output vmlinuz-5.14.0-051400rc7-generic.signed 
vmlinuz-5.14.0-051400rc7-generic
6. enroll mok key
 * mokutil --import Testker.der
7. reboot

The test kernel 5.14 and MOK key work normally.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939565

Title:
  kernel signed by mok failed to boot if secure boot is on

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1939565/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939565] Re: kernel signed by mok failed to boot if secure boot is on

[Ivan Hu]

Test again  with my UEFI develop kit(RainbowPass) platform by following
procedures and still cannot reproduce this issue.

1. install focal
2. update shim-signed to 1.40.6+15.4.0ubuntu7 and grub2 to 2.04-1ubuntu26.12
3. install mainline kernel(unsigned), 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.18/
4. signed kernel module and enrolled key to MOK( install a DKMS and followed 
the official procedures)
5. run the script and EFI application to signed key and enroll key to MOK(need 
to disable secureboot first), 
https://github.com/Ivanhu5866/MokEnrollKey/blob/master/mok_testkernel_key.sh
this basically is the same procedure as OEM image installation.
6. reboot

@YC
per talk, please enable the shim log for me to check first by
$sudo mokutil --set-verbosity true

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939565

Title:
  kernel signed by mok failed to boot if secure boot is on

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1939565/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939565] Re: kernel signed by mok failed to boot if secure boot is on

[Ivan Hu]

After singing kernel modules and enroll key to MOK, still cannot
reproduce this with my UEFI develop kit(RainbowPass) platform.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939565

Title:
  kernel signed by mok failed to boot if secure boot is on

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1939565/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939565] Re: kernel signed by mok failed to boot if secure boot is on

[Ivan Hu]

Manually test with my UEFI develop kit(RainbowPass) platform by
following procedures and cannot reproduce this issue.

1. install focal
2. update shim-signed to 1.40.6+15.4.0ubuntu7 and grub2 to 2.04-1ubuntu26.12
3. install mainline kernel(unsigned), 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.18/
4. check or create test kernel key
   * mkdir -p /var/lib/test_ker/
   * openssl genrsa -out /var/lib/test_ker/TestKer.priv 2048
   * openssl req -new -x509 -sha256 -subj '/CN=TestKer-key' -key 
/var/lib/test_ker/TestKer.priv -out /var/lib/test_ker/TestKer.pem
   * openssl x509 -in /var/lib/test_ker/TestKer.pem -inform PEM -out 
/var/lib/test_ker/TestKer.der -outform DER
5. signed kernel
  * sbsign --key /var/lib/test_ker/TestKer.priv --cert 
/var/lib/test_ker/TestKer.pem --output vmlinuz-5.8.18-05.0818-generic.signed 
vmlinuz-5.8.18-05.0818-generic
6. enroll mok key
 * mokutil --import Testker.der
7. reboot

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939565

Title:
  kernel signed by mok failed to boot if secure boot is on

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1939565/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938678] Re: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H

[Ivan Hu]

The setting,
Go to Advanced menu> TPM configuration > TCG2 Configuration > enable PCR Bank  
PCR Bank: SM3_256 [x ]

is for PCR Bank supported Hash Algorithm.

Here, what Ethan mentioned is for remove the SM3_256 supported for the
platform, not only the PCR bank SM3_256 supported.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938678

Title:
  [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on
  TGL-H

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1938678/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939565] Re: kernel signed by mok failed to boot if secure boot is on

[Ivan Hu]

@ycheng-twn

Have you also updated the Grub2?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939565

Title:
  kernel signed by mok failed to boot if secure boot is on

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1939565/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938678] Re: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H

[Ivan Hu]

Snapd is not using the tpm2-tss, so it is not the same as mentioned in
https://bugs.launchpad.net/intel/+bug/1936899/comments/10.

Instead, snapd is using go-tpm2 from comment#15.
Per talk to Ethan, he is building newer version which has some defined values 
of SM3_256 for testing, let's wait for the testing result.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938678

Title:
  [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on
  TGL-H

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1938678/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936899] Re: [IoTG] [TGL-H] TPM tests fail

[Ivan Hu]

For the tpm2_loadexternal, and tpm2_import tests, the failure seems from
RSA private key 1024 bit no support for this platform. So TPM returned
ErrorCode (0x02c4), "value is out of range or is not correct for the
context"

+ openssl genrsa -aes128 -passout pass:mypassword -out private.pem 1024
Generating RSA private key, 1024 bit long modulus (2 primes)
.+
...+
e is 65537 (0x010001)
+ '[' pass:mypassword '!=' stdin ']'
+ cmd='tpm2_loadexternal -Q -G rsa -r private.pem -c key.ctx --passin 
pass:mypassword'
+ eval tpm2_loadexternal -Q -G rsa -r private.pem -c key.ctx --passin 
pass:mypassword
++ tpm2_loadexternal -Q -G rsa -r private.pem -c key.ctx --passin 
pass:mypassword
WARNING:esys:src/tss2-esys/api/Esys_LoadExternal.c:304:Esys_LoadExternal_Finish()
 Received TPM Error 
ERROR:esys:src/tss2-esys/api/Esys_LoadExternal.c:108:Esys_LoadExternal() Esys 
Finish ErrorCode (0x02c4) 
ERROR: Esys_LoadExternal(0x2C4) - tpm:parameter(2):value is out of range or is 
not correct for the context
ERROR: Unable to run tpm2_loadexternal

From the PTP spec"TCG PC Client Platform TPM Profile Specification for TPM 2.0",
Table2. PC Client TPM Algorithms
It described,
TPM_ALG_RSA M Support for 2048-bit keys is required; the TPM SHOULD NOT support 
1024-bit keys.

So I think this could be safely ignored, if 1024 key is not supported.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936899

Title:
  [IoTG] [TGL-H] TPM tests fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1936899/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936899] Re: [IoTG] [TGL-H] TPM tests fail

[Ivan Hu]

For the tpm2_createprimary tests,

The failures are both from tpm2_createprimary whit hash-algorithm
sm3_256

+ tpm2_createprimary -Q -g sm3_256 -G rsa -c context.out
ERROR:esys_crypto:src/tss2-esys/esys_crypto_ossl.c:103:iesys_cryptossl_hash_start()
 ErrorCode (0x00070002) Unsupported hash algorithm (18) 
ERROR:esys:src/tss2-esys/esys_iutil.c:1493:iesys_get_name() crypto hash start 
ErrorCode (0x00070002) 
ERROR:esys:src/tss2-esys/api/Esys_CreatePrimary.c:426:Esys_CreatePrimary_Finish()
 ErrorCode (0x00070011) in Public name not equal name in response 
ERROR:esys:src/tss2-esys/api/Esys_CreatePrimary.c:135:Esys_CreatePrimary() Esys 
Finish ErrorCode (0x00070011) 
ERROR: Esys_CreatePrimary(0x70011) - esapi:Response is malformed
ERROR:esys:src/tss2-esys/esys_iutil.c:1134:iesys_check_sequence_async() Esys 
called in bad sequence. 
ERROR:esys:src/tss2-esys/api/Esys_FlushContext.c:66:Esys_FlushContext() Error 
in async function ErrorCode (0x00070007) 
ERROR: Esys_FlushContext(0x70007) - esapi:Function called in the wrong order
ERROR: Unable to run tpm2_createprimary

the latest tpm2_tests will first check the platform supported hash algorithms, 
then do the tests with the hash algorithms.
But test with it, got
ERROR:esys_crypto:src/tss2-esys/esys_crypto_ossl.c:103:iesys_cryptossl_hash_start()
 ErrorCode (0x00070002) Unsupported hash algorithm (18)

Checking the tpm2-tss code, the sm3_256, so got the Unsupported hash algorithm 
return from tpm2-tss.
Below is the tss support hash,
get_ossl_hash_md(TPM2_ALG_ID hashAlg)
{
switch (hashAlg) {
case TPM2_ALG_SHA1:
return EVP_sha1();
break;
case TPM2_ALG_SHA256:
return EVP_sha256();
break;
case TPM2_ALG_SHA384:
return EVP_sha384();
break;
case TPM2_ALG_SHA512:
return EVP_sha512();
break;
default:
return NULL;
}
}

From the latest Spec "TCG PC Client Platform TPM Profile Specification for TPM 
2.0, Version 1.05
Revision 14 September 4, 2020"
I found that "sm3_256" is optional.
So, I think this failure could be safely ignored.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936899

Title:
  [IoTG] [TGL-H] TPM tests fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1936899/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936899] Re: [IoTG] [TGL-H] TPM tests fail

[Ivan Hu]

For the tpm2_clockrateadjust test fail,

+ tpm2_clockrateadjust s
WARNING:esys:src/tss2-esys/api/Esys_ClockRateAdjust.c:287:Esys_ClockRateAdjust_Finish()
 Received TPM Error 
ERROR:esys:src/tss2-esys/api/Esys_ClockRateAdjust.c:100:Esys_ClockRateAdjust() 
Esys Finish ErrorCode (0x01c4) 
ERROR: Esys_ClockRateAdjust(0x1C4) - tpm:parameter(1):value is out of range or 
is not correct for the context
ERROR: Unable to run tpm2_clockrateadjust

it occurred on the tpm2_clockrateadjust to slow down the clock period
one fine increment and got the "value is out of range or is not correct
for the context" from TPM.

It is due to the platform unsupported the clock rate adjust, it is known
that some firmware TPM do not support this function, please check if
this platform is firmware TPM, and check with your TPM vendors.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936899

Title:
  [IoTG] [TGL-H] TPM tests fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1936899/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939259] [NEW] xtables-addons-dkms 3.9-1ubuntu0.2~20.04.1: xtables-addons kernel module failed to build

[Ivan Biscaldi]

Public bug reported:

The bug appeared after turning on the PC. 
-Ubuntu 20.04 lts

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: xtables-addons-dkms 3.9-1ubuntu0.2~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.11.0-25-generic
Date: Sun Aug  8 23:12:00 2021
DuplicateSignature: 
dkms:xtables-addons-dkms:3.9-1ubuntu0.2~20.04.1:/var/lib/dkms/xtables-addons/3.9/build/extensions/pknock/xt_pknock.c:263:20:
 error: implicit declaration of function ‘get_seconds’ 
[-Werror=implicit-function-declaration]
InstallationDate: Installed on 2020-12-14 (237 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
PackageVersion: 3.9-1ubuntu0.2~20.04.1
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: xtables-addons
Title: xtables-addons-dkms 3.9-1ubuntu0.2~20.04.1: xtables-addons kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xtables-addons (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/1939259

Title:
  xtables-addons-dkms 3.9-1ubuntu0.2~20.04.1: xtables-addons kernel
  module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1939259/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900254] Re: fails to suspend unless I unbind a device from elants_i2c driver

[Ivan Zakharyaschev]

** Also affects: linux-signed-hwe-5.8 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=207759
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900254

Title:
  fails to suspend unless I unbind a device from elants_i2c driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1900254/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend

[Ivan]

In addition to my previous comment:
I have the latest bios for my laptop: 1.19.0
I also have tried these kernel versions:
5.4.0-26.30
5.11.0-25.27~20.04.1

without any success.

I'm attaching report file from `apport-collect -p linux ` and I'm ready
for any further debug.

** Attachment added: "apport.linux.muox5fp0.apport"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+attachment/5514100/+files/apport.linux.muox5fp0.apport

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909005

Title:
  Ubuntu does not resume (wake up) from suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend

[Ivan]

The same problem with
Latitude 7290
xubuntu 20.04.2
kernel 5.8.0-63-generic #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:08 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909005

Title:
  Ubuntu does not resume (wake up) from suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1830979] Re: org.gtk.setting.file-chooser.location-mode setting is not respected and is reset to path-bar

[Ivan Zakharyaschev]

This issue is also discussed at
.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830979

Title:
  org.gtk.setting.file-chooser.location-mode setting is not respected
  and is reset to path-bar

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1830979/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1830979] Re: org.gtk.setting.file-chooser.location-mode setting is not respected and is reset to path-bar

[Ivan Zakharyaschev]

https://gitlab.gnome.org/GNOME/gtk/-/issues/938 :

In a reddit thread [1] someone pointed to the source code where
location-mode is not loaded when the dialog opens [2] (presumably using
the default) but it does save the value when closed. [3]

[1]: 
https://www.reddit.com/r/linuxquestions/comments/7579w0/gsettings_value_getting_overwritten_after_setting/
[2]: 
https://git.gnome.org/browse/gtk+/tree/gtk/gtkfilechooserwidget.c?h=gtk-3-22#n3877
[3]: 
https://git.gnome.org/browse/gtk+/tree/gtk/gtkfilechooserwidget.c?h=gtk-3-22#n3916

GTK developers' response
https://gitlab.gnome.org/GNOME/gtk/-/issues/938#note_111883 :

It is a private gtk setting, you don't really have any business tweaking
it. It may disappear at any point.

* * *

As for me personally, I'd still like to be able to configure it,
particularly, for typing the path on the File Chooser in Firefox, as
discussed in https://bugzilla.mozilla.org/show_bug.cgi?id=374011#c133
and https://bugzilla.mozilla.org/show_bug.cgi?id=1518742

** Bug watch added: Mozilla Bugzilla #374011
   https://bugzilla.mozilla.org/show_bug.cgi?id=374011

** Bug watch added: Mozilla Bugzilla #1518742
   https://bugzilla.mozilla.org/show_bug.cgi?id=1518742

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830979

Title:
  org.gtk.setting.file-chooser.location-mode setting is not respected
  and is reset to path-bar

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1830979/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1830979] Re: org.gtk.setting.file-chooser.location-mode setting is not respected and is reset to path-bar

[Ivan Zakharyaschev]

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #938
   https://gitlab.gnome.org/GNOME/gtk/-/issues/938

** Also affects: gtk via
   https://gitlab.gnome.org/GNOME/gtk/-/issues/938
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830979

Title:
  org.gtk.setting.file-chooser.location-mode setting is not respected
  and is reset to path-bar

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1830979/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1933547] Re: tpm driver causes non-fatal kernel crash on boot

[Ivan Hu]

The kernel seems try to set up the interrupt and send data, but failed.
After got error returned, the kernel will disable interrupt and using polling 
instead.

I beleve it will have the following messages in dmesg log
kernel: tpm tpm0: tpm_try_transmit: send(): error -62
kernel: tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead

The call trace seems from the patch which add the checking for the invalid 
status,
https://patchwork.kernel.org/project/linux-integrity/patch/9bad3da0c31ae2620aaae0d75748c3387afa3d47.ca...@hansenpartnership.com/#23649371

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933547

Title:
  tpm driver causes non-fatal kernel crash on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933547/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928571] Re: Error in rebuld for php8

[Ivan Borzenkov]

also need update version and create package-8.xml

here you can find new version
https://launchpad.net/~ivan1986/+archive/ubuntu/ppa

** Description changed:

  in 1.4.0-8build2 for impish file gnupg.so not exist in package
+ 
+ here you can find new version
+ https://launchpad.net/~ivan1986/+archive/ubuntu/ppa

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928571

Title:
  Error in rebuld for php8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-gnupg/+bug/1928571/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901294] Re: nouveau timeout and system lockup

[Ivan Larionov]

I spoke too soon. This bug is back for me.

** Attachment added: "dmesg_gpu_freeze.log"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+attachment/5502015/+files/dmesg_gpu_freeze.log

** Tags added: hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901294

Title:
  nouveau timeout and system lockup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930170] [NEW] package apache2 2.4.41-4ubuntu3.1 failed to install/upgrade: installed apache2 package post-installation script subprocess returned error exit status 1.

[Ivan Parhamovic]

Public bug reported:

It is happened when I install apache. Maybe because I install nginx
before.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: apache2 2.4.41-4ubuntu3.1
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Apache2ConfdDirListing: False
Apache2Modules:
 Error: command ['/usr/sbin/apachectl', '-D DUMP_MODULES'] failed with exit 
code 1: apache2: Could not open configuration file /etc/apache2/apache2.conf: 
No such file or directory
 Action '-D DUMP_MODULES' failed.
 The Apache error log may have more information.
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun May 30 17:58:40 2021
ErrorMessage: installed apache2 package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2021-05-10 (20 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: apache2
Title: package apache2 2.4.41-4ubuntu3.1 failed to install/upgrade: installed 
apache2 package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
error.log:
 
modified.conffile..etc.apache2.apache2.conf: [deleted]
modified.conffile..etc.apache2.conf-available.charset.conf: [deleted]
modified.conffile..etc.apache2.conf-available.localized-error-pages.conf: 
[deleted]
modified.conffile..etc.apache2.conf-available.other-vhosts-access-log.conf: 
[deleted]
modified.conffile..etc.apache2.conf-available.security.conf: [deleted]
modified.conffile..etc.apache2.conf-available.serve-cgi-bin.conf: [deleted]
modified.conffile..etc.apache2.envvars: [deleted]
modified.conffile..etc.apache2.magic: [deleted]
modified.conffile..etc.apache2.mods-available.access_compat.load: [deleted]
modified.conffile..etc.apache2.mods-available.actions.conf: [deleted]
modified.conffile..etc.apache2.mods-available.actions.load: [deleted]
modified.conffile..etc.apache2.mods-available.alias.conf: [deleted]
modified.conffile..etc.apache2.mods-available.alias.load: [deleted]
modified.conffile..etc.apache2.mods-available.allowmethods.load: [deleted]
modified.conffile..etc.apache2.mods-available.asis.load: [deleted]
modified.conffile..etc.apache2.mods-available.auth_basic.load: [deleted]
modified.conffile..etc.apache2.mods-available.auth_digest.load: [deleted]
modified.conffile..etc.apache2.mods-available.auth_form.load: [deleted]
modified.conffile..etc.apache2.mods-available.authn_anon.load: [deleted]
modified.conffile..etc.apache2.mods-available.authn_core.load: [deleted]
modified.conffile..etc.apache2.mods-available.authn_dbd.load: [deleted]
modified.conffile..etc.apache2.mods-available.authn_dbm.load: [deleted]
modified.conffile..etc.apache2.mods-available.authn_file.load: [deleted]
modified.conffile..etc.apache2.mods-available.authn_socache.load: [deleted]
modified.conffile..etc.apache2.mods-available.authnz_fcgi.load: [deleted]
modified.conffile..etc.apache2.mods-available.authnz_ldap.load: [deleted]
modified.conffile..etc.apache2.mods-available.authz_core.load: [deleted]
modified.conffile..etc.apache2.mods-available.authz_dbd.load: [deleted]
modified.conffile..etc.apache2.mods-available.authz_dbm.load: [deleted]
modified.conffile..etc.apache2.mods-available.authz_groupfile.load: [deleted]
modified.conffile..etc.apache2.mods-available.authz_host.load: [deleted]
modified.conffile..etc.apache2.mods-available.authz_owner.load: [deleted]
modified.conffile..etc.apache2.mods-available.authz_user.load: [deleted]
modified.conffile..etc.apache2.mods-available.autoindex.conf: [deleted]
modified.conffile..etc.apache2.mods-available.autoindex.load: [deleted]
modified.conffile..etc.apache2.mods-available.brotli.load: [deleted]
modified.conffile..etc.apache2.mods-available.buffer.load: [deleted]
modified.conffile..etc.apache2.mods-available.cache.load: [deleted]
modified.conffile..etc.apache2.mods-available.cache_disk.conf: [deleted]
modified.conffile..etc.apache2.mods-available.cache_disk.load: [deleted]
modified.conffile..etc.apache2.mods-available.cache_socache.load: [deleted]
modified.conffile..etc.apache2.mods-available.cern_meta.load: [deleted]
modified.conffile..etc.apache2.mods-available.cgi.load: [deleted]
modified.conffile..etc.apache2.mods-available.cgid.conf: [deleted]
modified.conffile..etc.apache2.mods-available.cgid.load: [deleted]
modified.conffile..etc.apache2.mods-available.charset_lite.load: [deleted]
modified.conffile..etc.apache2.mods-available.data.load: [deleted]
modified.conffile..etc.apache2.mods-available.dav.load: [deleted]
modified.conffile..etc.apache2.mods-available.dav_fs.conf: [deleted]
modified.conffile..etc.apache2.mods-available.dav_fs.load: [deleted]

[Bug 1901294] Re: nouveau timeout and system lockup

[Ivan Larionov]

This is fixed in 21.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901294

Title:
  nouveau timeout and system lockup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

[Ivan D]

Tested on: Ubuntu 21.04
Package: evolution-data-server 3.40.1-2 (from Impish-proposed)

There aren't packages for hursuit (21.04) but I just tried the impish
(21.10) package and works.

Thanks again

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925742

Title:
  Recent iCloud versions trigger an issue in IMAP x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

[Ivan D]

Tested on: Ubuntu 20.04.2 LTS
Package: evolution-data-server 3.36.5-0ubuntu1 amd64

Personal iCloud account, now is solved.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925742

Title:
  Recent iCloud versions trigger an issue in IMAP x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928571] [NEW] Error in rebuld for php8

[Ivan Borzenkov]

Public bug reported:

in 1.4.0-8build2 for impish file gnupg.so not exist in package

** Affects: php-gnupg (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/1928571

Title:
  Error in rebuld for php8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-gnupg/+bug/1928571/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926481] Re: lockf returns false-positive EDEADLK in multiprocess multithreaded environment

[Ivan Zuboff]

Posted info to LKML with topic "lockf returns false-positive EDEADLK in
multiprocess multithreaded environment":
https://lkml.org/lkml/2021/5/15/287

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926481

Title:
  lockf returns false-positive EDEADLK in multiprocess multithreaded
  environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927553] [NEW] Ubuntu install crashed at step 'set timezone' before I pressed any buttons

[Ivan Rodionov]

Public bug reported:

There were no issues with installation before the process suddenly
crushed.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.10
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
Date: Fri May  7 00:09:27 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927553

Title:
  Ubuntu install crashed at step 'set timezone' before I pressed any
  buttons

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1927553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926481] WifiSyslog.txt

[Ivan Zuboff]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1926481/+attachment/5493127/+files/WifiSyslog.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926481

Title:
  lockf returns false-positive EDEADLK in multiprocess multithreaded
  environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926481] UdevDb.txt

[Ivan Zuboff]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1926481/+attachment/5493126/+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/1926481

Title:
  lockf returns false-positive EDEADLK in multiprocess multithreaded
  environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926481] ProcModules.txt

[Ivan Zuboff]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1926481/+attachment/5493125/+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/1926481

Title:
  lockf returns false-positive EDEADLK in multiprocess multithreaded
  environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926481] ProcCpuinfoMinimal.txt

[Ivan Zuboff]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1926481/+attachment/5493123/+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/1926481

Title:
  lockf returns false-positive EDEADLK in multiprocess multithreaded
  environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926481] ProcInterrupts.txt

[Ivan Zuboff]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1926481/+attachment/5493124/+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/1926481

Title:
  lockf returns false-positive EDEADLK in multiprocess multithreaded
  environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926481] ProcCpuinfo.txt

[Ivan Zuboff]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1926481/+attachment/5493122/+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/1926481

Title:
  lockf returns false-positive EDEADLK in multiprocess multithreaded
  environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926481] Lsusb-v.txt

[Ivan Zuboff]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1926481/+attachment/5493121/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926481

Title:
  lockf returns false-positive EDEADLK in multiprocess multithreaded
  environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926481] Lspci-vt.txt

[Ivan Zuboff]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1926481/+attachment/5493120/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926481

Title:
  lockf returns false-positive EDEADLK in multiprocess multithreaded
  environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926481] Lspci.txt

[Ivan Zuboff]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1926481/+attachment/5493119/+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/1926481

Title:
  lockf returns false-positive EDEADLK in multiprocess multithreaded
  environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926481] CurrentDmesg.txt

[Ivan Zuboff]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1926481/+attachment/5493118/+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/1926481

Title:
  lockf returns false-positive EDEADLK in multiprocess multithreaded
  environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926481] Re: lockf returns false-positive EDEADLK in multiprocess multithreaded environment

[Ivan Zuboff]

apport information

** Tags added: apport-collected uec-images

** Description changed:

  As a developer, I found a counter-intuitive behavior in lockf function
  provided by glibc and Linux kernel that is likely a bug.
  
  In glibc, lockf function is implemented on top of fcntl system call: 
https://github.com/lattera/glibc/blob/master/io/lockf.c
  man page says that lockf can sometimes detect deadlock: 
http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html
  Same with fcntl(F_SETLKW), on top of which lockf is implemented: 
http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html
  
  Deadlock detection algorithm 
(https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because 
it can easily give false positives. Suppose we have two processes A and B, 
process A has threads 1 and 2, process B has threads 3 and 4. When this 
processes execute concurrently, following sequence of actions is possible:
  1. processA thread1 gets lockI
  2. processB thread2 gets lockII
  3. processA thread3 tries to get lockII, starts to wait
  4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is 
returned from lockf function
  
  Steps to reproduce this scenario (see attached file):
  1. gcc -o edeadlk ./edeadlk.c -lpthread
  2. Launch "./edeadlk a b" in first terminal window.
  3. Launch "./edeadlk a b" in second terminal window.
  
  What I expected to happen: two instances of the program is steadily
  working.
  
  What happened instead:
  Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, 
errno:35 . Error:: Resource deadlock avoided
  Aborted (core dumped)
  
  Surely, this behavior is kind of "right". lockf file locks belongs to
  process, so on the process level it seems that deadlock is just about to
  happen: process A holds lockI and waits for lockII, process B holds
  lockII and is going to wait for lockI. However, algorithm in kernel
  doesn't take threads into account. In fact, deadlock is not gonna happen
  here if thread scheduler will give control to some thread holding a
  lock.
  
  I think there's a problem with deadlock detection algorithm because it's
  overly pessimistic, which in turn creates problems -- lockf errors in
  applications.
  
  # lsb_release -rd
  Description:Ubuntu 20.04.1 LTS
  Release:20.04
  
  # uname -a
  Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 ноя 12 09:53 seq
+  crw-rw 1 root audio 116, 33 ноя 12 09:53 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.20.11-0ubuntu27.4
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CasperMD5CheckResult: pass
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-07-22 (280 days ago)
+ InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lsusb:
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 004: ID 0a89:0030 Aktiv Rutoken ECP
+  Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
+  Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ Lsusb-t:
+  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
+  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
+  |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
+  |__ Port 1: Dev 4, If 0, Class=Chip/SmartCard, Driver=, 12M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
+ MachineType: VMware, Inc. VMware Virtual Platform
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=ru_RU.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 svgadrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=1d0fe562-8128-4922-836e-b0a384fc5054 ro maybe-ubiquity
+ ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-42-generic N/A
+  linux-backports-modules-5.4.0-42-generic  N/A
+  linux-firmware1.187.2
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+ Tags:  focal uec-images
+ Uname: Linux 5.4.0-42-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 09/21/2015
+ dmi.bios.vendor: Phoenix Technologies LTD
+ dmi.bios.version: 6.00
+ dmi.board.name: 440BX Desktop Reference Platform
+ dmi.board.vendor: Intel Corporation
+ dmi.board.version: None
+ dmi.chassis.asset.tag: No Asset Tag
+ 

[Bug 1926481] [NEW] lockf returns false-positive EDEADLK in multiprocess multithreaded environment

[Ivan Zuboff]

Public bug reported:

As a developer, I found a counter-intuitive behavior in lockf function
provided by glibc and Linux kernel that is likely a bug.

In glibc, lockf function is implemented on top of fcntl system call: 
https://github.com/lattera/glibc/blob/master/io/lockf.c
man page says that lockf can sometimes detect deadlock: 
http://manpages.ubuntu.com/manpages/xenial/man3/lockf.3.html
Same with fcntl(F_SETLKW), on top of which lockf is implemented: 
http://manpages.ubuntu.com/manpages/hirsute/en/man3/fcntl.3posix.html

Deadlock detection algorithm 
(https://github.com/torvalds/linux/blob/master/fs/locks.c) seems buggy because 
it can easily give false positives. Suppose we have two processes A and B, 
process A has threads 1 and 2, process B has threads 3 and 4. When this 
processes execute concurrently, following sequence of actions is possible:
1. processA thread1 gets lockI
2. processB thread2 gets lockII
3. processA thread3 tries to get lockII, starts to wait
4. processB thread4 tries to get lockI, kernel detects deadlock, EDEADLK is 
returned from lockf function

Steps to reproduce this scenario (see attached file):
1. gcc -o edeadlk ./edeadlk.c -lpthread
2. Launch "./edeadlk a b" in first terminal window.
3. Launch "./edeadlk a b" in second terminal window.

What I expected to happen: two instances of the program is steadily
working.

What happened instead:
Assertion failed: (lockf(fd, 1, 1)) != -1 file: ./edeadlk.c, line:25, errno:35 
. Error:: Resource deadlock avoided
Aborted (core dumped)

Surely, this behavior is kind of "right". lockf file locks belongs to
process, so on the process level it seems that deadlock is just about to
happen: process A holds lockI and waits for lockII, process B holds
lockII and is going to wait for lockI. However, algorithm in kernel
doesn't take threads into account. In fact, deadlock is not gonna happen
here if thread scheduler will give control to some thread holding a
lock.

I think there's a problem with deadlock detection algorithm because it's
overly pessimistic, which in turn creates problems -- lockf errors in
applications.

# lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04

# uname -a
Linux test-x64-ub20 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "test to reproduce the problem"
   https://bugs.launchpad.net/bugs/1926481/+attachment/5493082/+files/edeadlk.c

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926481

Title:
  lockf returns false-positive EDEADLK in multiprocess multithreaded
  environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs