[Touch-packages] [Bug 1902432] Re: Sound card not detected yet seen in the terminal (fictitious output sound)

2020-11-01 Thread lotuspsychje
** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1902432

Title:
  Sound card not detected yet seen in the terminal (fictitious output
  sound)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Je suis sur un ASUS X555BP initialement Windows 8 puis maj pour windows 10. 
Suite à une modification de ma part sur la carte graphique (maj) il y a eut une 
incompatibilité donc j'ai du passé sur Ubuntu 20.04.1 LTS par clé usb. Je suis 
en 64 bits sous gnome 3.36.3. Aucun problème pour lire une vidéo etc si ce 
n'est que le son ne sort pas. Dans le terminal j'ai déjà désintallé et 
réinstallé Pulse Audio. Il est capable de me sortir le nom de ma carte 
graphique quand je l'interroge par sudo lspci A9-9420 radeon r5, 5 compute 
cores 2c+3g × 2 mais aucune carte n'est détecté quand je tape aplay -l.
  Normalement le système d'exploitation installe automatiquement des drivers 
compatibles avec ma carte graphique donc je ne sais pas quoi faire. D'après 
apt-cache j'use apt 2.0.2ubuntu0.1 (amd64).
  Oh et j'ai aussi un problème de detection de mise en charge de ma batterie 
d'ordinateur, je ne sais pas si c'est lié. Cependant cela n'arrivait pas avant. 
Un informaticien a déjà regardé mon oridinateur, je n'ai pas de problème de 
disque dur ou de carte mère.

  I am on an ASUS X555BP initially Windows 8 then update for Windows 10. 
Following a modification by myself on the graphics card (update) there was an 
incompatibility so I went on Ubuntu 20.04.1 LTS by usb key . I am in 64 bits 
under gnome 3.36.3. No problem to play a video etc except that the sound does 
not come out. In the terminal I have already uninstalled and reinstalled Pulse 
Audio, Alsa etc. It is able to give me the name of my graphics card when I 
query it through sudo lspci A9-9420 radeon r5, 5 compute cores 2c + 3g × 2 but 
no card is detected when I type aplay -l.
  Normally the operating system automatically installs drivers compatible with 
my graphics card so I don't know what to do. According to apt-cache I am using 
apt 2.0.2ubuntu0.1 (amd64) and I have also struggle with my computer's load 
detection. It accepts to be in charge once in ten which did not happen before. 
My computer was checked by a computer scientist, I have no hard drive or 
motherboard problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  1 13:52:11 2020
  InstallationDate: Installed on 2020-10-13 (18 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555BP.326
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555BP
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555BP.326:bd05/13/2019:svnASUSTeKCOMPUTERINC.:pnX555BP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555BP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555BP
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1899857] Re: [SRU] alsa-lib: support the enum value settings both in "" and in ''

2020-11-01 Thread Kai-Chuan Hsieh
Hello,

May I know what blocks the focal release SRU?

Thanks,

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1899857

Title:
  [SRU] alsa-lib: support the enum value settings both in "" and in ''

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Recently the ucm added some amixer settings, like this one:
  cset "name='rt711 ADC 23 Mux' 'MIC2'"
  This setting is needed for Dell soundwire audio machines, and only
  this setting is set correctly, the headset-mic could work. And we
  already backported this ucm to focal. But the alsa-lib ctl parse
  doesn't support the enum value in the '' yet, so this amixer setting
  can't be set correctly under current focal and groovy, we need to
  backport a patch from alsa-lib master branch.

  [Fix]
  Backport a patch from upstream, this patch is not in the groovy
  yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this
  patch.

  [Test Case]
  On the Dell soundwire audio machine, run alsactl init, then check if
  the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set
  correctly, it means the alsalib enum ctl parse support both "" and ''
  now.

  
  [Regression Risk]
  This could introduce failure on setting enum amixer settings, users
  will experience the failure of audio device like the speaker can't output
  sound, the mic can't record sound. But this possibility is very low since
  we have tested this SRU on many LENOVO and Dell machines (with and without
  soundwire audio), all worked as fine as before.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1893846] Re: Sound doesn't switch to headphones automatically when plugged in

2020-11-01 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1893846

Title:
  Sound doesn't switch to headphones automatically when plugged in

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  1) Ubuntu 20.04.1 LTS
  2) gnome-control-center 1:3.36.4-0ubuntu1
  3) What you expected to happen:I expected to connect my headphone and listen 
to any sound automatically.
  4) What happened instead: In order to make the headset work, I must go to the 
Control Center, then "Sound" and choose "Headphones-Built-in Audio" as my 
Output Device, since the default is "Analog Output-Built-in Audio" (getting no 
sound from my headset).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1859 F pulseaudio
   /dev/snd/controlC1:  douglas1859 F pulseaudio
   /dev/snd/controlC3:  douglas1859 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (129 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/20/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: Z68XP-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68XP-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-11-01 Thread smurf
ok, got it, thx a lot.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871794

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-11-01 Thread Hui Wang
https://github.com/rtlwifi-linux/rtlwifi-next/issues

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871794

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-11-01 Thread Hui Wang
I don't know, maybe it is a wireless mouse receiver?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871794

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time

2020-11-01 Thread jeremyszu
** Also affects: alsa-ucm-conf (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- The rear panel of Lenovo P620 doesn't support more than one audio device in 
at the same time
+ The rear panel of Lenovo P620 doesn't support more than one audio device at 
the same time

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1902464

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After backporting following patches from PA and alsa-ucm-conf and then
  it works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-11-01 Thread smurf
@Hui Wang,
I tried to access https://github.com/rtlwifi-linux, but I didn't find where to 
report my issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871794

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1902361] Re: Delete key inputs Unicode Delete character (007F) instead of deleting the next character

2020-11-01 Thread Daniel van Vugt
That xev output looks correct, I get the same output from 'xev' but
don't get this bug.

Does the problem occur in GNOME Terminal or some other terminal app?
Also do you have any accessibility settings enabled (look in Settings >
Universal Access)?

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Changed in: mutter (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1902361

Title:
  Delete key inputs Unicode Delete character (007F) instead of deleting
  the next character

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When pressed, the delete key inputs the Unicode 007F character instead
  of deleting the following character. In most cases, this is difficult
  to see, but in a terminal, the 007F is clearly visible.

  The xev output for the key press is following:

  KeyPress event, serial 36, synthetic NO, window 0x421,
  root 0x5df, subw 0x0, time 81101326, (1403,948), root:(1453,1062),
  state 0x0, keycode 119 (keysym 0x, Delete), same_screen YES,
  XLookupString gives 1 bytes: (7f) ""
  XmbLookupString gives 1 bytes: (7f) ""
  XFilterEvent returns: False

  KeyRelease event, serial 36, synthetic NO, window 0x421,
  root 0x5df, subw 0x0, time 81101443, (1403,948), root:(1453,1062),
  state 0x0, keycode 119 (keysym 0x, Delete), same_screen YES,
  XLookupString gives 1 bytes: (7f) ""
  XFilterEvent returns: False

  
  This is a new fresh install of Ubuntu 20.04, I don't remember the delete key 
working at any point since the installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 31 12:54:40 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 (Whiskey Lake) 
[1025:1312]
  InstallationDate: Installed on 2020-10-14 (16 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Acer Swift SF514-53T
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.name: Carlsberg_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd04/25/2019:svnAcer:pnSwiftSF514-53T:pvrV1.09:rvnWL:rnCarlsberg_WL:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF514-53T
  dmi.product.sku: 
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time

2020-11-01 Thread jeremyszu
** Changed in: oem-priority
 Assignee: (unassigned) => jeremyszu (os369510)

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1902464

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device in at the same time

Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After backporting following patches from PA and alsa-ucm-conf and then
  it works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-11-01 Thread smurf
ok, but what about that "Maxxter wireless receiver"?
I don't understand: my laptop has 2 pieces of hardware to manage the wi-fi?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871794

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1902464] [NEW] The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time

2020-11-01 Thread jeremyszu
Public bug reported:

After backporting following patches from PA and alsa-ucm-conf and then
it works.

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-Audio

Here is the test PPA:
https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

Since the upstream not yet accepted those patches, the regression
potential may quite high.

** Affects: oem-priority
 Importance: Undecided
 Assignee: jeremyszu (os369510)
 Status: Confirmed

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


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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1902464

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device in at the same time

Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After backporting following patches from PA and alsa-ucm-conf and then
  it works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1902436] Re: Mouse slow in fractional scaling

2020-11-01 Thread Daniel van Vugt
This bug is somewhat expected because fractional scaling works by
rendering the desktop at a higher resolution than your screen. So it
will take more mouse movement for the pointer to cross the screen.

Integer scaling doesn't work that way so the mouse should move at
"normal" speed there.

** Tags added: xrandr-scaling

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Low

** Changed in: mutter (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1902436

Title:
  Mouse slow in fractional scaling

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  I have a Dell XPS 17 with a 3,840 x 2,400 screen and an external
  monitor with 3840 x 1600 resolution. When I use only one of them it
  works totally fine. I use the external monitor without scaling and my
  notebook display with fractional scaling of 150%. But when i want to
  use both at the same time, my mouse starts to be slow. So in this
  scenario i have the external monitor at 100% and the notebook screen
  at 150%. Everything works fine expect the mouse which is slow,on both
  screens. What I found is, when i set both my screens to 200% while
  fractional scaling is enabled. The issue is gone. Same with 100%. But
  as soon as I start using fractions, the mouse is slow again. I don't
  believe it is an power issue because my hardware is mostly in idle.
  Also, i tried different mouses over Bluetooth and USB but no change.

  I am currently using 20.10 but had the same issue with 20.04. But when
  i use Wayland, the problem is gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1)
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  1 14:01:59 2020
  DistUpgraded: 2020-10-30 12:11:16,382 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 1.7.0, 5.8.0-26-generic, x86_64: installed
   nvidia, 450.80.02, 5.8.0-26-generic, x86_64: installed
   soundwire, 1.2.2: added
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics [1028:098f]
   NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU106M [GeForce RTX 2060 Max-Q] [1028:098f]
  InstallationDate: Installed on 2020-09-19 (42 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. XPS 17 9700
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic 
root=UUID=6d098ea0-9d87-46ec-beb0-cc19a3b20841 ro quiet splash 
resume=UUID=723b6007-ad35-4e89-be9e-341d54fe18f8 nouveau.modset=0
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago)
  dmi.bios.date: 08/18/2020
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0P1CHN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd08/18/2020:br1.3:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P1CHN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9700
  dmi.product.sku: 098F
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: 

[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-11-01 Thread Hui Wang
@smurf,

OK, got your wifi's type, it is rtl8822ce, I will check if I could find
a machine with this Wifi chip in the office.

BTW, you could raise your issue to https://github.com/rtlwifi-linux too,
and I found there is a driver specific to 8822ce: https://github.com
/rtlwifi-linux/rtk_wifi_driver_rtl8822ce

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871794

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-11-01 Thread smurf
@Hui Wang,
actually I can't switch to hsp/hfp mode.
In BlueMan device window, if I try to switch profile I receive an error (the 
red bar at window bottom) and in Pulseaudio I don't have the option to switch.
Furthermore, in Blueman window manager, when I connect the headphone I see an 
orange button with an orange bar above, a green button with no bar above and a 
blue button with a blue bar above.
If I use a tp-link dongle I see the green bar as well.
On the same laptop I have windows 10 (dual boot) and there the headphone 
microphone works fine.

Here lspci and lusb output,let me know if you need some more info.

luca@laptop-luca:~$ lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root 
Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 
00h-1fh) PCIe Dummy Host Bridge
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP 
Bridge [6:0]
00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP 
Bridge [6:0]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 
00h-1fh) PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal 
PCIe GPP Bridge 0 to Bus A
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: 
Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: 
Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: 
Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: 
Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: 
Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: 
Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: 
Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: 
Function 7
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM981/PM981/PM983
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac 
PCIe Wireless Network Adapter
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Picasso (rev c2)
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] 
Raven/Raven2/Fenghuang HDMI/DP Audio Controller
03:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 10h-1fh) Platform Security Processor
03:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1
03:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1
03:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2/FireFlight/Renoir Audio Processor
03:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 
10h-1fh) HD Audio Controller
luca@laptop-luca:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 1358:c123 Realtek Bluetooth Radio
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 13d3:56f9 IMC Networks 
Bus 001 Device 004: ID 27c6:5110 Shenzhen Goodix Technology Co.,Ltd. 
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 248a:8514 Maxxter Wireless Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
luca@laptop-luca:~$

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871794

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: 

[Touch-packages] [Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly

2020-11-01 Thread Thiago Martins
Any news about this?!

The vim is still very bad on Ubuntu 20.04.

Any recommendation for a better /etc/vim/* ?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1767314

Title:
  Ubuntu Bionic vi/vim not working correctly

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  The vim default configuration in Bionic does not match Ubuntu 17.10
  nor Centos 7 and is hard to use. It auto-inserts tabs or spaces, and
  the '/' search mode command works differently (pressing enter is
  required before you can use cursors left/right).

  For some discussion, please see
  https://askubuntu.com/questions/1026820/vi-vim-usage-in-ubuntu-bionic-
  not-normal/1028684#1028684

  Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be
  required.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

2020-11-01 Thread DDD
i have also Problems with my internal MIC on HP x360 1040:
https://bugzilla.kernel.org/show_bug.cgi?id=201251#c231

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1523100

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-11-01 Thread DDD
Problem on my HP x360 1040 G5 with the internal MIC:
https://bugzilla.kernel.org/show_bug.cgi?id=201251#c231

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1840725

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1902446] [NEW] Not possible to see list of wifi networks

2020-11-01 Thread Vadim Peretokin
Public bug reported:

Using the default 'light' theme, the network listing is impossible to
read

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  1 19:41:38 2020
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-02-15 (1355 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Workspace 1_350.png"
   
https://bugs.launchpad.net/bugs/1902446/+attachment/5430088/+files/Workspace%201_350.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1902446

Title:
  Not possible to see list of wifi networks

Status in network-manager package in Ubuntu:
  New

Bug description:
  Using the default 'light' theme, the network listing is impossible to
  read

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  1 19:41:38 2020
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-15 (1355 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1770961] Re: Add options to set the snappy refresh schedule

2020-11-01 Thread Ads20000
Forum thread on this bug's feature request which includes Canonical
employee Alan Pope including in their strawman proposal an 'off switch':
https://forum.snapcraft.io/t/re-visiting-update-control-on-the-
desktop/17170

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1770961

Title:
  Add options to set the snappy refresh schedule

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Snappy has a feature where the user can state when in a month to
  refresh (update) their snaps. Please provide options in Software &
  Updates to control this.

  https://docs.snapcraft.io/system-options

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun May 13 15:10:07 2018
  InstallationDate: Installed on 2017-08-03 (282 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

2020-11-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1901922

Title:
  [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After logging in, only a dummy device is available for audio playback
  (resulting in no audible playback). When running "pactl load-module
  module-detect" the sound card shows up, and playback works as
  expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UDCTO1WW
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1902437] [NEW] `rm -i` doesn't work well if "language-pack-es" is installed. Problems arise

2020-11-01 Thread Ganton
Public bug reported:

Dear people,

SUMMARY
After "deleting" files, sometimes users will have great problems because, for 
example, important information has not been deleted and users don't know it.

STEPS TO REPRODUCE
Install the "language-pack-es" package, reboot.
Execute `touch 1; rm -i 1`
See that you are asked "rm: ¿borrar el fichero regular vacío '1'? (s/n)" (it 
means "do you want to delete the empty file 1?").
Press the S key (that means the same as pressing the Y key in the 
English-speaking version)
Press Return.
See that the file is not deleted, and you don't know about it.

EXPECTED RESULT
As always has happened, pressing the S key and Return would have deleted the 
file.
Note: Pressing the Y key and Return really deletes the file.

OS VERSIONS
Linux: Ubuntu 20.10
Note: The bug doesn't happen using Ubuntu 20.04

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

** Description changed:

  Dear people,
  
  SUMMARY
- Sometimes users get deceived when deleting files, and some of them will have 
great problems because, for example, important information has not been deleted.
+ After "deleting" files, sometimes users will have great problems because, for 
example, important information has not been deleted and users don't know it.
  
  STEPS TO REPRODUCE
  Install the "language-pack-es" package, reboot.
  Execute `touch 1; rm -i 1`
  See that you are asked "rm: ¿borrar el fichero regular vacío '1'? (s/n)" (it 
means "do you want to delete the empty file 1?").
  Press the S key (that means the same as pressing the Y key in the 
English-speaking version)
  Press Return.
  See that the file is not deleted, and you don't know about it.
  
  EXPECTED RESULT
  As always has happened, pressing the S key and Return would have deleted the 
file.
  Note: Pressing the Y key and Return really deletes the file.
  
  OS VERSIONS
  Linux: Ubuntu 20.10
  Note: The bug doesn't happen using Ubuntu 20.04

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1902437

Title:
  `rm -i` doesn't work well if "language-pack-es" is installed. Problems
  arise

Status in coreutils package in Ubuntu:
  New

Bug description:
  Dear people,

  SUMMARY
  After "deleting" files, sometimes users will have great problems because, for 
example, important information has not been deleted and users don't know it.

  STEPS TO REPRODUCE
  Install the "language-pack-es" package, reboot.
  Execute `touch 1; rm -i 1`
  See that you are asked "rm: ¿borrar el fichero regular vacío '1'? (s/n)" (it 
means "do you want to delete the empty file 1?").
  Press the S key (that means the same as pressing the Y key in the 
English-speaking version)
  Press Return.
  See that the file is not deleted, and you don't know about it.

  EXPECTED RESULT
  As always has happened, pressing the S key and Return would have deleted the 
file.
  Note: Pressing the Y key and Return really deletes the file.

  OS VERSIONS
  Linux: Ubuntu 20.10
  Note: The bug doesn't happen using Ubuntu 20.04

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1902432] Re: Carte son non detectée pourtant vu dans le terminal (son sortie fictive)

2020-11-01 Thread Chloé BREDON
I am on an ASUS X555BP initially Windows 8 then update for Windows 10. 
Following a modification by myself on the graphics card (update) there was an 
incompatibility so I went on Ubuntu 20.04.1 LTS by usb key . I am in 64 bits 
under gnome 3.36.3. No problem to play a video etc except that the sound does 
not come out. In the terminal I have already uninstalled and reinstalled Pulse 
Audio, Alsa etc. It is able to give me the name of my graphics card when I 
query it through sudo lspci A9-9420 radeon r5, 5 compute cores 2c + 3g × 2 but 
no card is detected when I type aplay -l.
Normally the operating system automatically installs drivers compatible with my 
graphics card so I don't know what to do. According to apt-cache I am using apt 
2.0.2ubuntu0.1 (amd64) and I have also struggle with my computer's load 
detection. It accepts to be in charge once in ten which did not happen before. 
My computer was checked by a computer scientist, I have no hard drive or 
motherboard problem.

** Summary changed:

- Carte son non detectée pourtant vu dans le terminal (son sortie fictive)
+ Sound card not detected yet seen in the terminal (fictitious output sound)

** Description changed:

  Je suis sur un ASUS X555BP initialement Windows 8 puis maj pour windows 10. 
Suite à une modification de ma part sur la carte graphique (maj) il y a eut une 
incompatibilité donc j'ai du passé sur Ubuntu 20.04.1 LTS par clé usb. Je suis 
en 64 bits sous gnome 3.36.3. Aucun problème pour lire une vidéo etc si ce 
n'est que le son ne sort pas. Dans le terminal j'ai déjà désintallé et 
réinstallé Pulse Audio. Il est capable de me sortir le nom de ma carte 
graphique quand je l'interroge par sudo lspci A9-9420 radeon r5, 5 compute 
cores 2c+3g × 2 mais aucune carte n'est détecté quand je tape aplay -l.
  Normalement le système d'exploitation installe automatiquement des drivers 
compatibles avec ma carte graphique donc je ne sais pas quoi faire. D'après 
apt-cache j'use apt 2.0.2ubuntu0.1 (amd64).
+ Oh et j'ai aussi un problème de detection de mise en charge de ma batterie 
d'ordinateur, je ne sais pas si c'est lié. Cependant cela n'arrivait pas avant. 
Un informaticien a déjà regardé mon oridinateur, je n'ai pas de problème de 
disque dur ou de carte mère.
+ 
+ I am on an ASUS X555BP initially Windows 8 then update for Windows 10. 
Following a modification by myself on the graphics card (update) there was an 
incompatibility so I went on Ubuntu 20.04.1 LTS by usb key . I am in 64 bits 
under gnome 3.36.3. No problem to play a video etc except that the sound does 
not come out. In the terminal I have already uninstalled and reinstalled Pulse 
Audio, Alsa etc. It is able to give me the name of my graphics card when I 
query it through sudo lspci A9-9420 radeon r5, 5 compute cores 2c + 3g × 2 but 
no card is detected when I type aplay -l.
+ Normally the operating system automatically installs drivers compatible with 
my graphics card so I don't know what to do. According to apt-cache I am using 
apt 2.0.2ubuntu0.1 (amd64) and I have also struggle with my computer's load 
detection. It accepts to be in charge once in ten which did not happen before. 
My computer was checked by a computer scientist, I have no hard drive or 
motherboard problem.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  1 13:52:11 2020
  InstallationDate: Installed on 2020-10-13 (18 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555BP.326
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555BP
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555BP.326:bd05/13/2019:svnASUSTeKCOMPUTERINC.:pnX555BP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555BP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555BP
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

-- 
You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1902436] Re: Mouse slow in fractional scaling

2020-11-01 Thread Sevi
I forgot to say that this problem is only with the external mouse. With
the touch pad, i have no issue.

I have an RTX 2060 Max-q in my notebook with Nvidia driver installed but
it is deactivated as on demand. But even if I enable this card, it has
no effect.

I believe that because of the fractional scaling, the reading of the
input device gets somehow mixed up.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1902436

Title:
  Mouse slow in fractional scaling

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Dell XPS 17 with a 3,840 x 2,400 screen and an external
  monitor with 3840 x 1600 resolution. When I use only one of them it
  works totally fine. I use the external monitor without scaling and my
  notebook display with fractional scaling of 150%. But when i want to
  use both at the same time, my mouse starts to be slow. So in this
  scenario i have the external monitor at 100% and the notebook screen
  at 150%. Everything works fine expect the mouse which is slow,on both
  screens. What I found is, when i set both my screens to 200% while
  fractional scaling is enabled. The issue is gone. Same with 100%. But
  as soon as I start using fractions, the mouse is slow again. I don't
  believe it is an power issue because my hardware is mostly in idle.
  Also, i tried different mouses over Bluetooth and USB but no change.

  I am currently using 20.10 but had the same issue with 20.04. But when
  i use Wayland, the problem is gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1)
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  1 14:01:59 2020
  DistUpgraded: 2020-10-30 12:11:16,382 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 1.7.0, 5.8.0-26-generic, x86_64: installed
   nvidia, 450.80.02, 5.8.0-26-generic, x86_64: installed
   soundwire, 1.2.2: added
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics [1028:098f]
   NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU106M [GeForce RTX 2060 Max-Q] [1028:098f]
  InstallationDate: Installed on 2020-09-19 (42 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. XPS 17 9700
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic 
root=UUID=6d098ea0-9d87-46ec-beb0-cc19a3b20841 ro quiet splash 
resume=UUID=723b6007-ad35-4e89-be9e-341d54fe18f8 nouveau.modset=0
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago)
  dmi.bios.date: 08/18/2020
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0P1CHN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd08/18/2020:br1.3:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P1CHN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9700
  dmi.product.sku: 098F
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: 

[Touch-packages] [Bug 1902436] [NEW] Mouse slow in fractional scaling

2020-11-01 Thread Sevi
Public bug reported:

I have a Dell XPS 17 with a 3,840 x 2,400 screen and an external monitor
with 3840 x 1600 resolution. When I use only one of them it works
totally fine. I use the external monitor without scaling and my notebook
display with fractional scaling of 150%. But when i want to use both at
the same time, my mouse starts to be slow. So in this scenario i have
the external monitor at 100% and the notebook screen at 150%. Everything
works fine expect the mouse which is slow,on both screens. What I found
is, when i set both my screens to 200% while fractional scaling is
enabled. The issue is gone. Same with 100%. But as soon as I start using
fractions, the mouse is slow again. I don't believe it is an power issue
because my hardware is mostly in idle. Also, i tried different mouses
over Bluetooth and USB but no change.

I am currently using 20.10 but had the same issue with 20.04. But when i
use Wayland, the problem is gone.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.80.02  Wed Sep 23 01:13:39 
UTC 2020
 GCC version:  gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1)
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  1 14:01:59 2020
DistUpgraded: 2020-10-30 12:11:16,382 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: groovy
DistroVariant: ubuntu
DkmsStatus:
 evdi, 1.7.0, 5.8.0-26-generic, x86_64: installed
 nvidia, 450.80.02, 5.8.0-26-generic, x86_64: installed
 soundwire, 1.2.2: added
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics [1028:098f]
 NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Dell TU106M [GeForce RTX 2060 Max-Q] [1028:098f]
InstallationDate: Installed on 2020-09-19 (42 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. XPS 17 9700
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic 
root=UUID=6d098ea0-9d87-46ec-beb0-cc19a3b20841 ro quiet splash 
resume=UUID=723b6007-ad35-4e89-be9e-341d54fe18f8 nouveau.modset=0
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago)
dmi.bios.date: 08/18/2020
dmi.bios.release: 1.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.2
dmi.board.name: 0P1CHN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd08/18/2020:br1.3:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P1CHN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug groovy ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1902436

Title:
  Mouse slow in fractional scaling

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Dell XPS 17 with a 3,840 x 2,400 screen and an external
  monitor with 3840 x 1600 resolution. When I use only one of them it
  works totally fine. I use the external monitor without scaling and my
  notebook display with fractional scaling of 150%. But when i want 

[Touch-packages] [Bug 1902432] Re: Carte son non detectée pourtant vu dans le terminal (son sortie fictive)

2020-11-01 Thread lotuspsychje
Thank you for taking the time to report this issue and helping to make
Ubuntu better. We noticed that some of the sentences in this bug report
are not in English. If they were translated to English they would be
more understandable to triagers. Could you please translate them?

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1902432

Title:
  Carte son non detectée pourtant vu dans le terminal (son sortie
  fictive)

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Je suis sur un ASUS X555BP initialement Windows 8 puis maj pour windows 10. 
Suite à une modification de ma part sur la carte graphique (maj) il y a eut une 
incompatibilité donc j'ai du passé sur Ubuntu 20.04.1 LTS par clé usb. Je suis 
en 64 bits sous gnome 3.36.3. Aucun problème pour lire une vidéo etc si ce 
n'est que le son ne sort pas. Dans le terminal j'ai déjà désintallé et 
réinstallé Pulse Audio. Il est capable de me sortir le nom de ma carte 
graphique quand je l'interroge par sudo lspci A9-9420 radeon r5, 5 compute 
cores 2c+3g × 2 mais aucune carte n'est détecté quand je tape aplay -l.
  Normalement le système d'exploitation installe automatiquement des drivers 
compatibles avec ma carte graphique donc je ne sais pas quoi faire. D'après 
apt-cache j'use apt 2.0.2ubuntu0.1 (amd64).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  1 13:52:11 2020
  InstallationDate: Installed on 2020-10-13 (18 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555BP.326
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555BP
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555BP.326:bd05/13/2019:svnASUSTeKCOMPUTERINC.:pnX555BP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555BP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555BP
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1902432] [NEW] Carte son non detectée pourtant vu dans le terminal (son sortie fictive)

2020-11-01 Thread Chloé BREDON
Public bug reported:

Je suis sur un ASUS X555BP initialement Windows 8 puis maj pour windows 10. 
Suite à une modification de ma part sur la carte graphique (maj) il y a eut une 
incompatibilité donc j'ai du passé sur Ubuntu 20.04.1 LTS par clé usb. Je suis 
en 64 bits sous gnome 3.36.3. Aucun problème pour lire une vidéo etc si ce 
n'est que le son ne sort pas. Dans le terminal j'ai déjà désintallé et 
réinstallé Pulse Audio. Il est capable de me sortir le nom de ma carte 
graphique quand je l'interroge par sudo lspci A9-9420 radeon r5, 5 compute 
cores 2c+3g × 2 mais aucune carte n'est détecté quand je tape aplay -l.
Normalement le système d'exploitation installe automatiquement des drivers 
compatibles avec ma carte graphique donc je ne sais pas quoi faire. D'après 
apt-cache j'use apt 2.0.2ubuntu0.1 (amd64).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  1 13:52:11 2020
InstallationDate: Installed on 2020-10-13 (18 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/13/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X555BP.326
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X555BP
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555BP.326:bd05/13/2019:svnASUSTeKCOMPUTERINC.:pnX555BP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555BP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X555BP
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1902432

Title:
  Carte son non detectée pourtant vu dans le terminal (son sortie
  fictive)

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Je suis sur un ASUS X555BP initialement Windows 8 puis maj pour windows 10. 
Suite à une modification de ma part sur la carte graphique (maj) il y a eut une 
incompatibilité donc j'ai du passé sur Ubuntu 20.04.1 LTS par clé usb. Je suis 
en 64 bits sous gnome 3.36.3. Aucun problème pour lire une vidéo etc si ce 
n'est que le son ne sort pas. Dans le terminal j'ai déjà désintallé et 
réinstallé Pulse Audio. Il est capable de me sortir le nom de ma carte 
graphique quand je l'interroge par sudo lspci A9-9420 radeon r5, 5 compute 
cores 2c+3g × 2 mais aucune carte n'est détecté quand je tape aplay -l.
  Normalement le système d'exploitation installe automatiquement des drivers 
compatibles avec ma carte graphique donc je ne sais pas quoi faire. D'après 
apt-cache j'use apt 2.0.2ubuntu0.1 (amd64).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  1 13:52:11 2020
  InstallationDate: Installed on 2020-10-13 (18 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555BP.326
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555BP
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Touch-packages] [Bug 1902430] [NEW] package ca-certificates 20201027ubuntu0.20.10.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exi

2020-11-01 Thread Craig Seabrooks
Public bug reported:

I just reinstalled Ubuntu 20.10 on RPi 4 (4GB)

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: ca-certificates 20201027ubuntu0.20.10.1
ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14
Uname: Linux 5.8.0-1006-raspi aarch64
ApportVersion: 2.20.11-0ubuntu50
AptOrdering:
 ca-certificates:arm64: Install
 NULL: ConfigurePending
Architecture: arm64
CasperMD5CheckResult: skip
Date: Sun Nov  1 07:18:27 2020
DuplicateSignature:
 package:ca-certificates:20201027ubuntu0.20.10.1
 Setting up ca-certificates (20201027ubuntu0.20.10.1) ...
 debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another 
process: Resource temporarily unavailable
 dpkg: error processing package ca-certificates (--configure):
  installed ca-certificates package post-installation script subprocess 
returned error exit status 1
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
ImageMediaBuild: 20201022
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10
SourcePackage: ca-certificates
Title: package ca-certificates 20201027ubuntu0.20.10.1 failed to 
install/upgrade: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package arm64 groovy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1902430

Title:
  package ca-certificates 20201027ubuntu0.20.10.1 failed to
  install/upgrade: installed ca-certificates package post-installation
  script subprocess returned error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  I just reinstalled Ubuntu 20.10 on RPi 4 (4GB)

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: ca-certificates 20201027ubuntu0.20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14
  Uname: Linux 5.8.0-1006-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50
  AptOrdering:
   ca-certificates:arm64: Install
   NULL: ConfigurePending
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Sun Nov  1 07:18:27 2020
  DuplicateSignature:
   package:ca-certificates:20201027ubuntu0.20.10.1
   Setting up ca-certificates (20201027ubuntu0.20.10.1) ...
   debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by 
another process: Resource temporarily unavailable
   dpkg: error processing package ca-certificates (--configure):
installed ca-certificates package post-installation script subprocess 
returned error exit status 1
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  ImageMediaBuild: 20201022
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10
  SourcePackage: ca-certificates
  Title: package ca-certificates 20201027ubuntu0.20.10.1 failed to 
install/upgrade: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1902430] Re: package ca-certificates 20201027ubuntu0.20.10.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit

2020-11-01 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1902430

Title:
  package ca-certificates 20201027ubuntu0.20.10.1 failed to
  install/upgrade: installed ca-certificates package post-installation
  script subprocess returned error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  I just reinstalled Ubuntu 20.10 on RPi 4 (4GB)

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: ca-certificates 20201027ubuntu0.20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14
  Uname: Linux 5.8.0-1006-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50
  AptOrdering:
   ca-certificates:arm64: Install
   NULL: ConfigurePending
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Sun Nov  1 07:18:27 2020
  DuplicateSignature:
   package:ca-certificates:20201027ubuntu0.20.10.1
   Setting up ca-certificates (20201027ubuntu0.20.10.1) ...
   debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by 
another process: Resource temporarily unavailable
   dpkg: error processing package ca-certificates (--configure):
installed ca-certificates package post-installation script subprocess 
returned error exit status 1
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  ImageMediaBuild: 20201022
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10
  SourcePackage: ca-certificates
  Title: package ca-certificates 20201027ubuntu0.20.10.1 failed to 
install/upgrade: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)

2020-11-01 Thread Guilherme G. Piccoli
I was able to verify this bug with systemd from bionic-proposed (version
237-3ubuntu10.43) by following the procedure in the test case; it's
working as expected, I can see 64M in the memlock limit.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1830746

Title:
  memlock setting in systemd (pid 1) too low for containers (bionic)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [Impact]
  * Since systemd commit fb3ae275cb ("main: bump RLIMIT_NOFILE for the root 
user substantially") [https://github.com/systemd/systemd/commit/fb3ae275cb], 
which is present in Bionic, the memlock ulimit value was bumped to 16M. It's an 
adjustable limit, but the default (in previous Ubuntu releases/systemd 
versions) was really small.
  * Although bumping this value was a good thing, 16M is not enough and we can 
see failures on mlock'ed allocations on Bionic, like the one hereby reported by 
Kees or the recent introduced cryptsetup build failures (due to PPA builder 
updates to Bionic) - see https://bugs.launchpad.net/bugs//1891473.

  * It's especially harmful in containers to have such "small" limit, so
  we are hereby SRUing a more recent bump from upstream systemd, in the
  form of commit 91cfdd8d29 ("core: bump mlock ulimit to 64Mb")
  [https://github.com/systemd/systemd/commit/91cfdd8d29]. Latest Ubuntu
  releases, like Focal and subsequent ones, already include this patch
  so effectively we're putting Bionic on-par with newer releases.

  * A discussion about this topic (leading to this SRU) is present in
  ubuntu-devel ML: https://lists.ubuntu.com/archives/ubuntu-
  devel/2020-September/041159.html.

  [Test Case]
  * The straightforward test is to just look "ulimit -l" and "ulimit -Hl" in a 
current Bionic system, and then install an updated version with the hereby 
proposed SRU to see such limit bump from 16M to 64M (after a reboot) - a 
version containing this fix is available at my PPA as of 2020-09-10 [0] (likely 
to be deleted in next month or so).

  * A more interesting test is to run a Focal container in a current
  Bionic system and try to build the cryptsetup package - it'll fail in
  some tests. After updating the host (Bionic) systemd to include the
  mlock bump patch, the build succeeds in the Focal container.

  [Regression Potential]
  * Since it's a simple bump and it makes Bionic behave like Focal, I don't 
foresee regressions. One potential issue would be if some users rely on the 
lower default limit (16M) and this value is bumped by a package update, but 
that could be circumvented by setting a lower limit in limits.conf. The 
benefits for such bump are likely much bigger than any "regression" caused for 
users relying on such default limit.

  
  [0] https://launchpad.net/~gpiccoli/+archive/ubuntu/test1830746

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1902427] [NEW] systemd pauses for unspecified reason

2020-11-01 Thread ralphb
Public bug reported:

I recently installed Kubuntu 20.04 on a new Ryzen 3900X system. I
noticed that the boot time (time between entering LUKS credentials and
appearance of login screen) took more than 1 minute.

Using `systemd-analyze`, I found the following:

```
cassiopeia:~# systemd-analyze 
Startup finished in 24.819s (kernel) + 1min 32.150s (userspace) = 1min 56.969s 
graphical.target reached after 1min 32.144s in userspace
cassiopeia:~# systemd-analyze blame
4.721s fstrim.service   
2.949s apt-daily-upgrade.service
2.380s systemd-cryptsetup@store.service 
1.739s NetworkManager-wait-online.service   
 439ms apt-daily.service
 421ms man-db.service   
 398ms systemd-logind.service   
 323ms dev-mapper-root.device   
 294ms systemd-fsck@dev-mapper-store.service
 204ms logrotate.service
 153ms systemd-journald.service 
...
cassiopeia:~# systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 32.144s
└─multi-user.target @1min 32.144s
  └─fetchmail.service @1min 32.128s +16ms
└─network-online.target @1min 32.127s
  └─NetworkManager-wait-online.service @1min 30.388s +1.739s
└─NetworkManager.service @1min 30.282s +105ms
  └─dbus.service @1min 30.279s
└─basic.target @1min 30.265s
  └─sockets.target @1min 30.265s
└─snapd.socket @1min 30.264s +370us
  └─sysinit.target @1min 30.262s
└─systemd-timesyncd.service @1min 30.219s +42ms
  └─systemd-tmpfiles-setup.service @1min 30.202s +15ms
└─systemd-journal-flush.service @288ms +49ms
  └─systemd-journald.service @131ms +153ms
└─systemd-journald.socket @129ms
  └─-.mount @127ms
└─blockdev@dev-mapper-root.target @410ms
  └─systemd-cryptsetup@root.service @401ms +8ms
└─dev-nvme0n1p2.device @398ms
```

This didn't really help, but `systemd-analyze plot > boot.svg` produced
an SVG file (see attachment) that shows a gap between store.mount
(completes within 38 ms) and apparmor.service of almost 1:30 minutes.
What did systemd do during this gap?

I think it is either a bug in systemd that idles, or in systemd-analyze
that doesn't disclose the actions in that gap.

(Note: I have posted this question in two well-known Ubuntu forums, but
I didn't receive any answers.)

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

** Attachment added: "boot.svg"
   https://bugs.launchpad.net/bugs/1902427/+attachment/5429998/+files/boot.svg

** Package changed: snapd (Ubuntu) => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1902427

Title:
  systemd pauses for unspecified reason

Status in systemd package in Ubuntu:
  New

Bug description:
  I recently installed Kubuntu 20.04 on a new Ryzen 3900X system. I
  noticed that the boot time (time between entering LUKS credentials and
  appearance of login screen) took more than 1 minute.

  Using `systemd-analyze`, I found the following:

  ```
  cassiopeia:~# systemd-analyze 
  Startup finished in 24.819s (kernel) + 1min 32.150s (userspace) = 1min 
56.969s 
  graphical.target reached after 1min 32.144s in userspace
  cassiopeia:~# systemd-analyze blame
  4.721s fstrim.service   
  2.949s apt-daily-upgrade.service
  2.380s systemd-cryptsetup@store.service 
  1.739s NetworkManager-wait-online.service   
   439ms apt-daily.service
   421ms man-db.service   
   398ms systemd-logind.service   
   323ms dev-mapper-root.device   
   294ms systemd-fsck@dev-mapper-store.service
   204ms logrotate.service
   153ms systemd-journald.service 
  ...
  cassiopeia:~# systemd-analyze critical-chain
  The time when unit became active or started is printed after the "@" 
character.
  The time the unit took to start is printed after the "+" character.

  graphical.target @1min 32.144s
  └─multi-user.target @1min 32.144s
└─fetchmail.service @1min 32.128s +16ms
  └─network-online.target @1min 32.127s
└─NetworkManager-wait-online.service @1min 30.388s +1.739s
  └─NetworkManager.service @1min 30.282s +105ms
└─dbus.service @1min 30.279s
  └─basic.target @1min 30.265s
└─sockets.target @1min 30.265s
  └─snapd.socket @1min 30.264s +370us
└─sysinit.target @1min 30.262s
   

[Touch-packages] [Bug 1902427] [NEW] systemd pauses for unspecified reason

2020-11-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I recently installed Kubuntu 20.04 on a new Ryzen 3900X system. I
noticed that the boot time (time between entering LUKS credentials and
appearance of login screen) took more than 1 minute.

Using `systemd-analyze`, I found the following:

```
cassiopeia:~# systemd-analyze 
Startup finished in 24.819s (kernel) + 1min 32.150s (userspace) = 1min 56.969s 
graphical.target reached after 1min 32.144s in userspace
cassiopeia:~# systemd-analyze blame
4.721s fstrim.service   
2.949s apt-daily-upgrade.service
2.380s systemd-cryptsetup@store.service 
1.739s NetworkManager-wait-online.service   
 439ms apt-daily.service
 421ms man-db.service   
 398ms systemd-logind.service   
 323ms dev-mapper-root.device   
 294ms systemd-fsck@dev-mapper-store.service
 204ms logrotate.service
 153ms systemd-journald.service 
...
cassiopeia:~# systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 32.144s
└─multi-user.target @1min 32.144s
  └─fetchmail.service @1min 32.128s +16ms
└─network-online.target @1min 32.127s
  └─NetworkManager-wait-online.service @1min 30.388s +1.739s
└─NetworkManager.service @1min 30.282s +105ms
  └─dbus.service @1min 30.279s
└─basic.target @1min 30.265s
  └─sockets.target @1min 30.265s
└─snapd.socket @1min 30.264s +370us
  └─sysinit.target @1min 30.262s
└─systemd-timesyncd.service @1min 30.219s +42ms
  └─systemd-tmpfiles-setup.service @1min 30.202s +15ms
└─systemd-journal-flush.service @288ms +49ms
  └─systemd-journald.service @131ms +153ms
└─systemd-journald.socket @129ms
  └─-.mount @127ms
└─blockdev@dev-mapper-root.target @410ms
  └─systemd-cryptsetup@root.service @401ms +8ms
└─dev-nvme0n1p2.device @398ms
```

This didn't really help, but `systemd-analyze plot > boot.svg` produced
an SVG file (see attachment) that shows a gap between store.mount
(completes within 38 ms) and apparmor.service of almost 1:30 minutes.
What did systemd do during this gap?

I think it is either a bug in systemd that idles, or in systemd-analyze
that doesn't disclose the actions in that gap.

(Note: I have posted this question in two well-known Ubuntu forums, but
I didn't receive any answers.)

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

-- 
systemd pauses for unspecified reason
https://bugs.launchpad.net/bugs/1902427
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1902311] Re: GNU sha256sum(1) --check (-c) output depends on order of --quiet and --warn

2020-11-01 Thread Brian Foster
** Summary changed:

- GNU sha256(1)  --check (-c) output depends on order of --quiet and --warn
+ GNU sha256sum(1)  --check (-c) output depends on order of --quiet and 
--warn

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1902311

Title:
  GNU sha256sum(1)  --check (-c) output depends on order of --quiet
  and --warn

Status in coreutils package in Ubuntu:
  Confirmed

Bug description:
  The output of GNU sha256sum --check (or -c), and related tools (i.e., sha1sum,
  sha224sum, sha384sum, and sha512sum) depends on the order of the --quiet and
  --warn options.  This is counter-intuitive, not documented in the man(1) 
pages,
  and unnecessary.

  Simple example:

1$ date >/tmp/data
2$ sha256sum /tmp/data >/tmp/sums
3$ sha256sum -c --warn --quiet /tmp/sums# No output (expected)
4$ sha256sum -c --quiet --warn /tmp/sums# Unexpected "Ok"...
/tmp/data: OK
5$ 

  The manual page says (spurious lines omitted):

 The following five options are useful only when verifying checksums:
   --quiet   don't print OK for each successfully verified file
   -w, --warnwarn about improperly formatted checksum lines

  There is no reason --warn should affect the operation of --quiet (nor
  visa-versa).  The operations as documented are orthogonal.

  Attached is a bash(1) shell script written when puzzling over this
  inconsistent behaviour; it may be useful (use --help for a summary).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: coreutils 8.30-3ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Oct 30 21:34:31 2020
  InstallationDate: Installed on 2020-10-19 (11 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2020-11-01 Thread Steve Langasek
** Changed in: debconf (Ubuntu)
 Assignee: Ahmed Mohamed Tayel (atayel18) => (unassigned)

** Changed in: aptdaemon (Ubuntu)
 Assignee: Ahmed Mohamed Tayel (atayel18) => (unassigned)

** Changed in: aptdaemon
 Assignee: Ahmed Mohamed Tayel (atayel18) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/349469

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Invalid
Status in debconf package in Ubuntu:
  Fix Released

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp