[Bug 2083807] [NEW] package thunderbird 1:115.15.0+build1-0ubuntu0.22.04.1 failed to install/upgrade: 新的 thunderbird 软件包 pre-installation 脚本 子进程返回错误状态 1

2024-10-06 Thread Ke LI
Public bug reported:

None

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: thunderbird 1:115.15.0+build1-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
Uname: Linux 5.15.0-91-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
BuildID: 20240903191356
CasperMD5CheckResult: pass
Channel: Unavailable
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Mon Oct  7 13:42:16 2024
ErrorMessage: 新的 thunderbird 软件包 pre-installation 脚本 子进程返回错误状态 1
ForcedLayersAccel: False
IfupdownConfig:
 
InstallationDate: Installed on 2021-05-10 (1245 days ago)
InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
IpRoute:
 default via 192.168.2.1 dev eno4 proto static 
 192.168.2.0/24 dev eno4 proto kernel scope link src 192.168.2.4
NoProfiles: True
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
 No PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04.1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.3
 apt  2.4.13
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Title: package thunderbird 1:115.15.0+build1-0ubuntu0.22.04.1 failed to 
install/upgrade: 新的 thunderbird 软件包 pre-installation 脚本 子进程返回错误状态 1
UpgradeStatus: Upgraded to jammy on 2024-10-07 (0 days ago)
dmi.bios.date: 07/20/2015
dmi.bios.release: 1.50
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 2.30
dmi.modalias: 
dmi:bvnHP:bvrP89:bd07/20/2015:br1.50:efr2.30:svnHP:pnProLiantDL388Gen9:pvr:cvnHP:ct23:cvr:sku775451-AA1:
dmi.product.family: ProLiant
dmi.product.name: ProLiant DL388 Gen9
dmi.product.sku: 775451-AA1
dmi.sys.vendor: HP

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


** Tags: amd64 apport-package jammy third-party-packages uec-images

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

Title:
  package thunderbird 1:115.15.0+build1-0ubuntu0.22.04.1 failed to
  install/upgrade: 新的 thunderbird 软件包 pre-installation 脚本 子进程返回错误状态 1

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


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

[Bug 2081940] Re: package shim-signed 1.51.3+15.7-0ubuntu1 failed to install/upgrade: 已安装 shim-signed 软件包 post-installation 脚本 子进程返回错误状态 127

2024-10-05 Thread Hongbo Li
Hey James,

I also encountered this problem days before. And I find the answer in
this link quite helpful. Maybe you could have a try.

https://askubuntu.com/questions/1481336/var-lib-dpkg-info-shim-signed-
postinst-165-usr-lib-grub-grub-multi-install

Best

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

Title:
  package shim-signed 1.51.3+15.7-0ubuntu1 failed to install/upgrade:
  已安装 shim-signed 软件包 post-installation 脚本 子进程返回错误状态 127

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


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

[Bug 2058192] Re: [MIR] lenovo-wwan-unlock

2024-09-29 Thread Bin Li
I updated the rules, and the issue in #16 is fixed.

