[Touch-packages] [Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Triaged => Fix Released

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

Title:
  posix_spawn usage in gnu make causes failures on s390x

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in flatpak package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in make-dfsg package in Ubuntu:
  Invalid

Bug description:
  posix_spawn usage in gnu make causes failures on s390x

  Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
  started to use posix_spawn, instead of fork()/exec().

  This has caused failure of an unrelated package flatpak-builder
  autopkgtests on s390x only, like so

echo Building
make: echo: Operation not permitted
make: *** [Makefile:2: all] Error 127

  Julian Klaude investigated this in-depth. His earlier research also
  indicated that this is a heisenbug, if one tries to print to stderr
  before printing to stdout, no issue occurs.

  We are configuring GNU make to be build with --disable-posix-spawn on
  s390x only. We passed these details to Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=964541 too.

  But I do wonder, if there is something different or incorrect about
  posix_spawn() implementation in either glibc, or linux kernel, on
  s390x. Or gnu-make's usage of posix_spawn().

  As otherise, using posix_spawn() in gnu-make works on other
  architectures, and flatpak-builder autopkgtests pass too.

  It seems very weird that stdout does not appear to be functional,
  unless stderr was opened/written to, from gnu-make execution compiled
  with posix-spawn feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+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 1886626] Re: after login to gnome with snd_hda_intel 0000:00:1f.3: No response from codec

[Hui Wang]

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

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

Title:
  after login to gnome with snd_hda_intel :00:1f.3: No response from
  codec

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  After login to gnome, login takes an unsual amount of time.
  Goes back to login screen.
  On second login, works normally but audio sliders are not showing correctly. 
After a while, it operates normally.
  Logs are showing a lot of
  snd_hda_intel :00:1f.3: No response from codec, resetting bus:last 
cmd0x20a70500
  +pci::00:1f.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-1063.68-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1063-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  killian68   1816 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  7 08:56:11 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-20190418-59+beaver-osp1+X00
  InstallationDate: Installed on 2020-04-02 (96 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.11
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1886626/+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 1893969] Re: Screen corruption and delayed update using onboard Intel video

[Daniel van Vugt]

I can't see a problem in that screenshot or the logs. Maybe consider
attaching a video instead?

Also please tell us if the problem happens:

 * Without your custom xrandr commands

 * In a Wayland session (select 'Ubuntu on Wayland') from the login
screen after selecting your username.


** Tags added: xrandr-scaling

** Tags added: multimonitor

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

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

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

Title:
  Screen corruption and delayed update using onboard Intel video

Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I frequently get screen corruption or delayed screen updates using
  onboard Intel video (i7-10710U in a Dell XPS 13 7390).  I am attaching
  a screen shot of an example of this in Emacs, where you can see echoes
  of past cursor locations (center right side of screen, the highlighted
  word "boolean").

  A frequent failure is that an application updates its window, but the
  updates do not appear on screen until I take some action to disturb
  the window (move or resize it, change focus, change desktops, etc.),
  after which it cleans itself up.  Small changes (such as selecting
  text) will often clean up the image where the change is made without
  repainting the entire window.

  My display panel is 4K UHD+, and I have attached two external Full HD
  DisplayPort monitors using chaining with 2x2 scale using XrandR.  This
  corruption appears to happen on all three surfaces.  The configuration
  for my desktop is:

  HIX=3840
  HIY=2160
  HI=${HIX}x${HIY}
  xrandr --fb $(($HIX * 3))x$HIY \
 --output eDP-1 --auto --panning ${HI}+$(($HIX * 2))+0 \
 --output DP-2-8 --auto --panning ${HI}+$HIX+0 \
 --scale-from $HI --left-of eDP-1 --scale 2x2 \
 --output DP-2-1 --auto --panning $HI+0+0 \
 --scale-from $HI --left-of DP-2-8 --scale 2x2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop:
   
  Date: Wed Sep  2 11:48:03 2020
  DistUpgraded: 2020-06-21 15:36:52,619 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-42-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=UUID=aeb9197c-491f-493d-9a7a-7094efd5023c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-21 (72 days ago)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1893969/+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 1893952] Re: very long boot/log in with log in window upper left corner?

[Daniel van Vugt]

I can't find a simple answer for the slowness or any evidence of it in
the log. However I can see this unsupported package installed, which
will affect practically everything:

  libc6 2.31-2ubuntu1 [origin: unknown]

Please revert that package to a supported version:

  http://launchpadlibrarian.net/495370423/libc6_2.31-0ubuntu11_amd64.deb

Please also reproduce the very long boot again and then run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.


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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  very long boot/log in with log in window upper left corner?

Status in Ubuntu:
  Incomplete

Bug description:
  Been having problems with my installation of 20.10 U-MATE . . .
  reported here earlier to little fanfare . . . but the issues with very
  slow boot times, and then when finally arriving at GUI log in window,
  the log in "tray" is positioned upper left corner of the display and
  it's like a TTY, where it wants user name and then password.  I think
  today it literally took 5 minutes to get logged into the GUI . . . .

  As reported previously I have an install of Lu 20.10 in the same drive
  . . . so far is not having the same problems that U-MATE is having . .
  . .

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Wed Sep  2 07:28:33 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus: broadcom-sta, 6.30.223.271, 5.4.0-42-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK110 [GeForce GTX 780] [10de:1004] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK110 [GeForce GTX 780] [3842:0781]
  InstallationDate: Installed on 2020-01-20 (226 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200119)
  MachineType: Apple Inc. MacPro5,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=e795b2e6-5bef-4a6e-9217-539a6debda90 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 138.0.0.0.0
  dmi.board.asset.tag: 0
  dmi.board.name: Mac-F221BEC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F221BEC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvr138.0.0.0.0:bd07/30/2018:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8:
  dmi.product.family: MacPro
  dmi.product.name: MacPro5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 0.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.5-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

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

[Hui Wang]

Could you please test this kernel:
https://people.canonical.com/~hwang4/testdetect/

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

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

Status in pulseaudio package in Ubuntu:
  Incomplete

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

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

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

[Touch-packages] [Bug 677067] Re: No subwoofer and frontcenter with 5.1 soundblaster x-fi

[Daniel van Vugt]

This bug is closed. Please open a new bug by running:

  ubuntu-bug pulseaudio

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

Title:
  No subwoofer and frontcenter with 5.1 soundblaster x-fi

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  When I select 5.1 analog output I get no sound whatsoever out of the 
subwoofer and front center speakers. These to speakers never emit sound in 
linux (they do in windows), no matter what setting I try.
  Also the input (for microphone) does not work... no sound is registering. I 
do not even get (static) noise when inserting the mini-jack...

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: XFi [Creative X-Fi], device 0: ctxfi [Front/WaveIn]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wouterd1818 F pulseaudio
   /dev/snd/seq:timidity   1638 F timidity
  Card0.Amixer.info:
   Card hw:0 'XFi'/'Creative X-Fi 20K1 SB073x'
 Mixer name : '20K1'
 Components : ''
 Controls  : 29
 Simple ctrls  : 10
  Date: Thu Nov 18 17:15:45 2010
  EcryptfsInUse: Yes
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 03/09/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd03/09/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/677067/+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 1761096] Re: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

[Sergio Durigan Junior]

Thanks for the further investigation, Christian.

So, it doesn't seem to me that /bin/systemd-tty-ask-password-agent is
the culprit here.  Actually, if you look at when it is invoked, you will
notice that it is only executed when the systemctl command is issued
from the tty, which is not our case here: the command that is hanging
("systemctl reload squid") is being invoked indirectly due to the start
of dnsmasq.service.

When we issue a "systemctl start dnsmasq", we can see /bin/systemd-tty-
ask-password-agent there, but not as a child of the "systemctl reload
squid":

root9164  0.0  0.0  26164  1040 pts/0S+   22:23   0:00  |   
\_ systemctl start dnsmasq.service
root9165  0.0  0.0  12512  2084 pts/0S+   22:23   0:00  |   
\_ /bin/bash /bin/systemd-tty-ask-password-agent --watch

This is because we invoked "systemctl start dnsmasq" from the tty.  We
can easily verify that /bin/systemd-tty-ask-password-agent is not to
blame by using "systemctl --no-ask-password stop dnsmasq" and then
"systemctl --no-ask-password start dnsmasq", and verifying that the hang
still happens even though /bin/systemd-tty-ask-password-agent was not
invoked.

Anyway, continuing the investigation here, this is the output of
"systemctl list-jobs":

$ systemctl list-jobs --all 
 JOB UNIT  TYPE   STATE  
2512 dnsmasq.service   start  running
2561 squid.service reload waiting
2560 nss-lookup.target start  waiting

3 jobs listed.

Nothing really new here, except the fact that the squid reload happens
*because* of the nss-lookup.target start, and both jobs are blocked
waiting.  It's interesting to notice that squid's SysV init file says
that squid "Should-Start: $named", which translated to squid trying to
start nss-lookup.target itself.  I think this is a strong indicator that
we might be seeing a deadlock here.

After a bit more investigation, I found
https://github.com/systemd/systemd/issues/10464, which led me to
https://github.com/systemd/systemd/pull/13860.  I tried backporting the
patch (which is very simple) and seeing if it had any impact, but
unfortunately it didn't.

I then did a quick test and hacked /usr/sbin/invoke-rc.d, specifically
around line 570, and commented out the "if" surrounding sctl_args
="--job-mode=ignore-dependencies" (in other words, I made systemctl
always use this option), and unsurprisingly the bug went away.  However,
just like with the "--no-block" hack I mentioned in my previous comment,
I'm not sure this is a good solution for the problem.

As I'm running out of ideas here, I'd like to propose a possible fix for
the problem, based on what Martin Pitt wrote in one of the bug reports I
mentioned (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777113).
I'd like to suggest that we expand /etc/resolvconf/update-libc.d/squid
to take into account whether systemd is being used behind the scenes,
and invoke systemctl to reload squid while also passing "--no-block" to
it.  Something like this:

 if [ -d /run/systemd ]; then
   systemctl --no-block reload squid
 else
   invoke-rc.d squid reload || true
 fi

Based on local tests here, this works and has the benefit of unblocking
nss-lookup.target to also finish, which means that, by the end of the
"systemctl start dnsmasq" process, we will have both successfully
reloaded squid *and* started nss-lookup.target (as well as started
dnsmasq.service, of course).

This is not the perfect solution, of course, but I feel like we're
wasting a lot of time on this old bug already, and this solution is not
entirely bad, IMHO.  We could in theory try to bisect systemd between
xenial and bionic and see if we could determine what change (or changes)
made this scenario work OK on the latter, but that's assuming that it is
systemd indeed who is causing this (I think it is, but I'm not 100% sure
yet).

Anyway, I'll wait for your answer in the morning.  We can discuss this
during standup too, if you'd like.

** Bug watch added: github.com/systemd/systemd/issues #10464
   https://github.com/systemd/systemd/issues/10464

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

Title:
  dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in squid package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  Confirmed
Status in squid source package in Xenial:
  Confirmed

Bug description:
  Setup to reproduce:

  Ubuntu Xenial amd64 net install iso from
  http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-
  amd64/current/images/netboot/mini.iso

  Install system with mostly defaults + LVM + OpenSSH server

  Note that this bug applies to both DHCP and static IP+DNS network
  configurations

  Once server rebooted and is available, log in and install dnsmasq + squid:
  apt-get 

[Touch-packages] [Bug 677067] Re: No subwoofer and frontcenter with 5.1 soundblaster x-fi

[death]

Because for my card, center channel is not called Center, LFE or CLFE
like other cards, but it's Center/LFE instead.

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

Title:
  No subwoofer and frontcenter with 5.1 soundblaster x-fi

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  When I select 5.1 analog output I get no sound whatsoever out of the 
subwoofer and front center speakers. These to speakers never emit sound in 
linux (they do in windows), no matter what setting I try.
  Also the input (for microphone) does not work... no sound is registering. I 
do not even get (static) noise when inserting the mini-jack...

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: XFi [Creative X-Fi], device 0: ctxfi [Front/WaveIn]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wouterd1818 F pulseaudio
   /dev/snd/seq:timidity   1638 F timidity
  Card0.Amixer.info:
   Card hw:0 'XFi'/'Creative X-Fi 20K1 SB073x'
 Mixer name : '20K1'
 Components : ''
 Controls  : 29
 Simple ctrls  : 10
  Date: Thu Nov 18 17:15:45 2010
  EcryptfsInUse: Yes
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 03/09/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd03/09/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/677067/+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 677067] Re: No subwoofer and frontcenter with 5.1 soundblaster x-fi

[death]

For Ubuntu 20.04 or any distro:

I confirm that Middle/center/Subwoofer is working, when add this:

[Element Center/LFE]
switch = mute
volume = merge
override-map.1 = center,lfe

To the /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf

The card is Auzentech Auzen X-Fi Prelude 7.1 with Creative X-Fi 20k1
chip

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

Title:
  No subwoofer and frontcenter with 5.1 soundblaster x-fi

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  When I select 5.1 analog output I get no sound whatsoever out of the 
subwoofer and front center speakers. These to speakers never emit sound in 
linux (they do in windows), no matter what setting I try.
  Also the input (for microphone) does not work... no sound is registering. I 
do not even get (static) noise when inserting the mini-jack...

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: XFi [Creative X-Fi], device 0: ctxfi [Front/WaveIn]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wouterd1818 F pulseaudio
   /dev/snd/seq:timidity   1638 F timidity
  Card0.Amixer.info:
   Card hw:0 'XFi'/'Creative X-Fi 20K1 SB073x'
 Mixer name : '20K1'
 Components : ''
 Controls  : 29
 Simple ctrls  : 10
  Date: Thu Nov 18 17:15:45 2010
  EcryptfsInUse: Yes
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 03/09/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd03/09/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/677067/+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 1886814] Re: posix_spawn usage in gnu make causes failures on s390x

[Dimitri John Ledkov]

All tests run automatically, and yes flatpak-builder was automatically
tested and new flatpak with this fix migrated fine.

See http://autopkgtest.ubuntu.com/packages/flatpak-builder/groovy/s390x

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

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

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: make-dfsg (Ubuntu)
   Status: New => Invalid

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

Title:
  posix_spawn usage in gnu make causes failures on s390x

Status in Ubuntu on IBM z Systems:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in make-dfsg package in Ubuntu:
  Invalid

Bug description:
  posix_spawn usage in gnu make causes failures on s390x

  Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
  started to use posix_spawn, instead of fork()/exec().

  This has caused failure of an unrelated package flatpak-builder
  autopkgtests on s390x only, like so

echo Building
make: echo: Operation not permitted
make: *** [Makefile:2: all] Error 127

  Julian Klaude investigated this in-depth. His earlier research also
  indicated that this is a heisenbug, if one tries to print to stderr
  before printing to stdout, no issue occurs.

  We are configuring GNU make to be build with --disable-posix-spawn on
  s390x only. We passed these details to Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=964541 too.

  But I do wonder, if there is something different or incorrect about
  posix_spawn() implementation in either glibc, or linux kernel, on
  s390x. Or gnu-make's usage of posix_spawn().

  As otherise, using posix_spawn() in gnu-make works on other
  architectures, and flatpak-builder autopkgtests pass too.

  It seems very weird that stdout does not appear to be functional,
  unless stderr was opened/written to, from gnu-make execution compiled
  with posix-spawn feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+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 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content

[Brian Murray]

>From what release is the crash file which you are trying to unpack?

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

Title:
  apport-unpack: ValueError: ['UserGroups'] has no binary content

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Focal:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  apport-unpack crashes when trying to unpack a crash

  [Test Case]
  On a system running 20.04 LTS:
  1) create an additional user who is only a member of their own group e.g.
  bdmurray@clean-focal-amd64:~$ id crashy
  uid=1001(crashy) gid=1001(crashy) groups=1001(crashy)
  2) Launch a process as that user
  3) kill -11 that process
  4) Confirm there is a crash file in /var/crash for that process
  5) Run apport-unpack on that .crash file

  With the version of apport from -proposed you will not get another
  crash file when unpacking the crash file.

  [Regression Potential]
  We are just setting UserGroups to 'N/A' as opposed to having it be completely 
empty so there isn't any chance for regression.

  When running apport-unpack to get at a core dump

  laney@raleigh> sudo apport-unpack 
_usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz
  [sudo] password for laney:
  Traceback (most recent call last):
    File "/usr/bin/apport-unpack", line 73, in 
  pr.extract_keys(f, bin_keys, dir)
    File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in 
extract_keys
  [item for item, element in b64_block.items() if element is False])
  ValueError: ['UserGroups'] has no binary content
  laney@raleigh> apport-cli --version
  2.16.2

  It's not terrible, because most files are unpacked (those which sort
  before UserGroups, I guess).

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: apport 2.16.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportLog:

  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 10:09:26 2015
  InstallationDate: Installed on 2012-10-07 (876 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

[Brian Murray]

Could somebody actively suffering from this problem include the output
of 'sudo service whoopsie status'? Thanks in advance.

It's also worth noting that the apport-autoreport.service is provided by
the apport-noui package and removing that package would be a better way
to work around this problem then removing all of apport.

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

Title:
  systemd 100% cpu usage apport-autoreport.service: Failed with result
  'start-limit-hit'

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  after upgrade from Ubuntu 20.04 to 20.10  
  seeing systemd use 100% cpu forever


  top

top - 10:16:19 up 20 min,  1 user,  load average: 3.91, 4.28, 3.39
Tasks: 332 total,   2 running, 330 sleeping,   0 stopped,   0 zombie
%Cpu(s): 18.7 us,  6.4 sy, 11.9 ni, 62.2 id,  0.0 wa,  0.0 hi,  0.8 si, 
 0.0 st
MiB Mem :  15917.6 total,   8553.4 free,   2604.3 used,   4759.9 
buff/cache
MiB Swap:   2048.0 total,   2048.0 free,  0.0 used.  12633.7 avail 
Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND  
  1 root  20   0  177316  12252   8684 R 100.0   0.1  15:01.25 
systemd  
   4636 kush  39  19  633796 176152  16360 S  98.3   1.1  17:51.56 
tracker-miner-f  
820 message+  20   0   10740   6452   4212 S  39.8   0.0   6:19.06 
dbus-daemon  
316 root  19  -1  535916 322896 320824 S  15.3   2.0   3:16.41 
systemd-journal  
844 syslog20   0  221136   5840   3920 S  13.6   0.0   2:14.52 
rsyslogd 
858 root  20   0   83708  74124   7568 S  12.7   0.5   2:06.98 
systemd-logind   
  5 root  20   0   0  0  0 I   3.4   0.0   0:05.01 
kworker/0:0-events   
  35566 kush  20   0 3850088 588344 262192 S   2.5   3.6   0:30.48 
MainThread   
   5626 kush  20   0 5004788 260876  93400 S   1.7   1.6   3:05.19 
gnome-shell  
   7033 kush  20   0  869792  66440  44272 S   1.7   0.4   0:06.05 
gnome-terminal-  
  36790 kush  20   0 2525432 156636  98568 S   1.7   1.0   0:04.99 
Web Content  
957 root  20   0 1556196  45044  24284 S   0.8   0.3   0:02.48 
containerd   
   1038 root  20   0   10460   4412   3300 S   0.8   0.0   0:00.16 
fancontrol   



  
sudo tail -n 100 /var/log/syslog
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 

[Touch-packages] [Bug 1894000] [NEW] package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

[JHON Bobie]

Public bug reported:

installation impossible

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lvm2 2.03.07-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Sep  2 15:37:38 2020
ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2020-08-29 (4 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: 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: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

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:
  New

Bug description:
  installation impossible

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep  2 15:37:38 2020
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-08-29 (4 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: 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: No upgrade log present (probably fresh install)

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

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

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

[Douglas Santos]

It seems to be very similar to bug 1881659, indeed.

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

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

Status in pulseaudio package in Ubuntu:
  Incomplete

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

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

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

[Touch-packages] [Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content

[Eric Desrochers]

I'm having the same stack trace from groovy, when trying to unpack

ii  apport 2.20.11-0ubuntu45 all
  automatically generate crash reports for debugging
ii  apport-symptoms0.23  all
  symptom scripts for apport
ii  python3-apport 2.20.11-0ubuntu45 all
  Python 3 library for Apport crash report handling

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

Title:
  apport-unpack: ValueError: ['UserGroups'] has no binary content

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Focal:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  apport-unpack crashes when trying to unpack a crash

  [Test Case]
  On a system running 20.04 LTS:
  1) create an additional user who is only a member of their own group e.g.
  bdmurray@clean-focal-amd64:~$ id crashy
  uid=1001(crashy) gid=1001(crashy) groups=1001(crashy)
  2) Launch a process as that user
  3) kill -11 that process
  4) Confirm there is a crash file in /var/crash for that process
  5) Run apport-unpack on that .crash file

  With the version of apport from -proposed you will not get another
  crash file when unpacking the crash file.

  [Regression Potential]
  We are just setting UserGroups to 'N/A' as opposed to having it be completely 
empty so there isn't any chance for regression.

  When running apport-unpack to get at a core dump

  laney@raleigh> sudo apport-unpack 
_usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz
  [sudo] password for laney:
  Traceback (most recent call last):
    File "/usr/bin/apport-unpack", line 73, in 
  pr.extract_keys(f, bin_keys, dir)
    File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in 
extract_keys
  [item for item, element in b64_block.items() if element is False])
  ValueError: ['UserGroups'] has no binary content
  laney@raleigh> apport-cli --version
  2.16.2

  It's not terrible, because most files are unpacked (those which sort
  before UserGroups, I guess).

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: apport 2.16.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportLog:

  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 10:09:26 2015
  InstallationDate: Installed on 2012-10-07 (876 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1888572] Re: motd-news: use wget instead of curl

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 11ubuntu5.2

---
base-files (11ubuntu5.2) focal; urgency=medium

  [ Andreas Hasenack ]
  * motd/50-motd-news: don't include uptime in the user-agent string
(LP: #1886572)
  * Move the /etc/default/motd-news conffile to the motd-news-config
package (LP: #1888575):
- d/base-files.maintscript: remove /etc/default/motd-news config file
  on upgrade
- d/control: break on ubuntu-server << 1.450.2 to force an upgrade if
  it is installed, which will pull motd-news-config and the conffile
  back in
- d/motd-news-config.postinst:
  + handle the upgrade case where the motd-news config file was
changed while it belonged to base-files
  + disable motd-news if the config file was removed by hand before
the upgrade
- d/postinst.in: signal the motd-news-config package if the
  motd-news config file was removed manually before the upgrade
- d/control: new motd-news-config package, carrying the
  configuration file for the /etc/update-motd.d/50-motd-news script.
- d/rules, d/motd-news-config.install: /e/d/motd-news is in the
  motd-news-config package now

  [ Steve Langasek ]
  * motd/50-motd-news: use wget instead of curl, since wget is standard but
curl is optional (LP: #1888572):
- This changes the timeout behavior slightly because wget does not have
  an exact equivalent to curl's --max-time argument, we are using
  --timeout instead.

 -- Andreas Hasenack   Mon, 17 Aug 2020 10:31:58
-0300

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

Title:
  motd-news: use wget instead of curl

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released

Bug description:
  [Impact] 
  The motd-news script is using curl, but since that is an optional package, 
there is no guarantee that it will be installed. The script correctly checks 
for its presence before trying to use it, though, so it won't fail. As we don't 
want to add such a dependency to the base-files package, we should switch to 
wget, which is standard.

  [Test Case]
  wget has a different behavior than curl in some areas, one of which is 
crucial for the motd-per-cloud feature. While curl will only complain about a 
404 from the server if given a specific parameter (-f), wget does that by 
default, and needs special handling.

  a) With curl, base-files and ubuntu-server installed, first verify motd-news 
works:
  $ sudo /etc/update-motd.d/50-motd-news --force

   * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
 sudo snap install microk8s --channel=1.19/candidate --classic

 https://microk8s.io/ has docs and details.

  Now remove curl, and retry. It should exit immediately with no output:

  $ sudo /etc/update-motd.d/50-motd-news --force

  Install the updated base-files package and the new motd-news-config
  package from proposed:

  $ sudo apt install base-files motd-news-config

  Note curl is still not available:
  $ curl

  Command 'curl' not found, but can be installed with:

  sudo apt install curl

  Re-run the motd-news script, this time it should produce output again:
  $ sudo /etc/update-motd.d/50-motd-news --force

   * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
 sudo snap install microk8s --channel=1.19/candidate --classic

 https://microk8s.io/ has docs and details.

  b) Verify motd-news per cloud remains working.
  If you have /usr/bin/cloud-id, copy it to a backup:
  sudo cp /usr/bin/cloud-id{,.orig}

  Create a new one, per supported cloud. For aws, for example:
  echo -e '#!/bin/sh\necho aws' | sudo tee /usr/bin/cloud-id

  Confirm by running it:
  $ cloud-id
  aws

  And confirm motd-news keeps working (it might return different content):
  $ sudo /etc/update-motd.d/50-motd-news --force

   * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
 sudo snap install microk8s --channel=1.19/candidate --classic

 https://microk8s.io/ has docs and details.

  Repeat for the gce and azure clouds, by changing the cloud-id script
  accordingly.

  To confirm the right cloud_id is being used, use sh -x and grep for
  its output:

  $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1 | grep -wE 'wget 
.*cloud_id/[a-z]+'
  + wget --timeout 60 -U wget/1.20.3-1ubuntu1 Ubuntu/20.04.1/LTS 
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz 
cloud_id/azure -O- --content-on-error https://motd.ubuntu.com

  This also verifies again it's using wget instead of curl.

  
  [Regression Potential] 
  Possible regressions will likely be tied to a difference in behavior between 
curl and wget. In 

[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.450.2

---
ubuntu-meta (1.450.2) focal; urgency=medium

  * d/control: have ubuntu-server depend on motd-news-config
(LP: #1888575)

 -- Andreas Hasenack   Thu, 06 Aug 2020 14:36:39
-0300

** Changed in: base-files (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 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 ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
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)

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 
jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's 
configure case.

  b) /e/d/motd-news config file was *removed* while it belonged to base-files. 
In such a case, a normal upgrade of the package (base-files in this example) 
would not reinstate the file. Much less this upgrade here, which has an 
explicit rm_conffile maintscript-helper for it. But the motd-news-config 
package that could be installed in the transaction would 

[Touch-packages] [Bug 1886572] Update Released

[Steve Langasek]

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released

Bug description:
  [Impact] 
  The uptime value in the user-agent string sent to the motd-news server is 
unused and not necessary. It should be removed.

  [Test Case]
  Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is 
no longer used.

  Previous version:
  $ grep uptime /etc/update-motd.d/50-motd-news 
  # Some messages may only be pertinent before or after some amount of uptime
  read up idle < /proc/uptime
  uptime="uptime/$up/$idle"
  USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id"

  Updated version:
  $ grep uptime /etc/update-motd.d/50-motd-news
   (no output)

  
  [Regression Potential] 
  The server side, if it were checking this value, could be surprised by this 
change.

  [Other Info]
  N/A

  [Original Description]
  I don't why that was included but it shouldn't be. Please remove it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+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 1886572] Re: Remove uptime from the motd-news user agent

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 11ubuntu5.2

---
base-files (11ubuntu5.2) focal; urgency=medium

  [ Andreas Hasenack ]
  * motd/50-motd-news: don't include uptime in the user-agent string
(LP: #1886572)
  * Move the /etc/default/motd-news conffile to the motd-news-config
package (LP: #1888575):
- d/base-files.maintscript: remove /etc/default/motd-news config file
  on upgrade
- d/control: break on ubuntu-server << 1.450.2 to force an upgrade if
  it is installed, which will pull motd-news-config and the conffile
  back in
- d/motd-news-config.postinst:
  + handle the upgrade case where the motd-news config file was
changed while it belonged to base-files
  + disable motd-news if the config file was removed by hand before
the upgrade
- d/postinst.in: signal the motd-news-config package if the
  motd-news config file was removed manually before the upgrade
- d/control: new motd-news-config package, carrying the
  configuration file for the /etc/update-motd.d/50-motd-news script.
- d/rules, d/motd-news-config.install: /e/d/motd-news is in the
  motd-news-config package now

  [ Steve Langasek ]
  * motd/50-motd-news: use wget instead of curl, since wget is standard but
curl is optional (LP: #1888572):
- This changes the timeout behavior slightly because wget does not have
  an exact equivalent to curl's --max-time argument, we are using
  --timeout instead.

 -- Andreas Hasenack   Mon, 17 Aug 2020 10:31:58
-0300

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released

Bug description:
  [Impact] 
  The uptime value in the user-agent string sent to the motd-news server is 
unused and not necessary. It should be removed.

  [Test Case]
  Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is 
no longer used.

  Previous version:
  $ grep uptime /etc/update-motd.d/50-motd-news 
  # Some messages may only be pertinent before or after some amount of uptime
  read up idle < /proc/uptime
  uptime="uptime/$up/$idle"
  USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id"

  Updated version:
  $ grep uptime /etc/update-motd.d/50-motd-news
   (no output)

  
  [Regression Potential] 
  The server side, if it were checking this value, could be surprised by this 
change.

  [Other Info]
  N/A

  [Original Description]
  I don't why that was included but it shouldn't be. Please remove it.

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

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 10.1ubuntu2.10

---
base-files (10.1ubuntu2.10) bionic; urgency=medium

  [ Andreas Hasenack ]
  * motd/50-motd-news: don't include uptime in the user-agent string
(LP: #1886572)
  * Move the /etc/default/motd-news conffile to the motd-news-config
package (LP: #1888575):
- d/base-files.maintscript: remove /etc/default/motd-news config file
  on upgrade
- d/control: break on ubuntu-server << 1.417.5 to force an upgrade if
  it is installed, which will pull motd-news-config and the conffile
  back in
- d/motd-news-config.postinst:
  + handle the upgrade case where the motd-news config file was
changed while it belonged to base-files
  + disable motd-news if the config file was removed by hand before
the upgrade
- d/postinst.in: signal the motd-news-config package if the
  motd-news config file was removed manually before the upgrade
- d/control: new motd-news-config package, carrying the
  configuration file for the /etc/update-motd.d/50-motd-news script.
- d/rules, d/motd-news-config.install: /e/d/motd-news is in the
  motd-news-config package now

  [ Steve Langasek ]
  * motd/50-motd-news: use wget instead of curl, since wget is standard but
curl is optional (LP: #1888572):
- This changes the timeout behavior slightly because wget does not have
  an exact equivalent to curl's --max-time argument, we are using
  --timeout instead.

 -- Andreas Hasenack   Thu, 13 Aug 2020 15:59:47
-0300

** Changed in: ubuntu-meta (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 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 ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
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, 

[Touch-packages] [Bug 1888572] Re: motd-news: use wget instead of curl

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 10.1ubuntu2.10

---
base-files (10.1ubuntu2.10) bionic; urgency=medium

  [ Andreas Hasenack ]
  * motd/50-motd-news: don't include uptime in the user-agent string
(LP: #1886572)
  * Move the /etc/default/motd-news conffile to the motd-news-config
package (LP: #1888575):
- d/base-files.maintscript: remove /etc/default/motd-news config file
  on upgrade
- d/control: break on ubuntu-server << 1.417.5 to force an upgrade if
  it is installed, which will pull motd-news-config and the conffile
  back in
- d/motd-news-config.postinst:
  + handle the upgrade case where the motd-news config file was
changed while it belonged to base-files
  + disable motd-news if the config file was removed by hand before
the upgrade
- d/postinst.in: signal the motd-news-config package if the
  motd-news config file was removed manually before the upgrade
- d/control: new motd-news-config package, carrying the
  configuration file for the /etc/update-motd.d/50-motd-news script.
- d/rules, d/motd-news-config.install: /e/d/motd-news is in the
  motd-news-config package now

  [ Steve Langasek ]
  * motd/50-motd-news: use wget instead of curl, since wget is standard but
curl is optional (LP: #1888572):
- This changes the timeout behavior slightly because wget does not have
  an exact equivalent to curl's --max-time argument, we are using
  --timeout instead.

 -- Andreas Hasenack   Thu, 13 Aug 2020 15:59:47
-0300

** Changed in: base-files (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  motd-news: use wget instead of curl

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released

Bug description:
  [Impact] 
  The motd-news script is using curl, but since that is an optional package, 
there is no guarantee that it will be installed. The script correctly checks 
for its presence before trying to use it, though, so it won't fail. As we don't 
want to add such a dependency to the base-files package, we should switch to 
wget, which is standard.

  [Test Case]
  wget has a different behavior than curl in some areas, one of which is 
crucial for the motd-per-cloud feature. While curl will only complain about a 
404 from the server if given a specific parameter (-f), wget does that by 
default, and needs special handling.

  a) With curl, base-files and ubuntu-server installed, first verify motd-news 
works:
  $ sudo /etc/update-motd.d/50-motd-news --force

   * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
 sudo snap install microk8s --channel=1.19/candidate --classic

 https://microk8s.io/ has docs and details.

  Now remove curl, and retry. It should exit immediately with no output:

  $ sudo /etc/update-motd.d/50-motd-news --force

  Install the updated base-files package and the new motd-news-config
  package from proposed:

  $ sudo apt install base-files motd-news-config

  Note curl is still not available:
  $ curl

  Command 'curl' not found, but can be installed with:

  sudo apt install curl

  Re-run the motd-news script, this time it should produce output again:
  $ sudo /etc/update-motd.d/50-motd-news --force

   * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
 sudo snap install microk8s --channel=1.19/candidate --classic

 https://microk8s.io/ has docs and details.

  b) Verify motd-news per cloud remains working.
  If you have /usr/bin/cloud-id, copy it to a backup:
  sudo cp /usr/bin/cloud-id{,.orig}

  Create a new one, per supported cloud. For aws, for example:
  echo -e '#!/bin/sh\necho aws' | sudo tee /usr/bin/cloud-id

  Confirm by running it:
  $ cloud-id
  aws

  And confirm motd-news keeps working (it might return different content):
  $ sudo /etc/update-motd.d/50-motd-news --force

   * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
 sudo snap install microk8s --channel=1.19/candidate --classic

 https://microk8s.io/ has docs and details.

  Repeat for the gce and azure clouds, by changing the cloud-id script
  accordingly.

  To confirm the right cloud_id is being used, use sh -x and grep for
  its output:

  $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1 | grep -wE 'wget 
.*cloud_id/[a-z]+'
  + wget --timeout 60 -U wget/1.20.3-1ubuntu1 Ubuntu/20.04.1/LTS 
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz 
cloud_id/azure -O- --content-on-error https://motd.ubuntu.com

  This 

[Touch-packages] [Bug 1886572] Re: Remove uptime from the motd-news user agent

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 9.4ubuntu4.13

---
base-files (9.4ubuntu4.13) xenial; urgency=medium

  [ Andreas Hasenack ]
  * motd/50-motd-news: don't include uptime in the user-agent string
(LP: #1886572)
  * Move the /etc/default/motd-news conffile to the motd-news-config
package (LP: #1888575):
- d/postinst.in, d/postrm, d/preinst: remove /etc/default/motd-news
  config file on base-files upgrade using dpkg-maintscript-helper
- d/rules: install d/preinst
- d/control: break on ubuntu-server << 1.361.5 to force an upgrade if
  it is installed, which will pull motd-news-config and the conffile
  back in
- d/control: new motd-news-config package, carrying the
  configuration file for the /etc/update-motd.d/50-motd-news script.
- d/motd-news-config.postinst:
  + handle the upgrade case where the motd-news config file was
changed while it belonged to base-files
  + disable motd-news if the config file was removed by hand before
the upgrade
- d/postinst.in: signal the motd-news-config package if the
  motd-news config file was removed manually before the upgrade
- d/conffiles: remove motd-news
- d/rules, d/motd-news-config.conffiles: packaging motd-news-config
  without debhelper

  [ Steve Langasek ]
  * motd/50-motd-news: use wget instead of curl, since wget is standard but
curl is optional (LP: #1888572):
- This changes the timeout behavior slightly because wget does not have
  an exact equivalent to curl's --max-time argument, we are using
  --timeout instead.

 -- Andreas Hasenack   Mon, 17 Aug 2020 11:19:19
-0300

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released

Bug description:
  [Impact] 
  The uptime value in the user-agent string sent to the motd-news server is 
unused and not necessary. It should be removed.

  [Test Case]
  Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is 
no longer used.

  Previous version:
  $ grep uptime /etc/update-motd.d/50-motd-news 
  # Some messages may only be pertinent before or after some amount of uptime
  read up idle < /proc/uptime
  uptime="uptime/$up/$idle"
  USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id"

  Updated version:
  $ grep uptime /etc/update-motd.d/50-motd-news
   (no output)

  
  [Regression Potential] 
  The server side, if it were checking this value, could be surprised by this 
change.

  [Other Info]
  N/A

  [Original Description]
  I don't why that was included but it shouldn't be. Please remove it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+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 1886572] Re: Remove uptime from the motd-news user agent

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 10.1ubuntu2.10

---
base-files (10.1ubuntu2.10) bionic; urgency=medium

  [ Andreas Hasenack ]
  * motd/50-motd-news: don't include uptime in the user-agent string
(LP: #1886572)
  * Move the /etc/default/motd-news conffile to the motd-news-config
package (LP: #1888575):
- d/base-files.maintscript: remove /etc/default/motd-news config file
  on upgrade
- d/control: break on ubuntu-server << 1.417.5 to force an upgrade if
  it is installed, which will pull motd-news-config and the conffile
  back in
- d/motd-news-config.postinst:
  + handle the upgrade case where the motd-news config file was
changed while it belonged to base-files
  + disable motd-news if the config file was removed by hand before
the upgrade
- d/postinst.in: signal the motd-news-config package if the
  motd-news config file was removed manually before the upgrade
- d/control: new motd-news-config package, carrying the
  configuration file for the /etc/update-motd.d/50-motd-news script.
- d/rules, d/motd-news-config.install: /e/d/motd-news is in the
  motd-news-config package now

  [ Steve Langasek ]
  * motd/50-motd-news: use wget instead of curl, since wget is standard but
curl is optional (LP: #1888572):
- This changes the timeout behavior slightly because wget does not have
  an exact equivalent to curl's --max-time argument, we are using
  --timeout instead.

 -- Andreas Hasenack   Thu, 13 Aug 2020 15:59:47
-0300

** Changed in: base-files (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released

Bug description:
  [Impact] 
  The uptime value in the user-agent string sent to the motd-news server is 
unused and not necessary. It should be removed.

  [Test Case]
  Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is 
no longer used.

  Previous version:
  $ grep uptime /etc/update-motd.d/50-motd-news 
  # Some messages may only be pertinent before or after some amount of uptime
  read up idle < /proc/uptime
  uptime="uptime/$up/$idle"
  USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id"

  Updated version:
  $ grep uptime /etc/update-motd.d/50-motd-news
   (no output)

  
  [Regression Potential] 
  The server side, if it were checking this value, could be surprised by this 
change.

  [Other Info]
  N/A

  [Original Description]
  I don't why that was included but it shouldn't be. Please remove it.

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

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 11ubuntu5.2

---
base-files (11ubuntu5.2) focal; urgency=medium

  [ Andreas Hasenack ]
  * motd/50-motd-news: don't include uptime in the user-agent string
(LP: #1886572)
  * Move the /etc/default/motd-news conffile to the motd-news-config
package (LP: #1888575):
- d/base-files.maintscript: remove /etc/default/motd-news config file
  on upgrade
- d/control: break on ubuntu-server << 1.450.2 to force an upgrade if
  it is installed, which will pull motd-news-config and the conffile
  back in
- d/motd-news-config.postinst:
  + handle the upgrade case where the motd-news config file was
changed while it belonged to base-files
  + disable motd-news if the config file was removed by hand before
the upgrade
- d/postinst.in: signal the motd-news-config package if the
  motd-news config file was removed manually before the upgrade
- d/control: new motd-news-config package, carrying the
  configuration file for the /etc/update-motd.d/50-motd-news script.
- d/rules, d/motd-news-config.install: /e/d/motd-news is in the
  motd-news-config package now

  [ Steve Langasek ]
  * motd/50-motd-news: use wget instead of curl, since wget is standard but
curl is optional (LP: #1888572):
- This changes the timeout behavior slightly because wget does not have
  an exact equivalent to curl's --max-time argument, we are using
  --timeout instead.

 -- Andreas Hasenack   Mon, 17 Aug 2020 10:31:58
-0300

-- 
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 ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
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 

[Touch-packages] [Bug 1888572] Re: motd-news: use wget instead of curl

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 9.4ubuntu4.13

---
base-files (9.4ubuntu4.13) xenial; urgency=medium

  [ Andreas Hasenack ]
  * motd/50-motd-news: don't include uptime in the user-agent string
(LP: #1886572)
  * Move the /etc/default/motd-news conffile to the motd-news-config
package (LP: #1888575):
- d/postinst.in, d/postrm, d/preinst: remove /etc/default/motd-news
  config file on base-files upgrade using dpkg-maintscript-helper
- d/rules: install d/preinst
- d/control: break on ubuntu-server << 1.361.5 to force an upgrade if
  it is installed, which will pull motd-news-config and the conffile
  back in
- d/control: new motd-news-config package, carrying the
  configuration file for the /etc/update-motd.d/50-motd-news script.
- d/motd-news-config.postinst:
  + handle the upgrade case where the motd-news config file was
changed while it belonged to base-files
  + disable motd-news if the config file was removed by hand before
the upgrade
- d/postinst.in: signal the motd-news-config package if the
  motd-news config file was removed manually before the upgrade
- d/conffiles: remove motd-news
- d/rules, d/motd-news-config.conffiles: packaging motd-news-config
  without debhelper

  [ Steve Langasek ]
  * motd/50-motd-news: use wget instead of curl, since wget is standard but
curl is optional (LP: #1888572):
- This changes the timeout behavior slightly because wget does not have
  an exact equivalent to curl's --max-time argument, we are using
  --timeout instead.

 -- Andreas Hasenack   Mon, 17 Aug 2020 11:19:19
-0300

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

Title:
  motd-news: use wget instead of curl

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released

Bug description:
  [Impact] 
  The motd-news script is using curl, but since that is an optional package, 
there is no guarantee that it will be installed. The script correctly checks 
for its presence before trying to use it, though, so it won't fail. As we don't 
want to add such a dependency to the base-files package, we should switch to 
wget, which is standard.

  [Test Case]
  wget has a different behavior than curl in some areas, one of which is 
crucial for the motd-per-cloud feature. While curl will only complain about a 
404 from the server if given a specific parameter (-f), wget does that by 
default, and needs special handling.

  a) With curl, base-files and ubuntu-server installed, first verify motd-news 
works:
  $ sudo /etc/update-motd.d/50-motd-news --force

   * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
 sudo snap install microk8s --channel=1.19/candidate --classic

 https://microk8s.io/ has docs and details.

  Now remove curl, and retry. It should exit immediately with no output:

  $ sudo /etc/update-motd.d/50-motd-news --force

  Install the updated base-files package and the new motd-news-config
  package from proposed:

  $ sudo apt install base-files motd-news-config

  Note curl is still not available:
  $ curl

  Command 'curl' not found, but can be installed with:

  sudo apt install curl

  Re-run the motd-news script, this time it should produce output again:
  $ sudo /etc/update-motd.d/50-motd-news --force

   * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
 sudo snap install microk8s --channel=1.19/candidate --classic

 https://microk8s.io/ has docs and details.

  b) Verify motd-news per cloud remains working.
  If you have /usr/bin/cloud-id, copy it to a backup:
  sudo cp /usr/bin/cloud-id{,.orig}

  Create a new one, per supported cloud. For aws, for example:
  echo -e '#!/bin/sh\necho aws' | sudo tee /usr/bin/cloud-id

  Confirm by running it:
  $ cloud-id
  aws

  And confirm motd-news keeps working (it might return different content):
  $ sudo /etc/update-motd.d/50-motd-news --force

   * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
 sudo snap install microk8s --channel=1.19/candidate --classic

 https://microk8s.io/ has docs and details.

  Repeat for the gce and azure clouds, by changing the cloud-id script
  accordingly.

  To confirm the right cloud_id is being used, use sh -x and grep for
  its output:

  $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1 | grep -wE 'wget 
.*cloud_id/[a-z]+'
  + wget --timeout 60 -U wget/1.20.3-1ubuntu1 Ubuntu/20.04.1/LTS 
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz 
cloud_id/azure -O- --content-on-error 

[Touch-packages] [Bug 1888572] Update Released

[Steve Langasek]

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

Title:
  motd-news: use wget instead of curl

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released

Bug description:
  [Impact] 
  The motd-news script is using curl, but since that is an optional package, 
there is no guarantee that it will be installed. The script correctly checks 
for its presence before trying to use it, though, so it won't fail. As we don't 
want to add such a dependency to the base-files package, we should switch to 
wget, which is standard.

  [Test Case]
  wget has a different behavior than curl in some areas, one of which is 
crucial for the motd-per-cloud feature. While curl will only complain about a 
404 from the server if given a specific parameter (-f), wget does that by 
default, and needs special handling.

  a) With curl, base-files and ubuntu-server installed, first verify motd-news 
works:
  $ sudo /etc/update-motd.d/50-motd-news --force

   * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
 sudo snap install microk8s --channel=1.19/candidate --classic

 https://microk8s.io/ has docs and details.

  Now remove curl, and retry. It should exit immediately with no output:

  $ sudo /etc/update-motd.d/50-motd-news --force

  Install the updated base-files package and the new motd-news-config
  package from proposed:

  $ sudo apt install base-files motd-news-config

  Note curl is still not available:
  $ curl

  Command 'curl' not found, but can be installed with:

  sudo apt install curl

  Re-run the motd-news script, this time it should produce output again:
  $ sudo /etc/update-motd.d/50-motd-news --force

   * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
 sudo snap install microk8s --channel=1.19/candidate --classic

 https://microk8s.io/ has docs and details.

  b) Verify motd-news per cloud remains working.
  If you have /usr/bin/cloud-id, copy it to a backup:
  sudo cp /usr/bin/cloud-id{,.orig}

  Create a new one, per supported cloud. For aws, for example:
  echo -e '#!/bin/sh\necho aws' | sudo tee /usr/bin/cloud-id

  Confirm by running it:
  $ cloud-id
  aws

  And confirm motd-news keeps working (it might return different content):
  $ sudo /etc/update-motd.d/50-motd-news --force

   * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
 sudo snap install microk8s --channel=1.19/candidate --classic

 https://microk8s.io/ has docs and details.

  Repeat for the gce and azure clouds, by changing the cloud-id script
  accordingly.

  To confirm the right cloud_id is being used, use sh -x and grep for
  its output:

  $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1 | grep -wE 'wget 
.*cloud_id/[a-z]+'
  + wget --timeout 60 -U wget/1.20.3-1ubuntu1 Ubuntu/20.04.1/LTS 
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz 
cloud_id/azure -O- --content-on-error https://motd.ubuntu.com

  This also verifies again it's using wget instead of curl.

  
  [Regression Potential] 
  Possible regressions will likely be tied to a difference in behavior between 
curl and wget. In fact, one was caught[1] in the development release and the 
fix is included here, with a test.

  
  [Other Info]
  N/A

  1. https://bugs.launchpad.net/bugs/1889117

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

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 9.4ubuntu4.13

---
base-files (9.4ubuntu4.13) xenial; urgency=medium

  [ Andreas Hasenack ]
  * motd/50-motd-news: don't include uptime in the user-agent string
(LP: #1886572)
  * Move the /etc/default/motd-news conffile to the motd-news-config
package (LP: #1888575):
- d/postinst.in, d/postrm, d/preinst: remove /etc/default/motd-news
  config file on base-files upgrade using dpkg-maintscript-helper
- d/rules: install d/preinst
- d/control: break on ubuntu-server << 1.361.5 to force an upgrade if
  it is installed, which will pull motd-news-config and the conffile
  back in
- d/control: new motd-news-config package, carrying the
  configuration file for the /etc/update-motd.d/50-motd-news script.
- d/motd-news-config.postinst:
  + handle the upgrade case where the motd-news config file was
changed while it belonged to base-files
  + disable motd-news if the config file was removed by hand before
the upgrade
- d/postinst.in: signal the motd-news-config package if the
  motd-news config file was removed manually before the upgrade
- d/conffiles: remove motd-news
- d/rules, d/motd-news-config.conffiles: packaging motd-news-config
  without debhelper

  [ Steve Langasek ]
  * motd/50-motd-news: use wget instead of curl, since wget is standard but
curl is optional (LP: #1888572):
- This changes the timeout behavior slightly because wget does not have
  an exact equivalent to curl's --max-time argument, we are using
  --timeout instead.

 -- Andreas Hasenack   Mon, 17 Aug 2020 11:19:19
-0300

-- 
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 ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
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, 

[Touch-packages] [Bug 1888575] Update Released

[Steve Langasek]

The verification of the Stable Release Update for base-files 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 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 ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
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)

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 
jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's 
configure case.

  b) /e/d/motd-news config file was *removed* while it belonged to base-files. 
In such a case, a normal upgrade of the package (base-files in this example) 
would not reinstate the file. Much less this upgrade here, which has an 

[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.417.5

---
ubuntu-meta (1.417.5) bionic; urgency=medium

  * d/control: ubuntu-server depends on motd-news-config
(LP: #1888575)

 -- Andreas Hasenack   Fri, 07 Aug 2020 19:11:57
+

** Changed in: ubuntu-meta (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: base-files (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 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 ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
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)

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 
jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's 
configure case.

  b) /e/d/motd-news config file was *removed* while it belonged to base-files. 
In such a case, a normal upgrade of the package (base-files in this example) 
would not reinstate the file. Much less this upgrade here, which has an 
explicit rm_conffile maintscript-helper for 

[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.361.5

---
ubuntu-meta (1.361.5) xenial; urgency=medium

  * d/control: ubuntu-server depends on motd-news-config
(LP: #1888575)

 -- Andreas Hasenack   Thu, 13 Aug 2020 17:41:56
-0300

** Changed in: ubuntu-meta (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: base-files (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 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 ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
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)

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 
jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's 
configure case.

  b) /e/d/motd-news config file was *removed* while it belonged to base-files. 
In such a case, a normal upgrade of the package (base-files in this example) 
would not reinstate the file. Much less this upgrade here, which has an 
explicit rm_conffile maintscript-helper for 

[Touch-packages] [Bug 1893846] Dependencies.txt

[Douglas Santos]

apport information

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

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

Status in pulseaudio package in Ubuntu:
  Incomplete

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

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

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

[Touch-packages] [Bug 1893846] ProcCpuinfoMinimal.txt

[Douglas Santos]

apport information

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

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

Status in pulseaudio package in Ubuntu:
  Incomplete

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

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

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

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

[Douglas Santos]

apport information

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

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

Status in pulseaudio package in Ubuntu:
  Incomplete

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

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

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

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

[Douglas Santos]

apport information

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

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

Status in pulseaudio package in Ubuntu:
  Incomplete

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

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

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

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

[Douglas Santos]

apport information

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

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

Status in pulseaudio package in Ubuntu:
  Incomplete

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

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

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

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

[Douglas Santos]

apport information

** Tags added: apport-collected

** Description changed:

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

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

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

Status in pulseaudio package in Ubuntu:
  Incomplete

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

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

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

[Touch-packages] [Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content

[Eric Desrochers]

$ lsb_release -cs
bionic

$ apport-unpack /var/tmp/_usr_bin_.0.crash /tmp/
Traceback (most recent call last):
  File "/usr/bin/apport-unpack", line 74, in 
pr.extract_keys(f, bin_keys, dir)
  File "/usr/lib/python3/dist-packages/problem_report.py", line 270, in 
extract_keys
[item for item, element in b64_block.items() if element is False])
ValueError: ['UserGroups'] has no binary content

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

Title:
  apport-unpack: ValueError: ['UserGroups'] has no binary content

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Focal:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  apport-unpack crashes when trying to unpack a crash

  [Test Case]
  On a system running 20.04 LTS:
  1) create an additional user who is only a member of their own group e.g.
  bdmurray@clean-focal-amd64:~$ id crashy
  uid=1001(crashy) gid=1001(crashy) groups=1001(crashy)
  2) Launch a process as that user
  3) kill -11 that process
  4) Confirm there is a crash file in /var/crash for that process
  5) Run apport-unpack on that .crash file

  With the version of apport from -proposed you will not get another
  crash file when unpacking the crash file.

  [Regression Potential]
  We are just setting UserGroups to 'N/A' as opposed to having it be completely 
empty so there isn't any chance for regression.

  When running apport-unpack to get at a core dump

  laney@raleigh> sudo apport-unpack 
_usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz
  [sudo] password for laney:
  Traceback (most recent call last):
    File "/usr/bin/apport-unpack", line 73, in 
  pr.extract_keys(f, bin_keys, dir)
    File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in 
extract_keys
  [item for item, element in b64_block.items() if element is False])
  ValueError: ['UserGroups'] has no binary content
  laney@raleigh> apport-cli --version
  2.16.2

  It's not terrible, because most files are unpacked (those which sort
  before UserGroups, I guess).

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: apport 2.16.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportLog:

  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 10:09:26 2015
  InstallationDate: Installed on 2012-10-07 (876 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1893686] Re: [nvidia] Some apps are partially transparent/corrupt

[Gavin Haslett]

I have not had the same issue with Chromium, but I suspect you might be
right and it's still related. Any thoughts right now on when 450 reaches
official?

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

Title:
  [nvidia] Some apps are partially transparent/corrupt

Status in gtk+3.0 package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  NVidia drivers in Ubuntu 20.04 show corruption in certain
  applications. Most egregious bug appears to be "Ubuntu Software
  Center" which is almost completely transparent and unusable.

  Also see occasional corruption in window decorations in other apps,
  namely Gnome Tweaks as a prime example.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 31 13:33:16 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: Dell UHD Graphics 630 (Desktop 9 Series) [1028:08f7]
   NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU104 [GeForce RTX 2080 Rev. A] [1028:3729]
  InstallationDate: Installed on 2020-06-25 (67 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Alienware Alienware Aurora R8
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=c80a6058-31c8-4117-a747-3193e765eff9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.12
  dmi.board.name: 02XRCM
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.12:bd02/20/2020:svnAlienware:pnAlienwareAuroraR8:pvr1.0.12:rvnAlienware:rn02XRCM:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R8
  dmi.product.sku: 08F7
  dmi.product.version: 1.0.12
  dmi.sys.vendor: Alienware
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1893686/+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 1798369] Re: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock"

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~brian-murray/ubiquity/+git/ubiquity/+merge/390185

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

Title:
  Reinstall Ubuntu (with preserving existing data) shows error message
  due to "Could not get lock /target/var/cache/apt/archives/lock"

Status in APT:
  New
Status in ubiquity:
  New
Status in apt package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Confirmed
Status in apt source package in Eoan:
  Invalid
Status in ubiquity source package in Eoan:
  Won't Fix

Bug description:
  When trying to reinstall an existing Ubuntu cosmic installation using
  latest 18.10 desktop images, the install shows an error dialog around
  the end of the installation with an "Error restoring installed
  applications". Looking at the syslog such a traceback can be seen:

  apt_pkg.Error: E:Could not get lock
  /target/var/cache/apt/archives/lock - open (11: Resource temporarily
  unavailable), E:Unable to lock directory
  /target/var/cache/apt/archives/

  After reproducing this on a live session, after chrooting into /target
  indeed any apt-get install operations result in the same lock-file
  error. The whole syslog of the reinstall attached to the bug.

  Test case:
   * Download latest cosmic image
   * Install cosmic on the whole disk (can be on a VM)
   * (optional) Boot into the system and leave a file in the home directory (to 
leave a trace, just in case)
   * Reboot and install cosmic using the first option in ubiquity: Reinstall 
Ubuntu
   * Finish configuration

  The install itself doesn't fail, but around the end of the
  installation process the error dialog appears. System is still
  bootable but left with old packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1798369/+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 1273258] Re: Hundreds of dbus-daemon processes

[Diego Machado Dias]

I have the same bug: a number of /usr/bin/dbus-deamon processes which
spawn from "/sbin/init splash".

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

Title:
  Hundreds of dbus-daemon processes

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  I find a growing number of root owned dbus-daemon processes.
  Eventually, this results in a 'too many processes' error preventing something 
to fork, e.g. a login.

  They get created by batches of 4, every 30 minutes on my box.
  My box is a puppet client, so that these 30 minutes are not in a local cron 
tab.
  The pids are 11 units apart (when the box is otherwise idle).
  The command line is:
  //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session

  ~# ps -fu root | grep dbus-daemon | grep -v grep | tail -8
  root 17509 1  0 11:25 ?00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root 17520 1  0 11:25 ?00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root 17531 1  0 11:25 ?00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root 17542 1  0 11:25 ?00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root 17972 1  0 11:55 ?00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root 17983 1  0 11:55 ?00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root 17994 1  0 11:55 ?00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session
  root 18005 1  0 11:55 ?00:00:00 //bin/dbus-daemon --fork 
--print-pid 4 --print-address 6 --session

  I reported this first to https://bugs.freedesktop.org/show_bug.cgi?id=74114
  and was told to report it to ubuntu instead.
  Here were some additional comments:

  The symptoms you described probably mean that something running as
  root is either running /usr/bin/dbus-launch, or attempting to access a
  D-Bus session via the autolaunch: transport while under a transient
  X11 session, 4 times every 30 minutes.

  If this machine does not intentionally run an X11 GUI or a D-Bus
  session, uninstalling the dbus-x11 package or making /usr/bin/dbus-
  launch non-executable might work around this. Don't do that if you use
  an X11 GUI environment, though.

  Since 1.4.8, dbus autolaunch has only been effective when DISPLAY is
  set and non-empty, so if this is autolaunch, an X11 session must be
  involved somehow.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: dbus 1.4.18-1ubuntu1.4
  ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53
  Uname: Linux 3.2.0-58-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Jan 27 14:51:19 2014
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1273258/+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 1800012] Re: ogg vorbis corruption

[Fidel Ramos]

Is there a timeline for when the fix for Focal will be released? I have
corrupted half my music collection due to this bug, good thing I had a
backup.

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

Title:
  ogg vorbis corruption

Status in TagLib:
  Fix Released
Status in taglib package in Ubuntu:
  Fix Released
Status in taglib source package in Bionic:
  Confirmed
Status in taglib source package in Eoan:
  Won't Fix
Status in taglib source package in Focal:
  In Progress
Status in taglib source package in Groovy:
  Fix Released
Status in taglib package in Debian:
  Fix Released

Bug description:
  [Impact]

  TagLib 1.11.1 corrupts ogg vorbis files. The proposed uploads fix the
  problem.

  [Test Case]

  
  [Regression Potential]

  
  [Original description]

  TagLib 1.11.1 corrupts ogg vorbis files. See
  https://github.com/taglib/taglib/issues/775 It would be good to apply
  attached patch for released distributions.

  See upstream bugs for more details:
  https://github.com/taglib/taglib/issues/775
  https://github.com/taglib/taglib/issues/864

To manage notifications about this bug go to:
https://bugs.launchpad.net/taglib/+bug/1800012/+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 1888352] Re: use builtin dump_acpi_tables.py in hookutils

[Brian Murray]

I've uploaded this to the focal SRU queue for review by an SRU team
member.

** Also affects: apport (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: apport (Ubuntu Focal)
   Status: New => In Progress

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

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  In Progress
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+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 1893899] Re: update alsa/audio realted infomation collection code in apport

[Brian Murray]

** Tags added: rls-gg-incoming

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

Title:
  update alsa/audio realted infomation collection code in apport

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

Bug description:
  what need to change

  1. try to use /usr/sbin/alsa-info before try 
/usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info 
co-exists, but anyway)
  2. add pa-info (exist after focal)
  3. add ucm2 directory. (exist after focal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893899/+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 1887186] Re: Please switch to nftables as the default backend

[Oibaf]

Can you please merge 1.8.5 from Debian along switching to -nft?
1.8.4 still has some bugs with -nft, which are fixed in 1.8.5.
Thanks

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

Title:
  Please switch to nftables as the default backend

Status in iptables package in Ubuntu:
  Confirmed

Bug description:
  The iptables package in Ubuntu already made the switch but it was
  reverted in LP: #1843468 due to breaking reverse dependencies and
  software not packaged in the Ubuntu Archive.

  The switch of the default backend is also a preparation for making the
  nftables frontend to be the preferred tool for interfacing the
  Netfilter framework, thus please Recommend: it.

  Inclusion of the nftables package in main is traced at LP: #1887187.

  I've prepared a Bileto ticket for staging and testing the packages which need 
to be changed:
  https://bileto.ubuntu.com/#/ticket/4044

  The updated package break any package or project, please mark them
  affected and/or leave a commend in this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1887186/+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 1893958] Re: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend

[Oibaf]

Can you please merge 1.8.5 from Debian along switching to -nft?
1.8.4 still has some bugs with -nft, which are fixed in 1.8.5.
Thanks

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

Title:
  [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables
  backend

Status in iptables package in Ubuntu:
  New

Bug description:
  The change is a planned change for this development cycle and the fix
  has been tested as described in LP: #1887186 and
  https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html
  .

  
  Changes:
   iptables (1.8.4-3ubuntu3) groovy; urgency=medium
   .
 * Swap alternative priority and prefer nftables backend over legacy
   (LP: #1887186)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1893958/+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 1893686] Re: [nvidia] Some apps are partially transparent/corrupt

[Gavin Haslett]

Thanks, Daniel... I don't know as I run Firefox rather than Chromium.
Let me fire it up and play with it for a day or two and see if I get the
same issue. Thanks!

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

Title:
  [nvidia] Some apps are partially transparent/corrupt

Status in gtk+3.0 package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  NVidia drivers in Ubuntu 20.04 show corruption in certain
  applications. Most egregious bug appears to be "Ubuntu Software
  Center" which is almost completely transparent and unusable.

  Also see occasional corruption in window decorations in other apps,
  namely Gnome Tweaks as a prime example.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 31 13:33:16 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: Dell UHD Graphics 630 (Desktop 9 Series) [1028:08f7]
   NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU104 [GeForce RTX 2080 Rev. A] [1028:3729]
  InstallationDate: Installed on 2020-06-25 (67 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Alienware Alienware Aurora R8
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=c80a6058-31c8-4117-a747-3193e765eff9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.12
  dmi.board.name: 02XRCM
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.12:bd02/20/2020:svnAlienware:pnAlienwareAuroraR8:pvr1.0.12:rvnAlienware:rn02XRCM:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R8
  dmi.product.sku: 08F7
  dmi.product.version: 1.0.12
  dmi.sys.vendor: Alienware
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1893686/+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 1893969] [NEW] Screen corruption and delayed update using onboard Intel video

[Ethan Blanton]

Public bug reported:

I frequently get screen corruption or delayed screen updates using
onboard Intel video (i7-10710U in a Dell XPS 13 7390).  I am attaching a
screen shot of an example of this in Emacs, where you can see echoes of
past cursor locations (center right side of screen, the highlighted word
"boolean").

A frequent failure is that an application updates its window, but the
updates do not appear on screen until I take some action to disturb the
window (move or resize it, change focus, change desktops, etc.), after
which it cleans itself up.  Small changes (such as selecting text) will
often clean up the image where the change is made without repainting the
entire window.

My display panel is 4K UHD+, and I have attached two external Full HD
DisplayPort monitors using chaining with 2x2 scale using XrandR.  This
corruption appears to happen on all three surfaces.  The configuration
for my desktop is:

HIX=3840
HIY=2160
HI=${HIX}x${HIY}
xrandr --fb $(($HIX * 3))x$HIY \
   --output eDP-1 --auto --panning ${HI}+$(($HIX * 2))+0 \
   --output DP-2-8 --auto --panning ${HI}+$HIX+0 \
   --scale-from $HI --left-of eDP-1 --scale 2x2 \
   --output DP-2-1 --auto --panning $HI+0+0 \
   --scale-from $HI --left-of DP-2-8 --scale 2x2

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop:
 
Date: Wed Sep  2 11:48:03 2020
DistUpgraded: 2020-06-21 15:36:52,619 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-42-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0962]
MachineType: Dell Inc. XPS 13 7390
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=UUID=aeb9197c-491f-493d-9a7a-7094efd5023c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-06-21 (72 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0377MH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390
dmi.product.sku: 0962
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal ubuntu

** Attachment added: "corruption.png"
   
https://bugs.launchpad.net/bugs/1893969/+attachment/5407026/+files/corruption.png

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

Title:
  Screen corruption and delayed update using onboard Intel video

Status in xorg package in Ubuntu:
  New

Bug description:
  I frequently get screen corruption or delayed screen updates using
  onboard Intel video (i7-10710U in a Dell XPS 13 7390).  I am attaching
  a screen shot of an example of this in Emacs, where you can see echoes
  of past cursor locations (center right side of screen, the highlighted
  word "boolean").

  A frequent failure is that an application updates its window, but the
  updates do not appear on screen until I take some action to disturb
  the window (move or resize it, change focus, change desktops, etc.),
  after which it cleans itself up.  Small changes (such as selecting
  text) will often clean up the image where the change is made without
  repainting the entire window.

  My display panel is 4K UHD+, and I have attached two external Full HD
  DisplayPort monitors using chaining with 2x2 scale using XrandR.  This
  corruption appears to happen on all three surfaces.  The configuration
  for my desktop is:

  HIX=3840
  HIY=2160
  HI=${HIX}x${HIY}
  xrandr --fb $(($HIX * 3))x$HIY \
 --output eDP-1 --auto --panning ${HI}+$(($HIX * 2))+0 \
 --output DP-2-8 --auto --panning ${HI}+$HIX+0 \
  

[Touch-packages] [Bug 1893967] [NEW] After reboot/power up, even if headphones are connected, the selected output are the speakers

[Luca De Cave]

Public bug reported:

The bug is little: after power up/reboot the selected output for audio are 
always the speakers, even if the headphones are connected. 
Audio works as supposed, I have just to switch from speakers to headphones in 
the audio panel inside the settings page if I have headphones plugged in. 

My system is an upgrade from Ubuntu 16.04 LTS (now 18.04 LTS)

uname -a output
Linux muletto 5.4.0-45-generic #49~18.04.2-Ubuntu SMP Wed Aug 26 16:29:02 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -rd output
Description:Ubuntu 18.04.5 LTS
Release:18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-45.49~18.04.2-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  muletto5653 F pulseaudio
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Wed Sep  2 17:37:39 2020
InstallationDate: Installed on 2016-09-04 (1459 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Audio interno - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [Inspiron 5570, Realtek ALC3246, Black Headphone Out, Front] Playback 
problem
UpgradeStatus: Upgraded to bionic on 2018-08-21 (742 days ago)
dmi.bios.date: 08/15/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.8
dmi.board.name: 09YTN7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.8:bd08/15/2018:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  After reboot/power up, even if headphones are connected, the selected
  output are the speakers

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The bug is little: after power up/reboot the selected output for audio are 
always the speakers, even if the headphones are connected. 
  Audio works as supposed, I have just to switch from speakers to headphones in 
the audio panel inside the settings page if I have headphones plugged in. 

  My system is an upgrade from Ubuntu 16.04 LTS (now 18.04 LTS)

  uname -a output
  Linux muletto 5.4.0-45-generic #49~18.04.2-Ubuntu SMP Wed Aug 26 16:29:02 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -rd output
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-45.49~18.04.2-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  muletto5653 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Wed Sep  2 17:37:39 2020
  InstallationDate: Installed on 2016-09-04 (1459 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio interno - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [Inspiron 5570, Realtek ALC3246, Black Headphone Out, Front] Playback 
problem
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (742 days ago)
  dmi.bios.date: 08/15/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.8
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.8:bd08/15/2018:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

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

-- 

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

[Michael Neuffer]

I also had to purge apport in order to get this under control.

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

Title:
  systemd 100% cpu usage apport-autoreport.service: Failed with result
  'start-limit-hit'

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  after upgrade from Ubuntu 20.04 to 20.10  
  seeing systemd use 100% cpu forever


  top

top - 10:16:19 up 20 min,  1 user,  load average: 3.91, 4.28, 3.39
Tasks: 332 total,   2 running, 330 sleeping,   0 stopped,   0 zombie
%Cpu(s): 18.7 us,  6.4 sy, 11.9 ni, 62.2 id,  0.0 wa,  0.0 hi,  0.8 si, 
 0.0 st
MiB Mem :  15917.6 total,   8553.4 free,   2604.3 used,   4759.9 
buff/cache
MiB Swap:   2048.0 total,   2048.0 free,  0.0 used.  12633.7 avail 
Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND  
  1 root  20   0  177316  12252   8684 R 100.0   0.1  15:01.25 
systemd  
   4636 kush  39  19  633796 176152  16360 S  98.3   1.1  17:51.56 
tracker-miner-f  
820 message+  20   0   10740   6452   4212 S  39.8   0.0   6:19.06 
dbus-daemon  
316 root  19  -1  535916 322896 320824 S  15.3   2.0   3:16.41 
systemd-journal  
844 syslog20   0  221136   5840   3920 S  13.6   0.0   2:14.52 
rsyslogd 
858 root  20   0   83708  74124   7568 S  12.7   0.5   2:06.98 
systemd-logind   
  5 root  20   0   0  0  0 I   3.4   0.0   0:05.01 
kworker/0:0-events   
  35566 kush  20   0 3850088 588344 262192 S   2.5   3.6   0:30.48 
MainThread   
   5626 kush  20   0 5004788 260876  93400 S   1.7   1.6   3:05.19 
gnome-shell  
   7033 kush  20   0  869792  66440  44272 S   1.7   0.4   0:06.05 
gnome-terminal-  
  36790 kush  20   0 2525432 156636  98568 S   1.7   1.0   0:04.99 
Web Content  
957 root  20   0 1556196  45044  24284 S   0.8   0.3   0:02.48 
containerd   
   1038 root  20   0   10460   4412   3300 S   0.8   0.0   0:00.16 
fancontrol   



  
sudo tail -n 100 /var/log/syslog
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.

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

[Eric Desrochers]

[sts-sponsor]

Sponsored in Focal/Bionic.

Thanks for your contribution.

-- 
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:
  In Progress
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:
  In Progress
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:
  In Progress
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  In Progress
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 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

[Dimitri John Ledkov]

** Description changed:

  [Impact]
  
   * update-initramfs -u fails on arm64 m6g instances in AWS
  
  [Test Case]
  
   * launch m6g instance in AWS
   * install libc6-lse (if not installed)
   * run $ update-initramfs -u
   * It should suceed
+  * It should contain pthread, and libgcc_s libraries
  
  [Regression Potential]
  
   * Adding one more path to libgcc_s1 resolution. This will still fail if
  something compiles libc6 for _two_ optimisations like
  /lib/$arch/foo/bar/libpthread.
  
  [Other Info]
  
   * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in
  the initrd libgcc_s1 must be copied in too. However the logic to find
  matching libgcc_s1 is broken for optimizied builds of libc6 without
  optimized build of libgcc_s1. I think libpthread should link against
  libgcc_s1 to prevent these issues.
  
   * Original bug report
  
  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:
  
  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.
  
  ## Steps to reproduce (on AWS)
  
  ### With focal 20200423 AMI
  
  1. Find the following AMI and launch on m6g instance family
  
     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423
  
  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u
  
  ### With focal 20200522 AMI
  
  1. Find the following AMI and launch on m6g instance family
  
     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522
  
  2. Try: sudo update-initramfs -u
  
  ## Note
  
  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.
  
  ## Expected behavior
  
  Does not fail.
  
  ## Background to find this bug
  
  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get upgrade
  pulls newer package that triggers update-initramfs, apt-get upgrade
  always fail on 20200522 AMI.
  
  the following is an apport report on 20200423 AMI:
  
  
  
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
   gcc-10-base 10-20200411-0ubuntu1
   libc6 2.31-0ubuntu9
   libcrypt1 1:4.4.10-10ubuntu4
   libgcc-s1 10-20200411-0ubuntu1
   libidn2-0 2.2.0-2
   libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
   processor  : 0
   BogoMIPS   : 243.75
   Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
   CPU implementer: 0x41
   CPU architecture: 8
   CPU variant: 0x3
   CPU part   : 0xd0c
   CPU revision   : 1
  ProcEnviron:
   LANG=C.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: New => In Progress

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

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

Status in cloud-images:
  New
Status in btrfs-progs package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in btrfs-progs source package in Bionic:
  Invalid
Status in glibc source package in Bionic:
  Invalid
Status in initramfs-tools source package in Bionic:
  In Progress
Status in btrfs-progs source package in Focal:
  Invalid
Status in glibc source package in Focal:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * update-initramfs -u fails on arm64 m6g instances in AWS

  [Test Case]

   * launch m6g instance in AWS
   * install libc6-lse (if not installed)
   * run $ update-initramfs -u
   * It should suceed
   * It should contain pthread, and libgcc_s libraries

  [Regression Potential]

   * Adding one more path to libgcc_s1 resolution. This will still fail
  if something compiles libc6 for _two_ optimisations like
  

[Touch-packages] [Bug 1893958] [NEW] [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend

[Balint Reczey]

Public bug reported:

The change is a planned change for this development cycle and the fix
has been tested as described in LP: #1887186 and
https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html .


Changes:
 iptables (1.8.4-3ubuntu3) groovy; urgency=medium
 .
   * Swap alternative priority and prefer nftables backend over legacy
 (LP: #1887186)

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

** Attachment added: "iptables_1.8.4-3ubuntu3.diff"
   
https://bugs.launchpad.net/bugs/1893958/+attachment/5407008/+files/iptables_1.8.4-3ubuntu3.diff

** Description changed:

  The change is a planned change for this development cycle and the fix
  has been tested as described in LP: #1887186 and
  https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html .
+ 
+ 
+ Changes:
+  iptables (1.8.4-3ubuntu3) groovy; urgency=medium
+  .
+* Swap alternative priority and prefer nftables backend over legacy
+  (LP: #1887186)

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

Title:
  [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables
  backend

Status in iptables package in Ubuntu:
  New

Bug description:
  The change is a planned change for this development cycle and the fix
  has been tested as described in LP: #1887186 and
  https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html
  .

  
  Changes:
   iptables (1.8.4-3ubuntu3) groovy; urgency=medium
   .
 * Swap alternative priority and prefer nftables backend over legacy
   (LP: #1887186)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1893958/+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 1887186] Re: Please switch to nftables as the default backend

[Balint Reczey]

FFe: LP: #1893958

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

Title:
  Please switch to nftables as the default backend

Status in iptables package in Ubuntu:
  Confirmed

Bug description:
  The iptables package in Ubuntu already made the switch but it was
  reverted in LP: #1843468 due to breaking reverse dependencies and
  software not packaged in the Ubuntu Archive.

  The switch of the default backend is also a preparation for making the
  nftables frontend to be the preferred tool for interfacing the
  Netfilter framework, thus please Recommend: it.

  Inclusion of the nftables package in main is traced at LP: #1887187.

  I've prepared a Bileto ticket for staging and testing the packages which need 
to be changed:
  https://bileto.ubuntu.com/#/ticket/4044

  The updated package break any package or project, please mark them
  affected and/or leave a commend in this bug.

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

[Eric Desrochers]

[sts-sponsor]

Sponsored in Focal/Bionic.

Thanks for your contribution.

-- 
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:
  In Progress
Status in initramfs-tools source package in Bionic:
  In Progress
Status in initramfs-tools source package in Eoan:
  Won't Fix
Status in initramfs-tools source package in Focal:
  In Progress
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 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces

[Eric Desrochers]

[sts-sponsor]

Sponsored in Bionic.

Thanks for your contribution.

-- 
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:
  In Progress
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 1893952] [NEW] very long boot/log in with log in window upper left corner?

[Fritz Hudnut]

Public bug reported:

Been having problems with my installation of 20.10 U-MATE . . . reported
here earlier to little fanfare . . . but the issues with very slow boot
times, and then when finally arriving at GUI log in window, the log in
"tray" is positioned upper left corner of the display and it's like a
TTY, where it wants user name and then password.  I think today it
literally took 5 minutes to get logged into the GUI . . . .

As reported previously I have an install of Lu 20.10 in the same drive .
. . so far is not having the same problems that U-MATE is having . . . .

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: MATE
Date: Wed Sep  2 07:28:33 2020
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
DkmsStatus: broadcom-sta, 6.30.223.271, 5.4.0-42-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK110 [GeForce GTX 780] [10de:1004] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GK110 [GeForce GTX 780] [3842:0781]
InstallationDate: Installed on 2020-01-20 (226 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119)
MachineType: Apple Inc. MacPro5,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=e795b2e6-5bef-4a6e-9217-539a6debda90 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/30/2018
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 138.0.0.0.0
dmi.board.asset.tag: 0
dmi.board.name: Mac-F221BEC8
dmi.board.vendor: Apple Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F221BEC8
dmi.modalias: 
dmi:bvnAppleInc.:bvr138.0.0.0.0:bd07/30/2018:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8:
dmi.product.family: MacPro
dmi.product.name: MacPro5,1
dmi.product.sku: System SKU#
dmi.product.version: 0.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.5-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug groovy third-party-packages 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/1893952

Title:
  very long boot/log in with log in window upper left corner?

Status in xorg package in Ubuntu:
  New

Bug description:
  Been having problems with my installation of 20.10 U-MATE . . .
  reported here earlier to little fanfare . . . but the issues with very
  slow boot times, and then when finally arriving at GUI log in window,
  the log in "tray" is positioned upper left corner of the display and
  it's like a TTY, where it wants user name and then password.  I think
  today it literally took 5 minutes to get logged into the GUI . . . .

  As reported previously I have an install of Lu 20.10 in the same drive
  . . . so far is not having the same problems that U-MATE is having . .
  . .

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Wed Sep  2 07:28:33 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus: broadcom-sta, 6.30.223.271, 5.4.0-42-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK110 [GeForce GTX 780] [10de:1004] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK110 [GeForce GTX 780] [3842:0781]
  InstallationDate: Installed on 2020-01-20 (226 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200119)
  MachineType: Apple Inc. MacPro5,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 

[Touch-packages] [Bug 1891316] Re: duplicate "progname" under gcc-10

[Francis Ginther]

** Tags added: id-5f35085ec297bd359765109f

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

Title:
  duplicate "progname" under gcc-10

Status in kbd package in Ubuntu:
  Fix Released

Bug description:
  Under gcc-10's linker an error occurs wherein "progname" appears to be
  included from multiple locations (as it's defined in version.h rather
  than merely declared).

  A trivial patch is available from the following branch:

  https://code.launchpad.net/~waveform/ubuntu/+source/kbd/+git/kbd/+ref
  /fix-duplicate-progname

  With test builds in the following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/kbd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1891316/+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 1891716] Re: Networking broken after systemd update

[Francis Ginther]

** Tags added: id-5f3afdc64e09838ff1afe222

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

Title:
  Networking broken after systemd update

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd package in Debian:
  Unknown

Bug description:
  # Description:

  After this upgrade in groovy, networking stopped working:

  Start-Date: 2020-08-14  17:02:50
  Commandline: apt-get dist-upgrade --assume-yes
  Requested-By: ubuntu (1000)
  Install: motd-news-config:amd64 (11ubuntu11, automatic)
  Upgrade: libaudit-common:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), 
alsa-ucm-conf:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), libmpfr6:amd64 
(4.0.2-1build1, 4.1.0-3), python3-software-properties:amd64 (0.98.10, 0.99.2), 
cloud-initramfs-dyn-netconf:amd64 (0.45ubuntu1, 0.46ubuntu1), libsystemd0:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libpam-cap:amd64 (1:2.36-1, 1:2.42-2), 
libgmp10:amd64 (2:6.2.0+dfsg-6, 2:6.2.0+dfsg-6ubuntu1), ubuntu-standard:amd64 
(1.452, 1.453), nano:amd64 (4.9.3-1, 5.1-1), udev:amd64 (245.7-1ubuntu1, 
246-2ubuntu1), ubuntu-server:amd64 (1.452, 1.453), libpipeline1:amd64 
(1.5.2-2build1, 1.5.3-1), isc-dhcp-common:amd64 (4.4.1-2.1ubuntu6, 
4.4.1-2.1ubuntu9), libudev1:amd64 (245.7-1ubuntu1, 246-2ubuntu1), 
systemd-timesyncd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-minimal:amd64 
(1.452, 1.453), libcap2:amd64 (1:2.36-1, 1:2.42-2), systemd-sysv:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libcap2-bin:amd64 (1:2.36-1, 1:2.42-2), 
libpam-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd:amd64 
(245.7-1ubuntu1, 246-2ubuntu1), libnss-systemd:amd64 (245.7-1ubuntu1, 
246-2ubuntu1), ethtool:amd64 (1:5.4-1, 1:5.8-1), overlayroot:amd64 
(0.45ubuntu1, 0.46ubuntu1), cloud-initramfs-copymods:amd64 (0.45ubuntu1, 
0.46ubuntu1), isc-dhcp-client:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), 
libaudit1:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), base-files:amd64 
(11ubuntu10, 11ubuntu11), software-properties-common:amd64 (0.98.10, 0.99.2)
  End-Date: 2020-08-14  17:03:10

  # Reproduction steps:

  $ multipass launch --name groovy-update-test daily:groovy
  $ multipass connect groovy-update-test
  # connected to VM
  $ sudo apt-get update && sudo apt-get dist-upgrade --assume-yes
  # works fine
  $ sudo apt-get update
  Err:1 http://security.ubuntu.com/ubuntu groovy-security InRelease
    Temporary failure resolving 'security.ubuntu.com'
  Err:2 http://archive.ubuntu.com/ubuntu groovy InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Err:3 http://archive.ubuntu.com/ubuntu groovy-updates InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Err:4 http://archive.ubuntu.com/ubuntu groovy-backports InRelease
    Temporary failure resolving 'archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/groovy-updates/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/groovy-backports/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/groovy-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  $ sudo systemctl list-units --failed
    UNIT LOAD   ACTIVE SUBDESCRIPTION
  ● systemd-networkd.service loaded failed failed Network Service
  ● systemd-networkd.socket  loaded failed failed Network Service Netlink Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  2 loaded units listed.
  $ systemctl status systemd-networkd.service
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-08-14 17:03:01 EDT; 
12min ago
  TriggeredBy: ● systemd-networkd.socket
 Docs: man:systemd-networkd.service(8)
 Main PID: 2745 (code=exited, status=1/FAILURE)

  Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Main 
process exited, code=exited, status=1/FAILURE
  Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: 
Failed with result 'exit-code'.
  Aug 14 17:03:01 fulfilling-hornet systemd[1]: Failed to start Network Service.
  Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: 
Scheduled restart job, restart counter is at 5.
  Aug 14 17:03:01 fulfilling-hornet systemd[1]: Stopped Network Service.
  Aug 14 17:03:01 fulfilling-hornet 

[Touch-packages] [Bug 1870088] Re: xz-utils ftbfs in focal

[Francis Ginther]

** Tags added: id-5f358382ed1710839c11231c

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

Title:
  xz-utils ftbfs in focal

Status in xz-utils package in Ubuntu:
  Fix Released
Status in xz-utils source package in Focal:
  Fix Released
Status in xz-utils package in Debian:
  New

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz

  dh build --parallel 
  make[2]: Leaving directory '/<>'
 dh_testroot -O--parallel
 dh_prep -O--parallel
 debian/rules override_dh_auto_install
  make[2]: Entering directory '/<>'
  dh_auto_install --builddirectory debian/xzdec-build
  dh_auto_install --builddirectory debian/normal-build
  dh_auto_install --builddirectory debian/static-build
  set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \
  install -d debian/tmp/lib/$arch; \
  mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \
  dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \
  ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so
  mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such 
file or directory
  make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [debian/rules:4: install] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:4: binary] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+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 1886886] Re: Plymouth 0.9.5 release

[Francis Ginther]

** Tags added: id-5f2c24768341188658b45297

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

Title:
  Plymouth 0.9.5 release

Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Plymouth 0.9.5 release:

  https://www.freedesktop.org/software/plymouth/releases/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1886886/+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 1627564] Re: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades)

[Francis Ginther]

** Tags added: id-5f3eab1b0d119251fb17b47e

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

Title:
  Debconf crash due to assertion failure in ensure_surface_for_gicon
  [gtkiconhelper.c:493] (when png loader is missing/during upgrades)

Status in debconf package in Ubuntu:
  Confirmed
Status in debconf source package in Focal:
  New

Bug description:
  https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689
  https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383

  ---

  bubble opened up indicating there was a failure during the latest
  update.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.4.0-9136-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  Date: Sun Sep 25 20:37:06 2016
  ExecutablePath: /usr/sbin/lightdm-gtk-greeter
  InstallationDate: Installed on 2016-08-04 (52 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
  ProcCmdline: /usr/sbin/lightdm-gtk-greeter
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: lightdm-gtk-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
   [greeter]
   theme-name = Lubuntu-dark-panel
  mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 
2016-08-14T22:33:57.293011

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1627564/+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 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]

[Francis Ginther]

** Tags added: id-5f47d293daee608106fb4eb5

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

Title:
  isc-dhcp-server crashing constantly [Ubuntu 20.04]

Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in isc-dhcp source package in Focal:
  New

Bug description:
  isc-dhcp-server crashing constantly (sometimes within seconds or minutes, 
sometimes within hours) with the following error messages:
  Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service.
  Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ??
  Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ??
  Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ??
  Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ??
  Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ??
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+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 1891486] Re: vim ftbfs in focal (armhf, ppc64el)

[Francis Ginther]

** Tags added: id-5f35848d1ba9e31606c5359b

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

Title:
  vim ftbfs in focal (armhf, ppc64el)

Status in vim package in Ubuntu:
  Confirmed
Status in vim source package in Focal:
  New

Bug description:
  seen in a focal test rebuild:
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801040
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801038

  ---
  Executed:  2257 Tests
   Skipped:31 Tests
FAILED: 1 Tests

  
  Failures: 
From test_debugger.vim:
Found errors in Test_Debugger():
function 
RunTheTest[40]..Test_Debugger[157]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..59
 line 1: Expected 'No breakpoints defined' but got 'cmd: echo Foo()'
function 
RunTheTest[40]..Test_Debugger[185]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..71
 line 1: Expected '19' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[188]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..72
 line 1: Expected 'E161: Breakpoint not found: 2' but got '~\[  occurs 74 
times]'
function 
RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..73
 line 1: Expected 'Entering Debug mode.  Type "cont" to continue.' but got '~\[ 
 occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..74
 line 1: Expected 'function Bazz' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..75
 line 1: Expected 'line 2: let var1 = 3 + a:var' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..76
 line 1: Expected '  3  func Bazz  line 2' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..77
 line 1: Expected '  4  expr var3' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..78
 line 1: Expected 'Breakpoint in "Bazz" line 5' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..79
 line 1: Expected 'Oldval = "''another var''"' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..80
 line 1: Expected 'Newval = "''value2''"' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..81
 line 1: Expected 'function Bazz' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..82
 line 1: Expected 'line 5: catch' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[208]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..83
 line 1: Expected 'No breakpoints defined' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..84
 line 1: Expected 'Error detected while processing function Bazz:' but got '~\[ 
 occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..85
 line 1: Expected 'line5:' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..86
 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[215]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..87
 line 1: Expected 'E475: Invalid argument: func' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[216]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..88
 line 1: Expected 'E475: Invalid argument: func 2' but got '~\[  occurs 74 
times]'
function 
RunTheTest[40]..Test_Debugger[217]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..89
 line 1: Expected 'E475: Invalid argument: func a()' but got '~\[  occurs 74 
times]'
function 
RunTheTest[40]..Test_Debugger[218]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..90
 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[219]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..91
 line 1: Expected 'E475: Invalid argument: func' but got '~\[  occurs 74 times]'
function 
RunTheTest[40]..Test_Debugger[220]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..92
 

[Touch-packages] [Bug 1893170] Re: [Ubuntu 20.10] zlib: DFLTCC compression level switching issues

[Francis Ginther]

** Tags added: id-5f47e13db3cb5759fc5c5d2f

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

Title:
  [Ubuntu 20.10] zlib: DFLTCC compression level switching issues

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  New
Status in zlib source package in Focal:
  New
Status in zlib source package in Groovy:
  New

Bug description:
  Description:   zlib: DFLTCC compression level switching issues
  Symptom:   Switching compression levels corrupts data
  Problem:   Hardware and software compression states become desynchronized.
  Solution:  Improve compression state synchronization. Since zlib project
 does not accept patches at the moment, the fix has been
 integrated into the DFLTCC pull request:
 https://github.com/madler/zlib/pull/410
 The commitid is 992a7afc3edfa511dff0650d1c545b11bf64e655.
  Reproduction:  Not possible with popular command line tools. The issues were
 discovered using example_call_fuzzer from:
 https://github.com/iii-i/zlib-ng/tree/fuzz/test/fuzz/

  This needs also be applied against 20.04 !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893170/+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 1893925] [NEW] WF-SP800N Bluetooth ear pods not detected as sound device

[Robert Collins]

Public bug reported:

They seem to pair ok, but don't show up as sound hardware, either
microphone or speaker/headphones.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  robertc3384 F pulseaudio
 /dev/snd/pcmC0D0p:   robertc3384 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep  2 22:00:24 2020
InstallationDate: Installed on 2020-07-07 (56 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/08/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.11
dmi.board.name: 0WX9VX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9300
dmi.product.sku: 096D
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  WF-SP800N Bluetooth ear pods not detected as sound device

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  They seem to pair ok, but don't show up as sound hardware, either
  microphone or speaker/headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robertc3384 F pulseaudio
   /dev/snd/pcmC0D0p:   robertc3384 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  2 22:00:24 2020
  InstallationDate: Installed on 2020-07-07 (56 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.11
  dmi.board.name: 0WX9VX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893925/+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 1893655] Re: Headphones connect but don't appear in the audio devices list

[Daniel van Vugt]

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

** Summary changed:

- Headphones connect but don't appear in the audio devices list
+ Sony WH-1000XM3 headphones connect but don't appear in the audio devices list

** Also affects: bluez (Ubuntu)
   Importance: Undecided
   Status: 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/1893655

Title:
  Sony WH-1000XM3 headphones connect but don't appear in the audio
  devices list

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1893655/+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 1893655] Re: Headphones connect but don't appear in the audio devices list

[Alistair Cunningham]

I logged out, and logged in again using regular Ubuntu, and the same
happens. When I switch the headphones on, the Bluetooth settings show
the headphones connected for a second or so, then disconnected. They
don't appear in the sounds settings.

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

Title:
  Headphones connect but don't appear in the audio devices list

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1893655/+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 1893899] Re: update alsa/audio realted infomation collection code in apport

[Ubuntu Foundations Team Bug Bot]

The attachment "apport-diff-groovy-audio-info-refinement.patch" seems to
be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff.  If
the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  update alsa/audio realted infomation collection code in apport

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

Bug description:
  what need to change

  1. try to use /usr/sbin/alsa-info before try 
/usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info 
co-exists, but anyway)
  2. add pa-info (exist after focal)
  3. add ucm2 directory. (exist after focal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893899/+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 1886626] Re: after login to gnome with snd_hda_intel 0000:00:1f.3: No response from codec

[killian68]

Problem solved after upgrading to 20.04.01

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

Title:
  after login to gnome with snd_hda_intel :00:1f.3: No response from
  codec

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After login to gnome, login takes an unsual amount of time.
  Goes back to login screen.
  On second login, works normally but audio sliders are not showing correctly. 
After a while, it operates normally.
  Logs are showing a lot of
  snd_hda_intel :00:1f.3: No response from codec, resetting bus:last 
cmd0x20a70500
  +pci::00:1f.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-1063.68-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1063-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  killian68   1816 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  7 08:56:11 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-20190418-59+beaver-osp1+X00
  InstallationDate: Installed on 2020-04-02 (96 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.11
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

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

[Daniel van Vugt]

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

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

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

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

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

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Package changed: xorg-server (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

** Summary changed:

- Xorg crash
+ Crash

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

Title:
  Crash

Status in Ubuntu:
  Incomplete

Bug description:
  Despues de un bloqueo de pantalla, me atentique y el equipo se
  desbloqueo, pero aparecio una ventana que pedia atenticarse para algo
  relacionado con un demonio. En esa ventana no podía introducir la
  contraseña, ni cerrar la ventana. Despues de apagar el equipo, se
  quedo en bucle de inicio de sesión, la contraseña es correcta pero no
  inicia.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  2 09:30:16 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0794]
  InstallationDate: Installed on 2020-04-26 (129 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 15-3568
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=9fb1e369-7f7f-446b-b384-a83cbaf54f9d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.07.00
  dmi.board.name: 0571HJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.07.00:bd02/15/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0571HJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0794
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1893909/+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 1893889] Re: unattended-upgrade of nova-common failure due to conffile prompt

[Balint Reczey]

As I recall the unattended-upgrades package which hit this bug was not
the latest version from bionic-updates. Right?

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Incomplete

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

Title:
  unattended-upgrade of nova-common failure due to conffile prompt

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  unattended-upgrades attempted to upgrade nova from 2:17.0.9-0ubuntu1
  to 2:17.0.10-0ubuntu2.1 (bionic-security), however nova-common
  contains a modified conffile (/etc/nova/nova.conf) which prompts
  during upgrade and leaves apt/dpkg in a permanent error state
  requiring manual intervention. It also prevents other automated apt
  install operations from working while in this state.

  I understand that this conffile prompt is a generally known problem
  and that unattended-upgrades specifically attempts to skip upgrades
  that have such a conffile prompt, however that did not work on this
  case. I am filing this bug to try and identify and resolve the cause
  and this affected multiple systems in an Ubuntu OpenStack deployment.

  rbalint advised that this is very likely a more complex interaction with the 
exact upgrades that were being staged at the time and hence more logs would be 
needed, indeed attempting to reproduce this very simply with a downgrade of 
nova packages to 2:17.0.0-0ubuntu1 results in it being skipped, as expected:
  root@juju-c21ec6-bionic-nova-7:/home/ubuntu# unattended-upgrade
  Package nova-common has conffile prompt and needs to be upgraded manually

  And from the unattended-upgrades log we can see that 179 packages in
  total were scheduled to upgrade together during this run.

  Attaching the following logs files:
  /var/log/unattended-upgrades/*
  /var/log/dpkg*
  dpkg_-l (As at 2020-04-27 16:22, the same time period as the 
unattended-upgrades logs, but the dpkg.log* files were taken later but also 
cover the full time period from before 2019-12-28 and after 2020-04-27).

  The first instance of the failure is in unattended-upgrades.log.4.gz Line 161
  "2019-12-28 06:15:29,837 Packages that will be upgraded: amd64-microcode... 
[truncated, 179 packages total]"

  That relates to the output in unattended-upgrades-dpkg.log.4.gz Line
  791 "Log started: 2019-12-28  06:25:56"

  Which relates to the output of dpkg.log.6.gz Line 392
  "2019-12-28 06:25:56 upgrade nova-compute-kvm:all 2:17.0.9-0ubuntu1 
2:17.0.10-0ubuntu2.1"

  It fails many times after that as anytime you attempt to install a
  package, it attempts to configure nova.conf again and exits with an
  error again. But that is the original failure. But note that various
  package upgrades happened by unattended-upgrades (and possibly other
  sources) in the intervening 4 months and so I guess reproducing the
  situation may require reverse engineering the original package list
  from the dpkg logs. I have not currently attempted to do that with the
  hopes intimate knowledge of the unattended-upgrades code and logs will
  make that process faster.

  A full sosreport from the system is available if more information is
  required that will include other log files, and various other command
  outputs. It is not uploaded initially for privacy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1893889/+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 1893907] Re: Xorg crash

[Daniel van Vugt]

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

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

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

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

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

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Crash

Status in Ubuntu:
  Incomplete

Bug description:
  Me aparecio una ventana pidiendome que me atenticara para algo
  relacionado con un demonio. No me dejaba introducir la contraseña. Al
  final reinicie e equipo y entro en bucle de inicio de sesión.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  2 09:20:43 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04f5]
  InstallationDate: Installed on 2020-02-19 (195 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. OptiPlex 390
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-115-generic 
root=UUID=5420fc93-5321-4f87-9fa0-bdc6fc629763 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0M5DCD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd10/14/2013:svnDellInc.:pnOptiPlex390:pvr01:rvnDellInc.:rn0M5DCD:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 390
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1893907/+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 1893909] [NEW] Xorg crash

[Carlos Barriuso]

Public bug reported:

Despues de un bloqueo de pantalla, me atentique y el equipo se
desbloqueo, pero aparecio una ventana que pedia atenticarse para algo
relacionado con un demonio. En esa ventana no podía introducir la
contraseña, ni cerrar la ventana. Despues de apagar el equipo, se quedo
en bucle de inicio de sesión, la contraseña es correcta pero no inicia.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep  2 09:30:16 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 620 [1028:0794]
InstallationDate: Installed on 2020-04-26 (129 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 15-3568
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=9fb1e369-7f7f-446b-b384-a83cbaf54f9d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.07.00
dmi.board.name: 0571HJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.07.00:bd02/15/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0571HJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 15-3568
dmi.product.sku: 0794
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug crash focal ubuntu

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Despues de un bloqueo de pantalla, me atentique y el equipo se
  desbloqueo, pero aparecio una ventana que pedia atenticarse para algo
  relacionado con un demonio. En esa ventana no podía introducir la
  contraseña, ni cerrar la ventana. Despues de apagar el equipo, se
  quedo en bucle de inicio de sesión, la contraseña es correcta pero no
  inicia.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  2 09:30:16 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0794]
  InstallationDate: Installed on 2020-04-26 (129 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 15-3568
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   

[Touch-packages] [Bug 1893907] [NEW] Xorg crash

[Carlos Barriuso]

Public bug reported:

Me aparecio una ventana pidiendome que me atenticara para algo
relacionado con un demonio. No me dejaba introducir la contraseña. Al
final reinicie e equipo y entro en bucle de inicio de sesión.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
Uname: Linux 4.15.0-115-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep  2 09:20:43 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04f5]
InstallationDate: Installed on 2020-02-19 (195 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. OptiPlex 390
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-115-generic 
root=UUID=5420fc93-5321-4f87-9fa0-bdc6fc629763 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0M5DCD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd10/14/2013:svnDellInc.:pnOptiPlex390:pvr01:rvnDellInc.:rn0M5DCD:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 390
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Me aparecio una ventana pidiendome que me atenticara para algo
  relacionado con un demonio. No me dejaba introducir la contraseña. Al
  final reinicie e equipo y entro en bucle de inicio de sesión.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  2 09:20:43 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04f5]
  InstallationDate: Installed on 2020-02-19 (195 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. OptiPlex 390
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-115-generic 
root=UUID=5420fc93-5321-4f87-9fa0-bdc6fc629763 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0M5DCD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd10/14/2013:svnDellInc.:pnOptiPlex390:pvr01:rvnDellInc.:rn0M5DCD:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 390
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: 

[Touch-packages] [Bug 1761096] Re: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

[Christian Ehrhardt ]

As already reported dnsmasq hangs on the hooks:
 ├─2089 /bin/sh /etc/init.d/dnsmasq systemd-start-resolvconf
 ├─2097 run-parts --arg=-a --arg=lo.dnsmasq /etc/resolvconf/update.d
 ├─2116 run-parts /etc/resolvconf/update-libc.d
 ├─2129 /bin/sh /etc/resolvconf/update-libc.d/squid
 ├─2130 /bin/sh /usr/sbin/invoke-rc.d squid reload
 └─2148 systemctl reload squid.service

The hierarchy of these is:
run-parts /etc/resolvconf/update-libc.d
  -> /etc/resolvconf/update-libc.d/squid
-> /usr/sbin/invoke-rc.d squid reload

The actual reload is done really fast:
Sep 02 06:32:19 x2 systemd[1]: Reloading LSB: Squid HTTP Proxy version 3.x.
Sep 02 06:32:19 x2 squid[2505]:  * Reloading Squid HTTP Proxy configuration 
files
Sep 02 06:32:19 x2 squid[2505]:...done.
Sep 02 06:32:19 x2 systemd[1]: Reloaded LSB: Squid HTTP Proxy version 3.x.

But in ps hierarchy the systemctl reload hangs still
0 02737   1  20   0   4500  1372 wait   Ss   ?  0:00 
/bin/sh /etc/init.d/dnsmasq systemd-start-resolvconf
0 027452737  20   0   4360   644 wait   S?  0:00  \_ 
run-parts --arg=-a --arg=lo.dnsmasq /etc/resolvconf/update.d
0 027632745  20   0   4360  1184 wait   S?  0:00  
\_ run-parts /etc/resolvconf/update-libc.d
0 027762763  20   0   4500   692 wait   S?  0:00
  \_ /bin/sh /etc/resolvconf/update-libc.d/squid
0 027772776  20   0   4500  1300 wait   S?  0:00
  \_ /bin/sh /usr/sbin/invoke-rc.d squid reload
0 027952777  20   0  24884  1068 poll_s S?  0:00
  \_ systemctl reload squid.service


The delay on that is actually 90 seconds.
And it waits until killed:
 0.00 ppoll([{fd=3, events=POLLIN}], 1, NULL, NULL, 8) = 1 ([{fd=3, 
revents=POLLIN}]) <53.100476>
53.101445 +++ killed by SIGKILL +++
Due to
  Sep 02 06:37:19 x2 systemd[1]: dnsmasq.service: Start-post operation timed 
out. Stopping.


The old init script reload in xenial was:
reload|force-reload)
res=`$DAEMON -k parse -f $CONFIG 2>&1 | grep -o "FATAL: .*"`
if test -n "$res";
then
log_failure_msg "$res"
exit 3
else
log_action_msg "Reloading $DESC configuration files"
start-stop-daemon --stop --signal 1 \
--pidfile $PIDFILE --quiet --exec $DAEMON
log_action_end_msg 0
fi
;;


But all these actions directly executed are always fast:
- /usr/sbin/invoke-rc.d squid reload
- systemctl reload squid
- start-stop-daemon --stop --signal 1 --pidfile /var/run/squid.pid --quiet 
--exec /usr/sbin/squid

I can make "systemctl reload squid" hang thou - if I invoke it at the right 
time.
To do so I replaced /etc/resolvconf/update-libc.d/squid with a debug hook that 
waits on me:
echo "DEBUG DEBUG DEBUG"
echo "would call 'invoke-rc.d squid reload' now"
echo "instead wait until /tmp/foo was touched"
f="/tmp/foo"
start=$(date -r $f);
new=$(date -r $f);
while [ "$start" = "$new" ]; do
  sleep 2;
  new=$(date -r $f);
done;
echo "DEBUG DEBUG DEBUG"


Once that is active "systemctl reload squid.service" hangs as it is in the 
error case.
This only calls into "/etc/init.d/squid reload" and that is what actually hangs

And what did I find when watching this hang:
0 041352159  20   0   4500  1368 wait   S+   ?  0:00  \_ 
/bin/sh /etc/init.d/squid reload
0 041434135  20   0  26588  1128 poll_s S+   ?  0:00  
\_ /bin/systemctl --no-pager reload squid.service
0 041444143  20   0  15404   840 poll_s S+   ?  0:00
  \_ /bin/systemd-tty-ask-password-agent --watch

I mean systemd-tty-ask-password-agent what ?!?

I must say that I love to hate the old complexity of the sysV<->systemd change.
- /etc/init.d/squid is generated into a service
- dnsmasq hook calls: systemctl reload squid
- that calls: /etc/init.d/squid reload
- which calls: /bin/systemctl --no-pager reload squid.service

This is back to step #2 one would think :-)

But if at the broken time I directly call "/bin/systemctl --no-pager reload 
squid.service" I get the same behavior with less redirections:
4 02159   0  20   0  21608  2800 wait   Ss   ?  0:00 bash
0 053122159  20   0  26588  2364 poll_s S+   ?  0:00  \_ 
/bin/systemctl --no-pager reload squid.service
0 053145312  20   0  15404   840 poll_s S+   ?  0:00  
\_ /bin/systemd-tty-ask-password-agent --watch

But when this happens /run/systemd/ask-password is empty.

I think we are looking at something more similar to:
- https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456789
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774153
- https://bugs.freedesktop.org/show_bug.cgi?id=92430
- https://bugzilla.redhat.com/show_bug.cgi?id=1367981
But 

[Touch-packages] [Bug 1893899] Re: update alsa/audio realted infomation collection code

[Yuan-Chen Cheng]

** Information type changed from Proprietary to Public

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

** Summary changed:

- update alsa/audio realted infomation collection code
+ update alsa/audio realted infomation collection code in apport

** Patch added: "apport-diff-groovy-audio-info-refinement.patch"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1893899/+attachment/5406852/+files/apport-diff-groovy-audio-info-refinement.patch

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

Title:
  update alsa/audio realted infomation collection code in apport

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

Bug description:
  what need to change

  1. try to use /usr/sbin/alsa-info before try 
/usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info 
co-exists, but anyway)
  2. add pa-info (exist after focal)
  3. add ucm2 directory. (exist after focal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893899/+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 1893899] Re: update alsa/audio realted infomation collection code in apport

[Yuan-Chen Cheng]

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

Title:
  update alsa/audio realted infomation collection code in apport

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

Bug description:
  what need to change

  1. try to use /usr/sbin/alsa-info before try 
/usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info 
co-exists, but anyway)
  2. add pa-info (exist after focal)
  3. add ucm2 directory. (exist after focal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893899/+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 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"

[Sebastian Unger]

Looks like the secondary problem is here is the same as
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1880305

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

Title:
  gio - cifs mount smb not possible "Location is not mountable"

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

Bug description:
  1) Release
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2) Package
  $ apt-cache policy libglib2.0-bin
  libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
   *** 2.64.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expected to happen
  The path should be mounted at
  /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

  4) What happened instead:
  Error Message:
  gio: smb://192.168.178.1/PathName/: Location is not mountable

  5) Long description / explanation
  Since some years, I mount a Windows drive with

  gio mount smb://192.168.178.1/PathName

  After upgrading from 19.04 to 20.04 beta, this does not work any more,
  I get the error message

  gio: smb://192.168.178.1/PathName/: Location is not mountable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-bin 2.64.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 12 12:43:53 2020
  InstallationDate: Installed on 2019-02-17 (420 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1872286/+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 1761096] Re: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

[Christian Ehrhardt ]

Since Sergio mentioned groovy, this really only is a xenial issue:

Test:
1. install dnsqmasq+squid
2. ensure dnsmasq is able to run (port collision >=Focal)
3. stop/start dnsmasq in a loop

for i in $(seq 1 4); do date; echo "-"; systemctl stop dnsmasq; date;
echo "+"; systemctl start dnsmasq; date; done

Xenial: slow
Bionic: fast
Focal: fast
Groovy: fast

Xenial:
Wed Sep  2 06:24:15 UTC 2020
-
Wed Sep  2 06:24:15 UTC 2020
+
Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
Wed Sep  2 06:25:46 UTC 2020
Wed Sep  2 06:25:46 UTC 2020
-
Wed Sep  2 06:25:46 UTC 2020
+
Wed Sep  2 06:25:47 UTC 2020
Wed Sep  2 06:25:47 UTC 2020
-
Wed Sep  2 06:25:47 UTC 2020
+
Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
Wed Sep  2 06:27:18 UTC 2020
Wed Sep  2 06:27:18 UTC 2020
-
Wed Sep  2 06:27:18 UTC 2020
+
Wed Sep  2 06:27:18 UTC 2020


So as the bug was already flagged, this is really only a xenial issue anymore.
And the fact that it is "ok" for squid to take 30 second for a restart is 
intentional as outlined above.

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

Title:
  dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in squid package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  Confirmed
Status in squid source package in Xenial:
  Confirmed

Bug description:
  Setup to reproduce:

  Ubuntu Xenial amd64 net install iso from
  http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-
  amd64/current/images/netboot/mini.iso

  Install system with mostly defaults + LVM + OpenSSH server

  Note that this bug applies to both DHCP and static IP+DNS network
  configurations

  Once server rebooted and is available, log in and install dnsmasq + squid:
  apt-get update && apt-get install squid dnsmasq

  output of this can be found at https://pastebin.com/9Atuipju
  journalctl -xe output at https://pastebin.com/uLhfM4jN

  Furthermore at this point I can run alternating errors

  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:18:07 CEST 2018
  Wed Apr  4 09:18:07 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq stop ; date
  Wed Apr  4 09:18:39 CEST 2018
  Wed Apr  4 09:18:39 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:19:10 CEST 2018
  Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
  Wed Apr  4 09:20:40 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:42:57 CEST 2018
  Wed Apr  4 09:42:57 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq stop ; date
  Wed Apr  4 09:43:14 CEST 2018
  Wed Apr  4 09:43:14 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:43:26 CEST 2018
  Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
  Wed Apr  4 09:44:56 CEST 2018

  and so on... Each and every 1 out of 2 stop/start cycle fails in 1m30s
  timeout

  Complete journalctl -xe output attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1761096/+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 1761096] Re: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

[Christian Ehrhardt ]

Sergio:
> "squid takes 30 seconds to restart regardless of dnsmasq/resolvconf (this is 
> still true nowadays, with groovy)"


I'm ashamed - it seems I have taken the most complex way to resolve a simple 
thing.
Imagine a very complex debugging through strace and gdb to reach a trivial 
config option - I removed the debugging section as it has no meaning


The 30 seconds on squid are just the default config of it.
You can set any other value to get it's restart to be quicker (but also more 
rude to potential clients).

/etc/squid/squid.conf:
#  TAG: shutdown_lifetime   time-units
#   When SIGTERM or SIGHUP is received, the cache is put into
#   "shutdown pending" mode until all active sockets are closed.
#   This value is the lifetime to set for all open descriptors
#   during shutdown mode.  Any active clients after this many
#   seconds will receive a 'timeout' message.
#Default:
# shutdown_lifetime 30 seconds
shutdown_lifetime 5 seconds

So squid to shut down / restart in 30 seconds is normal/expected.

And reload command is
ExecReload=/bin/kill -HUP $MAINPID

MAINPID is the parent, this will make it not trigger the 30 sec on
"systemctl reload" but only on "systemctl restart"

 CGroup: /system.slice/squid.service
 ├─4011 /usr/sbin/squid --foreground -sYC   <-- gets 
HUP for reload 
 ├─4013 (squid-1) --kid squid-1 --foreground -sYC
 ├─4014 (logfile-daemon) /var/log/squid/access.log
 └─4015 (pinger)

On reload is replaced with
 CGroup: /system.slice/squid.service
 ├─4011 /usr/sbin/squid --foreground -sYC
 ├─4013 (squid-1) --kid squid-1 --foreground -sYC
 ├─4024 (pinger)
 ├─4048 (logfile-daemon) /var/log/squid/access.log
 └─4049 (pinger)

And after the delay just one is left:
 CGroup: /system.slice/squid.service
 ├─4011 /usr/sbin/squid --foreground -sYC
 ├─4013 (squid-1) --kid squid-1 --foreground -sYC
 ├─4048 (logfile-daemon) /var/log/squid/access.log
 └─4049 (pinger)

So to summarize:
- squid shutdown/restart is intentionally slow to be graceful
- squid reload is fast

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

Title:
  dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in squid package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  Confirmed
Status in squid source package in Xenial:
  Confirmed

Bug description:
  Setup to reproduce:

  Ubuntu Xenial amd64 net install iso from
  http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-
  amd64/current/images/netboot/mini.iso

  Install system with mostly defaults + LVM + OpenSSH server

  Note that this bug applies to both DHCP and static IP+DNS network
  configurations

  Once server rebooted and is available, log in and install dnsmasq + squid:
  apt-get update && apt-get install squid dnsmasq

  output of this can be found at https://pastebin.com/9Atuipju
  journalctl -xe output at https://pastebin.com/uLhfM4jN

  Furthermore at this point I can run alternating errors

  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:18:07 CEST 2018
  Wed Apr  4 09:18:07 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq stop ; date
  Wed Apr  4 09:18:39 CEST 2018
  Wed Apr  4 09:18:39 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:19:10 CEST 2018
  Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
  Wed Apr  4 09:20:40 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:42:57 CEST 2018
  Wed Apr  4 09:42:57 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq stop ; date
  Wed Apr  4 09:43:14 CEST 2018
  Wed Apr  4 09:43:14 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:43:26 CEST 2018
  Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
  Wed Apr  4 09:44:56 CEST 2018

  and so on... Each and every 1 out of 2 stop/start cycle fails in 1m30s
  timeout

  Complete journalctl -xe output attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1761096/+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 1761096] Re: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

[Christian Ehrhardt ]

Sergio:
> ... reload" actually exits successfully ... systemctl ... keeps waiting

For the systemd side I'd wonder as there are so myn type= options if it is not 
getting that squid is restarted.
(https://www.freedesktop.org/software/systemd/man/systemd.service.html#Options) 
maybe worth to experiment with them?

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

Title:
  dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in squid package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  Confirmed
Status in squid source package in Xenial:
  Confirmed

Bug description:
  Setup to reproduce:

  Ubuntu Xenial amd64 net install iso from
  http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-
  amd64/current/images/netboot/mini.iso

  Install system with mostly defaults + LVM + OpenSSH server

  Note that this bug applies to both DHCP and static IP+DNS network
  configurations

  Once server rebooted and is available, log in and install dnsmasq + squid:
  apt-get update && apt-get install squid dnsmasq

  output of this can be found at https://pastebin.com/9Atuipju
  journalctl -xe output at https://pastebin.com/uLhfM4jN

  Furthermore at this point I can run alternating errors

  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:18:07 CEST 2018
  Wed Apr  4 09:18:07 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq stop ; date
  Wed Apr  4 09:18:39 CEST 2018
  Wed Apr  4 09:18:39 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:19:10 CEST 2018
  Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
  Wed Apr  4 09:20:40 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:42:57 CEST 2018
  Wed Apr  4 09:42:57 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq stop ; date
  Wed Apr  4 09:43:14 CEST 2018
  Wed Apr  4 09:43:14 CEST 2018
  root@ubuntu-min:~# date ; service dnsmasq start ; date
  Wed Apr  4 09:43:26 CEST 2018
  Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl 
status dnsmasq.service" and "journalctl -xe" for details.
  Wed Apr  4 09:44:56 CEST 2018

  and so on... Each and every 1 out of 2 stop/start cycle fails in 1m30s
  timeout

  Complete journalctl -xe output attached

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