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

2020-11-22 Thread Anthony Wong
** Also affects: hwe-next
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: alsa-ucm-conf (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

-- 
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 HWE Next:
  New
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/hwe-next/+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 1273524] Re: LXDE guest session shows error message "no session for pid "

2020-11-22 Thread Chris Guiver
Thank you for reporting this bug to Ubuntu.

Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

Note: Lubuntu (universe) packages in Xenial 16.04 are unsupported,
having been since 2019-April.

** Changed in: lightdm
   Status: Triaged => Incomplete

** Changed in: lightdm/1.18
   Status: Triaged => Incomplete

** Changed in: hundredpapercuts
   Status: Triaged => Incomplete

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

** Changed in: lxsession (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Incomplete
Status in Light Display Manager:
  Incomplete
Status in Light Display Manager 1.18 series:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete
Status in lxsession package in Ubuntu:
  Incomplete
Status in lightdm source package in Xenial:
  Confirmed
Status in lxsession source package in Xenial:
  Confirmed

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+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 1872504] Re: date modified is wrong for files on an exfat formatted drive

2020-11-22 Thread Oleg
Same issue here with the files copied from my Sony a6000 camera. Any
suggestions how to fix it?

>After installing fuse-exfat 
It gives me "E: Unable to locate package fuse-exfat"

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

Title:
  date modified is wrong for files on an exfat formatted drive

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  When using exfat formatted drives (e.g. my camera card) with focal
  fossa any access causes the date modified to be set, even when it
  would not normally be set, and it is set a month into the future.

  Installing exfat-fuse and exfat-utils results in the correct
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 17:27:30 2020
  InstallationDate: Installed on 2020-04-12 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1872504/+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 1891910] Re: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: initramfs-tools paketi post-installation betiği kuruldu alt süreci 1 hatalı çıkış kodu ile sona erd

2020-11-22 Thread Tim Kruzel
This is my first post here so I apologize if this is not appropriate.

On Nov 22, 2020 I upgraded from 18.04 LTS to 20.04 LTS over the wire (no
physical media). During the upgrade I received the following error
message in a dialog box:

"Could not install initramfs-tools"

"The upgrade will continue but the initramfs-tools package may not be in
a working state. Please consider submitting a bug report about it."
(which I did)

"installed initramfs-tools package post installation script subprocess
returned error exit status 1"

My system seems to be working with the 20.04 upgrade applied. I don't
know the language that this web page
(https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1891910)
is written in, so I am not sure what if any action I should be taking.
Is there a fix? Can anyone explain in English please? Thanks!

** Attachment added: "initramfs-tools-INSTALL_ERROR.png"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1891910/+attachment/5437127/+files/initramfs-tools-INSTALL_ERROR.png

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

Title:
  package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade:
  initramfs-tools paketi post-installation betiği kuruldu alt süreci 1
  hatalı çıkış kodu ile sona erdi

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  E: 'http://ppa.launchpad.net/tualatrix/next/ubuntu focal Release' deposunda 
Release dosyası yok.
  N: Böyle bir depodan güvenli bir şekilde güncelleme yapılamaz, bu nedenle 
depo devre dışı bırakılmıştır.
  N: Depo oluşturma ve kullanıcı yapılandırması hakkında ayrıntılı bilgi için 
apt-secure(8) rehber sayfasında bulunabilir. bu sorunu çözemiyorum

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Aug 17 18:38:35 2020
  ErrorMessage: initramfs-tools paketi post-installation betiği kuruldu alt 
süreci 1 hatalı çıkış kodu ile sona erdi
  InstallationDate: Installed on 2020-08-15 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 
initramfs-tools paketi post-installation betiği kuruldu alt süreci 1 hatalı 
çıkış kodu ile sona erdi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1891910/+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 1891910] Re: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: initramfs-tools paketi post-installation betiği kuruldu alt süreci 1 hatalı çıkış kodu ile sona erd

2020-11-22 Thread Tim Kruzel
This is my first post here so I apologize if this is not appropriate.

On Nov 22, 2020 I upgraded from 18.04 LTS to 20.04 LTS over the wire (no
physical media). During the upgrade I received the following error
message in a dialog box:

"Could not install initramfs-tools"

"The upgrade will continue but the initramfs-tools package may not be in
a working state. Please consider submitting a bug report about it."
(which I did)

"installed initramfs-tools package post installation script subprocess
returned error exit status 1"

My system seems to be working with the 20.04 upgrade applied. I don't
know the language that this web page
(https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1891910)
is written in, so I am not sure what if any action I should be taking.
Is there a fix? Can anyone explain in English please? Thanks!

** Attachment added: "initramfs-tools-INSTALL_ERROR.png"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1891910/+attachment/5437126/+files/initramfs-tools-INSTALL_ERROR.png

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

Title:
  package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade:
  initramfs-tools paketi post-installation betiği kuruldu alt süreci 1
  hatalı çıkış kodu ile sona erdi

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  E: 'http://ppa.launchpad.net/tualatrix/next/ubuntu focal Release' deposunda 
Release dosyası yok.
  N: Böyle bir depodan güvenli bir şekilde güncelleme yapılamaz, bu nedenle 
depo devre dışı bırakılmıştır.
  N: Depo oluşturma ve kullanıcı yapılandırması hakkında ayrıntılı bilgi için 
apt-secure(8) rehber sayfasında bulunabilir. bu sorunu çözemiyorum

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Aug 17 18:38:35 2020
  ErrorMessage: initramfs-tools paketi post-installation betiği kuruldu alt 
süreci 1 hatalı çıkış kodu ile sona erdi
  InstallationDate: Installed on 2020-08-15 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 
initramfs-tools paketi post-installation betiği kuruldu alt süreci 1 hatalı 
çıkış kodu ile sona erdi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1891910/+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 1905185] Re: [ThinkPad T14s Gen 1 20UJ0014IX] Internal microphone randomly does not work

2020-11-22 Thread Daniel van Vugt
** Summary changed:

- [20UJ0014IX, Realtek ALC257, Speaker, Internal] Pulseaudio fails to detect 
card
+ [ThinkPad T14s Gen 1 20UJ0014IX] Internal microphone randomly does not work

-- 
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/1905185

Title:
  [ThinkPad T14s Gen 1 20UJ0014IX] Internal microphone randomly does not
  work

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  good evening, I have a problem with internal microphone, sometimes it works 
and sometimes it doesn't, it happens randomly, just a restart
  my pc should be Ubuntu certified

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  roxibar73   1518 F pulseaudio
   /dev/snd/controlC0:  roxibar73   1518 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 18:32:04 2020
  InstallationDate: Installed on 2020-11-20 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HD-Audio Generic
  Symptom_Jack: Speaker, Internal
  Title: [20UJ0014IX, Realtek ALC257, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2020
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET56W(1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UJ0014IX
  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.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET56W(1.25):bd09/15/2020:br1.25:efr1.25:svnLENOVO:pn20UJ0014IX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UJ0014IX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14s Gen 1
  dmi.product.name: 20UJ0014IX
  dmi.product.sku: LENOVO_MT_20UJ_BU_Think_FM_ThinkPad T14s Gen 1
  dmi.product.version: ThinkPad T14s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905185/+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 1905228] Re: DIsplay Rotates to Portrait Mode when Certain Apps Open

2020-11-22 Thread Daniel van Vugt
Interestingly Xwayland thinks the screen is portrait:

XWAYLAND2 connected 2160x3840+0+0 (0x3d3) normal (normal left inverted
right x axis y axis) 190mm x 340mm

but the BIOS and Xorg think it is landscape:

[0.495406] efifb: mode is 3840x2160x32, linelength=15360, pages=1

[52.062] (II) modeset(0): Modeline "3840x2160"x60.0  533.25  3840
3888 3920 4000  2160 2163 2168  -hsync -vsync (133.3 kHz eP)

so that makes me think it's just mutter/gnome-shell giving the wrong
info to Xwayland and certain apps.

Do you find the same bug in Xorg sessions? Try logging into 'Ubuntu'
instead of 'Ubuntu on Wayland'.

** Tags added: amdgpu hybrid

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

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

** 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/1905228

Title:
  DIsplay Rotates to Portrait Mode when Certain Apps Open

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using a 2 in 1 tablet with auto-rotation (Dell Precision 5530 2
  in 1), the screen will frequently incorrectly rotate whenever some
  apps open. This has been observed with Settings, Videos, Steam,
  Lollypop and Firefox. Issue still occurs when the screen rotation is
  locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 22:59:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:08ac]
 Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
  InstallationDate: Installed on 2020-11-18 (4 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5530 2-in-1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.10
  dmi.board.name: 02TH5P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrecision55302-in-1:pvr:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5530 2-in-1
  dmi.product.sku: 08AC
  dmi.sys.vendor: Dell Inc.
  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/gnome-shell/+bug/1905228/+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 1905184] Re: [Intel Gemini Lake] No video signal during Ubuntu splash screen and also during Logon procedure

2020-11-22 Thread Daniel van Vugt
This sounds like a kernel problem. And both plymouth and the login
screen do use the same kernel interfaces...

First, please try removing these kernel parameters:

  video=efifb fbcon=rotate:1

and if that doesn't solve it please also try changing the kernel
parameter "splash" to "nosplash".

Also you may be able to use this as a workaround for the login screen:
Edit /etc/gdm3/custom.conf and change:

  #WaylandEnable=false

to

  WaylandEnable=false


** Summary changed:

- No video signal during Ubuntu splash screen and also during Logon procedure
+ [Intel Gemini Lake] No video signal during Ubuntu splash screen and also 
during Logon procedure

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

** Changed in: linux (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/1905184

Title:
  [Intel Gemini Lake] No video signal during Ubuntu splash screen and
  also during Logon procedure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello.

  I don't have any video during Ubuntu splash screen and also during the logon 
procedure.
  I only have video in GRUB and after the logon operation takes place.
  After I type in my password (in blind mode), Ubuntu will then start normally 
with correct video settings (resolution, etc...).

  To workaround this error, I can either:

  Workaround 1) Enable automatic login. That way the system doesn't get stuck 
in logon screen and Ubuntu loads immediately.
  Problem: Boot splash won't be displayed anyway and I don't want this because 
I'm in a multi-user scenario.

  Workaround 2) Add a kernel boot option "nomodeset" in /etc/default/grub
  When I do this I will always get video signal.
  Problem: The computer is an ECS Hybrid Device (tablet+detachable keyboard), 
and when I use this workaround, user session loads in Portrait mode (not 
Landscape) and there is no auto-rotation support.

  Workaround 3) Although I don't have video signal during Boot Splash and Logon 
screen, I do have backlight continuously applied to the display.
  If I wait 5 minutes or so in the logon screen the backlight will deactivate...
  However, when I touch the keyboard or touchpad the computer will then show 
video signal and I will be able to see the logon screen perfectly.
  Problem: I don't want to wait 5 minutes in the logon screen to obtain proper 
video signal.

  Computer is this one:
  
https://www.ecs.com.tw/ECSWebSite/Product/Product_Overview/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC

  Specs are here:
  
https://www.ecs.com.tw/ECSWebSite/Product/Product_SPEC/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC

  Feel free to request any extra information.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Nov 22 19:56:20 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2020-11-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ECS CMPC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=2e7d6b98-86c2-4579-bd7f-fa31664333f6 ro quiet video=efifb 
fbcon=rotate:1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02.00.STD
  dmi.board.asset.tag: Default string
  dmi.board.name: ik Educational Software
  dmi.board.vendor: ECS
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 30
  dmi.chassis.vendor: NULL
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02.00.STD:bd10/15/2019:svnECS:pnCMPC:pvrDefaultstring:rvnECS:rnikEducationalSoftware:rvrDefaultstring:cvnNULL:ct30:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: CMPC
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: ECS
  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.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-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  

[Touch-packages] [Bug 1905142] Re: When vblank is send the monitors turn off then immediatly turn back on

2020-11-22 Thread Daniel van Vugt
It sounds like there are two bugs here so please choose which one you
would like this bug to be about.

Also "vblank" is something that happens 60 times per second when the
monitor is on, so I don't think you mean "vblank". Do you mean sleep
mode?

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

** Changed in: xserver-xorg-video-amdgpu (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/1905142

Title:
  When vblank is send the monitors turn off then immediatly turn back on

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  every time that happens the following message is shown in syslog:
  /usr/libexec/gdm-x-session[3330]: (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot 
get last vblank counter

  Also, the monitors turn on one by one which means that all windows are
  moved to the one that turns on first.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Uname: Linux 5.8.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 21 18:38:27 2020
  DistUpgraded: 2020-11-18 01:07:32,653 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
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] [1458:2316]
  MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming
  ProcEnviron:
   LANGUAGE=en_IE:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-30-generic 
root=UUID=556540f5-c271-4a31-8207-81a7fcaac401 ro amdgpu.dc=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to groovy on 2020-11-18 (3 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50a
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-03-16T23:17:19.931496
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1
  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 20.2.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Tue Nov 17 23:04:32 2020
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.8-2ubuntu2.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1905142/+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 1163644] Re: Login screen does not work; must log in via terminal and then startx

2020-11-22 Thread Chris Guiver
Thank you for reporting this bug to Ubuntu.

Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

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

Title:
  Login screen does not work; must log in via terminal and then startx

Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  I was running lubuntu 13.04 and wanted to see how gnome worked on my
  machine. (iBook G4)

  I installed it and was unable to log in via the login screen. Then i
  tried uninstalling. It still didn't work, and I didn't have a whole
  lubuntu-desktop package anymore. I reinstalled lubuntu-desktop and
  gnome, attempting to fix the problem.

  I'm going to reinstall and reattempt installing multiple desktop
  environments.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: login 1:4.1.5.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-6.12-powerpc-smp 3.8.4
  Uname: Linux 3.8.0-6-powerpc-smp ppc
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: powerpc
  Date: Tue Apr  2 21:27:45 2013
  InstallationDate: Installed on 2013-03-19 (14 days ago)
  InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Alpha powerpc 
(20130311.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1163644/+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 1455219] Re: Cannot connect to PPPoE using NetworkManager: Could not find pppoe binary.

2020-11-22 Thread Chris Guiver
Thank you for reporting this bug to Ubuntu.

Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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/1455219

Title:
  Cannot connect to PPPoE using NetworkManager: Could not find pppoe
  binary.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  TL;DR: NetworkManager requires "pppoe" package, which was not
  installed by default in Lubuntu 15.04.

  
  I tried using Network Manager (nm-applet) to configure a PPPoE connection. I 
can create the connection, but trying to connect to it fails.

  The erro message that shows up in a dialog is not helpful at all:

  (1) Creating object for path
  '/org/freedesktop/NetworkManager/ActiveConnection/23' failed in libnm-
  glib.

  What is helpful is a message buried in /var/log/syslog:

  
  NetworkManager[713]:  (eth0): PPPoE failed to start: Could not find 
pppoe binary.

  
  Workaround: apt-get install pppoe.

  Desirable solution: pppoe package being a dependency of another
  package (lubuntu-desktop seems like a good one).

  
  Using Lubuntu 15.04 (upgraded from previous versions). This is the first time 
configuring a DSL/PPPoE connection in this system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1455219/+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 1706701] Re: Default Keyring is not unlocked for the user in Lubuntu

2020-11-22 Thread Chris Guiver
** Tags added: bionic

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

Title:
  Default Keyring is not unlocked for the user in Lubuntu

Status in gnupg package in Ubuntu:
  Confirmed

Bug description:
  Example scenario:
  1. Go to the file manager (e.g. Nautilus, PCManFM)
  2. Connect to a server via FTP
  3. Enter the password and select "Remember forever"

  In Ubuntu, this is correctly placed into the Default Keyring, and
  remembered (even after a reboot) so that the password does not have to
  be retyped.

  But in Lubuntu, the Default Keyring is locked, and the user has to
  enter the account password to unlock it before it can be used by the
  system.

  • This must be done every time when attempting reconnection after reboot or 
after logging out and in again.
  • When this happens, even though the correct account password is entered, the 
first time, the FTP password is not retrieved.
  • If the Default Keyring is manually unlocked beforehand (e.g. via seahorse), 
the connection proceeds without hindrance.

  Anything that requires access to the Default Keyring within Lubuntu
  would be affected.

  This has been tested on Lubuntu 16.04 including a vanilla
  installation, on both PCManFM and Nautilus.

  Note that if Lubuntu is used by installing lubuntu-desktop over an
  Ubuntu 16.04 installation, this problem does not occur.

  Ubuntu Forums discussion:
  https://ubuntuforums.org/showthread.php?t=2367062

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnupg 1.4.20-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Jul 26 16:39:16 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-17 (38 days ago)
  InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnupg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1706701/+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 1881129] Re: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug

2020-11-22 Thread Chris Guiver
Thank you for reporting this bug to Ubuntu.

Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

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

Title:
  package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces
  post-removal script geïnstalleerd gaf een foutwaarde 1 terug

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  u

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  AptOrdering:
   lubuntu-desktop: Purge
   lubuntu-default-session: Purge
   lubuntu-core: Purge
   lubuntu-default-settings: Purge
   lightdm: Purge
  Architecture: i386
  Date: Thu May 28 13:54:09 2020
  DuplicateSignature: package:lightdm:1.10.6-0ubuntu1:subproces post-removal 
script geïnstalleerd gaf een foutwaarde 1 terug
  ErrorMessage: subproces post-removal script geïnstalleerd gaf een foutwaarde 
1 terug
  InstallationDate: Installed on 2014-09-27 (2069 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user=marleen
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen 
van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet
   
   ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen 
van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen 
van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet
   
   ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen 
van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.24
  SourcePackage: lightdm
  Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces 
post-removal script geïnstalleerd gaf een foutwaarde 1 terug
  UpgradeStatus: Upgraded to trusty on 2020-05-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1881129/+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 1427638] Re: Extra package box does not expand with its window, rendering its contents unreadable

2020-11-22 Thread Chris Guiver
Thank you for reporting this bug to Ubuntu.

Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: gdebi (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Extra package box does not expand with its window, rendering its
  contents unreadable

Status in gdebi package in Ubuntu:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 14.10 with lubuntu-desktop
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  0.9.5.4
  3) What you expected to happen
  Look at attached screenshot:
  Window containing focused string "libjpeg62:i386"  should be 
resizable/adjustable to display more than 1 string  (automatically? manually?)
  4) What happened instead
  It's not resizable automatically nor I'm able to resize it to display more 
than 1 string

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1427638/+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 1905228] [NEW] DIsplay Rotates to Portrait Mode when Certain Apps Open

2020-11-22 Thread Patrick Garraud
Public bug reported:

When using a 2 in 1 tablet with auto-rotation (Dell Precision 5530 2 in
1), the screen will frequently incorrectly rotate whenever some apps
open. This has been observed with Settings, Videos, Steam, Lollypop and
Firefox. Issue still occurs when the screen rotation is locked.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 22 22:59:56 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 630 [1028:08ac]
   Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
InstallationDate: Installed on 2020-11-18 (4 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5530 2-in-1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.10
dmi.board.name: 02TH5P
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrecision55302-in-1:pvr:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5530 2-in-1
dmi.product.sku: 08AC
dmi.sys.vendor: Dell Inc.
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

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


** Tags: amd64 apport-bug focal ubuntu wayland-session

-- 
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/1905228

Title:
  DIsplay Rotates to Portrait Mode when Certain Apps Open

Status in xorg package in Ubuntu:
  New

Bug description:
  When using a 2 in 1 tablet with auto-rotation (Dell Precision 5530 2
  in 1), the screen will frequently incorrectly rotate whenever some
  apps open. This has been observed with Settings, Videos, Steam,
  Lollypop and Firefox. Issue still occurs when the screen rotation is
  locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 22:59:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:08ac]
 Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
  InstallationDate: Installed on 2020-11-18 (4 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5530 2-in-1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: 

[Touch-packages] [Bug 1905199] Re: Computer crashing when exiting the lock screen after login, random admin authentication window stuck on the screen.

2020-11-22 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1824874 ***
https://bugs.launchpad.net/bugs/1824874

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1824874, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1824874
   undismissable, unclickable authentication dialog left on screen (top-left 
corner) after policykit authentication [pushModal: invocation of begin_modal 
failed]

-- 
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/1905199

Title:
  Computer crashing when exiting the lock screen after login, random
  admin authentication window stuck on the screen.

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  xorg:
Instalado: 1:7.7+19ubuntu14
Candidato: 1:7.7+19ubuntu14
Tabela de versão:
   *** 1:7.7+19ubuntu14 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Sometimes when I lock the screen or suspend the computer (I'm not sure
  if both or just lock) and after I log in to my user again, a window
  asking for the administrator password appears. This window is located
  in the upper left corner of the screen and is not clickable. I try to
  enter the password or cancel it but it is impossible, it is as if
  after the screen lock that window would get stuck ...

  Result: if I can use the computer normally, I cannot remove the
  window, which occupies a significant part of the screen. Sometimes the
  situation gets worse and everything starts to stall. In such cases, I
  can only move the mouse, without being able to interact. Everything is
  stuck and never comes back. I can only fix this problem by restarting
  the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 17:35:26 2020
  DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / 
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1043:0513]
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=b12510e7-1702-4d36-80bc-11251ef87185 ro quiet splash radeon.audio=1 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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/xorg/+bug/1905199/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1905076] Re: module-alsa-sink's "control" argument causes segmentation fault

2020-11-22 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

-- 
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/1905076

Title:
  module-alsa-sink's "control" argument causes segmentation fault

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Loading the pulseaudio module 'module-alsa-sink' with the "control"
  argument causes pulseaudio to segfault on my system.

  In /etc/pulse/default.pa find this line:

  #load-module module-alsa-sink

  and change it to this:

  load-module module-alsa-sink control=Master

  then restart pulseaudio by running these commands:

  pulseaudio -k
  pulseaudio --start

  Notice that it prints this into the terminal.
  E: [pulseaudio] main.c: Daemon startup failed.

  Try starting pulseaudio itself in the terminal, and you see what's happening:
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  Segmentation fault (core dumped)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-04-15 (219 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: pulseaudio 1:13.99.2-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  groovy
  Uname: Linux 5.4.0-54-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: 07/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1804
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905076/+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 1904924] Re: Xorg freeze

2020-11-22 Thread Daniel van Vugt
If you can move the mouse around then Xorg is definitely not frozen. It
sounds like only gnome-shell is frozen.

** Summary changed:

- Xorg freeze
+ Gnome Shell freeze

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Tags added: nvidia

** Summary changed:

- Gnome Shell freeze
+ [nvidia] Gnome Shell freeze

** Summary changed:

- [nvidia] Gnome Shell freeze
+ [nvidia] Gnome Shell freeze (page allocation failure in nvidia_modeset)

** Package changed: gnome-shell (Ubuntu) => nvidia-graphics-drivers-455
(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/1904924

Title:
  [nvidia] Gnome Shell freeze (page allocation failure in
  nvidia_modeset)

Status in nvidia-graphics-drivers-455 package in Ubuntu:
  New

Bug description:
  Sounds like a fairly common problem according to [this
  page](https://wiki.ubuntu.com/X/Troubleshooting/Freeze): my display
  freezes, and while I'm still able to move the mouse around, I can't
  successfully click or type at any windows. It takes about 30 seconds
  for gnome-shell to restart, and then the clock starts running (and the
  system monitor starts updating) again.

  This problem has been bugging me for a few months now, but I'm not
  sure when it started. It tends to happen in clumps; sometimes it will
  go several days without happening, but once it starts it often happens
  twice pretty quickly, and often a few times across a day. I haven't
  been able to isolate what causes it, but more often than not it has
  something to do with clicking on a window or tab in Chrome. (It
  definitely also happens in other applications, though.)

  Every time it happens, dmesg contains a stack dump for gnome-shell
  ("page allocation failure"). I can provide gists of these dumps if
  that's helpful (and not already included in the apport data). So I'm
  not sure if this is actually an xorg thing or a gnome-shell thing.

  % lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  % dpkg -l xorg* gnome-shell* | grep '^ii'
  ii  gnome-shell  3.38.1-1ubuntu1.1
  amd64graphical shell for the GNOME desktop
  ii  gnome-shell-common   3.38.1-1ubuntu1.1
  all  common files for the GNOME graphical shell
  ii  gnome-shell-extension-appindicator   34-1 
  all  AppIndicator/KStatusNotifierItem support for GNOME Shell
  ii  gnome-shell-extension-desktop-icons  20.04.0+git20200908-1
  all  desktop icon support for GNOME Shell
  ii  gnome-shell-extension-prefs  3.38.1-1ubuntu1.1
  amd64tool to enable / disable GNOME Shell extensions
  ii  gnome-shell-extension-system-monitor 38+git20200414-32cc79e-1 
  all  Display system information in GNOME Shell status bar
  ii  gnome-shell-extension-system76-power 
2.0.0~1602857239~20.10~914b531~dev all  Gnome-shell extension for 
System76 Power Management
  ii  gnome-shell-extension-ubuntu-dock68ubuntu20.10.1  
  all  Ubuntu Dock for GNOME Shell
  ii  gnome-shell-extensions   3.38.1-1 
  all  Extensions to extend functionality of GNOME Shell
  ii  xorg 1:7.7+19ubuntu15 
  amd64X.Org X Window System
  ii  xorg-docs-core   1:1.7.1-1.1  
  all  Core documentation for the X.org X Window System
  ii  xorg-sgml-doctools   1:1.11-1 
  all  Common tools for building X.Org SGML documentation

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 
5.8.0-7630.32~1605108806~20.10~7e52b13~dev-generic 5.8.17
  Uname: Linux 5.8.0-7630-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  455.38  Thu Oct 22 06:06:59 
UTC 2020
   GCC version:  gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1)
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: 

[Touch-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug

2020-11-22 Thread Daniel van Vugt
** Tags added: groovy

-- 
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/1877194

Title:
  switch-on-connect mistakes startup for USB hotplug

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  In short:
  1. Boot system
  2. "Analogue Output - RODE NT-USB" is selected by default. I want to use 
"Line Out - Built-in Audio", which I choose.
  3. Reboot.
  4 Output device is now back to "Analogue Output - RODE NT-USB".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1904903] Re: Pulseaudio always defaults to any external audio device connected when booting up

2020-11-22 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1877194 ***
https://bugs.launchpad.net/bugs/1877194

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1877194, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Tags added: groovy

** This bug has been marked a duplicate of bug 1877194
   switch-on-connect mistakes startup for USB hotplug

-- 
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/1904903

Title:
  Pulseaudio always defaults to any external audio device connected when
  booting up

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I am booting the computer up, it never sets the default output to
  the one I was using previously, which should be the norm. This is also
  the same for audio inputs. It works perfectly fine when connecting any
  new sound sources to the PC, which then pulseaudio sets the
  output/input to. But regarding it's state when booting up, it should
  stay on the last used audio device.

  1) Description:   Ubuntu 20.10
  Release:  20.10

  2) pulseaudio:
Instalado: 1:13.99.2-1ubuntu2
Candidato: 1:13.99.2-1ubuntu2
Tabela de versão:
   *** 1:13.99.2-1ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.2-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1904903/+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 1904902] Re: Pulseaudio produces a lot of crackling audio after awhile

2020-11-22 Thread Daniel van Vugt
Please report the issue to the developers at:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues

and then tell us the new issue ID.

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

-- 
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/1904902

Title:
  Pulseaudio produces a lot of crackling audio after awhile

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  1) Description:   Ubuntu 20.10
 Release: 20.10

  2) pulseaudio:
Instalado: 1:13.99.2-1ubuntu2
Candidato: 1:13.99.2-1ubuntu2
Tabela de versão:
   *** 1:13.99.2-1ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.2-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

  3) What you expected to happen: It shouldn't produce any crackles in the 
audio after a set amount of time.
  4) What happened instead: It starts to crackle with a very low volume, then 
it keeps increasing until it reaches the same volume as the music/audio. 
Running systemctl --user restart pulseaudio.service fixes the issue until the 
next restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov 19 14:09:37 2020
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2020-06-16 (156 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2202
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2202:bd07/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1904902/+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 1905078] Re: pavucontrol duplex profiles disappeared for SB Audigy after upgrading to Ubuntu 20.04

2020-11-22 Thread Daniel van Vugt
** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #750
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/750

** Also affects: pulseaudio via
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/750
   Importance: Unknown
   Status: Unknown

** Tags added: focal

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

** Tags added: fixed-in-13.99.2 fixed-upstream

** Also affects: pulseaudio (Ubuntu Hirsute)
   Importance: Undecided
   Status: Fix Committed

** Also affects: pulseaudio (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu Groovy)
   Status: New => Fix Released

** Changed in: pulseaudio (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

** Tags added: rls-ff-incoming

-- 
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/1905078

Title:
  pavucontrol duplex profiles disappeared for SB Audigy after upgrading
  to Ubuntu 20.04

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Released

Bug description:
  I just upgraded from Ubuntu 18 to 20 and analog stereo duplex profile
  is gone. The duplex profile was there and was working properly before.

  The following seems to be related:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/750

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1905078/+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-22 Thread Hui Wang
The Intel bluetooth firmware will be upgraded with this bug #1905214

-- 
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 1901901] Re: Lenovo Yoga Slim 7: Sound output device is not detected after upgrade from Ubuntu 20.04 to 20.10

2020-11-22 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu)
   Status: New => Fix Released

** Changed in: pulseaudio (Ubuntu)
   Status: Fix Released => Fix Committed

** Package changed: pulseaudio (Ubuntu) => alsa-lib (Ubuntu)

-- 
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/1901901

Title:
  Lenovo Yoga Slim 7: Sound output device is not detected after upgrade
  from Ubuntu 20.04 to 20.10

Status in alsa-lib package in Ubuntu:
  Fix Committed

Bug description:
  My output sound device "Lenovo Family 17h" worked well in Ubuntu 20.04.
  But when I upgraded to Ubuntu 20.10, I cannot hear any sound. The sound card 
is not detected, "System => Sound => Output Device" shows only "Dummy Output".
  I'm able to reproduce it even with live Ubuntu 20.10 from USB key.

  I checked that the issue happens in Ubuntu 20.10 with official kernel 5.8.0 
and even with 5.9.1. Note that in Ubuntu 20.04 it worked well with 5.4 and 5.8.x
  So it doesn't seem to be depend on used kernel.

  
---

  $ systemctl --user status pulseaudio.service 
  ● pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-10-28 14:25:34 CET; 25min ago
  TriggeredBy: ● pulseaudio.socket
 Main PID: 3002 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   └─3002 /usr/bin/pulseaudio --daemonize=no --log-target=journal

  Oct 28 14:25:34 yoga pulseaudio[3002]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" 
card_name="alsa_card.pci-_03_00.6>
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile.
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" 
card_name="alsa_card.pci-_03_00.6>
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile.
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" 
card_name="alsa_card.pci-_03_00.6>
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile.
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" 
card_name="alsa_card.pci-_03_00.6>
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile.
  Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" 
card_name="alsa_card.pci-_03_00.6>
  Oct 28 14:25:35 yoga pulseaudio[3002]: Tried to configure 
/devices/pci:00/:00:08.1/:03:00.6/sound/card1 
(alsa_card.pci-_03_00.6) more often than 5 time>

  
---

  When pulseaudio starts in verbose mode:

  $ pulseaudio -v
  ...
  I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC2D0c' failed (-16)
  I: [pulseaudio] alsa-util.c: Error opening PCM device hw:acp: Device or 
resource busy
  D: [pulseaudio] alsa-mixer.c: Profile set 0x558aa38b6670, auto_profiles=no, 
probed=yes, n_mappings=0, n_profiles=0, n_decibel_fixes=0
  E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
  E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: 
"device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes avoid_resampling=no 
card_properties="module-udev-detect.discovered=1""): initialization failed.
  I: [pulseaudio] module-udev-detect.c: Card 
/devices/pci:00/:00:08.1/:03:00.6/sound/card1 
(alsa_card.pci-_03_00.6) failed to load module.

  
---

  $ lspci -nnk | grep -A2 Audio
  03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device 
[1002:1637]
Subsystem: Lenovo Device [17aa:380d]
Kernel driver in use: snd_hda_intel
  --
  03:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01)
Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor 
[17aa:380d]
Kernel driver in use: snd_rn_pci_acp3x
Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x
  03:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 10h-1fh) HD Audio Controller [1022:15e3]
Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller 
[17aa:380d]
Kernel driver in use: snd_hda_intel
Kernel modules: 

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2020-11-22 Thread Mathew Hodson
** Bug watch added: Debian Bug tracker #972552
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972552

** Changed in: apt (Debian)
   Status: Fix Released => Unknown

** Changed in: apt (Debian)
 Remote watch: Debian Bug tracker #953260 => Debian Bug tracker #972552

** Bug watch removed: Debian Bug tracker #953260
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953260

** Bug watch removed: Sourceware.org Bugzilla #25652
   https://sourceware.org/bugzilla/show_bug.cgi?id=25652

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Triaged
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  Fix Committed
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  So what we do is change that to a warning.

  [Test case]
  Not available right now. Issues can flare up and then disappear again.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under 

[Touch-packages] [Bug 1905080] Re: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV

2020-11-22 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1905080

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

-- 
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/1905080

Title:
  After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI
  output disabled and doesn't turn on when I turn on the TV

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Before the upgrade the HDMI 4 digital stereo output was chosen
  automatically for my nvidia GF card and was usable by the players
  immediately after turning the TV on. After the upgrade I have to
  switch the profile from Disabled to HDMI4 each time I turn the TV on.
  It doesn't get stored properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905080/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2020-11-22 Thread Mathew Hodson
** No longer affects: glibc (Ubuntu)

** No longer affects: glibc (Ubuntu Bionic)

** No longer affects: glibc (Ubuntu Focal)

** Project changed: glibc => ubuntu-translations

** No longer affects: ubuntu-translations

** Changed in: apt (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: apt (Ubuntu Groovy)
   Importance: Undecided => Medium

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Triaged
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  Fix Committed
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  So what we do is change that to a warning.

  [Test case]
  Not available right now. Issues can flare up and then disappear again.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 

[Touch-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

2020-11-22 Thread Mathew Hodson
** No longer affects: bluez (Ubuntu)

** No longer affects: bluez (Ubuntu Focal)

** No longer affects: bluez (Ubuntu Hirsute)

** No longer affects: bluez (Ubuntu Groovy)

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed
Status in apport source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.

  [Test Case]
  On an Ubuntu desktop system perform the following step
  1) sudo pkill -11 upowerd

  With the current version of apport there will not be a crash file for
  upowerd in /var/crash/. With the version of apport in -proposed there
  will be a crash file for upowerd in /var/crash/.

  [Regression Potential]
  In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.

  [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+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 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

2020-11-22 Thread Mathew Hodson
** Changed in: wpa (Ubuntu Bionic)
   Importance: Undecided => High

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

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  One of the distro patch is incorrect and create issues when trying to query 
dbus properties

  * Test Case

  $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1
  /fi/w1/wpa_supplicant1/Interfaces/1
  org.freedesktop.DBus.Properties.GetAll
  string:fi.w1.wpa_supplicant1.Interface

  shouldn't error out

  (the /1 reflect the interface number and could be a different value,
  check with d-feet if needed)

  * Regression potential

  The fixes is in the dbus interface, check that communication with
  desktop clients (indicator, applet, settings) still works correctly,
  returning expected informations on the signal, etc

  -

  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc.
  The regression was introduced when someone try to have the Station attribute 
supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

2020-11-22 Thread Mathew Hodson
** Project changed: pulseaudio => alsa-lib

** Changed in: alsa-lib
   Importance: Unknown => Undecided

** Changed in: alsa-lib
   Status: Unknown => New

** Changed in: alsa-lib
 Remote watch: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1030 => 
None

** Changed in: alsa-lib
   Status: New => Fix Released

** Bug watch removed: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues 
#1030
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1030

-- 
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/1901922

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

Status in ALSA Libraries:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Released
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  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
  

[Touch-packages] [Bug 1905199] Re: Admin authentication crashing after exiting the lock screen

2020-11-22 Thread SepukkuHero
** Summary changed:

- Xorg freeze
+ Admin authentication crashing after exiting the lock screen

** Summary changed:

- Admin authentication crashing after exiting the lock screen
+ Computer crashing when exiting the lock screen after login, random admin 
authentication window stuck on the screen.

-- 
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/1905199

Title:
  Computer crashing when exiting the lock screen after login, random
  admin authentication window stuck on the screen.

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  xorg:
Instalado: 1:7.7+19ubuntu14
Candidato: 1:7.7+19ubuntu14
Tabela de versão:
   *** 1:7.7+19ubuntu14 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Sometimes when I lock the screen or suspend the computer (I'm not sure
  if both or just lock) and after I log in to my user again, a window
  asking for the administrator password appears. This window is located
  in the upper left corner of the screen and is not clickable. I try to
  enter the password or cancel it but it is impossible, it is as if
  after the screen lock that window would get stuck ...

  Result: if I can use the computer normally, I cannot remove the
  window, which occupies a significant part of the screen. Sometimes the
  situation gets worse and everything starts to stall. In such cases, I
  can only move the mouse, without being able to interact. Everything is
  stuck and never comes back. I can only fix this problem by restarting
  the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 17:35:26 2020
  DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / 
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1043:0513]
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=b12510e7-1702-4d36-80bc-11251ef87185 ro quiet splash radeon.audio=1 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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/xorg/+bug/1905199/+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 1905199] [NEW] Xorg freeze

2020-11-22 Thread SepukkuHero
Public bug reported:

Ubuntu 20.04.1 LTS

xorg:
  Instalado: 1:7.7+19ubuntu14
  Candidato: 1:7.7+19ubuntu14
  Tabela de versão:
 *** 1:7.7+19ubuntu14 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

Sometimes when I lock the screen or suspend the computer (I'm not sure
if both or just lock) and after I log in to my user again, a window
asking for the administrator password appears. This window is located in
the upper left corner of the screen and is not clickable. I try to enter
the password or cancel it but it is impossible, it is as if after the
screen lock that window would get stuck ...

Result: if I can use the computer normally, I cannot remove the window,
which occupies a significant part of the screen. Sometimes the situation
gets worse and everything starts to stall. In such cases, I can only
move the mouse, without being able to interact. Everything is stuck and
never comes back. I can only fix this problem by restarting the
computer.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 22 17:35:26 2020
DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Once a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: I don't know
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1043:0513]
InstallationDate: Installed on 2020-07-24 (121 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=b12510e7-1702-4d36-80bc-11251ef87185 ro quiet splash radeon.audio=1 
vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
dmi.bios.date: 11/25/2014
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-78LMT-USB3 6.0
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: SEx
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-78LMT-USB3 6.0
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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

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


** Tags: amd64 apport-bug focal freeze ubuntu

** Attachment added: "Captura de tela de 2020-11-22 17-45-42.png"
   
https://bugs.launchpad.net/bugs/1905199/+attachment/5437014/+files/Captura%20de%20tela%20de%202020-11-22%2017-45-42.png

-- 
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/1905199

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  xorg:
Instalado: 1:7.7+19ubuntu14
Candidato: 1:7.7+19ubuntu14
Tabela de versão:
   *** 1:7.7+19ubuntu14 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Sometimes when I lock the screen or suspend the computer (I'm not sure
  if both or just lock) and after I log in to my user again, a window
  asking for the administrator password appears. This window is located
  in the upper left corner of the screen and is not clickable. I try to
  enter the password or cancel it but it is impossible, it is as if
  after the screen lock that window would get stuck ...

  Result: if I can use the computer normally, I cannot remove the
  window, which occupies a significant part of the screen. Sometimes the
  situation gets worse and everything starts to stall. In such cases, I
  can only move 

[Touch-packages] [Bug 1905194] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2020-11-22 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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1905194

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading from 18.04 to 20.04 (LTS)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 4.15.0-125.128-generic 4.15.18
  Uname: Linux 4.15.0-125-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 12:04:13 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-08-20 (1190 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools 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/initramfs-tools/+bug/1905194/+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 1905194] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2020-11-22 Thread Lucien SAMUEL
Upgrading from 18.04 to 20.04 (LTS)

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading from 18.04 to 20.04 (LTS)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 4.15.0-125.128-generic 4.15.18
  Uname: Linux 4.15.0-125-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 12:04:13 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-08-20 (1190 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools 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/initramfs-tools/+bug/1905194/+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 1905194] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2020-11-22 Thread Lucien SAMUEL
Upgrading from 18.04 to 20.04 (LTS)

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading from 18.04 to 20.04 (LTS)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 4.15.0-125.128-generic 4.15.18
  Uname: Linux 4.15.0-125-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 12:04:13 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-08-20 (1190 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools 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/initramfs-tools/+bug/1905194/+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 1905194] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

2020-11-22 Thread Lucien SAMUEL
Public bug reported:

Upgrading from 18.04 to 20.04 (LTS)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.3
ProcVersionSignature: Ubuntu 4.15.0-125.128-generic 4.15.18
Uname: Linux 4.15.0-125-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Nov 22 12:04:13 2020
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2017-08-20 (1190 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading from 18.04 to 20.04 (LTS)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 4.15.0-125.128-generic 4.15.18
  Uname: Linux 4.15.0-125-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 12:04:13 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-08-20 (1190 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools 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/initramfs-tools/+bug/1905194/+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 1905184] Re: No video signal during Ubuntu splash screen and also during Logon procedure

2020-11-22 Thread Agostinho Carvalho
** Description changed:

  Hello.
  
  I don't have any video during Ubuntu splash screen and also during the logon 
procedure.
  I only have video in GRUB and after the logon operation takes place.
  After I type in my password (in blind mode), Ubuntu will then start normally 
with correct video settings (resolution, etc...).
  
  To workaround this error, I can either:
- Workaround 1) Enable automatic login. That way the system doesn't get stuck 
in login screen and Ubuntu loads immediately.
- Problem: However, I don't want this because I'm in a multi-user scenario.
+ 
+ Workaround 1) Enable automatic login. That way the system doesn't get stuck 
in logon screen and Ubuntu loads immediately.
+ Problem: Boot splash won't be displayed anyway and I don't want this because 
I'm in a multi-user scenario.
+ 
  
  Workaround 2) Add a kernel boot option "nomodeset" in /etc/default/grub
  When I do this I will always get video signal.
  Problem: The computer is an ECS Hybrid Device (tablet+detachable keyboard), 
and when I use this workaround, user session loads in Portrait mode (not 
Landscape) and there is no auto-rotation support.
+ 
+ 
+ Workaround 3) Although I don't have video signal during Boot Splash and Logon 
screen, I do have backlight continuously applied to the display.
+ If I wait 5 minutes or so in the logon screen the backlight will deactivate...
+ However, when I touch the keyboard or touchpad the computer will then show 
video signal and I will be able to see the logon screen perfectly.
+ 
  
  Computer is this one:
  
https://www.ecs.com.tw/ECSWebSite/Product/Product_Overview/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC
  
  Specs are here:
  
https://www.ecs.com.tw/ECSWebSite/Product/Product_SPEC/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC
  
  Feel free to request any extra information.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Nov 22 19:56:20 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2020-11-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ECS CMPC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=2e7d6b98-86c2-4579-bd7f-fa31664333f6 ro quiet video=efifb 
fbcon=rotate:1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02.00.STD
  dmi.board.asset.tag: Default string
  dmi.board.name: ik Educational Software
  dmi.board.vendor: ECS
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 30
  dmi.chassis.vendor: NULL
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02.00.STD:bd10/15/2019:svnECS:pnCMPC:pvrDefaultstring:rvnECS:rnikEducationalSoftware:rvrDefaultstring:cvnNULL:ct30:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: CMPC
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: ECS
  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.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-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

** Description changed:

  Hello.
  
  I don't have any video during Ubuntu splash screen and also during the logon 
procedure.
  I only have video in GRUB and after the logon operation takes place.
  After I type in my password (in blind mode), Ubuntu will then start normally 
with correct video settings (resolution, etc...).
  
  To workaround this error, I can either:
  
  Workaround 1) Enable automatic login. That way the system doesn't get stuck 
in logon screen and Ubuntu loads immediately.
  Problem: Boot splash won't be displayed anyway and I don't want this because 
I'm in a multi-user scenario.
  
- 
  Workaround 2) Add a kernel boot option "nomodeset" in /etc/default/grub
  When I do this I will always get video signal.
  Problem: The computer is an ECS Hybrid Device (tablet+detachable keyboard), 
and when I use this workaround, user session loads in Portrait mode (not 
Landscape) and 

[Touch-packages] [Bug 1905185] [NEW] [20UJ0014IX, Realtek ALC257, Speaker, Internal] Pulseaudio fails to detect card

2020-11-22 Thread Romano
Public bug reported:

good evening, I have a problem with internal microphone, sometimes it works and 
sometimes it doesn't, it happens randomly, just a restart
my pc should be Ubuntu certified

thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  roxibar73   1518 F pulseaudio
 /dev/snd/controlC0:  roxibar73   1518 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 22 18:32:04 2020
InstallationDate: Installed on 2020-11-20 (1 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HD-Audio Generic
Symptom_Jack: Speaker, Internal
Title: [20UJ0014IX, Realtek ALC257, Speaker, Internal] Pulseaudio fails to 
detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2020
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: R1CET56W(1.25 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UJ0014IX
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.25
dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET56W(1.25):bd09/15/2020:br1.25:efr1.25:svnLENOVO:pn20UJ0014IX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UJ0014IX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T14s Gen 1
dmi.product.name: 20UJ0014IX
dmi.product.sku: LENOVO_MT_20UJ_BU_Think_FM_ThinkPad T14s Gen 1
dmi.product.version: ThinkPad T14s Gen 1
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug groovy

-- 
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/1905185

Title:
  [20UJ0014IX, Realtek ALC257, Speaker, Internal] Pulseaudio fails to
  detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  good evening, I have a problem with internal microphone, sometimes it works 
and sometimes it doesn't, it happens randomly, just a restart
  my pc should be Ubuntu certified

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  roxibar73   1518 F pulseaudio
   /dev/snd/controlC0:  roxibar73   1518 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 18:32:04 2020
  InstallationDate: Installed on 2020-11-20 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HD-Audio Generic
  Symptom_Jack: Speaker, Internal
  Title: [20UJ0014IX, Realtek ALC257, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2020
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET56W(1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UJ0014IX
  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.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET56W(1.25):bd09/15/2020:br1.25:efr1.25:svnLENOVO:pn20UJ0014IX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UJ0014IX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14s Gen 1
  dmi.product.name: 20UJ0014IX
  dmi.product.sku: LENOVO_MT_20UJ_BU_Think_FM_ThinkPad T14s Gen 1
  dmi.product.version: ThinkPad T14s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905185/+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 1905184] [NEW] No video signal during Ubuntu splash screen and also during Logon procedure

2020-11-22 Thread Agostinho Carvalho
Public bug reported:

Hello.

I don't have any video during Ubuntu splash screen and also during the logon 
procedure.
I only have video in GRUB and after the logon operation takes place.
After I type in my password (in blind mode), Ubuntu will then start normally 
with correct video settings (resolution, etc...).

To workaround this error, I can either:
Workaround 1) Enable automatic login. That way the system doesn't get stuck in 
login screen and Ubuntu loads immediately.
Problem: However, I don't want this because I'm in a multi-user scenario.

Workaround 2) Add a kernel boot option "nomodeset" in /etc/default/grub
When I do this I will always get video signal.
Problem: The computer is an ECS Hybrid Device (tablet+detachable keyboard), and 
when I use this workaround, user session loads in Portrait mode (not Landscape) 
and there is no auto-rotation support.

Computer is this one:
https://www.ecs.com.tw/ECSWebSite/Product/Product_Overview/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC

Specs are here:
https://www.ecs.com.tw/ECSWebSite/Product/Product_SPEC/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC

Feel free to request any extra information.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Sun Nov 22 19:56:20 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 
00 [VGA controller])
InstallationDate: Installed on 2020-11-22 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: ECS CMPC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=2e7d6b98-86c2-4579-bd7f-fa31664333f6 ro quiet video=efifb 
fbcon=rotate:1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.02.00.STD
dmi.board.asset.tag: Default string
dmi.board.name: ik Educational Software
dmi.board.vendor: ECS
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 30
dmi.chassis.vendor: NULL
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02.00.STD:bd10/15/2019:svnECS:pnCMPC:pvrDefaultstring:rvnECS:rnikEducationalSoftware:rvrDefaultstring:cvnNULL:ct30:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: CMPC
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: ECS
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.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-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

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


** Tags: amd64 apport-bug focal 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/1905184

Title:
  No video signal during Ubuntu splash screen and also during Logon
  procedure

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello.

  I don't have any video during Ubuntu splash screen and also during the logon 
procedure.
  I only have video in GRUB and after the logon operation takes place.
  After I type in my password (in blind mode), Ubuntu will then start normally 
with correct video settings (resolution, etc...).

  To workaround this error, I can either:
  Workaround 1) Enable automatic login. That way the system doesn't get stuck 
in login screen and Ubuntu loads immediately.
  Problem: However, I don't want this because I'm in a multi-user scenario.

  Workaround 2) Add a kernel boot option "nomodeset" in /etc/default/grub
  When I do this I will always get video signal.
  Problem: The computer is an ECS Hybrid Device (tablet+detachable keyboard), 
and when I use this workaround, user session loads in Portrait mode (not 
Landscape) and there is no auto-rotation support.

  Computer is this one:
  
https://www.ecs.com.tw/ECSWebSite/Product/Product_Overview/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC

  Specs are here:
  
https://www.ecs.com.tw/ECSWebSite/Product/Product_SPEC/EN/Tablet%20PC/TH10GM2/10-inch%20Tablet%20PC

  Feel free to request any extra information.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 

[Touch-packages] [Bug 1905183] [NEW] [Mi Laptop Pro 15, Realtek ALC256, Speaker, Internal] fails after a while

2020-11-22 Thread Yuriy Padlyak
Public bug reported:

sound dissapears after suspend, restored only after reboot

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
Uname: Linux 5.8.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  yuriy  2155 F pulseaudio
 /dev/snd/pcmC0D0p:   yuriy  2155 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 22 19:13:54 2020
InstallationDate: Installed on 2017-10-07 (1142 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Вбудоване аудіо - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 лис 21 21:31:17 yurko-laptop systemd[1517]: Not generating service for XDG 
autostart app-pulseaudio-autostart.service, startup phases are not supported.
 лис 21 21:31:17 yurko-laptop dbus-daemon[1066]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.33' (uid=121 pid=1519 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
 лис 21 21:31:30 yurko-laptop systemd[1509]: pulseaudio.service: Succeeded.
 лис 21 21:31:41 yurko-laptop systemd[1509]: pulseaudio.socket: Succeeded.
Symptom_Type: Sound works for a while, then breaks
Title: [Mi Laptop Pro 15, Realtek ALC256, Speaker, Internal] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2020
dmi.bios.release: 1.4
dmi.bios.vendor: TIMI
dmi.bios.version: XMACM500P0401
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: TM1905
dmi.board.vendor: TIMI
dmi.board.version: AX23XXAXE
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TIMI
dmi.ec.firmware.release: 1.1
dmi.modalias: 
dmi:bvnTIMI:bvrXMACM500P0401:bd08/18/2020:br1.4:efr1.1:svnTIMI:pnMiLaptopPro15:pvr:rvnTIMI:rnTM1905:rvrAX23XXAXE:cvnTIMI:ct10:cvr:
dmi.product.family: Mi Laptop
dmi.product.name: Mi Laptop Pro 15
dmi.product.sku: TM1905-25887
dmi.sys.vendor: TIMI

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


** Tags: amd64 apport-bug groovy

-- 
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/1905183

Title:
  [Mi Laptop Pro 15, Realtek ALC256, Speaker, Internal] fails after a
  while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  sound dissapears after suspend, restored only after reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yuriy  2155 F pulseaudio
   /dev/snd/pcmC0D0p:   yuriy  2155 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 19:13:54 2020
  InstallationDate: Installed on 2017-10-07 (1142 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Вбудоване аудіо - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   лис 21 21:31:17 yurko-laptop systemd[1517]: Not generating service for XDG 
autostart app-pulseaudio-autostart.service, startup phases are not supported.
   лис 21 21:31:17 yurko-laptop dbus-daemon[1066]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.33' (uid=121 pid=1519 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
   лис 21 21:31:30 yurko-laptop systemd[1509]: pulseaudio.service: Succeeded.
   лис 21 21:31:41 yurko-laptop systemd[1509]: pulseaudio.socket: Succeeded.
  Symptom_Type: Sound works for a while, then breaks
  Title: [Mi Laptop Pro 15, Realtek ALC256, Speaker, Internal] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: TIMI
  dmi.bios.version: XMACM500P0401
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: TM1905
  dmi.board.vendor: TIMI
  dmi.board.version: AX23XXAXE
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnTIMI:bvrXMACM500P0401:bd08/18/2020:br1.4:efr1.1:svnTIMI:pnMiLaptopPro15:pvr:rvnTIMI:rnTM1905:rvrAX23XXAXE:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: Mi Laptop Pro 15
  dmi.product.sku: TM1905-25887
  dmi.sys.vendor: 

[Touch-packages] [Bug 1905175] Re: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2020-11-22 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: fsys-tarfile-error

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

-- 
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/1905175

Title:
  package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade:
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  package upgrade failed

  ProblemType: Package
  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 10:07:04 2020
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2020-09-29 (53 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 10.1.10.11 dev wlp8s0 proto dhcp metric 600 
   10.1.0.0/20 dev wlp8s0 proto kernel scope link src 10.1.2.25 metric 600 
   169.254.0.0/16 dev wlp8s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: network-manager
  Title: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  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/1905175/+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 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied

2020-11-22 Thread LyckeleB
I had two problems : 
   1) no PID-file created and
   2) I couldn't assign a NIC to "isc-dhcp-server"aka "dhcpd".

It turned out that the PID-file has to be "/var/run/dhcp-
server/dhcpd.pid". If not, apparmor wouldn't allow the creation of the
PID-file.

And the the file defining the originally installed dhcpd-service script 
("/usr/lib/systemd/system/isc-dhcp-server.service") is having other erroneous 
fixed paths.
 
Solution
-
So I copied "/usr/lib/systemd/system/isc-dhcp-server.service" to 
"/etc/systemd/system/" and modified it into the one shown below. This solved my 
problems.

[Unit]
Description=ISC DHCP IPv4 server
Documentation=man:dhcpd(8)
Wants=network-online.target
After=network-online.target
After=time-sync.target
ConditionPathExists=/etc/default/isc-dhcp-server
ConditionPathExists=|/etc/ltsp/dhcpd.conf
ConditionPathExists=|/etc/dhcp/dhcpd.conf

[Service]
EnvironmentFile=/etc/default/isc-dhcp-server
RuntimeDirectory=dhcp-server
# The leases files need to be root:dhcpd even when dropping privileges
ExecStart=/bin/sh -ec '\
CONFIG_FILE=/etc/dhcp/dhcpd.conf; \
if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi; \
if [ ! -d /var/run/dhcp-server ]; then mkdir -p /var/run/dhcp-server ; 
chown dhcpd:dhcpd /var/run/dhcp-server ; chmod u=rwx,go=rx /var/run/dhcp-server 
; fi; \
if [ ! "$DHCPDv4_PID" ] ; then DHCPDv4_PID=/var/run/dhcp-server/dhcpd.pid; 
fi; \
[ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \
chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \
chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \
exec dhcpd -user dhcpd -group dhcpd -f -4 -pf $DHCPDv4_PID -cf $CONFIG_FILE 
$INTERFACESv4'

[Install]
WantedBy=multi-user.target

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

Title:
  isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid:
  Permission denied

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 14-10 to 15-04, and now see the following in
  syslog:

  Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 
audit(1430045408.725:8): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1  capname="dac_ove
  rride"
  Apr 26 10:50:08 server sh[8619]: Can't create PID file 
/run/dhcp-server/dhcpd.pid: Permission denied.

  Description:Ubuntu 15.04
  Release:15.04

  isc-dhcp-server:
Installed: 4.3.1-5ubuntu2

  --- 8x -

  # cat /etc/default/isc-dhcp-server

  # Defaults for isc-dhcp-server initscript
  # sourced by /etc/init.d/isc-dhcp-server
  # installed at /etc/default/isc-dhcp-server by the maintainer scripts

  #
  # This is a POSIX shell fragment
  #

  # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
  #DHCPD_CONF=/etc/dhcp/dhcpd.conf

  # Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
  #DHCPD_PID=/var/run/dhcpd.pid

  # Additional options to start dhcpd with.
  #   Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
  #OPTIONS=""

  # On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
  #   Separate multiple interfaces with spaces, e.g. "eth0 eth1".
  INTERFACES=""

  --- 8x -

  # ls -la /var/run
  lrwxrwxrwx 1 root root 4 Oct 24  2013 /var/run -> /run

  # ls -la /run/dhcp-server/
  total 0
  drwxr-xr-x  2 dhcpd dhcpd   40 Apr 26 10:59 .
  drwxr-xr-x 34 root  root  1060 Apr 26 11:33 ..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+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 1905175] Re: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2020-11-22 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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1905175

Title:
  package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade:
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2

Status in network-manager package in Ubuntu:
  New

Bug description:
  package upgrade failed

  ProblemType: Package
  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 10:07:04 2020
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2020-09-29 (53 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 10.1.10.11 dev wlp8s0 proto dhcp metric 600 
   10.1.0.0/20 dev wlp8s0 proto kernel scope link src 10.1.2.25 metric 600 
   169.254.0.0/16 dev wlp8s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: network-manager
  Title: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  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/1905175/+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 1905175] [NEW] package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2020-11-22 Thread Randy Fry
Public bug reported:

package upgrade failed

ProblemType: Package
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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Nov 22 10:07:04 2020
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
InstallationDate: Installed on 2020-09-29 (53 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
 default via 10.1.10.11 dev wlp8s0 proto dhcp metric 600 
 10.1.0.0/20 dev wlp8s0 proto kernel scope link src 10.1.2.25 metric 600 
 169.254.0.0/16 dev wlp8s0 scope link metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: network-manager
Title: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
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-package focal need-duplicate-check

-- 
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/1905175

Title:
  package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade:
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2

Status in network-manager package in Ubuntu:
  New

Bug description:
  package upgrade failed

  ProblemType: Package
  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 10:07:04 2020
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2020-09-29 (53 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 10.1.10.11 dev wlp8s0 proto dhcp metric 600 
   10.1.0.0/20 dev wlp8s0 proto kernel scope link src 10.1.2.25 metric 600 
   169.254.0.0/16 dev wlp8s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: network-manager
  Title: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  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/1905175/+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 1905027] PulseList.txt

2020-11-22 Thread Pedot
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1905027/+attachment/5436885/+files/PulseList.txt

-- 
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/1905027

Title:
  Need to force alsa to reload after reboot to have sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version.

  I need to reload at each reboot alsa with:

  sudo alsa force-reload

  The workaround proposed here work for me.
  https://askubuntu.com/a/1281216/772996

  alsa seems to kill timidity (?)

  This solves it:
  systemctl disable timidity

  
  I didn't find an issue for this bug. Feel free to remove if needed.

  
  Thanks !


  apt-cache policy alsa gives me empty:
  alsa:
Installé : (aucun)
Candidat : (aucun)
   Table de version :
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thomas 1961 F pulseaudio
   /dev/snd/controlC0:  thomas 1961 F pulseaudio
   /dev/snd/pcmC0D0p:   thomas 1961 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-29 (1058 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-17 (4 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H170M-HD3 DDR3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH170M-HD3DDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-02-04T11:58:08.087306

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1905027/+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 1905027] ProcEnviron.txt

2020-11-22 Thread Pedot
apport information

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

-- 
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/1905027

Title:
  Need to force alsa to reload after reboot to have sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version.

  I need to reload at each reboot alsa with:

  sudo alsa force-reload

  The workaround proposed here work for me.
  https://askubuntu.com/a/1281216/772996

  alsa seems to kill timidity (?)

  This solves it:
  systemctl disable timidity

  
  I didn't find an issue for this bug. Feel free to remove if needed.

  
  Thanks !


  apt-cache policy alsa gives me empty:
  alsa:
Installé : (aucun)
Candidat : (aucun)
   Table de version :
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thomas 1961 F pulseaudio
   /dev/snd/controlC0:  thomas 1961 F pulseaudio
   /dev/snd/pcmC0D0p:   thomas 1961 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-29 (1058 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-17 (4 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H170M-HD3 DDR3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH170M-HD3DDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-02-04T11:58:08.087306

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1905027/+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 1905027] ProcCpuinfoMinimal.txt

2020-11-22 Thread Pedot
apport information

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

-- 
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/1905027

Title:
  Need to force alsa to reload after reboot to have sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version.

  I need to reload at each reboot alsa with:

  sudo alsa force-reload

  The workaround proposed here work for me.
  https://askubuntu.com/a/1281216/772996

  alsa seems to kill timidity (?)

  This solves it:
  systemctl disable timidity

  
  I didn't find an issue for this bug. Feel free to remove if needed.

  
  Thanks !


  apt-cache policy alsa gives me empty:
  alsa:
Installé : (aucun)
Candidat : (aucun)
   Table de version :
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thomas 1961 F pulseaudio
   /dev/snd/controlC0:  thomas 1961 F pulseaudio
   /dev/snd/pcmC0D0p:   thomas 1961 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-29 (1058 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-17 (4 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H170M-HD3 DDR3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH170M-HD3DDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-02-04T11:58:08.087306

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1905027/+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 1905027] CurrentDmesg.txt

2020-11-22 Thread Pedot
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1905027/+attachment/5436882/+files/CurrentDmesg.txt

-- 
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/1905027

Title:
  Need to force alsa to reload after reboot to have sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version.

  I need to reload at each reboot alsa with:

  sudo alsa force-reload

  The workaround proposed here work for me.
  https://askubuntu.com/a/1281216/772996

  alsa seems to kill timidity (?)

  This solves it:
  systemctl disable timidity

  
  I didn't find an issue for this bug. Feel free to remove if needed.

  
  Thanks !


  apt-cache policy alsa gives me empty:
  alsa:
Installé : (aucun)
Candidat : (aucun)
   Table de version :
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thomas 1961 F pulseaudio
   /dev/snd/controlC0:  thomas 1961 F pulseaudio
   /dev/snd/pcmC0D0p:   thomas 1961 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-29 (1058 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-17 (4 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H170M-HD3 DDR3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH170M-HD3DDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-02-04T11:58:08.087306

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1905027/+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 1905027] Re: Need to force alsa to reload after reboot to have sound

2020-11-22 Thread Pedot
apport information

** Tags added: apport-collected focal

** Description changed:

  Hello,
  I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version.
  
  I need to reload at each reboot alsa with:
  
  sudo alsa force-reload
  
  The workaround proposed here work for me.
  https://askubuntu.com/a/1281216/772996
  
  alsa seems to kill timidity (?)
  
  This solves it:
  systemctl disable timidity
  
  
  I didn't find an issue for this bug. Feel free to remove if needed.
  
  
  Thanks !
  
  
  apt-cache policy alsa gives me empty:
  alsa:
Installé : (aucun)
Candidat : (aucun)
   Table de version :
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.12
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  thomas 1961 F pulseaudio
+  /dev/snd/controlC0:  thomas 1961 F pulseaudio
+  /dev/snd/pcmC0D0p:   thomas 1961 F...m pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2017-12-29 (1058 days ago)
+ InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: alsa-driver (not installed)
+ ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
+ Tags:  focal
+ Uname: Linux 5.4.0-54-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-11-17 (4 days ago)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/27/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F2
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: H170M-HD3 DDR3-CF
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: x.x
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH170M-HD3DDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: To be filled by O.E.M.
+ dmi.product.sku: To be filled by O.E.M.
+ dmi.product.version: To be filled by O.E.M.
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.
+ modified.conffile..etc.default.apport:
+  # set this to 0 to disable apport, or to 1 to enable it
+  # you can temporarily override this with
+  # sudo service apport start force_start=1
+  enabled=0
+ mtime.conffile..etc.default.apport: 2018-02-04T11:58:08.087306

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1905027/+attachment/5436881/+files/AlsaInfo.txt

-- 
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/1905027

Title:
  Need to force alsa to reload after reboot to have sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version.

  I need to reload at each reboot alsa with:

  sudo alsa force-reload

  The workaround proposed here work for me.
  https://askubuntu.com/a/1281216/772996

  alsa seems to kill timidity (?)

  This solves it:
  systemctl disable timidity

  
  I didn't find an issue for this bug. Feel free to remove if needed.

  
  Thanks !


  apt-cache policy alsa gives me empty:
  alsa:
Installé : (aucun)
Candidat : (aucun)
   Table de version :
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thomas 1961 F pulseaudio
   /dev/snd/controlC0:  thomas 1961 F pulseaudio
   /dev/snd/pcmC0D0p:   thomas 1961 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-12-29 (1058 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-17 (4 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H170M-HD3 DDR3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Touch-packages] [Bug 1905139] PulseList.txt

2020-11-22 Thread Niccolò
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1905139/+attachment/5436850/+files/PulseList.txt

-- 
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/1905139

Title:
  HP pavilion cw1010nl - audio noise

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi, i've encountered an audio problem after the installation of KDE
  Neon in my laptop (HP pavilion cw1010nl). I hear a constant noise that
  is not showed in pavucontrol and even when all the audio peripherals
  are disabled. When i use windows 10 this problem does not occur. I
  cannot say in what package i found the bug but i use alsa and
  pulseaudio. Guide me if you need other informations for better
  understanding the problem.

  Kernel version: 5.9.8
  Audio driver in use: snd_hda_intel
  Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) 
HD Audio Controller

  $ aplay --list-devices
   List of PLAYBACK Hardware Devices 
  card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: Generic_1 [HD-Audio Generic], device 0: ALC295 Analog [ALC295 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  $ lsb_release -rd
  Description:KDE neon User Edition 5.20
  Release:20.04

  $ apt-cache policy alsa-base
  alsa-base:
Installato: 1.0.25+dfsg-0ubuntu5
Candidato:  1.0.25+dfsg-0ubuntu5
Tabella versione:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  niccolo3779 F pulseaudio
   /dev/snd/controlC0:  niccolo3779 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: KDE neon 20.04
  InstallationDate: Installed on 2020-11-18 (4 days ago)
  InstallationMedia: neon user "Focal" - Build amd64 LIVE Binary 20201112-12:05
  Package: alsa-driver (not installed)
  Tags:  focal
  Uname: Linux 5.9.8-050908-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/24/2019
  dmi.bios.release: 15.35
  dmi.bios.vendor: AMI
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8615
  dmi.board.vendor: HP
  dmi.board.version: 46.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 46.23
  dmi.modalias: 
dmi:bvnAMI:bvrF.35:bd09/24/2019:br15.35:efr46.23:svnHP:pnHPPavilionLaptop15-cw1xxx:pvr:rvnHP:rn8615:rvr46.23:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cw1xxx
  dmi.product.sku: 6LH22EA#ABZ
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1905139/+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 1905139] ProcEnviron.txt

2020-11-22 Thread Niccolò
apport information

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

-- 
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/1905139

Title:
  HP pavilion cw1010nl - audio noise

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi, i've encountered an audio problem after the installation of KDE
  Neon in my laptop (HP pavilion cw1010nl). I hear a constant noise that
  is not showed in pavucontrol and even when all the audio peripherals
  are disabled. When i use windows 10 this problem does not occur. I
  cannot say in what package i found the bug but i use alsa and
  pulseaudio. Guide me if you need other informations for better
  understanding the problem.

  Kernel version: 5.9.8
  Audio driver in use: snd_hda_intel
  Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) 
HD Audio Controller

  $ aplay --list-devices
   List of PLAYBACK Hardware Devices 
  card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: Generic_1 [HD-Audio Generic], device 0: ALC295 Analog [ALC295 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  $ lsb_release -rd
  Description:KDE neon User Edition 5.20
  Release:20.04

  $ apt-cache policy alsa-base
  alsa-base:
Installato: 1.0.25+dfsg-0ubuntu5
Candidato:  1.0.25+dfsg-0ubuntu5
Tabella versione:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  niccolo3779 F pulseaudio
   /dev/snd/controlC0:  niccolo3779 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: KDE neon 20.04
  InstallationDate: Installed on 2020-11-18 (4 days ago)
  InstallationMedia: neon user "Focal" - Build amd64 LIVE Binary 20201112-12:05
  Package: alsa-driver (not installed)
  Tags:  focal
  Uname: Linux 5.9.8-050908-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/24/2019
  dmi.bios.release: 15.35
  dmi.bios.vendor: AMI
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8615
  dmi.board.vendor: HP
  dmi.board.version: 46.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 46.23
  dmi.modalias: 
dmi:bvnAMI:bvrF.35:bd09/24/2019:br15.35:efr46.23:svnHP:pnHPPavilionLaptop15-cw1xxx:pvr:rvnHP:rn8615:rvr46.23:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cw1xxx
  dmi.product.sku: 6LH22EA#ABZ
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1905139/+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 1905139] ProcCpuinfoMinimal.txt

2020-11-22 Thread Niccolò
apport information

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

-- 
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/1905139

Title:
  HP pavilion cw1010nl - audio noise

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi, i've encountered an audio problem after the installation of KDE
  Neon in my laptop (HP pavilion cw1010nl). I hear a constant noise that
  is not showed in pavucontrol and even when all the audio peripherals
  are disabled. When i use windows 10 this problem does not occur. I
  cannot say in what package i found the bug but i use alsa and
  pulseaudio. Guide me if you need other informations for better
  understanding the problem.

  Kernel version: 5.9.8
  Audio driver in use: snd_hda_intel
  Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) 
HD Audio Controller

  $ aplay --list-devices
   List of PLAYBACK Hardware Devices 
  card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: Generic_1 [HD-Audio Generic], device 0: ALC295 Analog [ALC295 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  $ lsb_release -rd
  Description:KDE neon User Edition 5.20
  Release:20.04

  $ apt-cache policy alsa-base
  alsa-base:
Installato: 1.0.25+dfsg-0ubuntu5
Candidato:  1.0.25+dfsg-0ubuntu5
Tabella versione:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  niccolo3779 F pulseaudio
   /dev/snd/controlC0:  niccolo3779 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: KDE neon 20.04
  InstallationDate: Installed on 2020-11-18 (4 days ago)
  InstallationMedia: neon user "Focal" - Build amd64 LIVE Binary 20201112-12:05
  Package: alsa-driver (not installed)
  Tags:  focal
  Uname: Linux 5.9.8-050908-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/24/2019
  dmi.bios.release: 15.35
  dmi.bios.vendor: AMI
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8615
  dmi.board.vendor: HP
  dmi.board.version: 46.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 46.23
  dmi.modalias: 
dmi:bvnAMI:bvrF.35:bd09/24/2019:br15.35:efr46.23:svnHP:pnHPPavilionLaptop15-cw1xxx:pvr:rvnHP:rn8615:rvr46.23:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cw1xxx
  dmi.product.sku: 6LH22EA#ABZ
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1905139/+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 1905167] Re: htop shows 100% usage of systemd-udevd

2020-11-22 Thread Lyubomir
** Attachment added: "udev.perf"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905167/+attachment/5436868/+files/udev.perf

-- 
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/1905167

Title:
  htop shows 100% usage of systemd-udevd

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm attaching a perf profile.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65
  Uname: Linux 5.4.0-54-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 13:57:47 2020
  InstallationDate: Installed on 2020-02-08 (287 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Aspire A515-51G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash 
resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality 
intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/dnscrypt-proxy.service → 
/etc/systemd/system/dnscrypt-proxy.service.d/override.conf
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742
  mtime.conffile..etc.systemd.sleep.conf: 2020-09-26T18:33:31.018002

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905167/+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 1905139] Re: HP pavilion cw1010nl - audio noise

2020-11-22 Thread Niccolò
apport information

** Tags added: apport-collected focal

** Description changed:

  Hi, i've encountered an audio problem after the installation of KDE Neon
  in my laptop (HP pavilion cw1010nl). I hear a constant noise that is not
  showed in pavucontrol and even when all the audio peripherals are
  disabled. When i use windows 10 this problem does not occur. I cannot
  say in what package i found the bug but i use alsa and pulseaudio. Guide
  me if you need other informations for better understanding the problem.
  
  Kernel version: 5.9.8
  Audio driver in use: snd_hda_intel
  Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) 
HD Audio Controller
  
  $ aplay --list-devices
   List of PLAYBACK Hardware Devices 
  card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: Generic_1 [HD-Audio Generic], device 0: ALC295 Analog [ALC295 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  
  
  $ lsb_release -rd
  Description:KDE neon User Edition 5.20
  Release:20.04
  
  $ apt-cache policy alsa-base
  alsa-base:
Installato: 1.0.25+dfsg-0ubuntu5
Candidato:  1.0.25+dfsg-0ubuntu5
Tabella versione:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.12
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  niccolo3779 F pulseaudio
+  /dev/snd/controlC0:  niccolo3779 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
+ DistroRelease: KDE neon 20.04
+ InstallationDate: Installed on 2020-11-18 (4 days ago)
+ InstallationMedia: neon user "Focal" - Build amd64 LIVE Binary 20201112-12:05
+ Package: alsa-driver (not installed)
+ Tags:  focal
+ Uname: Linux 5.9.8-050908-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dip lpadmin plugdev sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/24/2019
+ dmi.bios.release: 15.35
+ dmi.bios.vendor: AMI
+ dmi.bios.version: F.35
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: 8615
+ dmi.board.vendor: HP
+ dmi.board.version: 46.23
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: HP
+ dmi.chassis.version: Chassis Version
+ dmi.ec.firmware.release: 46.23
+ dmi.modalias: 
dmi:bvnAMI:bvrF.35:bd09/24/2019:br15.35:efr46.23:svnHP:pnHPPavilionLaptop15-cw1xxx:pvr:rvnHP:rn8615:rvr46.23:cvnHP:ct10:cvrChassisVersion:
+ dmi.product.family: 103C_5335KV HP Pavilion
+ dmi.product.name: HP Pavilion Laptop 15-cw1xxx
+ dmi.product.sku: 6LH22EA#ABZ
+ dmi.sys.vendor: HP

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1905139/+attachment/5436847/+files/AlsaInfo.txt

-- 
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/1905139

Title:
  HP pavilion cw1010nl - audio noise

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi, i've encountered an audio problem after the installation of KDE
  Neon in my laptop (HP pavilion cw1010nl). I hear a constant noise that
  is not showed in pavucontrol and even when all the audio peripherals
  are disabled. When i use windows 10 this problem does not occur. I
  cannot say in what package i found the bug but i use alsa and
  pulseaudio. Guide me if you need other informations for better
  understanding the problem.

  Kernel version: 5.9.8
  Audio driver in use: snd_hda_intel
  Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) 
HD Audio Controller

  $ aplay --list-devices
   List of PLAYBACK Hardware Devices 
  card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: Generic_1 [HD-Audio Generic], device 0: ALC295 Analog [ALC295 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  $ lsb_release -rd
  Description:KDE neon User Edition 5.20
  Release:20.04

  $ apt-cache policy alsa-base
  alsa-base:
Installato: 1.0.25+dfsg-0ubuntu5
Candidato:  1.0.25+dfsg-0ubuntu5
Tabella versione:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  niccolo3779 F pulseaudio
   /dev/snd/controlC0:  niccolo3779 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not 

[Touch-packages] [Bug 1905167] [NEW] htop shows 100% usage of systemd-udevd

2020-11-22 Thread Lyubomir
Public bug reported:

I'm attaching a perf profile.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.3
ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65
Uname: Linux 5.4.0-54-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Nov 22 13:57:47 2020
InstallationDate: Installed on 2020-02-08 (287 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Acer Aspire A515-51G
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash 
resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality 
intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /usr/lib/systemd/system/dnscrypt-proxy.service → 
/etc/systemd/system/dnscrypt-proxy.service.d/override.conf
 [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
 
 3 overridden configuration files found.
UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago)
dmi.bios.date: 01/03/2019
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.02
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Charmander_KL
dmi.board.vendor: KBL
dmi.board.version: V2.02
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.02
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
dmi.product.family: Aspire 5
dmi.product.name: Aspire A515-51G
dmi.product.sku: 
dmi.product.version: V2.02
dmi.sys.vendor: Acer
mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742
mtime.conffile..etc.systemd.sleep.conf: 2020-09-26T18:33:31.018002

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


** Tags: amd64 apport-bug focal

-- 
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/1905167

Title:
  htop shows 100% usage of systemd-udevd

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm attaching a perf profile.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65
  Uname: Linux 5.4.0-54-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 13:57:47 2020
  InstallationDate: Installed on 2020-02-08 (287 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Aspire A515-51G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash 
resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality 
intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/dnscrypt-proxy.service → 
/etc/systemd/system/dnscrypt-proxy.service.d/override.conf
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742
  mtime.conffile..etc.systemd.sleep.conf: 2020-09-26T18:33:31.018002

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905167/+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 1534115] Re: apt-add-repository ppa:user/distro/repository pattern not recognized

2020-11-22 Thread Colin Watson
"distro" in this case means e.g. "ubuntu", not an Ubuntu series such as
"vivid".  This distinction was introduced due to the separate "ubuntu-
rtm" distribution that was at one point in use for the Ubuntu phone
project.

It's true that the documentation could be clearer about this.

-- 
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/1534115

Title:
  apt-add-repository ppa:user/distro/repository pattern not recognized

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  add-apt-repository --help shows ppa:user/distro/repository as possible
  pattern to add.

  sudo apt-add-repository ppa:nginx/stable works as expected.

  sudo apt-add-repository ppa:nginx/vivid/stable doesn't works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1534115/+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 1905027] Re: Need to force alsa to reload after reboot to have sound

2020-11-22 Thread lotuspsychje
please run the command apport-collect 1905027 in a terminal

-- 
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/1905027

Title:
  Need to force alsa to reload after reboot to have sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  I just installed ubuntu 20.04.01 (Focal Fossa) from a 18.04 version.

  I need to reload at each reboot alsa with:

  sudo alsa force-reload

  The workaround proposed here work for me.
  https://askubuntu.com/a/1281216/772996

  alsa seems to kill timidity (?)

  This solves it:
  systemctl disable timidity

  
  I didn't find an issue for this bug. Feel free to remove if needed.

  
  Thanks !


  apt-cache policy alsa gives me empty:
  alsa:
Installé : (aucun)
Candidat : (aucun)
   Table de version :

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1905027/+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 1905166] [NEW] systemd-shutdown cannot detach DM

2020-11-22 Thread Ingo Kueper
Public bug reported:

when powering down the system systemd cannot unmount /

systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy
systemd-shutdown[1]: Failed to finalize  DM devices, ignoring
reboot: Power down

as a result at each startup the filesystem is checked:

Press Ctrl+C to cancel all filesystem checks in progress

If systemd cannot unmount / that might not be a problem but it should be
less noisy and not result in a filesystem check after each reboot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.3
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 22 11:40:05 2020
MachineType: Dell Inc. Latitude 7410
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/11/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.1
dmi.board.name: 0M5G57
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd10/11/2020:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn0M5G57:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 7410
dmi.product.sku: 09CD
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

-- 
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/1905166

Title:
  systemd-shutdown cannot detach DM

Status in systemd package in Ubuntu:
  New

Bug description:
  when powering down the system systemd cannot unmount /

  systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy
  systemd-shutdown[1]: Failed to finalize  DM devices, ignoring
  reboot: Power down

  as a result at each startup the filesystem is checked:

  Press Ctrl+C to cancel all filesystem checks in progress

  If systemd cannot unmount / that might not be a problem but it should
  be less noisy and not result in a filesystem check after each reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 11:40:05 2020
  MachineType: Dell Inc. Latitude 7410
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0M5G57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd10/11/2020:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn0M5G57:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7410
  dmi.product.sku: 09CD
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+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 1894902] Re: 2 apparmor items missing for 'groovy'

2020-11-22 Thread lotuspsychje
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1894902

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  2 apparmor items missing for 'groovy'

Status in apparmor package in Ubuntu:
  New
Status in ntpsec package in Ubuntu:
  New

Bug description:
  need to add

  ~# cat /etc/apparmor.d/local/usr.sbin.ntpd 
  /run/systemd/userdb/io.systemd.Machine wr,
  /etc/ssl/openssl.cnf r,

  otherwise you get

  Sep  8 16:07:44 noc4 kernel: [ 1843.949193] audit: type=1400 
audit(1599599264.140:52): apparmor="DENIED" operation="connect" 
profile="/usr/sbin/ntpd" name="/run/systemd/userdb/io.systemd.Machine" 
pid=16851 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Sep  8 16:11:22 noc4 kernel: [ 2062.263356] audit: type=1400 
audit(1599599482.449:138): apparmor="DENIED" operation="open" 
profile="/usr/sbin/ntpd" name="/etc/ssl/openssl.cnf" pid=17639 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1894902/+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 1905139] Re: HP pavilion cw1010nl - audio noise

2020-11-22 Thread lotuspsychje
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1905139

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

-- 
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/1905139

Title:
  HP pavilion cw1010nl - audio noise

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi, i've encountered an audio problem after the installation of KDE
  Neon in my laptop (HP pavilion cw1010nl). I hear a constant noise that
  is not showed in pavucontrol and even when all the audio peripherals
  are disabled. When i use windows 10 this problem does not occur. I
  cannot say in what package i found the bug but i use alsa and
  pulseaudio. Guide me if you need other informations for better
  understanding the problem.

  Kernel version: 5.9.8
  Audio driver in use: snd_hda_intel
  Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) 
HD Audio Controller

  $ aplay --list-devices
   List of PLAYBACK Hardware Devices 
  card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: Generic_1 [HD-Audio Generic], device 0: ALC295 Analog [ALC295 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  $ lsb_release -rd
  Description:KDE neon User Edition 5.20
  Release:20.04

  $ apt-cache policy alsa-base
  alsa-base:
Installato: 1.0.25+dfsg-0ubuntu5
Candidato:  1.0.25+dfsg-0ubuntu5
Tabella versione:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1905139/+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