date:20201006

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  systemd-run --user fails to run

Status in systemd package in Ubuntu:
  Expired

Bug description:
  Almost fresh install of 20.04, I run:

  $ systemd-run --user --wait true

  As is documented in the man page for systemd-run, and get the output:

  Failed to create bus connection: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Aug  6 12:36:53 2020
  InstallationDate: Installed on 2020-08-01 (4 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   LC_CTYPE=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2fa4d6db-e304-45ab-89aa-2a183f41fc4c ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: TRX40 Creator
  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.:bvrP1.70:bd05/29/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Creator: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.sku: 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/1890597/+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 1888575] Re: Split motd-news config into a new package

2020-10-06 Thread Cody Shepherd

My attempts to verify test case k) seem to indicate there is still a
problem somewhere.

I've verified

i) that grub-legacy-ec2 is no longer in the server seed [1]
iv) that the livecd.ubuntu-cpc.manifest contains grub-legacy-ec2 and 
ubuntu-server.

However,

ii) the rootfs manifest has not retained ubuntu-server
iii) cpc "secret sauce" hooks which purge grub-legacy-ec2 have not retained 
ubuntu-server.

The failure of ii) occurred in a livefs-build of the ubuntu-cpc project
in the xenial branch livecd-rootfs at version 2.408.61 (02ea8c93).

The failure of iii) occurred in a build of CPC "secret sauce" hooks
using the Ubuntu Old Fashioned tool [2] and the same branch/revision of
livecd-rootfs described above.

[1] 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/tree/server?h=xenial
[2] https://github.com/chrisglass/ubuntu-old-fashioned

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  j) Perform a release upgrade from the previous ubuntu release to the
  one being tested while having ubuntu-server NOT installed (or use a
  desktop install). At the end, motd-news should be disabled. Verify
  with:

  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)

  k) Test that supporting changes for xenial are in place:

[Touch-packages] [Bug 1898713] Re: Xorg crashes sometimes with Easystrokes

