from:"Kota"

adminuser@adminuser-Latitude-7350:~$ sudo cat 
/sys/bus/usb/devices/3-10/power/control
auto

adminuser@adminuser-Latitude-7350:~$ lsusb | grep Broadcom Bus 003
Device 004: ID 0a5c:5864 Broadcom Corp. 58200

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

Title:
  0a5c: 58xx USB device doesn't receive suspend interrupt from USBD
  Linux Driver/controller

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


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

[Bug 2066218] Re: 0a5c: 58xx USB device doesn't receive suspend interrupt from USBD Linux Driver/controller

Bus 003 Device 004: ID 0a5c:5864 Broadcom Corp. 58200
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize064
  idVendor   0x0a5c Broadcom Corp.
  idProduct  0x5864 
  bcdDevice1.01
  iManufacturer   1 Broadcom Corp
  iProduct2 58200
  iSerial 3 0123456789ABCD
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   0x008b
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower  100mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   254 Application Specific Interface
  bInterfaceSubClass  0 
  bInterfaceProtocol  0 
  iInterface  4 Broadcom ControlVault 3+
  ** UNRECOGNIZED:  10 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85  EP 5 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   1
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass11 Chip/SmartCard
  bInterfaceSubClass  0 
  bInterfaceProtocol  0 
  iInterface  5 Contacted SmartCard
  ChipCard Interface Descriptor:
bLength54
bDescriptorType33
bcdCCID  1.00
nMaxSlotIndex   0
bVoltageSupport 7  5.0V 3.0V 1.8V 
dwProtocols 3  T=0 T=1
dwDefaultClock   4000
dwMaxiumumClock  4000
bNumClockSupported  0
dwDataRate   9600 bps
dwMaxDataRate  25 bps
bNumDataRatesSupp.  0
dwMaxIFSD 247
dwSyncProtocols   
dwMechanical  
dwFeatures   000102BA
  Auto configuration based on ATR
  Auto voltage selection
  Auto clock change
  Auto baud rate change
  Auto PPS made by CCID
  NAD value other than 0x00 accepted
  TPDU level exchange
dwMaxCCIDMsgLen   271
bClassGetResponse  00
bClassEnvelope 00
wlcdLayout   none
bPINSupport 0 
bMaxCCIDBusySlots   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86  EP 6 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   1
Device Qualifier (for other device speed):
  bLength

[Bug 2066218] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2066218/+attachment/5780554/+files/ProcCpuinfoMinimal.txt

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

Title:
  0a5c: 58xx USB device doesn't receive suspend interrupt from USBD
  Linux Driver/controller

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


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

[Bug 2066218] Re: 0a5c: 58xx USB device doesn't receive suspend interrupt from USBD Linux Driver/controller

Kindly move the defect to Intel USB controller Linux driver package to
address it, i couldn't assign it to right package.

** Tags added: apport-collected jammy

** Description changed:

  0a5c: 58xx USB device doesn't receive suspend interrupt from Intel USBD Linux 
Driver/controller by default when no user space fingerprint drivers are 
installed for this device.
  Where as similar situation at windows, Windows USB controller sends suspend 
interrupt to device.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.5
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistributionChannelDescriptor:
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-oddish+X118
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2024-03-20 (61 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
+ Package: gnome-control-center (not installed)
+ ProcEnviron:
+  LANGUAGE=en_IN:en
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_IN
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 6.5.0-1023.24-oem 6.5.13
+ Tags:  jammy
+ Uname: Linux 6.5.0-1023-oem x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True

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

Title:
  0a5c: 58xx USB device doesn't receive suspend interrupt from USBD
  Linux Driver/controller

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


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

[Bug 2066218] [NEW] 0a5c: 58xx USB device doesn't receive suspend interrupt from USBD Linux Driver/controller

2024-05-20 Thread prafulla chandra kota

Public bug reported:

0a5c: 58xx USB device doesn't receive suspend interrupt from Intel USBD Linux 
Driver/controller by default when no user space fingerprint drivers are 
installed for this device.
Where as similar situation at windows, Windows USB controller sends suspend 
interrupt to device.

** Affects: gnome-control-center (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/2066218

Title:
  0a5c: 58xx USB device doesn't receive suspend interrupt from USBD
  Linux Driver/controller

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


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

[Bug 2058442] ProcCpuinfoMinimal.txt

2024-03-20 Thread prafulla chandra kota

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2058442/+attachment/5757411/+files/ProcCpuinfoMinimal.txt

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

Title:
  FP fingerprints are not deleted when user is removed

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


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

[Bug 2058442] Re: FP fingerprints are not deleted when user is removed

2024-03-20 Thread prafulla chandra kota

apport information

** Tags added: apport-collected jammy

** Description changed:

  FP: Fingerprint
  “FP templates were not deleted when user is removed”
  •From admin user account, create a new user account (user1) and login to it 
using password. Enroll 2 FP in it.
  •Lock the user account and login using enrolled FP. Observe that login is 
successful.
  •Now login to admin user and delete the newly created account (user1). Select 
"Delete files" option while removing the account.
  •Create a new user again (user 1). Observe that FP authentication with 
previously enrolled FPs still work at login screen.
  Attached the snapshot of user delete option chosen from GUI.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.5
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistributionChannelDescriptor:
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X46
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2023-11-13 (127 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
+ Package: gnome-control-center 1:41.7-0ubuntu0.22.04.7
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANGUAGE=en_IN:en
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_IN
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
+ Tags:  jammy
+ Uname: Linux 6.1.0-1025-oem x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True

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

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

Title:
  FP fingerprints are not deleted when user is removed

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


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

[Bug 2058442] [NEW] FP fingerprints are not deleted when user is removed

2024-03-19 Thread prafulla chandra kota

Public bug reported:

FP: Fingerprint
“FP templates were not deleted when user is removed”
•From admin user account, create a new user account (user1) and login to it
using password. Enroll 2 FP in it.
•Lock the user account and login using enrolled FP. Observe that login is
successful.
•Now login to admin user and delete the newly created account (user1). Select
"Delete files" option while removing the account.
•Create a new user again (user 1). Observe that FP authentication with
previously enrolled FPs still work at login screen.
Attached the snapshot of user delete option chosen from GUI.

** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New

** Attachment added: "snapshot of user delete"

https://bugs.launchpad.net/bugs/2058442/+attachment/5757401/+files/linux_user_delete.jpg

** Description changed:

+ FP: Fingerprint
“FP templates were not deleted when user is removed”
•From admin user account, create a new user account (user1) and login to it
using password. Enroll 2 FP in it.
•Lock the user account and login using enrolled FP. Observe that login is
successful.
•Now login to admin user and delete the newly created account (user1). Select
"Delete files" option while removing the account.
- •Create a new user again (user 1). Observe that FP auth with previously
enrolled FPs still work at login screen.
+ •Create a new user again (user 1). Observe that FP authentication with
previously enrolled FPs still work at login screen.
Attached the snapshot of user delete option chosen from GUI.

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

Title:
FP fingerprints are not deleted when user is removed

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

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

[Bug 1923418] Re: Fingerprint identification not working when system is idle without screen going blank

2022-01-13 Thread prafulla chandra kota

Another observation: on Login screen 20.04 version: when esc button is
pressed, it is not showing swipe your finger option for few esc key
press and it is enabled only after some time.

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

Title:
  Fingerprint identification not working when system is idle without
  screen going blank

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


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

[Bug 1923419] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1923419/+attachment/5486824/+files/ProcEnviron.txt

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

Title:
  FP identification is not working immediately after entering wrong
  password

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

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

[Bug 1923419] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1923419/+attachment/5486823/+files/ProcCpuinfoMinimal.txt

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

Title:
  FP identification is not working immediately after entering wrong
  password

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

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

[Bug 1923419] Dependencies.txt

apport information

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

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

Title:
  FP identification is not working immediately after entering wrong
  password

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

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

[Bug 1923419] [NEW] FP identification is not working immediately after entering wrong password

Public bug reported:

Issue: FP identification is not working immediately after entering wrong
password

System prerequisite:  FP enrolled on system, Identify works fine.
OS: Verified on: 20.04 PPA release.
•   Lock the screen
•   Enter wrong regular password and press enter.
•   Observe that "please try again" error is shown. 
•   Now try to login using enrolled FP. Observe that FP gets detected (FW 
uart log shows that FP is detected) but there will be no change in the login 
screen.
•   Need to enter password to login into user account or Hit enter again, 
login screen will show the Swipe your finger option and FP identify works.
Attached the fprintd debug log.
Events actions are mentioned with this symbol <==> at attached output.
Post wrong password attempt, FW is immediately ready to capture the finger, but 
host is saying device is already claimed and acquiring after hitting enter key 
again.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-09-24 (200 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Package: fprintd 1.90.9-1~ubuntu20.04.1 [origin: 
LP-PPA-ci-train-ppa-service-4509.1]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Tags: third-party-packages focal
Uname: Linux 5.8.0-44-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

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


** Tags: apport-collected focal third-party-packages

** Attachment added: "CS_5267_fprintd_log.txt"
   
https://bugs.launchpad.net/bugs/1923419/+attachment/5486821/+files/CS_5267_fprintd_log.txt

** Tags added: apport-collected focal third-party-packages

** Description changed:

  Issue: FP identification is not working immediately after entering wrong
  password
  
  System prerequisite:  FP enrolled on system, Identify works fine.
  OS: Verified on: 20.04 PPA release.
  • Lock the screen
  • Enter wrong regular password and press enter.
  • Observe that "please try again" error is shown. 
  • Now try to login using enrolled FP. Observe that FP gets detected (FW 
uart log shows that FP is detected) but there will be no change in the login 
screen.
  • Need to enter password to login into user account or Hit enter again, 
login screen will show the Swipe your finger option and FP identify works.
  Attached the fprintd debug log.
  Events actions are mentioned with this symbol <==> at attached output.
  Post wrong password attempt, FW is immediately ready to capture the finger, 
but host is saying device is already claimed and acquiring after hitting enter 
key again.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.16
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-09-24 (200 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ Package: fprintd 1.90.9-1~ubuntu20.04.1 [origin: 
LP-PPA-ci-train-ppa-service-4509.1]
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
+ Tags: third-party-packages focal
+ Uname: Linux 5.8.0-44-generic x86_64
+ UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  FP identification is not working immediately after entering wrong
  password

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

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

[Bug 1923418] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1923418/+attachment/5486820/+files/ProcEnviron.txt

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

Title:
  Fingerprint identification not working when system is idle without
  screen going blank

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

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

[Bug 1923418] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1923418/+attachment/5486819/+files/ProcCpuinfoMinimal.txt

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

Title:
  Fingerprint identification not working when system is idle without
  screen going blank

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

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

[Bug 1923418] Dependencies.txt

apport information

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

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

Title:
  Fingerprint identification not working when system is idle without
  screen going blank

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

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

[Bug 1923418] [NEW] Fingerprint identification not working when system is idle without screen going blank

Public bug reported:

Issue: Fingerprint identification not working when system is idle without 
screen going blank
Setup
System prerequisite:  FP enrolled on system, Identify works fine.
OS: Verified on: 20.04 PPA release.
Steps to reproduce: 
•   Now lock the user again. Select the User.
•   Leave the laptop idle for 30sec, swipe mouse across and don’t allow the 
system to go for sleep for 30 seconds. Place the enrolled FP on reader post 30 
seconds.
•   Observe that FP doesn't get detected at login screen.
•   Need to enter password to login into user account.
• Note: "Swipe finger" option at login screen is still shown even if FP 
doesn't get detected
Attached the fprintd debug log.

Events actions are mentioned with this symbol <==> at attached output.

<==> Some timeout is observed and after this Host is releasing the device and 
Identification is working only after hitting Enter key to start identification 
process, timeout is not generated from FW and FW is ready to accept the finger 
swipe.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-09-24 (200 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Package: fprintd 1.90.9-1~ubuntu20.04.1 [origin: 
LP-PPA-ci-train-ppa-service-4509.1]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Tags: third-party-packages focal
Uname: Linux 5.8.0-44-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

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


** Tags: apport-collected focal third-party-packages

** Attachment added: "CS_5266.txt"
   
https://bugs.launchpad.net/bugs/1923418/+attachment/5486817/+files/CS_5266.txt

** Tags added: apport-collected focal third-party-packages

** Description changed:

  Issue: Fingerprint identification not working when system is idle without 
screen going blank
  Setup
  System prerequisite:  FP enrolled on system, Identify works fine.
  OS: Verified on: 20.04 PPA release.
  Steps to reproduce: 
  • Now lock the user again. Select the User.
  • Leave the laptop idle for 30sec, swipe mouse across and don’t allow the 
system to go for sleep for 30 seconds. Place the enrolled FP on reader post 30 
seconds.
  • Observe that FP doesn't get detected at login screen.
  • Need to enter password to login into user account.
  • Note: "Swipe finger" option at login screen is still shown even if 
FP doesn't get detected
  Attached the fprintd debug log.
  
  Events actions are mentioned with this symbol <==> at attached output.
  
- <==> Some timeout is observed and after this Host is releasing the
- device and Identification is working only after hitting Enter key to
- start identification process, timeout is not generated from FW and FW is
- ready to accept the finger swipe.
+ <==> Some timeout is observed and after this Host is releasing the device and 
Identification is working only after hitting Enter key to start identification 
process, timeout is not generated from FW and FW is ready to accept the finger 
swipe.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.16
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-09-24 (200 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ Package: fprintd 1.90.9-1~ubuntu20.04.1 [origin: 
LP-PPA-ci-train-ppa-service-4509.1]
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
+ Tags: third-party-packages focal
+ Uname: Linux 5.8.0-44-generic x86_64
+ UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  Fingerprint identification not working when system is idle without
  screen going blank

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

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

[Bug 1893059] Re: Need information: Finger print sensor disabled after some incorrect failure attempts either consecutively or not in sequence with a count of some number

2021-01-25 Thread prafulla chandra kota

This issue is fixed in libfprint v1.90.2

** Changed in: fprintd (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/1893059

Title:
  Need information: Finger print sensor disabled after some incorrect
  failure attempts either consecutively or not in sequence with a count
  of some number

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

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

[Bug 1882878] Re: The user panel let you enroll the same finger several times

2021-01-20 Thread prafulla chandra kota

FP_DEVICE_ERROR_DATA_DUPLICATE error is added in libfprint 1.90.3
version, but when driver is returned this error, UI is not showing as
duplicate finger error and showing Fingerprint enroll is failed, UI
should show proper error here.

And also, post this failure, next finger enrollment is failed until
system restart.

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

Title:
  The user panel let you enroll the same finger several times

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1882878/+subscriptions

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

[Bug 1882880] Re: FP Auth enroll screen issue: Max limit not defined

2020-11-09 Thread prafulla chandra kota

** Changed in: gnome-control-center (Ubuntu)
   Status: Expired => New

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

Title:
  FP Auth enroll screen issue: Max limit not defined

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

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

[Bug 1902018] Re: Fingerprint: "scan your finger" option is not displayed at login screen on ubuntu 20.10 version

2020-11-01 Thread prafulla chandra kota

ScanYourFinger message is not visible, FP is enrolled, Fingerprint
identification also working fine.

** Attachment removed: "IMG_0054.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902018/+attachment/5429346/+files/IMG_0054.jpg

** Attachment added: "ScanYourFinger message is not visible, FP is enrolled"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902018/+attachment/5430192/+files/IMG_0123.jpg

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

Title:
  Fingerprint: "scan your finger" option is not displayed at login
  screen on ubuntu 20.10 version

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

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

[Bug 1902018] Re: Fingerprint: "scan your finger" option is not displayed at login screen on ubuntu 20.10 version

2020-10-30 Thread prafulla chandra kota

Attached login screen doesn't show 'scan your finger' message

** Attachment added: "IMG_0054.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902018/+attachment/5429346/+files/IMG_0054.jpg

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

Title:
  Fingerprint: "scan your finger" option is not displayed at login
  screen on ubuntu 20.10 version

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

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

[Bug 1902018] Re: Fingerprint: "scan your finger" option is not displayed at login screen on ubuntu 20.10 version

2020-10-30 Thread prafulla chandra kota

attached log output of 'journalctl -b 0' , login screen doesn't show the
message of 'scan your finger' but fingerprint identify operation works
fine.

** Attachment added: "3.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902018/+attachment/5429345/+files/3.txt

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

Title:
  Fingerprint: "scan your finger" option is not displayed at login
  screen on ubuntu 20.10 version

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

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

[Bug 1902018] Dependencies.txt

apport information

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

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

Title:
  Fingerprint: "scan your finger" option is not displayed at login
  screen on ubuntu 20.10 version

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

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

[Bug 1902018] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1902018/+attachment/5428918/+files/ProcCpuinfoMinimal.txt

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

Title:
  Fingerprint: "scan your finger" option is not displayed at login
  screen on ubuntu 20.10 version

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

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

[Bug 1902018] [NEW] Fingerprint: "scan your finger" option is not displayed at login screen on ubuntu 20.10 version

Public bug reported:

OS: Ubuntu 20.10 version
Test sequence:
Fingeprint is enrolled
Win+L: At login screen, earlier in 20.04 version, it used to display "scan your 
finger", it is not displayed in 20.10 version, but fingerprint identify is 
working fine.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.10
InstallationDate: Installed on 2020-09-29 (29 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Package: gnome-control-center 1:3.38.1-1ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Tags:  groovy
Uname: Linux 5.8.0-25-generic x86_64
UpgradeStatus: Upgraded to groovy on 2020-10-27 (1 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-collected groovy

** Tags added: apport-collected groovy

** Description changed:

  OS: Ubuntu 20.10 version
  Test sequence:
  Fingeprint is enrolled
  Win+L: At login screen, earlier in 20.04 version, it used to display "scan 
your finger", it is not displayed in 20.10 version, but fingerprint identify is 
working fine.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2020-09-29 (29 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ Package: gnome-control-center 1:3.38.1-1ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
+ Tags:  groovy
+ Uname: Linux 5.8.0-25-generic x86_64
+ UpgradeStatus: Upgraded to groovy on 2020-10-27 (1 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  Fingerprint: "scan your finger" option is not displayed at login
  screen on ubuntu 20.10 version

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

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

[Bug 1902018] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1902018/+attachment/5428919/+files/ProcEnviron.txt

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

Title:
  Fingerprint: "scan your finger" option is not displayed at login
  screen on ubuntu 20.10 version

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

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

[Bug 1899779] [NEW] Finger Print authentication doesn't work after logout in linux

Public bug reported:

Setup: Dell laptop with inbuilt fingerprint module
Below modules installed:
1) fprintd (1.90.1-1ubuntu1)
2) libpam-fprintd  (1.90.1-1ubuntu1)
3) libfprint-2-tod-dev (1:1.90.2+tod1-0ubuntu1~20.04.1)
4) Installed Broadcom TOD driver

Test procedure steps:

Logout from the user
Try to authenticate with enrolled FP
Observe that FP authentication allows login, but immediately asks for user 
password with error, attached screenshot of error
  "The login keyring did not get unlocked when you logged into your computer"

journlctl log didn't had any specific errors mentioned and log comes out is 
same for regular FP identify and post log-off and FP identify.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-09-24 (20 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72
Package: gnome-control-center 1:3.36.4-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Tags:  focal
Uname: Linux 5.4.0-48-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-collected focal

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1899779/+attachment/5422174/+files/FingerprintIdentifyIssuePostUserLogOff.jpg

** Tags added: apport-collected focal

** Description changed:

  Setup: Dell laptop with inbuilt fingerprint module
  Below modules installed:
  1) fprintd (1.90.1-1ubuntu1)
  2) libpam-fprintd  (1.90.1-1ubuntu1)
  3) libfprint-2-tod-dev (1:1.90.2+tod1-0ubuntu1~20.04.1)
  4) Installed Broadcom TOD driver
  
  Test procedure steps:
  
  Logout from the user
  Try to authenticate with enrolled FP
  Observe that FP authentication allows login, but immediately asks for user 
password with error, attached screenshot of error
"The login keyring did not get unlocked when you logged into your computer"
  
- journlctl log didn't had any specific errors mentioned and log comes out
- is same for regular FP identify and post log-off and FP identify.
+ journlctl log didn't had any specific errors mentioned and log comes out is 
same for regular FP identify and post log-off and FP identify.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.9
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-09-24 (20 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72
+ Package: gnome-control-center 1:3.36.4-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
+ Tags:  focal
+ Uname: Linux 5.4.0-48-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  Finger Print authentication doesn't work after logout in linux

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

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

[Bug 1899779] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1899779/+attachment/5422177/+files/ProcEnviron.txt

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

Title:
  Finger Print authentication doesn't work after logout in linux

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

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

[Bug 1899779] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1899779/+attachment/5422176/+files/ProcCpuinfoMinimal.txt

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

Title:
  Finger Print authentication doesn't work after logout in linux

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

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

[Bug 1899779] Dependencies.txt

apport information

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

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

Title:
  Finger Print authentication doesn't work after logout in linux

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

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

[Bug 1897693] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1897693/+attachment/5415172/+files/ProcEnviron.txt

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

Title:
  Fingerprint enroll progress is NOT displayed for immediate 2nd
  fingerprint enrollment

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

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

[Bug 1897693] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1897693/+attachment/5415171/+files/ProcCpuinfoMinimal.txt

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

Title:
  Fingerprint enroll progress is NOT displayed for immediate 2nd
  fingerprint enrollment

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

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

[Bug 1897693] Dependencies.txt

apport information

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

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

Title:
  Fingerprint enroll progress is NOT displayed for immediate 2nd
  fingerprint enrollment

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

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

[Bug 1897693] [NEW] Fingerprint enroll progress is NOT displayed for immediate 2nd fingerprint enrollment

Public bug reported:

Fingerprint enroll progress is NOT displayed for immediate 2nd fingerprint 
enrollment with out closing the FP GUI.
2nd finger enrollment: After first swipe of 2nd FP, even though progress is not 
displayed on circle for 2nd fingerprint, it is properly enrolled after 
continuous swipe and later it will be identified, but user will have confusion 
about appearance that is the 2nd finger enrollment is happening or not.

Steps to reproduce:
Enroll 1st FP ==> enrollment progress is shown on circle, after it completes, 
don't close GUI, proceed with 2nd finger enrollment
Enroll the second FP ==> observe that enrollment progress is NOT shown on 
circle, but if we keep on placing finger, after few attempts, finger will be 
enrolled.

verified on two DELL models
model-1: latitude 7300: 2nd fp enrollment progress is shown for 1 or 2 swipes, 
but didn't completed the progress circle.
model-2: latitude 7520: 2nd fp enrollment progress is NOT shown at all

Both cases 2nd FP enrollment is done and later it is also identified,
only progress is NOT displayed.

journlctl --unit fprintd.service was shown the messages of fingerprint
enroll swipes properly with out any issues

"Capture initiated, please place your finger now n the sensor now" for all 
swipes.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-09-24 (5 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Package: gnome-control-center 1:3.36.4-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Tags:  focal
Uname: Linux 5.4.0-48-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-collected focal

** Tags added: apport-collected focal

** Description changed:

  Fingerprint enroll progress is NOT displayed for immediate 2nd fingerprint 
enrollment with out closing the FP GUI.
  2nd finger enrollment: After first swipe of 2nd FP, even though progress is 
not displayed on circle for 2nd fingerprint, it is properly enrolled after 
continuous swipe and later it will be identified, but user will have confusion 
about appearance that is the 2nd finger enrollment is happening or not.
  
  Steps to reproduce:
  Enroll 1st FP ==> enrollment progress is shown on circle, after it completes, 
don't close GUI, proceed with 2nd finger enrollment
  Enroll the second FP ==> observe that enrollment progress is NOT shown on 
circle, but if we keep on placing finger, after few attempts, finger will be 
enrolled.
  
  verified on two DELL models
  model-1: latitude 7300: 2nd fp enrollment progress is shown for 1 or 2 
swipes, but didn't completed the progress circle.
  model-2: latitude 7520: 2nd fp enrollment progress is NOT shown at all
  
  Both cases 2nd FP enrollment is done and later it is also identified,
  only progress is NOT displayed.
  
  journlctl --unit fprintd.service was shown the messages of fingerprint
  enroll swipes properly with out any issues
  
- "Capture initiated, please place your finger now n the sensor now" for
- all swipes.
+ "Capture initiated, please place your finger now n the sensor now" for all 
swipes.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.4
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-09-24 (5 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ Package: gnome-control-center 1:3.36.4-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
+ Tags:  focal
+ Uname: Linux 5.4.0-48-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  Fingerprint enroll progress is NOT displayed for immediate 2nd
  fingerprint enrollment

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

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

[Bug 1893746] Re: fingerprint cancel operation is taking 50 seconds to cancel GUI window

2020-09-01 Thread prafulla chandra kota

Time took between last 2 lines and verified from fingerprint device
that, there is no delay occurred from device side.

17:20:14.429: Start the enrollment
17:20:14.441: Update the enrollment
Capture Initiated, Please place your finger now on the sensor now
17:20:17.432: Idle cancelling on ongoing operation!
17:20:17.432: device_cancel - start -
17:20:17.432: device_cancel - end -
17:20:17.432: Idle cancelling completed operation!
17:20:42.433: file_storage_discover_prints() for user 'adminuser' in 
'/var/lib/fprint/adminuser/broadcom/0'

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

Title:
  fingerprint cancel operation is taking 50 seconds to cancel GUI window

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

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

[Bug 1893059] Re: Need information: Finger print sensor disabled after some incorrect failure attempts either consecutively or not in sequence with a count of some number

2020-09-01 Thread prafulla chandra kota

** Package changed: gnome-control-center (Ubuntu) => fprintd (Ubuntu)

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

Title:
  Need information: Finger print sensor disabled after some incorrect
  failure attempts either consecutively or not in sequence with a count
  of some number

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

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

[Bug 1893746] [NEW] fingerprint cancel operation is taking 50 seconds to cancel GUI window

2020-09-01 Thread prafulla chandra kota

Public bug reported:

Test procedure to reproduce the issue:
1) click on fingerprint login for respective user
2) click next button
3) immediately click on cancel or back button
4) Observe a delay of 50 second is observed to comeback

Expectation: should not take long enough to cancel operation

fprind.service log
Sep 01 13:21:04 adminuser-Latitude-5411 fprintd[2648]: 
file_storage_discover_prints() for user 'adminuser' in 
'/var/lib/fprint/adminuser/broadcom/0'
Sep 01 13:21:11 adminuser-Latitude-5411 fprintd[2648]: 
file_storage_discover_prints() for user 'adminuser' in 
'/var/lib/fprint/adminuser/broadcom/0'
Sep 01 13:21:11 adminuser-Latitude-5411 fprintd[2648]: user 'adminuser' 
claiming the device: 0
Sep 01 13:21:11 adminuser-Latitude-5411 fprintd[2648]: Device reported open 
completion
Sep 01 13:21:11 adminuser-Latitude-5411 fprintd[2648]: Completing action 2 in 
idle!
Sep 01 13:21:11 adminuser-Latitude-5411 fprintd[2648]: claimed device 0
Sep 01 13:21:29 adminuser-Latitude-5411 fprintd[2648]: start enrollment device 
0 finger 6
Sep 01 13:21:29 adminuser-Latitude-5411 fprintd[2648]: Start the enrollment
Sep 01 13:21:29 adminuser-Latitude-5411 fprintd[2648]: Update the enrollment
Sep 01 13:21:53 adminuser-Latitude-5411 fprintd[2648]: Idle cancelling on 
ongoing operation!
Sep 01 13:22:18 adminuser-Latitude-5411 fprintd[2648]: 
file_storage_discover_prints() for user 'adminuser' in 
'/var/lib/fprint/adminuser/broadcom/0'
Sep 01 13:22:30 adminuser-Latitude-5411 fprintd[2648]: Device reported enroll 
completion
Sep 01 13:22:30 adminuser-Latitude-5411 fprintd[2648]: Completing action 4 in 
idle!
Sep 01 13:22:30 adminuser-Latitude-5411 fprintd[2648]: enroll_cb: result 
enroll-failed
Sep 01 13:37:13 adminuser-Latitude-5411 fprintd[2648]: 
file_storage_discover_prints() for user 'adminuser' in 
'/var/lib/fprint/adminuser/broadcom/0'

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: fprintd (not installed)
ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep  1 13:37:38 2020
InstallationDate: Installed on 2020-08-14 (17 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: fprintd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  fingerprint cancel operation is taking 50 seconds to cancel GUI window

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

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

[Bug 1893059] Re: Need information: Finger print sensor disabled after some incorrect failure attempts either consecutively or not in sequence with a count of some number

name of the package affected or relevant to this issue is: fprintd &
libfprint.

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

Title:
  Need information: Finger print sensor disabled after some incorrect
  failure attempts either consecutively or not in sequence with a count
  of some number

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

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

[Bug 1893059] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1893059/+attachment/5406030/+files/ProcCpuinfoMinimal.txt

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

Title:
  Need information: Finger print sensor disabled after some incorrect
  failure attempts either consecutively or not in sequence with a count
  of some number

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

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

[Bug 1893059] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1893059/+attachment/5406031/+files/ProcEnviron.txt

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

Title:
  Need information: Finger print sensor disabled after some incorrect
  failure attempts either consecutively or not in sequence with a count
  of some number

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

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

[Bug 1893059] Re: Need information: Finger print sensor disabled after some incorrect failure attempts either consecutively or not in sequence with a count of some number

apport information

** Tags added: apport-collected focal

** Description changed:

  Observation:
  
  It is observed that finger print sensor is disabled after few failure
  attempts not in sequence with a count of some number of attempts.
  
  Is there any such count requirement of disabling Fingerprint sensor for
  few seconds after some incorrect failure attempts not in sequence with a
  count of "X" ?, it is observed failure with below sequence:
  
  WF - wrong finger, CF - correct finger
  
  WF, WF, CF, WF, WF, CF, WF, WF, CF, WF, WF, CF, WF, WF, CF, WF, WF, CF,
  WF, WF, CF, WF, WF
  
  I have looked at fprintd service logs from host and didn't observed any
  different commands received from host when the fingerprint is disabled
  for few seconds.
  
  Need some clarity on behavior of this feature and if there is any
  document or link explains the requirements of Fingerprint application
  behavior will be helpful in understanding the host behavior.
  
  Kindly let me know if i can provide any extra information.
  
  Thanks,
  Prafulla Kota
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.8
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-08-14 (16 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia
+ Package: gnome-control-center 1:3.36.4-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
+ Tags:  focal
+ Uname: Linux 5.4.0-42-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Need information: Finger print sensor disabled after some incorrect
  failure attempts either consecutively or not in sequence with a count
  of some number

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

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

[Bug 1893059] [NEW] Need information: Finger print sensor disabled after some incorrect failure attempts either consecutively or not in sequence with a count of some number

2020-08-26 Thread prafulla chandra kota

Public bug reported:

Observation:

It is observed that finger print sensor is disabled after few failure
attempts not in sequence with a count of some number of attempts.

Is there any such count requirement of disabling Fingerprint sensor for
few seconds after some incorrect failure attempts not in sequence with a
count of "X" ?, it is observed failure with below sequence:

WF - wrong finger, CF - correct finger

WF, WF, CF, WF, WF, CF, WF, WF, CF, WF, WF, CF, WF, WF, CF, WF, WF, CF,
WF, WF, CF, WF, WF

I have looked at fprintd service logs from host and didn't observed any
different commands received from host when the fingerprint is disabled
for few seconds.

Need some clarity on behavior of this feature and if there is any
document or link explains the requirements of Fingerprint application
behavior will be helpful in understanding the host behavior.

Kindly let me know if i can provide any extra information.

Thanks,
Prafulla Kota

** Affects: gnome-control-center (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/1893059

Title:
  Need information: Finger print sensor disabled after some incorrect
  failure attempts either consecutively or not in sequence with a count
  of some number

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

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

[Bug 1738156] Re: mdadm may break bbl if bitmap is too large

2017-12-14 Thread Kota Uchida

** Summary changed:

- mdadm may broke bbl if bitmap is too large
+ mdadm may break bbl if bitmap is too large

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

Title:
  mdadm may break bbl if bitmap is too large

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

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

[Bug 1738156] [NEW] mdadm may broke bbl if bitmap is too large

2017-12-14 Thread Kota Uchida

Public bug reported:

mdadm 3.3-2ubuntu7.6 (for xenial) has a bug which may break an internal 
write-intent bitmap.
Due to this bug, a bitmap overlaps with a bbl (bad block log), then the bbl 
gets to be inconsistent.

The cause of the bug is that a bbl is placed at a fixed location (80 sectors 
from the beginning of a disk).
Because an internal write-intent bitmap is placed before the bbl (16 sectors 
from the beginning of a disk),
it overlaps with the bbl when it grows too large (> 64 sectors).

See this figure. https://cdn-ak.f.st-
hatena.com/images/fotolife/u/uchan_nos/20171126/20171126111715.png

This bug has been fixed in upstream of mdadm. The fixing commit is
https://github.com/neilbrown/mdadm/commit/1b7eb672f7792313cc1517feaae8267575fc496b

I tested the bug on the following versions:

- mdadm 3.3-2ubuntu7.6 (for xenial) : The bug is reproduced
- mdadm 3.4-4ubuntu0.1 (for zesty) : The bug is reproduced
- mdadm 4.0-2 (for artful) : The bug has been fixed

I want you to backport the patch to Ubuntu 16.04 LTS because the bug is
serious.


Detailed description (containing scripts to reproduce the bug) is here:
https://gist.github.com/uchan-nos/4a4894f3c8e4a59ed0b870b5a516dcad#file-mdadm_bug_bbl_disruption-md

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mdadm 3.3-2ubuntu7.2
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
Date: Thu Dec 14 18:09:57 2017
InstallationDate: Installed on 2017-02-03 (313 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
Lspci:
 
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed 
with exit code 1: mdadm: cannot open /dev/sda: Permission denied
MDadmExamine.dev.sda1: Error: command ['/sbin/mdadm', '-E', '/dev/sda1'] failed 
with exit code 1: mdadm: cannot open /dev/sda1: Permission denied
MDadmExamine.dev.sda2: Error: command ['/sbin/mdadm', '-E', '/dev/sda2'] failed 
with exit code 1: mdadm: cannot open /dev/sda2: Permission denied
MDadmExamine.dev.sda3: Error: command ['/sbin/mdadm', '-E', '/dev/sda3'] failed 
with exit code 1: mdadm: cannot open /dev/sda3: Permission denied
MDadmExamine.dev.sdb: Error: command ['/sbin/mdadm', '-E', '/dev/sdb'] failed 
with exit code 1: mdadm: cannot open /dev/sdb: Permission denied
MDadmExamine.dev.sdb1: Error: command ['/sbin/mdadm', '-E', '/dev/sdb1'] failed 
with exit code 1: mdadm: cannot open /dev/sdb1: Permission denied
MachineType: Microsoft Corporation Virtual Machine
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-96-generic 
root=/dev/mapper/hostname--vg-root ro rootflags=subvol=@
SourcePackage: mdadm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/26/2016
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: Hyper-V UEFI Release v2.0
dmi.board.asset.tag: None
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: Hyper-V UEFI Release v2.0
dmi.chassis.asset.tag: 6099-8796-9610-2381-8579-4771-22
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: Hyper-V UEFI Release v2.0
dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev2.0:bd08/26/2016:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev2.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev2.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev2.0:
dmi.product.name: Virtual Machine
dmi.product.version: Hyper-V UEFI Release v2.0
dmi.sys.vendor: Microsoft Corporation
etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'

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


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  mdadm may broke bbl if bitmap is too large

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

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

[Bug 1706630] Re: aarch64: MSI is not supported by interrupt controller

2017-09-26 Thread Raghuram Kota

@admcleod : Any updates on Pike testing with qemu2.10 mentioned in comm
#9 ?

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

Title:
  aarch64: MSI is not supported by interrupt controller

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

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

[Bug 1709920] Re: criu is not built for arm64

2017-09-13 Thread Raghuram Kota

@stgraber ; From comment #3, who's the right person/team to lead Xenial
SRU, now that criu seems to have landed in Artful ? Thanks.

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

Title:
  criu is not built for arm64

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

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

[Bug 1673564] Re: ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with vhost=on

2017-09-11 Thread Raghuram Kota

Backporting to the Xenial (Ubntu 16.04) kernel isn't feasible. 16.04
users are requested to use the hwe-z kernel as noted in the following
Wiki page :
https://wiki.ubuntu.com/HardwareSupport/Machines/Servers/Cavium/ThunderXCRB1S

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

Title:
  ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with
  vhost=on

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

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

[Bug 1706735] Re: lmbench tcp lib backlog reservation too small, can cause hang.

2017-09-05 Thread Raghuram Kota

** Tags added: cn99xx

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

Title:
  lmbench tcp lib backlog reservation too small, can cause hang.

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

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

[Bug 1709920] Re: criu is not built for arm64

2017-08-10 Thread Raghuram Kota

** Tags added: arm64

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

Title:
  criu is not built for arm64

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

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

[Bug 1702979] Re: Deeply layered Docker image problems

2017-08-10 Thread Raghuram Kota

Hi @Edward Vielmetti : Trying to follow up to see if you had a chance to
test.  Many thanks for the help!

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

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

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

[Bug 1702979] Re: Deeply layered Docker image problems

2017-07-31 Thread Raghuram Kota

Hi @Edward Vielmetti : Would it be possible for you to test the fix
uploaded to PPA by mwhudson (comm # 4 ?) ? Thx!

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

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

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

[Bug 1697610] Re: aarch64: logfile not supported in this QEMU binary

2017-07-27 Thread Raghuram Kota

@James : Thanks for the new patch (comm #24)! Does this allow kernel
boot messages to be also captured and address the limitation mentioned
in comm #21 ? Thx

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

Title:
  aarch64: logfile not supported in this QEMU binary

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

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

[Bug 1702979] Re: Deeply layered Docker image problems

2017-07-19 Thread Raghuram Kota

A build with option #1 suggested in comment #2 is now available in a PPA
(Many thanks to mwhudson!) and is ready for test. To install :

$ sudo add-apt-repository ppa:mwhudson/devirt
$ sudo apt-get update

Then apt-get upgrade or apt-get install docker.io containerd runc should
get the rebuilt versions.

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

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

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

[Bug 1694221] Re: fix rxbuf size for netdev-dpdk

2017-06-13 Thread Raghuram Kota

it appears that this patch is now ACKed upstream
:https://patchwork.ozlabs.org/patch/774670/

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

Title:
  fix rxbuf size for netdev-dpdk

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

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

[Bug 1694506] Re: arm-smmu arm-smmu.2.auto: Unhandled context fault

2017-05-30 Thread Raghuram Kota

** Tags added: acpi arm

** Tags removed: arm
** Tags added: arm64 hs-arm64

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

Title:
  arm-smmu arm-smmu.2.auto: Unhandled context fault

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

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

[Bug 1673467] Re: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor

2017-04-03 Thread Raghuram Kota

The plan is to implement an arch specific charm change  to pass in the
"host-passthrough" as  CPU mode until a newer libvirt with functional
"host-model" parameter is available in a future Ubuntu release.

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

Title:
  [ocata] unsupported configuration: CPU mode 'host-model' for aarch64
  kvm domain on aarch64 host is not supported by hypervisor

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

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

[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM

2017-03-29 Thread Raghuram Kota

It looks like so far we have the following data points.  :

ARM64
-
1) Xenial-Mitaka : Fail (comm#3)

X86-64
-
a) Trusty - Mitaka : Fail (Comm #4)
b) Xenial-Mitaka : OK (Comm #7) 

In addition, Linaro had confirmed that
https://bugs.linaro.org/show_bug.cgi?id=2462 (that trigerred the testing
that sourced this bug)  was occurring on both x86  and ARM64, but didn't
specify the OPenstack versions. Something I'll try to follow up.

@paelzer, @dmitriis :With the above data,  what in your view would be
good set of experiments to run ?

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

Title:
  [ARM]  : Unable to use Cinder volumes on ARM

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

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

[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM

2017-03-29 Thread Raghuram Kota

@Ryan Beisner (1chb1n)  : Oh, my apologies, I was only looking at the
libvirt version (as the fix seems to be there) and went by the
following statement in comm#13  : " But UCA-Newton has only Xenials
libvirt that is on libvirt 1.3.1 and should not be affected at all
either."

Are there components beyond libvirt involved in this fix ?

Thanks,
Raghu

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

Title:
  [ARM]  : Unable to use Cinder volumes on ARM

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

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

[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM

2017-03-29 Thread Raghuram Kota

@paelzer : Many thanks for looking into this. Xenial-Mitaka test on
comm#7 was actually done by Dimitrii (dmitriis).Thanks go out to him.
Based on comm#13, your  hypothesis seems to be that this should only
occur on Yakkety.

@dmitriis : Are you able to help with the tests  #2-#5 on ServerStack or
othewise, similar to testing you did in comm#7 to prove/disprove this
hypothesis ?

Many Thanks,
Raghu

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

Title:
  [ARM]  : Unable to use Cinder volumes on ARM

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

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

[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM

2017-03-27 Thread Raghuram Kota

This bug seems to have been addressed in upstream libvirt, per comm#18
of https://bugs.linaro.org/show_bug.cgi?id=2462

Per  Gem Gomez  (Linaro) :

The upstream review, commit of the patch can be found on the libvirt upstream 
mailing :
http://www.redhat.com/archives/libvir-list/2016-October/msg00395.html
 
Here is the message that confirms this patch made it to libvirt:
http://www.redhat.com/archives/libvir-list/2016-October/msg00876.html

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

Title:
  [ARM]  : Unable to use Cinder volumes on ARM

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

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

[Bug 1673467] Re: [ocata] unsupported configuration: CPU mode 'host-model' for aarch64 kvm domain on aarch64 host is not supported by hypervisor

2017-03-22 Thread Raghuram Kota

@Corey @Christian the xml in comm#12 from Jason is Xenial-Newton.

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

Title:
  [ocata] unsupported configuration: CPU mode 'host-model' for aarch64
  kvm domain on aarch64 host is not supported by hypervisor

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

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

[Bug 1630038] Re: thunder nic: avoid link delays due to RX_PACKET_DIS

2017-03-21 Thread Raghuram Kota

Hi,

Regarding comment#6, can you please help provide :

1) The model of the specific server in  use ? 
2) A console log that help determine the UEFI firmware version running on that 
model ? 

Thanks,
Raghu

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

Title:
  thunder nic: avoid link delays due to RX_PACKET_DIS

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

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

[Bug 1664764] Re: ARM Opentack API/Dashboard calls are very slow

2017-03-01 Thread Raghuram Kota

@Billy : Nevermind comment #11. mreed8855 mentioned that the benchmark
comes with a "compare" option that can be used to compare results. Thx.

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

Title:
  ARM Opentack  API/Dashboard  calls are very slow

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

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

[Bug 1664764] Re: ARM Opentack API/Dashboard calls are very slow

2017-03-01 Thread Raghuram Kota

@Billy Olsen : Michael R  helped run the benchmarks  you pointed to on
ARM64 and posted  the results on comm #9. Do you happen to know how they
can be interpreted/compared with other archs  ?

Thanks,
Raghu

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

Title:
  ARM Opentack  API/Dashboard  calls are very slow

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

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

[Bug 1664764] Re: ARM Opentack API/Dashboard calls are very slow

Billy Olsen (billy-olsen) wrote on 2017-02-13:

If we think this is a python performance issue, it might be beneficial
to get some data running the python performance suite - which is
available here https://github.com/python/performance. Also, its likely
we should target this at the Python Ubuntu package to see if there's
some compile time optimizations that can be done for the python
interpreter.

** Tags added: arm64 openstack uosci

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

Title:
  ARM Opentack  API/Dashboard  calls are very slow

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

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

[Bug 1664764] Re: ARM Opentack API/Dashboard calls are very slow

dann frazier (dannf) wrote on 2017-01-26: Re: [Bug 1652377] Re: API
calls are very slow :

On Wed, Jan 25, 2017 at 6:31 PM, Ryan Beisner
<1652...@bugs.launchpad.net> wrote:
> Without scientific data at this point, I can confirm that every CLI/API
> call I make on a freshly-deployed Xenial-Mitaka arm64 cloud is
> noticeably sluggish compared with x86 deploys, where the x86 machines
> are 6 years old, have 75% of the RAM, and less than half the advertised
> cores.
>
> This is worth profiling without OpenStack in the mix.

Do you know of a way to reproduce it without OpenStack in the mix?

  -dann

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

Title:
  ARM Opentack  API/Dashboard  calls are very slow

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

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

[Bug 1664764] Re: ARM Opentack API/Dashboard calls are very slow

Ryan Beisner (1chb1n) wrote on 2017-01-26:

For example, this should not take 19s on a cloud with no tenants, no
instances, 1 image, and light system resource allocation per-node:

`time glance image-list`
+--++
| ID | Name |
+--++
| 0d66c03c-fe4c-4d26-bfac-74ecb55735ab | xenial |
+--++

real 0m19.580s
user 0m0.888s
sys 0m0.068s

.

`time nova list`
jenkins@juju-osci1-machine-6:~/temp/openstack-charm-testing$ time nova list
++--+++-+--+
| ID | Name | Status | Task State | Power State | Networks |
++--+++-+--+
++--+++-+--+

real 0m11.833s
user 0m1.028s
sys 0m0.076s

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

Title:
  ARM Opentack  API/Dashboard  calls are very slow

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

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

[Bug 1664764] Re: ARM Opentack API/Dashboard calls are very slow

Ryan Beisner (1chb1n) wrote on 2017-01-26:

Without scientific data at this point, I can confirm that every CLI/API
call I make on a freshly-deployed Xenial-Mitaka arm64 cloud is
noticeably sluggish compared with x86 deploys, where the x86 machines
are 6 years old, have 75% of the RAM, and less than half the advertised
cores.

This is worth profiling without OpenStack in the mix.

I'd like to have HWCERT or Server Team or Kernel Team to provide system
performance profiling methodology info (presuming there is an existing
approach). Then I'd like to exercise that on these arm64 machines and
the x86 machines, then compare to get baseline info (again, absent
OpenStack).

@raghu: please see if you can gather info from other teams and direct
that info here. TIA!

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

Title:
  ARM Opentack  API/Dashboard  calls are very slow

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

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

[Bug 1664764] [NEW] ARM Opentack API/Dashboard calls are very slow

Public bug reported:

dann frazier (dannf) on 2016-12-23 :

I'm using openstack-base deployed on an arm64-only MAAS (xenial/newton).
Both the CLI and dashboard are very slow to respond. CLI commands (e.g.
nova list) take about 15s to complete. Logging into the dashboard takes
more than 30s. 'top' shows plenty of available CPU/memory on the
dashboard node.

Note: This isn't new - it is something we've observed with previous
versions of Ubuntu OpenStack as well, but haven't yet gotten to the
bottom of it.

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


** Tags: arm64 openstack uosci

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

Title:
  ARM Opentack  API/Dashboard  calls are very slow

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

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

[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM

>From  Ryan Beisner (1chb1n)  :

Xenial-Mitaka

I've confirmed that hot-plugging a cinder volume to a uefi arm64 nova
instance doesn't work out of the box.

After attaching the volume, it was necessary to reboot the instance in
order to detect and use the new volume.

$ openstack volume create --size 60 volume1

$ openstack server add volume xenial-uefi-20170119b221218 volume1

+--+--++--+--+
| ID | Display Name | Status | Size | Attached to |
+--+--++--+--+
| 2631f6fe-ff0b-4357-9b65-1b449fc0905b | volume1 | in-use | 60 | Attached to 
xenial-uefi-20170119b221218 on /dev/vdc |
| cc15681a-4957-4653-b18b-63188430477d | volume0 | in-use | 10 | Attached to 
xenial-uefi-20170119b221218 on /dev/vdb |
+--+--++--+--+

# Note the lack of the 60G storage
ubuntu@xenial-uefi-20170119b221218:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 253:0 0 10G 0 disk
vdb 253:16 0 20G 0 disk
├─vdb1 253:17 0 19.9G 0 part /
└─vdb15 253:31 0 99M 0 part /boot/efi

# After simply rebooting the nova instance, the 60G storage is attached
ubuntu@xenial-uefi-20170119b221218:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 253:0 0 10G 0 disk
vdb 253:16 0 20G 0 disk
├─vdb1 253:17 0 19.9G 0 part /
└─vdb15 253:31 0 99M 0 part /boot/efi
vdc 253:32 0 60G 0 disk

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

Title:
  [ARM]  : Unable to use Cinder volumes on ARM

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

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

[Bug 1664737] [NEW] [ARM] : Unable to use Cinder volumes on ARM

Public bug reported:

From: Dann Frazier (dannf)  :

I have an OpenStack setup built on an arm64-only MAAS using the
openstack-base w/ default settings. From the cli, I am able to create
and attach a volume to a running guest. However, that volume never
appears in the guest - nothing new in dmesg, nothing new in
/proc/partitions. There's no obvious errors, or even informational
messages, in the nova, libvirt or cinder logs (included in attached juju
crashdump).

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

** Attachment added: 
"juju-crashdump-a3000f7f-fb1f-4945-8910-0f38447c8e26.tar.xz"
   
https://bugs.launchpad.net/bugs/1664737/+attachment/4819040/+files/juju-crashdump-a3000f7f-fb1f-4945-8910-0f38447c8e26.tar.xz

** Bug watch added: Linaro Bug Tracking System #2462
   https://bugs.linaro.org/show_bug.cgi?id=2462

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

Title:
  [ARM]  : Unable to use Cinder volumes on ARM

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

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

[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM

Dmitrii Shcherbakov (dmitriis) wrote on 2017-02-02:

@beisner

Had issues with deployment - for some reason a couple of undercloud VMs
got stuck (juju was waiting for a machine allocation while it already
booted) after running juju-deployer. Had to manually remove affected
units and 'juju add-unit' them to get it working.

Nevertheless, here's the result with a fully-deployed xenial-mitaka
next.yaml bundle from the o-c-t (amd64, serverstack, some package
versions included in the paste):

https://pastebin.canonical.com/178064/

I checked it from the nova, libvirt, qemu and guest POV - it looks good
I wasn't able to reproduce the original issue.

virtio-blk devices are used by default so PCI-hotplug
(http://wiki.qemu.org/Features/PCIBridgeHotplug) was triggered inside
the guest kernel. I verified that libvirt has set up an RBD for the
added virtio-blk device and that it was visible by qemu (checked via
QMP) and the guest (dmesg + lsblk). Removal worked just fine as well.

Double addition of the same volume to the same VM without reboot worked
fine too.

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

Title:
  [ARM]  : Unable to use Cinder volumes on ARM

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

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

[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM

Ryan Beisner (1chb1n) wrote on 2017-02-02:

@dmitrii Can you please independently exercise the following?:

On ServerStack (x86_64):

 - Boot a new nova instance.
 - Create a cinder volume.
 - Attach the cinder volume to the running nova instance (with openstack cli).

We are looking to confirm whether or not the guest instance sees the
newly-attached block device without rebooting the instance.

Many thanks!

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

Title:
  [ARM]  : Unable to use Cinder volumes on ARM

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

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

[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM

Ryan Beisner (1chb1n) wrote on 2017-01-26:

This does not appear to specific to arm64. On an x86 internal dev cloud,
Trusty-Mitaka, I also have to reboot my nova instance after attaching
ceph-backed cinder volumes before they are usable.

Next steps: test again with vanilla cinder (not ceph-backed).

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

Title:
  [ARM]  : Unable to use Cinder volumes on ARM

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

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

[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM

From: Dann Frazier (dannf) :

Note that the reason I went about testing this was because I ran across this 
one:
  https://bugs.linaro.org/show_bug.cgi?id=2462
The symptoms don't seem to be the same - OpenStack in that case generated an 
error on attach. In this case, there was no error, but the instance did not see 
it.

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

Title:
  [ARM]  : Unable to use Cinder volumes on ARM

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

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

[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM