date:20201220

[Touch-packages] [Bug 1713279] Re: package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2020-12-20 Thread Launchpad Bug Tracker

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

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

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

Title:
  package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 128

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  Recién acabo de instalar ubuntu 17.10 para probarlo.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: rsyslog 8.16.0-1ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 26 19:02:21 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~rc1~ubuntu1
  SourcePackage: rsyslog
  Title: package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1713279/+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] Re: Backport packages for 20.04.2 HWE stack

2020-12-20 Thread Colin Canham

To all above, my Ubuntu 20.04lts software update is attempting to load
but hangs and this repeats every time I reboot machine.

I was just reading through the technical descriptions trying to figure
out what could be causing the hanging up...and selected a random link to
open browser to attempt to highlight my plight...

Also not sure if this is related to the Display (Extended) screen issues
I'm again having on 20.04lts. Got it (Extended) displays going a while
back but then after a reinstall for other software issues from Microchip
MPLAB X IDE again am having difficulty trying to get extended display to
word again...

Know it's a shot in the dark mentioning this here with the hanging
Software update... but worth a try.

** Attachment added: "Hanging Software Update and repeat attempt on every 
reboot."
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1902244/+attachment/5445381/+files/Screenshot%20from%202020-12-21%2005-53-58.png

-- 
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.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in libglvnd source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.2 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

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

  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 1908843] [NEW] fstrim spins up HDDs

2020-12-20 Thread V33m

Public bug reported:

Issue: fstrim.timer is enabled and trigger "/sbin/fstrim --fstab
--verbose --quiet" which spins up hard drives mounted in fstab. How can
one ignore or specify which drives to use fstrim on for fstrim? Or could
this be related to that I've symbolic links between SD card and drives?
If the latter might be the case, is there a way to ignore folders and
paths? Or shouldn't symbolic links be ignored by default as they are of
no relevance given the data is placed elsewhere?


- - - More information - - -
I've fstrim.timer enabled on Ubuntu 20.04.1 LTS (Focal Fossa) using util-linux 
2.34-0.1ubuntu9.1. My setup consist of an eMMC (/), micro SD card (/mnt/SD) and 
two hard drives. All drives are mounted in fstab:

LABEL=BOOT /media/boot vfat umask=0077 0 1
UUID=REMOVED / ext4 errors=remount-ro 0 1
UUID=REMOVED /mnt/SD ext4 noatime,nofail,defaults 0 1
UUID=REMOVED /mnt/USB1 ext4 noatime,nofail,defaults 0 2
UUID=REMOVED /mnt/USB2 ext4 noatime,nofail,defaults 0 2

# Bind Mounts
/mnt/SD/FOLDER /FOLDER none bind,nobootwait 0 2
/mnt/SD/home/USER /home/USER none bind,nobootwait 0 2


- - - fstrim.timer triggers every week - - -

● fstrim.service - Discard unused blocks on filesystems from /etc/fstab
 Loaded: loaded (/lib/systemd/system/fstrim.service; static; vendor preset: 
enabled)
 Active: inactive (dead) since Mon 2020-12-14 00:00:09 CET; 1 weeks 0 days 
ago
TriggeredBy: ● fstrim.timer
   Docs: man:fstrim(8)
Process: 997644 ExecStart=/sbin/fstrim --fstab --verbose --quiet 
(code=exited, status=0/SUCCESS)
   Main PID: 997644 (code=exited, status=0/SUCCESS)

Dec 14 00:00:00 HOST systemd[1]: Starting Discard unused blocks on filesystems 
from /etc/fstab...
Dec 14 00:00:09 HOST fstrim[997644]: /mnt/SD: 5.4 GiB (5763649536 bytes) 
trimmed on /dev/mmcblk1p1
Dec 14 00:00:09 HOST fstrim[997644]: /: 4.3 GiB (4591874048 bytes) trimmed on 
/dev/mmcblk0p2
Dec 14 00:00:09 HOST systemd[1]: fstrim.service: Succeeded.
Dec 14 00:00:09 HOST systemd[1]: Finished Discard unused blocks on filesystems 
from /etc/fstab.


- - - Drives spin up every week - - -

● hd-idle.service - hd-idle - spin down idle hard disks
 Loaded: loaded (/lib/systemd/system/hd-idle.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Sun 2020-12-06 15:26:09 CET; 2 weeks 0 days 
ago
   Docs: man:hd-idle(8)
   Main PID: 2281 (hd-idle)
  Tasks: 10 (limit: 3840)
 Memory: 4.1M
 CGroup: /system.slice/hd-idle.service
 └─2281 /usr/sbin/hd-idle -i 0 -c ata -s 1 -l /var/log/hd-idle.log 
-a /dev/disk/by-label/...

Dec 07 00:00:57 HOST hd-idle[2281]: sda spinup
Dec 07 00:00:57 HOST hd-idle[2281]: sdb spinup
Dec 07 00:15:57 HOST hd-idle[2281]: /dev/sda spindown
Dec 07 00:15:58 HOST hd-idle[2281]: /dev/sdb spindown
Dec 14 00:00:14 HOST hd-idle[2281]: sda spinup
Dec 14 00:00:14 HOST hd-idle[2281]: sdb spinup
Dec 14 00:15:14 HOST hd-idle[2281]: /dev/sda spindown
Dec 14 00:15:14 HOST hd-idle[2281]: /dev/sdb spindown

I know that the drives spin up as you can hear it. Simply disabling
fstrim.timer did not make the drives spin up, however, I loose the
benefits of using the service.

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

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

Title:
  fstrim spins up HDDs

Status in util-linux package in Ubuntu:
  New

Bug description:
  Issue: fstrim.timer is enabled and trigger "/sbin/fstrim --fstab
  --verbose --quiet" which spins up hard drives mounted in fstab. How
  can one ignore or specify which drives to use fstrim on for fstrim? Or
  could this be related to that I've symbolic links between SD card and
  drives? If the latter might be the case, is there a way to ignore
  folders and paths? Or shouldn't symbolic links be ignored by default
  as they are of no relevance given the data is placed elsewhere?

  
  - - - More information - - -
  I've fstrim.timer enabled on Ubuntu 20.04.1 LTS (Focal Fossa) using 
util-linux 2.34-0.1ubuntu9.1. My setup consist of an eMMC (/), micro SD card 
(/mnt/SD) and two hard drives. All drives are mounted in fstab:

  LABEL=BOOT /media/boot vfat umask=0077 0 1
  UUID=REMOVED / ext4 errors=remount-ro 0 1
  UUID=REMOVED /mnt/SD ext4 noatime,nofail,defaults 0 1
  UUID=REMOVED /mnt/USB1 ext4 noatime,nofail,defaults 0 2
  UUID=REMOVED /mnt/USB2 ext4 noatime,nofail,defaults 0 2

  # Bind Mounts
  /mnt/SD/FOLDER /FOLDER none bind,nobootwait 0 2
  /mnt/SD/home/USER /home/USER none bind,nobootwait 0 2

  
  - - - fstrim.timer triggers every week - - -

  ● fstrim.service - Discard unused blocks on filesystems from /etc/fstab
   Loaded: loaded (/lib/systemd/system/fstrim.service; static; vendor 
preset: enabled)
   Active: inactive (dead) since Mon 2020-12-14 00:00:09 CET; 1 weeks 0 
days ago
  TriggeredBy: ● fstrim.timer
 Docs:

[Touch-packages] [Bug 1907676] Re: segmentation fault when opening fd

2020-12-20 Thread Marc Deslauriers

There are updates for this issue built in the security team PPA here:

https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages

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

Title:
  segmentation fault when opening fd

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Focal:
  New
Status in python-apt source package in Groovy:
  New
Status in python-apt package in Debian:
  Unknown

Bug description:
  [Impact]

  USN-4668-1 introduced a regression in python-apt when using certain
  APIs with a file handle.

  [Test case]

  # Landscape scenario:
  1) On the Landscape server, create a package profile that installs a single 
package, 'hello' is enough.
  2) On the Landscape server, apply the package profile to a client
  3) On the Landscape client, verify that there is no segfault message on 
'/var/log/kern.log'
  4) On the Landscape server, verify that the activity to apply the package 
profile ends with success.

  Step 3) would show a segfault and step 4), the activity would stay 'In
  Progress' forever.

  # dak scenario:
  dak crashes with a segmentation fault in python3-apt when processing
  uploads or processing the NEW queue on ftp-master; and also on my
  playground server (used to generate the backtrace).

  [Where problems could occurs]

  [Other info]

  See Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000

  Fix:
  
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1907676/+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 1907676] Re: segmentation fault when opening fd

2020-12-20 Thread Eric Desrochers

This is fixed in active development release (hirsute):

python-apt (2.1.7) unstable; urgency=medium

  * SECURITY UPDATE: various memory and file descriptor leaks (LP: #1899193)
- python/arfile.cc, python/generic.h, python/tag.cc, python/tarfile.cc:
  fix file descriptor and memory leaks
- python/apt_instmodule.cc, python/apt_instmodule.h, python/arfile.h:
  Avoid reference cycle with control,data members in apt_inst.DebFile
  objects
- tests/test_cve_2020_27351.py: Test cases for DebFile (others not easily
  testable)
  * Regression fixes for the updates merged too:
- arfile.cc: Fix segmentation fault when opening fd, track lifetime 
correctly
  (Closes: #977000)
- arfile: Regression: Collect file<->deb/ar reference cycles

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

Title:
  segmentation fault when opening fd

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Focal:
  New
Status in python-apt source package in Groovy:
  New
Status in python-apt package in Debian:
  Unknown

Bug description:
  [Impact]

  USN-4668-1 introduced a regression in python-apt when using certain
  APIs with a file handle.

  [Test case]

  # Landscape scenario:
  1) On the Landscape server, create a package profile that installs a single 
package, 'hello' is enough.
  2) On the Landscape server, apply the package profile to a client
  3) On the Landscape client, verify that there is no segfault message on 
'/var/log/kern.log'
  4) On the Landscape server, verify that the activity to apply the package 
profile ends with success.

  Step 3) would show a segfault and step 4), the activity would stay 'In
  Progress' forever.

  # dak scenario:
  dak crashes with a segmentation fault in python3-apt when processing
  uploads or processing the NEW queue on ftp-master; and also on my
  playground server (used to generate the backtrace).

  [Where problems could occurs]

  [Other info]

  See Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000

  Fix:
  
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1907676/+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 1903903] Re: [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing

2020-12-20 Thread Stilor

Thanks, I can confirm that the workaround in bug 1897965 (changing the
line in pipewire.conf) worked for me. Perhaps this is another duplicate
of that bug.

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

Title:
  [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After every reboot, the profile named "Analog Stereo Duplex" keeps
  disappearing on my laptop; only "Analog Stereo Input" and "Analog
  Stereo Output" are present. Without "duplex", I cannot use both the
  built-in microphone and the speakers/headphones at the same time.

  A workaround I found is to remove the user's configuration for
  pulseaudio and restart it:

  rm -rf .config/pulse
  pulseaudio -k

  This brings the "Analog Stereo Duplex" profile back until the next
  reboot.

  This problem started after an upgrade from Ubuntu 20.04 to 20.10.

  I made a screencast of this: https://youtu.be/Vlz5471EYVQ

  The laptop is MSI WE73-8SK.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf]
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov 11 10:50:54 2020
  InstallationDate: Installed on 2019-01-08 (673 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-29 (13 days ago)
  dmi.bios.date: 05/20/2019
  dmi.bios.release: 1.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C5IWS.10F
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C5IWS.10F:bd05/20/2019:br1.15:svnMicro-StarInternationalCo.,Ltd.:pnWE738SK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: WE
  dmi.product.name: WE73 8SK
  dmi.product.sku: 17C5.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1903903/+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 1907676] Re: segmentation fault when opening fd

2020-12-20 Thread Eric Desrochers

@julian, thanks for the quick reply. Will do.

** Changed in: python-apt (Ubuntu)
   Status: New => Fix Released

** Description changed:

  [Impact]
  
  USN-4668-1 introduced a regression in python-apt when using certain APIs
  with a file handle.
  
  [Test case]
  
  # Landscape scenario:
  1) On the Landscape server, create a package profile that installs a single 
package, 'hello' is enough.
  2) On the Landscape server, apply the package profile to a client
  3) On the Landscape client, verify that there is no segfault message on 
'/var/log/kern.log'
  4) On the Landscape server, verify that the activity to apply the package 
profile ends with success.
  
  Step 3) would show a segfault and step 4), the activity would stay 'In
  Progress' forever.
  
- [Where problem could occurs]
+ # dak scenario:
+ dak crashes with a segmentation fault in python3-apt when processing
+ uploads or processing the NEW queue on ftp-master; and also on my
+ playground server (used to generate the backtrace).
+ 
+ [Where problems could occurs]
  
  [Other info]
  
  See Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000
  
  Fix:
  
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

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

Title:
  segmentation fault when opening fd

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Focal:
  New
Status in python-apt source package in Groovy:
  New
Status in python-apt package in Debian:
  Unknown

Bug description:
  [Impact]

  USN-4668-1 introduced a regression in python-apt when using certain
  APIs with a file handle.

  [Test case]

  # Landscape scenario:
  1) On the Landscape server, create a package profile that installs a single 
package, 'hello' is enough.
  2) On the Landscape server, apply the package profile to a client
  3) On the Landscape client, verify that there is no segfault message on 
'/var/log/kern.log'
  4) On the Landscape server, verify that the activity to apply the package 
profile ends with success.

  Step 3) would show a segfault and step 4), the activity would stay 'In
  Progress' forever.

  # dak scenario:
  dak crashes with a segmentation fault in python3-apt when processing
  uploads or processing the NEW queue on ftp-master; and also on my
  playground server (used to generate the backtrace).

  [Where problems could occurs]

  [Other info]

  See Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000

  Fix:
  
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1907676/+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 1907676] Re: segmentation fault when opening fd

2020-12-20 Thread Julian Andres Klode

They prepared the updates on the same day as the fix (well the full
regression fix with the follow-up commits) but did not roll out the fix
so far because only dak reported a regression and codesearch did not
yield any other users of that interface.

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

Title:
  segmentation fault when opening fd

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Focal:
  New
Status in python-apt source package in Groovy:
  New
Status in python-apt package in Debian:
  Unknown

Bug description:
  [Impact]

  USN-4668-1 introduced a regression in python-apt when using certain
  APIs with a file handle.

  [Test case]

  # Landscape scenario:
  1) On the Landscape server, create a package profile that installs a single 
package, 'hello' is enough.
  2) On the Landscape server, apply the package profile to a client
  3) On the Landscape client, verify that there is no segfault message on 
'/var/log/kern.log'
  4) On the Landscape server, verify that the activity to apply the package 
profile ends with success.

  Step 3) would show a segfault and step 4), the activity would stay 'In
  Progress' forever.

  # dak scenario:
  dak crashes with a segmentation fault in python3-apt when processing
  uploads or processing the NEW queue on ftp-master; and also on my
  playground server (used to generate the backtrace).

  [Where problems could occurs]

  [Other info]

  See Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000

  Fix:
  
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1907676/+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 1907676] Re: segmentation fault when opening fd

2020-12-20 Thread Julian Andres Klode

Eric, the updates are built ready in the security team PPA since Dec 10
and only need to be released. I've subscribed security team, but you
might want to talk to them directly.

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

Title:
  segmentation fault when opening fd

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Focal:
  New
Status in python-apt source package in Groovy:
  New
Status in python-apt package in Debian:
  Unknown

Bug description:
  [Impact]

  USN-4668-1 introduced a regression in python-apt when using certain
  APIs with a file handle.

  [Test case]

  # Landscape scenario:
  1) On the Landscape server, create a package profile that installs a single 
package, 'hello' is enough.
  2) On the Landscape server, apply the package profile to a client
  3) On the Landscape client, verify that there is no segfault message on 
'/var/log/kern.log'
  4) On the Landscape server, verify that the activity to apply the package 
profile ends with success.

  Step 3) would show a segfault and step 4), the activity would stay 'In
  Progress' forever.

  # dak scenario:
  dak crashes with a segmentation fault in python3-apt when processing
  uploads or processing the NEW queue on ftp-master; and also on my
  playground server (used to generate the backtrace).

  [Where problems could occurs]

  [Other info]

  See Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000

  Fix:
  
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1907676/+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 1907676] Re: segmentation fault when opening fd

2020-12-20 Thread Eric Desrochers

This package is 'native' and I don't want for instance to introduce
'quilt' before talking to the maintainer.

@julian, how do you want to proceed to fix this bug in python-apt ?

- Eric

** Description changed:

  [Impact]
  
  USN-4668-1 introduced a regression in python-apt when using certain APIs
  with a file handle.
  
  [Test case]
  
- # Landscape scenario: 
+ # Landscape scenario:
  1) On the Landscape server, create a package profile that installs a single 
package, 'hello' is enough.
  2) On the Landscape server, apply the package profile to a client
  3) On the Landscape client, verify that there is no segfault message on 
'/var/log/kern.log'
  4) On the Landscape server, verify that the activity to apply the package 
profile ends with success.
  
  Step 3) would show a segfault and step 4), the activity would stay 'In
  Progress' forever.
  
  [Where problem could occurs]
  
  [Other info]
  
  See Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000
  
  Fix:
  
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

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

Title:
  segmentation fault when opening fd

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Focal:
  New
Status in python-apt source package in Groovy:
  New
Status in python-apt package in Debian:
  Unknown

Bug description:
  [Impact]

  USN-4668-1 introduced a regression in python-apt when using certain
  APIs with a file handle.

  [Test case]

  # Landscape scenario:
  1) On the Landscape server, create a package profile that installs a single 
package, 'hello' is enough.
  2) On the Landscape server, apply the package profile to a client
  3) On the Landscape client, verify that there is no segfault message on 
'/var/log/kern.log'
  4) On the Landscape server, verify that the activity to apply the package 
profile ends with success.

  Step 3) would show a segfault and step 4), the activity would stay 'In
  Progress' forever.

  # dak scenario:
  dak crashes with a segmentation fault in python3-apt when processing
  uploads or processing the NEW queue on ftp-master; and also on my
  playground server (used to generate the backtrace).

  [Where problems could occurs]

  [Other info]

  See Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000

  Fix:
  
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1907676/+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 1907676] Re: segmentation fault when opening fd

2020-12-20 Thread Julian Andres Klode

Yes the security team has the packages ready to go out for a week now
essentially.

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

Title:
  segmentation fault when opening fd

Status in python-apt package in Ubuntu:
  New
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Focal:
  New
Status in python-apt source package in Groovy:
  New
Status in python-apt package in Debian:
  Unknown

Bug description:
  [Impact]

  USN-4668-1 introduced a regression in python-apt when using certain
  APIs with a file handle.

  [Test case]

  # Landscape scenario:
  1) On the Landscape server, create a package profile that installs a single 
package, 'hello' is enough.
  2) On the Landscape server, apply the package profile to a client
  3) On the Landscape client, verify that there is no segfault message on 
'/var/log/kern.log'
  4) On the Landscape server, verify that the activity to apply the package 
profile ends with success.

  Step 3) would show a segfault and step 4), the activity would stay 'In
  Progress' forever.

  [Where problem could occurs]

  [Other info]

  See Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000

  Fix:
  
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1907676/+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 1907676] Re: segmentation fault when opening fd

2020-12-20 Thread Eric Desrochers

** Description changed:

+ [Impact]
+ 
  USN-4668-1 introduced a regression in python-apt when using certain APIs
  with a file handle.
  
+ [Test case]
+ 
+ # Landscape scenario: 
+ 1) On the Landscape server, create a package profile that installs a single 
package, 'hello' is enough.
+ 2) On the Landscape server, apply the package profile to a client
+ 3) On the Landscape client, verify that there is no segfault message on 
'/var/log/kern.log'
+ 4) On the Landscape server, verify that the activity to apply the package 
profile ends with success.
+ 
+ Step 3) would show a segfault and step 4), the activity would stay 'In
+ Progress' forever.
+ 
+ [Where problem could occurs]
+ 
+ [Other info]
+ 
  See Debian bug:
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000
  
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000
+ Fix:
+ 
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

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

Title:
  segmentation fault when opening fd

Status in python-apt package in Ubuntu:
  New
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Focal:
  New
Status in python-apt source package in Groovy:
  New
Status in python-apt package in Debian:
  Unknown

Bug description:
  [Impact]

  USN-4668-1 introduced a regression in python-apt when using certain
  APIs with a file handle.

  [Test case]

  # Landscape scenario:
  1) On the Landscape server, create a package profile that installs a single 
package, 'hello' is enough.
  2) On the Landscape server, apply the package profile to a client
  3) On the Landscape client, verify that there is no segfault message on 
'/var/log/kern.log'
  4) On the Landscape server, verify that the activity to apply the package 
profile ends with success.

  Step 3) would show a segfault and step 4), the activity would stay 'In
  Progress' forever.

  [Where problem could occurs]

  [Other info]

  See Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000

  Fix:
  
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1907676/+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 1907676] Re: segmentation fault when opening fd

2020-12-20 Thread David Negreira

Hello,

I have tested with the test package 1.6.5ubuntu0.4+testpkg20201220b1
provided by ~slashd on his ppa[1] on bionic with all updates applied and
this fixes the segmentation fault issue.

Steps to test:
1) On the LDS server, create a package profile that installs a single package, 
'hello' is enough.
2) On the LDS server, apply the package profile to a client
3) On the LDS client, verify that there is no segfault message on 
'/var/log/kern.log'
4) On the LDS server, verify that the activity to apply the package profile 
ends with success.

Before ~slashd fix, step 3) would show a segfault and step 4), the
activity would stay 'In Progress' forever.

[1] https://launchpad.net/~slashd/+archive/ubuntu/sruverif

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

Title:
  segmentation fault when opening fd

Status in python-apt package in Ubuntu:
  New
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Focal:
  New
Status in python-apt source package in Groovy:
  New
Status in python-apt package in Debian:
  Unknown

Bug description:
  USN-4668-1 introduced a regression in python-apt when using certain
  APIs with a file handle.

  See Debian bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1907676/+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 1907676] Re: segmentation fault when opening fd

2020-12-20 Thread Eric Desrochers

The current situation of python-apt is somewhat critical as no packages
can be pushed via Landscape to machines at the moment. This is causing
landscape-package-changer to segfault as follows:

[apport-retrace]
Core was generated by `/usr/bin/python3 /usr/bin/landscape-package-changer 
--quiet'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 ararchive_new (type=0x7f652626e0a0 , args=, 
kwds=)
at python/arfile.cc:438


This seems to be a fix candidate:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

- Eric

** Tags added: seg sts

** Also affects: python-apt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: python-apt (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: python-apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: python-apt (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: python-apt (Ubuntu Groovy)
   Importance: Undecided => High

** Changed in: python-apt (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: python-apt (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: python-apt (Ubuntu)
   Importance: Undecided => High

** Changed in: python-apt (Ubuntu Bionic)
   Importance: Undecided => Critical

** Changed in: python-apt (Ubuntu Bionic)
   Importance: Critical => High

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

Title:
  segmentation fault when opening fd

Status in python-apt package in Ubuntu:
  New
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Focal:
  New
Status in python-apt source package in Groovy:
  New
Status in python-apt package in Debian:
  Unknown

Bug description:
  USN-4668-1 introduced a regression in python-apt when using certain
  APIs with a file handle.

  See Debian bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1907676/+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 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default

2020-12-20 Thread David Reagan

I just ran into this issue myself on 20.04. Specifically I was adding my
own internal nameserver to a vm.

@Ubfan, why is stub-resolv.conf the correct file?

The file that /etc/systemd/resolved.conf updates is
/run/systemd/resolve/resolv.conf. As far as I can tell, the proper way
to update /etc/resolv.conf is via /etc/systemd/resolved.conf. So if I
want my changes to apply, then the /etc/resolv.conf link should point to
the file systemd actually changes.

Or is there a different method of updating what nameservers your
computer uses? If there is, why is systemd involved with resolv.conf at
all?

Anyway, I believe this is a bug. Fortunately not one that effects people
who don't know how to find the workarounds, but still a bug. I do hope
it eventually gets fixed.

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

Title:
  The symbolic link /etc/resolv.conf points to the wrong file by default

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When using nslookup for local machine names, the local DNS was being
  ignored (not queried) and none of the local machines could be found.

  After much research and digging, it was discovered that the cause was
  the incorrect symbolic link /etc/resolv.conf file.

  The default install caused systemd-resolve to configure the link to point to 
the stub file:
  /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

  Reomving that link and pointing it to the correct file solved the DNS lookup 
issue. The correct link looks like this:
  /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

  
  Steps used to test the bug before fixing the link is to perform an nslookup 
on a local (non FQDN) machine that is in your local DNS (my router is my DNS 
server for this case) Here is an example of the incorrect output:

  $ nslookup web1

  Server: 127.0.0.53
  Address:127.0.0.53#53

  ** server can't find web1: SERVFAIL

  
  Switching the symbolic link solves the problem. Here is my solution:

  $ sudo rm -f /etc/resolv.conf
  $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

  
  After switching the symbolic link, the nslookup functions properly.

  $ nslookup web1

  Server: 192.168.1.1
  Address:192.168.1.1#53

  Name:   web1
  Address: 192.168.1.107

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  1 05:28:41 2018
  InstallationDate: Installed on 2018-01-20 (131 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5755
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=7fe151d3-4033-4903-b356-341d9f16e124 ro acpi=force
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (33 days ago)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0VY15F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/27/2015:svnDellInc.:pnInspiron5755:pvrA08:rvnDellInc.:rn0VY15F:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 5755
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774632/+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 1908699] Re: New bugfix release 20.2.6

2020-12-20 Thread Boaz Dodin

There is some dependency error in 20.2.6-0ubuntu0.20.04.1 package:
The "libegl-mesa0" package could not be marked for installation or upgrade:
Depends: libegl-mesa0 (=20.2.6-0ubuntu0.20.04.1), but 
20.2.6-0ubuntu0.20.04.1 is to be installed

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

Title:
  New bugfix release 20.2.6

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 20.2.x-series, we should put it
  in groovy so latest bugfixes would get there, and for focal because
  that would minimize the risk of regressions when going from 20.0.x to
  20.2.x.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699/+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 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat

2020-12-20 Thread Frank Heimes

** Also affects: elfutils (Ubuntu Hirsute)
   Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
   Status: New

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

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

Title:
  Ubuntu 20.10 - elfutils unwinding broken for s390 compat

Status in Ubuntu on IBM z Systems:
  New
Status in elfutils package in Ubuntu:
  New
Status in elfutils source package in Groovy:
  New
Status in elfutils source package in Hirsute:
  New

Bug description:
  ---Problem Description---
  libdw unwinding fails for 32 bit binaries.
   
  Elfutils biarch test currently fails on s390x doing unwinding for a 32 bit 
process.

  FAIL: run-backtrace-native-biarch.sh
  

  0x557e7000  0x557eb000  /root/elfutils/tests/backtrace-child-biarch
  0x7dba4000  0x7dd51000  /usr/lib/libc-2.32.so
  0x7dd53000  0x7dd7  /usr/lib/libpthread-2.32.so
  0x7dd7f000  0x7dda6000  /usr/lib/ld-2.32.so
  TID 376858:
  # 0 0x7dd6668a  raise
  # 1 0x7fd0ef60 - 1  
  /root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information 
found
  backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL && 
strcmp (symname, "sigusr2") == 0' failed.
  ./test-subr.sh: line 84: 376822 Aborted (core dumped) 
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH" 
$VALGRIND_CMD "$@"
  backtrace-child-biarch: no main
  FAIL run-backtrace-native-biarch.sh (exit status: 1)

  Patch has already been posted and upstream committed:
  https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html

  Please pick up the following commit for the next release:
  commit e4d985a3c1c873f77d20fa0cd421458cc2824996
  Author: Andreas Krebbel 
  Date:   Thu Nov 19 20:32:24 2020 +0100

  IBM Z: Fix endianess problem in pid_memory_read
  
  The cached reads lack the big endian adjustments done in the fallback
  path.
  
  Signed-off-by: Andreas Krebbel 

  
  The patch applies cleanly ontop of elfutils_0.181-1.

  
  strace right now is not built with unwinding support for IBM Z although both 
variants should work - libdw and libunwind.

  Other distros use libdw from elfutils while Ubuntu on x86 appears to
  use libunwind. libdw and libunwind do support IBM Z.

  It would be good to build strace with unwinding support for Z.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1908756/+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 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat

2020-12-20 Thread Frank Heimes

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

Title:
  Ubuntu 20.10 - elfutils unwinding broken for s390 compat

Status in Ubuntu on IBM z Systems:
  New
Status in elfutils package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  libdw unwinding fails for 32 bit binaries.
   
  Elfutils biarch test currently fails on s390x doing unwinding for a 32 bit 
process.

  FAIL: run-backtrace-native-biarch.sh
  

  0x557e7000  0x557eb000  /root/elfutils/tests/backtrace-child-biarch
  0x7dba4000  0x7dd51000  /usr/lib/libc-2.32.so
  0x7dd53000  0x7dd7  /usr/lib/libpthread-2.32.so
  0x7dd7f000  0x7dda6000  /usr/lib/ld-2.32.so
  TID 376858:
  # 0 0x7dd6668a  raise
  # 1 0x7fd0ef60 - 1  
  /root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information 
found
  backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL && 
strcmp (symname, "sigusr2") == 0' failed.
  ./test-subr.sh: line 84: 376822 Aborted (core dumped) 
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH" 
$VALGRIND_CMD "$@"
  backtrace-child-biarch: no main
  FAIL run-backtrace-native-biarch.sh (exit status: 1)

  Patch has already been posted and upstream committed:
  https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html

  Please pick up the following commit for the next release:
  commit e4d985a3c1c873f77d20fa0cd421458cc2824996
  Author: Andreas Krebbel 
  Date:   Thu Nov 19 20:32:24 2020 +0100

  IBM Z: Fix endianess problem in pid_memory_read
  
  The cached reads lack the big endian adjustments done in the fallback
  path.
  
  Signed-off-by: Andreas Krebbel 

  
  The patch applies cleanly ontop of elfutils_0.181-1.

  
  strace right now is not built with unwinding support for IBM Z although both 
variants should work - libdw and libunwind.

  Other distros use libdw from elfutils while Ubuntu on x86 appears to
  use libunwind. libdw and libunwind do support IBM Z.

  It would be good to build strace with unwinding support for Z.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1908756/+subscriptions

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

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

2020-12-20 Thread Jean-Baptiste Perrin

Also I hate to say this but how on earth is this bug classified as "Fix
Released" despite happening on a fresh Ubuntu image install?

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

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

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

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

  So what we do is change that to a warning.

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64

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

2020-12-20 Thread Jean-Baptiste Perrin

I got this same bug when trying to reinstall Ubuntu 20.10.04 LTS after a
dual boot Windows install had killed my ubuntu. I have Nvidia and I did
chose to download drivers during install. How do we solve this problem?
Is there a valid workaround?

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

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

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

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

  So what we do is change that to a warning.

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64

[Touch-packages] [Bug 1908818] [NEW] pure packaging of libnss3

2020-12-20 Thread Sergey Ivanov

Public bug reported:

dpkg -L libnss3
/.
/usr
/usr/lib
/usr/lib/${DEB_HOST_MULTIARCH}
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libnss3.so
/usr/lib/x86_64-linux-gnu/libnssutil3.so
/usr/lib/x86_64-linux-gnu/libsmime3.so
/usr/lib/x86_64-linux-gnu/libssl3.so
/usr/lib/x86_64-linux-gnu/nss
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
/usr/share
/usr/share/doc
/usr/share/doc/libnss3
/usr/share/doc/libnss3/changelog.Debian.gz
/usr/share/doc/libnss3/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libnss3
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk


as we can see soft links to libraries do nor resolve ${DEB_HOST_MULTIARCH} to 
x86_64-linux-gnu

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Dec 20 14:36:10 2020
SourcePackage: nss
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  pure packaging of libnss3

Status in nss package in Ubuntu:
  New

Bug description:
  dpkg -L libnss3
  /.
  /usr
  /usr/lib
  /usr/lib/${DEB_HOST_MULTIARCH}
  /usr/lib/x86_64-linux-gnu
  /usr/lib/x86_64-linux-gnu/libnss3.so
  /usr/lib/x86_64-linux-gnu/libnssutil3.so
  /usr/lib/x86_64-linux-gnu/libsmime3.so
  /usr/lib/x86_64-linux-gnu/libssl3.so
  /usr/lib/x86_64-linux-gnu/nss
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
  /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
  /usr/share
  /usr/share/doc
  /usr/share/doc/libnss3
  /usr/share/doc/libnss3/changelog.Debian.gz
  /usr/share/doc/libnss3/copyright
  /usr/share/lintian
  /usr/share/lintian/overrides
  /usr/share/lintian/overrides/libnss3
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk

  
  as we can see soft links to libraries do nor resolve ${DEB_HOST_MULTIARCH} to 
x86_64-linux-gnu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libnss3 2:3.55-1ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Dec 20 14:36:10 2020
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1908818/+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 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

2020-12-20 Thread Olivier V

I compiled 5.10 kernel downloaded here 
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
and applied the patch given here 
https://marc.info/?l=linux-bluetooth=160378222632366=2.

I works perfectly on my rtl8822cu device, with suspend and resume too.

To solve the bug it is only necessary to add the patch to the next
kernel.

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

Title:
  Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
  laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

Status in Linux:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
  to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.

  I've been unsuccessful to pair with 2 different bluetooth mice.
  However bluetooth seems to work with other devices. I'm under the
  impression that this problem only happens with Bluetooth LE devices.

  Trying to pair using bluetoothctl fails with the
  org.bluez.Error.AuthenticationCanceled error:

  [bluetooth]# pair E5:5B:67:2A:09:76
  Attempting to pair with E5:5B:67:2A:09:76
  [CHG] Device E5:5B:67:2A:09:76 Connected: yes
  [CHG] Device E5:5B:67:2A:09:76 Connected: no
  Failed to pair: org.bluez.Error.AuthenticationCanceled

  A quick google search for org.bluez.Error.AuthenticationCanceled
  reported nothing relevant.

  Running btmon while trying to pair with the device gives me the
  following:

  Bluetooth monitor ver 5.53
  = Note: Linux version 5.4.0-40-generic (x86_64)   
0.998188
  = Note: Bluetooth subsystem version 2.22  
0.998193
  = New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0) 
 [hci0] 0.998194
  = Open Index: E8:6F:38:9C:2B:3C   
 [hci0] 0.998195
  = Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)   
 [hci0] 0.998197
  @ MGMT Open: bluetoothd (privileged) version 1.14 
   {0x0001} 0.998198
  @ MGMT Open: btmon (privileged) version 1.14  
   {0x0002} 0.998310
  @ MGMT Command: Pair Device (0x0019) plen 8   
{0x0001} [hci0] 8.162442
  LE Address: E5:5B:67:2A:09:76 (Static)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8   
  #1 [hci0] 8.162527
  Own address type: Public (0x00)
  Filter policy: Ignore not in white list (0x01)
  PHYs: 0x01
  Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
  > HCI Event: Command Complete (0x0e) plen 4   
  #2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
  Status: Success (0x00)
  < HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6   
  #3 [hci0] 8.284654
  Extended scan: Enabled (0x01)
  Filter duplicates: Enabled (0x01)
  Duration: 0 msec (0x)
  Period: 0.00 sec (0x)
  > HCI Event: Command Complete (0x0e) plen 4   
  #4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
  Status: Success (0x00)
  > HCI Event: LE Meta Event (0x3e) plen 52 
  #5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
  Num reports: 1
  Entry 0
Event type: 0x0013
  Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
  Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI

[Touch-packages] [Bug 1891761] Re: Add a way to change the application_id of a toplevel wayland GdkSurface (so LibreOffice can reuse toplevels and get the right task icons in Wayland)

2020-12-20 Thread Amr Ibrahim

I've tested and this is now fixed in Groovy.

Could this be SRUed to Focal?

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

Title:
  Add a way to change the application_id of a toplevel wayland
  GdkSurface (so LibreOffice can reuse toplevels and get the right task
  icons in Wayland)

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  This is already committed upstream in GTK 3.24.22:
  
https://gitlab.gnome.org/GNOME/gtk/-/commit/2b74662b2befebb988b63118c8d7ee8c9d90e736

  LibreOffice in a Wayland session uses the same generic icon for its
  different apps, so when I have Writer, Calc and Impress open, they all
  share the same generic LO icon, which is not a very good experience.
  The upstream GTK commit should fix that, however, I have not tested
  it.

  The reason why I'm using Wayland in Ubuntu 20.04 is that I have a
  second 4K UHD monitor and fractional scaling + 4K UHD resolution is
  unusable in X11, so I'm kind of forced to use Wayland for fractional
  scaling. See bug #1890802.

  So I hope this fix could be committed in Ubuntu 20.04 to improve the
  LibreOffice experience in Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgtk-3-0 3.24.20-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 15 17:14:07 2020
  InstallationDate: Installed on 2020-04-26 (111 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  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/1891761/+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 1908814] [NEW] systemd : inconsistencies in man pages

2020-12-20 Thread Sergey Ivanov

Public bug reported:

>From "man systemd-system.conf":

When packages need to customize the configuration, they can install
configuration snippets in /usr/lib/systemd/*.conf.d/ or
/usr/local/lib/systemd/*.conf.d/. The main configuration file is read
before any of the configuration directories, and has the lowest
precedence; entries in a file in any configuration directory override
entries in the single configuration file. Files in the *.conf.d/
configuration subdirectories are sorted by their filename in
lexicographic order, regardless of in which of the subdirectories they
reside. When multiple files specify the same option, for options which
accept just a single value, the entry in the file with the
lexicographically latest name takes precedence. For options which accept
a list of values, entries are collected as they occur in files sorted
lexicographically.


However from "man SYSTEMD":

DIRECTORIES
   System unit directories
   The systemd system manager reads unit configuration from various 
directories. Packages that want to install unit files shall place them in the 
directory returned by pkg-config systemd
   --variable=systemdsystemunitdir. Other directories checked are 
/usr/local/lib/systemd/system and /lib/systemd/system. User configuration 
always takes precedence.  pkg-config systemd
   --variable=systemdsystemconfdir returns the path of the system 
configuration directory. Packages should alter the content of these directories 
only with the enable and disable commands of
   the systemctl(1) tool. Full list of directories is provided in 
systemd.unit(5).

   User unit directories
   Similar rules apply for the user unit directories. However, here the 
XDG Base Directory specification[6] is followed to find units. Applications 
should place their unit files in the
   directory returned by pkg-config systemd 
--variable=systemduserunitdir. Global configuration is done in the directory 
reported by pkg-config systemd --variable=systemduserconfdir. The
   enable and disable commands of the systemctl(1) tool can handle both 
global (i.e. for all users) and private (for one user) enabling/disabling of 
units. Full list of directories is provided
   in systemd.unit(5).


Obviously, the 2nd one is more precise about directories for
configuration files and therefore should be used in all cases. 1st
paragraph of doc should link there

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

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

Title:
  systemd : inconsistencies in man pages

Status in openssh package in Ubuntu:
  New

Bug description:
  From "man systemd-system.conf":

  When packages need to customize the configuration, they can install
  configuration snippets in /usr/lib/systemd/*.conf.d/ or
  /usr/local/lib/systemd/*.conf.d/. The main configuration file is read
  before any of the configuration directories, and has the lowest
  precedence; entries in a file in any configuration directory override
  entries in the single configuration file. Files in the *.conf.d/
  configuration subdirectories are sorted by their filename in
  lexicographic order, regardless of in which of the subdirectories they
  reside. When multiple files specify the same option, for options which
  accept just a single value, the entry in the file with the
  lexicographically latest name takes precedence. For options which
  accept a list of values, entries are collected as they occur in files
  sorted lexicographically.

  
  However from "man SYSTEMD":

  DIRECTORIES
 System unit directories
 The systemd system manager reads unit configuration from various 
directories. Packages that want to install unit files shall place them in the 
directory returned by pkg-config systemd
 --variable=systemdsystemunitdir. Other directories checked are 
/usr/local/lib/systemd/system and /lib/systemd/system. User configuration 
always takes precedence.  pkg-config systemd
 --variable=systemdsystemconfdir returns the path of the system 
configuration directory. Packages should alter the content of these directories 
only with the enable and disable commands of
 the systemctl(1) tool. Full list of directories is provided in 
systemd.unit(5).

 User unit directories
 Similar rules apply for the user unit directories. However, here 
the XDG Base Directory specification[6] is followed to find units. Applications 
should place their unit files in the
 directory returned by pkg-config systemd 
--variable=systemduserunitdir. Global configuration is done in the directory 
reported by pkg-config systemd --variable=systemduserconfdir. The
 enable and disable commands of the systemctl(1) tool can handle 
both global (i.e.

[Touch-packages] [Bug 1908726] Re: Update the package for Focal Fossa to >= 0.27.3

2020-12-20 Thread lotuspsychje

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

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

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

Title:
  Update the package for Focal Fossa to >= 0.27.3

Status in exiv2 package in Ubuntu:
  New

Bug description:
  The current Darktable from the Focal Fossa repo can't be upgraded
  because it requires libexiv2-27 (>= 0.27.3) and the currently
  available one is libexiv2-27/0.27.2-8ubuntu2

  Can you please update it to >= 0.27.3 ?

  $ sudo apt upgrade darktable
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   darktable : Depends: libexiv2-27 (>= 0.27.3) but 0.27.2-8ubuntu2 is to be 
installed
   Depends: libilmbase25 (>= 2.5.3) but it is not installable
   Depends: libjson-glib-1.0-0 (>= 1.5.2) but 1.4.4-2ubuntu2 is to 
be installed
   Depends: libopenexr25 (>= 2.5.3) but it is not installable
  E: Broken packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1908726/+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 1713279] Re: package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Touch-packages] [Bug 1902244] Re: Backport packages for 20.04.2 HWE stack

[Touch-packages] [Bug 1908843] [NEW] fstrim spins up HDDs

[Touch-packages] [Bug 1907676] Re: segmentation fault when opening fd

[Touch-packages] [Bug 1907676] Re: segmentation fault when opening fd

[Touch-packages] [Bug 1903903] Re: [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing

[Touch-packages] [Bug 1907676] Re: segmentation fault when opening fd

[Touch-packages] [Bug 1907676] Re: segmentation fault when opening fd

[Touch-packages] [Bug 1907676] Re: segmentation fault when opening fd

[Touch-packages] [Bug 1907676] Re: segmentation fault when opening fd

[Touch-packages] [Bug 1907676] Re: segmentation fault when opening fd

[Touch-packages] [Bug 1907676] Re: segmentation fault when opening fd

[Touch-packages] [Bug 1907676] Re: segmentation fault when opening fd

[Touch-packages] [Bug 1907676] Re: segmentation fault when opening fd

[Touch-packages] [Bug 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default

[Touch-packages] [Bug 1908699] Re: New bugfix release 20.2.6

[Touch-packages] [Bug 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat

[Touch-packages] [Bug 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat

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

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

[Touch-packages] [Bug 1908818] [NEW] pure packaging of libnss3

[Touch-packages] [Bug 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

[Touch-packages] [Bug 1891761] Re: Add a way to change the application_id of a toplevel wayland GdkSurface (so LibreOffice can reuse toplevels and get the right task icons in Wayland)

[Touch-packages] [Bug 1908814] [NEW] systemd : inconsistencies in man pages

[Touch-packages] [Bug 1908726] Re: Update the package for Focal Fossa to >= 0.27.3

25 matches

Site Navigation

Mail list logo

Footer information