** Package changed: xorg (Ubuntu) => xorg-server (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/1898713

Title:
  Xorg crashes sometimes with Easystrokes

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xorg crashes, session closes, all unsaved data is gone.

  What I did / Reproducing
  ===

  It happens when I use Easystrokes to emulate `Ctrl+F4` or
  `Ctrl+PageUp/Down`.

  So far it happened about 5 recognized times, 3 recorded within the
  last 3(?) month. twice during tab switching in incognito Firefox and
  once in VSCode.

  Reproducability
  
  I feel it's very consistent in crashing in Firefox incognito. But it's not 
purposely reproducible 100%.

  I would give more information, but the stacktrace of the crashdump
  does not tell much. I installed debug symbols for xorg, but they made
  no change viewing it.

  Here is the (obscured) stack trace:

  ```
  Reading symbols from /usr/lib/xorg/Xorg...
  Reading symbols from 
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
  [New LWP 100716]
  [New LWP 100705]
  [New LWP 100704]
  [New LWP 100707]
  [New LWP 100709]
  [New LWP 100708]
  [New LWP 100706]
  [New LWP 100711]
  [New LWP 100710]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  --Type  for more, q to quit, c to continue without paging--
  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x55a0da61fe9c in miPointerSetPosition (
  pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
  screenx=screenx@entry=0x7f707b57d570, 
  screeny=screeny@entry=0x7f707b57d578, 
  nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
  at ../../../../mi/mipointer.c:610
  610   ../../../../mi/mipointer.c: No such file or directory.
  [Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
  (gdb) 
  (gdb) 
  (gdb) bt full
  #0  0x55a0da61fe9c in miPointerSetPosition
  (pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at 
../../../../mi/mipointer.c:610
  pScreenPriv = 
  pScreen = 
  newScreen = 0x254
  x = 802
  y = 596
  switch_screen = 0
  should_constrain_barriers = 0
  i = 
  pPointer = 0x0
  #1  0x55a0da4ec840 in positionSprite
  (dev=dev@entry=0x55a0dc969400, mode=mode@entry=0, 
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580, 
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570, 
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at 
../../../../dix/getevents.c:961
  scr = 
  tmpx = 801.02961125081322
  tmpy = 595.47038874918678
  #2  0x55a0da4ecf4d in positionSprite
  (events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578, 
scre--Type  for more, q to quit, c to continue without paging--
  enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580, 
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at 
../../../../dix/getevents.c:952
  scr = 0x0
  num_events = 2
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #3  fill_pointer_events (events=0x7f708d903c20, 
  events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, 
type=, buttons=buttons@entry=0, ms=ms@entry=289728198, 
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at 
../../../../dix/getevents.c:1434
  num_events = 2
  --Type  for more, q to quit, c to continue without paging--
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #4  0x55a0da4ee620 in GetPointerEvents
  (events=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, type=, type@entry=6, buttons=buttons@entry=0,

[Touch-packages] [Bug 1898447] Re: HDMI sound output disappears after sleep

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

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

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  umayr  4915 F pulseaudio
   /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
   /dev/snd/controlC1:  umayr  4915 F pulseaudio
   /dev/snd/controlC2:  umayr  4915 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-12 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  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.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898447/+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 1898646] Re: Ubuntu 20.04 without sound with Via 1705 chipset

*** This bug is a duplicate of bug 1793640 ***
https://bugs.launchpad.net/bugs/1793640

You don't need to do anything more, thanks.

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

Title:
  Ubuntu 20.04 without sound with Via 1705 chipset

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  working very well with ubuntu 18.04 during two years with the chipset Via 
1705,upgrade to ubuntu 20.04 sound do not work. Without sound, only appear 
ficticius in configuration without any device detected.
  We do all the steps indicated in the link 
https://help.ubuntu.com/community/SoundTroubleshootingProcedure but don't 
resolved.
  We like of Ubuntu 20.04, please need a solution. Thanks.

  Estimados, trabajamos muy bien con el Ubuntu 18.04 durante dos añoscon el 
chip Via 1705 sin problemas, com un sonido refinado em caja de sonido 
Harman/Kardon, lamentablemente al actualizar para Ubuntu 20,04 el sonido no se 
escucha, intentamos todos los pasos indicados en el link 
https://help.ubuntu.com/community/SoundTroubleshootingProcedure, pero no 
resolvio.
  Nos agradó el nuevo Ubuntu 20.04, por favor una solución para no desistir de 
este. Gracias.

  Bom, para que fique bem claro, este é um equipamento com o que
  trabalho em varias regiões, por isso se houver algum colegas que
  entenda um destes idiomas, agradeceria uma solução, trabalhamos
  durante dois anos com um chipset Via 1705 num Ubuntu 18.04, ao
  atualizar para a nova versão Ubuntu 20.04 nos deparamos em que o som
  não funciona, a placa não é detectada pelo painel GUI das
  configurações do Gnome, e pelo terminal o pulseaudio não funciona.
  Favor indicar uma solução pois o resto do sistema está estável e
  funcionando, não queremos desistir da atualização. Obrigado

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity935 F timidity
   /dev/snd/pcmC0D0p:   timidity935 F...m timidity
   /dev/snd/seq:timidity935 F timidity
   /dev/snd/timer:  timidity935 f timidity
  CasperMD5CheckResult: skip
  Date: Mon Oct  5 22:31:16 2020
  InstallationDate: Installed on 2018-10-27 (709 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to focal on 2020-10-03 (2 days ago)
  dmi.bios.date: 06/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81H3-M4
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/30/2014:svnECS:pnH81H3-M4:pvr1.0:rvnECS:rnH81H3-M4:rvr1.0:cvnECS:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H81H3-M4
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898646/+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 1897478] Re: ubuntu 20.04 is extremely slow to upgrade, install or uninstall any software and launch any of it

Thanks. It looks like your system log has hundreds of megabytes of
mostly microk8s messages like:

  microk8s.daemon-kubelet[7809]: E1003 21:06:32.8472257809
kubelet.go:2183] node "kam-wrkst" not found

Please try disabling microk8s if you can, and/or run 'top' and 'iotop'
to find out which processes are using the most CPU and disk bandwidth.


  

** Package changed: apt (Ubuntu) => ubuntu

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

Title:
  ubuntu 20.04 is extremely slow to upgrade, install or uninstall any
  software and launch any of it

Status in Ubuntu:
  Incomplete

Bug description:
  After upgrade from 18.04 to 20.04, any upgrade, installing or uninstalling of 
any softwares take a long time to be done sometimes 2-3 hours.
   and no one of tools monitors show where is bottleneck.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60
  Uname: Linux 5.4.0-48-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun Sep 27 16:11:22 2020
  DisplayManager: lightdm
  InstallationDate: Installed on 2018-05-05 (875 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  ShellJournal:
   -- Logs begin at Thu 2020-09-24 18:12:38 EDT, end at Sun 2020-09-27 16:18:05 
EDT. --
   -- No entries --
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1897478/+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 1880250] Autopkgtest regression report (plymouth/0.9.4git20200323-0ubuntu6.1)

2020-10-06 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted plymouth (0.9.4git20200323-0ubuntu6.1) 
for focal have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/245.4-4ubuntu3.2 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#plymouth

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Ctrl-C message displayed without any actual disk check

Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in plymouth source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  Confirmed
Status in plymouth source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Confirmed

Bug description:
  [Impact]

   * fsck messages is shown by plymouth, despite all fscks already
  completed.

  [Test Case]

   * Install Ubuntu Desktop with full disk encryption

   * Observe that fsck messages (press ctrl+c) is shown, and remains
  there on screen for a little while as plymouth transitions to gdm

   * After installing the update, observe that when fsck completes the
  messages are cleared and the transition to gdm is done without
  fsck/ctrl+c message present.

   * After this change lands in -updates, and daily desktop images are
  built with this, double check that casper-md5sum transition is also
  smooth.

  
  [Regression Potential] 

   * plymouth spinner theme is adjusted to clear the footer, at the end
  of fsck, even if systemd-fsckd didn't do that. At the moment there are
  two consumers of the fsck apis systemd-fsckd & casper-md5sum used on
  installed systems and live-isos respectively. If something else pushes
  messages to the footer, they might get cleared at the end of fsck.

  [Other Info]
   
   * Original bug report

  It seems the transition to bgrt lost something with Ubuntu's disk
  check details. The only thing I see on my screen during a long disk
  check is the "press Ctrl-C to stop all in progress disk checks" with
  no progress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+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 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces

2020-10-06 Thread Jay Vosburgh

Si-Wei,

In the test environment I'm using, the only change needed was to
initramfs-tools.  I suspect the udevd change you're thinking of was an
alternate implementation that we did not proceed with due to the
regression it introduced (that network interface names would change).

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

Title:
  netplan should consider adding more udev attribute for exact matching
  of failover 3-netdev interfaces

Status in netplan:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in netplan.io source package in Bionic:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  [Impact]

  * At present, virtual machines utilizing net_failover network
  interface configurations are incorrectly configured due to the
  reliance on the MAC address to identify specific network interfaces.
  When net_failover is utilized, multiple interfaces will bear the same
  MAC address (the net_failover master itself, as well as the interfaces
  subordinate to it), rendering the MAC address ineffective for unique
  identification of the interface.  This results in incorrect naming of
  network interfaces from the "set-name" directive in the netplan
  configuration.

  * The solution here is to use the interface name instead of the MAC
  address when the interface is a net_failover master device.  Logic is
  added on initramfs-tools to check the device type and virtio flags to
  apply this change only to net_failover master devices.

  [Test Case]

  * The change can be tested by configuring a virtual machine with a
  virtio_net network device with the "failover=on" option to the
  "-device" option to qemu, e.g.,

  -device virtio-net-
  
pci,netdev=hostnet0,id=net0,bus=pci.0,addr=0x3,mac=00:00:17:00:18:04,failover=on

  * This will set the virtio device "standby" feature bit (bit 62,
  counting from 0).  This requires a version of qemu with support for
  this feature.

  * When so configured, the netplan configuration generated by initramfs
  will not contain a "macaddress:" match directive for the network
  interface in question.

  [Regression Potential]

  * Erroneous identification of a network interface as a net_failover
  master device could lead to omission of a macaddress directive,
  causing interfaces to be incorrectly named.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1820929/+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 1898590] Re: Verify DNS fingerprints not working

2020-10-06 Thread Seth Arnold

Hello, dig will do dns lookups itself, it doesn't rely on the host
resolver configuration. Does your host resolver configuration support
dnssec? It might be worth using tcpdump or tshark or wireshark to see if
the queries are properly formed, and if the replies are correct.

Thanks

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

Title:
  Verify DNS fingerprints not working

Status in openssh package in Ubuntu:
  New

Bug description:
  When setting in /etc/ssh/ssh_config VerifyHostKeyDNS to yes the fingerprints 
are fetched, but the result is always:
  debug1: found n insecure fingerprints in DNS
  With dig +dnssec -tsshfp hostname the result is ok: ad flg is set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1898590/+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 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces

2020-10-06 Thread Si-Wei Liu

I will get some time to test it this week. Are there other packages than
initramfs-tools that are deem required  to make net_failover work on
Bionic? I recall there's some systemd-udevd level change needed not just
initramfs-tools that has to be fixed.

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

Title:
  netplan should consider adding more udev attribute for exact matching
  of failover 3-netdev interfaces

Status in netplan:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in netplan.io source package in Bionic:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  [Impact]

  * At present, virtual machines utilizing net_failover network
  interface configurations are incorrectly configured due to the
  reliance on the MAC address to identify specific network interfaces.
  When net_failover is utilized, multiple interfaces will bear the same
  MAC address (the net_failover master itself, as well as the interfaces
  subordinate to it), rendering the MAC address ineffective for unique
  identification of the interface.  This results in incorrect naming of
  network interfaces from the "set-name" directive in the netplan
  configuration.

  * The solution here is to use the interface name instead of the MAC
  address when the interface is a net_failover master device.  Logic is
  added on initramfs-tools to check the device type and virtio flags to
  apply this change only to net_failover master devices.

  [Test Case]

  * The change can be tested by configuring a virtual machine with a
  virtio_net network device with the "failover=on" option to the
  "-device" option to qemu, e.g.,

  -device virtio-net-
  
pci,netdev=hostnet0,id=net0,bus=pci.0,addr=0x3,mac=00:00:17:00:18:04,failover=on

  * This will set the virtio device "standby" feature bit (bit 62,
  counting from 0).  This requires a version of qemu with support for
  this feature.

  * When so configured, the netplan configuration generated by initramfs
  will not contain a "macaddress:" match directive for the network
  interface in question.

  [Regression Potential]

  * Erroneous identification of a network interface as a net_failover
  master device could lead to omission of a macaddress directive,
  causing interfaces to be incorrectly named.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1820929/+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 1898157] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2020-10-06 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Hello

  
  while upgrading from 18.04 LTS to 20.04 LTS I found this Error, please 
resolve it

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct  2 10:43:58 2020
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2020-04-04 (180 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to focal on 2020-10-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1898157/+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 1898157] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2020-10-06 Thread Seth Arnold

** Information type changed from Private Security to Public

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

Title:
  package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Hello

  
  while upgrading from 18.04 LTS to 20.04 LTS I found this Error, please 
resolve it

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct  2 10:43:58 2020
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2020-04-04 (180 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to focal on 2020-10-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1898157/+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 1732962] Re: apport uses sys.argv instead of named arguments

This bug was fixed in the package apport - 2.20.9-0ubuntu7.18

---
apport (2.20.9-0ubuntu7.18) bionic; urgency=medium

  * data/apport: Introduce support for non-positional arguments so we can
easily extend core_pattern in the future (LP: #1732962)

 -- Matthieu Clemenceau   Fri, 21 Aug
2020 10:12:55 -0500

** Changed in: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1732962

Title:
  apport uses sys.argv instead of named arguments

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Won't Fix
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Bionic:
  Fix Released
Status in apport source package in Cosmic:
  Won't Fix
Status in apport source package in Disco:
  Fix Released

Bug description:
  SRU Description

  [Impact]
  data/apport which processes core files expects a certain quantity of 
arguments in a specific order. This ended up causing an issue with some 
security updates where we were trying to support a new version of apport on a 
host system and one inside a container.
  This SRU for xenial and bionic based on the work made in cosmic enabled 
proper handling of named argument.
  Note that this is disabled for now on ALL series

  [Test Case]
  No real test here since apport general behavior should be unchanged Just to 
check that the feature is disable, /proc/sys/kernel/core_pattern
  content should remain unchanged :

  $> cat /proc/sys/kernel/core_pattern
  |/usr/share/apport/apport %p %s %c %d %P %E

  [Regression Potential]
  The new feature is not enabled so the regression risk is fairly low. this 
will take place in a future coordinated SRU across all LTS but in the meanwhile 
we can make sure that there's no regression by making sure apport still behave 
properly. starting and killing xeyes should trigger apport normal operation and 
start apport.
  $> xeyes &
  $> kill -SEGV $!

  End SRU Description

  data/apport which processes core files expects a certain quantity of
  arguments in a specific order. This ended up causing an issue with
  some security updates where we were trying to support a new version of
  apport on a host system and one inside a container.  Here's something
  of an example:

  347 # Normal startup
  348 if len(sys.argv) not in (5, 6):
  349 try:
  350 print('Usage: %s [global pid]' % sys.argv[0])
  351 print('The core dump is read from stdin.')

  We could not maintain backwards compatibility because "global pid" is
  an optional argument and "dump mode" was a new argument. So if there
  were five arguments its possible the last one was "dump mode" (no
  global pid) or "global pid" (no support for dump mode).

  Its possible to use strings in /proc/sys/kernel/core_pattern so we
  could use those and have apport accept named arguments e.g:

  $ cat /proc/sys/kernel/core_pattern
  |/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d 
--global-pid=%P

  ['/home/bdmurray/source-trees/apport/artful/data/apport', '--
  pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global-
  pid=5870']

  Tyler said "that's probably a nice cleanup to make no matter what
  because the magic arg ordering is dangerous".

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

2020-10-06 Thread Brian Murray

The verification of the Stable Release Update for apport 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1732962

Title:
  apport uses sys.argv instead of named arguments

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Won't Fix
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Bionic:
  Fix Released
Status in apport source package in Cosmic:
  Won't Fix
Status in apport source package in Disco:
  Fix Released

Bug description:
  SRU Description

  [Impact]
  data/apport which processes core files expects a certain quantity of 
arguments in a specific order. This ended up causing an issue with some 
security updates where we were trying to support a new version of apport on a 
host system and one inside a container.
  This SRU for xenial and bionic based on the work made in cosmic enabled 
proper handling of named argument.
  Note that this is disabled for now on ALL series

  [Test Case]
  No real test here since apport general behavior should be unchanged Just to 
check that the feature is disable, /proc/sys/kernel/core_pattern
  content should remain unchanged :

  $> cat /proc/sys/kernel/core_pattern
  |/usr/share/apport/apport %p %s %c %d %P %E

  [Regression Potential]
  The new feature is not enabled so the regression risk is fairly low. this 
will take place in a future coordinated SRU across all LTS but in the meanwhile 
we can make sure that there's no regression by making sure apport still behave 
properly. starting and killing xeyes should trigger apport normal operation and 
start apport.
  $> xeyes &
  $> kill -SEGV $!

  End SRU Description

  data/apport which processes core files expects a certain quantity of
  arguments in a specific order. This ended up causing an issue with
  some security updates where we were trying to support a new version of
  apport on a host system and one inside a container.  Here's something
  of an example:

  347 # Normal startup
  348 if len(sys.argv) not in (5, 6):
  349 try:
  350 print('Usage: %s [global pid]' % sys.argv[0])
  351 print('The core dump is read from stdin.')

  We could not maintain backwards compatibility because "global pid" is
  an optional argument and "dump mode" was a new argument. So if there
  were five arguments its possible the last one was "dump mode" (no
  global pid) or "global pid" (no support for dump mode).

  Its possible to use strings in /proc/sys/kernel/core_pattern so we
  could use those and have apport accept named arguments e.g:

  $ cat /proc/sys/kernel/core_pattern
  |/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d 
--global-pid=%P

  ['/home/bdmurray/source-trees/apport/artful/data/apport', '--
  pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global-
  pid=5870']

  Tyler said "that's probably a nice cleanup to make no matter what
  because the magic arg ordering is dangerous".

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1732962/+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 1732962] Re: apport uses sys.argv instead of named arguments

This bug was fixed in the package apport - 2.20.1-0ubuntu2.25

---
apport (2.20.1-0ubuntu2.25) xenial; urgency=medium

  * data/apport: Introduce support for non-positional arguments so we can
easily extend core_pattern in the future (LP: #1732962)

 -- Matthieu Clemenceau   Fri, 21 Aug
2020 10:24:13 -0500

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

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

Title:
  apport uses sys.argv instead of named arguments

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Won't Fix
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Bionic:
  Fix Released
Status in apport source package in Cosmic:
  Won't Fix
Status in apport source package in Disco:
  Fix Released

Bug description:
  SRU Description

  [Impact]
  data/apport which processes core files expects a certain quantity of 
arguments in a specific order. This ended up causing an issue with some 
security updates where we were trying to support a new version of apport on a 
host system and one inside a container.
  This SRU for xenial and bionic based on the work made in cosmic enabled 
proper handling of named argument.
  Note that this is disabled for now on ALL series

  [Test Case]
  No real test here since apport general behavior should be unchanged Just to 
check that the feature is disable, /proc/sys/kernel/core_pattern
  content should remain unchanged :

  $> cat /proc/sys/kernel/core_pattern
  |/usr/share/apport/apport %p %s %c %d %P %E

  [Regression Potential]
  The new feature is not enabled so the regression risk is fairly low. this 
will take place in a future coordinated SRU across all LTS but in the meanwhile 
we can make sure that there's no regression by making sure apport still behave 
properly. starting and killing xeyes should trigger apport normal operation and 
start apport.
  $> xeyes &
  $> kill -SEGV $!

  End SRU Description

  data/apport which processes core files expects a certain quantity of
  arguments in a specific order. This ended up causing an issue with
  some security updates where we were trying to support a new version of
  apport on a host system and one inside a container.  Here's something
  of an example:

  347 # Normal startup
  348 if len(sys.argv) not in (5, 6):
  349 try:
  350 print('Usage: %s [global pid]' % sys.argv[0])
  351 print('The core dump is read from stdin.')

  We could not maintain backwards compatibility because "global pid" is
  an optional argument and "dump mode" was a new argument. So if there
  were five arguments its possible the last one was "dump mode" (no
  global pid) or "global pid" (no support for dump mode).

  Its possible to use strings in /proc/sys/kernel/core_pattern so we
  could use those and have apport accept named arguments e.g:

  $ cat /proc/sys/kernel/core_pattern
  |/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d 
--global-pid=%P

  ['/home/bdmurray/source-trees/apport/artful/data/apport', '--
  pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global-
  pid=5870']

  Tyler said "that's probably a nice cleanup to make no matter what
  because the magic arg ordering is dangerous".

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1732962/+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 1898646] Re: Ubuntu 20.04 without sound with Via 1705 chipset

2020-10-06 Thread Marcelo Smacom

*** This bug is a duplicate of bug 1793640 ***
https://bugs.launchpad.net/bugs/1793640

Thanks for your contatct, gracias por seu contacto, obrigado pela resposta.
Reading with attention bug#1793640 and installing with apt-get install timidity
timidity-daemon, all the sound return with excelent funcionality.

How should I report correctly that the problem of this bug was fixed?
Como debo informar que el problema deste bug fu solucionado?
Sem querer incomodar mais ficamos ao seu dispor.

Marcelo Mattiello.
SMA Com. e Rep.de Informtica Ltda.
Fone/Fax: 0xx47-3045-2590
Email: marc...@smacom.com.br
Celular: 0xx47-8402-5563
Skype: marcelo_smacom
www.smacom.com.br

Data: 05/10/2020
De: Daniel van Vugt 1898...@bugs.launchpad.net
Para: Bug 1898646 1898...@bugs.launchpad.net
Assunto: [Bug 1898646] Re: Ubuntu 20.04 without sound with Via 1705 chipset ***
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.

** 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 subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1898646

Title:
Ubuntu 20.04 without sound with Via 1705 chipset

Status in pulseaudio package in Ubuntu:
New

Bug description:
working very well with ubuntu 18.04 during two years with the chipset
Via 1705,upgrade to ubuntu 20.04 sound do not work. Without sound, only appear
ficticius in configuration without any device detected.
We do all the steps indicated in the link
https://help.ubuntu.com/community/SoundTroubleshootingProcedure but don't
resolved.
We like of Ubuntu 20.04, please need a solution. Thanks.

Estimados, trabajamos muy bien con el Ubuntu 18.04 durante dos
aoscon el chip Via 1705 sin problemas, com un sonido refinado em caja
de sonido Harman/Kardon, lamentablemente al actualizar para Ubuntu 20,04 el
sonido no se escucha, intentamos todos los pasos indicados en el link
https://help.ubuntu.com/community/SoundTroubleshootingProcedure, pero no
resolvio.
Nos agrad el nuevo Ubuntu 20.04, por favor una solucin
para no desistir de este. Gracias.

Bom, para que fique bem claro, este um equipamento com o que
trabalho em varias regies, por isso se houver algum colegas que
entenda um destes idiomas, agradeceria uma soluo,
trabalhamos
durante dois anos com um chipset Via 1705 num Ubuntu 18.04, ao
atualizar para a nova verso Ubuntu 20.04 nos deparamos em que o
som
no funciona, a placa no detectada pelo painel
GUI das
configuraes do Gnome, e pelo terminal o pulseaudio
no funciona.
Favor indicar uma soluo pois o resto do sistema
est estvel e
funcionando, no queremos desistir da atualizao.
Obrigado

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.7
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: timidity 935 F timidity
/dev/snd/pcmC0D0p: timidity 935 F...m timidity
/dev/snd/seq:timidity 935 F
timidity
/dev/snd/timer: timidity 935 f
timidity
CasperMD5CheckResult: skip
Date: Mon Oct 5 22:31:16 2020
InstallationDate: Installed on 2018-10-27 (709 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
ProcEnviron:
LANGUAGE=pt_BR:pt:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=pt_BR.UTF-8
SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to focal on 2020-10-03 (2 days ago)
dmi.bios.date: 06/30/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81H3-M4
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/30/2014:svnECS:pnH81H3-M4:pvr1.0:rvnECS:rnH81H3-M4:rvr1.0:cvnECS:ct3:cvr1.0:

dmi.product.family: To be filled by O.E.M.
dmi.product.name: H81H3-M4
dmi.product.sku: To be filled by O.E.M.

[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check

2020-10-06 Thread Brian Murray

Hello Kees, or anyone else affected,

Accepted plymouth into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/plymouth/0.9.4git20200323-0ubuntu6.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: plymouth (Ubuntu Focal)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  Ctrl-C message displayed without any actual disk check

Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in plymouth source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  Confirmed
Status in plymouth source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Confirmed

Bug description:
  [Impact]

   * fsck messages is shown by plymouth, despite all fscks already
  completed.

  [Test Case]

   * Install Ubuntu Desktop with full disk encryption

   * Observe that fsck messages (press ctrl+c) is shown, and remains
  there on screen for a little while as plymouth transitions to gdm

   * After installing the update, observe that when fsck completes the
  messages are cleared and the transition to gdm is done without
  fsck/ctrl+c message present.

   * After this change lands in -updates, and daily desktop images are
  built with this, double check that casper-md5sum transition is also
  smooth.

  
  [Regression Potential] 

   * plymouth spinner theme is adjusted to clear the footer, at the end
  of fsck, even if systemd-fsckd didn't do that. At the moment there are
  two consumers of the fsck apis systemd-fsckd & casper-md5sum used on
  installed systems and live-isos respectively. If something else pushes
  messages to the footer, they might get cleared at the end of fsck.

  [Other Info]
   
   * Original bug report

  It seems the transition to bgrt lost something with Ubuntu's disk
  check details. The only thing I see on my screen during a long disk
  check is the "press Ctrl-C to stop all in progress disk checks" with
  no progress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+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 1898785] [NEW] [VivoBook 15_ASUS Laptop X542UF, Realtek ALC294, Speaker, Internal] No sound at all

2020-10-06 Thread yochay

Public bug reported:

As I tried to update my files, and install other addons from the terminal, 
nothing happened.. 
On my computer I have dual boot option and when Im using Windows it works fine. 
At ubuntu the speakers doesnt work at any application..

Thanks for you help :)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  yochay 1124 F pulseaudio
 /dev/snd/pcmC0D0p:   yochay 1124 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  6 23:36:02 2020
InstallationDate: Installed on 2020-09-23 (13 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
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:  yochay 1124 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [VivoBook 15_ASUS Laptop X542UF, Realtek ALC294, Speaker, Internal] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X542UF.306
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X542UF
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.:bvrX542UF.306:bd05/22/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX542UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook 15_ASUS Laptop X542UF
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug focal

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

Title:
  [VivoBook 15_ASUS Laptop X542UF, Realtek ALC294, Speaker, Internal] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  As I tried to update my files, and install other addons from the terminal, 
nothing happened.. 
  On my computer I have dual boot option and when Im using Windows it works 
fine. At ubuntu the speakers doesnt work at any application..

  Thanks for you help :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yochay 1124 F pulseaudio
   /dev/snd/pcmC0D0p:   yochay 1124 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  6 23:36:02 2020
  InstallationDate: Installed on 2020-09-23 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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:  yochay 1124 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [VivoBook 15_ASUS Laptop X542UF, Realtek ALC294, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X542UF.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X542UF
  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.:bvrX542UF.306:bd05/22/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX542UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook 15_ASUS Laptop X542UF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Touch-packages] [Bug 1898447] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1898447/+attachment/5418509/+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/1898447

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  umayr  4915 F pulseaudio
   /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
   /dev/snd/controlC1:  umayr  4915 F pulseaudio
   /dev/snd/controlC2:  umayr  4915 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-12 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  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.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1898447/+attachment/5418507/+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/1898447

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  umayr  4915 F pulseaudio
   /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
   /dev/snd/controlC1:  umayr  4915 F pulseaudio
   /dev/snd/controlC2:  umayr  4915 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-12 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  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.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1898447/+attachment/5418508/+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/1898447

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  umayr  4915 F pulseaudio
   /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
   /dev/snd/controlC1:  umayr  4915 F pulseaudio
   /dev/snd/controlC2:  umayr  4915 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-12 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  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.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1898447/+attachment/5418510/+files/PulseList.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/1898447

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  umayr  4915 F pulseaudio
   /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
   /dev/snd/controlC1:  umayr  4915 F pulseaudio
   /dev/snd/controlC2:  umayr  4915 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-12 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  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.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898447/+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 1867157] Re: Improve command-not-found package headers

2020-10-06 Thread Dimitri John Ledkov

# /usr/lib/command-not-found python3.7

Command 'python3.7' not found, did you mean:

  command 'python2.7' from deb python2.7 (2.7.18-1~20.04)
  command 'python3.8' from deb python3.8 (3.8.5-1~20.04)
  command 'python3.9' from deb python3.9 (3.9.0~rc1-1~20.04)

Try: apt install 


On focal, correctly shows that python3.8 is installable / available by 
installing python3.8 package (despite the /usr/bin/python3.8 shipped in 
python3.8-minimal package).

Thus cnf metadata of python3.8 3.8.5-1~20.04 is now correct.

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

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

Title:
  Improve command-not-found package headers

Status in python-defaults package in Ubuntu:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3.8 package in Ubuntu:
  Fix Released
Status in python3.8 source package in Focal:
  Fix Committed

Bug description:
  Improve command-not-found package headers

  
  command-not-found uses package metadata, and to improve the UX of the 
misspelled commands / proposed packages.

  python2.7-minimal should gain XB-Cnf-Visible-Pkgname: python2.7

  python3.8-minimal should gain XB-Cnf-Visible-Pkgname: python3.8

  python2-minimal should gain XB-Cnf-Visible-Pkgname: python2

  python3-minimal should gain XB-Cnf-Visible-Pkgname: python3

  This will then improve these messages from:

  """
command 'python2.7' from deb python2.7-minimal (2.7.17-1)
command 'python3.8' from deb python3.8-minimal (3.8.0-5)
command 'python2' from deb python2-minimal (2.7.17-2)
command 'python3' from deb python3-minimal (3.7.5-1ubuntu1)
  """

  To

  """
command 'python2.7' from deb python2.7 (2.7.17-1)
command 'python3.8' from deb python3.8 (3.8.0-5)
command 'python2' from deb python2 (2.7.17-2)
command 'python3' from deb python3 (3.7.5-1ubuntu1)
  """

  
  python3 should drop
  XB-Cnf-Extra-Commands: python
  XB-Cnf-Priority-Bonus: 5

  Such that it stops suggesting that somehow python is available from
  python3 package, which is a lie.

  There is a special case for "python" command hint in command-not-found
  already, which simply points people to "python3".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1867157/+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 1898447] Re: HDMI sound output disappears after sleep

apport information

** Tags added: apport-collected

** Description changed:

  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME settings
  sound settings after waking the computer up from sleep. Running `pacmd
  list-cards` does show the HDMI sound output listed. I can bring the
  output back as a choice if I run `pulseaudio -k`, but I will lose the
  choice to select this output if I put the computer to sleep, leaving me
  only with the S/PDIF output from my motherboard.
  
  I didnt see this issue prior to what I suspect was an `apt upgrade`.
  
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3
  
  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.9
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  umayr  4915 F pulseaudio
+  /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
+  /dev/snd/controlC1:  umayr  4915 F pulseaudio
+  /dev/snd/controlC2:  umayr  4915 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-01-12 (267 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: pulseaudio 1:13.99.1-1ubuntu3.6
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
+ Tags:  focal
+ Uname: Linux 5.4.0-48-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/06/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F11
+ dmi.board.asset.tag: Default string
+ dmi.board.name: X570 AORUS MASTER
+ 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.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: Default string
+ dmi.product.name: X570 AORUS MASTER
+ dmi.product.sku: Default string
+ dmi.product.version: -CF
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1898447/+attachment/5418505/+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/1898447

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID

[Touch-packages] [Bug 1898447] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1898447/+attachment/5418506/+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/1898447

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  umayr  4915 F pulseaudio
   /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
   /dev/snd/controlC1:  umayr  4915 F pulseaudio
   /dev/snd/controlC2:  umayr  4915 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-12 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  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.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898447/+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 495981] Re: NM disconnects Wi-Fi every 2 minutes but iwconfig+dhclient and wicd don't -- ath9k

2020-10-06 Thread Chris

I'm going to bump this, as the last report was years ago. I'm now
experiencing this issue on a Qualcomm Atheros AR938x device I've had for
years now. Same issue with constant disconnects as well as a new issue
that might involve iommu?

[  680.361521] ath9k :21:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x0010 address=0xfdee1544 flags=0x]
[  680.425700] ath9k :21:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x0010 address=0xfe720fc4 flags=0x]
[  680.425707] ath9k :21:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x0010 address=0xfe721000 flags=0x]
[  680.489520] ath9k :21:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x0010 address=0xff0d5a44 flags=0x]
[  680.650051] wlo1: authenticate with 10:c3:7b:ce:7e:ac
[  680.665173] wlo1: send auth to 10:c3:7b:ce:7e:ac (try 1/3)
[  680.666229] wlo1: authenticated
[  680.669072] wlo1: associate with 10:c3:7b:ce:7e:ac (try 1/3)
[  680.670356] wlo1: RX AssocResp from 10:c3:7b:ce:7e:ac (capab=0x11 status=0 
aid=4)
[  680.670494] wlo1: associated
[ 1014.692234] wlo1: authenticate with 10:c3:7b:ce:7e:ac
[ 1014.707630] wlo1: send auth to 10:c3:7b:ce:7e:ac (try 1/3)
[ 1014.708714] wlo1: authenticated
[ 1014.711340] wlo1: associate with 10:c3:7b:ce:7e:ac (try 1/3)
[ 1014.712644] wlo1: RX AssocResp from 10:c3:7b:ce:7e:ac (capab=0x11 status=0 
aid=4)
[ 1014.712784] wlo1: associated
[ 1295.496298] wlo1: authenticate with 10:c3:7b:ce:7e:ac
[ 1295.511421] wlo1: send auth to 10:c3:7b:ce:7e:ac (try 1/3)
[ 1295.512484] wlo1: authenticated
[ 1295.514554] wlo1: associate with 10:c3:7b:ce:7e:ac (try 1/3)
[ 1295.515851] wlo1: RX AssocResp from 10:c3:7b:ce:7e:ac (capab=0x11 status=0 
aid=4)

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

Title:
  NM disconnects Wi-Fi every 2 minutes but iwconfig+dhclient and wicd
  don't -- ath9k

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager

  I have Dell studio XPS 13 running:
  Description:  Ubuntu 9.10
  Release:  9.10

  with wifi card (lspci):
  06:00.0 Network controller: Atheros Communications Inc. AR928X Wireless 
Network Adapter (PCI-Express) (rev 01)

  that works (tries to) with ath9k module.

  It connects to my access point and works ok however, It disconnects every 2-3 
min saying (in dmesg):
  [  311.600306] wlan0: RX AssocResp from 00:1d:68:0c:97:63 (capab=0x411 
status=0 aid=2)
  and then automatically reconnects... I have tried different drivers and other 
things

  Interestingly when I right-clicked on network manger applet, select ¨disable 
networking¨ and then set up everything myself on console using iwconfig and 
dhclient. IT WORKS!!!
  no disconnections
  wpa_supplicant is still running in a background but not doing anything (my 
wifi has WEP encryption).

  I´ve seen some similar reports in Internet but they seem to think that
  it is a driver problem when to me it looks like a NetworkManager
  issue...

  Hope it helps

  drphd

  ProblemType: Bug
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sat Dec 12 19:42:18 2009
  DistroRelease: Ubuntu 9.10
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  IpRoute:
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.65
   172.16.77.0/24 dev vmnet1  proto kernel  scope link  src 172.16.77.1
   172.16.158.0/24 dev vmnet8  proto kernel  scope link  src 172.16.158.1
   default via 192.168.1.254 dev wlan0
  NonfreeKernelModules: nvidia
  Package: network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: network-manager
  Uname: Linux 2.6.31-16-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/495981/+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 1898771] [NEW] suspend does not lock screen Fresh Ubuntu Mate 20.04.1

2020-10-06 Thread Richard Silver

Public bug reported:

When suspending my freshly installed 20.04.1 system I noticed that on waking a 
password is not required. lightdm does not have locking enabled on suspend. A 
workaround I found from pszafer
 on archlinux blog. 

Quoted below:


create lockscreen.sh file somewhere in your home directory with:

#!/bin/sh
XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" dm-tool lock
- I've prefer just for sure creating dmlock.service file in home dir and create 
symlink to /etc/systemd/system.
File has to be in /etc/systemd/system/dmlock.service

[Unit]
Description=DM Lock before sleep
Before=sleep.target

[Service]
ExecStart=/home/user/dir/lockscreen.sh

[Install]
WantedBy=sleep.target
For your needs, you probably need hibernate.target.

Next run following commands:

systemctl daemon-reload
systemctl enable dmlock.service
Just for sure it is working you could run:

systemctl list-unit-files
systemctl start dmlock.service
Hope it helps you a little

** Affects: ubuntu-mate
 Importance: Undecided
 Status: New

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


** Tags: lightdm lock security suspend unlock

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

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

Title:
  suspend does not lock screen Fresh Ubuntu Mate 20.04.1

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  When suspending my freshly installed 20.04.1 system I noticed that on waking 
a password is not required. lightdm does not have locking enabled on suspend. A 
workaround I found from pszafer
   on archlinux blog. 

  Quoted below:

  
  create lockscreen.sh file somewhere in your home directory with:

  #!/bin/sh
  XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" dm-tool lock
  - I've prefer just for sure creating dmlock.service file in home dir and 
create symlink to /etc/systemd/system.
  File has to be in /etc/systemd/system/dmlock.service

  [Unit]
  Description=DM Lock before sleep
  Before=sleep.target

  [Service]
  ExecStart=/home/user/dir/lockscreen.sh

  [Install]
  WantedBy=sleep.target
  For your needs, you probably need hibernate.target.

  Next run following commands:

  systemctl daemon-reload
  systemctl enable dmlock.service
  Just for sure it is working you could run:

  systemctl list-unit-files
  systemctl start dmlock.service
  Hope it helps you a little

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1898771/+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 1890272] Re: SRU: Update to the final python 2.7.18 release

This bug was fixed in the package python2.7 - 2.7.18-1~20.04

---
python2.7 (2.7.18-1~20.04) focal; urgency=medium

  * SRU: LP: #1890272: Update to to the final 2.7.18 release.

 -- Matthias Klose   Tue, 04 Aug 2020 13:16:42 +0200

** Changed in: python2.7 (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 python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1890272

Title:
  SRU: Update to the final python 2.7.18 release

Status in python2.7 package in Ubuntu:
  New
Status in python2.7 source package in Focal:
  Fix Released

Bug description:
  Ubuntu 20.04 LTS shipped with the python 2.7.18 release candidate.
  Please let's update to the final release.

  Upstream changes are:

  - Documentation changes

  - Identify as 2.7.18 instead of 2.7.18rc1

  Acceptance criteria: The package builds, and the testsuite doesn't
  show regressions.

  The package was also part of an archive test rebuild (main), and
  didn't show any regressions.

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

2020-10-06 Thread Brian Murray

The verification of the Stable Release Update for python2.7 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 python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1890272

Title:
  SRU: Update to the final python 2.7.18 release

Status in python2.7 package in Ubuntu:
  New
Status in python2.7 source package in Focal:
  Fix Released

Bug description:
  Ubuntu 20.04 LTS shipped with the python 2.7.18 release candidate.
  Please let's update to the final release.

  Upstream changes are:

  - Documentation changes

  - Identify as 2.7.18 instead of 2.7.18rc1

  Acceptance criteria: The package builds, and the testsuite doesn't
  show regressions.

  The package was also part of an archive test rebuild (main), and
  didn't show any regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1890272/+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 1897478] Re: ubuntu 20.04 is extremely slow to upgrade, install or uninstall any software and launch any of it

2020-10-06 Thread Solaris

journalctl.txt

I followed your instructions, here the result.
If I missed something please let me know.

On Tue, Sep 29, 2020 at 5:00 AM Daniel van Vugt <1897...@bugs.launchpad.net>
wrote:

> 1. Can you benchmark your disk(s) with the 'Disks' app and/or 'hdparm
> -t' and tell us what their speed is?
>
> 2. Please run this command to watch and check nothing is flooding the
> system log while it is slow:
>
>journalctl -f
>
> 3. Please try uninstalling/disabling all of your extensions:
>
> "['gnote_integrat...@awamper.gmail.com', 'ubuntu-
> appindicat...@ubuntu.com', 'user-theme@gnome-shell-
> extensions.gcampax.github.com', 'openweather-extens...@jenslody.de',
> 'extensi...@abteil.org', 'panel-...@berend.de.schouwer.gmail.com',
> 'clipboard-indica...@tudmotu.com', 'advanced-settings-in-usermenu@SHS-
> Schubert.de', 'panelsetti...@eddiefullmetal.gr',
> 'connectionmana...@ciancio.net', 'cpuf...@zdyb.tk',
> 'a...@maggiolo00.gmail.com', 'indicator-sens...@alexmurray.github.com',
> 'ryanwh...@126.com', 'pulseaudio_loopback_dev...@jocagovi.gmail.com',
> 'pulseaudio-equali...@s8dragon.vn', 'pulse-audio-shortc...@l300lvl.tk',
> 'turn-off-pulseau...@ebanat.org', 'services-syst...@abteil.org',
> 'connectionmanag...@ciancio.net', 'move_cl...@jonathan.bluemosh.com',
> 'update-extensi...@franglais125.gmail.com', 'sound-output-device-
> choo...@kgshank.net', 'systemMonitor@gnome-shell-
> extensions.gcampax.github.com', 'temperature@xtranophilist', 'force-
> quit@xtranophilist', 'alternate-tab@gnome-shell-
> extensions.gcampax.github.com', 'auto-move-windows@gnome-shell-
> extensions.gcampax.github.com', 'bettervol...@tudmotu.com',
> 'mediapla...@patapon.info', 'multi-monitors-add-on@spin83', 'native-
> window-placem...@gnome-shell-extensions.gcampax.github.com', 'apps-menu
> @gnome-shell-extensions.gcampax.github.com',
> 'harddisk...@bijidroid.gmail.com', 'launch-new-instance@gnome-shell-
> extensions.gcampax.github.com', 'places-menu@gnome-shell-
> extensions.gcampax.github.com', 'drive-menu@gnome-shell-
> extensions.gcampax.github.com', 'screenshot-window-sizer@gnome-shell-
> extensions.gcampax.github.com', 'shortc...@kyle.aims.ac.za', 'suspend-
> button@laserb', 'system-moni...@paradoxxx.zero.gmail.com',
> 'topic...@phocean.net', 'gnome-shell-trash-extension', 'window-list
> @gnome-shell-extensions.gcampax.github.com', 'windowsNavigator@gnome-
> shell-extensions.gcampax.github.com', 'workspace-indicator@gnome-shell-
> extensions.gcampax.github.com', 'workspaces-to-
> d...@passingthru67.gmail.com', 'TilixDropdown@ivku...@gmail.com',
> 'nvidiatemp@baco', 'nvidiautil@ethanwharris', 'show-
> i...@sgaraud.github.com', 'caffe...@patapon.info', 'd...@linuxdeepin.com',
> 'onboard_indica...@onboard.org', 'ubuntu-d...@ubuntu.com',
> 'persiancalen...@oxygenws.com']"
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1897478
>
> Title:
>   ubuntu 20.04 is extremely slow to upgrade, install or uninstall any
>   software and launch any of it
>
> Status in apt package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After upgrade from 18.04 to 20.04, any upgrade, installing or
> uninstalling of any softwares take a long time to be done sometimes 2-3
> hours.
>and no one of tools monitors show where is bottleneck.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
>   ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60
>   Uname: Linux 5.4.0-48-lowlatency x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
> nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu27.9
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: MATE
>   Date: Sun Sep 27 16:11:22 2020
>   DisplayManager: lightdm
>   InstallationDate: Installed on 2018-05-05 (875 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
>   ShellJournal:
>-- Logs begin at Thu 2020-09-24 18:12:38 EDT, end at Sun 2020-09-27
> 16:18:05 EDT. --
>-- No entries --
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1897478/+subscriptions
>


** Attachment added: "Home-Disk-Benchmark-Screenshot from 2020-10-05 
15-03-14.png"
   
https://bugs.launchpad.net/bugs/1897478/+attachment/5418459/+files/Home-Disk-Benchmark-Screenshot%20from%202020-10-05%2015-03-14.png

** Attachment added: "Boot--Root-disk-Benchmark-Screenshot from 2020-10-05 
15-01-23.png"
   
https://bugs.launchpad.net/bugs/1897478/+attachment/5418460/+files/Boot--Root-disk-Benchmark-Screenshot%20from%202020-10-05%2015-01-23.png

** Attachment added: "Tmp-Disk-Benchmark-Screenshot from 2020-10-05

[Touch-packages] [Bug 1898753] Re: Non-existent home directory entry in /etc/passwd

2020-10-06 Thread Patrick Goetz

** Description changed:

  This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two distros
  I've checked.
  
  This is likely a packaging error.  The syslog user appears in
  /etc/passwd as:
  
-   syslog:x:102:106::/home/syslog:/usr/sbin/nologin
+   syslog:x:102:106::/home/syslog:/usr/sbin/nologin
  
  Of course there is no directory /home/syslog.  This appears innocuous,
  but can cause problems for users that have, say autofs mounted home
- directories.  To cite one example, the python virtual envionment
- anaconda trolls through /etc/passw looking for environments in
+ directories.  To cite one example, the python virtual environment
+ anaconda trolls through /etc/passwd looking for environments in
  /home/USER.  This triggers autofs to try and mount /home/syslog, which
- doesn't existing, causing the automounter to hang under certain
+ doesn't exist, causing the automounter to hang under certain
  circumstances.  In, for example, Arch linux, this entry would appear as
  the considerably more sensible
  
-   syslog:x:102:106::/:/usr/sbin/nologin
+   syslog:x:102:106::/:/usr/sbin/nologin
  
  While an edge case in the current compute environment, this is also a
  very easy fix.  Don't reference non-existent directories. Many Ubuntu
  packages make this packaging error when creating local users with non-
  existent home directories; e.g. cups-pk-helper, which I'm filing a bug
  report for next.

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

Title:
  Non-existent home directory entry in /etc/passwd

Status in rsyslog package in Ubuntu:
  New

Bug description:
  This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two
  distros I've checked.

  This is likely a packaging error.  The syslog user appears in
  /etc/passwd as:

    syslog:x:102:106::/home/syslog:/usr/sbin/nologin

  Of course there is no directory /home/syslog.  This appears innocuous,
  but can cause problems for users that have, say autofs mounted home
  directories.  To cite one example, the python virtual environment
  anaconda trolls through /etc/passwd looking for environments in
  /home/USER.  This triggers autofs to try and mount /home/syslog, which
  doesn't exist, causing the automounter to hang under certain
  circumstances.  In, for example, Arch linux, this entry would appear
  as the considerably more sensible

    syslog:x:102:106::/:/usr/sbin/nologin

  While an edge case in the current compute environment, this is also a
  very easy fix.  Don't reference non-existent directories. Many Ubuntu
  packages make this packaging error when creating local users with non-
  existent home directories; e.g. cups-pk-helper, which I'm filing a bug
  report for next.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1898753/+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 1898729] Re: shim can end up being removed

Ok.  If this was initially installed using a currently-supported
release, it might be good to look back at the logs and at the code in
that version of the installer, to see if there's something we should fix
wrt the shim-signed package being marked as auto-installed instead of
manual.

(But a system installed here using 19.10 doesn't have shim-signed marked
as auto-installed, so I guess any bug in that regard may be rather old.)

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+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 1898421] Re: Suspend - takes 30 seconds to fully suspend

2020-10-06 Thread Tichun

Initial report used an old desktop, below is the output from a Renoir
laptop.

[ 1134.925114] PM: suspend entry (s2idle)
[ 1134.936220] Filesystems sync: 0.011 seconds
[ 1134.936483] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 1134.938761] OOM killer disabled.
[ 1134.938762] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[ 1134.940031] printk: Suspending console(s) (use no_console_suspend to debug)
[ 1134.962659] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 1134.963415] sd 1:0:0:0: [sda] Stopping disk
[ 1135.266599] [drm] free PSP TMR buffer
[ 1135.313789] ACPI: EC: interrupt blocked
[ 1135.331004] amdgpu :02:00.0: refused to change power state from D0 to 
D3hot
[ 1135.331007] xhci_hcd :02:00.4: refused to change power state from D0 to 
D3hot
[ 1150.496373] ACPI: EC: interrupt unblocked
[ 1150.537397] sd 1:0:0:0: [sda] Starting disk
[ 1150.556055] [drm] PCIE GART of 1024M enabled (table at 0x00F40090).
[ 1150.556092] [drm] PSP is resuming...
[ 1150.575984] [drm] reserve 0x40 from 0xf41fc0 for PSP TMR
[ 1150.848719] ata1: SATA link down (SStatus 0 SControl 300)
[ 1150.899613] amdgpu: SMU is resuming...
[ 1150.899660] amdgpu: dpm has been disabled
[ 1150.899676] amdgpu: SMU is resumed successfully!
[ 1151.011434] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1151.016213] ata2.00: configured for UDMA/133
[ 1151.144093] [drm] kiq ring mec 2 pipe 1 q 0
[ 1151.152943] [drm] DMUB hardware initialized: version=0x0001
[ 1151.282435] [drm] Failed to add display topology, DTM TA is not initialized.
[ 1151.309163] [drm] VCN decode and encode initialized successfully(under DPG 
Mode).
[ 1151.309272] [drm] JPEG decode initialized successfully.
[ 1151.309578] amdgpu :02:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[ 1151.309581] amdgpu :02:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 
on hub 0
[ 1151.309582] amdgpu :02:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 
on hub 0
[ 1151.309584] amdgpu :02:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 
on hub 0
[ 1151.309586] amdgpu :02:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 
on hub 0
[ 1151.309588] amdgpu :02:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 
on hub 0
[ 1151.309589] amdgpu :02:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 
on hub 0
[ 1151.309591] amdgpu :02:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 
on hub 0
[ 1151.309593] amdgpu :02:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 
on hub 0
[ 1151.309595] amdgpu :02:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 
on hub 0
[ 1151.309596] amdgpu :02:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 
1
[ 1151.309598] amdgpu :02:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on 
hub 1
[ 1151.309600] amdgpu :02:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on 
hub 1
[ 1151.309601] amdgpu :02:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on 
hub 1
[ 1151.309603] amdgpu :02:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on 
hub 1
[ 1151.318752] OOM killer enabled.
[ 1151.318754] Restarting tasks ... done.
[ 1151.343199] PM: suspend exit
[ 1158.309787] [drm] Failed to add display topology, DTM TA is not initialized.

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

Title:
  Suspend - takes 30 seconds to fully suspend

Status in systemd package in Ubuntu:
  New

Bug description:
  Using `systemctl suspend` or suspending through the power menu takes
  30 seconds for the system to fully suspend.

  Expected:
  The system suspends in under 2 seconds (e.g. check Arch Linux)
  Actual:
  The system takes 30 seconds to suspend (31.44 seconds using a stopwatch)

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Codename: focal

  DMESG: 
  [ 8521.093270] PM: suspend entry (deep)
  [ 8521.104938] Filesystems sync: 0.011 seconds
  [ 8521.182123] Freezing user space processes ... (elapsed 0.004 seconds) done.
  [ 8521.187004] OOM killer disabled.
  [ 8521.187005] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [ 8521.188754] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 8521.219072] sd 1:0:0:0: [sda] Synchronizing SCSI cache
  [ 8521.219621] sd 1:0:0:0: [sda] Stopping disk
  [ 8521.958776] ACPI: Preparing to enter system sleep state S3
  [ 8521.960793] PM: Saving platform NVS memory
  [ 8521.961025] Disabling non-boot CPUs ...
  [ 8521.961558] IRQ 26: no longer affine to CPU1
  [ 8521.962593] smpboot: CPU 1 is now offline
  [ 8521.964649] IRQ 18: no longer affine to CPU2
  [ 8521.965669] smpboot: CPU 2 is now offline
  [ 8521.967970] IRQ 27: no longer affine to CPU3
  [ 8521.968991] smpboot: CPU 3 is now offline
  [ 8521.970958] ACPI: Low-level resume complete
  [ 8521.970958] PM: Restoring platform NVS memory
  [ 8521.976827] Enabling non-boot CPUs ...
  [ 8521.976893] x86:

[Touch-packages] [Bug 1898753] [NEW] Non-existent home directory entry in /etc/passwd

2020-10-06 Thread Patrick Goetz

Public bug reported:

This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two distros
I've checked.

This is likely a packaging error.  The syslog user appears in
/etc/passwd as:

  syslog:x:102:106::/home/syslog:/usr/sbin/nologin

Of course there is no directory /home/syslog.  This appears innocuous,
but can cause problems for users that have, say autofs mounted home
directories.  To cite one example, the python virtual envionment
anaconda trolls through /etc/passw looking for environments in
/home/USER.  This triggers autofs to try and mount /home/syslog, which
doesn't existing, causing the automounter to hang under certain
circumstances.  In, for example, Arch linux, this entry would appear as
the considerably more sensible

  syslog:x:102:106::/:/usr/sbin/nologin

While an edge case in the current compute environment, this is also a
very easy fix.  Don't reference non-existent directories. Many Ubuntu
packages make this packaging error when creating local users with non-
existent home directories; e.g. cups-pk-helper, which I'm filing a bug
report for next.

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

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

Title:
  Non-existent home directory entry in /etc/passwd

Status in rsyslog package in Ubuntu:
  New

Bug description:
  This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two
  distros I've checked.

  This is likely a packaging error.  The syslog user appears in
  /etc/passwd as:

syslog:x:102:106::/home/syslog:/usr/sbin/nologin

  Of course there is no directory /home/syslog.  This appears innocuous,
  but can cause problems for users that have, say autofs mounted home
  directories.  To cite one example, the python virtual envionment
  anaconda trolls through /etc/passw looking for environments in
  /home/USER.  This triggers autofs to try and mount /home/syslog, which
  doesn't existing, causing the automounter to hang under certain
  circumstances.  In, for example, Arch linux, this entry would appear
  as the considerably more sensible

syslog:x:102:106::/:/usr/sbin/nologin

  While an edge case in the current compute environment, this is also a
  very easy fix.  Don't reference non-existent directories. Many Ubuntu
  packages make this packaging error when creating local users with non-
  existent home directories; e.g. cups-pk-helper, which I'm filing a bug
  report for next.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1898753/+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 1898729] Re: shim can end up being removed

2020-10-06 Thread Iain Lane

Cheers Steve. Nope, -proposed is not enabled.

Yes, it happened - it was the result of an explicit autoremove on my
part though after I had dist-upgraded to current focal-updates. I should
have noticed that this was happening and stopped it, granted. :)

Attached is the snippet of apt's term.log corresponding to the
autoremove run. It crapped out at the end as usual because I have a tiny
/boot; not included but mentioning because it might mean the log is
truncated a bit.

Now, this system has been through several Ubuntu development cycles.
It's likely to be unclean. So I don't mind if the priority is low but
making use of this feature of apt feels sensible to me, although
admittedly there's a question about where we would stop if we started to
do it.

** Attachment added: "shim"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+attachment/5418422/+files/shim

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

2020-10-06 Thread Eric Desrochers

I have a first iteration of a package:

It's not a final solution nor a long term solution. It is only made to
determine if its fix the problem before considering an SRU: (Ideally one
would test this package in non-production area)

Adding this PPA to your system
sudo add-apt-repository ppa:slashd/sf263217
sudo apt-get update

Please report back any feedbacks in this bug.

- Eric

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

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in keepalived source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in keepalived source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

2020-10-06 Thread Eric Desrochers

The above test package has been made for 'systemd' in bionic ^

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

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in keepalived source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in keepalived source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have to be hostname).
  vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
  vrrp_mcast_group6 ff02::12   # optional, default ff02::12
  enable_traps # enable SNMP traps
  }
  vrrp_sync_group collection {
  group {
  wan

[Touch-packages] [Bug 1898747] [NEW] [HP Pavilion Notebook, Nvidia GPU 80 HDMI/DP, Digital Out, HDMI] No sound at all on hdmi audio output

2020-10-06 Thread Lucas Arroyo Blanco

Public bug reported:

Recently I reinstalled ubuntu on my laptop and this time I found that
when I connect the laptop to the tv with the hdmi I manage to get the
video working but with no sound, it reproduces from the laptop speakers.

On pulseaudio volume control the digital stereo hdmi output appears as
unplugged and unavailable.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lucas  1634 F pulseaudio
 /dev/snd/controlC0:  lucas  1634 F pulseaudio
 /dev/snd/pcmC0D0c:   lucas  1634 F...m pulseaudio
 /dev/snd/pcmC0D0p:   lucas  1634 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  6 17:29:42 2020
InstallationDate: Installed on 2020-09-29 (7 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lucas  1634 F pulseaudio
 /dev/snd/controlC0:  lucas  1634 F pulseaudio
 /dev/snd/pcmC0D0c:   lucas  1634 F...m pulseaudio
 /dev/snd/pcmC0D0p:   lucas  1634 F...m pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [HP Pavilion Notebook, Nvidia GPU 80 HDMI/DP, Digital Out, HDMI] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 84F7
dmi.board.vendor: HP
dmi.board.version: 07.10
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.26:bd12/13/2019:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn84F7:rvr07.10:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Notebook
dmi.product.sku: 4AR14EA#ABE
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug focal

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

Title:
  [HP Pavilion Notebook, Nvidia GPU 80 HDMI/DP, Digital Out, HDMI] No
  sound at all on hdmi audio output

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Recently I reinstalled ubuntu on my laptop and this time I found that
  when I connect the laptop to the tv with the hdmi I manage to get the
  video working but with no sound, it reproduces from the laptop
  speakers.

  On pulseaudio volume control the digital stereo hdmi output appears as
  unplugged and unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lucas  1634 F pulseaudio
   /dev/snd/controlC0:  lucas  1634 F pulseaudio
   /dev/snd/pcmC0D0c:   lucas  1634 F...m pulseaudio
   /dev/snd/pcmC0D0p:   lucas  1634 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  6 17:29:42 2020
  InstallationDate: Installed on 2020-09-29 (7 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lucas  1634 F pulseaudio
   /dev/snd/controlC0:  lucas  1634 F pulseaudio
   /dev/snd/pcmC0D0c:   lucas  1634 F...m pulseaudio
   /dev/snd/pcmC0D0p:   lucas  1634 F...m pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [HP Pavilion Notebook, Nvidia GPU 80 HDMI/DP, Digital Out, HDMI] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.26
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 84F7
  dmi.board.vendor: HP
  dmi.board.version: 07.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.26:bd12/13/2019:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn84F7:rvr07.10:cvnHP:ct10:cvrChassisVersion:

[Touch-packages] [Bug 1872176] Re: [MS-7B38, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] fails after a while

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [MS-7B38, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] fails after a
  while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  When I'm using certain applications, mostly games, the sound starts
  breaking randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rohan  2393 F pulseaudio
   /dev/snd/pcmC0D7p:   rohan  2393 F...m pulseaudio
   /dev/snd/controlC1:  rohan  2393 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 14:17:58 2020
  InstallationDate: Installed on 2018-04-19 (722 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulseAudioLog:
   Apr 11 14:04:57 rohan-work dbus-daemon[884]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.32' (uid=126 pid=1920 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
   Apr 11 14:04:58 rohan-work dbus-daemon[884]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.37' (uid=126 pid=1920 comm="/usr/bin/pulseaudio --daemonize=no " 
label="unconfined")
   Apr 11 14:05:05 rohan-work systemd[1913]: pulseaudio.service: Succeeded.
   Apr 11 14:05:15 rohan-work systemd[1913]: pulseaudio.socket: Succeeded.
  Symptom_Type: Sound works for a while, then breaks
  Title: [MS-7B38, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] fails after a while
  UpgradeStatus: Upgraded to focal on 2020-04-02 (8 days ago)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.GR
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A320M PRO-VD PLUS (MS-7B38)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.GR:bd12/02/2019:svnMicro-StarInternationalCo.,Ltd:pnMS-7B38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnA320MPRO-VDPLUS(MS-7B38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B38
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1872176/+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 1894907] Re: FTBFS with sphinx 3.2

This bug was fixed in the package cyrus-sasl2 - 2.1.27+dfsg-2ubuntu1

---
cyrus-sasl2 (2.1.27+dfsg-2ubuntu1) groovy; urgency=medium

  * Disable sphinx doc build, as the extension bundled in this source is
not compatible with current sphinx release (LP: #1894907):
- d/control: remove python3-sphinx build-depends
- d/rules: disable sphinx doc build, copy pre-built manpages to build dirs

 -- Andreas Hasenack   Tue, 29 Sep 2020 19:25:19
+

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  FTBFS with sphinx 3.2

Status in Cyrus-sasl2:
  New
Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 package in Debian:
  New

Bug description:
  cyrus-sasl2 ships with a sphinx extension to build its documentation,
  and this extension was based on a very old sphinx version. It no
  longer builds with sphinx 3.2.1 from groovy, failing in several
  places:

  a) "NoUri"
  Extension error:
  Could not import extension sphinxlocal.builders.manpage (exception: cannot 
import name 'NoUri' from 'sphinx.environment' 
(/usr/lib/python3/dist-packages/sphinx/environment/__init__.py))
  make[2]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2
  make[2]: Leaving directory 
'/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal'
  make[1]: *** [Makefile:686: all-recursive] Error 1
  make[1]: Leaving directory 
'/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal'
  make: *** [Makefile:556: all] Error 2

  Debian has a bug report already at https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=955095

  b) MACRO_DEF
  Extension error:
  Could not import extension sphinxlocal.builders.manpage (exception: cannot 
import name 'MACRO_DEF' from 'sphinx.writers.manpage' 
(/usr/lib/python3/dist-packages/sphinx/writers/manpage.py))
  make[4]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2
  make[4]: Leaving directory 
'/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal'
  make[3]: *** [Makefile:686: all-recursive] Error 1
  make[3]: Leaving directory 
'/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal'
  make[2]: *** [Makefile:556: all] Error 2
  make[2]: Leaving directory 
'/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal'
  dh_auto_build: error: cd build-heimdal && make -j4 
sasldir=/usr/lib/x86_64-linux-gnu/sasl2 returned exit code 2
  make[1]: *** [debian/rules:164: override_dh_auto_build] Error 25
  make[1]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2'
  make: *** [debian/rules:122: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/1894907/+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 1898729] Re: shim can end up being removed

In order to understand the priority: did this happen with or without
-proposed enabled on the system?  Do you have apt logs from the actual
removal?

And when you say "autoremoval", did this actually happen as part of an
apt autoremove operation?

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+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 1898690] Re: package less 487-0.1 failed to install/upgrade: new less package pre-installation script subprocess returned error exit status 2

2020-10-06 Thread Guillaume

It was due to an issue with mysql /etc/mysql/my.cnf.fallback file.
This bug can be closed.

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

Title:
  package less 487-0.1 failed to install/upgrade: new less package pre-
  installation script subprocess returned error exit status 2

Status in less package in Ubuntu:
  New

Bug description:
  Ocurred during bionic to focal upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: less 487-0.1
  ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
  Uname: Linux 4.15.0-118-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Oct  6 09:47:23 2020
  DuplicateSignature:
   package:less:487-0.1
   Preparing to unpack .../007-less_551-1ubuntu0.1_amd64.deb ...
   update-alternatives: error: cannot stat file '/etc/mysql/my.cnf.fallback': 
Too many levels of symbolic links
   dpkg: error processing archive 
/tmp/apt-dpkg-install-W2kFIm/007-less_551-1ubuntu0.1_amd64.deb (--unpack):
new less package pre-installation script subprocess returned error exit 
status 2
  Ec2AMI: ami-0002
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: vps-cloud-2
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: new less package pre-installation script subprocess returned 
error exit status 2
  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: less
  Title: package less 487-0.1 failed to install/upgrade: new less package 
pre-installation script subprocess returned error exit status 2
  UpgradeStatus: Upgraded to focal on 2020-10-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/less/+bug/1898690/+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 1898729] Re: shim can end up being removed

2020-10-06 Thread Iain Lane

I've marked apt as affected because it ships
/etc/apt/apt.conf.d/01autoremove but I suppose each of the affected
packages could also supply their own snippets.

** Tags added: rls-ff-incoming

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+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 1892643] Re: [SRU] Update libgweather to 3.36.1

2020-10-06 Thread Sebastien Bacher

** Changed in: libgweather (Ubuntu Focal)
 Assignee: (unassigned) => Didier Roche (didrocks)

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

Title:
  [SRU] Update libgweather to 3.36.1

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Focal:
  New
Status in libgweather package in Debian:
  Unknown

Bug description:
  [Impact]

  libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36.

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions.

  Sometimes the current weather is not available because the NOAA
  weather servers aren't working correctly. Version 3.36.1 fixes the
  unavailability of current temperature in some locations.

  
  [Test case]

  Make sure that gnome-weather is still working properly and the weather
  in gnome-shell is shown when gnome-weather is installed.

  
  [Regression potential]

  The regression potential is low since the changes in version 3.36.1
  are small.

  
  [Other]

  libgweather 3.36.1 has been successfully built as a no-change backport
  from Groovy to Focal in my PPA and runs fine:

  
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather_filter=published_filter=

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 19:05:21 2020
  InstallationDate: Installed on 2020-04-26 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1892643/+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 1898729] [NEW] shim can end up being removed

2020-10-06 Thread Iain Lane

Public bug reported:

I just did a set of package updates in focal that ended up with shim
shim-signed mokutil being autoremoved.

I rebooted without noticing, and had to manually recover the system
thereafter. :(

Julian says there was a period of time where these were marked auto. I
suppose that I installed during this window, and now some dependency
change meant that as far as apt was concerned they weren't required any
more.

Can we please consider never proposing these packages for autoremoval?
apt has NeverAutoRemove for this which could be used, or some other
appropriate method.

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

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


** Tags: rls-ff-incoming

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

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+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 1723822] Re: uncaught TypeError triggers ValueError

This bug was fixed in the package nautilus - 1:3.38.1-1ubuntu1

---
nautilus (1:3.38.1-1ubuntu1) groovy; urgency=medium

  * New upstream version
- don't block to restore from trash (lp: #1839380)
  * debian/source_nautilus.py:
- updated the apport script to use the multiarch directory, install
  it in the nautilus binary that is arch any (lp: #1723822)
  * Resynchronizr on Debian:
- debian/control.in:
  + Build-Depend on libunity-dev
  + lower gnome-sushi Recommends to a Suggests
- debian/changelog, debian/nautilus.maintscript: set epoch number
  (which was added by error)
- debian/source_nautilus.py,
  debian/nautilus-data.install:
  + Apport hook to list versions of files in /usr/lib/nautilus and
reassign the crashes when they are not due to nautilus code directly
- debian/rules:
  + Build Unity support
- 0001-Respect-gtk-dialogs-use-header-for-all-dialogs.patch
  + Use a normal titlebar if the desktop environment wants it
- 04_suppress_umount_in_ltsp.patch:
  + Don't list unmount and eject actions on LTSP clients
- 12_unity_launcher_support.patch:
  + unity launcher integration (list bookmarks in the context menu,
display a bar on the icon during copies)
- 18_unity_icon_color.patch:
  + specify a background color for the unity launcher icon
- 19_unity_open_location_xid.patch:
  + Add a new dbus property to store the lists of opened locations
referenced by their parent nautilus window XID.
- 20_add_timestamp_to_operations.patch:
  + Add *WithTimestamp dbus methods for file operations that
might trigger a dialog, that should be presented with time.
- appstream-compulsory.patch:
  + Set nautilus as unremovable in GNOME Software
- nautilusgtkplacesview-show-error-if-volume-is-not-mo.patch:
  + show error if volume is not mounted, see LP #1764779
- ubuntu/shell-search-provider-implement-XUbuntuCancel-to-request-.patch:
  + implement XUbuntuCancel to request search cancellation
- ubuntu_backspace_behaviour.patch:
  + restore backspace behaviour to go back
- ubuntu_infobars_color.patch:
  + set infobar type to "other" rather than "question" to avoid blue
cluebars

 -- Sebastien Bacher   Mon, 05 Oct 2020 11:37:10
+0200

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

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

Title:
  uncaught TypeError triggers ValueError

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  $ ubuntu-bug nautilus
  ERROR: hook /usr/share/apport/package-hooks/source_nautilus.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
  TypeError: add_info() takes 1 positional argument but 2 were given

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 203, in 
_run_hook
  symb['add_info'](report)
File "/usr/share/apport/package-hooks/source_nautilus.py", line 23, in 
add_info
  report["usr_lib_nautilus"] = package_versions(*sorted(plugin_packages))
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 785, in 
package_versions
  map(max, [map(len, t) for t in zip(*versions)])
  ValueError: not enough values to unpack (expected 2, got 0)
  This tool has been deprecated, use 'gio open' instead.
  See 'gio help open' for more info.

  $ Created new window in existing browser session.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashReports:
   640:121:119:20593327:2017-10-14 08:49:43.994080376 -0700:2017-10-14 
08:49:24.682136558 -0700:/var/crash/_usr_bin_gnome-shell.121.crash
   640:0:119:712257:2017-10-13 22:55:49.843941428 -0700:2017-10-13 
22:55:48.723911385 -0700:/var/crash/_usr_lib_udisks2_udisksd.0.crash
   640:1000:119:432238:2017-10-14 07:48:01.498643348 -0700:2017-10-14 
07:48:00.714643372 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.crash
   664:1000:119:0:2017-10-13 19:55:40.447393054 -0700:2017-10-13 
19:55:40.447393054 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.upload
   600:112:119:0:2017-10-13 19:55:42.247460153 -0700:2017-10-13 
19:55:42.247460153 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.uploaded
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 17:52:08 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark"

[Touch-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No sound at all

2020-10-06 Thread Bug Watch Updater

** Changed in: alsa-driver
   Status: Unknown => Fix Released

** Changed in: alsa-driver
   Importance: Unknown => Medium

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No sound at all

Status in ALSA driver:
  Fix Released
Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/alsa-driver/+bug/1166529/+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 1685754] Re: 'systemd --user' unduly forces umask=0022

2020-10-06 Thread Etienne URBAH

REGRESSION:  With systemd 246.6-1ubuntu1 from Ubuntu 20.10 Beta (Groovy
Gorilla), the issue had reappeared

** Tags added: groovy

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

Title:
  'systemd --user' unduly forces umask=0022

Status in gedit:
  Invalid
Status in gnome-session:
  Invalid
Status in GNOME Terminal:
  Confirmed
Status in Nautilus:
  Invalid
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Bionic:
  Invalid
Status in gnome-terminal source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  In order to set the default umask of my users to 027 or 007, I
  followed the instructions provided in 'man pam_umask' :

  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).

  Then, MOST graphical applications systematically run with the correct
  umask.

  In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
  it systematically displays 0007.

  But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
  it systematically displays 0022.

  That is BAD, and is a security issue.

  
  Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
  UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
  if  [ "$UMASK" ];  then
umask  "${UMASK#$USER:*,umask=}"
  fi

  
  In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.

  Thank you in advance for a quick correction.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 24 08:36:58 2017
  InstallationDate: Installed on 2017-03-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

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

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

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

** Changed in: glibc (Ubuntu)
   Status: Fix Released => Invalid

** Changed in: glibc (Ubuntu Focal)
   Status: Fix Released => Invalid

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1871268/+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 1896577] Re: FFE: new upstream release 20.2 and migrate to llvm 11

2020-10-06 Thread Timo Aaltonen

This bug was fixed in the package mesa - 20.2.0-1

---
mesa (20.2.0-1) experimental; urgency=medium

  * New upstream release.
  * control: Add libclang-cpp11-dev to build-depends. (Closes: #954849)

 -- Timo Aaltonen   Tue, 29 Sep 2020 11:07:13 +0300

mesa (20.2.0~rc4-2) experimental; urgency=medium

  * Migrate to llvm/clang-11.
  * path_max.diff: Updated. (Closes: #969040)

 -- Timo Aaltonen   Thu, 17 Sep 2020 12:07:08 +0300

mesa (20.2.0~rc4-1) experimental; urgency=medium

  * New upstream prerelease.
  * rules: Move radv rule up to fix build on non-intel archs.

 -- Timo Aaltonen   Fri, 04 Sep 2020 19:32:58 +0300

mesa (20.2.0~rc2-1) experimental; urgency=medium

  * New upstream release candidate.
  * rules: Get rid of trailing commas in *_DRIVERS options.
  * control: Bump libglvnd build-dep.
  * Update mesa-common-dev.docs.

 -- Timo Aaltonen   Fri, 14 Aug 2020 18:30:42 +0300

** Changed in: mesa (Ubuntu)
   Status: New => 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/1896577

Title:
  FFE: new upstream release 20.2 and migrate to llvm 11

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Mesa 20.2.0 was released on Sep 28th a month late, but we still want
  it in 20.10. It's been in debian experimental since rc1. The packaging
  in debian also migrates to use llvm 11.

  The risks involve graphical issues or even crashes when running more
  intense OpenGL/Vulkan apps like games. Running a desktop is a simple
  use-case and should work fine across the board. Upstream gitlab has a
  fairly extensive CI for various drivers, while Intel tests on their
  own CI. This means that any showstoppers should be shaken out already.

  We will be able to pull maybe two point-releases before groovy is
  frozen, and then push more as an SRU.

  I've tested 20.2.0 on Intel and AMD (RX 5700) and the latter too with
  some games, all good.

  packages for groovy are available on ppa:canonical-x/x-staging

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1896577/+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 1898713] Re: Xorg crashes sometimes with Easystrokes

** Attachment added: "text/plain; charset="utf-8""
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418339/+files/LightdmLog.txt

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

Title:
  Xorg crashes sometimes with Easystrokes

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg crashes, session closes, all unsaved data is gone.

  What I did / Reproducing
  ===

  It happens when I use Easystrokes to emulate `Ctrl+F4` or
  `Ctrl+PageUp/Down`.

  So far it happened about 5 recognized times, 3 recorded within the
  last 3(?) month. twice during tab switching in incognito Firefox and
  once in VSCode.

  Reproducability
  
  I feel it's very consistent in crashing in Firefox incognito. But it's not 
purposely reproducible 100%.

  I would give more information, but the stacktrace of the crashdump
  does not tell much. I installed debug symbols for xorg, but they made
  no change viewing it.

  Here is the (obscured) stack trace:

  ```
  Reading symbols from /usr/lib/xorg/Xorg...
  Reading symbols from 
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
  [New LWP 100716]
  [New LWP 100705]
  [New LWP 100704]
  [New LWP 100707]
  [New LWP 100709]
  [New LWP 100708]
  [New LWP 100706]
  [New LWP 100711]
  [New LWP 100710]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  --Type  for more, q to quit, c to continue without paging--
  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x55a0da61fe9c in miPointerSetPosition (
  pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
  screenx=screenx@entry=0x7f707b57d570, 
  screeny=screeny@entry=0x7f707b57d578, 
  nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
  at ../../../../mi/mipointer.c:610
  610   ../../../../mi/mipointer.c: No such file or directory.
  [Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
  (gdb) 
  (gdb) 
  (gdb) bt full
  #0  0x55a0da61fe9c in miPointerSetPosition
  (pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at 
../../../../mi/mipointer.c:610
  pScreenPriv = 
  pScreen = 
  newScreen = 0x254
  x = 802
  y = 596
  switch_screen = 0
  should_constrain_barriers = 0
  i = 
  pPointer = 0x0
  #1  0x55a0da4ec840 in positionSprite
  (dev=dev@entry=0x55a0dc969400, mode=mode@entry=0, 
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580, 
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570, 
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at 
../../../../dix/getevents.c:961
  scr = 
  tmpx = 801.02961125081322
  tmpy = 595.47038874918678
  #2  0x55a0da4ecf4d in positionSprite
  (events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578, 
scre--Type  for more, q to quit, c to continue without paging--
  enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580, 
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at 
../../../../dix/getevents.c:952
  scr = 0x0
  num_events = 2
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #3  fill_pointer_events (events=0x7f708d903c20, 
  events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, 
type=, buttons=buttons@entry=0, ms=ms@entry=289728198, 
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at 
../../../../dix/getevents.c:1434
  num_events = 2
  --Type  for more, q to quit, c to continue without paging--
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #4  0x55a0da4ee620 in GetPointerEvents

[Touch-packages] [Bug 1898713] Re: Xorg crashes sometimes with Easystrokes

** Attachment added: "text/plain; charset="utf-8""
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418340/+files/XorgLog.txt

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

Title:
  Xorg crashes sometimes with Easystrokes

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg crashes, session closes, all unsaved data is gone.

  What I did / Reproducing
  ===

  It happens when I use Easystrokes to emulate `Ctrl+F4` or
  `Ctrl+PageUp/Down`.

  So far it happened about 5 recognized times, 3 recorded within the
  last 3(?) month. twice during tab switching in incognito Firefox and
  once in VSCode.

  Reproducability
  
  I feel it's very consistent in crashing in Firefox incognito. But it's not 
purposely reproducible 100%.

  I would give more information, but the stacktrace of the crashdump
  does not tell much. I installed debug symbols for xorg, but they made
  no change viewing it.

  Here is the (obscured) stack trace:

  ```
  Reading symbols from /usr/lib/xorg/Xorg...
  Reading symbols from 
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
  [New LWP 100716]
  [New LWP 100705]
  [New LWP 100704]
  [New LWP 100707]
  [New LWP 100709]
  [New LWP 100708]
  [New LWP 100706]
  [New LWP 100711]
  [New LWP 100710]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  --Type  for more, q to quit, c to continue without paging--
  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x55a0da61fe9c in miPointerSetPosition (
  pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
  screenx=screenx@entry=0x7f707b57d570, 
  screeny=screeny@entry=0x7f707b57d578, 
  nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
  at ../../../../mi/mipointer.c:610
  610   ../../../../mi/mipointer.c: No such file or directory.
  [Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
  (gdb) 
  (gdb) 
  (gdb) bt full
  #0  0x55a0da61fe9c in miPointerSetPosition
  (pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at 
../../../../mi/mipointer.c:610
  pScreenPriv = 
  pScreen = 
  newScreen = 0x254
  x = 802
  y = 596
  switch_screen = 0
  should_constrain_barriers = 0
  i = 
  pPointer = 0x0
  #1  0x55a0da4ec840 in positionSprite
  (dev=dev@entry=0x55a0dc969400, mode=mode@entry=0, 
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580, 
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570, 
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at 
../../../../dix/getevents.c:961
  scr = 
  tmpx = 801.02961125081322
  tmpy = 595.47038874918678
  #2  0x55a0da4ecf4d in positionSprite
  (events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578, 
scre--Type  for more, q to quit, c to continue without paging--
  enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580, 
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at 
../../../../dix/getevents.c:952
  scr = 0x0
  num_events = 2
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #3  fill_pointer_events (events=0x7f708d903c20, 
  events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, 
type=, buttons=buttons@entry=0, ms=ms@entry=289728198, 
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at 
../../../../dix/getevents.c:1434
  num_events = 2
  --Type  for more, q to quit, c to continue without paging--
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #4  0x55a0da4ee620 in GetPointerEvents

[Touch-packages] [Bug 1898713] [NEW] Xorg crashes sometimes with Easystrokes

Public bug reported:

Xorg crashes, session closes, all unsaved data is gone.

What I did / Reproducing
===

It happens when I use Easystrokes to emulate `Ctrl+F4` or
`Ctrl+PageUp/Down`.

So far it happened about 5 recognized times, 3 recorded within the last
3(?) month. twice during tab switching in incognito Firefox and once in
VSCode.

Reproducability

I feel it's very consistent in crashing in Firefox incognito. But it's not 
purposely reproducible 100%.

I would give more information, but the stacktrace of the crashdump does
not tell much. I installed debug symbols for xorg, but they made no
change viewing it.

Here is the (obscured) stack trace:

```
Reading symbols from /usr/lib/xorg/Xorg...
Reading symbols from 
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
[New LWP 100716]
[New LWP 100705]
[New LWP 100704]
[New LWP 100707]
[New LWP 100709]
[New LWP 100708]
[New LWP 100706]
[New LWP 100711]
[New LWP 100710]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
--Type  for more, q to quit, c to continue without paging--
Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x55a0da61fe9c in miPointerSetPosition (
pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, 
screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
at ../../../../mi/mipointer.c:610
610 ../../../../mi/mipointer.c: No such file or directory.
[Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
(gdb) 
(gdb) 
(gdb) bt full
#0  0x55a0da61fe9c in miPointerSetPosition
(pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at 
../../../../mi/mipointer.c:610
pScreenPriv = 
pScreen = 
newScreen = 0x254
x = 802
y = 596
switch_screen = 0
should_constrain_barriers = 0
i = 
pPointer = 0x0
#1  0x55a0da4ec840 in positionSprite
(dev=dev@entry=0x55a0dc969400, mode=mode@entry=0, 
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580, 
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570, 
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at 
../../../../dix/getevents.c:961
scr = 
tmpx = 801.02961125081322
tmpy = 595.47038874918678
#2  0x55a0da4ecf4d in positionSprite
(events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578, 
scre--Type  for more, q to quit, c to continue without paging--
enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580, 
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at 
../../../../dix/getevents.c:952
scr = 0x0
num_events = 2
event = 
raw = 0x7f708d903010
screenx = 801.02961125081322
screeny = 595.47038874918678
devx = 801.02961125081322
devy = 595.47038874918678
sx = 0
sy = 0
mask = 
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
scr = 
num_barrier_events = 0
#3  fill_pointer_events (events=0x7f708d903c20, 
events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, 
type=, buttons=buttons@entry=0, ms=ms@entry=289728198, 
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at 
../../../../dix/getevents.c:1434
num_events = 2
--Type  for more, q to quit, c to continue without paging--
event = 
raw = 0x7f708d903010
screenx = 801.02961125081322
screeny = 595.47038874918678
devx = 801.02961125081322
devy = 595.47038874918678
sx = 0
sy = 0
mask = 
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
scr = 
num_barrier_events = 0
#4  0x55a0da4ee620 in GetPointerEvents
(events=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, type=, type@entry=6, buttons=buttons@entry=0, flags=10, mask_in=)
at ../../../../dix/getevents.c:1691
ms = 289728198
num_events = 0
nev_tmp = 
mask = 
{last_bit = 1 '\001', has_unaccelerated = 1 '\001', mask = 
"\003\000--Type  for more, q to quit, c to continue without paging--
\000\000", valuators = {-1, -1.5, 0 }, unaccelerated = {-2, 
-3, 0 }}
scroll = 
{last_bit = -128 '\200', has_unaccelerated = 4 '\004', mask = 
"eݠU", valuators = {6.9229118033614265e-310, 6.9229013081954128e-310,

[Touch-packages] [Bug 1898713] Re: Xorg crashes sometimes with Easystrokes

** Attachment added: "text utf8"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418338/+files/LightdmDisplayLog.txt

** Attachment removed: "LightdmLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418321/+files/LightdmLog.txt

** Attachment removed: "XorgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418333/+files/XorgLog.txt

** Attachment removed: "XorgLogOld.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418334/+files/XorgLogOld.txt

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

Title:
  Xorg crashes sometimes with Easystrokes

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg crashes, session closes, all unsaved data is gone.

  What I did / Reproducing
  ===

  It happens when I use Easystrokes to emulate `Ctrl+F4` or
  `Ctrl+PageUp/Down`.

  So far it happened about 5 recognized times, 3 recorded within the
  last 3(?) month. twice during tab switching in incognito Firefox and
  once in VSCode.

  Reproducability
  
  I feel it's very consistent in crashing in Firefox incognito. But it's not 
purposely reproducible 100%.

  I would give more information, but the stacktrace of the crashdump
  does not tell much. I installed debug symbols for xorg, but they made
  no change viewing it.

  Here is the (obscured) stack trace:

  ```
  Reading symbols from /usr/lib/xorg/Xorg...
  Reading symbols from 
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
  [New LWP 100716]
  [New LWP 100705]
  [New LWP 100704]
  [New LWP 100707]
  [New LWP 100709]
  [New LWP 100708]
  [New LWP 100706]
  [New LWP 100711]
  [New LWP 100710]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  --Type  for more, q to quit, c to continue without paging--
  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x55a0da61fe9c in miPointerSetPosition (
  pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
  screenx=screenx@entry=0x7f707b57d570, 
  screeny=screeny@entry=0x7f707b57d578, 
  nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
  at ../../../../mi/mipointer.c:610
  610   ../../../../mi/mipointer.c: No such file or directory.
  [Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
  (gdb) 
  (gdb) 
  (gdb) bt full
  #0  0x55a0da61fe9c in miPointerSetPosition
  (pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at 
../../../../mi/mipointer.c:610
  pScreenPriv = 
  pScreen = 
  newScreen = 0x254
  x = 802
  y = 596
  switch_screen = 0
  should_constrain_barriers = 0
  i = 
  pPointer = 0x0
  #1  0x55a0da4ec840 in positionSprite
  (dev=dev@entry=0x55a0dc969400, mode=mode@entry=0, 
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580, 
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570, 
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at 
../../../../dix/getevents.c:961
  scr = 
  tmpx = 801.02961125081322
  tmpy = 595.47038874918678
  #2  0x55a0da4ecf4d in positionSprite
  (events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578, 
scre--Type  for more, q to quit, c to continue without paging--
  enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580, 
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at 
../../../../dix/getevents.c:952
  scr = 0x0
  num_events = 2
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #3  fill_pointer_events (events=0x7f708d903c20, 
  events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, 
type=, buttons=buttons@entry=0, ms=ms@entry=289728198, 
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at 
../../../../dix/getevents.c:1434
  num_events = 2
  --Type  for more, q to quit, c to continue without paging--
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny =

[Touch-packages] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

2020-10-06 Thread Guilherme G. Piccoli

Thanks a lot Alex for your review from a security point-of-view. And thanks 
again Lukasz for dealing with this SRU!
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/1879980

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  In Progress
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  In Progress
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends its execution, we execute
  at least once more time cryptsetup. In an ideal world we should loop
  on local-block as Debian's initramfs (in a way to remove hardcoded
  mdadm/cryptsetup mentions from initramfs-tools code), but this would
  be really a big change, non-SRUable probably. I plan to work that for
  future Ubuntu releases.

  [Test case]
  * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to 
create a RAID1 volume and an encrypted root on top of it.

  * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table
  from one of the RAID members. Reboot and it will fail to mount rootfs
  and continue boot process.

  * If using the initramfs-toos/cryptsetup patches hereby proposed, the
  rootfs can be mounted normally.

  [Regression potential]

  * There are potential for regressions, since this is a change in 2
  boot components. The patches were designed in a way to keep the
  regular case working, it changes the failure case which is not
  currently working anyway.

  * A modification in the behavior of cryptsetup was introduced: right
  now, if we fail the password 3 times (the default maximum attempts),
  the script doesn't "panic" and drop to a shell immediately; instead it
  runs once more (or twice, if mdadm is installed) before failing. This
  is a minor change given the benefit of the being able to mount rootfs
  in a degraded RAID1 scenario.

  * Other potential regressions could show-up as boot problems, but the
  change in initramfs-tools specifically is not invasive, it just may
  delay boot time a bit, given we now run cryptsetup multiple times on
  local-block, with 1 sec delays between executions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+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 1751673] Re: nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

2020-10-06 Thread Cyrille37

*** This bug is a duplicate of bug 1755305 ***
https://bugs.launchpad.net/bugs/1755305

Hi,

This bug continue, on Ubuntu 18.04.5 LTS + MATE 1.20.1.

In .xsession-errors :

(nm-applet:2221): Gtk-CRITICAL **: 12:09:29.609: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
(nm-applet:2221): Gtk-CRITICAL **: 12:09:29.609: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
(nm-applet:2221): Gtk-WARNING **: 12:09:29.611: Can't set a parent on widget 
which has a parent
(nm-applet:2221): Gtk-CRITICAL **: 12:09:29.614: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
(nm-applet:2221): Gtk-CRITICAL **: 12:09:29.614: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
(nm-applet:2221): Gtk-WARNING **: 12:09:29.615: Can't set a parent on widget 
which has a parent

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

Title:
  nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET
  (widget)' failed

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  running 18.04 this message is spamming into syslog:
  > nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' 
failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.8.4-1ubuntu4
  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: Unity:Unity7:ubuntu
  Date: Mon Feb 26 01:16:49 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-09-28 (1611 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1 proto static metric 600 
   169.254.0.0/16 dev wlan1 scope link metric 1000 
   192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.34 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-01-12 (44 days ago)
  
modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla:
 [deleted]
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlan1  wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  k2l 
7df024b1-9b89-4f95-84c1-03188bb67f77  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   EC:88:92:02:17:7D  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  --  --   
 -- 
   eth1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

2020-10-06 Thread Chit San Maung

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

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

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

** Changed in: glibc (Ubuntu Focal)
   Status: Invalid => Fix Released

** Changed in: glibc (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in glibc source package in Focal:
  Fix Released

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1871268/+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 214786] Re: Apple USB ISO keyboard has incorrectly swapped keys

2020-10-06 Thread Pedro A. Aranda

After posting, I tried 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/214786/comments/78
and it worked for me on a Spanish USB apple keyboard.

Currently I have my laptop's and the USB Apple keyboard working
correctly _and_ simultaneously

Just my .2 cents

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

Title:
  Apple USB ISO keyboard has incorrectly swapped keys

Status in Mactel Support:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel to version 2.6.24-12.22 two keys are now
  swapped on my Apple USB aluminium keyboard with danish layout. Now the
  keys "<" and "½" are swapped and no longer matches the actual print on
  the keycaps.

  The error is isolated to the following commit:
  http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
  hardy.git;a=commitdiff;h=efb3031b446d441dca5b10619503ac0bba7f9748

  This commit introduced a key swapping for all "ISO" type Apple
  keyboards. In my case this swapping is incorrect, and generally it
  seems like a very bad idea to perform hard coded locale specific key
  mapping in kernel space as this is also done several places in user
  space.

  The included patch reverts the behavior to the default that matches
  the keycap printing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mactel-support/+bug/214786/+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 1893863] Re: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  dpkg: error processing package lvm2 (--configure):
   installed lvm2 package post-installation script subprocess returned error 
exit 
  status 1
  Processing triggers for initramfs-tools (0.136ubuntu6.2) ...
  update-initramfs: Generating /boot/initrd.img-5.4.0-45-generic
  Errors were encountered while processing:
   lvm2
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-1094.104-oem 4.15.18
  Uname: Linux 4.15.0-1094-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep  2 07:59:59 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-05-01 (123 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  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: lvm2
  Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-09-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1893863/+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 1898696] [NEW] add some deliminiter between ipv4 and ipv6 in ufw status

2020-10-06 Thread simohe

Public bug reported:

"ufw status numbered" shows all the rules in one block, numbered from top to 
bottom. First are the ipv4 rules, then the ipv6.
This has led to some irritation.

A user asked how to add a IPv4 rule to the end of the list.
https://answers.launchpad.net/ubuntu/+source/ufw/+question/692096
Inserting ipv6 rules to the correct position is not easy to understand
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1368411

My suggestion is to at least add some separator between the ipv4 and ipv6 rules 
in the output of "ufw status". A blank line, or a comment line (# IPv6 rules:) 
would be fine.
This would indicate that not both rule lists, but only one of them, is applied 
to a connection.

## output suggestion:

Status: active

 To Action  From
 -- --  
[ 1] 22/tcp ALLOW INAnywhere  
[ 2] 8080:8090/tcp  ALLOW INAnywhere   # mywww
[ 3] WWW Full   ALLOW INAnywhere  
 # IPv6 rules:
[ 4] 22/tcp (v6)ALLOW INAnywhere (v6) 
[ 5] 8080:8090/tcp (v6) ALLOW INAnywhere (v6)  # mywww
[ 6] WWW Full (v6)  ALLOW INAnywhere (v6)


## system info
ufw --version: ufw 0.35

 side note
But maybe this is irrelevant as long as the future plans of ufw are unclear. 
(https://answers.launchpad.net/ubuntu/+source/ufw/+question/692803)

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

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

Title:
  add some deliminiter between ipv4 and ipv6 in ufw status

Status in ufw package in Ubuntu:
  New

Bug description:
  "ufw status numbered" shows all the rules in one block, numbered from top to 
bottom. First are the ipv4 rules, then the ipv6.
  This has led to some irritation.

  A user asked how to add a IPv4 rule to the end of the list.
  https://answers.launchpad.net/ubuntu/+source/ufw/+question/692096
  Inserting ipv6 rules to the correct position is not easy to understand
  https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1368411

  My suggestion is to at least add some separator between the ipv4 and ipv6 
rules in the output of "ufw status". A blank line, or a comment line (# IPv6 
rules:) would be fine.
  This would indicate that not both rule lists, but only one of them, is 
applied to a connection.

  ## output suggestion:

  Status: active

   To Action  From
   -- --  
  [ 1] 22/tcp ALLOW INAnywhere  
  [ 2] 8080:8090/tcp  ALLOW INAnywhere   # mywww
  [ 3] WWW Full   ALLOW INAnywhere  
   # IPv6 rules:
  [ 4] 22/tcp (v6)ALLOW INAnywhere (v6) 
  [ 5] 8080:8090/tcp (v6) ALLOW INAnywhere (v6)  # mywww
  [ 6] WWW Full (v6)  ALLOW INAnywhere (v6)

  
  ## system info
  ufw --version: ufw 0.35

   side note
  But maybe this is irrelevant as long as the future plans of ufw are unclear. 
(https://answers.launchpad.net/ubuntu/+source/ufw/+question/692803)

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

2020-10-06 Thread Andy Wharton

Installing from the latest daily installer fails when installing grub-
efi-amd64 as it has unmeet dependencies:

grub-common and grub2-common give a warning about 2.04-1ubuntu26.4 being
required, but 2.04-1ubuntu26.5 is to be installed.

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1871268/+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 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

This bug was fixed in the package initramfs-tools - 0.130ubuntu3.11

---
initramfs-tools (0.130ubuntu3.11) bionic; urgency=medium

  [ Guilherme G. Piccoli ]
  * scripts/functions: Prevent printf error carry over if the wrong
console is set. (LP: #1879987)
  The function _log_msg() is "void" typed, returning whatever its
  last command returns. This function is the basic building block
  for all error/warning messages in initramfs-tools. If a bad console
  is provided to kernel on command-line, printf returns error, and so
  this error is carried over in _log_msg(). Happens that checkfs()
  function has a loop that runs forever in this scenario (*if* fsck
  is not present in initramfs and "quiet" is not passed in the
  command-line). If that happens, boot is stuck and cannot progress.
  The simple fix hereby merged is to return zero on _log_msg().

  * scripts/local: Re-execute cryptroot local-block script. (LP: #1879980)
  Currently, if an encrypted rootfs is configured on top of a MD RAID1
  array and such array gets degraded (like a member is removed/failed),
  initramfs-tools cannot mount the rootfs and the boot fails. We fix
  that issue here by allowing cryptroot script to re-run on local-block
  stage, given that mdadm is able to activate a degraded array in that
  point. There is a cryptsetup counter-part for this fix, but alone the
  initramfs-tools portion is innocuous.

  [ Jay Vosburgh ]
  * scripts/functions: Change netplan render for net_failover master
devices. (LP: #1820929)
  Modify the _render_netplan function to check for network interfaces
  that are net_failover master devices. When found, such devices are
  matched only by name, not by MAC address, as the MAC is not a unique
  identifier for the net_failover case. In the net_failover architecture,
  the MAC address is used to manage the membership of the net_failover
  interface set, thus multiple interfaces will be assigned the same MAC
  address.

 -- gpicc...@canonical.com (Guilherme G. Piccoli)  Wed, 12 Aug 2020
17:12:11 -0300

** Changed in: initramfs-tools (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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1879980

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  In Progress
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  In Progress
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends

[Touch-packages] [Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces

This bug was fixed in the package initramfs-tools - 0.130ubuntu3.11

---
initramfs-tools (0.130ubuntu3.11) bionic; urgency=medium

  [ Guilherme G. Piccoli ]
  * scripts/functions: Prevent printf error carry over if the wrong
console is set. (LP: #1879987)
  The function _log_msg() is "void" typed, returning whatever its
  last command returns. This function is the basic building block
  for all error/warning messages in initramfs-tools. If a bad console
  is provided to kernel on command-line, printf returns error, and so
  this error is carried over in _log_msg(). Happens that checkfs()
  function has a loop that runs forever in this scenario (*if* fsck
  is not present in initramfs and "quiet" is not passed in the
  command-line). If that happens, boot is stuck and cannot progress.
  The simple fix hereby merged is to return zero on _log_msg().

  * scripts/local: Re-execute cryptroot local-block script. (LP: #1879980)
  Currently, if an encrypted rootfs is configured on top of a MD RAID1
  array and such array gets degraded (like a member is removed/failed),
  initramfs-tools cannot mount the rootfs and the boot fails. We fix
  that issue here by allowing cryptroot script to re-run on local-block
  stage, given that mdadm is able to activate a degraded array in that
  point. There is a cryptsetup counter-part for this fix, but alone the
  initramfs-tools portion is innocuous.

  [ Jay Vosburgh ]
  * scripts/functions: Change netplan render for net_failover master
devices. (LP: #1820929)
  Modify the _render_netplan function to check for network interfaces
  that are net_failover master devices. When found, such devices are
  matched only by name, not by MAC address, as the MAC is not a unique
  identifier for the net_failover case. In the net_failover architecture,
  the MAC address is used to manage the membership of the net_failover
  interface set, thus multiple interfaces will be assigned the same MAC
  address.

 -- gpicc...@canonical.com (Guilherme G. Piccoli)  Wed, 12 Aug 2020
17:12:11 -0300

** Changed in: initramfs-tools (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/1820929

Title:
  netplan should consider adding more udev attribute for exact matching
  of failover 3-netdev interfaces

Status in netplan:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in netplan.io source package in Bionic:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  [Impact]

  * At present, virtual machines utilizing net_failover network
  interface configurations are incorrectly configured due to the
  reliance on the MAC address to identify specific network interfaces.
  When net_failover is utilized, multiple interfaces will bear the same
  MAC address (the net_failover master itself, as well as the interfaces
  subordinate to it), rendering the MAC address ineffective for unique
  identification of the interface.  This results in incorrect naming of
  network interfaces from the "set-name" directive in the netplan
  configuration.

  * The solution here is to use the interface name instead of the MAC
  address when the interface is a net_failover master device.  Logic is
  added on initramfs-tools to check the device type and virtio flags to
  apply this change only to net_failover master devices.

  [Test Case]

  * The change can be tested by configuring a virtual machine with a
  virtio_net network device with the "failover=on" option to the
  "-device" option to qemu, e.g.,

  -device virtio-net-
  
pci,netdev=hostnet0,id=net0,bus=pci.0,addr=0x3,mac=00:00:17:00:18:04,failover=on

  * This will set the virtio device "standby" feature bit (bit 62,
  counting from 0).  This requires a version of qemu with support for
  this feature.

  * When so configured, the netplan configuration generated by initramfs
  will not contain a "macaddress:" match directive for the network
  interface in question.

  [Regression Potential]

  * Erroneous identification of a network interface as a net_failover
  master device could lead to omission of a macaddress directive,
  causing interfaces to be incorrectly named.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1820929/+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.

This bug was fixed in the package initramfs-tools - 0.122ubuntu8.17

---
initramfs-tools (0.122ubuntu8.17) xenial; urgency=medium

  * scripts/functions: Prevent printf error carry over if the wrong
console is set. (LP: #1879987)
  The function _log_msg() is "void" typed, returning whatever its
  last command returns. This function is the basic building block
  for all error/warning messages in initramfs-tools. If a bad console
  is provided to kernel on command-line, printf returns error, and so
  this error is carried over in _log_msg(). Happens that checkfs()
  function has a loop that runs forever in this scenario (*if* fsck
  is not present in initramfs and "quiet" is not passed in the
  command-line). If that happens, boot is stuck and cannot progress.
  The simple fix hereby merged is to return zero on _log_msg().

 -- gpicc...@canonical.com (Guilherme G. Piccoli)  Thu, 23 Jul 2020
13:20:14 -0300

-- 
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:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in initramfs-tools source package in Eoan:
  Won't Fix
Status in initramfs-tools source package in Focal:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  * Currently, if users provide the wrong console in kernel command-line
  (like console=ttyS1, when the right one is ttyS0) *and* "quiet"
  parameter is not provided, we may face an infinite loop on initramfs-
  tools, effectively blocking the boot.

  * Details are: the _log_msg() functions is "void" typed, which means it 
returns whatever its last command returns; this function is the basic building 
block for all error/warning messages in initramfs-tools. In case a bad console 
was provided to kernel on command-line, printf (and apparently all 
write()-related functions) returns error, and so this error is carried over in 
_log_msg().
   
  * Happens that checkfs() function has a loop that runs forever in this 
scenario (*if* fsck is not present in initramfs, and obviously if "quiet" is 
not provided in the command-line). The situation is easily reproducible.

  * This SRU proposes a pretty simple fix: return zero on _log_msg(). We
  should definitely not brake the boot due to error log functions.

  
  [Test Case]

  * To reproduce this, one must boot a system (virtual machine is good)
  with the wrong console set on kernel command-line through the
  "console=" parameter *and* not pass the "quiet" parameter.

  * Also, e2fsck tool shouldn't be present in the initrd - for that, the
  6th field of /etc/fstab (fs_passno) should be 0 and initrd must be
  recreated after that. This is the default in Ubuntu, though.

  
  [Regression Potential]

  * The regression potential is small, we're just returning 0 after a
  printf that is executed in error paths, so I don't expect any issues
  from that. But in case something bad happens after this change, I
  expect a more friendly" breakage, like an initramfs panic (drop to a
  shell), not a silent failure or boot-loop.

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 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

This bug was fixed in the package initramfs-tools - 0.130ubuntu3.11

---
initramfs-tools (0.130ubuntu3.11) bionic; urgency=medium

  [ Guilherme G. Piccoli ]
  * scripts/functions: Prevent printf error carry over if the wrong
console is set. (LP: #1879987)
  The function _log_msg() is "void" typed, returning whatever its
  last command returns. This function is the basic building block
  for all error/warning messages in initramfs-tools. If a bad console
  is provided to kernel on command-line, printf returns error, and so
  this error is carried over in _log_msg(). Happens that checkfs()
  function has a loop that runs forever in this scenario (*if* fsck
  is not present in initramfs and "quiet" is not passed in the
  command-line). If that happens, boot is stuck and cannot progress.
  The simple fix hereby merged is to return zero on _log_msg().

  * scripts/local: Re-execute cryptroot local-block script. (LP: #1879980)
  Currently, if an encrypted rootfs is configured on top of a MD RAID1
  array and such array gets degraded (like a member is removed/failed),
  initramfs-tools cannot mount the rootfs and the boot fails. We fix
  that issue here by allowing cryptroot script to re-run on local-block
  stage, given that mdadm is able to activate a degraded array in that
  point. There is a cryptsetup counter-part for this fix, but alone the
  initramfs-tools portion is innocuous.

  [ Jay Vosburgh ]
  * scripts/functions: Change netplan render for net_failover master
devices. (LP: #1820929)
  Modify the _render_netplan function to check for network interfaces
  that are net_failover master devices. When found, such devices are
  matched only by name, not by MAC address, as the MAC is not a unique
  identifier for the net_failover case. In the net_failover architecture,
  the MAC address is used to manage the membership of the net_failover
  interface set, thus multiple interfaces will be assigned the same MAC
  address.

 -- gpicc...@canonical.com (Guilherme G. Piccoli)  Wed, 12 Aug 2020
17:12:11 -0300

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
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:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in initramfs-tools source package in Eoan:
  Won't Fix
Status in initramfs-tools source package in Focal:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  * Currently, if users provide the wrong console in kernel command-line
  (like console=ttyS1, when the right one is ttyS0) *and* "quiet"
  parameter is not provided, we may face an infinite loop on initramfs-
  tools, effectively blocking the boot.

  * Details are: the _log_msg() functions is "void" typed, which means it 
returns whatever its last command returns; this function is the basic building 
block for all error/warning messages in initramfs-tools. In case a bad console 
was provided to kernel on command-line, printf (and apparently all 
write()-related functions) returns error, and so this error is carried over in 
_log_msg().
   
  * Happens that checkfs() function has a loop that runs forever in this 
scenario (*if* fsck is not present in initramfs, and obviously if "quiet" is 
not provided in the command-line). The situation is easily reproducible.

  * This SRU proposes a pretty simple fix: return zero on _log_msg(). We
  should definitely not brake the boot due to error log functions.

  
  [Test Case]

  * To reproduce this, one must boot a system (virtual machine is good)
  with the wrong console set on kernel command-line through the
  "console=" parameter *and* not pass the "quiet" parameter.

  * Also, e2fsck tool shouldn't be present in the initrd - for that, the
  6th field of /etc/fstab (fs_passno) should be 0 and initrd must be
  recreated after that. This is the default in Ubuntu, though.

  
  [Regression Potential]

  * The regression potential is small, we're just returning 0 after a
  printf that is executed in error paths, so I don't expect any issues
  from that. But in case something bad happens after this change, I
  expect a more friendly" breakage, like an initramfs panic (drop to a
  shell), not a silent failure or boot-loop.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

2020-10-06 Thread Łukasz Zemczak

Thank you Alex! In that case, let me review the change once again.

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

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  In Progress
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  In Progress
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends its execution, we execute
  at least once more time cryptsetup. In an ideal world we should loop
  on local-block as Debian's initramfs (in a way to remove hardcoded
  mdadm/cryptsetup mentions from initramfs-tools code), but this would
  be really a big change, non-SRUable probably. I plan to work that for
  future Ubuntu releases.

  [Test case]
  * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to 
create a RAID1 volume and an encrypted root on top of it.

  * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table
  from one of the RAID members. Reboot and it will fail to mount rootfs
  and continue boot process.

  * If using the initramfs-toos/cryptsetup patches hereby proposed, the
  rootfs can be mounted normally.

  [Regression potential]

  * There are potential for regressions, since this is a change in 2
  boot components. The patches were designed in a way to keep the
  regular case working, it changes the failure case which is not
  currently working anyway.

  * A modification in the behavior of cryptsetup was introduced: right
  now, if we fail the password 3 times (the default maximum attempts),
  the script doesn't "panic" and drop to a shell immediately; instead it
  runs once more (or twice, if mdadm is installed) before failing. This
  is a minor change given the benefit of the being able to mount rootfs
  in a degraded RAID1 scenario.

  * Other potential regressions could show-up as boot problems, but the
  change in initramfs-tools specifically is not invasive, it just may
  delay boot time a bit, given we now run cryptsetup multiple times on
  local-block, with 1 sec delays between executions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+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 1820929] Update Released

2020-10-06 Thread Łukasz Zemczak

The verification of the Stable Release Update for initramfs-tools 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/1820929

Title:
  netplan should consider adding more udev attribute for exact matching
  of failover 3-netdev interfaces

Status in netplan:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in netplan.io source package in Bionic:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  [Impact]

  * At present, virtual machines utilizing net_failover network
  interface configurations are incorrectly configured due to the
  reliance on the MAC address to identify specific network interfaces.
  When net_failover is utilized, multiple interfaces will bear the same
  MAC address (the net_failover master itself, as well as the interfaces
  subordinate to it), rendering the MAC address ineffective for unique
  identification of the interface.  This results in incorrect naming of
  network interfaces from the "set-name" directive in the netplan
  configuration.

  * The solution here is to use the interface name instead of the MAC
  address when the interface is a net_failover master device.  Logic is
  added on initramfs-tools to check the device type and virtio flags to
  apply this change only to net_failover master devices.

  [Test Case]

  * The change can be tested by configuring a virtual machine with a
  virtio_net network device with the "failover=on" option to the
  "-device" option to qemu, e.g.,

  -device virtio-net-
  
pci,netdev=hostnet0,id=net0,bus=pci.0,addr=0x3,mac=00:00:17:00:18:04,failover=on

  * This will set the virtio device "standby" feature bit (bit 62,
  counting from 0).  This requires a version of qemu with support for
  this feature.

  * When so configured, the netplan configuration generated by initramfs
  will not contain a "macaddress:" match directive for the network
  interface in question.

  [Regression Potential]

  * Erroneous identification of a network interface as a net_failover
  master device could lead to omission of a macaddress directive,
  causing interfaces to be incorrectly named.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1820929/+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 1898690] Re: package less 487-0.1 failed to install/upgrade: new less package pre-installation script subprocess returned error exit status 2

2020-10-06 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package less 487-0.1 failed to install/upgrade: new less package pre-
  installation script subprocess returned error exit status 2

Status in less package in Ubuntu:
  New

Bug description:
  Ocurred during bionic to focal upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: less 487-0.1
  ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
  Uname: Linux 4.15.0-118-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Oct  6 09:47:23 2020
  DuplicateSignature:
   package:less:487-0.1
   Preparing to unpack .../007-less_551-1ubuntu0.1_amd64.deb ...
   update-alternatives: error: cannot stat file '/etc/mysql/my.cnf.fallback': 
Too many levels of symbolic links
   dpkg: error processing archive 
/tmp/apt-dpkg-install-W2kFIm/007-less_551-1ubuntu0.1_amd64.deb (--unpack):
new less package pre-installation script subprocess returned error exit 
status 2
  Ec2AMI: ami-0002
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: vps-cloud-2
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: new less package pre-installation script subprocess returned 
error exit status 2
  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: less
  Title: package less 487-0.1 failed to install/upgrade: new less package 
pre-installation script subprocess returned error exit status 2
  UpgradeStatus: Upgraded to focal on 2020-10-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/less/+bug/1898690/+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 1898690] [NEW] package less 487-0.1 failed to install/upgrade: new less package pre-installation script subprocess returned error exit status 2

2020-10-06 Thread Guillaume

Public bug reported:

Ocurred during bionic to focal upgrade.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: less 487-0.1
ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
Uname: Linux 4.15.0-118-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Oct  6 09:47:23 2020
DuplicateSignature:
 package:less:487-0.1
 Preparing to unpack .../007-less_551-1ubuntu0.1_amd64.deb ...
 update-alternatives: error: cannot stat file '/etc/mysql/my.cnf.fallback': Too 
many levels of symbolic links
 dpkg: error processing archive 
/tmp/apt-dpkg-install-W2kFIm/007-less_551-1ubuntu0.1_amd64.deb (--unpack):
  new less package pre-installation script subprocess returned error exit 
status 2
Ec2AMI: ami-0002
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: vps-cloud-2
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ErrorMessage: new less package pre-installation script subprocess returned 
error exit status 2
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: less
Title: package less 487-0.1 failed to install/upgrade: new less package 
pre-installation script subprocess returned error exit status 2
UpgradeStatus: Upgraded to focal on 2020-10-06 (0 days ago)

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


** Tags: amd64 apport-package ec2-images focal

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

Title:
  package less 487-0.1 failed to install/upgrade: new less package pre-
  installation script subprocess returned error exit status 2

Status in less package in Ubuntu:
  New

Bug description:
  Ocurred during bionic to focal upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: less 487-0.1
  ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
  Uname: Linux 4.15.0-118-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Oct  6 09:47:23 2020
  DuplicateSignature:
   package:less:487-0.1
   Preparing to unpack .../007-less_551-1ubuntu0.1_amd64.deb ...
   update-alternatives: error: cannot stat file '/etc/mysql/my.cnf.fallback': 
Too many levels of symbolic links
   dpkg: error processing archive 
/tmp/apt-dpkg-install-W2kFIm/007-less_551-1ubuntu0.1_amd64.deb (--unpack):
new less package pre-installation script subprocess returned error exit 
status 2
  Ec2AMI: ami-0002
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: vps-cloud-2
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: new less package pre-installation script subprocess returned 
error exit status 2
  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: less
  Title: package less 487-0.1 failed to install/upgrade: new less package 
pre-installation script subprocess returned error exit status 2
  UpgradeStatus: Upgraded to focal on 2020-10-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/less/+bug/1898690/+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 1897666] Re: FTBFS: nss for groovy ftbfs due to erroneous nonnull check arising from glibc getcwd() annotation

This bug was fixed in the package nss - 2:3.55-1ubuntu3

---
nss (2:3.55-1ubuntu3) groovy; urgency=medium

  * Fix FTBFS due to erroneous glibc out-of-bounds checking with gcc 10
(LP: #1897666)
- debian/patches/fix-ftbfs-glibc-invalid-oob-error.patch: Disable
  non-null error checking on call to getcwd since this results in an
  erroneous warning that causes the build to fail otherwise

 -- Alex Murray   Tue, 29 Sep 2020 10:39:29
+0930

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

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

Title:
  FTBFS: nss for groovy ftbfs due to erroneous nonnull check arising
  from glibc getcwd() annotation

Status in nss package in Ubuntu:
  Fix Released

Bug description:
  As per the archive test rebuild done recently by doko, nss FTBFS due
  to a compiler warning raised by gcc-10 (and this fails the build due
  to the use of -Werror in CFLAGS):

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200925-groovy/+build/20033437

  nsinstall.c: In function ‘main’:
  nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
argument 2 value is 4096 [-Werror=nonnull]
 70 | #define GETCWD getcwd
|^
  nsinstall.c:239:8: note: in expansion of macro ‘GETCWD’
239 |  cwd = GETCWD(0, PATH_MAX);
|^~
  In file included from nsinstall.c:20:
  /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ declared 
with attribute ‘write_only (1, 2)’
520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
|  ^~
  nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
argument 2 value is 4096 [-Werror=nonnull]
 70 | #define GETCWD getcwd
|^
  nsinstall.c:246:13: note: in expansion of macro ‘GETCWD’
246 | todir = GETCWD(0, PATH_MAX);
| ^~
  In file included from nsinstall.c:20:
  /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ declared 
with attribute ‘write_only (1, 2)’
520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
|  ^~
  cc1: all warnings being treated as errors

  According to the upstream bug report at
  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96832 this would appear
  to be because of the annotation of getcwd() with the access attribute.
  However, there seems to be some debate about the best way to resolve
  this (whether in glibc or in the callers of getcwd, ie nss) for now I
  propose to just disable this check via the use of gcc's #pragma
  directive.

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected