[Touch-packages] [Bug 1880640] Re: unable to create '/bin/systemd-hwdb.dpkg-new' (while processing './bin/systemd- hwdb'): Operation not permitted

2020-05-25 Thread Gigalo_CA
** Description changed:

+ Ubuntu 20.04
+ Kernel 5.4.0-31-generic
+ 
+ apt upgrade failed.  Cannot clear the error.
+ 
  Ran apt --fix-broken install as suggested and the following error fell
  through.
  
  Reading package lists... Done
- Building dependency tree   
+ Building dependency tree
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
-   udev
+   udev
  The following packages will be upgraded:
-   udev
+   udev
  1 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
  Need to get 0 B/1,362 kB of archives.
  After this operation, 1,024 B of additional disk space will be used.
- Do you want to continue? [Y/n] 
+ Do you want to continue? [Y/n]
  (Reading database ... 229440 files and directories currently installed.)
  Preparing to unpack .../udev_245.4-4ubuntu3.1_amd64.deb ...
  Unpacking udev (245.4-4ubuntu3.1) over (245.4-4ubuntu3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/udev_245.4-4ubuntu3.1_amd
  64.deb (--unpack):
-  unable to create '/bin/systemd-hwdb.dpkg-new' (while processing 
'./bin/systemd-
+  unable to create '/bin/systemd-hwdb.dpkg-new' (while processing 
'./bin/systemd-
  hwdb'): Operation not permitted
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
-  /var/cache/apt/archives/udev_245.4-4ubuntu3.1_amd64.deb
+  /var/cache/apt/archives/udev_245.4-4ubuntu3.1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
+ 
+ Following running apt --fix-broken install whoopsie
+ The following packages have unmet dependencies:
+  udev : Depends: libudev1 (= 245.4-4ubuntu3) but 245.4-4ubuntu3.1 is to be 
installed
+ 
+ E: Unmet dependencies. Try 'apt --fix-broken install' with no packages
+ (or specify a solution).

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

Title:
  unable to create '/bin/systemd-hwdb.dpkg-new' (while processing
  './bin/systemd- hwdb'): Operation not permitted

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  Kernel 5.4.0-31-generic

  apt upgrade failed.  Cannot clear the error.

  Ran apt --fix-broken install as suggested and the following error fell
  through.

  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
    udev
  The following packages will be upgraded:
    udev
  1 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
  Need to get 0 B/1,362 kB of archives.
  After this operation, 1,024 B of additional disk space will be used.
  Do you want to continue? [Y/n]
  (Reading database ... 229440 files and directories currently installed.)
  Preparing to unpack .../udev_245.4-4ubuntu3.1_amd64.deb ...
  Unpacking udev (245.4-4ubuntu3.1) over (245.4-4ubuntu3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/udev_245.4-4ubuntu3.1_amd
  64.deb (--unpack):
   unable to create '/bin/systemd-hwdb.dpkg-new' (while processing 
'./bin/systemd-
  hwdb'): Operation not permitted
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/udev_245.4-4ubuntu3.1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Following running apt --fix-broken install whoopsie
  The following packages have unmet dependencies:
   udev : Depends: libudev1 (= 245.4-4ubuntu3) but 245.4-4ubuntu3.1 is to be 
installed

  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages
  (or specify a solution).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1880640/+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 1880640] [NEW] unable to create '/bin/systemd-hwdb.dpkg-new' (while processing './bin/systemd- hwdb'): Operation not permitted

2020-05-25 Thread Gigalo_CA
Public bug reported:

Ran apt --fix-broken install as suggested and the following error fell
through.

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  udev
The following packages will be upgraded:
  udev
1 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
Need to get 0 B/1,362 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 229440 files and directories currently installed.)
Preparing to unpack .../udev_245.4-4ubuntu3.1_amd64.deb ...
Unpacking udev (245.4-4ubuntu3.1) over (245.4-4ubuntu3) ...
dpkg: error processing archive /var/cache/apt/archives/udev_245.4-4ubuntu3.1_amd
64.deb (--unpack):
 unable to create '/bin/systemd-hwdb.dpkg-new' (while processing './bin/systemd-
hwdb'): Operation not permitted
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/udev_245.4-4ubuntu3.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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


** Tags: systemd-hwdb udev

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

Title:
  unable to create '/bin/systemd-hwdb.dpkg-new' (while processing
  './bin/systemd- hwdb'): Operation not permitted

Status in systemd package in Ubuntu:
  New

Bug description:
  Ran apt --fix-broken install as suggested and the following error fell
  through.

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
udev
  The following packages will be upgraded:
udev
  1 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
  Need to get 0 B/1,362 kB of archives.
  After this operation, 1,024 B of additional disk space will be used.
  Do you want to continue? [Y/n] 
  (Reading database ... 229440 files and directories currently installed.)
  Preparing to unpack .../udev_245.4-4ubuntu3.1_amd64.deb ...
  Unpacking udev (245.4-4ubuntu3.1) over (245.4-4ubuntu3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/udev_245.4-4ubuntu3.1_amd
  64.deb (--unpack):
   unable to create '/bin/systemd-hwdb.dpkg-new' (while processing 
'./bin/systemd-
  hwdb'): Operation not permitted
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/udev_245.4-4ubuntu3.1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1880640/+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 1794523] Re: lxc-net.service is not properly ordered with network-online.target

2020-05-25 Thread Launchpad Bug Tracker
[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  lxc-net.service is not properly ordered with network-online.target

Status in lxc package in Ubuntu:
  Expired

Bug description:
  I made several tests and I figure out that the lxc-net.service is
  missing a Wants= directive to be properly ordered against network-
  online.target.

  As I understand the systemd.unit manpage, to be properly ordered a
  unit must define a Requires=/Wants= in addition to an After=/Before=.

  Regards.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1794523/+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 1879206] Re: cups hplip not install printer

2020-05-25 Thread Stefano Dall'Agata
** Attachment added: "Schermata del 2020-05-26 06-09-30.png"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+attachment/5376745/+files/Schermata%20del%202020-05-26%2006-09-30.png

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1879206] Re: cups hplip not install printer

2020-05-25 Thread Stefano Dall'Agata
The printer still does not work.

stefano@stefano-Lenovo-G50-30:~$ sudo dpkg -P --force-depends hplip hplip-data 
hplip-doc hplip-gui \
> libsane-hpaio printer-driver-hpcups printer-driver-hpijs 
> printer-driver-postscript-hp \
> hpijs-ppds libhpmud0
[sudo] password di stefano: 
(Lettura del database... 227442 file e directory attualmente installati.)
Rimozione di hplip (3.20.3+dfsg0-2)...
Eliminazione dei file di configurazione di hplip (3.20.3+dfsg0-2)...
Rimozione di hplip-data (3.20.3+dfsg0-2)...
dpkg: attenzione: nel rimuovere hplip-data, la directory "/usr/share/hplip/ui5" 
è risultata non vuota e non viene rimossa
dpkg: attenzione: nel rimuovere hplip-data, la directory 
"/usr/share/hplip/scan" è risultata non vuota e non viene rimossa
dpkg: attenzione: nel rimuovere hplip-data, la directory 
"/usr/share/hplip/prnt" è risultata non vuota e non viene rimossa
dpkg: attenzione: nel rimuovere hplip-data, la directory 
"/usr/share/hplip/pcard" è risultata non vuota e non viene rimossa
dpkg: attenzione: nel rimuovere hplip-data, la directory 
"/usr/share/hplip/installer" è risultata non vuota e non viene rimossa
dpkg: attenzione: nel rimuovere hplip-data, la directory "/usr/share/hplip/fax" 
è risultata non vuota e non viene rimossa
dpkg: attenzione: nel rimuovere hplip-data, la directory 
"/usr/share/hplip/copier" è risultata non vuota e non viene rimossa
dpkg: attenzione: nel rimuovere hplip-data, la directory 
"/usr/share/hplip/base/pexpect" è risultata non vuota e non viene rimossa
dpkg: attenzione: viene ignorata la richiesta di rimuovere hplip-doc poiché non 
è installato
Eliminazione dei file di configurazione di hplip-gui (3.20.3+dfsg0-2)...
Rimozione di libsane-hpaio:amd64 (3.20.3+dfsg0-2)...
Eliminazione dei file di configurazione di libsane-hpaio:amd64 
(3.20.3+dfsg0-2)...
dpkg: attenzione: nel rimuovere libsane-hpaio:amd64, la directory 
"/usr/share/hplip" è risultata non vuota e non viene rimossa
Rimozione di printer-driver-hpcups (3.20.3+dfsg0-2)...
dpkg: attenzione: viene ignorata la richiesta di rimuovere printer-driver-hpijs 
poiché non è installato
Rimozione di printer-driver-postscript-hp (3.20.3+dfsg0-2)...
dpkg: attenzione: viene ignorata la richiesta di rimuovere hpijs-ppds poiché 
non è installato
Rimozione di libhpmud0:amd64 (3.20.3+dfsg0-2)...
Elaborazione dei trigger per man-db (2.9.1-1)...
Elaborazione dei trigger per dbus (1.12.16-2ubuntu2)...
Elaborazione dei trigger per cups (2.3.1-9ubuntu1.1)...
Elaborazione dei trigger per libc-bin (2.31-0ubuntu9)...
stefano@stefano-Lenovo-G50-30:~$ wget 
https://nchc.dl.sourceforge.net/project/hplip/hplip/3.20.3/hplip-3.20.3.run
--2020-05-26 05:58:02--  
https://nchc.dl.sourceforge.net/project/hplip/hplip/3.20.3/hplip-3.20.3.run
Risoluzione di nchc.dl.sourceforge.net (nchc.dl.sourceforge.net)... 
140.110.96.69, 2001:e10::1f02::17
Connessione a nchc.dl.sourceforge.net 
(nchc.dl.sourceforge.net)|140.110.96.69|:443... connesso.
Richiesta HTTP inviata, in attesa di risposta... 200 OK
Lunghezza: 25724602 (25M) [application/x-makeself]
Salvataggio in: "hplip-3.20.3.run"

hplip-3.20.3.run100%[===>]  24,53M  5,05MB/sin
7,6s

2020-05-26 05:58:12 (3,25 MB/s) - "hplip-3.20.3.run" salvato
[25724602/25724602]

stefano@stefano-Lenovo-G50-30:~$ sh hplip-3.20.3.run --noexec
Creating directory hplip-3.20.3
Verifying archive integrity... All good.
Uncompressing HPLIP 3.20.3 Self Extracting 

[Touch-packages] [Bug 1880571] Re: PCI/internal sound card not detected on ubuntu focal

2020-05-25 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1793640 ***
https://bugs.launchpad.net/bugs/1793640

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 1793640, 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.


** No longer affects: ubuntu

** This bug has been marked a duplicate of bug 1793640
   Pulseaudio fails to detect sound card, while timidity is installed

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in alsa-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid
Status in timidity package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1880571/+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 1880589] Re: Screen Tearing - Ubuntu 20.04

2020-05-25 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1853094 ***
https://bugs.launchpad.net/bugs/1853094

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 1853094, 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 1853094
   [modeset] Screen tearing when using multiple monitors

** Tags added: tearing

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

Title:
  Screen Tearing - Ubuntu 20.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using the free drivers for my Nvidia card, since the private
  drivers gave more trouble than ever. I reported it too and the
  suggestion they gave me was to remove them and use the free drivers,
  but I have a serious problem with screen tearing, and I can't find a
  solution anywhere about it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 12:18:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:100d]
   NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 635M] [1043:100d]
  InstallationDate: Installed on 2020-04-24 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. K46CM
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=2d00d17e-c566-412e-bdfd-529af92571e2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K46CM.317
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K46CM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK46CM.317:bd05/17/2013:svnASUSTeKCOMPUTERINC.:pnK46CM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K46CM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/1880589/+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 1880589] Re: Screen Tearing - Ubuntu 20.04

2020-05-25 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1853094 ***
https://bugs.launchpad.net/bugs/1853094

For the full set of known tearing issues see:

https://bugs.launchpad.net/ubuntu/+bugs?field.tag=tearing

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

Title:
  Screen Tearing - Ubuntu 20.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using the free drivers for my Nvidia card, since the private
  drivers gave more trouble than ever. I reported it too and the
  suggestion they gave me was to remove them and use the free drivers,
  but I have a serious problem with screen tearing, and I can't find a
  solution anywhere about it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 12:18:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:100d]
   NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 635M] [1043:100d]
  InstallationDate: Installed on 2020-04-24 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. K46CM
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=2d00d17e-c566-412e-bdfd-529af92571e2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K46CM.317
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K46CM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK46CM.317:bd05/17/2013:svnASUSTeKCOMPUTERINC.:pnK46CM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K46CM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/1880589/+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 1880614] [NEW] Network Manager and the Menu Bar display a question mark, as though it wasn't able to connect to the internet, but Ubuntu can access the internet just fine; this w

2020-05-25 Thread Seija Kijin
Public bug reported:

A false flag of reporting a network without wifi access.

This happens when leaving the computer idle for 20 minutes or more.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon May 25 19:01:36 2020
InstallationDate: Installed on 2020-05-07 (18 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 20600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
 running  1.22.10  connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-05-25 19-01-22.png"
   
https://bugs.launchpad.net/bugs/1880614/+attachment/5376679/+files/Screenshot%20from%202020-05-25%2019-01-22.png

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

Title:
  Network Manager and the Menu Bar display a question mark, as though it
  wasn't able to connect to the internet, but Ubuntu can access the
  internet just fine; this was a false flag

Status in network-manager package in Ubuntu:
  New

Bug description:
  A false flag of reporting a network without wifi access.

  This happens when leaving the computer idle for 20 minutes or more.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon May 25 19:01:36 2020
  InstallationDate: Installed on 2020-05-07 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 20600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.22.10  connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880614/+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 1759950] Re: Lid-close suspend: blank screen when switching to user session

2020-05-25 Thread Sean Davis
** Changed in: xubuntu-default-settings (Ubuntu)
   Importance: Undecided => High

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

Title:
  Lid-close suspend: blank screen when switching to user session

Status in Light-Locker:
  New
Status in Xfce4 Power Manager:
  Confirmed
Status in light-locker package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in xfce4-power-manager package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Confirmed

Bug description:
  I'm currently testing Xubuntu 18.04 after a do-release-upgrade from
  16.04.

  I discovered a very weird issue. When doing S3 sleep via closing the
  lid, on resume the lock screen appears, I authenticate, but as soon as
  it switches to the user session the screen goes blank - not even a
  backlight.

  Switching to other ttys works and they display correctly but the GUI
  user session remains blank.

  If the system is manually suspended (not using the lid), then resumed
  either by opening the lid or pressing the power button, the GUI user
  session is fine.

  I narrowed it down to xfce4-power-manager and discovered disabling the
  lock-screen cured the issue.

  I cloned the repository and reviewed commits between 1.7 and 1.8.
  Fortunately there aren't many. Looking at 6365683 "Proper exit status
  for light-locker-command" I suspected the change in the SetActive
  return value, and reverted it.

  After a build/install cycle I've found the system now behaves
  correctly so I think the change should be reverted.

  I've created an issue upstream for this at

  https://github.com/the-cavalry/light-locker/issues/108

To manage notifications about this bug go to:
https://bugs.launchpad.net/light-locker/+bug/1759950/+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 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2020-05-25 Thread Sean Davis
** Changed in: xubuntu-docs (Ubuntu)
   Status: Confirmed => Triaged

** Summary changed:

- apt install xubuntu-desktop does not resolve dependencies properly
+ Document installation of xubuntu-desktop

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

Title:
  Document installation of xubuntu-desktop

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Fix Released
Status in xubuntu-docs package in Ubuntu:
  Triaged
Status in xubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+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 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)

2020-05-25 Thread Ben Bell
+1 to bionic backport please

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

Title:
  fstab binds appear as mounts (x-gvfs-hide is being ignored)

Status in GLib:
  Expired
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as
  well, I haven't tested) causes fstab binds to appear as mounts in
  Nautilus (and in Deepin Dock - Deepin is based on Gnome).

  Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour.

  I first noted this bug behaviour here:
  https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049

  Details of my particular system and issue with what I tried to resolve
  it can be found here:
  https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030

  1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux.

   OS: Arch Linux 
   Kernel: x86_64 Linux 4.10.13-1-ARCH
   Shell: bash 4.4.12
   Resolution: 1920x1200
   DE: Deepin 15.4
   WM: Deepin WM
   WM Theme: Arc-Darker
   GTK Theme: Arc-Darker [GTK2/3]
   Icon Theme: deepin
   Font: Noto Sans 11
   CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C]
   GPU: GeForce GTX 950
   RAM: 2598MiB / 15990MiB

  2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the
  problem).

  3. Nautilus to list internal physical drives (my SSD and 1TB HDD)
  only.

  4. Nautilus listed my system disk (as expected) but also listed all of
  my fstab binds as removable drives (Downloads, Music, Pictures, Videos
  and Documents although this was not listed as "Documents" but instead
  listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide
  those drives.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1691908/+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 1879206] Re: cups hplip not install printer

2020-05-25 Thread Till Kamppeter
Stefano, thanks for the Mate forum link, I have tried to make up the sum
of the tips to help users get HPLIP working again.

So anyone here, please try to clean up any HPLIP mess on your system
using the following steps:

1. Remove HPLIP deb-packages

sudo dpkg -P --force-depends hplip hplip-data hplip-doc hplip-gui \
libsane-hpaio printer-driver-hpcups printer-driver-hpijs 
printer-driver-postscript-hp \
hpijs-ppds libhpmud0

2. Remove upstream-installed HPLIP using HPLIP binary uninstaller

wget https://nchc.dl.sourceforge.net/project/hplip/hplip/3.20.3/hplip-3.20.3.run
sh hplip-3.20.3.run --noexec
cd hplip-3.20.3
sudo python3 ./uninstall.py
sudo rm -rf /usr/share/hplip/

3. Reinstall deb-packages with:

sudo apt install -f hplip-gui printer-driver-hpcups printer-driver-
postscript-hp libsane-hpaio

Then try to create a print queue with hp-setup and, if needed load the
proprietary plugin with hp-plugin. Also printer setup with GNOME Control
Center or system-config-printer should work again.

DO NOT install printer-driver-hpijs and hpijs-ppds. These packages are
deprecated and not maintained any more, and they also have no benefit
compared to printer-driver-hpcups.

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

2020-05-25 Thread El jinete sin cabeza
** Tags added: groovy

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

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in GNOME Shell:
  Unknown
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec
  https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  ---

  Happened during normal use of the desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1865300/+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 1879206] Re: cups hplip not install printer

2020-05-25 Thread Stefano Dall'Agata
It seems to me that in this discussion from the Ubuntu Mate forum there is a 
similar problem:
https://ubuntu-mate.community/t/hplip-missing-files/21782

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config

2020-05-25 Thread Johan Ehnberg
Digging even further back, it turns out that IFDOWN is in itself a
workaround for an equal issue dating back to ~2012. As such, the core of
the issue lies with how initramfs network setup overrides netplan.
Adding that package.

Given the very limited setup /etc/initramfs-tools/initramfs.conf allows
(including the DHCP default mentioned in the description), there is a
case to be made for allowing admins to rely on the full config rather
than initramfs for their network setup.

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

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

Title:
  DROPBEAR_IFDOWN=* takes interface down but leaves netplan config

Status in dropbear package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  On bionic, setting the network interface up (e.g. eno1) with DHCP now
  causes a /run/netplan/eno1.yaml and a /run/net-eno1.conf file to be
  written. The former gets imported by netplan after boot and causes the
  DHCP lease from the initrd to be around forever, which I think goes
  against the intent of DROPBEAR_IFDOWN=*.

  I have brewed up a workaround script that lives in /etc/initramfs-
  tools/scripts/init-bottom/hack-delete-netif-netplan.sh for now:

  
    8< cut >8 
  #!/bin/sh

  PREREQ=""

  prereqs() {
  echo "$PREREQ"
  }

  case "$1" in
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /scripts/functions

  log_begin_msg "Deleting all network configuration that systemd could try to 
import"
  rm /run/net-*.conf
  rm /run/netplan/*.yaml
  log_end_msg
    8< cut >8 

  I think that dropbear-intiramfs's init-bottom script should do this in
  addition to downing the interfaces that it finds via the
  DROPBEAR_IFDOWN pattern. Do you agree?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1813394/+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 1880594] [NEW] Ubuntu-server slow after upgrade to 20.04

2020-05-25 Thread Danilo Alculete
Public bug reported:

After upgrading to 20.04 my ubuntu-server seems very slow. Also using
tab to autocomplete commands takes ~10 Seconds to complete

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-server 1.450
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon May 25 19:57:43 2020
InstallationDate: Installed on 2020-03-10 (75 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta
UpgradeStatus: Upgraded to focal on 2020-04-26 (29 days ago)

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


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

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

Title:
  Ubuntu-server slow after upgrade to 20.04

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  After upgrading to 20.04 my ubuntu-server seems very slow. Also using
  tab to autocomplete commands takes ~10 Seconds to complete

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-server 1.450
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon May 25 19:57:43 2020
  InstallationDate: Installed on 2020-03-10 (75 days ago)
  InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-04-26 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1880594/+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 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

2020-05-25 Thread Guilherme G. Piccoli
*** This bug is a duplicate of bug 1573095 ***
https://bugs.launchpad.net/bugs/1573095

Although this is closed as dup, I thought would be good to clarify why
Debian Buster doesn't reproduce (at first). What happens is that Debian
includes the fsck on initrd by default, and in Ubuntu that doesn't
happen - the reason behind it is that rootfs is marked as always-verify
in the 6th field of fstab (fs_passno) in the Debian cloud image I got,
whereas Ubuntu cloud image use the default value, 0.

Once I changed Debian to not include fsck on initrd, it reproduced the
issue. And once I set Ubuntu rootfs to have value 1 on fstab's 6th
field, it stopped to reproduce. When fsck is on initrd, we don't
log_warn "fsck not present, so skipping $NAME file system", so we don't
fail in _checkfs_once(), hence there's no infinite loop on checkfs().

Cheers,


Guilherme

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

Title:
  machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel get stucks at boot if console=ttyS* is specified in the kernel
  cmdline and that serial HW isn't available on the system.

  Reproduced with:
  4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next 
(mainline)

  Removing the non-existent 'console=ttyS*' parameter fixes the
  situation.

  I tested it using KVM/qemu, but it has been brought to my attention
  that it was reproducible in VMware as well.

  I think it is safe to say that it is unlikely to be specifics to a
  certain virtualization technology type.

  Didn't test on baremetal yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+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 1880589] [NEW] Screen Tearing - Ubuntu 20.04

2020-05-25 Thread Juan Pedraza
Public bug reported:

I am using the free drivers for my Nvidia card, since the private
drivers gave more trouble than ever. I reported it too and the
suggestion they gave me was to remove them and use the free drivers, but
I have a serious problem with screen tearing, and I can't find a
solution anywhere about it.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 12:18:36 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:100d]
 NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 635M] [1043:100d]
InstallationDate: Installed on 2020-04-24 (30 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUSTeK COMPUTER INC. K46CM
ProcEnviron:
 LANGUAGE=es_CO:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=2d00d17e-c566-412e-bdfd-529af92571e2 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/17/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K46CM.317
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K46CM
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK46CM.317:bd05/17/2013:svnASUSTeKCOMPUTERINC.:pnK46CM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: K
dmi.product.name: K46CM
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
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 corruption 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/1880589

Title:
  Screen Tearing - Ubuntu 20.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using the free drivers for my Nvidia card, since the private
  drivers gave more trouble than ever. I reported it too and the
  suggestion they gave me was to remove them and use the free drivers,
  but I have a serious problem with screen tearing, and I can't find a
  solution anywhere about it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 12:18:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:100d]
   NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 635M] [1043:100d]
  InstallationDate: Installed on 2020-04-24 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. K46CM
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=2d00d17e-c566-412e-bdfd-529af92571e2 ro quiet splash 

[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

2020-05-25 Thread Stefano Dall'Agata
~$ lpadmin -p DJ3630 -E -v ipp://localhost:6/ipp/print -m everywhere
lpadmin: Unable to query printer: Successo

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1880571] Re: PCI/internal sound card not detected on ubuntu focal

2020-05-25 Thread Moritz Ringler
** Also affects: timidity (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid
Status in timidity package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Re: PCI/internal sound card not detected on ubuntu focal

2020-05-25 Thread Moritz Ringler
Seeing 'timidity' in the data collected by apport I have just
uninstalled timidity. This has immediately restored the availability of
the sound output. Also after rebooting, sound output is working again (I
have since rebooted twice).

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Status changed to Confirmed

2020-05-25 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] ProcInterrupts.txt

2020-05-25 Thread Moritz Ringler
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1880571/+attachment/5376571/+files/ProcInterrupts.txt

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Re: PCI/internal sound card not detected on ubuntu focal

2020-05-25 Thread Moritz Ringler
I had thought that appending 
options snd-hda-intel dmic_detect=0
to /etc/modprobe.d/alsa-base.conf
had fixed the problem. But the problem has since reappeared.

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

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

2020-05-25 Thread Moritz Ringler
apport information

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

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] UdevDb.txt

2020-05-25 Thread Moritz Ringler
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1880571/+attachment/5376574/+files/UdevDb.txt

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] WifiSyslog.txt

2020-05-25 Thread Moritz Ringler
apport information

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

** Description changed:

  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
- HDMI sound output is also does not work when the internal sound output does 
not work, USB sound output works.
+ HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload
  
  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  
  5.4.0-31-generic #35-Ubuntu
  
  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  timidity   1144 F timidity
-  /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
-  /dev/snd/seq:timidity   1144 F timidity
-  /dev/snd/timer:  timidity   1144 f timidity
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  timidity   1144 F timidity
+  /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
+  /dev/snd/seq:timidity   1144 F timidity
+  /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2b Intel Corp.
+  Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-31-generic N/A
-  linux-backports-modules-5.4.0-31-generic  N/A
-  linux-firmware1.187
+  linux-restricted-modules-5.4.0-31-generic N/A
+  linux-backports-modules-5.4.0-31-generic  N/A
+  linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:
-  
+ 
  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  

[Touch-packages] [Bug 1880571] RfKill.txt

2020-05-25 Thread Moritz Ringler
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1880571/+attachment/5376573/+files/RfKill.txt

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Dependencies.txt

2020-05-25 Thread Moritz Ringler
apport information

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

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] IwConfig.txt

2020-05-25 Thread Moritz Ringler
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1880571/+attachment/5376564/+files/IwConfig.txt

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] ProcModules.txt

2020-05-25 Thread Moritz Ringler
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1880571/+attachment/5376572/+files/ProcModules.txt

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

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

2020-05-25 Thread Moritz Ringler
apport information

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

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Lsusb-v.txt

2020-05-25 Thread Moritz Ringler
apport information

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

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Lsusb-t.txt

2020-05-25 Thread Moritz Ringler
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1880571/+attachment/5376567/+files/Lsusb-t.txt

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Lspci.txt

2020-05-25 Thread Moritz Ringler
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1880571/+attachment/5376565/+files/Lspci.txt

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] Lspci-vt.txt

2020-05-25 Thread Moritz Ringler
apport information

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

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] CRDA.txt

2020-05-25 Thread Moritz Ringler
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1880571/+attachment/5376561/+files/CRDA.txt

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

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

2020-05-25 Thread Moritz Ringler
apport information

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

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] AlsaInfo.txt

2020-05-25 Thread Moritz Ringler
apport information

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

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

Title:
  PCI/internal sound card not detected on ubuntu focal

Status in Ubuntu:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  5.4.0-31-generic #35-Ubuntu

  @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   1144 F timidity
   /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
   /dev/snd/seq:timidity   1144 F timidity
   /dev/snd/timer:  timidity   1144 f timidity
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
  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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 18.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: X35
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: X35
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: TUXEDO InfinityBook 14v1
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: TUXEDO Computers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1880571/+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 1880571] [NEW] PCI/internal sound card not detected on ubuntu focal

2020-05-25 Thread Moritz Ringler
Public bug reported:

After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
HDMI sound output also does not work when the internal sound output does not 
work, USB sound output works.
The internal speakers and microphone are nearly always detected after running
pulseaudio -k && sudo alsa force-reload

lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04

5.4.0-31-generic #35-Ubuntu

@Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  timidity   1144 F timidity
 /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
 /dev/snd/seq:timidity   1144 F timidity
 /dev/snd/timer:  timidity   1144 f timidity
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
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 002: ID 058f:3822 Alcor Micro Corp. HD Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1
Package: pulseaudio 1:13.99.1-1ubuntu3.2
PackageArchitecture: amd64
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-31-generic N/A
 linux-backports-modules-5.4.0-31-generic  N/A
 linux-firmware1.187
Tags:  focal
Uname: Linux 5.4.0-31-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 09/30/2016
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 18.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: X35
dmi.board.vendor: TUXEDO Computers
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: X35
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion:
dmi.product.family: Type1Family
dmi.product.name: TUXEDO InfinityBook 14v1
dmi.product.sku: Type1Sku0
dmi.product.version: TBD by OEM
dmi.sys.vendor: TUXEDO Computers

** Affects: ubuntu
 Importance: Undecided
 Status: New

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

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

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


** Tags: apport-collected focal

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

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

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: apport-collected focal

** Description changed:

  After booting the system the internal laptop speakers and the internal 
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
  They were working fine under ubuntu 18.04, stopped working after upgrading to 
19.10 and are still not working under 20.04.
  HDMI sound output is also does not work when the internal sound output does 
not work, USB sound output works.
  The internal speakers and microphone are nearly always detected after running
  pulseaudio -k && sudo alsa force-reload
  
  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  
  5.4.0-31-generic #35-Ubuntu
  
- @Hui Wang asked me to report this as a new bug in
- https://bugs.launchpad.net/ubuntu/+source/linux-oem-
- osp1/+bug/1864061/comments/64
+ @Hui Wang asked me to report this as a new bug in 
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  timidity   1144 F timidity
+  /dev/snd/pcmC0D0p:   timidity   1144 F...m timidity
+  /dev/snd/seq:timidity   1144 F timidity
+  /dev/snd/timer:  timidity   1144 f timidity
+ CasperMD5CheckResult: skip
+ DistroRelease: Ubuntu 20.04
+ HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381
+ Lsusb:
+  Bus 

[Touch-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423

2020-05-25 Thread Dejan
This one is still working on Windows PC. And it was also working on
previous version of Ubuntu 19.04

I notice, that first time I plug it in, VMWAre Workstation with Windows
VM also see this in its USB device list. But then windows software just
can't read it. So, first time after reboot, Key even becomes Green, but
than when it try's to access it, it changes to Red.

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

Title:
  pcscd doesn't support ActivKEy SIM B/N: 0945423

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
  Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
  After restart of the pcscd service, USB key shows green light, but few 
seconds after it goes to red.

  sudo service pcscd status
  ● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
 Main PID: 230408 (pcscd)
Tasks: 5 (limit: 57614)
   Memory: 1.9M
   CGroup: /system.slice/pcscd.service
   └─230408 /usr/sbin/pcscd --foreground --auto-exit

  svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
  svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

  Result of pcsc_scan
  sudo pcsc_scan 
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...found one
  Scanning present readers...
  0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
   
  Thu May 21 15:44:16 2020
   Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
Event number: 0
Card state: Card inserted, Unresponsive card, 

  So USB key is visible

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pcscd 1.8.26-3
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:38:57 2020
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+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 1864215] Re: Please add webp loader to gdk-pixbuf

2020-05-25 Thread Akkana Peck
See also bug #1407644 (libwebp) and bug #1318327 (eog). Still a problem
in focal fossa.

** Tags added: focal

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

Title:
  Please add webp loader to gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Attempting to load a webp image -- for instance, 

https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp
  or

https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg
  -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file 
format" error.

  Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in
  libwebp, but isn't this really a gdk-pixbuf issue? If it really does
  belong to libwebp, my apologies, please dup this bug to 1407644 (I'm
  confident it doesn't belong to eog since I don't use that program; I
  have other programs that use libgdk-pixbuf).

  You can probably use eog to test this, or run
  /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i 
webp
  (I assume the loader would mention webp if there was a loader for it).

  I have these packages installed in addition to libgdk-pixbuf2.0-0:
  libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes
  the format:

  $ file /tmp/FKK78W.jpg.webp
  /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 
1200x533, Scaling: [none]x[none], YUV color, decoders should clamp

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  Date: Fri Feb 21 08:48:36 2020
  InstallationDate: Installed on 2019-10-10 (133 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1864215/+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 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify

2020-05-25 Thread Paride Legovini
Excellent, thanks Adriaan! I linked this bug report to the upstream bug,
so its status will be automatically monitored by Launchpad.

** Also affects: openssh via
   https://bugzilla.mindrot.org/show_bug.cgi?id=3169
   Importance: Unknown
   Status: Unknown

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

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

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

Title:
  Port parameter sshd_config is 22 AND whatever you specify

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged

Bug description:
  On my Ubuntu Server 20.04 LTS with OpenSSH 1:8.2p1-4, I have TWO sshd
  deamons. One (on port 22) is for internal use, accepts passwords etc.
  The second (on port 7722) does not allow PAM use and no passwords,
  allows only one user(name) and uses an alternative autorized_keys file
  (that only root can edit).

  Any parameter FIRST encountered in sshd_config is the one that is
  accepted; others do not override (like in many other config files).
  There is one exception: 'Port', which is accumulative. To make life
  easier, I set the more restrictive parameters for port 7722 first and
  next include the system-default /etc/ssh/sshd_config.

  The /etc/ssh/sshd_config file(s) in Ubuntu Server 20.04 DO NOT specify
  'Port' anywhere - the default is 22. But: it is obviously still
  accumulative: Setting 'Port' to 7722 makes sshd listen on port 7722
  AND 22. This is unwanted.

  Proposed solution: Remove the accumulative behavior for 'Port' and
  REQUIRE the 'Port' parameter like before (and maybe have second and
  later parameters override the earlier ones, like 'everyone else').

  Regards,

  Adriaan

  PS Searching for solutions, I found that specifying 'ListenAddress
  0.0.0.0:7722' stops sshd from listening to port 22. This, however, is
  not documented in 'man 5 sshd_config' and may be an unreliable side-
  effect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1876320/+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 1864558] Re: Printer adds automatically at boot with notification or if printer deleted

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

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

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

Title:
  Printer adds automatically at boot with notification or if printer
  deleted

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When booting 20.04 I get a notification on the logon screen each time
  advising that my wireless printer has been setup. If I remove the
  printer via settings, then as soon as it's removed, it gets re-added
  and I see the same notification as I do on the logon screen about the
  printer having been setup. I've attached a screenshot of this
  notification.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.35.91-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 24 21:49:43 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-02-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221)
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1864558/+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 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423

2020-05-25 Thread Ludovic Rousseau
from your log I can see when you removed the device:
0016 [139787462866688] ccid_usb.c:857:WriteUSB() write failed (1/10): -4 
LIBUSB_ERROR_NO_DEVICE

Your problem is that reader can not power up the card after the reader is 
inserted again.
0003 [139787471259392] ifdhandler.c:1221:IFDHPowerICC() PowerUp failed

What is strange is that the first time the card power up is very slow but works 
fine.
The second time the reader responds very quickly with an error.

I don't think the driver can do much to solve that.
Do you have the same result if you use a different smart card?

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

Title:
  pcscd doesn't support ActivKEy SIM B/N: 0945423

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
  Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
  After restart of the pcscd service, USB key shows green light, but few 
seconds after it goes to red.

  sudo service pcscd status
  ● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
 Main PID: 230408 (pcscd)
Tasks: 5 (limit: 57614)
   Memory: 1.9M
   CGroup: /system.slice/pcscd.service
   └─230408 /usr/sbin/pcscd --foreground --auto-exit

  svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
  svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

  Result of pcsc_scan
  sudo pcsc_scan 
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...found one
  Scanning present readers...
  0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
   
  Thu May 21 15:44:16 2020
   Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
Event number: 0
Card state: Card inserted, Unresponsive card, 

  So USB key is visible

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pcscd 1.8.26-3
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:38:57 2020
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago)

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


Re: [Touch-packages] [Bug 1877159] Re: netlink: 'systemd-network': attribute type 5 has an invalid length.

2020-05-25 Thread Simon Déziel
On 2020-05-25 4:17 a.m., Łukasz Zemczak wrote:
> This is fine right now, but please be sure to be a bit more verbose
> about what kind of testing has been performed on the selected package!

I went through the [test case] steps before and after the -proposed
update. Should I simply explicitly mention me going trough it or do I
need to copy it again?

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

Title:
  netlink: 'systemd-network': attribute type 5 has an invalid length.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  systemd-networkd uses incorrect netlink attribute length for
  wireguard's persistent keepalive interval, which logs error messages
  from the kernel, and may incorrectly set the parameter.

  [test case]

  Only 1 Bionic VM is required to reproduce the problem:

  $ lxc launch images:ubuntu/bionic --vm -c security.secureboot=false foo
  $ sleep 10 # allow booting
  $ lxc exec foo -- apt install -y software-properties-common
  $ lxc exec foo -- add-apt-repository -y ppa:wireguard/wireguard
  $ lxc exec foo -- apt install -y wireguard-tools

  $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.netdev
  # foo
  [NetDev]
  Name=wg0
  Kind=wireguard

  [WireGuard]
  ListenPort=
  PrivateKey=cBkljQSKhtEe/U8GZmCAk2MBbKWL4TLC9PVtbMFyCVQ=

  [WireGuardPeer]
  PublicKey=emfIuZ3hZ+AnWIrKex/EqCp2mfzip8AxJu6RuweyRGc=
  AllowedIPs=192.168.255.2
  Endpoint=bar.lxd:
  EOF

  $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.network
  # foo
  [Match]
  Name=wg0

  [Network]
  Address=192.168.255.1/24
  EOF

  $ lxc exec foo -- systemctl restart systemd-networkd

  # notice the invalid length in dmesg
  $ lxc exec foo -- journalctl -kn 8
  -- Logs begin at Mon 2020-05-11 16:56:40 UTC, end at Mon 2020-05-11 17:03:46 
UTC. --
  May 11 16:58:25 foo kernel: nf_tables: (c) 2007-2009 Patrick McHardy 

  May 11 17:01:57 foo kernel: PKCS#7 signature not signed with a trusted key
  May 11 17:01:57 foo kernel: wireguard: module verification failed: signature 
and/or required key missing - tainting kernel
  May 11 17:01:57 foo kernel: wireguard: WireGuard 1.0.20200429 loaded. See 
www.wireguard.com for information.
  May 11 17:01:57 foo kernel: wireguard: Copyright (C) 2015-2019 Jason A. 
Donenfeld . All Rights Reserved.
  May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.
  May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.
  May 11 17:02:23 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.

  [regression potential]

  this adjusts the length of the specific netlink parameter, so any
  regression would likely relate to incorrectly setting the persistent
  keepalive interval parameter, or failure to set the parameter.

  [scope]

  this is needed only for Bionic.

  this was fixed upstream in commit
  7d0b26a027118ca063780421cb31c74e9d2664ee which was first included in
  v240, so this is fixed in Eoan and later.  Xenial does not include
  support for wireguard, so this does not apply there.

  [original description]

  This morning, our 2 Bionic machine configured with the wireguard's PPA
  and using systemd-networkd to configure the wireguard tunnel started
  misbehaving. Why this started just now is unclear ATM but their dmesg
  was filled with this:

  validate_nla: 100 callbacks suppressed
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.

  Folks in #systemd mentioned
  https://github.com/systemd/systemd/issues/11575 which points to 2
  commits missing from Bionic's systemd version:

  
https://github.com/systemd/systemd/commit/7d0b26a027118ca063780421cb31c74e9d2664ee
  
https://github.com/systemd/systemd/commit/624a47694cad4c87b2e807c32db656f3e9d679c5

  Focal's systemd have the above commits. Would it be possible to
  backport those 2 commits to Bionic?

  Additional information:

  # uname -a
  Linux noc-eu1 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 
x86_64 x86_64 

[Touch-packages] [Bug 1880541] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation returned error code 1

2020-05-25 Thread Balint Reczey
Yes, the kvm group is not created by systemd on 18.04 and users who
created it as a non-system group can observe that failure during the
upgrade.

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

** Tags added: rls-ff-incoming

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

Title:
  package udev 245.4-4ubuntu3 failed to install/upgrade: podproces
  zainstalowany pakiet udev skrypt post-installation returned error code
  1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  During the Dist upgrade from 18.04 LTS to 20.04 LTS udev failed to
  configure interrupting the upgrade.

  dpkg complained that kvm already exist but it is not a system group.

  From what I saw my user was the only member of kvm group
  I don't recall installing kvm manually but I do have Android emulator 
installed so it is possible that it is related.

  Removing kvm group via
  groupdel kvm
  allowed 
  dpkg --configure -a 
  to succeed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 56-hpmud.rules 70-snap.core.rules
  Date: Mon May 25 11:01:36 2020
  ErrorMessage: podproces zainstalowany pakiet udev skrypt post-installation 
zwrócił kod błędu 1
  InstallationDate: Installed on 2017-10-18 (949 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic 
root=UUID=1c3374a5-d07b-4588-8159-7607318eb2c9 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces 
zainstalowany pakiet udev skrypt post-installation zwrócił kod błędu 1
  UpgradeStatus: Upgraded to focal on 2020-05-25 (0 days ago)
  dmi.bios.date: 07/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.80
  dmi.board.name: X370 Taichi
  dmi.board.vendor: ASRock
  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.:bvrP4.80:bd07/18/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr: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.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1880541/+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 1879206] Re: cups hplip not install printer

2020-05-25 Thread Till Kamppeter
Could you try

lpadmin -p DJ3630 -E -v ipp://localhost:6/ipp/print -m everywhere

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423

2020-05-25 Thread Dejan
pcscd log when I pulled USB out and put it back in.

** Attachment added: "Log2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+attachment/5376525/+files/log2.txt

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

Title:
  pcscd doesn't support ActivKEy SIM B/N: 0945423

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
  Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
  After restart of the pcscd service, USB key shows green light, but few 
seconds after it goes to red.

  sudo service pcscd status
  ● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
 Main PID: 230408 (pcscd)
Tasks: 5 (limit: 57614)
   Memory: 1.9M
   CGroup: /system.slice/pcscd.service
   └─230408 /usr/sbin/pcscd --foreground --auto-exit

  svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
  svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

  Result of pcsc_scan
  sudo pcsc_scan 
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...found one
  Scanning present readers...
  0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
   
  Thu May 21 15:44:16 2020
   Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
Event number: 0
Card state: Card inserted, Unresponsive card, 

  So USB key is visible

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pcscd 1.8.26-3
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:38:57 2020
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+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 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423

2020-05-25 Thread Dejan
It gets new USB Device ID every time I plugin the Key
ID 11, re plugin, ID 12...

root@rodigerlaptop1:/dev/bus/usb/001# ls -la
total 0
drwxr-xr-x 2 root root 180 svi  25 13:29 .
drwxr-xr-x 6 root root 120 svi  25 13:11 ..
crw-rw-r-- 1 root root 189,  0 svi  25 13:11 001
crw-rw-r-- 1 root root 189,  1 svi  25 13:11 002
crw-rw-r-- 1 root root 189,  2 svi  25 13:11 003
crw-rw-r-- 1 root root 189,  3 svi  25 13:11 004
crw-rw-r-- 1 root root 189,  4 svi  25 13:11 005
crw-rw-r-- 1 root root 189,  5 svi  25 13:11 006
crw-rw-r-- 1 root root 189, 10 svi  25 13:29 011
root@rodigerlaptop1:/dev/bus/usb/001# ls -la
total 0
drwxr-xr-x 2 root root 180 svi  25 13:33 .
drwxr-xr-x 6 root root 120 svi  25 13:11 ..
crw-rw-r-- 1 root root 189,  0 svi  25 13:11 001
crw-rw-r-- 1 root root 189,  1 svi  25 13:11 002
crw-rw-r-- 1 root root 189,  2 svi  25 13:11 003
crw-rw-r-- 1 root root 189,  3 svi  25 13:11 004
crw-rw-r-- 1 root root 189,  4 svi  25 13:11 005
crw-rw-r-- 1 root root 189,  5 svi  25 13:11 006
crw-rw-r-- 1 root root 189, 11 svi  25 13:33 012

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

Title:
  pcscd doesn't support ActivKEy SIM B/N: 0945423

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
  Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
  After restart of the pcscd service, USB key shows green light, but few 
seconds after it goes to red.

  sudo service pcscd status
  ● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
 Main PID: 230408 (pcscd)
Tasks: 5 (limit: 57614)
   Memory: 1.9M
   CGroup: /system.slice/pcscd.service
   └─230408 /usr/sbin/pcscd --foreground --auto-exit

  svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
  svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

  Result of pcsc_scan
  sudo pcsc_scan 
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...found one
  Scanning present readers...
  0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
   
  Thu May 21 15:44:16 2020
   Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
Event number: 0
Card state: Card inserted, Unresponsive card, 

  So USB key is visible

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pcscd 1.8.26-3
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:38:57 2020
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+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 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423

2020-05-25 Thread Dejan
After pcscd restart, I see ActivKey got new Device ID

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

Title:
  pcscd doesn't support ActivKEy SIM B/N: 0945423

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
  Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
  After restart of the pcscd service, USB key shows green light, but few 
seconds after it goes to red.

  sudo service pcscd status
  ● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
 Main PID: 230408 (pcscd)
Tasks: 5 (limit: 57614)
   Memory: 1.9M
   CGroup: /system.slice/pcscd.service
   └─230408 /usr/sbin/pcscd --foreground --auto-exit

  svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
  svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

  Result of pcsc_scan
  sudo pcsc_scan 
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...found one
  Scanning present readers...
  0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
   
  Thu May 21 15:44:16 2020
   Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
Event number: 0
Card state: Card inserted, Unresponsive card, 

  So USB key is visible

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pcscd 1.8.26-3
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:38:57 2020
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+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 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423

2020-05-25 Thread Dejan
sudo lsusb |grep ActivKey
Bus 001 Device 008: ID 09c3:0014 HID Global ActivIdentity ActivKey SIM USB Token

lsusb -D /dev/bus/usb/001/008 
Device: ID 09c3:0014 HID Global ActivIdentity ActivKey SIM USB Token
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize016
  idVendor   0x09c3 HID Global
  idProduct  0x0014 ActivIdentity ActivKey SIM USB Token
  bcdDevice2.07
  iManufacturer   1 ActivIdentity
  iProduct2 Activkey_Sim
  iSerial 0 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   0x005d
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  3 CCID 1.10
bmAttributes 0x80
  (Bus Powered)
MaxPower  100mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass11 Chip/SmartCard
  bInterfaceSubClass  0 
  bInterfaceProtocol  0 
  iInterface  4 CCID Bulk Interface
  ChipCard Interface Descriptor:
bLength54
bDescriptorType33
bcdCCID  1.10  (Warning: Only accurate for version 1.0)
nMaxSlotIndex   0
bVoltageSupport 7  5.0V 3.0V 1.8V 
dwProtocols 3  T=0 T=1
dwDefaultClock   4800
dwMaxiumumClock  4800
bNumClockSupported  0
dwDataRate  12903 bps
dwMaxDataRate  412903 bps
bNumDataRatesSupp.  0
dwMaxIFSD 254
dwSyncProtocols   
dwMechanical  
dwFeatures   00010030
  Auto clock change
  Auto baud rate change
  TPDU level exchange
dwMaxCCIDMsgLen   271
bClassGetResponse  00
bClassEnvelope 00
wlcdLayout   none
bPINSupport 0 
bMaxCCIDBusySlots   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval  16
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x
  (Bus Powered)

service pcscd restart
root@rodigerlaptop1:/dev/bus/usb/001# lsusb 
Bus 004 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit 
Ethernet Adapter
Bus 004 Device 003: ID 0424:5807 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 004 Device 002: ID 2109:0820 VIA Labs, Inc. USB3.1 Hub 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 006: ID 2109: VIA Labs, Inc. 
Bus 003 Device 012: ID 0451:3421 Texas Instruments, Inc. USB2.0 Hub 
Bus 003 Device 011: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 003 Device 008: ID 03f0:0667 HP, Inc 
Bus 003 Device 005: ID 03f0:0269 HP, Inc 
Bus 003 Device 003: ID 0424:2807 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 003 Device 002: ID 2109:2820 VIA Labs, Inc. USB2.0 Hub 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint 
Reader
Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera
Bus 001 Device 003: ID 0b0e:245e GN Netcom Jabra Link 370
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 006: ID 8087:0a2b Intel Corp. 
Bus 001 Device 009: ID 09c3:0014 HID Global ActivIdentity ActivKey SIM USB Token
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 

[Touch-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423

2020-05-25 Thread Dejan
sudo service pcscd status
● pcscd.service - PC/SC Smart Card Daemon
 Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
 Active: inactive (dead)
TriggeredBy: ● pcscd.socket
   Docs: man:pcscd(8)
drodiger@rodigerlaptop1:~$ sudo pcsc_scan 
Using reader plug'n play mechanism
Scanning present readers...
0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
 
Mon May 25 13:13:00 2020
 Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
  Event number: 0
  Card state: Card inserted, Unresponsive card, 
Scanning present readers...
Waiting for the first reader...found one
Scanning present readers...
0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
 
Mon May 25 13:13:16 2020
 Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
  Event number: 0
  Card state: Card inserted, Unresponsive card, 
 /   

Reporting this Unresponsive Card, when it should detect the card?

sudo service pcscd status
● pcscd.service - PC/SC Smart Card Daemon
 Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
 Active: inactive (dead) since Mon 2020-05-25 13:14:24 CEST; 29s ago
TriggeredBy: ● pcscd.socket
   Docs: man:pcscd(8)
Process: 16280 ExecStart=/usr/sbin/pcscd --foreground --auto-exit 
(code=exited, status=0/SUCCESS)
   Main PID: 16280 (code=exited, status=0/SUCCESS)

svi 25 13:12:59 rodigerlaptop1 pcscd[16280]: 0268 commands.c:249:CmdPowerOn 
Card absent or mute
svi 25 13:12:59 rodigerlaptop1 pcscd[16280]: 0007 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
svi 25 13:12:59 rodigerlaptop1 pcscd[16280]: 0004 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016
svi 25 13:13:11 rodigerlaptop1 pcscd[16280]: 11584403 ccid_usb.c:857:WriteUSB() 
write failed (1/7): -4 LIBUSB_ERROR_NO_DEVICE
svi 25 13:13:16 rodigerlaptop1 pcscd[16280]: 04928359 commands.c:249:CmdPowerOn 
Card absent or mute
svi 25 13:13:16 rodigerlaptop1 pcscd[16280]: 0240 commands.c:249:CmdPowerOn 
Card absent or mute
svi 25 13:13:16 rodigerlaptop1 pcscd[16280]: 0260 commands.c:249:CmdPowerOn 
Card absent or mute
svi 25 13:13:16 rodigerlaptop1 pcscd[16280]: 0006 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
svi 25 13:13:16 rodigerlaptop1 pcscd[16280]: 0004 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016
svi 25 13:14:24 rodigerlaptop1 systemd[1]: pcscd.service: Succeeded.

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

Title:
  pcscd doesn't support ActivKEy SIM B/N: 0945423

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
  Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
  After restart of the pcscd service, USB key shows green light, but few 
seconds after it goes to red.

  sudo service pcscd status
  ● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
 Main PID: 230408 (pcscd)
Tasks: 5 (limit: 57614)
   Memory: 1.9M
   CGroup: /system.slice/pcscd.service
   └─230408 /usr/sbin/pcscd --foreground --auto-exit

  svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
  svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

  Result of pcsc_scan
  sudo pcsc_scan 
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...found one
  Scanning present readers...
  0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
   
  Thu May 21 15:44:16 2020
   Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
Event number: 0
Card state: Card inserted, Unresponsive card, 

  So USB key is visible

  ProblemType: 

[Touch-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423

2020-05-25 Thread Ludovic Rousseau
I don't see any problem in your log.
The card is detected and the ATR is available.
You can test with the command pcsc_scan from the package pcsc-tools.

Please generate a new log including the problem.

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

Title:
  pcscd doesn't support ActivKEy SIM B/N: 0945423

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
  Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
  After restart of the pcscd service, USB key shows green light, but few 
seconds after it goes to red.

  sudo service pcscd status
  ● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
 Main PID: 230408 (pcscd)
Tasks: 5 (limit: 57614)
   Memory: 1.9M
   CGroup: /system.slice/pcscd.service
   └─230408 /usr/sbin/pcscd --foreground --auto-exit

  svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
  svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

  Result of pcsc_scan
  sudo pcsc_scan 
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...found one
  Scanning present readers...
  0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
   
  Thu May 21 15:44:16 2020
   Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
Event number: 0
Card state: Card inserted, Unresponsive card, 

  So USB key is visible

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pcscd 1.8.26-3
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:38:57 2020
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+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 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param

2020-05-25 Thread Todor Andreev
Thank you Dan Streetman and all for your work!

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released
Status in netplan.io source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Fix Released
Status in netplan.io source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in netplan.io source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  the networkd UseRoutes parameter allowed ignoring all routes provided
  by a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.

  The systemd in Focal unfortunately has part of the upstream code; it
  no longer ignores the gateway route when UseRoutes=false is specified,
  but also it does not include the UseGateway parameter.

  Before Focal, networkd did not allow ignoring dhcpv4 routes and the
  gateway separately; the UseRoutes= parameter either used, or ignored,
  both.  This is why upstream added the UseGateway= paramter, which
  should be backported to allow control of ignoring the dhcpv4 routes
  and gateway separately.

  [test case]

  In Focal, bug 1872589 has a good test case netplan config, but a very
  quick test can be done with the networkd config:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false

  this results in the system incorrectly setting a route via the default
  gateway:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  Before Focal, the above test case shows "correct" behavior, but there
  is no way to ignore the dhcpv4 routes but use the dhcpv4 gateway.
  This pre-Focal, the test case would be to use the UseGateway=
  parameter, e.g.:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  UseGateway=true

  which *should* result in the default gateway being configured:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  [regression potential]

  Any regression would likely involve incorrect setting, or ignoring, of
  dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the
  dhcpv4-provided gateway.

  [scope]

  This is fixed by these upstream PRs:
  https://github.com/systemd/systemd/pull/15443
  https://github.com/systemd/systemd/pull/15136
  https://github.com/systemd/systemd/pull/14983

  Parts of all those PRs are required in Focal, Eoan, and Bionic.

  I am not fixing this for Xenial, at this time.

  For Debian, I opened this MR:
  https://salsa.debian.org/systemd-team/systemd/-/merge_requests/92

  For Groovy, I opened this MR:
  
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/383661

  [other info]

  to properly support separation of 'routes' and 'gateways' received via
  dhcp4, SRU releases should also support the UseGateway parameter,
  which is what this bug was originally opened requesting.

  [original description]

  requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in
  https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1867375/+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 1880410] Re: pulseaudio doesn't enforce sample rate set in daemon.conf

2020-05-25 Thread Daniel van Vugt
Oh yes. I thought you mentioned the semicolons as only artistic
formatting.

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

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

Title:
  pulseaudio doesn't enforce sample rate set in daemon.conf

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

Bug description:
  Before submitting this bugreport I've went through the daemon.conf man page 
and the pulseaudio documentation, but have not found a solution to my problem.
  I've moved from Debian stable with
  pulseaudio version 12.2-4+deb10u1 to Kubuntu 20.04 with
  pulseaudio version 13.99.1-1ubuntu3.2.
  I'm experiencing cracking issues on external USB audio device Xonar U3 while 
listening to certain audio sources (system sounds included). This issue doesn't 
happen when using my laptop's internal audio device.
  Output of 'cat /proc/asound/card2/stream0' without audio stream running:
  C-Media Electronics Inc. USB Advanced Audio Device at usb-:00:14.0-2, 
full  : USB Audio

  Playback:
Status: Running
Interface = 1
Altset = 1
Packet Size = 200
Momentary freq = 44100 Hz (0x2c.199a)
Interface 1
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 1 OUT (ADAPTIVE)
Rates: 8000, 16000, 44100, 48000
Bits: 16

  Capture:
Status: Stop
Interface 2
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 2 IN (ASYNC)
Rates: 8000, 16000, 44100, 48000
Bits: 16
  The following behaviour happens with default settings in 
/etc/pulse/daemon.conf:
  Xonar U3 plugged in, firefox running:
Momentary freq = 48000 Hz (0x30.)

  Xonar U3 plugged in, Clementine/Strawberry audio player running:
Momentary freq = 44100 Hz (0x2c.199a)

  Xonar U3 plugged in with Deadbeef set to override sample rate to 48kHz:
Momentary freq = 48000 Hz (0x30.)
  I've modified the daemon.conf as follows:
  ; default-sample-format = s16le #no change on this line, this is 
corresponding with the format the usb audio device suggests to be using
  ; default-sample-rate = 48000
  ; alternate-sample-rate = 48000
  However, when running video or audio sources with 44100Hz audio, applications 
 do not respect the default-sample-rate and Momentary freq reports 44100Hz, 
while other sources either send 48kHz by default or have no problem respecting 
the setting (I've tried the game Into the Breach, VLC running 48kHz video and 
audio files).
  Complete /etc/pulse/daemon.conf contents:
  https://gist.github.com/zelmor/f224e6e4d300241e8431d3258e777e73
  Checking syslog doesn't indicate any errors either, gist:
  https://gist.github.com/zelmor/5e59094be4d90ffa9e0ff6275594e370
  ==Workarounds attempted==

  Modifying /etc/pulse/default.pa to include:

  load-module module-udev-detect tsched=0
  Even after killing pulseaudio, this did not resolve anything. It 
also doesn't look like a good overall solution to the problem.

  Modifying daemon.conf to:

  ; resample-method = src-sinc-best-quality
  ; avoid-resampling = true
  Did not fix the issue.
  It is not possible to roll back PA to a previous version in Kubuntu 20.04 
without breaking dependencies of the Plasma desktop, so this was not attempted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  zelmor 1994 F pulseaudio
   /dev/snd/controlC1:  zelmor 1994 F pulseaudio
   /dev/snd/controlC0:  zelmor 1994 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun May 24 16:30:11 2020
  InstallationDate: Installed on 2020-04-28 (25 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET46WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7S11H00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20B7S11H00:pvrThinkPadT450:rvnLENOVO:rn20B7S11H00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20B7S11H00
  dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.daemon.conf: [modified]
  

[Touch-packages] [Bug 1880410] Re: pulseaudio doesn't enforce sample rate set in daemon.conf

2020-05-25 Thread Peter Fiser
I've missed a crucial point on the top of the daemon.conf file:

The configuration file is a simple collection of variable declarations. If the 
configuration
file parser encounters either ; or # it ignores the rest of the line until its 
end.

Please close this issue.

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

Title:
  pulseaudio doesn't enforce sample rate set in daemon.conf

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

Bug description:
  Before submitting this bugreport I've went through the daemon.conf man page 
and the pulseaudio documentation, but have not found a solution to my problem.
  I've moved from Debian stable with
  pulseaudio version 12.2-4+deb10u1 to Kubuntu 20.04 with
  pulseaudio version 13.99.1-1ubuntu3.2.
  I'm experiencing cracking issues on external USB audio device Xonar U3 while 
listening to certain audio sources (system sounds included). This issue doesn't 
happen when using my laptop's internal audio device.
  Output of 'cat /proc/asound/card2/stream0' without audio stream running:
  C-Media Electronics Inc. USB Advanced Audio Device at usb-:00:14.0-2, 
full  : USB Audio

  Playback:
Status: Running
Interface = 1
Altset = 1
Packet Size = 200
Momentary freq = 44100 Hz (0x2c.199a)
Interface 1
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 1 OUT (ADAPTIVE)
Rates: 8000, 16000, 44100, 48000
Bits: 16

  Capture:
Status: Stop
Interface 2
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 2 IN (ASYNC)
Rates: 8000, 16000, 44100, 48000
Bits: 16
  The following behaviour happens with default settings in 
/etc/pulse/daemon.conf:
  Xonar U3 plugged in, firefox running:
Momentary freq = 48000 Hz (0x30.)

  Xonar U3 plugged in, Clementine/Strawberry audio player running:
Momentary freq = 44100 Hz (0x2c.199a)

  Xonar U3 plugged in with Deadbeef set to override sample rate to 48kHz:
Momentary freq = 48000 Hz (0x30.)
  I've modified the daemon.conf as follows:
  ; default-sample-format = s16le #no change on this line, this is 
corresponding with the format the usb audio device suggests to be using
  ; default-sample-rate = 48000
  ; alternate-sample-rate = 48000
  However, when running video or audio sources with 44100Hz audio, applications 
 do not respect the default-sample-rate and Momentary freq reports 44100Hz, 
while other sources either send 48kHz by default or have no problem respecting 
the setting (I've tried the game Into the Breach, VLC running 48kHz video and 
audio files).
  Complete /etc/pulse/daemon.conf contents:
  https://gist.github.com/zelmor/f224e6e4d300241e8431d3258e777e73
  Checking syslog doesn't indicate any errors either, gist:
  https://gist.github.com/zelmor/5e59094be4d90ffa9e0ff6275594e370
  ==Workarounds attempted==

  Modifying /etc/pulse/default.pa to include:

  load-module module-udev-detect tsched=0
  Even after killing pulseaudio, this did not resolve anything. It 
also doesn't look like a good overall solution to the problem.

  Modifying daemon.conf to:

  ; resample-method = src-sinc-best-quality
  ; avoid-resampling = true
  Did not fix the issue.
  It is not possible to roll back PA to a previous version in Kubuntu 20.04 
without breaking dependencies of the Plasma desktop, so this was not attempted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  zelmor 1994 F pulseaudio
   /dev/snd/controlC1:  zelmor 1994 F pulseaudio
   /dev/snd/controlC0:  zelmor 1994 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun May 24 16:30:11 2020
  InstallationDate: Installed on 2020-04-28 (25 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET46WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7S11H00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20B7S11H00:pvrThinkPadT450:rvnLENOVO:rn20B7S11H00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20B7S11H00
  dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T450
  

[Touch-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

2020-05-25 Thread Andrew Derry
I'm new on here - sorry for any mistakes.
I didn't know if it's worth adding, or where to add... that after I got this 
crash, I closed everything (and had my Android plugged in and mounted, but 
ejected it) and rebooted.
Now, when I plug my phone back in, it makes the little alert noise, but I 
cannot find my phone drive. It doesn't show up in Files like it did last time, 
even when I click "other locations". (Files was what I was using to look at the 
phone files before the reboot)

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

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in GNOME Shell:
  Unknown
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec
  https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  ---

  Happened during normal use of the desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1865300/+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 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423

2020-05-25 Thread Dejan
/usr/sbin/pcscd --version
pcsc-lite version 1.8.26.
Copyright (C) 1999-2002 by David Corcoran .
Copyright (C) 2001-2018 by Ludovic Rousseau .
Copyright (C) 2003-2004 by Damien Sauveron .
Report bugs to .
Enabled features: Linux x86_64-pc-linux-gnu libsystemd serial usb libudev 
usbdropdir=/usr/lib/pcsc/drivers ipcdir=/run/pcscd filter 
configdir=/etc/reader.conf.d

uname -a
Linux rodigerlaptop1 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

Ubuntu 20.04

HP Zbook 15 G3 laptop

ActivKey SIM B/N: 0945423
This is USB key

[ 6955.286635] usb 1-1: new full-speed USB device number 7 using xhci_hcd
[ 6955.437171] usb 1-1: New USB device found, idVendor=09c3, idProduct=0014, 
bcdDevice= 2.07
[ 6955.437172] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6955.437174] usb 1-1: Product: Activkey_Sim
[ 6955.437174] usb 1-1: Manufacturer: ActivIdentity



** Attachment added: "log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+attachment/5376522/+files/log.txt

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

Title:
  pcscd doesn't support ActivKEy SIM B/N: 0945423

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
  Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
  After restart of the pcscd service, USB key shows green light, but few 
seconds after it goes to red.

  sudo service pcscd status
  ● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
 Main PID: 230408 (pcscd)
Tasks: 5 (limit: 57614)
   Memory: 1.9M
   CGroup: /system.slice/pcscd.service
   └─230408 /usr/sbin/pcscd --foreground --auto-exit

  svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
  svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

  Result of pcsc_scan
  sudo pcsc_scan 
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...found one
  Scanning present readers...
  0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
   
  Thu May 21 15:44:16 2020
   Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
Event number: 0
Card state: Card inserted, Unresponsive card, 

  So USB key is visible

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pcscd 1.8.26-3
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:38:57 2020
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+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 1880541] [NEW] package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation returned error code 1

2020-05-25 Thread Sebastian "Nait" Kacprzak
Public bug reported:

During the Dist upgrade from 18.04 LTS to 20.04 LTS udev failed to
configure interrupting the upgrade.

dpkg complained that kvm already exist but it is not a system group.

>From what I saw my user was the only member of kvm group
I don't recall installing kvm manually but I do have Android emulator installed 
so it is possible that it is related.

Removing kvm group via
groupdel kvm
allowed 
dpkg --configure -a 
to succeed

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: udev 245.4-4ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
Uname: Linux 4.15.0-101-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CustomUdevRuleFiles: 56-hpmud.rules 70-snap.core.rules
Date: Mon May 25 11:01:36 2020
ErrorMessage: podproces zainstalowany pakiet udev skrypt post-installation 
zwrócił kod błędu 1
InstallationDate: Installed on 2017-10-18 (949 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic 
root=UUID=1c3374a5-d07b-4588-8159-7607318eb2c9 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: systemd
Title: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces 
zainstalowany pakiet udev skrypt post-installation zwrócił kod błędu 1
UpgradeStatus: Upgraded to focal on 2020-05-25 (0 days ago)
dmi.bios.date: 07/18/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.80
dmi.board.name: X370 Taichi
dmi.board.vendor: ASRock
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.:bvrP4.80:bd07/18/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr: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.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-package focal

** Description changed:

  During the Dist upgrade from 18.04 LTS to 20.04 LTS udev failed to
  configure interrupting the upgrade.
  
  dpkg complained that kvm already exist but it is not a system group.
  
  From what I saw my user was the only member of kvm group
  I don't recall installing kvm manually but I do have Android emulator 
installed so it is possible that it is related.
  
- Removing kvm user allowed dpkg --configure --all to succeed
+ Removing kvm group via
+ groupdel kvm
+ allowed 
+ dpkg --configure -a 
+ to succeed
  
  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 56-hpmud.rules 70-snap.core.rules
  Date: Mon May 25 11:01:36 2020
  ErrorMessage: podproces zainstalowany pakiet udev skrypt post-installation 
zwrócił kod błędu 1
  InstallationDate: Installed on 2017-10-18 (949 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic 
root=UUID=1c3374a5-d07b-4588-8159-7607318eb2c9 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
-  dpkg 1.19.7ubuntu3
-  apt  2.0.2ubuntu0.1
+  dpkg 1.19.7ubuntu3
+  apt  2.0.2ubuntu0.1
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces 
zainstalowany pakiet udev skrypt post-installation zwrócił kod błędu 1
  UpgradeStatus: Upgraded to focal on 2020-05-25 (0 days ago)
  dmi.bios.date: 07/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.80
  dmi.board.name: X370 Taichi
  dmi.board.vendor: ASRock
  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.:bvrP4.80:bd07/18/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-25 Thread Simon Repp
I did a clean install of 20.04 on my machine (which has been running
Ubuntu, most recently 19.04, without issue so far) and I am facing this
- importantly in my case it is NOT a harmless message but actually
preventing boot - I am stuck in the initramfs prompt.

I tried the suggested workaround of editing "/etc/initramfs-
tools/initramfs.conf" to specify COMPRESS=gzip instead of COMPRESS=lz4
to no avail (issue remains on next boot attempt).

I can not run try elsewhere also suggested "sudo update-initramfs -u"
command because as I understand it I am lacking the proper context in
which this would be run - in the initramfs prompt I can not run it (or
at least don't know how), and if I boot into live ubuntu (which works
perfectly - this is also where I was able to edit the initramfs.conf
file) I could probably run this although it would be in the wrong
context (that of the live ubuntu, not the one on disk I installed
previously).

Thanks everyone for the effort to resolve this! I'll run 19.10 or
another distro in the meantime and hope this can be resolved soon.

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1878945] Re: crash slapd after update

2020-05-25 Thread John
debconf option was not enable before the upgrade...

under /var/backups/*
slapd-2.4.42+dfsg-2ubuntu3.1
slapd-2.4.42+dfsg-2ubuntu3.2
slapd-2.4.42+dfsg-2ubuntu3.6
unknown-2.4.42+dfsg-2ubuntu3.8.ldapdb

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

Title:
  crash slapd after update

Status in openldap package in Ubuntu:
  Triaged

Bug description:
  hi,
  after update slapd to version 2.4.42+dfsg-2ubuntu3.8 I get not working ldap 
auth service;

  perform: slaptest -f /etc/ldap/slapd.conf -F /etc/ldap/slapd.d/ and
  get:

  5ebeb45f hdb_db_open: database "dc=myBase": 
db_open(/var/lib/ldap/id2entry.bdb) failed: No such file or directory (2).
  5ebeb45f backend_startup_one (type=hdb, suffix="dc=myBase"): bi_db_open 
failed! (2)
  slap_startup failed (test would succeed using the -u switch)

  journalctl -xe

  -- Unit slapd.service has finished starting up.
  --
  -- The start-up result is done.
  May 15 18:25:33 srv sshd[3917]: Connection closed by IP port PORT1 [preauth]
  May 15 18:26:32 srv sshd[3919]: Connection closed by IP port PORT2 [preauth]
  May 15 18:27:21 srv systemd[1]: Starting Daily apt download activities...
  -- Subject: Unit apt-daily.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit apt-daily.service has begun starting up.
  May 15 18:27:23 srv systemd[1]: Started Daily apt download activities.
  -- Subject: Unit apt-daily.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit apt-daily.service has finished starting up.
  --
  -- The start-up result is done.
  May 15 18:27:32 srv sshd[3987]: Connection closed by IP port PORT3 [preauth]
  May 15 18:28:04 srv systemd[1]: Stopping LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...
  -- Subject: Unit slapd.service has begun shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has begun shutting down.
  May 15 18:28:04 srv slapd[4020]:  * Stopping OpenLDAP slapd
  May 15 18:28:14 srv slapd[4020]:...fail!
  May 15 18:28:14 svr systemd[1]: slapd.service: Control process exited, 
code=exited status=1
  May 15 18:28:14 srv systemd[1]: Stopped LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol).
  -- Subject: Unit slapd.service has finished shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has finished shutting down.
  May 15 18:28:14 srv systemd[1]: slapd.service: Unit entered failed state.
  May 15 18:28:14 srv systemd[1]: slapd.service: Failed with result 'exit-code'.
  May 15 18:28:14 srv systemd[1]: Starting LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...
  -- Subject: Unit slapd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has begun starting up.
  May 15 18:28:15 srv slapd[4029]:  * Starting OpenLDAP slapd
  May 15 18:28:15 srv slapd[4029]:...done.
  May 15 18:28:15 srv systemd[1]: Started LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol).
  -- Subject: Unit slapd.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has finished starting up.
  --
  -- The start-up result is done.

  OS: Ubuntu 16.04.6 LTS

  help, please!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1878945/+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 1880536] Re: HDMI port is not working

2020-05-25 Thread Daniel van Vugt
If you have the AMD Radeon option then it's likely the HDMI port is
wired to that. But that GPU is also likely turned off by default so you
will also be missing the HDMI port option. To fix that please try
checking your BIOS and turn on both GPUs.

But there's a second problem here which seems more likely... The kernel
doesn't seem to recognise your very new Intel GPU. So even if the laptop
only has a single GPU the HDMI port would be missing :) To fix that
please install either:

  * https://releases.ubuntu.com/20.04/ or

  * https://releases.ubuntu.com/18.04.4/


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

** Changed in: linux (Ubuntu)
   Status: New => Won't Fix

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

Title:
  HDMI port is not working

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  HDMI port is not working and I don't the second secreen in Display
  settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 11:13:51 2020
  DistUpgraded: 2020-05-22 16:25:45,628 DEBUG /openCache(), new cache size 97390
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:5079]
  InstallationDate: Installed on 2020-04-02 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20RD004FMH
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic 
root=/dev/mapper/username--vg-root ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-05-22 (2 days ago)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R16ET21W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20RD004FMH
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR16ET21W(1.07):bd11/29/2019:svnLENOVO:pn20RD004FMH:pvrThinkPadE15:rvnLENOVO:rn20RD004FMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E15
  dmi.product.name: 20RD004FMH
  dmi.product.version: ThinkPad E15
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880536/+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 1880536] [NEW] HDMI port is not working

2020-05-25 Thread Ghassan
Public bug reported:

HDMI port is not working and I don't the second secreen in Display
settings.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
Uname: Linux 4.15.0-101-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 11:13:51 2020
DistUpgraded: 2020-05-22 16:25:45,628 DEBUG /openCache(), new cache size 97390
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:5079]
InstallationDate: Installed on 2020-04-02 (52 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20RD004FMH
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic 
root=/dev/mapper/username--vg-root ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2020-05-22 (2 days ago)
dmi.bios.date: 11/29/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R16ET21W (1.07 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20RD004FMH
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR16ET21W(1.07):bd11/29/2019:svnLENOVO:pn20RD004FMH:pvrThinkPadE15:rvnLENOVO:rn20RD004FMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E15
dmi.product.name: 20RD004FMH
dmi.product.version: ThinkPad E15
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1880536

Title:
  HDMI port is not working

Status in xorg package in Ubuntu:
  New

Bug description:
  HDMI port is not working and I don't the second secreen in Display
  settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 11:13:51 2020
  DistUpgraded: 2020-05-22 16:25:45,628 DEBUG /openCache(), new cache size 97390
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:5079]
  InstallationDate: Installed on 2020-04-02 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20RD004FMH
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic 
root=/dev/mapper/username--vg-root ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-05-22 (2 days ago)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R16ET21W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20RD004FMH
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR16ET21W(1.07):bd11/29/2019:svnLENOVO:pn20RD004FMH:pvrThinkPadE15:rvnLENOVO:rn20RD004FMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E15
  dmi.product.name: 20RD004FMH
  dmi.product.version: ThinkPad E15
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: 

[Touch-packages] [Bug 1880410] Re: pulseaudio doesn't enforce sample rate set in daemon.conf

2020-05-25 Thread Daniel van Vugt
** Also affects: pulseaudio via
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/897
   Importance: Unknown
   Status: Unknown

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

Title:
  pulseaudio doesn't enforce sample rate set in daemon.conf

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

Bug description:
  Before submitting this bugreport I've went through the daemon.conf man page 
and the pulseaudio documentation, but have not found a solution to my problem.
  I've moved from Debian stable with
  pulseaudio version 12.2-4+deb10u1 to Kubuntu 20.04 with
  pulseaudio version 13.99.1-1ubuntu3.2.
  I'm experiencing cracking issues on external USB audio device Xonar U3 while 
listening to certain audio sources (system sounds included). This issue doesn't 
happen when using my laptop's internal audio device.
  Output of 'cat /proc/asound/card2/stream0' without audio stream running:
  C-Media Electronics Inc. USB Advanced Audio Device at usb-:00:14.0-2, 
full  : USB Audio

  Playback:
Status: Running
Interface = 1
Altset = 1
Packet Size = 200
Momentary freq = 44100 Hz (0x2c.199a)
Interface 1
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 1 OUT (ADAPTIVE)
Rates: 8000, 16000, 44100, 48000
Bits: 16

  Capture:
Status: Stop
Interface 2
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 2 IN (ASYNC)
Rates: 8000, 16000, 44100, 48000
Bits: 16
  The following behaviour happens with default settings in 
/etc/pulse/daemon.conf:
  Xonar U3 plugged in, firefox running:
Momentary freq = 48000 Hz (0x30.)

  Xonar U3 plugged in, Clementine/Strawberry audio player running:
Momentary freq = 44100 Hz (0x2c.199a)

  Xonar U3 plugged in with Deadbeef set to override sample rate to 48kHz:
Momentary freq = 48000 Hz (0x30.)
  I've modified the daemon.conf as follows:
  ; default-sample-format = s16le #no change on this line, this is 
corresponding with the format the usb audio device suggests to be using
  ; default-sample-rate = 48000
  ; alternate-sample-rate = 48000
  However, when running video or audio sources with 44100Hz audio, applications 
 do not respect the default-sample-rate and Momentary freq reports 44100Hz, 
while other sources either send 48kHz by default or have no problem respecting 
the setting (I've tried the game Into the Breach, VLC running 48kHz video and 
audio files).
  Complete /etc/pulse/daemon.conf contents:
  https://gist.github.com/zelmor/f224e6e4d300241e8431d3258e777e73
  Checking syslog doesn't indicate any errors either, gist:
  https://gist.github.com/zelmor/5e59094be4d90ffa9e0ff6275594e370
  ==Workarounds attempted==

  Modifying /etc/pulse/default.pa to include:

  load-module module-udev-detect tsched=0
  Even after killing pulseaudio, this did not resolve anything. It 
also doesn't look like a good overall solution to the problem.

  Modifying daemon.conf to:

  ; resample-method = src-sinc-best-quality
  ; avoid-resampling = true
  Did not fix the issue.
  It is not possible to roll back PA to a previous version in Kubuntu 20.04 
without breaking dependencies of the Plasma desktop, so this was not attempted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  zelmor 1994 F pulseaudio
   /dev/snd/controlC1:  zelmor 1994 F pulseaudio
   /dev/snd/controlC0:  zelmor 1994 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun May 24 16:30:11 2020
  InstallationDate: Installed on 2020-04-28 (25 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET46WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7S11H00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20B7S11H00:pvrThinkPadT450:rvnLENOVO:rn20B7S11H00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20B7S11H00
  dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.daemon.conf: [modified]
  

[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)

2020-05-25 Thread Noctis Bennington
Talked about this topic on
https://forums.developer.nvidia.com/t/ubuntu-20-04-second-monitor-
doesnt-work-ubuntu-and-nvidia-settings-detects-it/124380/13

generix said maybe's a problem with the Intel GPU Firmware.

** Also affects: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mesa-utils (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS
  Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in mesa-utils package in Ubuntu:
  New
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with noveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+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 1878351] Re: System shutdown directly by pressing power button and releasing immediately

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

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

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

Title:
  System shutdown directly by pressing power button and releasing
  immediately

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  kchsieh@kchsieh-laptop:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS (fossa-bulbasaur X23)
  Release:  20.04

  kchsieh@kchsieh-laptop:~$ apt-cache policy systemd
  systemd:
Installed: 245.4-4ubuntu3
Candidate: 245.4-4ubuntu3
Version table:
   *** 245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Expect: When press the button, the endSeesionDialog should show up.
  Actual: The system shutdown directly.

  When the issue happend:
  endSessionDialog is not triggered immediately after the first power button 
event, but triggered after the second power button event.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-10 (3 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: systemd 245.4-4ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.1.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878351/+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 1878351] Re: System shutdown directly by pressing power button and releasing immediately

2020-05-25 Thread Yuan-Chen Cheng
** Changed in: oem-priority
   Importance: Undecided => High

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

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

Title:
  System shutdown directly by pressing power button and releasing
  immediately

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  kchsieh@kchsieh-laptop:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS (fossa-bulbasaur X23)
  Release:  20.04

  kchsieh@kchsieh-laptop:~$ apt-cache policy systemd
  systemd:
Installed: 245.4-4ubuntu3
Candidate: 245.4-4ubuntu3
Version table:
   *** 245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Expect: When press the button, the endSeesionDialog should show up.
  Actual: The system shutdown directly.

  When the issue happend:
  endSessionDialog is not triggered immediately after the first power button 
event, but triggered after the second power button event.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-10 (3 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: systemd 245.4-4ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.1.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878351/+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 1878351] Re: System shutdown directly by pressing power button and releasing immediately

2020-05-25 Thread Kai-Chuan Hsieh
It is quite special that one power button pressed, but systemd-logind
receive two power button pressed event consecutively.

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

Title:
  System shutdown directly by pressing power button and releasing
  immediately

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  kchsieh@kchsieh-laptop:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS (fossa-bulbasaur X23)
  Release:  20.04

  kchsieh@kchsieh-laptop:~$ apt-cache policy systemd
  systemd:
Installed: 245.4-4ubuntu3
Candidate: 245.4-4ubuntu3
Version table:
   *** 245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Expect: When press the button, the endSeesionDialog should show up.
  Actual: The system shutdown directly.

  When the issue happend:
  endSessionDialog is not triggered immediately after the first power button 
event, but triggered after the second power button event.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-10 (3 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: systemd 245.4-4ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.1.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878351/+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 1529152] Re: slow completion for systemd units

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.41

---
systemd (237-3ubuntu10.41) bionic; urgency=medium

  [ Dan Streetman ]
  * d/p/lp1867375/0001-network-Allow-to-configure-GW-even-UseRoutes-false.patch,

d/p/lp1867375/0002-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,

d/p/lp1867375/0003-network-change-UseGateway-default-to-UseRoutes-setti.patch:
- Move gateway ignoring from UseRoutes= to UseGateway= (LP: #1867375)
   * 
d/p/lp1873607/0002-core-make-sure-to-restore-the-control-command-id-too.patch:
 - Avoid segfault during serialization (LP: #1873607)
   * d/p/lp1529152/0001-bash-completion-systemctl-use-systemctl-no-pager.patch,
 
d/p/lp1529152/0002-bash-completion-systemctl-pass-current-partial-unit-.patch,
 
d/p/lp1529152/0003-shell-completion-systemctl-pass-current-word-to-all-.patch,
 
d/p/lp1529152/0004-bash-completion-systemctl-re-implement-__filter_unit.patch,
 d/p/lp1529152/0005-strip-value-from-property-names.patch:
 - fix slow systemctl tab completion (LP: #1529152)
   * d/p/lp1877159-networkd-fix-attribute-length-for-wireguard-10380.patch:
 - avoid kernel err msg setting wireguard param (LP: #1877159)

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

 -- Heitor Alves de Siqueira   Sun, 03 May 2020
11:30:25 +

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

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

Title:
  slow completion for systemd units

Status in systemd:
  Fix Released
Status in bash-completion package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in bash-completion source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Won't Fix
Status in bash-completion source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [impact]

  systemctl tab completion is annoyingly slow.

  [test case]

  on a bionic system:

  $ systemctl status systemd-

  any unit can be used, or even  before specifying any unit name
  chars.

  That will hang for sometimes a few seconds.

  [regression potential]

  this updates systemctl bash completion, so any regression would likely
  result in systemctl command misbehaving; most likely, failure to tab-
  complete.

  [scope]

  This is needed for Bionic and Xenial, however I am not currently
  planning to fix this for Xenial.

  This is fixed by upstream commit
  f28255e2d5695b0d060558ff8cbb2b526fc94cc0 and a few other previous
  commits, which are all included starting in v240, so this is fixed
  already in Eoan and later.

  [original description]

  Pressing Tab after entering `sudo systemctl status
  [existing service name without .service suffix]` into console it takes
  up to 5 seconds until the auto-completion completes. Until then the
  cursor can't be moved.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bash-completion 1:2.1-4.1ubuntu2
  Uname: Linux 4.2.5-040205-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Thu Dec 24 21:04:41 2015
  InstallationDate: Installed on 2015-04-20 (248 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: bash-completion
  UpgradeStatus: Upgraded to wily on 2015-10-26 (59 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1529152/+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 1529152] Update Released

2020-05-25 Thread Łukasz Zemczak
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  slow completion for systemd units

Status in systemd:
  Fix Released
Status in bash-completion package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in bash-completion source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Won't Fix
Status in bash-completion source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [impact]

  systemctl tab completion is annoyingly slow.

  [test case]

  on a bionic system:

  $ systemctl status systemd-

  any unit can be used, or even  before specifying any unit name
  chars.

  That will hang for sometimes a few seconds.

  [regression potential]

  this updates systemctl bash completion, so any regression would likely
  result in systemctl command misbehaving; most likely, failure to tab-
  complete.

  [scope]

  This is needed for Bionic and Xenial, however I am not currently
  planning to fix this for Xenial.

  This is fixed by upstream commit
  f28255e2d5695b0d060558ff8cbb2b526fc94cc0 and a few other previous
  commits, which are all included starting in v240, so this is fixed
  already in Eoan and later.

  [original description]

  Pressing Tab after entering `sudo systemctl status
  [existing service name without .service suffix]` into console it takes
  up to 5 seconds until the auto-completion completes. Until then the
  cursor can't be moved.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bash-completion 1:2.1-4.1ubuntu2
  Uname: Linux 4.2.5-040205-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Thu Dec 24 21:04:41 2015
  InstallationDate: Installed on 2015-04-20 (248 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: bash-completion
  UpgradeStatus: Upgraded to wily on 2015-10-26 (59 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1529152/+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 1876600] Update Released

2020-05-25 Thread Łukasz Zemczak
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  cookie overruns can cause org.freedesktop.systemd1 dbus to hang

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Long-running services overflow the sd_bus->cookie counter, causing further 
communication with org.freedesktop.systemd1 to stall.

  [Description]
  Systemd dbus messages include a "cookie" value to uniquely identify them in 
their bus context. This value is obtained from the bus header, and incremented 
for each exchanged message in the same bus object. For services that run for 
longer periods of time and keep communicating through dbus, it's possible to 
overflow the cookie value, causing further messages to the 
org.freedesktop.systemd1 dbus to fail. This can lead to these services becoming 
unresponsive, as they get stuck trying to communicate with invalid bus cookie 
values.

  This issue has been fixed upstream by the commit below:
  -  sd-bus: deal with cookie overruns (1f82f5bb4237)

  $ git describe --contains 1f82f5bb4237
  v242-rc1~228

  $ rmadison systemd
   systemd | 229-4ubuntu4 | xenial  | source, ...
   systemd | 229-4ubuntu21.27 | xenial-security | source, ...
   systemd | 229-4ubuntu21.27 | xenial-updates  | source, ...
   systemd | 229-4ubuntu21.28 | xenial-proposed | source, ...
   systemd | 237-3ubuntu10| bionic  | source, ...
   systemd | 237-3ubuntu10.38 | bionic-security | source, ...
   systemd | 237-3ubuntu10.39 | bionic-updates  | source, ...
   systemd | 237-3ubuntu10.40 | bionic-proposed | source, ... <
   systemd | 242-7ubuntu3 | eoan| source, ...

  Releases starting with Eoan already have this fix.

  [Test Case]
  There doesn't seem to be an easy test case for this, as the cookie values 
start at zero and won't overflow until (1<<32). There have been reports from 
users hitting this on Kubernetes clusters continuously running for longer 
periods (~5 months).
  Using GDB, we can construct an artificial test case to test the cookie 
overflow. The test case below performs the following steps:

  1. Create a new system bus object through sd_bus_default_system()
  2. Allocate and append a new method_call message to the bus
  3. Send the message through sd_bus_call()
  4. Handle the response message and free up the message objects

  It's essentially the example code from the
  sd_bus_message_new_method_call() manpage, with minor modifications:
  this is done continuously, to keep incrementing the bus cookie value.
  We step in with GDB when it reaches 0x1, and set its value to
  0xff00 which then causes the test program to fail shortly
  afterwards. An example test run of an impacted system:

  ubuntu@bionic:~$ gcc -Wall test.c -o cookie -lsystemd -g
  ubuntu@bionic:~$ gdb --batch --command=test.gdb --args ./cookie
  Breakpoint 1 at 0xe61: file test.c, line 38.
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  (16s) cookie: 0x0001reply-cookie: 0x0001

  Breakpoint 1, print_unit_path (bus=0x55757290) at test.c:38
  38  r = sd_bus_message_new_method_call(bus, ,
  $1 = 0x1
  $2 = 0xff00
  Call failed: Operation not supported
  Sleeping and retrying...
  Call failed: Invalid argument
  Assertion 'm->n_ref > 0' failed at 
../src/libsystemd/sd-bus/bus-message.c:934, function sd_bus_message_unref(). 
Aborting.

  Program received signal SIGABRT, Aborted.
  __GI_raise (sig=sig@entry=0x6) at ../sysdeps/unix/sysv/linux/raise.c:51
  51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.

  To compile and debug the test case above, libsystemd-dev and 
libsystemd0-dbgsym are required.
  Both test.c and test.gdb source code are attached to this LP bug.

  [Regression Potential]
  This fix introduces some changes in the way cookie incrementation is handled. 
We now have a reduced number of available values, since the patch makes use of 
a high order bit to indicate whether we have overflowed or not. Potential 
issues could arise from two distinct messages repeating the cookie value, or 
from us not handling the cookie reuse properly. In practice, this shouldn't 
cause serious problems as most dbus messages 

[Touch-packages] [Bug 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.41

---
systemd (237-3ubuntu10.41) bionic; urgency=medium

  [ Dan Streetman ]
  * d/p/lp1867375/0001-network-Allow-to-configure-GW-even-UseRoutes-false.patch,

d/p/lp1867375/0002-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,

d/p/lp1867375/0003-network-change-UseGateway-default-to-UseRoutes-setti.patch:
- Move gateway ignoring from UseRoutes= to UseGateway= (LP: #1867375)
   * 
d/p/lp1873607/0002-core-make-sure-to-restore-the-control-command-id-too.patch:
 - Avoid segfault during serialization (LP: #1873607)
   * d/p/lp1529152/0001-bash-completion-systemctl-use-systemctl-no-pager.patch,
 
d/p/lp1529152/0002-bash-completion-systemctl-pass-current-partial-unit-.patch,
 
d/p/lp1529152/0003-shell-completion-systemctl-pass-current-word-to-all-.patch,
 
d/p/lp1529152/0004-bash-completion-systemctl-re-implement-__filter_unit.patch,
 d/p/lp1529152/0005-strip-value-from-property-names.patch:
 - fix slow systemctl tab completion (LP: #1529152)
   * d/p/lp1877159-networkd-fix-attribute-length-for-wireguard-10380.patch:
 - avoid kernel err msg setting wireguard param (LP: #1877159)

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

 -- Heitor Alves de Siqueira   Sun, 03 May 2020
11:30:25 +

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

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released
Status in netplan.io source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Fix Released
Status in netplan.io source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in netplan.io source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  the networkd UseRoutes parameter allowed ignoring all routes provided
  by a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.

  The systemd in Focal unfortunately has part of the upstream code; it
  no longer ignores the gateway route when UseRoutes=false is specified,
  but also it does not include the UseGateway parameter.

  Before Focal, networkd did not allow ignoring dhcpv4 routes and the
  gateway separately; the UseRoutes= parameter either used, or ignored,
  both.  This is why upstream added the UseGateway= paramter, which
  should be backported to allow control of ignoring the dhcpv4 routes
  and gateway separately.

  [test case]

  In Focal, bug 1872589 has a good test case netplan config, but a very
  quick test can be done with the networkd config:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false

  this results in the system incorrectly setting a route via the default
  gateway:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  Before Focal, the above test case shows "correct" behavior, but there
  is no way to ignore the dhcpv4 routes but use the dhcpv4 gateway.
  This pre-Focal, the test case would be to use the UseGateway=
  parameter, e.g.:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  UseGateway=true

  which *should* result in the default gateway being configured:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  [regression potential]

  Any regression would likely involve incorrect setting, or ignoring, of
  dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the
  dhcpv4-provided gateway.

  [scope]

  This is fixed by these upstream PRs:
  https://github.com/systemd/systemd/pull/15443
  https://github.com/systemd/systemd/pull/15136
  https://github.com/systemd/systemd/pull/14983

  Parts of all those PRs are required in Focal, Eoan, 

[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.41

---
systemd (237-3ubuntu10.41) bionic; urgency=medium

  [ Dan Streetman ]
  * d/p/lp1867375/0001-network-Allow-to-configure-GW-even-UseRoutes-false.patch,

d/p/lp1867375/0002-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,

d/p/lp1867375/0003-network-change-UseGateway-default-to-UseRoutes-setti.patch:
- Move gateway ignoring from UseRoutes= to UseGateway= (LP: #1867375)
   * 
d/p/lp1873607/0002-core-make-sure-to-restore-the-control-command-id-too.patch:
 - Avoid segfault during serialization (LP: #1873607)
   * d/p/lp1529152/0001-bash-completion-systemctl-use-systemctl-no-pager.patch,
 
d/p/lp1529152/0002-bash-completion-systemctl-pass-current-partial-unit-.patch,
 
d/p/lp1529152/0003-shell-completion-systemctl-pass-current-word-to-all-.patch,
 
d/p/lp1529152/0004-bash-completion-systemctl-re-implement-__filter_unit.patch,
 d/p/lp1529152/0005-strip-value-from-property-names.patch:
 - fix slow systemctl tab completion (LP: #1529152)
   * d/p/lp1877159-networkd-fix-attribute-length-for-wireguard-10380.patch:
 - avoid kernel err msg setting wireguard param (LP: #1877159)

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

 -- Heitor Alves de Siqueira   Sun, 03 May 2020
11:30:25 +

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

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

Title:
  systemd segv coredump, reboot/poweroff ignored.

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  during systemctl daemon-reload, systemd sometimes segfaults while
  serializing a service.

  [test case]

  problem is intermittent, but the upstream bug suggests a reproducer.
  Also see original description.

  [regression potential]

  this adjusts serialization, so any regression would likely occur
  during serialization/deserialization, e.g. at daemon-reload.

  [scope]

  This is needed for Bionic and later.

  this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41
  which is included starting in v234.  The commit to fix it is
  e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in
  any release.

  The PR to fix this is https://github.com/systemd/systemd/pull/15546

  [other info]

  there is an additional PR that further avoids the error, but has not yet been 
accepted, and may not be accepted as it may not be necessary.
  https://github.com/systemd/systemd/pull/15370

  [original description]

  Proximate syslog:

  Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running:  ip -all netns 
del
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /r
  un/dbus/system_bus_socket; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/sssd.pid → /run/sssd.pid; plea
  se update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/oddjobd.pid → /run/oddjobd.p
  id; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/fail2ban/fail2ban.pid → /r
  un/fail2ban/fail2ban.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/certmonger.pid → /run/cer
  tmonger.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: Reloading.
  Apr 18 16:26:56 gate2 kernel: [  454.966336] systemd[1]: segfault at 50 ip 
55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000]
  Apr 18 16:26:56 gate2 kernel: [  454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 
00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 
1f 84 00 00 00 00 00 <48
  > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d
  Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK:   systemctl 
daemon-reload
  Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running:  systemctl 
enable rssmonitor.service
  

[Touch-packages] [Bug 1876600] Re: cookie overruns can cause org.freedesktop.systemd1 dbus to hang

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.41

---
systemd (237-3ubuntu10.41) bionic; urgency=medium

  [ Dan Streetman ]
  * d/p/lp1867375/0001-network-Allow-to-configure-GW-even-UseRoutes-false.patch,

d/p/lp1867375/0002-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,

d/p/lp1867375/0003-network-change-UseGateway-default-to-UseRoutes-setti.patch:
- Move gateway ignoring from UseRoutes= to UseGateway= (LP: #1867375)
   * 
d/p/lp1873607/0002-core-make-sure-to-restore-the-control-command-id-too.patch:
 - Avoid segfault during serialization (LP: #1873607)
   * d/p/lp1529152/0001-bash-completion-systemctl-use-systemctl-no-pager.patch,
 
d/p/lp1529152/0002-bash-completion-systemctl-pass-current-partial-unit-.patch,
 
d/p/lp1529152/0003-shell-completion-systemctl-pass-current-word-to-all-.patch,
 
d/p/lp1529152/0004-bash-completion-systemctl-re-implement-__filter_unit.patch,
 d/p/lp1529152/0005-strip-value-from-property-names.patch:
 - fix slow systemctl tab completion (LP: #1529152)
   * d/p/lp1877159-networkd-fix-attribute-length-for-wireguard-10380.patch:
 - avoid kernel err msg setting wireguard param (LP: #1877159)

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

 -- Heitor Alves de Siqueira   Sun, 03 May 2020
11:30:25 +

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

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

Title:
  cookie overruns can cause org.freedesktop.systemd1 dbus to hang

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Long-running services overflow the sd_bus->cookie counter, causing further 
communication with org.freedesktop.systemd1 to stall.

  [Description]
  Systemd dbus messages include a "cookie" value to uniquely identify them in 
their bus context. This value is obtained from the bus header, and incremented 
for each exchanged message in the same bus object. For services that run for 
longer periods of time and keep communicating through dbus, it's possible to 
overflow the cookie value, causing further messages to the 
org.freedesktop.systemd1 dbus to fail. This can lead to these services becoming 
unresponsive, as they get stuck trying to communicate with invalid bus cookie 
values.

  This issue has been fixed upstream by the commit below:
  -  sd-bus: deal with cookie overruns (1f82f5bb4237)

  $ git describe --contains 1f82f5bb4237
  v242-rc1~228

  $ rmadison systemd
   systemd | 229-4ubuntu4 | xenial  | source, ...
   systemd | 229-4ubuntu21.27 | xenial-security | source, ...
   systemd | 229-4ubuntu21.27 | xenial-updates  | source, ...
   systemd | 229-4ubuntu21.28 | xenial-proposed | source, ...
   systemd | 237-3ubuntu10| bionic  | source, ...
   systemd | 237-3ubuntu10.38 | bionic-security | source, ...
   systemd | 237-3ubuntu10.39 | bionic-updates  | source, ...
   systemd | 237-3ubuntu10.40 | bionic-proposed | source, ... <
   systemd | 242-7ubuntu3 | eoan| source, ...

  Releases starting with Eoan already have this fix.

  [Test Case]
  There doesn't seem to be an easy test case for this, as the cookie values 
start at zero and won't overflow until (1<<32). There have been reports from 
users hitting this on Kubernetes clusters continuously running for longer 
periods (~5 months).
  Using GDB, we can construct an artificial test case to test the cookie 
overflow. The test case below performs the following steps:

  1. Create a new system bus object through sd_bus_default_system()
  2. Allocate and append a new method_call message to the bus
  3. Send the message through sd_bus_call()
  4. Handle the response message and free up the message objects

  It's essentially the example code from the
  sd_bus_message_new_method_call() manpage, with minor modifications:
  this is done continuously, to keep incrementing the bus cookie value.
  We step in with GDB when it reaches 0x1, and set its value to
  0xff00 which then causes the test program to fail shortly
  afterwards. An example test run of an impacted system:

  ubuntu@bionic:~$ gcc -Wall test.c -o cookie -lsystemd -g
  ubuntu@bionic:~$ gdb --batch --command=test.gdb --args ./cookie
  Breakpoint 1 at 0xe61: file test.c, line 38.
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  (16s) cookie: 0x0001reply-cookie: 0x0001

  Breakpoint 1, print_unit_path (bus=0x55757290) at test.c:38
  38  r = sd_bus_message_new_method_call(bus, ,
  $1 = 0x1
  $2 = 0xff00
  Call 

[Touch-packages] [Bug 1877159] Update Released

2020-05-25 Thread Łukasz Zemczak
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  netlink: 'systemd-network': attribute type 5 has an invalid length.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  systemd-networkd uses incorrect netlink attribute length for
  wireguard's persistent keepalive interval, which logs error messages
  from the kernel, and may incorrectly set the parameter.

  [test case]

  Only 1 Bionic VM is required to reproduce the problem:

  $ lxc launch images:ubuntu/bionic --vm -c security.secureboot=false foo
  $ sleep 10 # allow booting
  $ lxc exec foo -- apt install -y software-properties-common
  $ lxc exec foo -- add-apt-repository -y ppa:wireguard/wireguard
  $ lxc exec foo -- apt install -y wireguard-tools

  $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.netdev
  # foo
  [NetDev]
  Name=wg0
  Kind=wireguard

  [WireGuard]
  ListenPort=
  PrivateKey=cBkljQSKhtEe/U8GZmCAk2MBbKWL4TLC9PVtbMFyCVQ=

  [WireGuardPeer]
  PublicKey=emfIuZ3hZ+AnWIrKex/EqCp2mfzip8AxJu6RuweyRGc=
  AllowedIPs=192.168.255.2
  Endpoint=bar.lxd:
  EOF

  $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.network
  # foo
  [Match]
  Name=wg0

  [Network]
  Address=192.168.255.1/24
  EOF

  $ lxc exec foo -- systemctl restart systemd-networkd

  # notice the invalid length in dmesg
  $ lxc exec foo -- journalctl -kn 8
  -- Logs begin at Mon 2020-05-11 16:56:40 UTC, end at Mon 2020-05-11 17:03:46 
UTC. --
  May 11 16:58:25 foo kernel: nf_tables: (c) 2007-2009 Patrick McHardy 

  May 11 17:01:57 foo kernel: PKCS#7 signature not signed with a trusted key
  May 11 17:01:57 foo kernel: wireguard: module verification failed: signature 
and/or required key missing - tainting kernel
  May 11 17:01:57 foo kernel: wireguard: WireGuard 1.0.20200429 loaded. See 
www.wireguard.com for information.
  May 11 17:01:57 foo kernel: wireguard: Copyright (C) 2015-2019 Jason A. 
Donenfeld . All Rights Reserved.
  May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.
  May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.
  May 11 17:02:23 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.

  [regression potential]

  this adjusts the length of the specific netlink parameter, so any
  regression would likely relate to incorrectly setting the persistent
  keepalive interval parameter, or failure to set the parameter.

  [scope]

  this is needed only for Bionic.

  this was fixed upstream in commit
  7d0b26a027118ca063780421cb31c74e9d2664ee which was first included in
  v240, so this is fixed in Eoan and later.  Xenial does not include
  support for wireguard, so this does not apply there.

  [original description]

  This morning, our 2 Bionic machine configured with the wireguard's PPA
  and using systemd-networkd to configure the wireguard tunnel started
  misbehaving. Why this started just now is unclear ATM but their dmesg
  was filled with this:

  validate_nla: 100 callbacks suppressed
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.

  Folks in #systemd mentioned
  https://github.com/systemd/systemd/issues/11575 which points to 2
  commits missing from Bionic's systemd version:

  
https://github.com/systemd/systemd/commit/7d0b26a027118ca063780421cb31c74e9d2664ee
  
https://github.com/systemd/systemd/commit/624a47694cad4c87b2e807c32db656f3e9d679c5

  Focal's systemd have the above commits. Would it be possible to
  backport those 2 commits to Bionic?

  Additional information:


[Touch-packages] [Bug 1877159] Re: netlink: 'systemd-network': attribute type 5 has an invalid length.

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.41

---
systemd (237-3ubuntu10.41) bionic; urgency=medium

  [ Dan Streetman ]
  * d/p/lp1867375/0001-network-Allow-to-configure-GW-even-UseRoutes-false.patch,

d/p/lp1867375/0002-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,

d/p/lp1867375/0003-network-change-UseGateway-default-to-UseRoutes-setti.patch:
- Move gateway ignoring from UseRoutes= to UseGateway= (LP: #1867375)
   * 
d/p/lp1873607/0002-core-make-sure-to-restore-the-control-command-id-too.patch:
 - Avoid segfault during serialization (LP: #1873607)
   * d/p/lp1529152/0001-bash-completion-systemctl-use-systemctl-no-pager.patch,
 
d/p/lp1529152/0002-bash-completion-systemctl-pass-current-partial-unit-.patch,
 
d/p/lp1529152/0003-shell-completion-systemctl-pass-current-word-to-all-.patch,
 
d/p/lp1529152/0004-bash-completion-systemctl-re-implement-__filter_unit.patch,
 d/p/lp1529152/0005-strip-value-from-property-names.patch:
 - fix slow systemctl tab completion (LP: #1529152)
   * d/p/lp1877159-networkd-fix-attribute-length-for-wireguard-10380.patch:
 - avoid kernel err msg setting wireguard param (LP: #1877159)

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

 -- Heitor Alves de Siqueira   Sun, 03 May 2020
11:30:25 +

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

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

Title:
  netlink: 'systemd-network': attribute type 5 has an invalid length.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  systemd-networkd uses incorrect netlink attribute length for
  wireguard's persistent keepalive interval, which logs error messages
  from the kernel, and may incorrectly set the parameter.

  [test case]

  Only 1 Bionic VM is required to reproduce the problem:

  $ lxc launch images:ubuntu/bionic --vm -c security.secureboot=false foo
  $ sleep 10 # allow booting
  $ lxc exec foo -- apt install -y software-properties-common
  $ lxc exec foo -- add-apt-repository -y ppa:wireguard/wireguard
  $ lxc exec foo -- apt install -y wireguard-tools

  $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.netdev
  # foo
  [NetDev]
  Name=wg0
  Kind=wireguard

  [WireGuard]
  ListenPort=
  PrivateKey=cBkljQSKhtEe/U8GZmCAk2MBbKWL4TLC9PVtbMFyCVQ=

  [WireGuardPeer]
  PublicKey=emfIuZ3hZ+AnWIrKex/EqCp2mfzip8AxJu6RuweyRGc=
  AllowedIPs=192.168.255.2
  Endpoint=bar.lxd:
  EOF

  $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.network
  # foo
  [Match]
  Name=wg0

  [Network]
  Address=192.168.255.1/24
  EOF

  $ lxc exec foo -- systemctl restart systemd-networkd

  # notice the invalid length in dmesg
  $ lxc exec foo -- journalctl -kn 8
  -- Logs begin at Mon 2020-05-11 16:56:40 UTC, end at Mon 2020-05-11 17:03:46 
UTC. --
  May 11 16:58:25 foo kernel: nf_tables: (c) 2007-2009 Patrick McHardy 

  May 11 17:01:57 foo kernel: PKCS#7 signature not signed with a trusted key
  May 11 17:01:57 foo kernel: wireguard: module verification failed: signature 
and/or required key missing - tainting kernel
  May 11 17:01:57 foo kernel: wireguard: WireGuard 1.0.20200429 loaded. See 
www.wireguard.com for information.
  May 11 17:01:57 foo kernel: wireguard: Copyright (C) 2015-2019 Jason A. 
Donenfeld . All Rights Reserved.
  May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.
  May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.
  May 11 17:02:23 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.

  [regression potential]

  this adjusts the length of the specific netlink parameter, so any
  regression would likely relate to incorrectly setting the persistent
  keepalive interval parameter, or failure to set the parameter.

  [scope]

  this is needed only for Bionic.

  this was fixed upstream in commit
  7d0b26a027118ca063780421cb31c74e9d2664ee which was first included in
  v240, so this is fixed in Eoan and later.  Xenial does not include
  support for wireguard, so this does not apply there.

  [original description]

  This morning, our 2 Bionic machine configured with the wireguard's PPA
  and using systemd-networkd to configure the wireguard tunnel started
  misbehaving. Why this started just now is unclear ATM but their dmesg
  was filled with this:

  validate_nla: 100 callbacks suppressed
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute 

[Touch-packages] [Bug 1877159] Re: netlink: 'systemd-network': attribute type 5 has an invalid length.

2020-05-25 Thread Łukasz Zemczak
This is fine right now, but please be sure to be a bit more verbose
about what kind of testing has been performed on the selected package!

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

Title:
  netlink: 'systemd-network': attribute type 5 has an invalid length.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  systemd-networkd uses incorrect netlink attribute length for
  wireguard's persistent keepalive interval, which logs error messages
  from the kernel, and may incorrectly set the parameter.

  [test case]

  Only 1 Bionic VM is required to reproduce the problem:

  $ lxc launch images:ubuntu/bionic --vm -c security.secureboot=false foo
  $ sleep 10 # allow booting
  $ lxc exec foo -- apt install -y software-properties-common
  $ lxc exec foo -- add-apt-repository -y ppa:wireguard/wireguard
  $ lxc exec foo -- apt install -y wireguard-tools

  $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.netdev
  # foo
  [NetDev]
  Name=wg0
  Kind=wireguard

  [WireGuard]
  ListenPort=
  PrivateKey=cBkljQSKhtEe/U8GZmCAk2MBbKWL4TLC9PVtbMFyCVQ=

  [WireGuardPeer]
  PublicKey=emfIuZ3hZ+AnWIrKex/EqCp2mfzip8AxJu6RuweyRGc=
  AllowedIPs=192.168.255.2
  Endpoint=bar.lxd:
  EOF

  $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.network
  # foo
  [Match]
  Name=wg0

  [Network]
  Address=192.168.255.1/24
  EOF

  $ lxc exec foo -- systemctl restart systemd-networkd

  # notice the invalid length in dmesg
  $ lxc exec foo -- journalctl -kn 8
  -- Logs begin at Mon 2020-05-11 16:56:40 UTC, end at Mon 2020-05-11 17:03:46 
UTC. --
  May 11 16:58:25 foo kernel: nf_tables: (c) 2007-2009 Patrick McHardy 

  May 11 17:01:57 foo kernel: PKCS#7 signature not signed with a trusted key
  May 11 17:01:57 foo kernel: wireguard: module verification failed: signature 
and/or required key missing - tainting kernel
  May 11 17:01:57 foo kernel: wireguard: WireGuard 1.0.20200429 loaded. See 
www.wireguard.com for information.
  May 11 17:01:57 foo kernel: wireguard: Copyright (C) 2015-2019 Jason A. 
Donenfeld . All Rights Reserved.
  May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.
  May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.
  May 11 17:02:23 foo kernel: netlink: 'systemd-network': attribute type 5 has 
an invalid length.

  [regression potential]

  this adjusts the length of the specific netlink parameter, so any
  regression would likely relate to incorrectly setting the persistent
  keepalive interval parameter, or failure to set the parameter.

  [scope]

  this is needed only for Bionic.

  this was fixed upstream in commit
  7d0b26a027118ca063780421cb31c74e9d2664ee which was first included in
  v240, so this is fixed in Eoan and later.  Xenial does not include
  support for wireguard, so this does not apply there.

  [original description]

  This morning, our 2 Bionic machine configured with the wireguard's PPA
  and using systemd-networkd to configure the wireguard tunnel started
  misbehaving. Why this started just now is unclear ATM but their dmesg
  was filled with this:

  validate_nla: 100 callbacks suppressed
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.

  Folks in #systemd mentioned
  https://github.com/systemd/systemd/issues/11575 which points to 2
  commits missing from Bionic's systemd version:

  
https://github.com/systemd/systemd/commit/7d0b26a027118ca063780421cb31c74e9d2664ee
  
https://github.com/systemd/systemd/commit/624a47694cad4c87b2e807c32db656f3e9d679c5

  Focal's systemd have the above commits. Would it be possible to
  backport those 2 commits to Bionic?

  Additional information:

  # uname -a
  Linux noc-eu1 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  # apt-cache policy systemd wireguard{,-tools,-dkms}
  systemd:
    Installed: 237-3ubuntu10.39
    Candidate: 237-3ubuntu10.39
    Version table:
   *** 237-3ubuntu10.39 500
  500 

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 245.4-4ubuntu3.1

---
systemd (245.4-4ubuntu3.1) focal; urgency=medium

  * 
d/p/lp1867375/0001-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,

d/p/lp1867375/0002-test-network-add-a-test-case-for-DHCPv4.UseGateway-n.patch,

d/p/lp1867375/0003-network-change-UseGateway-default-to-UseRoutes-setti.patch,

d/p/lp1867375/0004-test-modify-add-tests-for-UseRoutes-and-UseGateway-c.patch,

d/p/lp1867375/0005-network-honor-SetDNSRoutes-even-if-UseGateway-False.patch,

d/p/lp1867375/0006-test-verify-RoutesToDNS-is-independent-of-UseGateway.patch:
- Add UseGateway= parameter and default to value of UseRoutes, to restore
  backwards compatibility with old UseRoutes= behavior (LP: #1867375)
  * d/p/lp1860926-network-Change-IgnoreCarrierLoss-default-to-value-of.patch:
- default ignore_carrier_loss to value of configure_without_carrier,
  so carrier drop during configuration doesn't break networking
  (LP: #1860926)
   * d/e/initramfs-tools/hooks/udev:
 - Follow symlinks when finding link files to copy into initramfs
   (LP: #1868892)
   * d/p/lp1873607/0001-core-some-minor-clean-ups-modernizations.patch,
 
d/p/lp1873607/0002-core-make-sure-to-restore-the-control-command-id-too.patch:
 - Avoid segfault during serialization (LP: #1873607)

 -- Dan Streetman   Thu, 07 May 2020 09:21:22
-0400

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

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

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [test case, pre-focal]

  same netplan as above, but remove ethernets: section.  Reboot, and the
  bridge should have its address and route:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static linkdown 
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown 

  
  add and remove carrier, by adding and removing a slave interface:

  ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up
  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster

  
  the bridge no longer has its address after losing carrier:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever


  [regression potential]

  Any regression would likely involve incorrectly configured network
  after an interface carrier gain/loss.

  [scope]

  This is needed for Focal, Eoan, and Bionic.

  While this only reproduces at boot for Focal, the general loss of
  configuration on carrier loss even when 

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 242-7ubuntu3.9

---
systemd (242-7ubuntu3.9) eoan; urgency=medium

  * d/p/lp1867375/0001-network-Allow-to-configure-GW-even-UseRoutes-false.patch,

d/p/lp1867375/0002-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,

d/p/lp1867375/0003-network-change-UseGateway-default-to-UseRoutes-setti.patch,

d/p/lp1867375/0004-network-honor-SetDNSRoutes-even-if-UseGateway-False.patch:
- Move gateway ignoring from UseRoutes= to UseGateway= (LP: #1867375)
   * d/p/lp1873607/0001-core-some-minor-clean-ups-modernizations.patch,
 
d/p/lp1873607/0002-core-make-sure-to-restore-the-control-command-id-too.patch:
 - Avoid segfault during serialization (LP: #1873607)
   * d/p/lp1877271-network-drop-all-checks-of-ipv6_disabled-sysctl.patch:
 - enable ipv6 for interface when needed (LP: #1877271)
   * d/p/lp1860926-network-Change-IgnoreCarrierLoss-default-to-value-of.patch:
 - IgnoreCarrierLoss default to ConfigureWithoutCarrier (LP: #1860926)

 -- Dan Streetman   Fri, 08 May 2020 12:28:53
-0400

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [test case, pre-focal]

  same netplan as above, but remove ethernets: section.  Reboot, and the
  bridge should have its address and route:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static linkdown 
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown 

  
  add and remove carrier, by adding and removing a slave interface:

  ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up
  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster

  
  the bridge no longer has its address after losing carrier:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever


  [regression potential]

  Any regression would likely involve incorrectly configured network
  after an interface carrier gain/loss.

  [scope]

  This is needed for Focal, Eoan, and Bionic.

  While this only reproduces at boot for Focal, the general loss of
  configuration on carrier loss even when ConfigureWithoutCarrier=true
  is reproducable on all releases except Xenial, which does not have the
  ConfigureWithoutCarrier= parameter.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  

[Touch-packages] [Bug 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 242-7ubuntu3.9

---
systemd (242-7ubuntu3.9) eoan; urgency=medium

  * d/p/lp1867375/0001-network-Allow-to-configure-GW-even-UseRoutes-false.patch,

d/p/lp1867375/0002-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,

d/p/lp1867375/0003-network-change-UseGateway-default-to-UseRoutes-setti.patch,

d/p/lp1867375/0004-network-honor-SetDNSRoutes-even-if-UseGateway-False.patch:
- Move gateway ignoring from UseRoutes= to UseGateway= (LP: #1867375)
   * d/p/lp1873607/0001-core-some-minor-clean-ups-modernizations.patch,
 
d/p/lp1873607/0002-core-make-sure-to-restore-the-control-command-id-too.patch:
 - Avoid segfault during serialization (LP: #1873607)
   * d/p/lp1877271-network-drop-all-checks-of-ipv6_disabled-sysctl.patch:
 - enable ipv6 for interface when needed (LP: #1877271)
   * d/p/lp1860926-network-Change-IgnoreCarrierLoss-default-to-value-of.patch:
 - IgnoreCarrierLoss default to ConfigureWithoutCarrier (LP: #1860926)

 -- Dan Streetman   Fri, 08 May 2020 12:28:53
-0400

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released
Status in netplan.io source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Fix Released
Status in netplan.io source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in netplan.io source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  the networkd UseRoutes parameter allowed ignoring all routes provided
  by a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.

  The systemd in Focal unfortunately has part of the upstream code; it
  no longer ignores the gateway route when UseRoutes=false is specified,
  but also it does not include the UseGateway parameter.

  Before Focal, networkd did not allow ignoring dhcpv4 routes and the
  gateway separately; the UseRoutes= parameter either used, or ignored,
  both.  This is why upstream added the UseGateway= paramter, which
  should be backported to allow control of ignoring the dhcpv4 routes
  and gateway separately.

  [test case]

  In Focal, bug 1872589 has a good test case netplan config, but a very
  quick test can be done with the networkd config:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false

  this results in the system incorrectly setting a route via the default
  gateway:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  Before Focal, the above test case shows "correct" behavior, but there
  is no way to ignore the dhcpv4 routes but use the dhcpv4 gateway.
  This pre-Focal, the test case would be to use the UseGateway=
  parameter, e.g.:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  UseGateway=true

  which *should* result in the default gateway being configured:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  [regression potential]

  Any regression would likely involve incorrect setting, or ignoring, of
  dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the
  dhcpv4-provided gateway.

  [scope]

  This is fixed by these upstream PRs:
  https://github.com/systemd/systemd/pull/15443
  https://github.com/systemd/systemd/pull/15136
  https://github.com/systemd/systemd/pull/14983

  Parts of all those PRs are required in Focal, Eoan, and Bionic.

  I am not fixing this for Xenial, at this time.

  For Debian, I opened this MR:
  https://salsa.debian.org/systemd-team/systemd/-/merge_requests/92

  For Groovy, I opened this MR:
  
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/383661

  [other info]

  to properly support separation of 'routes' and 'gateways' received via
  dhcp4, SRU releases should also support 

[Touch-packages] [Bug 1876230] Update Released

2020-05-25 Thread Łukasz Zemczak
The verification of the Stable Release Update for liburcu has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address
  performance problems with MEMBARRIER_CMD_SHARED

Status in liburcu package in Ubuntu:
  Fix Released
Status in liburcu source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  In Linux 4.3, a new syscall was defined, called "membarrier". This
  systemcall was defined specifically for use in userspace-rcu (liburcu)
  to speed up the fast path / reader side of the library. The original
  implementation in Linux 4.3 only supported the MEMBARRIER_CMD_SHARED
  subcommand of the membarrier syscall.

  MEMBARRIER_CMD_SHARED executes a memory barrier on all threads from
  all processes running on the system. When it exits, the userspace
  thread which called it is guaranteed that all running threads share
  the same world view in regards to userspace addresses which are
  consumed by readers and writers.

  The problem with MEMBARRIER_CMD_SHARED is system calls made in this
  fashion can block, since it deploys a barrier across all threads in a
  system, and some other threads can be waiting on blocking operations,
  and take time to reach the barrier.

  In Linux 4.14, this was addressed by adding the
  MEMBARRIER_CMD_PRIVATE_EXPEDITED command to the membarrier syscall. It
  only targets threads which share the same mm as the thread calling the
  membarrier syscall, aka, threads in the current process, and not all
  threads / processes in the system.

  Calls to membarrier with the MEMBARRIER_CMD_PRIVATE_EXPEDITED command
  are guaranteed non-blocking, due to using inter-processor interrupts
  to implement memory barriers.

  Because of this, membarrier calls that use
  MEMBARRIER_CMD_PRIVATE_EXPEDITED are much faster than those that use
  MEMBARRIER_CMD_SHARED.

  Since Bionic uses a 4.15 kernel, all kernel requirements are met, and
  this SRU is to enable support for MEMBARRIER_CMD_PRIVATE_EXPEDITED in
  the liburcu package.

  This brings the performance of the liburcu library back in line to
  where it was in Trusty, as this particular user has performance
  problems upon upgrading from Trusty to Bionic.

  [Test]

  Testing performance is heavily dependant on the application which
  links against liburcu, and the workload which it executes.

  A test package is available in the following ppa:
  https://launchpad.net/~mruffell/+archive/ubuntu/sf276198-test

  For the sake of testing, we can use the benchmarks provided in the
  liburcu source code. Download a copy of the source code for liburcu
  either from the repos or from github:

  $ pull-lp-source liburcu bionic
  # OR
  $ git clone https://github.com/urcu/userspace-rcu.git
  $ git checkout v0.10.1 # version in bionic

  Build the code:

  $ ./bootstrap
  $ ./configure
  $ make

  Go into the tests/benchmark directory

  $ cd tests/benchmark

  From there, you can run benchmarks for the four main usages of
  liburcu: urcu, urcu-bp, urcu-signal and urcu-mb.

  On a 8 core machine, 6 threads for readers and 2 threads for writers,
  with a 10 second runtime, execute:

  $ ./test_urcu 6 2 10
  $ ./test_urcu_bp 6 2 10
  $ ./test_urcu_signal 6 2 10
  $ ./test_urcu_mb 6 2 10

  Results:

  ./test_urcu 6 2 10
  0.10.1-1: 17612527667 reads, 268 writes, 17612527935 ops
  0.10.1-1ubuntu1: 14988437247 reads, 810069 writes, 14989247316 ops

  $ ./test_urcu_bp 6 2 10
  0.10.1-1: 1177891079 reads, 1699523 writes, 1179590602 ops
  0.10.1-1ubuntu1: 13230354737 reads, 575314 writes, 13230930051 ops

  $ ./test_urcu_signal 6 2 10
  0.10.1-1: 20128392417 reads, 6859 writes, 20128399276 ops
  0.10.1-1ubuntu1: 20501430707 reads, 6890 writes, 20501437597 ops

  $ ./test_urcu_mb 6 2 10
  0.10.1-1: 627996563 reads, 5409563 writes, 633406126 ops
  0.10.1-1ubuntu1: 653194752 reads, 4590020 writes, 657784772 ops

  The SRU only changes behaviour for urcu and urcu-bp, since they are
  the only "flavours" of liburcu which the patches change. From a pure
  ops standpoint:

  $ ./test_urcu 6 2 10
  17612527935 ops
  14989247316 ops

  $ ./test_urcu_bp 6 2 10
  1179590602 ops
  13230930051 ops

  We see that this particular benchmark workload, test_urcu sees extra
  performance overhead with MEMBARRIER_CMD_PRIVATE_EXPEDITED, which is
  explained by the extra impact that it has on the slowpath, and the
  extra amount of writes it did during my benchmark.

  The real 

[Touch-packages] [Bug 1867375] Update Released

2020-05-25 Thread Łukasz Zemczak
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released
Status in netplan.io source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Fix Released
Status in netplan.io source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in netplan.io source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  the networkd UseRoutes parameter allowed ignoring all routes provided
  by a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.

  The systemd in Focal unfortunately has part of the upstream code; it
  no longer ignores the gateway route when UseRoutes=false is specified,
  but also it does not include the UseGateway parameter.

  Before Focal, networkd did not allow ignoring dhcpv4 routes and the
  gateway separately; the UseRoutes= parameter either used, or ignored,
  both.  This is why upstream added the UseGateway= paramter, which
  should be backported to allow control of ignoring the dhcpv4 routes
  and gateway separately.

  [test case]

  In Focal, bug 1872589 has a good test case netplan config, but a very
  quick test can be done with the networkd config:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false

  this results in the system incorrectly setting a route via the default
  gateway:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  Before Focal, the above test case shows "correct" behavior, but there
  is no way to ignore the dhcpv4 routes but use the dhcpv4 gateway.
  This pre-Focal, the test case would be to use the UseGateway=
  parameter, e.g.:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  UseGateway=true

  which *should* result in the default gateway being configured:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  [regression potential]

  Any regression would likely involve incorrect setting, or ignoring, of
  dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the
  dhcpv4-provided gateway.

  [scope]

  This is fixed by these upstream PRs:
  https://github.com/systemd/systemd/pull/15443
  https://github.com/systemd/systemd/pull/15136
  https://github.com/systemd/systemd/pull/14983

  Parts of all those PRs are required in Focal, Eoan, and Bionic.

  I am not fixing this for Xenial, at this time.

  For Debian, I opened this MR:
  https://salsa.debian.org/systemd-team/systemd/-/merge_requests/92

  For Groovy, I opened this MR:
  
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/383661

  [other info]

  to properly support separation of 'routes' and 'gateways' received via
  dhcp4, SRU releases should also support the UseGateway parameter,
  which is what this bug was originally opened requesting.

  [original description]

  requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in
  https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

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

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

[Touch-packages] [Bug 1860926] Update Released

2020-05-25 Thread Łukasz Zemczak
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [test case, pre-focal]

  same netplan as above, but remove ethernets: section.  Reboot, and the
  bridge should have its address and route:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static linkdown 
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown 

  
  add and remove carrier, by adding and removing a slave interface:

  ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up
  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster

  
  the bridge no longer has its address after losing carrier:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever


  [regression potential]

  Any regression would likely involve incorrectly configured network
  after an interface carrier gain/loss.

  [scope]

  This is needed for Focal, Eoan, and Bionic.

  While this only reproduces at boot for Focal, the general loss of
  configuration on carrier loss even when ConfigureWithoutCarrier=true
  is reproducable on all releases except Xenial, which does not have the
  ConfigureWithoutCarrier= parameter.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b 

[Touch-packages] [Bug 1876230] Re: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package liburcu - 0.10.1-1ubuntu1

---
liburcu (0.10.1-1ubuntu1) bionic; urgency=medium

  * d/p/liburcu-use-membarrier-private-expedited.patch
  * d/p/liburcu-bp-use-membarrier-private-expedited.patch
- Enable usage of MEMBARRIER_CMD_PRIVATE_EXPEDITED in the librcu and
  liburcu-bp flavours, for higher performance non-blocking syscalls.
  (LP: #1876230)

 -- Matthew Ruffell   Fri, 01 May 2020
16:11:48 +1200

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

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

Title:
  liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address
  performance problems with MEMBARRIER_CMD_SHARED

Status in liburcu package in Ubuntu:
  Fix Released
Status in liburcu source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  In Linux 4.3, a new syscall was defined, called "membarrier". This
  systemcall was defined specifically for use in userspace-rcu (liburcu)
  to speed up the fast path / reader side of the library. The original
  implementation in Linux 4.3 only supported the MEMBARRIER_CMD_SHARED
  subcommand of the membarrier syscall.

  MEMBARRIER_CMD_SHARED executes a memory barrier on all threads from
  all processes running on the system. When it exits, the userspace
  thread which called it is guaranteed that all running threads share
  the same world view in regards to userspace addresses which are
  consumed by readers and writers.

  The problem with MEMBARRIER_CMD_SHARED is system calls made in this
  fashion can block, since it deploys a barrier across all threads in a
  system, and some other threads can be waiting on blocking operations,
  and take time to reach the barrier.

  In Linux 4.14, this was addressed by adding the
  MEMBARRIER_CMD_PRIVATE_EXPEDITED command to the membarrier syscall. It
  only targets threads which share the same mm as the thread calling the
  membarrier syscall, aka, threads in the current process, and not all
  threads / processes in the system.

  Calls to membarrier with the MEMBARRIER_CMD_PRIVATE_EXPEDITED command
  are guaranteed non-blocking, due to using inter-processor interrupts
  to implement memory barriers.

  Because of this, membarrier calls that use
  MEMBARRIER_CMD_PRIVATE_EXPEDITED are much faster than those that use
  MEMBARRIER_CMD_SHARED.

  Since Bionic uses a 4.15 kernel, all kernel requirements are met, and
  this SRU is to enable support for MEMBARRIER_CMD_PRIVATE_EXPEDITED in
  the liburcu package.

  This brings the performance of the liburcu library back in line to
  where it was in Trusty, as this particular user has performance
  problems upon upgrading from Trusty to Bionic.

  [Test]

  Testing performance is heavily dependant on the application which
  links against liburcu, and the workload which it executes.

  A test package is available in the following ppa:
  https://launchpad.net/~mruffell/+archive/ubuntu/sf276198-test

  For the sake of testing, we can use the benchmarks provided in the
  liburcu source code. Download a copy of the source code for liburcu
  either from the repos or from github:

  $ pull-lp-source liburcu bionic
  # OR
  $ git clone https://github.com/urcu/userspace-rcu.git
  $ git checkout v0.10.1 # version in bionic

  Build the code:

  $ ./bootstrap
  $ ./configure
  $ make

  Go into the tests/benchmark directory

  $ cd tests/benchmark

  From there, you can run benchmarks for the four main usages of
  liburcu: urcu, urcu-bp, urcu-signal and urcu-mb.

  On a 8 core machine, 6 threads for readers and 2 threads for writers,
  with a 10 second runtime, execute:

  $ ./test_urcu 6 2 10
  $ ./test_urcu_bp 6 2 10
  $ ./test_urcu_signal 6 2 10
  $ ./test_urcu_mb 6 2 10

  Results:

  ./test_urcu 6 2 10
  0.10.1-1: 17612527667 reads, 268 writes, 17612527935 ops
  0.10.1-1ubuntu1: 14988437247 reads, 810069 writes, 14989247316 ops

  $ ./test_urcu_bp 6 2 10
  0.10.1-1: 1177891079 reads, 1699523 writes, 1179590602 ops
  0.10.1-1ubuntu1: 13230354737 reads, 575314 writes, 13230930051 ops

  $ ./test_urcu_signal 6 2 10
  0.10.1-1: 20128392417 reads, 6859 writes, 20128399276 ops
  0.10.1-1ubuntu1: 20501430707 reads, 6890 writes, 20501437597 ops

  $ ./test_urcu_mb 6 2 10
  0.10.1-1: 627996563 reads, 5409563 writes, 633406126 ops
  0.10.1-1ubuntu1: 653194752 reads, 4590020 writes, 657784772 ops

  The SRU only changes behaviour for urcu and urcu-bp, since they are
  the only "flavours" of liburcu which the patches change. From a pure
  ops standpoint:

  $ ./test_urcu 6 2 10
  17612527935 ops
  14989247316 ops

  $ ./test_urcu_bp 6 2 10
  1179590602 ops
  13230930051 ops

  We see that this particular benchmark workload, test_urcu sees extra
  performance overhead with MEMBARRIER_CMD_PRIVATE_EXPEDITED, which is
  explained by the extra impact that it has on the 

[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 245.4-4ubuntu3.1

---
systemd (245.4-4ubuntu3.1) focal; urgency=medium

  * 
d/p/lp1867375/0001-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,

d/p/lp1867375/0002-test-network-add-a-test-case-for-DHCPv4.UseGateway-n.patch,

d/p/lp1867375/0003-network-change-UseGateway-default-to-UseRoutes-setti.patch,

d/p/lp1867375/0004-test-modify-add-tests-for-UseRoutes-and-UseGateway-c.patch,

d/p/lp1867375/0005-network-honor-SetDNSRoutes-even-if-UseGateway-False.patch,

d/p/lp1867375/0006-test-verify-RoutesToDNS-is-independent-of-UseGateway.patch:
- Add UseGateway= parameter and default to value of UseRoutes, to restore
  backwards compatibility with old UseRoutes= behavior (LP: #1867375)
  * d/p/lp1860926-network-Change-IgnoreCarrierLoss-default-to-value-of.patch:
- default ignore_carrier_loss to value of configure_without_carrier,
  so carrier drop during configuration doesn't break networking
  (LP: #1860926)
   * d/e/initramfs-tools/hooks/udev:
 - Follow symlinks when finding link files to copy into initramfs
   (LP: #1868892)
   * d/p/lp1873607/0001-core-some-minor-clean-ups-modernizations.patch,
 
d/p/lp1873607/0002-core-make-sure-to-restore-the-control-command-id-too.patch:
 - Avoid segfault during serialization (LP: #1873607)

 -- Dan Streetman   Thu, 07 May 2020 09:21:22
-0400

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

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

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

Title:
  systemd segv coredump, reboot/poweroff ignored.

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  during systemctl daemon-reload, systemd sometimes segfaults while
  serializing a service.

  [test case]

  problem is intermittent, but the upstream bug suggests a reproducer.
  Also see original description.

  [regression potential]

  this adjusts serialization, so any regression would likely occur
  during serialization/deserialization, e.g. at daemon-reload.

  [scope]

  This is needed for Bionic and later.

  this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41
  which is included starting in v234.  The commit to fix it is
  e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in
  any release.

  The PR to fix this is https://github.com/systemd/systemd/pull/15546

  [other info]

  there is an additional PR that further avoids the error, but has not yet been 
accepted, and may not be accepted as it may not be necessary.
  https://github.com/systemd/systemd/pull/15370

  [original description]

  Proximate syslog:

  Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running:  ip -all netns 
del
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /r
  un/dbus/system_bus_socket; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/sssd.pid → /run/sssd.pid; plea
  se update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/oddjobd.pid → /run/oddjobd.p
  id; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/fail2ban/fail2ban.pid → /r
  un/fail2ban/fail2ban.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/certmonger.pid → /run/cer
  tmonger.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: Reloading.
  Apr 18 16:26:56 gate2 kernel: [  454.966336] systemd[1]: segfault at 50 ip 
55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000]
  Apr 18 16:26:56 gate2 kernel: [  454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 
00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 
1f 84 00 00 00 00 00 <48
  > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d
  Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK:   systemctl 
daemon-reload
  Apr 18 16:26:57 

[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 242-7ubuntu3.9

---
systemd (242-7ubuntu3.9) eoan; urgency=medium

  * d/p/lp1867375/0001-network-Allow-to-configure-GW-even-UseRoutes-false.patch,

d/p/lp1867375/0002-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,

d/p/lp1867375/0003-network-change-UseGateway-default-to-UseRoutes-setti.patch,

d/p/lp1867375/0004-network-honor-SetDNSRoutes-even-if-UseGateway-False.patch:
- Move gateway ignoring from UseRoutes= to UseGateway= (LP: #1867375)
   * d/p/lp1873607/0001-core-some-minor-clean-ups-modernizations.patch,
 
d/p/lp1873607/0002-core-make-sure-to-restore-the-control-command-id-too.patch:
 - Avoid segfault during serialization (LP: #1873607)
   * d/p/lp1877271-network-drop-all-checks-of-ipv6_disabled-sysctl.patch:
 - enable ipv6 for interface when needed (LP: #1877271)
   * d/p/lp1860926-network-Change-IgnoreCarrierLoss-default-to-value-of.patch:
 - IgnoreCarrierLoss default to ConfigureWithoutCarrier (LP: #1860926)

 -- Dan Streetman   Fri, 08 May 2020 12:28:53
-0400

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

Title:
  systemd segv coredump, reboot/poweroff ignored.

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  during systemctl daemon-reload, systemd sometimes segfaults while
  serializing a service.

  [test case]

  problem is intermittent, but the upstream bug suggests a reproducer.
  Also see original description.

  [regression potential]

  this adjusts serialization, so any regression would likely occur
  during serialization/deserialization, e.g. at daemon-reload.

  [scope]

  This is needed for Bionic and later.

  this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41
  which is included starting in v234.  The commit to fix it is
  e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in
  any release.

  The PR to fix this is https://github.com/systemd/systemd/pull/15546

  [other info]

  there is an additional PR that further avoids the error, but has not yet been 
accepted, and may not be accepted as it may not be necessary.
  https://github.com/systemd/systemd/pull/15370

  [original description]

  Proximate syslog:

  Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running:  ip -all netns 
del
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /r
  un/dbus/system_bus_socket; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/sssd.pid → /run/sssd.pid; plea
  se update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/oddjobd.pid → /run/oddjobd.p
  id; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/fail2ban/fail2ban.pid → /r
  un/fail2ban/fail2ban.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/certmonger.pid → /run/cer
  tmonger.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: Reloading.
  Apr 18 16:26:56 gate2 kernel: [  454.966336] systemd[1]: segfault at 50 ip 
55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000]
  Apr 18 16:26:56 gate2 kernel: [  454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 
00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 
1f 84 00 00 00 00 00 <48
  > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d
  Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK:   systemctl 
daemon-reload
  Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running:  systemctl 
enable rssmonitor.service
  Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled
  Apr 18 16:27:24 gate2 kernel: [  482.503042] printk: systemd: 43 output lines 
suppressed due to ratelimiting
  Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.7
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 

[Touch-packages] [Bug 1880410] Re: pulseaudio doesn't enforce sample rate set in daemon.conf

2020-05-25 Thread Peter Fiser
Hi Daniel, I've already done this and forgot to link to it. Here you go:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/897

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #897
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/897

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

Title:
  pulseaudio doesn't enforce sample rate set in daemon.conf

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Before submitting this bugreport I've went through the daemon.conf man page 
and the pulseaudio documentation, but have not found a solution to my problem.
  I've moved from Debian stable with
  pulseaudio version 12.2-4+deb10u1 to Kubuntu 20.04 with
  pulseaudio version 13.99.1-1ubuntu3.2.
  I'm experiencing cracking issues on external USB audio device Xonar U3 while 
listening to certain audio sources (system sounds included). This issue doesn't 
happen when using my laptop's internal audio device.
  Output of 'cat /proc/asound/card2/stream0' without audio stream running:
  C-Media Electronics Inc. USB Advanced Audio Device at usb-:00:14.0-2, 
full  : USB Audio

  Playback:
Status: Running
Interface = 1
Altset = 1
Packet Size = 200
Momentary freq = 44100 Hz (0x2c.199a)
Interface 1
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 1 OUT (ADAPTIVE)
Rates: 8000, 16000, 44100, 48000
Bits: 16

  Capture:
Status: Stop
Interface 2
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 2 IN (ASYNC)
Rates: 8000, 16000, 44100, 48000
Bits: 16
  The following behaviour happens with default settings in 
/etc/pulse/daemon.conf:
  Xonar U3 plugged in, firefox running:
Momentary freq = 48000 Hz (0x30.)

  Xonar U3 plugged in, Clementine/Strawberry audio player running:
Momentary freq = 44100 Hz (0x2c.199a)

  Xonar U3 plugged in with Deadbeef set to override sample rate to 48kHz:
Momentary freq = 48000 Hz (0x30.)
  I've modified the daemon.conf as follows:
  ; default-sample-format = s16le #no change on this line, this is 
corresponding with the format the usb audio device suggests to be using
  ; default-sample-rate = 48000
  ; alternate-sample-rate = 48000
  However, when running video or audio sources with 44100Hz audio, applications 
 do not respect the default-sample-rate and Momentary freq reports 44100Hz, 
while other sources either send 48kHz by default or have no problem respecting 
the setting (I've tried the game Into the Breach, VLC running 48kHz video and 
audio files).
  Complete /etc/pulse/daemon.conf contents:
  https://gist.github.com/zelmor/f224e6e4d300241e8431d3258e777e73
  Checking syslog doesn't indicate any errors either, gist:
  https://gist.github.com/zelmor/5e59094be4d90ffa9e0ff6275594e370
  ==Workarounds attempted==

  Modifying /etc/pulse/default.pa to include:

  load-module module-udev-detect tsched=0
  Even after killing pulseaudio, this did not resolve anything. It 
also doesn't look like a good overall solution to the problem.

  Modifying daemon.conf to:

  ; resample-method = src-sinc-best-quality
  ; avoid-resampling = true
  Did not fix the issue.
  It is not possible to roll back PA to a previous version in Kubuntu 20.04 
without breaking dependencies of the Plasma desktop, so this was not attempted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  zelmor 1994 F pulseaudio
   /dev/snd/controlC1:  zelmor 1994 F pulseaudio
   /dev/snd/controlC0:  zelmor 1994 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun May 24 16:30:11 2020
  InstallationDate: Installed on 2020-04-28 (25 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET46WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7S11H00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20B7S11H00:pvrThinkPadT450:rvnLENOVO:rn20B7S11H00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20B7S11H00
  dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T450
  dmi.product.version: 

[Touch-packages] [Bug 1868892] Re: initramfs-tools/hooks/udev for network *.link really sucks

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 245.4-4ubuntu3.1

---
systemd (245.4-4ubuntu3.1) focal; urgency=medium

  * 
d/p/lp1867375/0001-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,

d/p/lp1867375/0002-test-network-add-a-test-case-for-DHCPv4.UseGateway-n.patch,

d/p/lp1867375/0003-network-change-UseGateway-default-to-UseRoutes-setti.patch,

d/p/lp1867375/0004-test-modify-add-tests-for-UseRoutes-and-UseGateway-c.patch,

d/p/lp1867375/0005-network-honor-SetDNSRoutes-even-if-UseGateway-False.patch,

d/p/lp1867375/0006-test-verify-RoutesToDNS-is-independent-of-UseGateway.patch:
- Add UseGateway= parameter and default to value of UseRoutes, to restore
  backwards compatibility with old UseRoutes= behavior (LP: #1867375)
  * d/p/lp1860926-network-Change-IgnoreCarrierLoss-default-to-value-of.patch:
- default ignore_carrier_loss to value of configure_without_carrier,
  so carrier drop during configuration doesn't break networking
  (LP: #1860926)
   * d/e/initramfs-tools/hooks/udev:
 - Follow symlinks when finding link files to copy into initramfs
   (LP: #1868892)
   * d/p/lp1873607/0001-core-some-minor-clean-ups-modernizations.patch,
 
d/p/lp1873607/0002-core-make-sure-to-restore-the-control-command-id-too.patch:
 - Avoid segfault during serialization (LP: #1873607)

 -- Dan Streetman   Thu, 07 May 2020 09:21:22
-0400

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

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

Title:
  initramfs-tools/hooks/udev for network *.link really sucks

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  If the /{etc,lib}/systemd/network directory itself is a symlink, the find
  command will not actually find any of the files in the dir it links to.

  [test case]

  $ sudo touch /etc/systemd/network/lp1868892.link
  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  ...
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  usr/lib/systemd/network/lp1868892.link
  $ sudo mv /etc/systemd/network /etc/systemd/network.abc
  $ sudo ln -s network.abc /etc/systemd/network
  $ sudo update-initramfs -u
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  $ 

  [regression potential]

  this adjusts how link files are included in the initramfs, so
  regressions would likely occur when creating new initramfs, such as
  failure to create initramfs at all, or failure to properly copy link
  files into the initramfs, causing network setup failure.

  [scope]

  this is a Debian/Ubuntu specific file, and the Debian MR was just
  opened, so this is needed for Debian and all releases of Ubuntu.

  [other info]

  This bug likely has a very limited impact, as it is uncommon to
  symlink either the /lib/systemd/network or /etc/systemd/network dirs.

  [original description]

  If one creates e.g. /etc/systemd/network.cu and
  /etc/systemd/network.fc and symlinks  /etc/systemd/network to one of
  them, network setup will fail on reboot, because /usr/share/initramfs-
  tools/hooks/udev does a very poor job: it simply checks for a
  directory instead of the link files and therefore skips copying
  required files to the ram image. Another poor job is done when copying
  the files to the ram image: instead of following symlinks it copies
  them as which in turn makes them useless, because it does not copy the
  related dirs and thus the symlinks point to nothing. So keeping the
  system in an consistent state which such poor scripts is very hard,
  asking for trouble.

  Suggested fix is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1868892/+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 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 245.4-4ubuntu3.1

---
systemd (245.4-4ubuntu3.1) focal; urgency=medium

  * 
d/p/lp1867375/0001-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,

d/p/lp1867375/0002-test-network-add-a-test-case-for-DHCPv4.UseGateway-n.patch,

d/p/lp1867375/0003-network-change-UseGateway-default-to-UseRoutes-setti.patch,

d/p/lp1867375/0004-test-modify-add-tests-for-UseRoutes-and-UseGateway-c.patch,

d/p/lp1867375/0005-network-honor-SetDNSRoutes-even-if-UseGateway-False.patch,

d/p/lp1867375/0006-test-verify-RoutesToDNS-is-independent-of-UseGateway.patch:
- Add UseGateway= parameter and default to value of UseRoutes, to restore
  backwards compatibility with old UseRoutes= behavior (LP: #1867375)
  * d/p/lp1860926-network-Change-IgnoreCarrierLoss-default-to-value-of.patch:
- default ignore_carrier_loss to value of configure_without_carrier,
  so carrier drop during configuration doesn't break networking
  (LP: #1860926)
   * d/e/initramfs-tools/hooks/udev:
 - Follow symlinks when finding link files to copy into initramfs
   (LP: #1868892)
   * d/p/lp1873607/0001-core-some-minor-clean-ups-modernizations.patch,
 
d/p/lp1873607/0002-core-make-sure-to-restore-the-control-command-id-too.patch:
 - Avoid segfault during serialization (LP: #1873607)

 -- Dan Streetman   Thu, 07 May 2020 09:21:22
-0400

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

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

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released
Status in netplan.io source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Fix Released
Status in netplan.io source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in netplan.io source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  the networkd UseRoutes parameter allowed ignoring all routes provided
  by a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.

  The systemd in Focal unfortunately has part of the upstream code; it
  no longer ignores the gateway route when UseRoutes=false is specified,
  but also it does not include the UseGateway parameter.

  Before Focal, networkd did not allow ignoring dhcpv4 routes and the
  gateway separately; the UseRoutes= parameter either used, or ignored,
  both.  This is why upstream added the UseGateway= paramter, which
  should be backported to allow control of ignoring the dhcpv4 routes
  and gateway separately.

  [test case]

  In Focal, bug 1872589 has a good test case netplan config, but a very
  quick test can be done with the networkd config:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false

  this results in the system incorrectly setting a route via the default
  gateway:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  Before Focal, the above test case shows "correct" behavior, but there
  is no way to ignore the dhcpv4 routes but use the dhcpv4 gateway.
  This pre-Focal, the test case would be to use the UseGateway=
  parameter, e.g.:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  UseGateway=true

  which *should* result in the default gateway being configured:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  [regression potential]

  Any regression would likely involve incorrect setting, or ignoring, of
  dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the
  dhcpv4-provided gateway.

  [scope]

  This is fixed by these upstream PRs:
  https://github.com/systemd/systemd/pull/15443
  https://github.com/systemd/systemd/pull/15136
  

[Touch-packages] [Bug 1873607] Update Released

2020-05-25 Thread Łukasz Zemczak
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  systemd segv coredump, reboot/poweroff ignored.

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  during systemctl daemon-reload, systemd sometimes segfaults while
  serializing a service.

  [test case]

  problem is intermittent, but the upstream bug suggests a reproducer.
  Also see original description.

  [regression potential]

  this adjusts serialization, so any regression would likely occur
  during serialization/deserialization, e.g. at daemon-reload.

  [scope]

  This is needed for Bionic and later.

  this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41
  which is included starting in v234.  The commit to fix it is
  e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in
  any release.

  The PR to fix this is https://github.com/systemd/systemd/pull/15546

  [other info]

  there is an additional PR that further avoids the error, but has not yet been 
accepted, and may not be accepted as it may not be necessary.
  https://github.com/systemd/systemd/pull/15370

  [original description]

  Proximate syslog:

  Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running:  ip -all netns 
del
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /r
  un/dbus/system_bus_socket; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/sssd.pid → /run/sssd.pid; plea
  se update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/oddjobd.pid → /run/oddjobd.p
  id; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/fail2ban/fail2ban.pid → /r
  un/fail2ban/fail2ban.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/certmonger.pid → /run/cer
  tmonger.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: Reloading.
  Apr 18 16:26:56 gate2 kernel: [  454.966336] systemd[1]: segfault at 50 ip 
55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000]
  Apr 18 16:26:56 gate2 kernel: [  454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 
00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 
1f 84 00 00 00 00 00 <48
  > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d
  Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK:   systemctl 
daemon-reload
  Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running:  systemctl 
enable rssmonitor.service
  Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled
  Apr 18 16:27:24 gate2 kernel: [  482.503042] printk: systemd: 43 output lines 
suppressed due to ratelimiting
  Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.7
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Sat Apr 18 18:09:06 2020
  InstallationDate: Installed on 2019-11-01 (169 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   SHELL=/bin/bash
   

[Touch-packages] [Bug 1877271] Update Released

2020-05-25 Thread Łukasz Zemczak
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  networkd does not enable ipv6 when requested

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  if networkd is configured with ipv6 address but the 'disable_ipv6'
  sysctl is enabled, networkd does not enable it and set the ipv6
  configuration.

  [test case]

  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=2001:db8::100/64

  manually disable ipv6 for the interface:

  ubuntu@lp1859862-b:~$ echo 1 | sudo tee 
/proc/sys/net/ipv6/conf/ens3/disable_ipv6
  1

  the interface should not contain any ipv6 addresses:

  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$

  restart networkd; it should enable ipv6 as ipv6 addresses are
  configured, but it does not:

  ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$

  [regression potential]

  any regression would likely result in failure to configure ipv6
  addresses/routes.

  [scope]

  this is needed only for Eoan.

  this is fixed by commit 57ad76074670d4859e808a6aabd69fd6e58514c5,
  which is included starting in v243, so this is fixed in Focal and
  later.

  this bug was introduced by a series of patches starting at
  54a1a535bd60f13964bbddd8f381601e33e8e56f, which is included starting
  in v243, but was also pulled into Debian v242-4, and so included in
  Eoan.  This bug is not present in earlier versions so is not needed in
  Xenial or Bionic.

  [other info]

  this is a follow on for the fix in bug 1859862.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877271/+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 1877271] Re: networkd does not enable ipv6 when requested

2020-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 242-7ubuntu3.9

---
systemd (242-7ubuntu3.9) eoan; urgency=medium

  * d/p/lp1867375/0001-network-Allow-to-configure-GW-even-UseRoutes-false.patch,

d/p/lp1867375/0002-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,

d/p/lp1867375/0003-network-change-UseGateway-default-to-UseRoutes-setti.patch,

d/p/lp1867375/0004-network-honor-SetDNSRoutes-even-if-UseGateway-False.patch:
- Move gateway ignoring from UseRoutes= to UseGateway= (LP: #1867375)
   * d/p/lp1873607/0001-core-some-minor-clean-ups-modernizations.patch,
 
d/p/lp1873607/0002-core-make-sure-to-restore-the-control-command-id-too.patch:
 - Avoid segfault during serialization (LP: #1873607)
   * d/p/lp1877271-network-drop-all-checks-of-ipv6_disabled-sysctl.patch:
 - enable ipv6 for interface when needed (LP: #1877271)
   * d/p/lp1860926-network-Change-IgnoreCarrierLoss-default-to-value-of.patch:
 - IgnoreCarrierLoss default to ConfigureWithoutCarrier (LP: #1860926)

 -- Dan Streetman   Fri, 08 May 2020 12:28:53
-0400

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

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

Title:
  networkd does not enable ipv6 when requested

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  if networkd is configured with ipv6 address but the 'disable_ipv6'
  sysctl is enabled, networkd does not enable it and set the ipv6
  configuration.

  [test case]

  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=2001:db8::100/64

  manually disable ipv6 for the interface:

  ubuntu@lp1859862-b:~$ echo 1 | sudo tee 
/proc/sys/net/ipv6/conf/ens3/disable_ipv6
  1

  the interface should not contain any ipv6 addresses:

  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$

  restart networkd; it should enable ipv6 as ipv6 addresses are
  configured, but it does not:

  ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1859862-b:~$ ip -6 a show ens3
  ubuntu@lp1859862-b:~$

  [regression potential]

  any regression would likely result in failure to configure ipv6
  addresses/routes.

  [scope]

  this is needed only for Eoan.

  this is fixed by commit 57ad76074670d4859e808a6aabd69fd6e58514c5,
  which is included starting in v243, so this is fixed in Focal and
  later.

  this bug was introduced by a series of patches starting at
  54a1a535bd60f13964bbddd8f381601e33e8e56f, which is included starting
  in v243, but was also pulled into Debian v242-4, and so included in
  Eoan.  This bug is not present in earlier versions so is not needed in
  Xenial or Bionic.

  [other info]

  this is a follow on for the fix in bug 1859862.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877271/+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 1879625] Re: [Precision 5530, Realtek ALC3266] No sound after reboot until headphones are unplugged and plugged back in

2020-05-25 Thread SR
Well, I'm confused : how can I make this report useful ? Or is it
worthless that I create such reports ?

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

Title:
  [Precision 5530, Realtek ALC3266] No sound after reboot until
  headphones are unplugged and plugged back in

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Looks like a frequent problem that hits my system : I have no sound on my 
headphones after I reboot my laptop until I unplug and plug back in the 
headphones.
  I *may* have sound through the PC speaker. I used to have none, but today 
sound came out of it. As I have upgraded to 20.04 and have done some 
modifications in config files some time ago with 19.xx, I'm unsure this is 
reliable information.
  I've tried to apply some solutions found here or there, without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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/controlC0:  stan   2001 F pulseaudio
   /dev/snd/pcmC0D0p:   stan   2001 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 08:08:37 2020
  InstallationDate: Installed on 2019-04-26 (389 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1570 F pulseaudio
stan   2001 F pulseaudio
   /dev/snd/pcmC0D0p:   stan   2001 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Precision 5530, Realtek ALC3266, Black Headphone Out, Left] No sound 
at all
  UpgradeStatus: Upgraded to focal on 2020-05-07 (12 days ago)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0N0DK2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0N0DK2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5530
  dmi.product.sku: 087D
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-10T16:49:20.600250

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879625/+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 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”

2020-05-25 Thread Timo Aaltonen
closing, should be fixed

** Changed in: mesa (Ubuntu Bionic)
   Status: Incomplete => Fix Released

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

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

Title:
  Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion
  `templat->interlaced' failed”

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  Buggy as Kodi is, this seems to be a problem specifically with mesa-
  va-drivers.

  Kodi has worked just fine on my system, as recently as July 6th of
  this year, but yesterday (July 16) I tried Kodi again: I got a blank
  screen and a pause for a few moments, followed by an unceremonious
  crash-to-desktop. This happens every time I start Kodi, now.

  If I run it through the command-line, I get this:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so
  libva info: Found init function __vaDriverInit_1_1
  libva info: va_openDriver() returns 0
  kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: 
nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed.
  Aborted (core dumped)

  I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”,
  package version 2:18.3+git20190621.1610-final-0bionic, from the Team-
  XBMC PPA) since its release in June, but in between July 6th and 16th,
  I did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2
  19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers”
  package to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates
  Bionic repository), however, Kodi works again, without even requiring
  me to restart my machine. So, this is likely a problem with “mesa-va-
  drivers”.

  I tried looking in Xorg.0.log:

  [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620
  [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines:
  [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0   72.33  1366 1414 1446 
1526  768 770 775 790 -hsync -vsync (47.4 kHz eP)

  …that’s all that appears in the log when I try to load Kodi and a
  crash happens.

  I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if
  you need more information, I’ve attached a hardinfo report, too. I
  hope this bug can get fixed, soon. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+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 1879159] Re: Boot Problem

2020-05-25 Thread Daniel van Vugt
Can you please attach a photo of the "graphics problem"?

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

** Changed in: 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/1879159

Title:
  Boot Problem

Status in Ubuntu:
  Incomplete

Bug description:
  It shows graphics problem during booting and unable to operate mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219
  Uname: Linux 4.4.0-179-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun May 17 13:19:12 2020
  DistUpgraded: 2020-03-29 23:06:17,899 DEBUG /openCache(), new cache size 56855
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0555]
  InstallationDate: Installed on 2020-03-24 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Dell Inc. Inspiron 3520
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-179-generic 
root=UUID=2e048bbe-fc79-442e-ae8d-aac97ebb2938 ro quiet splash vt.handoff=7 
init=/sbin/upstart
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2020-03-29 (48 days ago)
  dmi.bios.date: 05/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0486TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3520
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May 17 13:15:51 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   21569 
   vendor SEC
  xserver.version: 2:1.18.4-0ubuntu0.8

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

2020-05-25 Thread Daniel van Vugt
Can you please attach a photo or video of the problem?

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Tags added: amdgpu

** Summary changed:

- Xorg freeze
+ [amdgpu] Xorg freeze

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

Title:
  [amdgpu] Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  when i was my computer on and start blinking middle of screen please
  solve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 10:24:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879234/+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 1880450] Re: Unmet package dependency "xserver-xorg-core (>= 2:1.17.2-2)"

2020-05-25 Thread Daniel van Vugt
The title of the bug and the text in the description don't match. Can
you fix that?

** Tags added: bionic

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (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/1880450

Title:
  Unmet package dependency "xserver-xorg-core (>= 2:1.17.2-2)"

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 18.04 x86_64 (fully patched) on a Dell XPS 8930
  (https://www.amazon.com/gp/product/B078N85NCR). I recently performed a
  dist-upgrade to 5.3.0-53-generic. After the upgrade I lost X in non-
  recovery mode. In recovery mode I get a GUI at 800x600. 800x600 leaves
  a lot to be desired with a 32" monitor.

  I reinstalled the kernel components with no joy. Secure Boot is Off.
  Reboots did not help. The kernel components were:

  * linux-headers-5.3.0-53-generic
  * linux-image-5.3.0-53-generic
  * linux-modules-5.3.0-53-generic
  * linux-modules-extra-5.3.0-53-generic
  * linux-tools-5.3.0-53-generic

  I tried the Nvidia drivers 435 and 440 with no joy. Reboots did not
  help.

  I then removed the Nvidia drivers, and I tried the default Xorg
  server, but it errors with the following. Reboots did not help.

  # apt-get install xserver-xorg-video-nouveau nouveau-firmware
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-video-nouveau : Depends: xorg-video-abi-23
    Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  I'm not sure which package is the problem here. I generically filed
  the report against Xorg, but I suspect there's a better choice of
  package. (There is no xserver-xorg-core package available to select).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1880450/+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 1880410] Re: pulseaudio doesn't enforce sample rate set in daemon.conf

2020-05-25 Thread Daniel van Vugt
Please report the bug upstream at:

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

and then tell us the new bug ID.

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

Title:
  pulseaudio doesn't enforce sample rate set in daemon.conf

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Before submitting this bugreport I've went through the daemon.conf man page 
and the pulseaudio documentation, but have not found a solution to my problem.
  I've moved from Debian stable with
  pulseaudio version 12.2-4+deb10u1 to Kubuntu 20.04 with
  pulseaudio version 13.99.1-1ubuntu3.2.
  I'm experiencing cracking issues on external USB audio device Xonar U3 while 
listening to certain audio sources (system sounds included). This issue doesn't 
happen when using my laptop's internal audio device.
  Output of 'cat /proc/asound/card2/stream0' without audio stream running:
  C-Media Electronics Inc. USB Advanced Audio Device at usb-:00:14.0-2, 
full  : USB Audio

  Playback:
Status: Running
Interface = 1
Altset = 1
Packet Size = 200
Momentary freq = 44100 Hz (0x2c.199a)
Interface 1
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 1 OUT (ADAPTIVE)
Rates: 8000, 16000, 44100, 48000
Bits: 16

  Capture:
Status: Stop
Interface 2
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 2 IN (ASYNC)
Rates: 8000, 16000, 44100, 48000
Bits: 16
  The following behaviour happens with default settings in 
/etc/pulse/daemon.conf:
  Xonar U3 plugged in, firefox running:
Momentary freq = 48000 Hz (0x30.)

  Xonar U3 plugged in, Clementine/Strawberry audio player running:
Momentary freq = 44100 Hz (0x2c.199a)

  Xonar U3 plugged in with Deadbeef set to override sample rate to 48kHz:
Momentary freq = 48000 Hz (0x30.)
  I've modified the daemon.conf as follows:
  ; default-sample-format = s16le #no change on this line, this is 
corresponding with the format the usb audio device suggests to be using
  ; default-sample-rate = 48000
  ; alternate-sample-rate = 48000
  However, when running video or audio sources with 44100Hz audio, applications 
 do not respect the default-sample-rate and Momentary freq reports 44100Hz, 
while other sources either send 48kHz by default or have no problem respecting 
the setting (I've tried the game Into the Breach, VLC running 48kHz video and 
audio files).
  Complete /etc/pulse/daemon.conf contents:
  https://gist.github.com/zelmor/f224e6e4d300241e8431d3258e777e73
  Checking syslog doesn't indicate any errors either, gist:
  https://gist.github.com/zelmor/5e59094be4d90ffa9e0ff6275594e370
  ==Workarounds attempted==

  Modifying /etc/pulse/default.pa to include:

  load-module module-udev-detect tsched=0
  Even after killing pulseaudio, this did not resolve anything. It 
also doesn't look like a good overall solution to the problem.

  Modifying daemon.conf to:

  ; resample-method = src-sinc-best-quality
  ; avoid-resampling = true
  Did not fix the issue.
  It is not possible to roll back PA to a previous version in Kubuntu 20.04 
without breaking dependencies of the Plasma desktop, so this was not attempted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  zelmor 1994 F pulseaudio
   /dev/snd/controlC1:  zelmor 1994 F pulseaudio
   /dev/snd/controlC0:  zelmor 1994 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun May 24 16:30:11 2020
  InstallationDate: Installed on 2020-04-28 (25 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET46WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7S11H00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20B7S11H00:pvrThinkPadT450:rvnLENOVO:rn20B7S11H00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20B7S11H00
  dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 

  1   2   >