[Touch-packages] [Bug 1838488] Re: [20217, Realtek ALC282, Speaker, Internal] Underruns, dropouts or crackling sound

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

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

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

Title:
  [20217, Realtek ALC282, Speaker, Internal] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recently installed Ubuntu in my Lenvo Ideapad and sound quality is
  very poor. Most of the  times audio is very little even though
  increased the volume to 100 and sound is crackling. I followed many
  sites to try to fix it but nothing works.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vomisha2164 F pulseaudio
   /dev/snd/controlC0:  vomisha2164 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 30 21:10:46 2019
  InstallationDate: Installed on 2019-04-21 (100 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [20217, Realtek ALC282, Speaker, Internal] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN32WW(V2.02)
  dmi.board.asset.tag: YB00141556
  dmi.board.name: 20217
  dmi.board.vendor: LENOVO
  dmi.board.version: 3194WIN8 STD SGL
  dmi.chassis.asset.tag: YB00141556
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN32WW(V2.02):bd06/04/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rn20217:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.sku: LENOVO_BI_IDEAPAD
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1838488/+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 1900068] Re: Upgrade to zeitgeist-1.0.3

2020-10-30 Thread crvi
GNOME Activity Journal 1.0 is complete:

https://gitlab.gnome.org/crvi/gnome-activity-journal/-/commits/master

but blocked on this issue, as it works only with zeitgeist-1.0.3

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

Title:
  Upgrade to zeitgeist-1.0.3

Status in zeitgeist package in Ubuntu:
  New
Status in zeitgeist package in Debian:
  Unknown

Bug description:
  Please do upgrade zeitgeist from current 1.0.2 to 1.0.3.

  It is required for GNOME Activity Journal to work. GNOME Activity Journal has
  been ported to GTK3. It will be available in GNOME repos shortly.

  For more details:

  https://discourse.gnome.org/t/zeitgeist-gnome-activity-
  journal-1-0/4521

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1900068/+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 1737614] Re: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop

2020-10-30 Thread jrda
No sound and mic here too:
http://alsa-project.org/db/?f=4237a4c012b0505892a70fbd4ed9764277bd6ccb

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

Title:
  Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP
  15-BS576TX laptop

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  I have a new laptop HP-15-BS576TX which has this Intel Corporation
  Sunrise Point-LP HD Audio.

  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD
  Audio [8086:9d71] (rev 21)

  The laptop sound works perfectly fine in Windows 10 with realtek
  drivers. However, in Ubuntu 17.10, the volume is significantly low,
  that I've to scroll the volume slider above 100% mark in pulseaudio to
  the maximum to get acceptable level of sound. I suspect the sound
  quality also is low (mono-like), may be not coming from all speakers
  (perhaps subwoofer exist for this model). Also alsamixer shows the
  speaker volume at the maximum.

   Details about the audio hardware are below:

  :~$ sudo lspci -vvv | grep -A 40 -i audio
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Hewlett-Packard Company Device 832b
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  /proc/asound/card0/codec#0 <==
  Codec: Realtek ALC3227

  ==> /proc/asound/card0/codec#2 <==
  Codec: Intel Kabylake HDMI

  :~$  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  I have gone through Linux kernel sources ALSA and Snd-HDA lists and
  unable to find any optimizations for this laptop.

  Here is the relevant dmesg details:

  [   15.502856] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [   16.310503] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3227: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [   16.310506] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   16.310507] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [   16.310508] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [   16.310509] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [   16.310510] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x19
  [   16.310512] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
  [   16.451397] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input9
  [   16.451451] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1f.3/sound/card0/input10
  [   16.451496] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input11
  [   16.451538] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input12
  [   16.451581] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input13
  [   16.451624] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input14
  [   16.451687] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input15

  Any further information needed, please let me know. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5 [modified: 
usr/share/alsa-base/alsa-info.sh]
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: ndiswrapper
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  admin2018   1246 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Dec 12 00:46:12 2017
  InstallationDate: Installed on 2017-11-22 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832B
  dmi.board.vendor: HP
  dmi.board.version: 

[Touch-packages] [Bug 1901929] Re: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all

2020-10-30 Thread Alan Easdale
Reinstalling Ubuntu. Thanks.

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

Title:
  [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi. I am new to ubuntu. I had sound at first then it just disappeared.
  I have tried to fix it. Note: When I woke ubuntu from sleep it would
  have no sound until I rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.6.0-050600-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alan  47711 F pulseaudio
   /dev/snd/controlC0:  alan  47711 F pulseaudio
   /dev/snd/pcmC0D1p:   alan  47711 F...m pulseaudio
   /dev/snd/controlC2:  alan  47711 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 28 17:32:40 2020
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alan  47711 F pulseaudio
   /dev/snd/controlC0:  alan  47711 F pulseaudio
   /dev/snd/pcmC0D1p:   alan  47711 F...m pulseaudio
   /dev/snd/controlC2:  alan  47711 F pulseaudio
  Symptom_Jack: SPDIF Out, Internal
  Symptom_Type: No sound at all
  Title: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970 GAMING (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV22.4:bd12/21/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7693
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-28T16:45:58.098082

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901929/+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 1902311] Re: GNU sha256(1) &tc --check (-c) output depends on order of --quiet and --warn

2020-10-30 Thread Brian Foster
Obviously, I meant sha256sum(1) in the bug's title!  (*sighs*)

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

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

Status in coreutils package in Ubuntu:
  New

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

  Simple example:

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

  The manual page says (spurious lines omitted):

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

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

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

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

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

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


[Touch-packages] [Bug 1902311] [NEW] GNU sha256(1) &tc --check (-c) output depends on order of --quiet and --warn

2020-10-30 Thread Brian Foster
Public bug reported:

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

Simple example:

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

The manual page says (spurious lines omitted):

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

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

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

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

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


** Tags: amd64 apport-bug focal

** Attachment added: "GNU Bash(1) script to show various differing behaviours 
(--help for summary)"
   
https://bugs.launchpad.net/bugs/1902311/+attachment/5429603/+files/sha-sum-chk.sh

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

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

Status in coreutils package in Ubuntu:
  New

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

  Simple example:

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

  The manual page says (spurious lines omitted):

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

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

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

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

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

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


[Touch-packages] [Bug 1800003] Re: evince crashes in FcConfigParseAndLoad

2020-10-30 Thread Johannes Martin
I experienced the same problem on an Ubuntu 18.04.5 system.

It was appearantly caused by .config being a symbolic link to a directory on a 
different file system. Once I moved that .config directory to my home 
directory, I was able to start evince. If the symbolic link points to a 
directory on the same file system, evince seems to work fine.
 
Linking .local to a directory on some other file system might cause similar 
problems.

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

Title:
  evince crashes in FcConfigParseAndLoad

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  I have the following situation persistently on my system (Ubuntu
  18.04.1 on Dell Latitude E6500):

  Evince called with any pdf file crashes immediately with a
  segmentation fault. From the crash dump, I see that the crash happens
  in fontconfig's FcConfigParseAndLoad function, i.e. when the system
  fonts.conf is read. I can reproduce the crash with the following
  minimal example:

  
  #include 

  const FcChar8* filename = "/home/mirkoh/fontconfig-test/fonts.conf";
  FcConfig* config;

  int main(){
 FcConfigParseAndLoad(config, filename, FcTrue);
  }
  

  The fonts.conf file used here is also absolutely minimal:

  
  
  
  
  
  

  (Get me right. It first happened with my system fonts.conf, which is
  not empty. In order to find out whether a specific entry lead to the
  crash, I deleted entry after entry, ultimately reaching the file
  above, and always FcConfigParseAndLoad crashes.

  I have no idea how to go on from here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/183/+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 1792978] Re: initscript avahi-daemon, action "start" failed

2020-10-30 Thread Billy Olsen
Avahi is not covered by field sla, so unsubscribing field-high

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

Title:
  initscript avahi-daemon, action "start" failed

Status in avahi package in Ubuntu:
  New

Bug description:
  When installing maas-region-controller, avahi-deamon failed to install
  because it was it seemed to already be running.

  
  $ apt-get -q install -y maas-region-controller
  
  [1invoke-rc.d: initscript avahi-daemon, action "start" failed.
  ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
 Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Sat 2018-09-15 
19:42:29 UTC; 9ms ago
 Process: 22726 ExecStart=/usr/sbin/avahi-daemon -s (code=exited, 
status=255)
   Main PID: 22726 (code=exited, status=255)
   
  Sep 15 19:42:29 leafeon systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
  Sep 15 19:42:29 leafeon avahi-daemon[22726]: Daemon already running on PID 
21868
  Sep 15 19:42:29 leafeon systemd[1]: avahi-daemon.service: Main 
process exit.../a
  Sep 15 19:42:29 leafeon systemd[1]: Failed to start Avahi 
mDNS/DNS-SD Stack.
  Sep 15 19:42:29 leafeon systemd[1]: avahi-daemon.service: Unit 
entered fail...e.
  Sep 15 19:42:29 leafeon systemd[1]: avahi-daemon.service: Failed 
with resul...'.
  Hint: Some lines were ellipsized, use -l to show in full.
  dpkg: error processing package avahi-daemon (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of avahi-utils:
   avahi-utils depends on avahi-daemon; however:
Package avahi-daemon is not configured yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1792978/+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 1902299] Re: auditd crash if resolver not started

2020-10-30 Thread Balázs Kalmár
Seems to be fixed in 2.8.3
https://github.com/linux-audit/audit-userspace/commit/a6c35bf4b2923943017f0410be96a1fd64acdd3a

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

Title:
  auditd crash if resolver not started

Status in audit package in Ubuntu:
  New

Bug description:
  When an email address is provided to auditd (not an alias for
  action_mail_acct) it crashes at system startup (segmentation fault).
  Since auditd.service is only depends on local-fs.target the crash
  always happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: auditd 1:2.8.2-1ubuntu1 [modified: lib/systemd/system/auditd.service]
  ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
  Uname: Linux 4.15.0-122-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  Date: Fri Oct 30 19:35:16 2020
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: audit
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.audit.auditd.conf: 2020-10-30T19:32:48.651578

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1902299/+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 1902299] [NEW] auditd crash if resolver not started

2020-10-30 Thread Balázs Kalmár
Public bug reported:

When an email address is provided to auditd (not an alias for
action_mail_acct) it crashes at system startup (segmentation fault).
Since auditd.service is only depends on local-fs.target the crash always
happens.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: auditd 1:2.8.2-1ubuntu1 [modified: lib/systemd/system/auditd.service]
ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
Uname: Linux 4.15.0-122-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.18
Architecture: amd64
Date: Fri Oct 30 19:35:16 2020
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
 TERM=xterm-256color
 PATH=(custom, no user)
SourcePackage: audit
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.audit.auditd.conf: 2020-10-30T19:32:48.651578

** Affects: audit (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 audit in Ubuntu.
https://bugs.launchpad.net/bugs/1902299

Title:
  auditd crash if resolver not started

Status in audit package in Ubuntu:
  New

Bug description:
  When an email address is provided to auditd (not an alias for
  action_mail_acct) it crashes at system startup (segmentation fault).
  Since auditd.service is only depends on local-fs.target the crash
  always happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: auditd 1:2.8.2-1ubuntu1 [modified: lib/systemd/system/auditd.service]
  ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
  Uname: Linux 4.15.0-122-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  Date: Fri Oct 30 19:35:16 2020
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: audit
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.audit.auditd.conf: 2020-10-30T19:32:48.651578

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1902299/+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 1875019] Re: ftbfs: Test failed: Basic functionality with the bind-mounted cache dir

2020-10-30 Thread themusicgod1
yeah i do

Running: Basic functionality with the bind-mounted cache dir
*** Test failed: Basic functionality with the bind-mounted cache dir
cache was updated.
FAIL run-test.sh (exit status: 1)


Testsuite summary for fontconfig 2.13.1

# TOTAL: 7
# PASS:  6
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See test/test-suite.log
Please report to https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/new

make[5]: *** [Makefile:954: test-suite.log] Error 1
make[5]: Leaving directory '/home/themusicgod1/workspace/fontconfig-2.13.1/test'
make[4]: *** [Makefile:1062: check-TESTS] Error 2
make[4]: Leaving directory '/home/themusicgod1/workspace/fontconfig-2.13.1/test'
make[3]: *** [Makefile:1171: check-am] Error 2
make[3]: Leaving directory '/home/themusicgod1/workspace/fontconfig-2.13.1/test'
make[2]: *** [Makefile:1173: check] Error 2
make[2]: Leaving directory '/home/themusicgod1/workspace/fontconfig-2.13.1/test'
make[1]: *** [Makefile:602: check-recursive] Error 1
make[1]: Leaving directory '/home/themusicgod1/workspace/fontconfig-2.13.1'
dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:10: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -i -I -b failed


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

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

Title:
  ftbfs:  Test failed: Basic functionality with the bind-mounted cache
  dir

Status in fontconfig package in Ubuntu:
  New

Bug description:
  1) apt-src install fontconfig
  2) cd fontconfig-2.13.1/
  3) debuild -us -uc -b

  gets to

  PASS: test-hash
  PASS: test-bz106632
  FAIL: run-test.sh
  
 fontconfig 2.13.1: test/test-suite.log
  

  # TOTAL: 7
  # PASS:  6
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  .. contents:: :depth: 2

  FAIL: run-test
  ==

  Running: Basic check
  Running: With a subdir
  Running: Subdir with a cache file
  Running: Complicated directory structure
  Running: Subdir with an out-of-date cache file
  Running: Dir with an out-of-date cache file
  Running: Re-creating .uuid
  Running: Consistency between .uuid and cache name
  
b41b6931-2503-44dd-a5d0-465a2c171511/home/z/fontconfig-2.13.1/test/cache.dir/08acdce6-36bc-4684-9a7b-0f24192abc6b-le64.cache-7
  Running: Keep mtime of the font directory
  Running: Basic functionality with the bind-mounted cache dir
  *** Test failed: Basic functionality with the bind-mounted cache dir
  cache was updated.
  FAIL run-test.sh (exit status: 1)

  
  ubuntu: focal 20.04 LTS
  fontconfig1: fontconfig:
Installed: 2.13.1-2ubuntu3
Candidate: 2.13.1-2ubuntu3
Version table:
   *** 2.13.1-2ubuntu3 500
  500 http://speglar.simnet.is/ubuntu focal/main amd64 Packages
  500 http://ubuntu.hysing.is/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: fontconfig 2.13.1-2ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 25 13:15:14 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1875019/+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 1900729] [NEW] gnome-terminal font settings show only italic version of ubuntu mono

2020-10-30 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

trying to change the font in gnome-terminal, only the italics version of
the ubuntu mono font is shown, as can be seen in the attachment. on the
other hand, when changing fonts in the appearance settings, i can see
all variants of the ubuntu fonts...

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-terminal 3.38.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Oct 20 16:56:57 2020
InstallationDate: Installed on 2020-10-20 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: amd64 apport-bug groovy
-- 
gnome-terminal font settings show only italic version of ubuntu mono
https://bugs.launchpad.net/bugs/1900729
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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


[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

2020-10-30 Thread Gunnar Hjalmarsson
** Package changed: gnome-terminal (Ubuntu) => gtk+3.0 (Ubuntu)

** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1900729/+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 1902244] [NEW] Backport packages for 20.04.1 HWE stack

2020-10-30 Thread Timo Aaltonen
Public bug reported:

[Impact]

These are needed for 20.04.1 images.

[Test case]

Boot a daily image, see that it still has the necessary stack installed
and working.

Check upgrade from stock bionic.

[Regression potential]

libdrm: very minimal chance for regressions

llvm-11: a new package, no regression potential on it's own

libclc: just a rebuild against the new llvm

mesa: a new major release, but we'll pull the final stable release of
20.2.x series, so there shouldn't be any regressions left at that point

xserver: a new point-release

xorg drivers: modest updates, if any

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

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

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

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

** Affects: libclc (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: libdrm (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: mesa (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: xorg-server (Ubuntu Focal)
 Importance: Undecided
 Status: New

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

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

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

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Backport packages for 20.04.1 HWE stack

Status in libclc package in Ubuntu:
  New
Status in libdrm package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New
Status in libclc source package in Focal:
  New
Status in libdrm source package in Focal:
  New
Status in mesa source package in Focal:
  New
Status in xorg-server source package in Focal:
  New

Bug description:
  [Impact]

  These are needed for 20.04.1 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

  xorg drivers: modest updates, if any

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1902236] [NEW] Duplicated root and nobody returned by getent on Focal

2020-10-30 Thread Simon Déziel
Public bug reported:

* Summary

systemd's NSS integration causes getent passwd/group to return
duplicated entries for root/root and nobody/nogroup. The root account
also gets a different shell (/bin/sh instead of /bin/bash).

* Steps to reproduce:

1) create a container
$ lxc launch images:ubuntu/focal test-nobody
2) check the root and nobody accounts
$ lxc exec test-nobody -- getent passwd | grep -E '^(root|nobody):'
3) check the root and nogroup groups
$ lxc exec test-nobody -- getent group | grep -E '^(root|nogroup):'

2 and 3 should report a single entry for each account/group but they
return dups like this:

root:x:0:0:root:/root:/bin/bash
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
root:x:0:0:root:/root:/bin/sh
nobody:x:65534:65534:nobody:/:/usr/sbin/nologin

* Description

The problem seems to come from the NSS integration:

$ lxc exec test-nobody -- grep -wF systemd /etc/nsswitch.conf
passwd: files systemd
group:  files systemd

as the /etc/passwd and /etc/group file contain no dups:

$ lxc exec test-nobody -- grep ^nobody: /etc/passwd
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
$ lxc exec test-nobody -- grep ^nogroup: /etc/group
nogroup:x:65534:

Removing systemd from /etc/nsswitch.conf indeed removes the dup.

An alternative way of seeing what systemd adds on top of the flat files:

$ lxc exec test-nobody -- bash -c 'diff -u /etc/passwd <(getent passwd)'
--- /etc/passwd 2020-10-30 13:07:52.219261001 +
+++ /dev/fd/63  2020-10-30 13:29:38.396928732 +
@@ -24,3 +24,5 @@
 _apt:x:105:65534::/nonexistent:/usr/sbin/nologin
 ubuntu:x:1000:1000::/home/ubuntu:/bin/bash
 systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
+root:x:0:0:root:/root:/bin/sh
+nobody:x:65534:65534:nobody:/:/usr/sbin/nologin

$ lxc exec test-nobody -- bash -c 'diff -u /etc/group <(getent group)'
--- /etc/group  2020-10-30 13:07:52.211261089 +
+++ /dev/fd/63  2020-10-30 13:29:45.892846747 +
@@ -50,3 +50,5 @@
 ubuntu:x:1000:
 ssh:x:111:
 systemd-coredump:x:999:
+root:x:0:
+nogroup:x:65534:

* Additional information

This bug seems to occur on Focal alone as Bionic and Groovy are not
affected.

$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04

$ apt-cache policy base-passwd systemd
base-passwd:
  Installed: 3.5.47
  Candidate: 3.5.47
  Version table:
 *** 3.5.47 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
systemd:
  Installed: 245.4-4ubuntu3.2
  Candidate: 245.4-4ubuntu3.2
  Version table:
 *** 245.4-4ubuntu3.2 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpkg/status
 245.4-4ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

** Description changed:

  * Summary
  
  systemd's NSS integration causes getent passwd/group to return
  duplicated entries for root/root and nobody/nogroup. The root account
  also gets a different shell (/bin/sh instead of /bin/bash).
  
  * Steps to reproduce:
  
  1) create a container
  $ lxc launch images:ubuntu/focal test-nobody
  2) check the root and nobody accounts
  $ lxc exec test-nobody -- getent passwd | grep -E '^(root|nobody):'
  3) check the root and nogroup groups
  $ lxc exec test-nobody -- getent group | grep -E '^(root|nogroup):'
  
  2 and 3 should report a single entry for each account/group but they
  return dups like this:
  
  root:x:0:0:root:/root:/bin/bash
  nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
  root:x:0:0:root:/root:/bin/sh
  nobody:x:65534:65534:nobody:/:/usr/sbin/nologin
- 
  
  * Description
  
  The problem seems to come from the NSS integration:
  
  $ lxc exec test-nobody -- grep -wF systemd /etc/nsswitch.conf
  passwd: files systemd
  group:  files systemd
  
  as the /etc/passwd and /etc/group file contain no dups:
  
  $ lxc exec test-nobody -- grep ^nobody: /etc/passwd
  nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
  $ lxc exec test-nobody -- grep ^nogroup: /etc/group
  nogroup:x:65534:
  
  Removing systemd from /etc/nsswitch.conf indeed removes the dup.
  
  An alternative way of seeing what systemd adds on top of the flat files:
  
  $ lxc exec test-nobody -- bash -c 'diff -u /etc/passwd <(getent passwd)'
  --- /etc/passwd   2020-10-30 13:07:52.219261001 +
  +++ /dev/fd/632020-10-30 13:29:38.396928732 +
  @@ -24,3 +24,5 @@
-  _apt:x:105:65534::/nonexistent:/usr/sbin/nologin
-  ubuntu:x:1000:1000::/home/ubuntu:/bin/bash
-  systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
+  _apt:x:105:65534::/nonexistent:/usr/sbin/nologin
+  ubuntu:x:1000:1000::/home/ubuntu:/bin/bash
+  systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  +root:x:0:0:root:/root:/bin/sh
  +nobody:x:65534:65534:nobody:/:/usr/sbin/nologin
  
  $ lxc exec test-nobody --

[Touch-packages] [Bug 1901020] Re: new upstream release 2020d

2020-10-30 Thread Launchpad Bug Tracker
This bug was fixed in the package tzdata - 2020d-0ubuntu0.18.04

---
tzdata (2020d-0ubuntu0.18.04) bionic; urgency=medium

  * New upstream version (LP: #1901020), affecting past and future timestamps:
- Palestine ends DST earlier than predicted, on 2020-10-24.
- Fiji starts DST later than usual, on 2020-12-20.
- Revised predictions for Morocco's changes starting in 2023.
- Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08.
- Macquarie Island has stayed in sync with Tasmania since 2011.
- Casey, Antarctica is at +08 in winter and +11 in summer since 2018.
  * Restore old SystemV timezones.

 -- Brian Murray   Thu, 22 Oct 2020 14:18:51 -0700

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

Title:
  new upstream release 2020d

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Precise:
  Fix Released
Status in tzdata source package in Trusty:
  Fix Released
Status in tzdata source package in Xenial:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Groovy:
  Fix Released

Bug description:
  New upstream version, affecting the following future timestamps:
    - Fiji starts DST later than usual, on 2020-12-20.
    - Palestine ends DST earlier than predicted, on 2020-10-24.
- Revised predictions for Morocco's changes starting in 2023.
- Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08.
- Macquarie Island has stayed in sync with Tasmania since 2011.
- Casey, Antarctica is at +08 in winter and +11 in summer since 2018.

  Additionally, upstream removed the "old" SystemV timezones, but the
  SRU will ensure that they are kept. Subsequently, these should be
  checked for using the following:

  zdump -v SystemV/MST7
  zdump -v America/Phoenix

  The information returned by SystemV/MST7 should be included in
  America/Phoenix's output.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+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 1901020] Re: new upstream release 2020d

2020-10-30 Thread Launchpad Bug Tracker
This bug was fixed in the package tzdata - 2020d-0ubuntu0.18.04

---
tzdata (2020d-0ubuntu0.18.04) bionic; urgency=medium

  * New upstream version (LP: #1901020), affecting past and future timestamps:
- Palestine ends DST earlier than predicted, on 2020-10-24.
- Fiji starts DST later than usual, on 2020-12-20.
- Revised predictions for Morocco's changes starting in 2023.
- Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08.
- Macquarie Island has stayed in sync with Tasmania since 2011.
- Casey, Antarctica is at +08 in winter and +11 in summer since 2018.
  * Restore old SystemV timezones.

 -- Brian Murray   Thu, 22 Oct 2020 14:18:51 -0700

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

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

Title:
  new upstream release 2020d

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Precise:
  Fix Released
Status in tzdata source package in Trusty:
  Fix Released
Status in tzdata source package in Xenial:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Groovy:
  Fix Released

Bug description:
  New upstream version, affecting the following future timestamps:
    - Fiji starts DST later than usual, on 2020-12-20.
    - Palestine ends DST earlier than predicted, on 2020-10-24.
- Revised predictions for Morocco's changes starting in 2023.
- Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08.
- Macquarie Island has stayed in sync with Tasmania since 2011.
- Casey, Antarctica is at +08 in winter and +11 in summer since 2018.

  Additionally, upstream removed the "old" SystemV timezones, but the
  SRU will ensure that they are kept. Subsequently, these should be
  checked for using the following:

  zdump -v SystemV/MST7
  zdump -v America/Phoenix

  The information returned by SystemV/MST7 should be included in
  America/Phoenix's output.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+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 1902200] Re: Ubuntu 20.04 - Network Manager blocks port 68 so our device agent is not able to complete DHCP Discovery

2020-10-30 Thread Paul White
** Package changed: ubuntu => network-manager (Ubuntu)

** Tags added: focal

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

Title:
  Ubuntu 20.04 - Network Manager blocks port 68 so our device agent is
  not able to complete DHCP Discovery

Status in network-manager package in Ubuntu:
  New

Bug description:
  Network Manager blocks port 68 so our device agent is not able to
  complete DHCP Discovery

  we have a component by name DCA-Enabler which does DHCP Discovery and expects 
response on port 68, this is generic DHCP behavior port number 68 is used by 
the client to receive (DHCP) server responses.
  Refer https://en.wikipedia.org/wiki/Bootstrap_Protocol  

  In older Ubuntu versions like 16.04, 18.04 etc. Network Manager does not 
blocks port 68 so DCA-E is able to read the responses.
  In Ubuntu 20.04, As network manager has already occupied port 68 it gets the 
DHCP response but DCA-E does not gets access to the port and cannot read the 
response. 

  So let us know what could be the solution for this, is there a way we can 
call network Manager API and read the DHCP Discovery response ?
  Or can we have a call with Canonical and understand on this change in 
behavior ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902200/+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 1902200] [NEW] Ubuntu 20.04 - Network Manager blocks port 68 so our device agent is not able to complete DHCP Discovery

2020-10-30 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Network Manager blocks port 68 so our device agent is not able to
complete DHCP Discovery

we have a component by name DCA-Enabler which does DHCP Discovery and expects 
response on port 68, this is generic DHCP behavior port number 68 is used by 
the client to receive (DHCP) server responses.
Refer https://en.wikipedia.org/wiki/Bootstrap_Protocol  

In older Ubuntu versions like 16.04, 18.04 etc. Network Manager does not blocks 
port 68 so DCA-E is able to read the responses.
In Ubuntu 20.04, As network manager has already occupied port 68 it gets the 
DHCP response but DCA-E does not gets access to the port and cannot read the 
response. 

So let us know what could be the solution for this, is there a way we can call 
network Manager API and read the DHCP Discovery response ?
Or can we have a call with Canonical and understand on this change in behavior ?

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


** Tags: bot-comment
-- 
Ubuntu 20.04 - Network Manager blocks port 68 so our device agent is not able 
to complete DHCP Discovery
https://bugs.launchpad.net/bugs/1902200
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager in Ubuntu.

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


[Touch-packages] [Bug 1901026] Re: [GDB] No socket file connection support

2020-10-30 Thread Matthias Klose
** Also affects: gdb (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  New

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1901026/+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 1902225] [NEW] SRU: update gdb 8.1.1 for 18.04 LTS

2020-10-30 Thread Matthias Klose
Public bug reported:

gdb 8.1.1 is a minor bug fix release for 8.1. Some of the issues fixed
in 8.1.1 are already fixed in the branch update in 8.1-0ubuntu3:

 * gdb 8.1.1 release.
This is a minor corrective release over GDB 8.1, fixing following issues:
- PR gdb/23028 (inconsistent disassemble of vcvtpd2dq)
- PR gdb/23053 (Fix -D_GLIBCXX_DEBUG gdb-add-index regression)
- PR gdb/23127 ([AArch64] GDB cannot be used for debugging software that
  uses high Virtual Addresses)
- PR server/23158 (gdbserver no longer functional on Windows)
- PR breakpoints/23210 ([8.1/8.2 Regression] Bogus Breakpoint address
  adjusted from 0xf7fe7dd3 to 0xf7fe7dd3)
Already fixed in 8.1-0ubuntu3:
- PR gdb/22824 (misleading description of new rbreak Python function in
  GDB 8.1 NEWS file)
- PR gdb/22849 (ctrl-c doesn't work in extended-remote)
- PR gdb/22907 ([Regression] gdbserver doesn't work with filename-only
  binaries).
  * Allow remote debugging over a Unix local domain socket. LP: #1901026.

This minor version update fixes four upstream issues (not counting the
Windows specific issue), plus allows remote debugging over a Unix local
domain socket., a patch taken from the 8.2 development.

Validation: The tests run during build time are passing, and the remote
debugging is checked to be working (no automated test case).

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

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

Title:
  SRU: update gdb 8.1.1 for 18.04 LTS

Status in gdb package in Ubuntu:
  New

Bug description:
  gdb 8.1.1 is a minor bug fix release for 8.1. Some of the issues fixed
  in 8.1.1 are already fixed in the branch update in 8.1-0ubuntu3:

   * gdb 8.1.1 release.
  This is a minor corrective release over GDB 8.1, fixing following issues:
  - PR gdb/23028 (inconsistent disassemble of vcvtpd2dq)
  - PR gdb/23053 (Fix -D_GLIBCXX_DEBUG gdb-add-index regression)
  - PR gdb/23127 ([AArch64] GDB cannot be used for debugging software that
uses high Virtual Addresses)
  - PR server/23158 (gdbserver no longer functional on Windows)
  - PR breakpoints/23210 ([8.1/8.2 Regression] Bogus Breakpoint address
adjusted from 0xf7fe7dd3 to 0xf7fe7dd3)
  Already fixed in 8.1-0ubuntu3:
  - PR gdb/22824 (misleading description of new rbreak Python function in
GDB 8.1 NEWS file)
  - PR gdb/22849 (ctrl-c doesn't work in extended-remote)
  - PR gdb/22907 ([Regression] gdbserver doesn't work with filename-only
binaries).
* Allow remote debugging over a Unix local domain socket. LP: #1901026.

  This minor version update fixes four upstream issues (not counting the
  Windows specific issue), plus allows remote debugging over a Unix
  local domain socket., a patch taken from the 8.2 development.

  Validation: The tests run during build time are passing, and the
  remote debugging is checked to be working (no automated test case).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1902225/+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 1902217] Re: package ca-certificates 20201027ubuntu0.20.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit

2020-10-30 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

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

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 20.04.1 LTS
 Release:   20.04

  2) ca-certificates:
Installiert:   20201027ubuntu0.20.04.1
Installationskandidat: 20201027ubuntu0.20.04.1
Versionstabelle:
   *** 20201027ubuntu0.20.04.1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main i386 
Packages
  100 /var/lib/dpkg/status
   20190110ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages

  3) Update runs smooth without errors

  4) Installation error

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ca-certificates 20201027ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct 30 12:11:41 2020
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-11-02 (2188 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20201027ubuntu0.20.04.1 failed to 
install/upgrade: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-08-02 (88 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1902217/+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 1902217] [NEW] package ca-certificates 20201027ubuntu0.20.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exi

2020-10-30 Thread Niels Braczek
Public bug reported:

1) Description: Ubuntu 20.04.1 LTS
   Release: 20.04

2) ca-certificates:
  Installiert:   20201027ubuntu0.20.04.1
  Installationskandidat: 20201027ubuntu0.20.04.1
  Versionstabelle:
 *** 20201027ubuntu0.20.04.1 500
500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages
100 /var/lib/dpkg/status
 20190110ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages

3) Update runs smooth without errors

4) Installation error

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: ca-certificates 20201027ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Oct 30 12:11:41 2020
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2014-11-02 (2188 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: ca-certificates
Title: package ca-certificates 20201027ubuntu0.20.04.1 failed to 
install/upgrade: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-08-02 (88 days ago)

** Affects: ca-certificates (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 ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1902217

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

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 20.04.1 LTS
 Release:   20.04

  2) ca-certificates:
Installiert:   20201027ubuntu0.20.04.1
Installationskandidat: 20201027ubuntu0.20.04.1
Versionstabelle:
   *** 20201027ubuntu0.20.04.1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main i386 
Packages
  100 /var/lib/dpkg/status
   20190110ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages

  3) Update runs smooth without errors

  4) Installation error

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ca-certificates 20201027ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct 30 12:11:41 2020
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-11-02 (2188 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20201027ubuntu0.20.04.1 failed to 
install/upgrade: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-08-02 (88 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1902217/+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 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack

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

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

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

Title:
  Lenovo P1G3 - unable to select system speakers when headset plugged
  into audio jack

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I suspect this is a pulseaudio or alsa bug.

  Our test team reported this:
  1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS .
  2. Boot system.
  3. Play audio or video file.
  4. Open Settings > Sound.
  5. Hot attach headset.
  6. Notice that headset is selected as output device in sound settings and 
sound can be heard from headset => EXPECTED
  7. While playback, select Internal Speaker as output device => KEYPOINT
  9. Notice:SUT havo no sound from Internal Speakers => PROBLEM

  I was able to confirm this - it seems with the headphones connected
  that I can't select the system speakers. If I don't have headphones
  connected I can switch between dock audio and system speakers
  correctly - so it's just related to the audio jack

  Thanks
  Mark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896098/+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 1902109] Re: rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted

2020-10-30 Thread Bug Watch Updater
Launchpad has imported 2 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=26401.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2020-08-17T16:13:21+00:00 Ldv-c wrote:

Fixes for https://sourceware.org/bugzilla/show_bug.cgi?id=14578
introduced regressions in cases when /proc is not mounted:
- lchmod used to return ENOSYS, now it returns EOPNOTSUPP;
- fchmodat(AT_SYMLINK_NOFOLLOW) used to return ENOTSUP, now it returns 
EOPNOTSUPP which is different from ENOTSUP on some architectures, e.g. hppa.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1902109/comments/0


On 2020-10-30T07:31:47+00:00 Alkis Georgopoulos wrote:

Hello, just noting that rsync in Ubuntu 20.10 is affected by this glibc
issue:

https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1902109
https://github.com/WayneD/rsync/issues/109

Reply at:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1902109/comments/4


** Changed in: glibc
   Status: Unknown => Confirmed

** Changed in: glibc
   Importance: Unknown => Medium

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

** Bug watch added: github.com/WayneD/rsync/issues #109
   https://github.com/WayneD/rsync/issues/109

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

Title:
  rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted

Status in GLibC:
  Confirmed
Status in glibc package in Ubuntu:
  New
Status in rsync package in Ubuntu:
  Triaged

Bug description:
  Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
  This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it 
returned "no" before.

  Steps to reproduce:

  # Emulate /proc not being mounted
  $ mount --bind / /mnt
  $ chroot /mnt rsync -a /bin/ls .
  rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not 
supported (95)
  rsync error: some files/attrs were not transferred (see previous errors) 
(code 3) at main.c(1330) [sender=3.2.3]

  I reported this issue upstream in
  https://github.com/WayneD/rsync/issues/109 but the rsync developer
  says it's a problem in libc, and it might well be.

  Simple C code to reproduce the problem without rsync:

  printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));

  If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails
  when /proc isn't mounted, yet it succeeds if it is mounted.

  Python had a similar issue, and they ended up avoiding
  AC_CHECK_FUNC(lchmod) under Linux:

  https://bugs.python.org/issue34652
  
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140

  ```c
  if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
  fi
  ```

  So I'm not sure which package is causing the bug here. Should autoconf
  return false? Should libc implement lchown without the bug? Or should
  rsync skip lchmod under Linux, like python did?

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1902109/+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 1899340] Re: preinstall `plasma-discover-backend-flatpak` by default

2020-10-30 Thread ruruoli
*** This bug is a duplicate of bug 1899338 ***
https://bugs.launchpad.net/bugs/1899338

** This bug has been marked a duplicate of bug 1899338
preinstall `plasma-discover-backend-flatpak` by default

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

Title:
  preinstall `plasma-discover-backend-flatpak` by default

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Would be nice to have ability to use flatpak out of the box.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1899340/+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 1902135] Re: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: el subproceso instalado paquete openssh-server script post-installation devolvió el código de sa

2020-10-30 Thread Christian Ehrhardt 
Hi,
thanks for the report but IMHO there is not much to do, port 22 is SSHs port 
and it is right to default to it. If your local configuration has port 22 bound 
to something else (Docker in your case) you need to adapt the configuration of 
either (ssh in its half installed state or your docker/images).

There is not much the ssh (package) could do IMHO.

So this looks like a local configuration problem, rather than a bug in
Ubuntu.

You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration problems, I'm marking this bug as Invalid. This helps us
to focus on fixing bugs in Ubuntu.

If you believe that this is really a bug, then you may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

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

Title:
  package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade:
  el subproceso instalado paquete openssh-server script post-
  installation devolvió el código de salida de error 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  just following the installation guide
  
https://community.home-assistant.io/t/installing-home-assistant-supervised-on-debian-10/200253

  it crashed installing openssh-server, because docker already have the
  port 22 binded

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: openssh-server 1:8.2p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  AptOrdering:
   ncurses-term:amd64: Install
   openssh-sftp-server:amd64: Install
   openssh-server:amd64: Install
   ssh-import-id:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Oct 29 21:04:55 2020
  ErrorMessage: el subproceso instalado paquete openssh-server script 
post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2020-10-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /run/sshd
  SourcePackage: openssh
  Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: 
el subproceso instalado paquete openssh-server script post-installation 
devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1902135/+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 1902109] Re: rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted

2020-10-30 Thread Christian Ehrhardt 
Awesome, thanks for updating the bug tasks and tracking bug already
Alkis!

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

Title:
  rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted

Status in GLibC:
  Unknown
Status in glibc package in Ubuntu:
  New
Status in rsync package in Ubuntu:
  Triaged

Bug description:
  Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
  This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it 
returned "no" before.

  Steps to reproduce:

  # Emulate /proc not being mounted
  $ mount --bind / /mnt
  $ chroot /mnt rsync -a /bin/ls .
  rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not 
supported (95)
  rsync error: some files/attrs were not transferred (see previous errors) 
(code 3) at main.c(1330) [sender=3.2.3]

  I reported this issue upstream in
  https://github.com/WayneD/rsync/issues/109 but the rsync developer
  says it's a problem in libc, and it might well be.

  Simple C code to reproduce the problem without rsync:

  printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));

  If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails
  when /proc isn't mounted, yet it succeeds if it is mounted.

  Python had a similar issue, and they ended up avoiding
  AC_CHECK_FUNC(lchmod) under Linux:

  https://bugs.python.org/issue34652
  
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140

  ```c
  if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
  fi
  ```

  So I'm not sure which package is causing the bug here. Should autoconf
  return false? Should libc implement lchown without the bug? Or should
  rsync skip lchmod under Linux, like python did?

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1902109/+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 1902109] Re: rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted

2020-10-30 Thread Alkis Georgopoulos
Hi Robie, thank you for the feedback,

I located an upstream bug report in glibc for this:
https://sourceware.org/bugzilla/show_bug.cgi?id=26401

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

** Also affects: rsync via
   https://sourceware.org/bugzilla/show_bug.cgi?id=26401
   Importance: Unknown
   Status: Unknown

** No longer affects: rsync

** Also affects: glibc via
   https://sourceware.org/bugzilla/show_bug.cgi?id=26401
   Importance: Unknown
   Status: Unknown

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

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

Title:
  rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted

Status in GLibC:
  Unknown
Status in glibc package in Ubuntu:
  New
Status in rsync package in Ubuntu:
  Triaged

Bug description:
  Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
  This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it 
returned "no" before.

  Steps to reproduce:

  # Emulate /proc not being mounted
  $ mount --bind / /mnt
  $ chroot /mnt rsync -a /bin/ls .
  rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not 
supported (95)
  rsync error: some files/attrs were not transferred (see previous errors) 
(code 3) at main.c(1330) [sender=3.2.3]

  I reported this issue upstream in
  https://github.com/WayneD/rsync/issues/109 but the rsync developer
  says it's a problem in libc, and it might well be.

  Simple C code to reproduce the problem without rsync:

  printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));

  If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails
  when /proc isn't mounted, yet it succeeds if it is mounted.

  Python had a similar issue, and they ended up avoiding
  AC_CHECK_FUNC(lchmod) under Linux:

  https://bugs.python.org/issue34652
  
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140

  ```c
  if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
  fi
  ```

  So I'm not sure which package is causing the bug here. Should autoconf
  return false? Should libc implement lchown without the bug? Or should
  rsync skip lchmod under Linux, like python did?

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