debian/opt.fcc_lenovo.DPR_Fcc_unlock_service
Original file line number   Diff line numberDiff line change
@@ -18,6 +18,7 @@ include 
  /usr/bin/ps Uxr,
  /usr/sbin/dmidecode Cx,
  /usr/libexec/mbim-proxy mrix,
  /opt/fcc_lenovo/lib/*.so mrix,

  owner /dev/ r,
  owner /dev/wwan0at0 rw,

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

Title:
  [MIR] lenovo-wwan-unlock

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


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

[Bug 2058192] Re: [MIR] lenovo-wwan-unlock

2024-09-27 Thread Bin Li
The latest v2.1.2 depends libmbimtools.so, FCC unlock failed because the
the apparmor block this library.

Sep 27 06:52:24 Thames-1 audit[2498]: AVC apparmor="DENIED"
operation="open" class="file"
profile="/opt/fcc_lenovo/DPR_Fcc_unlock_service"
name="/opt/fcc_lenovo/lib/libmbimtools.so" pid=2498
comm="DPR_Fcc_unlock_" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

Sep 27 06:52:24 Thames-1 kernel: audit: type=1400
audit(1727434344.811:80): apparmor="DENIED" operation="open"
class="file" profile="/opt/fcc_lenovo/DPR_Fcc_unlock_service"
name="/opt/fcc_lenovo/lib/libmbimtools.so" pid=2498
comm="DPR_Fcc_unlock_" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

Sep 27 06:52:24 Thames-1 DPR_Fcc_unlock_service[2498]: FCC unlock failed

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

Title:
  [MIR] lenovo-wwan-unlock

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


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

[Bug 2065161] Re: On the second opening, app folder will not close on click outside

2024-09-25 Thread Bin Li
** Tags added: jira-sutton-157

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

Title:
  On the second opening, app folder will not close on click outside

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


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

[Bug 2081965] Re: Closing 'Active Screen Edges' in Settings could not work

2024-09-25 Thread Bin Li
If I disabled the titling-assistant, then this issue is gone.

$ gnome-extensions disable titling-assist...@ubuntu.com

Should the titling-assistant carry on this setting from gnome-shell?
Thanks!

** Tags added: jira-sutton-156

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

Title:
  Closing 'Active Screen Edges' in Settings could not work

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


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

[Bug 2081965] [NEW] Closing 'Active Screen Edges' in Settings could not work

2024-09-25 Thread Bin Li
Public bug reported:

[Summary]

Close the Active Screen Edges, windows can still be resized after
dragging them against screen edges

[Steps to reproduce]
1.Install 24.04
2.Click Settings -> Multitasking -> General, close Active Screen Edges
3.Drag windows against screen edges, check the size of windows

[Expected result]

The windows will remain the same size after closing Active Screen Edges.

[Actual result]

Close Active Screen Edges, windows will still be resized after dragging
them against screen edges.

[Failure rate]

100%

** Affects: gnome-shell-extension-tiling-assistant (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: jira-sutton-156

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

Title:
  Closing 'Active Screen Edges' in Settings could not work

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


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

[Bug 2058192] Re: [MIR] lenovo-wwan-unlock

2024-09-18 Thread Bin Li
hi Seth, Mark

 Thanks for your review, I'm a member of OEM team, we could place the
package in the OEM archive directly, but this would create a gap between
Ubuntu and OEM. We prefer to have the package in the Ubuntu archive so
that more users can access this solution.

 BTW, currently this package is available in oracular.

https://launchpad.net/ubuntu/+source/lenovo-wwan-unlock

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

Title:
  [MIR] lenovo-wwan-unlock

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


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

[Bug 2053217] Re: Pycodestyle 2.11.1 breaks flake8 5.0.4 in noble

2024-09-13 Thread Bin Li
$ apt-cache policy flake8
flake8:
  Installed: 7.0.0-1
  Candidate: 7.0.0-1
  Version table:
 *** 7.0.0-1 500
500 http://mirrors.huaweicloud.com/repository/ubuntu noble/universe 
amd64 Packages
100 /var/lib/dpkg/status

** Changed in: pycodestyle (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Pycodestyle 2.11.1 breaks flake8 5.0.4 in noble

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


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

[Bug 2073430] Re: Automatic Time Zone not working on 24.04

2024-09-11 Thread Bin Li
** Description changed:

+ [Impact]
+ 
  I tick "automatic time zone" in the Date & Time settings, it does
  nothing, and when I return to Date & Time, the option is unselected
  again.
  
  This system is a fresh 24.04 install.
  
  See attached video.
+ 
+ Here is fix from upstream.
+ 
+ https://gitlab.gnome.org/GNOME/gnome-control-
+ center/-/merge_requests/2785
+ 
+ [Test Plan]
+ 
+  * Find a machine with 24.04
+ 
+  * Launch `settings` and enable "automatic time zone" in the Date & Time
+ settings, and close `settings`
+ 
+  * Launch `settings` again to check "automatic time zone" item.
+ 
+ [Where problems could occur]
+ 
+  * This patch is picked from upstream, it's low risk.

** Changed in: oem-priority
   Status: Confirmed => Triaged

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

Title:
  Automatic Time Zone not working on 24.04

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


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

[Bug 2073430] Re: Automatic Time Zone not working on 24.04

2024-09-11 Thread Bin Li
https://salsa.debian.org/gnome-team/gnome-control-
center/-/merge_requests/42

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

Title:
  Automatic Time Zone not working on 24.04

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


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

[Bug 2073430] Re: Automatic Time Zone not working on 24.04

2024-09-11 Thread Bin Li
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3157

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

Title:
  Automatic Time Zone not working on 24.04

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


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

[Bug 2073430] Re: Automatic Time Zone not working on 24.04

2024-09-11 Thread Bin Li
This issue is fixed in upstream of gnome-control-center

commit 801d7312484c2ba690f6efd09c1501fd0101fef0
Author: Daniel DeGrasse 
Date:   Mon Aug 12 08:41:38 2024 -0700

datetime: fix disabling of auto timezone during panel load

Commit 021fce8c9 (datetime: Don't show Auto Timezone setting
without location services) added code that unconditionally disables
the "automatic-timezone" dconf key while loading the datetime
panel view. Make this code conditional, so it only executes if
HAVE_LOCATION_SERVICES is not defined by the compiler.

Fixes #3157

Signed-off-by: Daniel DeGrasse 
(cherry picked from commit 213650b521073fade14410d57fae9f3d46cadbf9)

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #3157
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3157

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

Title:
  Automatic Time Zone not working on 24.04

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


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

[Bug 2073430] Re: Automatic Time Zone not working on 24.04

2024-09-11 Thread Bin Li
After enabling the "automatic time zone" in the Date & Time settings, the value 
is changed from false to true. It's always true until you open the 'Date & 
Time' page of settings again.
So this issue seems to be related to gnome-control-center.

$ gsettings get org.gnome.desktop.datetime automatic-timezone
true

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

Title:
  Automatic Time Zone not working on 24.04

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


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

[Bug 2073430] Re: Automatic Time Zone not working on 24.04

2024-09-11 Thread Bin Li
** Changed in: oem-priority
   Importance: Undecided => Medium

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  Automatic Time Zone not working on 24.04

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


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

[Bug 2073430] Re: Automatic Time Zone not working on 24.04

2024-09-11 Thread Bin Li
** Tags added: oem-priority originate-from-2080213 sutton

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

Title:
  Automatic Time Zone not working on 24.04

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


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

[Bug 2078759] Re: debsums: changed file /lib/netplan/00-network-manager-all.yaml (from ubuntu-settings package)

2024-09-10 Thread Bin Li
@seb128,

 I checked the history, and the comment line has been there since the
first commit. I'm not sure if there's a reason to keep it. Could we
remove the comment line in the YAML file? I just made a MR with the
suggestion from 'Danilo Egea Gondolfo'. Feel free to reject it if it's
not acceptable. Thanks!

commit 38a5c5b213120a2a8d96b3238e4e3f4566a13c4b
Author: Dave Jones 
Date:   Thu May 18 15:33:43 2023 +0100

Move 01-use-network-manager.yaml

To /lib/netplan/ and remove (or move, if modified) the original in
/etc/netplan. Use 00- prefix as agreed at the sprint to ensure it's
first in the configuration order. Finally, use 0600 mode to stop the
newer netplan complaining about the file mode.

diff --git a/data/ubuntu/00-network-manager-all.yaml 
b/data/ubuntu/00-network-manager-all.yaml
new file mode 100644
index 000..4a8fd08
--- /dev/null
+++ b/data/ubuntu/00-network-manager-all.yaml
@@ -0,0 +1,4 @@
+# Let NetworkManager manage all devices on this system
+network:
+  version: 2
+  renderer: NetworkManager


** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

** Changed in: oem-priority
   Importance: Undecided => Medium

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  debsums: changed file /lib/netplan/00-network-manager-all.yaml (from
  ubuntu-settings package)

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


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

[Bug 2078759] Re: debsums: changed file /lib/netplan/00-network-manager-all.yaml (from ubuntu-settings package)

2024-09-10 Thread Bin Li
With Danilo comment #4, it works fine if we could remove the comment.

u@oak2-10:~$ nmcli connection add type dummy ifname d0
Connection 'dummy-d0' (2364f50d-72d5-4849-804d-f6d28467bf93) successfully added.
u@oak2-10:~$ sudo cat /lib/netplan/00-network-manager-all.yaml·
# Let NetworkManager manage all devices on this system
network:
  version: 2
  renderer: NetworkManager
u@oak2-10:~$ sudo md5sum /lib/netplan/00-network-manager-all.yaml
81c200b0e29eeb56c518a23eb78777ab  /lib/netplan/00-network-manager-all.yaml

u@oak2-10:~$ nmcli connection delete dummy-d0·
Connection 'dummy-d0' (2364f50d-72d5-4849-804d-f6d28467bf93) successfully 
deleted.
u@oak2-10:~$ sudo md5sum /lib/netplan/00-network-manager-all.yaml
9b5681f7d3fc877b018790626772c504  /lib/netplan/00-network-manager-all.yaml

u@oak2-10:~$ sudo cat /lib/netplan/00-network-manager-all.yaml
network:
  version: 2
  renderer: NetworkManager

u@oak2-10:~$ nmcli connection add type dummy ifname d1
Connection 'dummy-d1' (f9e7f8f7-d685-4123-88e6-118f70342320) successfully added.
u@oak2-10:~$ sudo md5sum /lib/netplan/00-network-manager-all.yaml
9b5681f7d3fc877b018790626772c504  /lib/netplan/00-network-manager-all.yaml

u@oak2-10:~$ nmcli connection delete dummy-d1·
Connection 'dummy-d1' (f9e7f8f7-d685-4123-88e6-118f70342320) successfully 
deleted.
u@oak2-10:~$ sudo md5sum /lib/netplan/00-network-manager-all.yaml
9b5681f7d3fc877b018790626772c504  /lib/netplan/00-network-manager-all.yaml

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

Title:
  debsums: changed file /lib/netplan/00-network-manager-all.yaml (from
  ubuntu-settings package)

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


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

[Bug 2042394] Re: Support goodix fingerprint [27c6:6582]

2024-09-09 Thread Bin Li
** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  Support goodix fingerprint [27c6:6582]

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


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

[Bug 2073109] Re: nvidia-driver-550 could not be installed on [10de:25b0] and [10de:25b2]

2024-09-03 Thread Bin Li
@Eduard, thanks a lot!

** Changed in: oem-priority
   Status: New => Fix Released

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

Title:
  nvidia-driver-550 could not be installed on [10de:25b0] and
  [10de:25b2]

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


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

[Bug 2054538] Re: Support FPC MOC fingerprint [10a5:d805]

2024-09-03 Thread Bin Li
** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  Support FPC MOC fingerprint [10a5:d805]

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


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

[Bug 2058013] Re: Support Elan fp device [04F3:0C8C]

2024-09-03 Thread Bin Li
** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  Support Elan fp device [04F3:0C8C]

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


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

[Bug 2058202] Re: Support Goodix MoC fingerprint[27C6:659A]

2024-09-03 Thread Bin Li
** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  Support Goodix MoC fingerprint[27C6:659A]

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


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

[Bug 2078759] Re: debsums: changed file /lib/netplan/00-network-manager-all.yaml (from ubuntu-settings package)

2024-09-03 Thread Bin Li
** Tags added: jira-sutton-68

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

Title:
  debsums: changed file /lib/netplan/00-network-manager-all.yaml (from
  ubuntu-settings package)

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


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

[Bug 2078881] [NEW] mlx-bootctl: support RTC battery status read and clear

2024-09-03 Thread Xiangrong Li
Public bug reported:

SRU Justification:

[Impact]

The RTC battery status is not directly accessible from the kernel user
space. The recent Nvidia UEFI added SMC to report the RTC battery status
and clear the status bit if needed.

[Fix]

* Added an rtc_battery entry in the bootctl driver.
* Read the rtc_battery entry will trigger an SMC call to read the RTC battery 
status.

[Test Case]

* Check if the bootctl driver is loaded.
* Check the rtc_battery entry:
cat /sys/bus/platform/drivers/mlxbf-bootctl/rtc_battery
A value of 0x0 means RTC battery voltage is good.
A value of 0x80 means RTC battery voltage is low. The status bit is also 
cleared after the read.
An error code will be return if this feature is missing from UEFI.

[Other]
* This code is likely to change depending on feedback we received from 
maintainers.

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

** Description changed:

  SRU Justification:
  
  [Impact]
  
  The RTC battery status is not directly accessible from the kernel user
  space. The recent Nvidia UEFI added SMC to report the RTC battery status
  and clear the status bit if needed.
  
  [Fix]
  
  * Added an rtc_battery entry in the bootctl driver.
  * Read the rtc_battery entry will trigger an SMC call to read the RTC battery 
status.
  
  [Test Case]
  
  * Check if the bootctl driver is loaded.
  * Check the rtc_battery entry:
- cat /sys/bus/platform/drivers/mlxbf-bootctl/rtc_battery 
+ cat /sys/bus/platform/drivers/mlxbf-bootctl/rtc_battery
  A value of 0x0 means RTC battery voltage is good.
  A value of 0x80 means RTC battery voltage is low. The status bit is also 
cleared after the read.
  An error code will be return if this feature is missing from UEFI.
  
- [Regression Potential]
- 
- The Mellanox driver would fail to be loaded(?).
- 
- * The bootctl driver needs to be loaded.
- * The UEFI firmware needs to be in sync with change.
- 
  [Other]
  * This code is likely to change depending on feedback we received from 
maintainers.

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

Title:
  mlx-bootctl: support RTC battery status read and clear

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


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

[Bug 2078561] [NEW] can't upgrade to 24.04

2024-08-31 Thread li yichen
Public bug reported:

it says:
"... certificate errorserver..."

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.19
ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
Uname: Linux 6.8.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CrashReports:
 600:117:124:37:2024-08-28 07:17:37.772998941 +0800:2024-08-28 
07:17:37.772998941 +0800:/var/crash/_usr_bin_Xwayland.128.uploaded
 644:128:124:0:2024-08-28 07:17:35.412999145 +0800:2024-08-28 
07:17:35.412999145 +0800:/var/crash/_usr_bin_Xwayland.128.upload
 640:128:124:4516049:2024-08-28 07:17:35.412999145 +0800:2024-08-28 
07:17:35.443999142 +0800:/var/crash/_usr_bin_Xwayland.128.crash
 600:0:124:224401:2024-08-29 15:28:13.168237965 +0800:2024-09-01 
02:02:07.077999777 +0800:/var/crash/javascript-common.0.crash
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 31 20:04:20 2024
InstallationDate: Installed on 2024-01-20 (224 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade jammy wayland-session

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

Title:
  can't upgrade to 24.04

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


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

[Bug 2077496] Re: Only one fingerprint can be enrolled on Goodix FP

2024-08-20 Thread Bin Li
** Description changed:

  Only on goodix fingerprint could be enrolled. It will be failed when
  enrolling the second fingerprint.
  
  It sounds a general issue on Goodix Moc devices. Our customer met this
  issue on ThinkPad.
  
+ And this problem was fixed in libfprint 1.94.7(noble/oracular). It
+ sounds we need backport more patches to support 6582.
+ 
  https://bugs.launchpad.net/bugs/2058202
  https://bugs.launchpad.net/bugs/2042394
  
+ We need backport more patches for goodix moc driver. But we need check
+ what's the root cause of the CRC error.
+ 
+ https://salsa.debian.org/ubuntu-dev-team/libfprint/-/merge_requests/18
+ 
+ 
https://salsa.debian.org/ubuntu-dev-team/libfprint/-/commit/86566e8d0b7b36ebaa5588af75b46e2c93a12918
+ 
https://salsa.debian.org/ubuntu-dev-team/libfprint/-/commit/0bf7d58c5ea0c23b6d9371785af691e25f82a0f8
+ 
https://salsa.debian.org/ubuntu-dev-team/libfprint/-/commit/8552290becac51a89c9ff54dc82e6b2b896d4015
+ 
  OS: 22.04
  libfprint2-2 1:1.94.3+tod1-0ubuntu2~22.04.08

** Tags added: oem-priority originate-from-2058011 sutton

** Tags added: originate-from-2051323

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

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

Title:
  Only one fingerprint can be enrolled on Goodix FP

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


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

[Bug 2042394] Re: Support goodix fingerprint [27c6:6582]

2024-08-20 Thread Bin Li
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2042394

Title:
  Support goodix fingerprint [27c6:6582]

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


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

[Bug 2077496] [NEW] Only one fingerprint can be enrolled on Goodix FP

2024-08-20 Thread Bin Li
Public bug reported:

Only on goodix fingerprint could be enrolled. It will be failed when
enrolling the second fingerprint.

It sounds a general issue on Goodix Moc devices. Our customer met this
issue on ThinkPad.

https://bugs.launchpad.net/bugs/2058202
https://bugs.launchpad.net/bugs/2042394

OS: 22.04
libfprint2-2 1:1.94.3+tod1-0ubuntu2~22.04.08

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

** Attachment added: "659a_1fprint.mp4"
   
https://bugs.launchpad.net/bugs/2077496/+attachment/5807587/+files/659a_1fprint.mp4

** Description changed:

  Only on goodix fingerprint could be enrolled. It will be failed when
  enrolling the second fingerprint.
  
  It sounds a general issue on Goodix Moc devices. Our customer met this
  issue on ThinkPad.
  
  https://bugs.launchpad.net/bugs/2058202
  https://bugs.launchpad.net/bugs/2042394
+ 
+ OS: 22.04
+ libfprint2-2 1:1.94.3+tod1-0ubuntu2~22.04.08

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

Title:
  Only one fingerprint can be enrolled on Goodix FP

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


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

[Bug 2042394] Re: Support goodix fingerprint [27c6:6582]

2024-08-20 Thread Bin Li
** Changed in: libfprint (Ubuntu)
   Status: New => Fix Released

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

Title:
  Support goodix fingerprint [27c6:6582]

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


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

[Bug 2058202] Re: Support Goodix MoC fingerprint[27C6:659A]

2024-08-20 Thread Bin Li
After installing the libfprint2-2 1:1.94.3+tod1-0ubuntu2~22.04.08 from
proposed, Goodix MoC PID 659a works fine.

System: ThinkPad E16 Gen 1
OS: Ubuntu 22.04.4 LTS
Kernel: 6.5.0-1018-oem
FPR: Goodix MOC PID 659a

** Changed in: oem-priority
   Status: In Progress => Fix Committed

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

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

Title:
  Support Goodix MoC fingerprint[27C6:659A]

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


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

[Bug 2042394] Re: Support goodix fingerprint [27c6:6582]

2024-08-20 Thread Bin Li
After installing the new package 1:1.94.3+tod1-0ubuntu2~22.04.08 in
proposed, the new device was recognized and could be used.

System: ThinkPad X1 Carbon Gen 11
OS: Ubuntu 22.04.4 LTS
Kernel: 6.5.0-1016-oem
FPR: Goodix MOC PID 6582

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

** Changed in: oem-priority
   Status: Triaged => Fix Committed

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

Title:
  Support goodix fingerprint [27c6:6582]

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


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

[Bug 2058013] Re: Support Elan fp device [04F3:0C8C]

2024-08-19 Thread Bin Li
After installing the libfprint-2-2 from proposed, I could find the
'Fingerprint Login' option in 'settings'. I enabled `Fingerprint Login`
and enrolled right index finger and then logout, I could Login system
with enrolled finger successfully.

* Find a machine with this fingerprint device

u@Wei2-3:~$ lsusb | grep Elan
Bus 001 Device 002: ID 04f3:0c8c Elan Microelectronics Corp. ELAN:ARM-M4

u@Wei2-3:~$ apt-cache policy libfprint-2-2·
libfprint-2-2:
  Installed: 1:1.94.3+tod1-0ubuntu2~22.04.07
  Candidate: 1:1.94.3+tod1-0ubuntu2~22.04.08
  Version table:
 1:1.94.3+tod1-0ubuntu2~22.04.08 500
500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 
Packages
 *** 1:1.94.3+tod1-0ubuntu2~22.04.07 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:1.94.3+tod1-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

ubuntu@Wei2-3:~$ fprintd-verify
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
 - #0: right-index-finger
Verify started!
Verifying: right-index-finger
Verify result: verify-match (done)

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

** Changed in: oem-priority
   Status: In Progress => Fix Committed

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

Title:
  Support Elan fp device [04F3:0C8C]

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


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

[Bug 2054538] Re: Support FPC MOC fingerprint [10a5:d805]

2024-08-18 Thread Bin Li
After installing the libfprint-2-2 from proposed, I could find the
'Fingerprint Login' option in 'settings'. I enabled `Fingerprint Login`
and enrolled right index finger and then logout, I could Login system
with enrolled finger successfully.

* Find a machine with this fingerprint device
ubuntu@Jing2-2:~$ lsusb  | grep FPC
Bus 001 Device 002: ID 10a5:d805 FPC FPC L:0005 FW:2127077

ubuntu@Jing2-2:~$ sudo apt policy libfprint-2-2
libfprint-2-2:
  Installed: 1:1.94.3+tod1-0ubuntu2~22.04.06
  Candidate: 1:1.94.3+tod1-0ubuntu2~22.04.08
  Version table:
 1:1.94.3+tod1-0ubuntu2~22.04.08 500
500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 
Packages
 1:1.94.3+tod1-0ubuntu2~22.04.07 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
 *** 1:1.94.3+tod1-0ubuntu2~22.04.06 100
100 /var/lib/dpkg/status

ubuntu@Jing2-2:~$ fprintd-verify·
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
 - #0: right-index-finger
Verify started!
Verifying: right-index-finger
Verify result: verify-match (done)

** Attachment added: "fpc_testing.png"
   
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2054538/+attachment/5806945/+files/fpc_testing.png

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

** Changed in: oem-priority
   Status: In Progress => Fix Committed

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

Title:
  Support FPC MOC fingerprint [10a5:d805]

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


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

[Bug 2042394] Re: Support goodix fingerprint [27c6:6582]

2024-08-08 Thread Bin Li
Currently we only add d/p/goodixmoc-Add-PID-0x6582.patch to support this
fingerprint.

I reverted the 3 below patches because of potential regression. And it
has merged into jammy.

https://salsa.debian.org/ubuntu-dev-team/libfprint/-/merge_requests/21

 d/p/goodix-Reset-device-if-storage-listing-fails.patch
 d/p/goodixmoc-Fix-missing-enroll-create-state.patch
 d/p/goodixmoc-cleanup-enroll-state-machine.patch

And for noble/mantic, the goodixmoc-Add-PID-0x6582.patch has included.
So we just need SRU this issue for jammy.

** Changed in: libfprint (Ubuntu Noble)
   Status: New => Invalid

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

Title:
  Support goodix fingerprint [27c6:6582]

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


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

[Bug 2075495] Re: ipv6 dnat_and_snat does not work in distributed mode

2024-08-01 Thread Reason li
** Description changed:

  Description of problem:
- When I use the following command to configure the ipv6 floating IP, the 
function does not work properly.
+ When I use the following command to configure the ipv6 distributed floating 
IP, the function does not work properly.
  
  ovn-nbctl lr-nat-add ROUTER TYPE EXTERNAL_IP LOGICAL_IP [LOGICAL_PORT
  EXTERNAL_MAC]
  
  version: main
  
  Examples:
  (ovn-sb-db)[root@control03 /]# ovn-nbctl lr-nat-add 
10f6f37a-afb3-46a9-9aa6-91371cdeba1c dnat_and_snat ::8f 
fa16::f816:3eff:fe80:fb38  744e11a6-aa99-4b56-9258-e5429bed043b 
fa:16:3e:19:ba:cc
  
  (ovn-sb-db)[root@control03 /]# ovn-nbctl show 
10f6f37a-afb3-46a9-9aa6-91371cdeba1c
  router 10f6f37a-afb3-46a9-9aa6-91371cdeba1c 
(neutron-278772e5-a800-4c2f-b74f-237dc7b35c8c) (aka route_test_ipv6nat)
- port lrp-44f7bde4-5ecd-44fd-8b95-d87fe60dd750
- mac: "fa:16:3e:58:c8:02"
- networks: ["fa16::1/64"]
- port lrp-d135efaa-ff60-4047-a512-24fe592ebb6a
- mac: "fa:16:3e:f0:f3:d0"
- networks: ["123.123.0.1/24"]
- port lrp-3e9af04c-1e53-42e8-943a-b46ecec15fbe
- mac: "fa:16:3e:19:ba:35"
- networks: ["192.168.0.106/24", "::d1/120"]
- gateway chassis: [324e165cbbeefd8f611f8d6ad0ccca6c 
e4d7d407ee471b88ffe74fc779a26fcf 41ada164f3652920346ca3ed20e6513d]
- nat 8c503bae-a471-4b2f-87ce-2ab585460bee
- external ip: "::8f"
- logical ip: "fa16::f816:3eff:fe80:fb38"
- type: "dnat_and_snat"
+ port lrp-44f7bde4-5ecd-44fd-8b95-d87fe60dd750
+ mac: "fa:16:3e:58:c8:02"
+ networks: ["fa16::1/64"]
+ port lrp-d135efaa-ff60-4047-a512-24fe592ebb6a
+ mac: "fa:16:3e:f0:f3:d0"
+ networks: ["123.123.0.1/24"]
+ port lrp-3e9af04c-1e53-42e8-943a-b46ecec15fbe
+ mac: "fa:16:3e:19:ba:35"
+ networks: ["192.168.0.106/24", "::d1/120"]
+ gateway chassis: [324e165cbbeefd8f611f8d6ad0ccca6c 
e4d7d407ee471b88ffe74fc779a26fcf 41ada164f3652920346ca3ed20e6513d]
+ nat 8c503bae-a471-4b2f-87ce-2ab585460bee
+ external ip: "::8f"
+ logical ip: "fa16::f816:3eff:fe80:fb38"
+ type: "dnat_and_snat"
  
  (ovn-sb-db)[root@control03 /]# ovn-nbctl list nat
  _uuid   : 8c503bae-a471-4b2f-87ce-2ab585460bee
  allowed_ext_ips : []
  exempted_ext_ips: []
  external_ids: {}
  external_ip : "::8f"
  external_mac: "fa:16:3e:19:ba:cc"
  external_port_range : ""
  gateway_port: []
  logical_ip  : "fa16::f816:3eff:fe80:fb38"
  logical_port: "744e11a6-aa99-4b56-9258-e5429bed043b"
  options : {stateless="false"}
  type: dnat_and_snat
  
  Everything works fine up to this point, so keep checking ovn-sb's table 
port_binding
  (ovn-sb-db)[root@control03 /]# ovn-sbctl list port_binding  
4b4ccff5-f030-4c66-b6eb-b7dd43db4f2c
  _uuid   : 4b4ccff5-f030-4c66-b6eb-b7dd43db4f2c
  additional_chassis  : []
  additional_encap: []
  chassis : []
  datapath: b92d5cbf-08a4-49c1-ae24-3a0d7b0b1782
  encap   : []
  external_ids: {"neutron:cidrs"="192.168.0.106/24 ::d1/120", 
"neutron:device_id"="278772e5-a800-4c2f-b74f-237dc7b35c8c", 
"neutron:device_owner"="network:router_gateway", 
"neutron:network_name"=neutron-b6546c61-312a-47ac-9124-d19c9b871e92, 
"neutron:port_name"="", "neutron:project_id"="", 
"neutron:revision_number"="51", "neutron:security_group_ids"=""}
  gateway_chassis : []
  ha_chassis_group: []
  logical_port: "3e9af04c-1e53-42e8-943a-b46ecec15fbe"
  mac : [router]
  nat_addresses   : ["fa:16:3e:19:ba:35 192.168.0.106 
is_chassis_resident(\"cr-lrp-3e9af04c-1e53-42e8-943a-b46ecec15fbe\")"]
  options : {peer=lrp-3e9af04c-1e53-42e8-943a-b46ecec15fbe}
  parent_port : []
  port_security   : []
  requested_additional_chassis: []
  requested_chassis   : []
  tag : []
  tunnel_key  : 3
  type: patch
  up  : false
  virtual_parent  : []
  
  I found that nat_addresses has no information about ipv6
  nat_addresses should have something like this"fa:16:3e:19:ba:cc ::8f 
is_chassis_resident(\"744e11a6-aa99-4b56-9258-e5429bed043b\")"
  
  I add what is missing above to nat_addresses  by hand,then ipv6
  distributed floating IP is functional
  
  So I think there's something wrong with ovn-northd.
  
  Reading the code in northd.c, I see that the get_nat_addresses function
  only checks the external_ip address in IPV4 format.Is this why the ipv6
  configuration was skipped?
  
  northd.c  Line 2381
  static char **
  get_nat_addresses(const struct ovn_port *op, size_t *n, bool routable_only,
-   bool include_lb_ips,
-   const struct lr_stateful_record *lr_stateful_rec)
+   bool include_lb_ips,
+   const struct lr_stateful_record *lr_stateful_rec)

[Bug 2075495] [NEW] ipv6 dnat_and_snat does not work in distributed mode

2024-08-01 Thread Reason li
Public bug reported:

Description of problem:
When I use the following command to configure the ipv6 floating IP, the 
function does not work properly.

ovn-nbctl lr-nat-add ROUTER TYPE EXTERNAL_IP LOGICAL_IP [LOGICAL_PORT
EXTERNAL_MAC]

version: main

Examples:
(ovn-sb-db)[root@control03 /]# ovn-nbctl lr-nat-add 
10f6f37a-afb3-46a9-9aa6-91371cdeba1c dnat_and_snat ::8f 
fa16::f816:3eff:fe80:fb38  744e11a6-aa99-4b56-9258-e5429bed043b 
fa:16:3e:19:ba:cc

(ovn-sb-db)[root@control03 /]# ovn-nbctl show 
10f6f37a-afb3-46a9-9aa6-91371cdeba1c
router 10f6f37a-afb3-46a9-9aa6-91371cdeba1c 
(neutron-278772e5-a800-4c2f-b74f-237dc7b35c8c) (aka route_test_ipv6nat)
port lrp-44f7bde4-5ecd-44fd-8b95-d87fe60dd750
mac: "fa:16:3e:58:c8:02"
networks: ["fa16::1/64"]
port lrp-d135efaa-ff60-4047-a512-24fe592ebb6a
mac: "fa:16:3e:f0:f3:d0"
networks: ["123.123.0.1/24"]
port lrp-3e9af04c-1e53-42e8-943a-b46ecec15fbe
mac: "fa:16:3e:19:ba:35"
networks: ["192.168.0.106/24", "::d1/120"]
gateway chassis: [324e165cbbeefd8f611f8d6ad0ccca6c 
e4d7d407ee471b88ffe74fc779a26fcf 41ada164f3652920346ca3ed20e6513d]
nat 8c503bae-a471-4b2f-87ce-2ab585460bee
external ip: "::8f"
logical ip: "fa16::f816:3eff:fe80:fb38"
type: "dnat_and_snat"

(ovn-sb-db)[root@control03 /]# ovn-nbctl list nat
_uuid   : 8c503bae-a471-4b2f-87ce-2ab585460bee
allowed_ext_ips : []
exempted_ext_ips: []
external_ids: {}
external_ip : "::8f"
external_mac: "fa:16:3e:19:ba:cc"
external_port_range : ""
gateway_port: []
logical_ip  : "fa16::f816:3eff:fe80:fb38"
logical_port: "744e11a6-aa99-4b56-9258-e5429bed043b"
options : {stateless="false"}
type: dnat_and_snat

Everything works fine up to this point, so keep checking ovn-sb's table 
port_binding
(ovn-sb-db)[root@control03 /]# ovn-sbctl list port_binding  
4b4ccff5-f030-4c66-b6eb-b7dd43db4f2c
_uuid   : 4b4ccff5-f030-4c66-b6eb-b7dd43db4f2c
additional_chassis  : []
additional_encap: []
chassis : []
datapath: b92d5cbf-08a4-49c1-ae24-3a0d7b0b1782
encap   : []
external_ids: {"neutron:cidrs"="192.168.0.106/24 ::d1/120", 
"neutron:device_id"="278772e5-a800-4c2f-b74f-237dc7b35c8c", 
"neutron:device_owner"="network:router_gateway", 
"neutron:network_name"=neutron-b6546c61-312a-47ac-9124-d19c9b871e92, 
"neutron:port_name"="", "neutron:project_id"="", 
"neutron:revision_number"="51", "neutron:security_group_ids"=""}
gateway_chassis : []
ha_chassis_group: []
logical_port: "3e9af04c-1e53-42e8-943a-b46ecec15fbe"
mac : [router]
nat_addresses   : ["fa:16:3e:19:ba:35 192.168.0.106 
is_chassis_resident(\"cr-lrp-3e9af04c-1e53-42e8-943a-b46ecec15fbe\")"]
options : {peer=lrp-3e9af04c-1e53-42e8-943a-b46ecec15fbe}
parent_port : []
port_security   : []
requested_additional_chassis: []
requested_chassis   : []
tag : []
tunnel_key  : 3
type: patch
up  : false
virtual_parent  : []

I found that nat_addresses has no information about ipv6
nat_addresses should have something like this"fa:16:3e:19:ba:cc ::8f 
is_chassis_resident(\"744e11a6-aa99-4b56-9258-e5429bed043b\")"

I add what is missing above to nat_addresses  by hand,then ipv6
distributed floating IP is functional

So I think there's something wrong with ovn-northd.

Reading the code in northd.c, I see that the get_nat_addresses function
only checks the external_ip address in IPV4 format.Is this why the ipv6
configuration was skipped?

northd.c  Line 2381
static char **
get_nat_addresses(const struct ovn_port *op, size_t *n, bool routable_only,
  bool include_lb_ips,
  const struct lr_stateful_record *lr_stateful_rec)
{
..
/* Get NAT IP addresses. */
for (size_t i = 0; i < op->od->nbr->n_nat; i++) {
..
char *error = ip_parse_masked(nat->external_ip, &ip, &mask);
if (error || mask != OVS_BE32_MAX) {
free(error);
continue;
}

I think IPV6 address verification should be added here. Please kindly
confirm this problem

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


** Tags: ovn

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

Title:
  ipv6 dnat_and_snat does not work in distributed mode

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


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

[Bug 2054538] Re: Support FPC MOC fingerprint [10a5:d805]

2024-07-31 Thread Bin Li
In oracular/noble, these three patches for jammy are already included in
latest libpfrint-2-2. Please just help upload them for jammy.

libfprint-2-2 1:1.94.7+tod1-0ubuntu5~24.04.1

d/p/fpcmoc-Support-FPC-moc-devices.patch
d/p/fpcmoc-Ensure-the-current-SSM-is-never-overwritten.patch
d/p/fpcmoc-fix-use-after-free-in-multiple-callbacks.patch

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

Title:
  Support FPC MOC fingerprint [10a5:d805]

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


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

[Bug 2058202] Re: Support Goodix MoC fingerprint[27C6:659A]

2024-07-31 Thread Bin Li
In oracular/noble, the patch is already included. Please just help
upload the one for jammy.

libfprint-2-2  1:1.94.7+tod1-0ubuntu5~24.04.1

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

Title:
  Support Goodix MoC fingerprint[27C6:659A]

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


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

[Bug 2054538] Re: Support FPC MOC fingerprint [10a5:d805]

2024-07-31 Thread Bin Li
** Description changed:

- The finger print device cannot work.
+ [Impact]
+ The FPC finger print device[10a5:d805] cannot work.
  
  $ lsusb -s 003 -vv
  Bus 003 Device 003: ID 10a5:d805 FPC FPC L:0002 FW:2127051
  Couldn't open device, some information will be missing
  Device Descriptor:
-   bLength 18
-   bDescriptorType 1
-   bcdUSB 2.00
-   bDeviceClass 0
-   bDeviceSubClass 0
-   bDeviceProtocol 0
-   bMaxPacketSize0 64
-   idVendor 0x10a5
-   idProduct 0xd805
-   bcdDevice 0.51
-   iManufacturer 1 FPC
-   iProduct 2 FPC L:0002 FW:2127051
-   iSerial 0
-   bNumConfigurations 1
-   Configuration Descriptor:
- bLength 9
- bDescriptorType 2
- wTotalLength 0x0019
- bNumInterfaces 1
- bConfigurationValue 1
- iConfiguration 4
- bmAttributes 0xa0
-   (Bus Powered)
-   Remote Wakeup
- MaxPower 100mA
- Interface Descriptor:
-   bLength 9
-   bDescriptorType 4
-   bInterfaceNumber 0
-   bAlternateSetting 0
-   bNumEndpoints 1
-   bInterfaceClass 255 Vendor Specific Class
-   bInterfaceSubClass 255 Vendor Specific Subclass
-   bInterfaceProtocol 255 Vendor Specific Protocol
-   iInterface 5
-   Endpoint Descriptor:
- bLength 7
- bDescriptorType 5
- bEndpointAddress 0x81 EP 1 IN
- bmAttributes 2
-   Transfer Type Bulk
-   Synch Type None
-   Usage Type Data
- wMaxPacketSize 0x0040 1x 64 bytes
- bInterval 0
+   bLength 18
+   bDescriptorType 1
+   bcdUSB 2.00
+   bDeviceClass 0
+   bDeviceSubClass 0
+   bDeviceProtocol 0
+   bMaxPacketSize0 64
+   idVendor 0x10a5
+   idProduct 0xd805
+   bcdDevice 0.51
+   iManufacturer 1 FPC
+   iProduct 2 FPC L:0002 FW:2127051
+   iSerial 0
+   bNumConfigurations 1
+   Configuration Descriptor:
+ bLength 9
+ bDescriptorType 2
+ wTotalLength 0x0019
+ bNumInterfaces 1
+ bConfigurationValue 1
+ iConfiguration 4
+ bmAttributes 0xa0
+   (Bus Powered)
+   Remote Wakeup
+ MaxPower 100mA
+ Interface Descriptor:
+   bLength 9
+   bDescriptorType 4
+   bInterfaceNumber 0
+   bAlternateSetting 0
+   bNumEndpoints 1
+   bInterfaceClass 255 Vendor Specific Class
+   bInterfaceSubClass 255 Vendor Specific Subclass
+   bInterfaceProtocol 255 Vendor Specific Protocol
+   iInterface 5
+   Endpoint Descriptor:
+ bLength 7
+ bDescriptorType 5
+ bEndpointAddress 0x81 EP 1 IN
+ bmAttributes 2
+   Transfer Type Bulk
+   Synch Type None
+   Usage Type Data
+ wMaxPacketSize 0x0040 1x 64 bytes
+ bInterval 0
  
  [Steps to reproduce]
  Boot up the system, try to use the finger print related function.
  
  [Expected result]
  The FPR should work
  
  [Actual result]
  The FPR doesn't work
  
  [Failure rate]
  100%
  
  [Additional information]
  Ubuntu: 22.04
  kernel-version: 6.5.0-1014-oem
+ libfprint-2-2: 1:1.94.3+tod1-0ubuntu2~22.04.07
+ 
+ [Test Plan]
+ 
+  * Find a machine with this fingerprint device
+ 
+  * Launch `settings` and enable `Fingerprint Login`
+ 
+  * Enroll finger and then logout
+ 
+  * Login system with enrolled finger
+ 
+ [Where problems could occur]
+ 
+  * The patch is only for fpcmoc part which is backported from upstream ,
+ it should not affect the other devices.

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

Title:
  Support FPC MOC fingerprint [10a5:d805]

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


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

[Bug 2058202] Re: Support Goodix MoC fingerprint[27C6:659A]

2024-07-31 Thread Bin Li
** Description changed:

- commit 489332c07da4092adf75e28d86e1c9dad744af7a 
- Author: yangdi   
+ 
+ [Impact]
+ The Goodix finger print device [27c6:659a] cannot work on jammy.
+ 
+   usb device: name = 3-6:1.0
+ path = /devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0
+ modalias = "usb:v27C6p659Ad0100dcEFdsc00dp00icFFisc00ip00in00"
+ bInterfaceNumber = 0
+ bInterfaceClass = 255
+ bInterfaceSubClass = 0
+ bInterfaceProtocol = 0
+ if: 3-6:1.0 @ /devices/pci:00/:00:14.0/usb3/3-6
+ bDeviceClass = 239
+ bDeviceSubClass = 0
+ bDeviceProtocol = 0
+ idVendor = 0x27c6
+ idProduct = 0x659a
+ manufacturer = "Goodix Technology Co., Ltd."
+ product = "Goodix USB2.0 MISC"
+ serial = "UID97D3EDA0__MOC_B0"
+ bcdDevice = 0100
+ speed = "12"
+ 
+ It has been supported in https://fprint.freedesktop.org/supported-
+ devices.html, we just need backport below patch for it.
+ 
+ commit 489332c07da4092adf75e28d86e1c9dad744af7a
+ Author: yangdi 
  Date:   Tue Jul 19 11:37:09 2022 +0800
-   
- goodixmoc: add PID 0x659A
+ 
+ goodixmoc: add PID 0x659A
+ 
+ [Steps to reproduce]
+ Boot up the system, try to use the finger print related function.
+ 
+ [Expected result]
+ The FPR should work
+ 
+ [Actual result]
+ The FPR doesn't work
+ 
+ [Failure rate]
+ 100%
+ 
+ [Additional information]
+ Ubuntu: 22.04
+ kernel-version: 6.5.0-1014-oem
+ libfprint-2-2:  1:1.94.3+tod1-0ubuntu2~22.04.07
+ 
+ [Test Plan]
+ 
+  * Find a machine with this fingerprint device
+ 
+  * Launch `settings` and enable `Fingerprint Login`
+ 
+  * Enroll finger and then logout
+ 
+  * Login system with enrolled finger
+ 
+ [Where problems could occur]
+ 
+  * The patch just add new ids to id_table. Should not affect previous
+ supported  device.

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

Title:
  Support Goodix MoC fingerprint[27C6:659A]

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


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

[Bug 2073109] Re: nvidia-driver-550 could not be installed on [10de:25b0] and [10de:25b2]

2024-07-15 Thread Bin Li
** Description changed:

  With two nvidia drivers in oem image, we found the platforms with the
  below ids could not install nvidia-driver-535 or nvidia-driver-550
  successfully.
  
  NVIDIA_DEV.25B0 = "NVIDIA RTX A1000"
  NVIDIA_DEV.25B2 = "NVIDIA RTX A400"
  
  These two ids only in Pmaliases of 550.
  
  pci:v10DEd25B2sv17AAsd1879bc03sc*i*
  
  pci:v10DEd25B0sv17AAsd1878bc03sc*i*
  
- NV: 550.90.07-0ubuntu0.22.04.1
+ NV: 550.90.07-0ubuntu0.22.04.1 and 535.183.01-0ubuntu0.22.04.1

** Description changed:

  With two nvidia drivers in oem image, we found the platforms with the
  below ids could not install nvidia-driver-535 or nvidia-driver-550
  successfully.
  
  NVIDIA_DEV.25B0 = "NVIDIA RTX A1000"
  NVIDIA_DEV.25B2 = "NVIDIA RTX A400"
  
- These two ids only in Pmaliases of 550.
+ These two ids are only in Pmaliases of 550.
  
  pci:v10DEd25B2sv17AAsd1879bc03sc*i*
  
  pci:v10DEd25B0sv17AAsd1878bc03sc*i*
  
  NV: 550.90.07-0ubuntu0.22.04.1 and 535.183.01-0ubuntu0.22.04.1

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

Title:
  nvidia-driver-550 could not be installed on [10de:25b0] and
  [10de:25b2]

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


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

[Bug 2073109] Re: nvidia-driver-550 could not be installed on [10de:25b0] and [10de:25b2]

2024-07-15 Thread Bin Li
From the 550.76, these two ids are supported.

https://download.nvidia.com/XFree86/Linux-x86_64/550.76/README/supportedchips.html

https://download.nvidia.com/XFree86/Linux-x86_64/550.90.07/README/supportedchips.html


NVIDIA RTX A100025B0 1028 1878  K
NVIDIA RTX A100025B0 103C 1878  K
NVIDIA RTX A100025B0 10DE 1878  K
NVIDIA RTX A100025B0 17AA 1878  K
NVIDIA RTX A400 25B2 1028 1879  K
NVIDIA RTX A400 25B2 103C 1879  K
NVIDIA RTX A400 25B2 10DE 1879  K
NVIDIA RTX A400 25B2 17AA 1879  K

** Description changed:

  With two nvidia drivers in oem image, we found the platforms with the
  below ids could not install nvidia-driver-535 or nvidia-driver-550
  successfully.
  
  NVIDIA_DEV.25B0 = "NVIDIA RTX A1000"
  NVIDIA_DEV.25B2 = "NVIDIA RTX A400"
  
  These two ids only in Pmaliases of 550.
  
  pci:v10DEd25B2sv17AAsd1879bc03sc*i*
  
  pci:v10DEd25B0sv17AAsd1878bc03sc*i*
+ 
+ NV: 550.90.07-0ubuntu0.22.04.1

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

Title:
  nvidia-driver-550 could not be installed on [10de:25b0] and
  [10de:25b2]

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


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

[Bug 2073109] Re: nvidia-driver-550 could not be installed on [10de:25b0] and [10de:25b2]

2024-07-15 Thread Bin Li
** Description changed:

  With two nvidia drivers in oem image, we found the platforms with the
  below ids could not install nvidia-driver-535 or nvidia-driver-550
  successfully.
+ 
+ NVIDIA_DEV.25B0 = "NVIDIA RTX A1000"
+ NVIDIA_DEV.25B2 = "NVIDIA RTX A400"
  
  These two ids only in Pmaliases of 550.
  
  pci:v10DEd25B2sv17AAsd1879bc03sc*i*
  
  pci:v10DEd25B0sv17AAsd1878bc03sc*i*

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

Title:
  nvidia-driver-550 could not be installed on [10de:25b0] and
  [10de:25b2]

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


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

[Bug 2073109] Re: nvidia-driver-550 could not be installed on [10de:25b0] and [10de:25b2]

2024-07-15 Thread Bin Li
** Description changed:

- With two nvidia drivers in oem image, we found below ids could not
- install nvidia-driver-535 or nvidia-driver-550 successfully.
+ With two nvidia drivers in oem image, we found the platforms with the
+ below ids could not install nvidia-driver-535 or nvidia-driver-550
+ successfully.
  
  These two ids only in Pmaliases of 550.
  
  pci:v10DEd25B2sv17AAsd1879bc03sc*i*
  
  pci:v10DEd25B0sv17AAsd1878bc03sc*i*

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

Title:
  nvidia-driver-550 could not be installed on [10de:25b0] and
  [10de:25b2]

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


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

[Bug 2073109] [NEW] nvidia-driver-550 could not be installed on [10de:25b0] and [10de:25b2]

2024-07-15 Thread Bin Li
Public bug reported:

With two nvidia drivers in oem image, we found the platforms with the
below ids could not install nvidia-driver-535 or nvidia-driver-550
successfully.

These two ids only in Pmaliases of 550.

pci:v10DEd25B2sv17AAsd1879bc03sc*i*

pci:v10DEd25B0sv17AAsd1878bc03sc*i*

** Affects: oem-priority
 Importance: Undecided
 Status: New

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


** Tags: oem-priority originate-from-2072959 originate-from-2072967 sutton

** Tags added: oem-priority originate-from-2072959 sutton

** Tags added: originate-from-2072967

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

Title:
  nvidia-driver-550 could not be installed on [10de:25b0] and
  [10de:25b2]

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


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

[Bug 2072615] [NEW] Request to add a default profile for bitbake

2024-07-09 Thread Changqing Li
Public bug reported:

From Ubuntu 24.04,  apparmor is enabled by default, and restricts the
use of unprivileged user namespaces.  This change make yocto project,
which use bitbake as build tool failed to build on ubuntu24.04.


Related bug:  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056555

Yocto link:
https://www.yoctoproject.org/
Bitbake doc:
https://docs.yoctoproject.org/bitbake.html

Quick build steps:
1. git clone git://git.yoctoproject.org/poky
2. cd poky
3. source oe-init-build-env
4. bitbake core-image-minimal

I am opening this bug for requesting add a default profile for bitbake.
Since user may clone yocto project anywhere on the host,  it is not a
fixed path, so I recommends the following profile:

$ cat /etc/apparmor.d/bitbake

abi ,
include 
profile bitbake /**/bitbake/bin/bitbake flags=(unconfined) {
userns,
}

** Affects: apparmor (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/2072615

Title:
  Request to add  a  default profile for bitbake

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


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

[Bug 2056555] Re: Python can't write to /proc files

2024-07-08 Thread Changqing Li
The following profile works for me, using ** because user might put the
code anywhere, this might could match any path entry.

$ cat /etc/apparmor.d/bitbake
abi ,
include 
profile bitbake /**/bitbake/bin/bitbake flags=(unconfined) {
userns,
}

$ sudo apparmor_parser -r /etc/apparmor.d/bitbake

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

Title:
  Python can't write to /proc files

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


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

[Bug 1745538] Re: Support for Launchpad teams should be added

2024-07-08 Thread Bin Li
Hi simon,

 Could you help add 'python3-launchpadlib' in Depends? Thanks!

root@1d93703f947c:/# ssh-import-id binli
Traceback (most recent call last):
  File "/usr/bin/ssh-import-id", line 33, in 
sys.exit(load_entry_point('ssh-import-id==5.11', 'console_scripts', 
'ssh-import-id')())
 
^^^
  File "/usr/bin/ssh-import-id", line 25, in importlib_load_entry_point
return next(matches).load()
   
  File "/usr/lib/python3.12/importlib/metadata/__init__.py", line 205, in load
module = import_module(match.group('module'))
 
  File "/usr/lib/python3.12/importlib/__init__.py", line 90, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "", line 1387, in _gcd_import
  File "", line 1360, in _find_and_load
  File "", line 1331, in _find_and_load_unlocked
  File "", line 935, in _load_unlocked
  File "", line 995, in exec_module
  File "", line 488, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/ssh_import_id/__init__.py", line 33, in 

from launchpadlib.launchpad import Launchpad
ModuleNotFoundError: No module named 'launchpadlib'

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

Title:
  Support for Launchpad teams should be added

To manage notifications about this bug go to:
https://bugs.launchpad.net/ssh-import-id/+bug/1745538/+subscriptions


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

[Bug 1931514] Re: SRU: The NVIDIA X server Settings is blank when under Intel mode

2024-07-02 Thread Bin Li
** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  SRU: The NVIDIA X server Settings is blank when under Intel mode

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


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

[Bug 1945565] Re: [SRU] Revert amdgpu/renoir firmware

2024-07-02 Thread Bin Li
** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Revert amdgpu/renoir firmware

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


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

[Bug 1990870] Re: Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

2024-07-02 Thread Bin Li
** No longer affects: oemprocesses

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  Cannot update sutton.newell OEM packages since upgrade to LTS 22.04

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


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

[Bug 2028667] Re: [needs-packaging] fonts-alibaba-puhuiti3

2024-07-02 Thread Bin Li
** Changed in: oem-priority
 Assignee: Bin Li (binli) => (unassigned)

** Changed in: oem-priority
   Status: Triaged => Invalid

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

Title:
  [needs-packaging] fonts-alibaba-puhuiti3

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


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

[Bug 1895780] Re: Update latest pci.ids on focal

2024-07-02 Thread Bin Li
** No longer affects: oem-priority

** Changed in: pciutils (Ubuntu)
   Status: New => Opinion

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

Title:
  Update latest pci.ids on focal

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


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

[Bug 1997505] Re: Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

2024-07-02 Thread Bin Li
** Changed in: oem-priority
   Status: Confirmed => Fix Released

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

Title:
  Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

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


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

[Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

2024-06-26 Thread Daniel Li
Got pretty much same issue, but is just for the internal speaker.
External speakers works fine though. When playing any sound by built-in
speaker, got very noisy electric buzz sound (like old TV/radio without
signal). Tried Ubuntu 24.04, Fedora 40, Pop!Os 22, same issue. And btw
my razer blade is 2022 Advanced model - Razer Blade 15 (2022) -
RZ09-0421. And what I tried was Ubuntu 24.04 LTS.

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

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


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

[Bug 2000459] Re: Only shows half of menu if right-clicks mouse on the desktop if scaling screen

2024-06-18 Thread Bin Li
** Tags added: originate-from-2068111

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

Title:
  Only shows half of menu if right-clicks mouse on the desktop if
  scaling screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/2000459/+subscriptions


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

[Bug 2069261] Re: NV T400E use wrong nv driver

2024-06-13 Thread Bin Li
** Description changed:

- 535 driver match the T400E, but it's supported in 550.
+ 535 driver matches the T400E, and it's installed, but it's supported in
+ 550.
  
  535 pci:v10DEd1FF2sv*sd*bc03sc*i* in Modaliases
  
  550 pci:v10DEd1FF2sv17AAsd18FFbc03sc*i* only in
  Pmaliases
  
- In 550.67's supported gpu json file, 
+ In 550.67's supported gpu json file,
  {
    "devid": "0x1FF2",
    "subdevid": "0x18FF",
    "subvendorid": "0x10DE",
    "name": "NVIDIA T400E",
    "features": [
  "dpycbcr420",
  "dpgsynccompatible",
  "hdmi4k60rgb444",
  "hdmigsynccompatible",
  "runtimepm",
  "vdpaufeaturesetJ",
  "kernelopen"
    ]
  },
  {
    "devid": "0x1FF2",
    "subdevid": "0x1613",
    "subvendorid": "0x17AA",
    "name": "NVIDIA T400 4GB",
    "features": [
  "dpycbcr420",
  "dpgsynccompatible",
  "hdmi4k60rgb444",
  "hdmigsynccompatible",
  "runtimepm",
  "vdpaufeaturesetJ",
  "kernelopen"
    ]
  },
- {
-   "devid": "0x1FF2",
-   "subdevid": "0x18FF",
-   "subvendorid": "0x17AA",
-   "name": "NVIDIA T400E",
-   "features": [
- "dpycbcr420",
- "dpgsynccompatible",
- "hdmi4k60rgb444",
- "hdmigsynccompatible",
- "runtimepm",
- "vdpaufeaturesetJ",
- "kernelopen"
-   ]
- },
+ {
+   "devid": "0x1FF2",
+   "subdevid": "0x18FF",
+   "subvendorid": "0x17AA",
+   "name": "NVIDIA T400E",
+   "features": [
+ "dpycbcr420",
+ "dpgsynccompatible",
+ "hdmi4k60rgb444",
+ "hdmigsynccompatible",
+ "runtimepm",
+ "vdpaufeaturesetJ",
+ "kernelopen"
+   ]
+ },

** Description changed:

- 535 driver matches the T400E, and it's installed, but it's supported in
- 550.
+ 535 driver matches the T400E, and it's installed, but this card is
+ supported in 550.
  
  535 pci:v10DEd1FF2sv*sd*bc03sc*i* in Modaliases
  
  550 pci:v10DEd1FF2sv17AAsd18FFbc03sc*i* only in
  Pmaliases
  
  In 550.67's supported gpu json file,
  {
    "devid": "0x1FF2",
    "subdevid": "0x18FF",
    "subvendorid": "0x10DE",
    "name": "NVIDIA T400E",
    "features": [
  "dpycbcr420",
  "dpgsynccompatible",
  "hdmi4k60rgb444",
  "hdmigsynccompatible",
  "runtimepm",
  "vdpaufeaturesetJ",
  "kernelopen"
    ]
  },
  {
    "devid": "0x1FF2",
    "subdevid": "0x1613",
    "subvendorid": "0x17AA",
    "name": "NVIDIA T400 4GB",
    "features": [
  "dpycbcr420",
  "dpgsynccompatible",
  "hdmi4k60rgb444",
  "hdmigsynccompatible",
  "runtimepm",
  "vdpaufeaturesetJ",
  "kernelopen"
    ]
  },
  {
    "devid": "0x1FF2",
    "subdevid": "0x18FF",
    "subvendorid": "0x17AA",
    "name": "NVIDIA T400E",
    "features": [
  "dpycbcr420",
  "dpgsynccompatible",
  "hdmi4k60rgb444",
  "hdmigsynccompatible",
  "runtimepm",
  "vdpaufeaturesetJ",
  "kernelopen"
    ]
  },

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

Title:
  NV T400E use wrong nv driver

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


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

[Bug 2069261] Re: NV T400E use wrong nv driver

2024-06-13 Thread Bin Li
** Description changed:

  535 driver match the T400E, but it's supported in 550.
  
  535 pci:v10DEd1FF2sv*sd*bc03sc*i* in Modaliases
  
  550 pci:v10DEd1FF2sv17AAsd18FFbc03sc*i* only in
  Pmaliases
  
+ In 550.67's supported gpu json file, 
+ {
+   "devid": "0x1FF2",
+   "subdevid": "0x18FF",
+   "subvendorid": "0x10DE",
+   "name": "NVIDIA T400E",
+   "features": [
+ "dpycbcr420",
+ "dpgsynccompatible",
+ "hdmi4k60rgb444",
+ "hdmigsynccompatible",
+ "runtimepm",
+ "vdpaufeaturesetJ",
+ "kernelopen"
+   ]
+ },
+ {
+   "devid": "0x1FF2",
+   "subdevid": "0x1613",
+   "subvendorid": "0x17AA",
+   "name": "NVIDIA T400 4GB",
+   "features": [
+ "dpycbcr420",
+ "dpgsynccompatible",
+ "hdmi4k60rgb444",
+ "hdmigsynccompatible",
+ "runtimepm",
+ "vdpaufeaturesetJ",
+ "kernelopen"
+   ]
+ },
  {
"devid": "0x1FF2",
"subdevid": "0x18FF",
-   "subvendorid": "0x10DE",
+   "subvendorid": "0x17AA",
"name": "NVIDIA T400E",
"features": [
  "dpycbcr420",
  "dpgsynccompatible",
  "hdmi4k60rgb444",
  "hdmigsynccompatible",
  "runtimepm",
  "vdpaufeaturesetJ",
  "kernelopen"
]
  },
- {
-   "devid": "0x1FF2",
-   "subdevid": "0x1613",
-   "subvendorid": "0x17AA",
-   "name": "NVIDIA T400 4GB",
-   "features": [
- "dpycbcr420",
- "dpgsynccompatible",
- "hdmi4k60rgb444",
- "hdmigsynccompatible",
- "runtimepm",
- "vdpaufeaturesetJ",
- "kernelopen"
-   ]
- },

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

Title:
  NV T400E use wrong nv driver

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


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

[Bug 2069261] [NEW] NV T400E use wrong nv driver

2024-06-13 Thread Bin Li
Public bug reported:

535 driver match the T400E, but it's supported in 550.

535 pci:v10DEd1FF2sv*sd*bc03sc*i* in Modaliases

550 pci:v10DEd1FF2sv17AAsd18FFbc03sc*i* only in
Pmaliases

{
  "devid": "0x1FF2",
  "subdevid": "0x18FF",
  "subvendorid": "0x10DE",
  "name": "NVIDIA T400E",
  "features": [
"dpycbcr420",
"dpgsynccompatible",
"hdmi4k60rgb444",
"hdmigsynccompatible",
"runtimepm",
"vdpaufeaturesetJ",
"kernelopen"
  ]
},
{
  "devid": "0x1FF2",
  "subdevid": "0x1613",
  "subvendorid": "0x17AA",
  "name": "NVIDIA T400 4GB",
  "features": [
"dpycbcr420",
"dpgsynccompatible",
"hdmi4k60rgb444",
"hdmigsynccompatible",
"runtimepm",
"vdpaufeaturesetJ",
"kernelopen"
  ]
},

** Affects: nvidia-graphics-drivers-550 (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/2069261

Title:
  NV T400E use wrong nv driver

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


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

[Bug 2067672] Re: [SRU] Openssl copyright/changelog.Debian.gz file points at non-existent location

2024-06-06 Thread Bin Li
I need someone from the sponsor team to help upload the new package for
noble. From the changelog, I found 'Steve Langasek' which is from
sponsor team.

Hi vorlon,

 Could you help this in noble? Thanks!

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

Title:
  [SRU] Openssl copyright/changelog.Debian.gz file points at non-
  existent location

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


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

[Bug 2064064] Re: Add support of TAS2781 amp of audio

2024-06-03 Thread Bin Li
With the linux-firmware 20220329.git681281e4-0ubuntu3.31 in jammy-
proposed,  audio play via 2 speakers normally with 1023-oem kernel.

** Tags added: verification-done-jammy

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

Title:
  Add support of TAS2781 amp of audio

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2064064/+subscriptions


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

[Bug 2067672] Re: [SRU] Openssl copyright/changelog.Debian.gz file points at non-existent location

2024-06-02 Thread Bin Li
hi adrien,

 Thanks, and will the noble use 3.2.1? 
 And yes, our worry is the copyright file, especially in noble. :)

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

Title:
  [SRU] Openssl copyright/changelog.Debian.gz file points at non-
  existent location

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


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

[Bug 2067672] Re: Openssl copyright/changelog.Debian.gz file points at non-existent location

2024-05-31 Thread Bin Li
** Description changed:

- On 24.04, it's the wrong link location, and it should be libssl3t64.
+ [ Impact ]
  
+  * In OEM projects, our customers need check every copyright of
+ packages.
+ 
+ [ Test Plan ]
+ 
+  * list the openssl or libssl-dev to check if symbol link is valid.
+$ l -thal /usr/share/doc/libssl-dev/
+$ l -thal /usr/share/doc/openssl/
+$ file /usr/share/doc/libssl-dev/copyright
+$ file /usr/share/doc/openssl/copyright
+ 
+ [ Where problems could occur ]
+ 
+  * It didn't affects any functions, just the symbol links are misssing.
+ 
+ [ Other Info ]
+  Currently it link to the old version libssl3, currently libssl3 is purely 
virtual.
+ 
+ $ l -thal /usr/share/doc/openssl-dev/
  lrwxrwxrwx1 root root   30 May 14 17:06 changelog.Debian.gz -> 
../libssl3/changelog.Debian.gz
  lrwxrwxrwx1 root root   23 May 14 17:06 changelog.gz -> 
../libssl3/changelog.gz
  lrwxrwxrwx1 root root   20 May 14 17:06 copyright -> ../libssl3/copyright
  
  $ l -thal /usr/share/doc/libssl-dev/
  total 84K
  drwxr-xr-x2 root root 4.0K May 23 16:08 ./
  drwxr-xr-x 2180 root root  76K May 16 20:13 ../
  lrwxrwxrwx1 root root   30 May 14 17:06 changelog.Debian.gz -> 
../libssl3/changelog.Debian.gz
  lrwxrwxrwx1 root root   23 May 14 17:06 changelog.gz -> 
../libssl3/changelog.gz
  lrwxrwxrwx1 root root   20 May 14 17:06 copyright -> ../libssl3/copyright

** Summary changed:

- Openssl copyright/changelog.Debian.gz file points at non-existent location
+ [SRU] Openssl copyright/changelog.Debian.gz file points at non-existent 
location

** Changed in: oem-priority
   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/2067672

Title:
  [SRU] Openssl copyright/changelog.Debian.gz file points at non-
  existent location

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


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

[Bug 2067672] Re: Openssl copyright/changelog.Debian.gz file points at non-existent location

2024-05-31 Thread Bin Li
Here is defdiff for oracular

** Patch added: "openssl_3.0.13-0ubuntu5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2067672/+attachment/5784588/+files/openssl_3.0.13-0ubuntu5.debdiff

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

Title:
  Openssl copyright/changelog.Debian.gz file points at non-existent
  location

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


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

[Bug 2067672] Re: Openssl copyright/changelog.Debian.gz file points at non-existent location

2024-05-31 Thread Bin Li
Here the debdiff for noble

** Patch added: "openssl_3.0.13-0ubuntu3.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2067672/+attachment/5784495/+files/openssl_3.0.13-0ubuntu3.2.debdiff

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

Title:
  Openssl copyright/changelog.Debian.gz file points at non-existent
  location

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


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

[Bug 2067672] Re: Openssl copyright/changelog.Debian.gz file points at non-existent location

2024-05-30 Thread Bin Li
** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

** Changed in: oem-priority
   Status: New => In Progress

** Description changed:

  On 24.04, it's the wrong link location, and it should be libssl3t64.
  
  lrwxrwxrwx1 root root   30 May 14 17:06 changelog.Debian.gz -> 
../libssl3/changelog.Debian.gz
  lrwxrwxrwx1 root root   23 May 14 17:06 changelog.gz -> 
../libssl3/changelog.gz
  lrwxrwxrwx1 root root   20 May 14 17:06 copyright -> ../libssl3/copyright
+ 
+ $ l -thal /usr/share/doc/libssl-dev/
+ total 84K
+ drwxr-xr-x2 root root 4.0K May 23 16:08 ./
+ drwxr-xr-x 2180 root root  76K May 16 20:13 ../
+ lrwxrwxrwx1 root root   30 May 14 17:06 changelog.Debian.gz -> 
../libssl3/changelog.Debian.gz
+ lrwxrwxrwx1 root root   23 May 14 17:06 changelog.gz -> 
../libssl3/changelog.gz
+ lrwxrwxrwx1 root root   20 May 14 17:06 copyright -> ../libssl3/copyright

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

Title:
  Openssl copyright/changelog.Debian.gz file points at non-existent
  location

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


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

[Bug 2067672] [NEW] Openssl copyright/changelog.Debian.gz file points at non-existent location

2024-05-30 Thread Bin Li
Public bug reported:

On 24.04, it's the wrong link location, and it should be libssl3t64.

lrwxrwxrwx1 root root   30 May 14 17:06 changelog.Debian.gz -> 
../libssl3/changelog.Debian.gz
lrwxrwxrwx1 root root   23 May 14 17:06 changelog.gz -> 
../libssl3/changelog.gz
lrwxrwxrwx1 root root   20 May 14 17:06 copyright -> ../libssl3/copyright

** Affects: oem-priority
 Importance: High
 Assignee: Bin Li (binli)
 Status: In Progress

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


** Tags: oem-priority originate-from-2067643 sutton

** Description changed:

- It's the wrong link location, and it should be libssl3t64.
+ On noble, it's the wrong link location, and it should be libssl3t64.
  
  lrwxrwxrwx1 root root   30 May 14 17:06 changelog.Debian.gz -> 
../libssl3/changelog.Debian.gz
  lrwxrwxrwx1 root root   23 May 14 17:06 changelog.gz -> 
../libssl3/changelog.gz
  lrwxrwxrwx1 root root   20 May 14 17:06 copyright -> ../libssl3/copyright

** Description changed:

- On noble, it's the wrong link location, and it should be libssl3t64.
+ On 24.04, it's the wrong link location, and it should be libssl3t64.
  
  lrwxrwxrwx1 root root   30 May 14 17:06 changelog.Debian.gz -> 
../libssl3/changelog.Debian.gz
  lrwxrwxrwx1 root root   23 May 14 17:06 changelog.gz -> 
../libssl3/changelog.gz
  lrwxrwxrwx1 root root   20 May 14 17:06 copyright -> ../libssl3/copyright

** Tags added: oem-priority originate-from-2067643 sutton

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

Title:
  Openssl copyright/changelog.Debian.gz file points at non-existent
  location

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


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

[Bug 2063529] Re: Add support for Quectel RM520N-GL modem

2024-04-29 Thread Bin Li
** Description changed:

  [Impact]
  
- * Add support for Quectel RM520N-GL modem, so the device could be
- properly probed.
+ * Add support for Quectel RM520N-GL modem, so the device could be properly 
+ probed.
+ 
+ 08:00.0 Unassigned class [ff00]: Quectel Wireless Solutions Co., Ltd. Device 
[1eac:1007]
+ Subsystem: Quectel Wireless Solutions Co., Ltd. Device [1eac:100b]
  
  [Test Plan]
  
  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.
  
  [Where problems could occur]
  
  * These commits only introduces a PID, it won't impact devices which are
  supported originally.
  
  [Other Info]
  
  * Upstream commits:
    
https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e
    
https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081
  * Lenovo with this device will be enabled by linux-oem-6.5.

** Summary changed:

- Add support for Quectel RM520N-GL modem
+ Add support for Quectel RM520N-GL modem [1eac:1007]

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

Title:
  Add support for Quectel RM520N-GL modem [1eac:1007]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063529/+subscriptions


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

[Bug 2063399] Re: Add support for Quectel EM160R-GL modem [1eac:100d]

2024-04-29 Thread Bin Li
** Summary changed:

- Add support for Quectel EM160R-GL modem
+ Add support for Quectel EM160R-GL modem [1eac:100d]

** Description changed:

  [Impact]
  
  * Add support for Quectel EM160R-GL modem, so the device could be
  properly probed.
+ 
+ 08:00.0 Unassigned class [ff00]: Quectel Wireless Solutions Co., Ltd. Device 
[1eac:100d]
+ Subsystem: Quectel Wireless Solutions Co., Ltd. Device [1eac:5004]
  
  [Test Plan]
  
  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.
  
  [Where problems could occur]
  
  * The commit only introduces a PID, it won't impact devices which are
  supported originally.
  
  [Other Info]
  
  * Upstream commit: 
https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5
  * Lenovo with this device will be enabled by linux-oem-6.5.

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

Title:
  Add support for Quectel EM160R-GL modem [1eac:100d]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063399/+subscriptions


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

[Bug 2063977] [NEW] upgrade from 20.04 to 22.04 crashes

2024-04-27 Thread Li Chiu
Public bug reported:

upgrade show the following error:


Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

 This was likely caused by:
 * Unofficial software packages not provided by Ubuntu
Please use the tool 'ppa-purge' from the ppa-purge 
package to remove software from a Launchpad PPA and 
try the upgrade again.

If none of this applies, then please report this bug using the command
'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to
investigate this yourself the log files in '/var/log/dist-upgrade' will
contain details about the upgrade. Specifically, look at 'main.log' and
'apt.log'.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.41
ProcVersionSignature: Ubuntu 5.15.0-105.115~20.04.1-generic 5.15.148
Uname: Linux 5.15.0-105-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 28 10:17:49 2024
InstallationDate: Installed on 2021-05-16 (1077 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2024-04-28 (0 days ago)
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade focal third-party-packages

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

Title:
  upgrade from 20.04 to 22.04 crashes

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


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

[Bug 1977986] Re: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad

2024-04-25 Thread Bin Li
** Tags added: originate-from-2063092

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

Title:
  UPower and battery indicator show update in 2 minutes  when connecting
  power cable ThinkPad

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


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

[Bug 2063288] Re: nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

2024-04-25 Thread Bin Li
Hi timo,

 Do you have any timeline to put these ids into Modaliases nvidia-550
for 22.04? Thanks!

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

Title:
  nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

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


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

[Bug 2063288] Re: nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

2024-04-25 Thread Bin Li
Dirk found 10de:28b9 and 10de:2717 only found in Pmaliases section but
not able to find in Modaliases section of nvidia-driver-550

It should be related to this issue.

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-550/+bug/2061830

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

Title:
  nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

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


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

[Bug 2063288] Re: nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

2024-04-24 Thread Bin Li
** Tags added: oem-priority originate-from-2049497 sutton

** Changed in: oem-priority
   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/2063288

Title:
  nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

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


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

[Bug 2063288] Re: nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

2024-04-24 Thread Bin Li
I also find this issue might not just related 28B9.

Another card RTX4090(10de:2717), also could reproduce this issue.

I guess if the card is supported in 535 and 550 at the same time,
ubuntu-drivers will only list 535.

RTX 500 Ada (10de:28BA) is only supported in 550, ubuntu-drivers could
list the 550 driver successfully.

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

Title:
  nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

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


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

[Bug 2063288] Re: nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

2024-04-23 Thread Bin Li
535.171.04 supports the 28B9.

From apt-cache show nvidia-driver-535, it's also the same modalias.

pci:v10DEd28B9sv*sd*bc03sc*i*

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

Title:
  nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

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


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

[Bug 2063288] [NEW] nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

2024-04-23 Thread Bin Li
Public bug reported:

$ ubuntu-drivers list
nvidia-driver-535-open, (kernel modules provided by 
linux-modules-nvidia-535-open-oem-22.04d)
nvidia-driver-550-server-open, (kernel modules provided by 
nvidia-dkms-550-server-open)
nvidia-driver-535, (kernel modules provided by 
linux-modules-nvidia-535-oem-22.04d)
nvidia-driver-550-server, (kernel modules provided by nvidia-dkms-550-server)

u@Libra2v1-6:~$ lspci -nn | grep NV
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:28b9] 
(rev a1)
01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22be] (rev a1)

$ cat /sys/devices/pci:00/:00:01.0/:01:00.0/modalias
pci:v10DEd28B9sv17AAsd2306bc03sc00i00

From apt-cache show nvidia-driver-500, I could find the modalias below.

pci:v10DEd28B9sv*sd*bc03sc*i*

** Affects: nvidia-graphics-drivers-550 (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/2063288

Title:
  nvidia-driver-550 could not be installed on RTX 1000 Ada[10de:28B9]

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


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

[Bug 2062417] [NEW] the appindicator is almost invisible

2024-04-18 Thread LI Daobing
Public bug reported:

as the screenshot in attachment, the flameshot appindicator is almost
invisible under Ubuntu 22.04+GNOME Desktop

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

** Attachment added: "Screenshot from 2024-04-18 13-24-02.png"
   
https://bugs.launchpad.net/bugs/2062417/+attachment/5767658/+files/Screenshot%20from%202024-04-18%2013-24-02.png

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

Title:
  the appindicator is almost invisible

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


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

[Bug 2049570] Re: 10de:28B9 was not supported in nvidia-driver-535

2024-04-17 Thread Bin Li
535.171.04 is supported the 28B9.

available: 535.171.04-0ubuntu0.22.04.1 [distro] non-free
modalias: pci:v10DEd28B9sv17AAsd2234bc03sc02i00
path: /sys/devices/pci:00/:00:01.0/:01:00.0
vendor: NVIDIA Corporation
support level: PB

** Changed in: oem-priority
   Status: New => Fix Released

** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  10de:28B9 was not supported in nvidia-driver-535

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


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

[Bug 2054538] Re: Support FPC MOC fingerprint [10a5:d805]

2024-04-11 Thread Bin Li
https://salsa.debian.org/ubuntu-dev-team/libfprint/-/merge_requests/19

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

Title:
  Support FPC MOC fingerprint [10a5:d805]

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


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

[Bug 2042394] Re: Support goodix fingerprint [27c6:6582]

2024-04-11 Thread Bin Li
After installing the new package
libfprint-2-2_1.94.3+tod1-0ubuntu2~22.04.07binli5_amd64.deb, the problem
has been fixed. Please see attached files.

  * d/p/goodix-Reset-device-if-storage-listing-fails.patch
d/p/goodixmoc-Fix-missing-enroll-create-state.patch
d/p/goodixmoc-cleanup-enroll-state-machine.patch
d/p/goodixmoc-Add-PID-0x6582.patch (LP: #2042394)

https://launchpad.net/~binli/+archive/ubuntu/ppa/+files/libfprint-2-2_1.94.3+tod1-0ubuntu2~22.04.07binli5_amd64.deb

System: Panther-3
OS: Ubuntu 22.04.4 LTS
Kernel: 6.5.0-1016-oem
FPR: Goodix MOC PID 6582


** Attachment added: "journal_6582_fixed.txt"
   
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2042394/+attachment/5763608/+files/journal_6582_fixed.txt

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

Title:
  Support goodix fingerprint [27c6:6582]

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


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

[Bug 2058013] Re: Support Elan fp device [04F3:0C8C]

2024-04-10 Thread Bin Li
After installed the testing package, it works fine on ThinkPad E16.

libfprint (1:1.94.3+tod1-0ubuntu2~22.04.07binli5) jammy; urgency=medium

  * d/p/elanmoc-add-PID-0x0c8c-0x0c8d.patch (LP: #2058013)


https://launchpad.net/~binli/+archive/ubuntu/ppa/+files/libfprint-2-2_1.94.3+tod1-0ubuntu2~22.04.07binli5_amd64.deb

** Attachment added: "fprintd-debug.log"
   
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2058013/+attachment/5763273/+files/fprintd-debug.log

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

Title:
  Support Elan fp device [04F3:0C8C]

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


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

[Bug 2058013] Re: Support Elan fp device [04F3:0C8C]

2024-04-10 Thread Bin Li
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058013

Title:
  Support Elan fp device [04F3:0C8C]

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


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

[Bug 2054538] Re: Support FPC MOC fingerprint [10a5:d805]

2024-04-09 Thread Bin Li
Our customer met an crash issue, we need another patch for this issue.

traps: fprintd[1445] general protection fault ip:7dd9fde85d26
sp:7ffc98ac2ec0 error:0 in libglib-2.0.so.0.7200.4[7dd 9fde2d000+8f000]

https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/526
https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/421

** Bug watch added: gitlab.freedesktop.org/libfprint/libfprint/-/issues #526
   https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/526

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

Title:
  Support FPC MOC fingerprint [10a5:d805]

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


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

[Bug 2042394] Re: Support goodix fingerprint [27c6:6582]

2024-04-08 Thread Bin Li
https://salsa.debian.org/ubuntu-dev-team/libfprint/-/merge_requests/18

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

Title:
  Support goodix fingerprint [27c6:6582]

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


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

[Bug 2054538] Re: Support FPC MOC fingerprint [10a5:d805]

2024-04-08 Thread Bin Li
D805 works fine with these two patches.

https://launchpad.net/~binli/+archive/ubuntu/ppa/+files/libfprint-2-2_1.94.3+tod1-0ubuntu2~22.04.07binli1_amd64.deb

  * d/p/fpcmoc-Support-FPC-moc-devices.patch (LP: #2054538)
d/p/fpcmoc-Ensure-the-current-SSM-is-never-overwritten.patch

** Attachment added: "d805.log"
   
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2054538/+attachment/5762118/+files/d805.log

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

Title:
  Support FPC MOC fingerprint [10a5:d805]

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


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

[Bug 2054538] Re: Support FPC MOC fingerprint [10a5:d805]

2024-04-08 Thread Bin Li
https://salsa.debian.org/ubuntu-dev-team/libfprint/-/merge_requests/17

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

Title:
  Support FPC MOC fingerprint [10a5:d805]

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


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

[Bug 2054538] Re: Support FPC MOC fingerprint [10a5:d805]

2024-04-08 Thread Bin Li
For D805, another patch is needed.

From c782298ae49be33bc271476c4136cf8732b44436 Mon Sep 17 00:00:00 2001
From: haoweilo 
Date: Fri, 28 Oct 2022 15:47:43 +0800
Subject: [PATCH] fpcmoc: Ensure the current SSM is never overwritten

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

Title:
  Support FPC MOC fingerprint [10a5:d805]

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


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

[Bug 2058202] Re: Support Goodix MoC fingerprint[27C6:659A]

2024-04-08 Thread Bin Li
https://salsa.debian.org/ubuntu-dev-team/libfprint/-/merge_requests/16

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

Title:
  Support Goodix MoC fingerprint[27C6:659A]

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


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

[Bug 2058013] Re: Support Elan fp device [04F3:0C8C]

2024-04-08 Thread Bin Li
https://salsa.debian.org/ubuntu-dev-team/libfprint/-/merge_requests/15

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

Title:
  Support Elan fp device [04F3:0C8C]

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


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

[Bug 2058013] Re: Support Elan fp device [04F3:0C8C]

2024-04-08 Thread Bin Li
** Description changed:

  This patch is upstreamed:
  
  -
  https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/374
  
  [Impact]
  
-  * Support Elan [04f3:0c8c] fingerprint component.
+  * Support Elan [04f3:0c8c] fingerprint component.
  
  [Test Plan]
  
-  * Find a machine with this fingerprint device
+  * Find a machine with other fingerprint device (e.g. 04f3:0c8c)
  
-  * Find a machine with other fingerprint device (e.g. 04f3:0c8c)
+  * Launch `settings` and enable `Fingerprint Login`
  
-  * Launch `settings` and enable `Fingerprint Login`
+  * Enroll finger and then logout on both machines.
  
-  * Enroll finger and then logout on both machines.
- 
-  * Login system with enrolled finger on both machines.
+  * Login system with enrolled finger on both machines.
  
  [Where problems could occur]
  
-  * The patch also includes part for [04f3:0c8d].
-  * We did the similar support for 04f3:0c99. Bug #2031872 , the risk is low.
+  * The patch also includes part for [04f3:0c8d].
+  * We did the similar support for 04f3:0c99. Bug #2031872 , the risk is low.

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

Title:
  Support Elan fp device [04F3:0C8C]

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


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

[Bug 2042394] Re: Support goodix fingerprint [27c6:6582]

2024-04-03 Thread Bin Li
** Tags removed: originate-from-2040124
** Tags added: originate-from-2051323

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

Title:
  Support goodix fingerprint [27c6:6582]

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


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

[Bug 2058202] Re: Support Goodix MoC fingerprint[27C6:659A]

2024-04-03 Thread Bin Li
** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

** Changed in: oem-priority
   Status: New => In Progress

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

Title:
  Support Goodix MoC fingerprint[27C6:659A]

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


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

[Bug 2054538] Re: Support FPC MOC fingerprint [10a5:d805]

2024-04-03 Thread Bin Li
@3v1n0,

 Yes, gpb works fine in my side. Another question, currently we have 4
bugs needed SRU, do you prefer one debdiff file or 4 separated debdiff
files? Thanks!

https://code.launchpad.net/~binli/libfprint/+git/libfprint/+ref/ubuntu/jammy-
devel-d805

d/p/fpcmoc-Support-FPC-moc-devices.patch (LP: #2054538)
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2054538

d/p/elanmoc-add-PID-0x0c8c-0x0c8d.patch (LP: #2058013)
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2058013

d/p/goodixmoc-add-PID-0x659A.patch (LP: #2058202)
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2058202

d/p/goodixmoc-Add-PID-0x6582.patch (LP: #2042394)
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2042394

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

** Changed in: oem-priority
   Status: New => In Progress

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

Title:
  Support FPC MOC fingerprint [10a5:d805]

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


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

[Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

2024-03-27 Thread Bin Li
** Changed in: libmbim (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: libmbim (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

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


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

[Bug 2049569] Re: Enable the mic-mute led on Dell MTL laptops

2024-03-27 Thread Bin Li
Installed the 2.0-1ubuntu4.7 version of firmware-sof-signed on the
previously failed ThinkPad platforms. Confirmed that now the LEDs can
toggle accordingly.

** Tags added: originate-from-2047202 sutton

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

Title:
  Enable the mic-mute led on Dell MTL laptops

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2049569/+subscriptions


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

[Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking

2024-03-27 Thread Bin Li
** Tags added: originate-from-2047204 sutton

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

Title:
  Mirror mode doesn't work when panel only supports one refresh rate
  with reduced blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions


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

[Bug 2058202] [NEW] Support Goodix MoC fingerprint[27C6:659A]

2024-03-17 Thread Bin Li
Public bug reported:

commit 489332c07da4092adf75e28d86e1c9dad744af7a 
Author: yangdi   
Date:   Tue Jul 19 11:37:09 2022 +0800
  
goodixmoc: add PID 0x659A

** Affects: libfprint (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/2058202

Title:
  Support Goodix MoC fingerprint[27C6:659A]

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


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

[Bug 2058013] Re: Support Elan fp device [04F3:0C8C]

2024-03-15 Thread Bin Li
lunar is EOL, mantic and noble have included this fix. We only need it
for jammy.

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

Title:
  Support Elan fp device [04F3:0C8C]

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


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

  1   2   3   4   5   6   7   8   9   10   >